Am I the First? Hard Bricked H9500+

[pcprice76]

Nothing to do... tried also with 1312 versione of sptool.. getting always a 4k file

[stevenma61]

Nothing to do... tried also with 1312 versione of sptool.. getting always a 4k file

open yr scatter file with microsoft wordd, or note, try to check if your scatter look like this

PRELOADER 0x0
{
}
MBR 0x600000

so the second one start with 0x600000 , it mean the preloader sit from 0 x000 to 0x600000

so if u read back the ROM_0 from your working phone(S5) it will copy about 6mb
create the ROM_0 with Sp flash tool, Read Back button, did u get the green circle


after that u process thr ROM_0 with the MTK tools

dont be confused, youhave two ROM_0 file, try to seach in the folder in the computer. look for 6mb, or when u save the ROM_0 , u rename it to ROM_AAA, then u will not be confused when u look for this file



and u have to chage the line from 0x0000000
end at 0x600000 , it mean copy start from 0 to 600000 , then u have 6mb file come out at the end

[jamius19]

I've bricked my symphony W125 (mt 6589)
I was trying to flash a room through sp flash tool, then I guess I've to say rip to it!

sometime computer recognizes it as USB Modem Driver, but for most time it's MTK USB port

It detects the phone when I plug it in (I get the normal USB beep beep too) as MTK Com5. I think this is OK. The red line moves across quickly and then it just sits for 41 seconds until it times out and I ge "BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)"

same thing here
what can i do?
any help would be greatly appreciated

[stevenma61]

I've bricked my symphony W125 (mt 6589)
I was trying to flash a room through sp flash tool, then I guess I've to say rip to it!

sometime computer recognizes it as USB Modem Driver, but for most time it's MTK USB port

It detects the phone when I plug it in (I get the normal USB beep beep too) as MTK Com5. I think this is OK. The red line moves across quickly and then it just sits for 41 seconds until it times out and I ge "BROM ERROR: S_FT_ENABLE_DRAM_FAIL (4032)"

same thing here
what can i do?
any help would be greatly appreciated

u have to get the preloader.bin to replace the one in the rom u download, u have to check with someone who has the same model as yours

[dhcj]

Please help me to fix my MT6589 HTC ONE clone. I factory reset my mobile. Then wipe cache using cwm. then restart. now its totally bricked. its not even charging. can't on. no light. no vibration. no recovery mode. even pc cant recognize the device. please help me to fix it. i just bought it. only a week.

[didi8]

I am having the same 4032 error problem, but i do have a user.backup file. is there a possibility of extracting preloader.bin from this file!

Starting recovery on Fri Jan 1 00:05:39 2010
Partition Information:
preloader 0x0000000000600000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003400000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003700000 2 /dev/block/mmcblk0
android 0x0000000028a00000 0x0000000004100000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002cb00000 2 /dev/block/mmcblk0p6
usrdata 0x00000000b6080000 0x0000000034900000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0

recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
7 /system ext4 /dev/block/mmcblk0p5 (null) 0

[stevenma61]

I am having the same 4032 error problem, but i do have a user.backup file. is there a possibility of extracting preloader.bin from this file!

not too sure where u get the file from
but it looks like the same as a file "firmware.info" in the MTK droid root n tool backup file.
the way i saw it is, u did check the firmware before n u just keep the info as a text format file only, actually u did not backup the rom previously.

if u did a correct backup by mtk droid root n tools, then u should have a file folder with files that is about 300MB to 600MB or more in size. and u have a file named "preloader_and_dsp" that is about 2048kb in size in that file folder. then u can process n get the preloader.bin from the file folder.

[TassieAU]

I've not managed to fix my phone as yet (despite three nights working on it!). I have two 'S4 Android' H9500+ phones that were purchased from Japan – one is working and one stops at Android Logo. They have 1gb RAM and 8gb internal SD (and take up to 32gb external SD). They only have Google Japanese input installed so were obviously set up for the Japan market only but my working one works fine in Australia.

Model : GT-H9500 Build number : ALPS.JB2.MP.V1.2

Build date UTC : 20130511-074106 Android v : 4.2.1

Baseband v: MOLY.WR8.W1248.MD.WG.MP.V6.P4, 2013/05/04 18:26

Kernel v : 3.4.5 (root@android) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Sat May 11 15:50:18 CST 2013

I've rooted the working phone and made several attempts to create a working ROM from it using this resource ( [Only registered and activated users can see links Click here to register] ) and the Bedove MTK6577 PDF guide. Every ROM I try to flash including ROMS compiled from my working phone return the error 'BROM ERROR: S_FT_DOWNLOAD_FAIL (4008). The ROMS I'm compiling do not seem big enough and are always missing ANDROID, CACHE and USRDATA files.

I'm using SP Flash 3.1328.0.183 (MTK ALLnOneDA.bin) and MTK Droid Tools V2.4.8.

Any suggestions?

[stevenma61]

Back up the rom from yr working phone by MTK root n tool , button "backup"
After finish , then hit the button "to prepare block for flash tool" in the MTK root n tool

Then use SP flash tool to flash yr back up rom(!file to flash tool) to yr soft brick phone.


U are right, I tried to read back the rom by sp flash tool, I don't get all the file also

[TassieAU]

U are right, I tried to read back the rom by sp flash tool, I don't get all the file also
[/quote]

I'm closer but not there yet. I think my phone didn't properly root the first time I did it. I had rooted it using the 'MT6589 Rooting Package' and noticed that MTK Droid tools did not always have a green box in bottom left corner (was sometimes yellow with a root tab highlighted). I rooted the phone again using the 'Bedove x21 MTK6577 Root Procedure' PDF method and it rooted properly this time.

I then followed your recommendations but every time I run my '!file to flash tool' file through SP Flash tool it populates without UBOOT, SEC_RO, ANDROID, CACHE and USRDATA files. I'm now left wondering if some file names have been changed in my ROM version so are not being picked up by the flash tool. For instance - I have a 'secro' file but no SEC_RO, I have a 'system' file but no ANDROID, I also have a boot and a uboot but neither loads in the UBOOT slot. I don't have any files called CACHE or USRDATA in my backed up ROM.