Alright, newb here.
Now that that is out of the way, let me get to the issue.
History: I was following a howto on theunlockr.com (or however it's spelled) for rooting my myTouch 3g w/ 3.5mm headphone jack. Created goldcard, put sappimg on it, booted phone into bootloader, nothing, didn't recognize the image file. Thinking that the file was bad, I downloaded another sappimg.zip file (which I realize now was a bad mistake). After realizing that the card needed to be empty (no files other than sappimg.zip), put JUST sappimg.zip on goldcard and it worked. It uploaded the zip to memory and flashed. Then it rebooted and was stuck at a Vodafone logo. No bootup, just hangs at logo (I've left it at that for a good 10 minutes, still nothing). I can't flash from fastboot, as the SPL does signature checking. I've tried fastbooting into a recovery image, but the four I've tried so far, won't get past the three droids skating logo (and that's if I use fastboot to erase system, boot, userdata, and cache, otherwise, they'll hang at the Vodafone logo too). I've also wiped every partition on the flash other than the bootloader.
Yesterday, I've even tried to run a couple of RUU's for the thing. I had a friend try all three T-Mobile RUU's for the myTouch (from the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread), all failed with some version (Different failures for each though).
Oh, also, I can't do the goldcard trick anymore, because when it tries to flash the rom, the SPL hangs on the system partition.
So, gentlemen, I do believe I'm screwed.
Any help towards getting it unscrewed (even back to stock) would be greatly appreciated.
Details:
Bootloader screen banner:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
May 8 2009, 21:02:32
Recoveries tried:
recovery-RAv1.0H
recovery-RA-hero-v1.6.2
recovery-RA-magic-v1.3.2H
recovery-RA-sapphire-v1.7.0G
recovery-RA-sapphire-v1.7.0H
Nothing?
So, nothing???
Nevermind.
Sent from my HTC Magic using XDA App
ZeroSigea said:
So, nothing???
Click to expand...
Click to collapse
I also have a MT3G 1.2 with the symptoms you describe - hangs on unzipping the system image in sappimg.zip (2.10.531.3) and (2.10.531.4). Don't even think about trying to flash sappimg.nbh (1.94.531.1) - that got me a brick semi-recoverable via JTAG.
I have also seen the Fail-PU message appear when it tries to flash the system partition (when radio 2.22.23.02 was installed).
I found that you can successfully flash sappimg.zip (2.53.707.2 including eng spl 1.33.2010), but fastboot is useless since you get the (remote: signature verify fail) message. Needless to say, this rom doesn't boot successfully.
In addition to the symptoms you describe, the USB is also broken on my MT3G 1.2, so I would need a solution that doesn't use fastboot.
Has anybody else experienced this problem or something similar with their MT3G 1.2? I would like to collect as much information as I can about this problem. I have so far been unsuccessful in finding a solution
I have working JTAG on my MT3G 1.2, so I can easily softboot any SPL. See wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic for more details.
I had an idea to edit the SPL so that it skips the signature check on any sappimg.zip file you give it, and easily flash a custom sappimg.zip. Another idea I had was to get it to skip checking the main version on any sappimg.zip file you give it.
Does anybody have any ARMv6 (ARM11) disassembly experience? I could only ever get arm-none-eabi-objdump to disassemble the SPL as a ARMv5 binary...
Does anybody have any idea what I'm talking about? Am I crazy?
stewdk said:
I have working JTAG on my MT3G 1.2, so I can easily softboot any SPL. See wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic for more details.
I had an idea to edit the SPL so that it skips the signature check on any sappimg.zip file you give it, and easily flash a custom sappimg.zip. Another idea I had was to get it to skip checking the main version on any sappimg.zip file you give it.
Does anybody have any ARMv6 (ARM11) disassembly experience? I could only ever get arm-none-eabi-objdump to disassemble the SPL as a ARMv5 binary...
Does anybody have any idea what I'm talking about? Am I crazy?
Click to expand...
Click to collapse
I have some ideas that I would like to bounce off you...and I would be willing to provide a phone to try them on...then we could have something to offer because this seems to be a big problem for this phone. Please PM me.
Dude, the post is from September 2010... :0)
Good luck..
mumilover said:
Dude, the post is from September 2010... :0)
Good luck..
Click to expand...
Click to collapse
It may be an old post, but I'm still having the problem I described above
My phone is sitting right here collecting dust, JTAG still hooked up and everything.
jonk26.2, I got your PM. I'm interested.
I just need to get a working openocd installation up and running again - shouldn't take too long.
EDIT: I mean I'm interested in trying your ideas. No need to send me a phone.
Let me tell you where I am and what I am thinking.
I bought a 3.5mm phone on ebay that had this issue...stuck on fastboot screen. I could get into USB fastboot just fine...and could try the goldcard root process just fine...but had the same freeze on unzipping files that everybody else had. I had the brilliant idea that I could use fastboot to erase the bad files so it could unzip files...and in my haste I erased EVERYTHING...no fastboot no nothing...dead. Then I started looking around the site for JTAG and found your post and then I thought...maybe this is the way to start...absolutely wipe the slate clean and start over.
Anyway...my mobo is dead on this phone and I would like to try to fix it if you are game.
jonk26.2 said:
and in my haste I erased EVERYTHING...
Click to expand...
Click to collapse
If you erased the radio, then I'm afraid that even the current JTAG procedure won't help you much... Try seeing if blue LED light mode works - if it does, then you might still have hope. This is discussed in the JTAG thread http://forum.xda-developers.com/showthread.php?t=591048 and also at http://wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic
I know the JTAG thread can be a bear to sift through, but it has a lot of good information, including what kind of equipment they use (I'm using a Stellaris EKC-LM3S6965 eval kit which doubles as a USB-serial adapter if you program it right).
Remember that the MT3G 1.2 3.5mm jack / Fender LE won't boot anything without the stock SPL and a known compatible radio (2.22.23.02 is one).
Yes...Blue LED...nothing else.
jonk26.2 said:
Yes...Blue LED...nothing else.
Click to expand...
Click to collapse
Then in theory un-bricking is possible via jtag and serial cable.
I'm not sure about this, but if your phone is in a condition like mine, then JTAG may only be able to bring it back to the limbo state we've been seeing. Symptoms of this are: 1. seeing something like fastboot remote signature verify fail when fastboot worked (even with an engineering SPL) and 2. stuck at unzipping the system image or getting Fail-PU when installing a sappimg.zip. And as far as I know this only applies to the MT3G 1.2 3.5mm jack.
Wow...
Haven't been on in a while and I come back and see that the thread did blossom into a full discussion. Nice. Sorry to leave y'all out in the dark for so long, but I've been busy (and distracted).
So, my solution was to get it replaced. Cheap, I know, but something had to be done. So, I got another MyTouch 3G and when I was feeling brave again, I tried a different route and went with Universal Androot to root the stock ROM in place and use ClockworkMod to flash CM6 onto the device. Awesome, it worked. So we (me and the girlfriend) enjoyed our MyTouch's until we got fed up with T-Mobile's service (crappy signal, where I live). Switched to AT&T and got a HTC Aria, which I suppose is the MyTouch's cousin.
I feel hopeless
I am also suffering the same problem.
I can access fastboot but I can do nothing [Perfect SPL].
I have created a working gold card but all I'm seeing is the frozen system extraction.
tried almost any possible howto's I can find on the net but to no avail.
due to my experiment on flashing sappimg.zip, I seem have a mutated radio/spl combo!
phone info(s):
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0000 (SAPP31000)
CPLD-13
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
Phone CID: T-MOB010E
Phone version-main: 2.53.707.2
having the same problem
I have tried every combination of firmwares known to man. I have got several to begin flashing, but all stick on the unzipping system. I messed it up by originally following another post for rooting the phone and didnt realize that this my touch 1.2 is special. Apparently the firmware I flashed it with is a 32A firmware and the spl and radio are no good for this phone. So now nothing will flash. Probably have to Jtag it...
I have the same problem.
Using eng spl 1.33.2009 and 1.33.2005 through JTAG on MT3G 1.2,
At first, if I used eng spl 1.33.2009, fastboot flash [partition] [partition.img]
I got: FAILED (remote: image update error).
After that, I switched to eng spl 1.33.2005, somehow I could use fastboot flash hboot boot.nb0 from T-Mobile_US_2.10.531.4. But I only flashed that and rebooted the system to see what happened. Then I cannot do it again.
(Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
Now using eng spl 1.33.2005, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash radio.img.
using eng spl 1.33.2009, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash hboot, boot, radio.img. splash, but stuck at sytem image.
Using eng spl 1.33.2009 through JTAG on MT3G 1.2,
1. Stuck at unzipping the system image.
Or
2. (Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
When the system was stucked at unzipping the system image, the serial cable continues to give message:
[MDDI_HW_ERR] mddi_queue_image timeout
[MDDI_HW_ERR] mddi_queue_image timeout
Something is broken.
I can only flash sappimg.zip with eng 1.33.2010, but it doesn't a working system.
Can anyone shine light on this one?
hubh98 said:
I have the same problem.
Using eng spl 1.33.2009 and 1.33.2005 through JTAG on MT3G 1.2,
At first, if I used eng spl 1.33.2009, fastboot flash [partition] [partition.img]
I got: FAILED (remote: image update error).
After that, I switched to eng spl 1.33.2005, somehow I could use fastboot flash hboot boot.nb0 from T-Mobile_US_2.10.531.4. But I only flashed that and rebooted the system to see what happened. Then I cannot do it again.
(Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
Now using eng spl 1.33.2005, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash radio.img.
using eng spl 1.33.2009, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash hboot, boot, radio.img. splash, but stuck at sytem image.
Using eng spl 1.33.2009 through JTAG on MT3G 1.2,
1. Stuck at unzipping the system image.
Or
2. (Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
When the system was stucked at unzipping the system image, the serial cable continues to give message:
[MDDI_HW_ERR] mddi_queue_image timeout
[MDDI_HW_ERR] mddi_queue_image timeout
Something is broken.
I can only flash sappimg.zip with eng 1.33.2010, but it doesn't a working system.
Can anyone shine light on this one?
Click to expand...
Click to collapse
man, if this IS thru JTAG..., I am losing hope
I still have hope.
I was able to bring it back to work once.
After fastboot flash zip T-Mobile_US_2.10.531.4.zip, stucked at unzipping the system image, I took off the battery and was able to flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully. And system was working but SD card reader was disabled in android system, so I read that I need to root the system, and I followed the
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
and installed the sappimg.zip with (eng spl 2010). Then eng spl 2010 flashed sappimg.zip (T-Mobile_US_2.10.531.4) and stuck at unzipping the system image. [However, it was worked at the very beginning when the MT3G 1.2 with froyo,~~~ Wrong! I didn't use the SAPPIMG with eng spl 2010 at that time, and I only used the universal androot to root the phone~~~ and before I bricked the phone when I used RUU to downgraded it back to Donut.~~This is true. ]
This can explain why I can flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully at first place. So the sappimg.zip with (eng spl 2010) is halmful, because it updates the main version.
When I rebooted the system and used the stock spl 1.33.0013G to reflash (T-Mobile_US_2.10.531.4), I have the "main version is older" error.
It looks like each time it becomes worse, there are some kind of watchdog programs in the system?
Because of the hybrid nature of the MT3G 1.2 (32A hardware/32B ROM), the partitions probably messed up, because I saw "partition update failed".
I just cannot repeat the process, when I jtag the phone,
I also saw
[ERR] partition_read::Failed to read page 19072 or it is empty, when soft boot the system as
http://forum.xda-developers.com/showpost.php?p=5715534&postcount=214.
hubh98 said:
I still have hope.
I was able to bring it back to work once.
After fastboot flash zip T-Mobile_US_2.10.531.4.zip, stucked at unzipping the system image, I took off the battery and was able to flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully. And system was working but SD card reader was disabled in android system, so I read that I need to root the system, and I followed the
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
and installed the sappimg.zip with (eng spl 2010). Then eng spl 2010 flashed sappimg.zip (T-Mobile_US_2.10.531.4) and stuck at unzipping the system image. [However, it was worked at the very beginning when the MT3G 1.2 with froyo, and before I bricked the phone when I used RUU to downgraded it back to Donut.]
When I rebooted the system and used the stock spl 1.33.0013G to reflash (T-Mobile_US_2.10.531.4), I have the "main version is older" error.
It looks like each time it becomes worse, there are some kind of watchdog programs in the system?
Because of the hybrid nature of the MT3G 1.2 (32A hardware/32B ROM), the partitions probably messed up, because I saw "partition update failed".
I just cannot repeat the process, when I jtag the phone,
I also saw
[ERR] partition_read::Failed to read page 19072 or it is empty, when soft boot the system as
http://forum.xda-developers.com/showpost.php?p=5715534&postcount=214.
Click to expand...
Click to collapse
ok bro, I wish you luck on unbricking your phone, let us know if you succeeded!
Can any one help me check the main version of the original MT3G 1.2 before using the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2)?
fastboot getvar version-main
Even after I flashed back to T-Mobile_US_2.10.531.4 (stopped at system), the main version is still 2.53.707.2. I think the main version of T-Mobile_US_2.10.531.4
is 2.10.531.4. So the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2) is potentially harmful at least for some MT3G 1.2.
hubh98 said:
Can any one help me check the main version of the original MT3G 1.2 before using the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2)?
fastboot getvar version-main
Even after I flashed back to T-Mobile_US_2.10.531.4 (stopped at system), the main version is still 2.53.707.2. I think the main version of T-Mobile_US_2.10.531.4
is 2.10.531.4. So the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2) is potentially harmful at least for some MT3G 1.2.
Click to expand...
Click to collapse
I don't hold the unit now, but I hope someone here could lend a hand on this
Hi so I've been searching the forum for 2 days and tried i think is everything but still cant make my phone work..it can only access the fastboot mode now and if i turn on the phone i cant pass the "htc magic" splash screen. And yes i have a goldcard and tried to flash the engineering spl 2010 but it stuck at unzipping system part. I cant flash anything and when i input command it appears as
1.if i input "fastboot flash (partition) "xxxx"" it will show the "remote:verify INFOsignature fail" error
2. if i input "fastboot boot "xxxx"" then it will show the "remote: reproduce boot image with on-flash ramdisk error"
3. error with RUU: the RUU has the main version error
my fastboot screen info:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
May 8 2009,21:02:32
So far i think i might need the original RUU of my phone and swap in engineering spl 2010 in the temp. file as soon as it releases it.Then flash it see if that helps. But i cant find any original RUU on the road...
Help me master!
ps: and yea i would be glad to pay 20 usd if anyone help me to get this thing working again. ^^
you could try my posthttp://forum.xda-developers.com/showthread.php?t=831044
It wont work...
Actually i've tried the 3 official roms via RUU app already and i did get error with RUU as i said so now I just tried the 3 roms from tmobile which means the same as my phone's cid appeared as T-MOBO10 via my goldcard. The 2.10.531.4 and 2.11.531.3 ones failed with it saying" main version is older" and the 1.94.531.1 which extracted as a .nbh file failed at signature checking point. ah...yea, thanks a lot for helping me though.
Type this and post the outcome here:
Code:
fastboot getvar version-main
From there we can try to determine what to do!
main version
It says version-main: 2.16.707.3.
BTW my phone had stock 1.6
If you are getting main version older error it is possible that your goldcard has become ungolden. Try remaking your goldcard, put sappimg.img(found on the how to root MyTouch 1.2 thread) on the root of it, reboot holding volume down and boot and when in hboot screen hold trackball down until it finds sappimg.img and it shoudl update itself. Then reboot to fastboot and flash radio, hboot and recovery. Then reboot to recovery and flash the rom u want.
The goldcard will not let you update a sappimg.zip which has older system version then what you have now!!!
So it's not a faulty goldcard.
The solution:
There is a special sappimg.zip which has an eng spl and is signed by htc :0)
Luckily you have a system version which is lower :0)
If you flash that sappimg.zip you can then flash what ever you want and get the system back on track.
The zip is for the 32A device... but we just need the eng spl to flash the 1.2 device layout.
You game with that ?
I just helped somebody to regain their device using this approach...
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The link above has all what you need.
Follow it to step 10. The rom they use in step 10 is outdated... Use this instead:
Rom: http://khsk.uberitz.net/cm/update-cm-6.0.0-DS-signed.zip
Gapps: http://cyanogenmod-mirror.local.host.name/gapps/gapps-mdpi-tiny-20101020-signed.zip
You should be good to go :0)
Remember, if you get problems post here... don't do something stupid and don't work in the dark...
KNOW WHAT YOU ARE DOING OR ASK FOR HELP :0)
uh...
So I do have questions:
I tried that page b4 and the sappimg.zip in step one does not work with freeze at unzipping system. And the stock spl, radio, &AR recovery simply don't work since they all cannot pass the INFOsignature check.
So should I simply skip to step 10 and flash the special sappimg.zip from you?
And how does that sappimg work with the gapp? I don't know how to use that gapp package...never used it b4. Oh that post mention the use of gapp on step 12...should i do step 10~12 then?
Thanks a million for helping. ^^
Edit: uh... wait a second. do you mean the special sappimg.zip is the sappimg in step1 from that post or is the special sappimg you mean is from your rom link?
continued
well i suppose theres no harm in trying to flash the cm 6.0 update rom via hboot...well the result is the phone back to defualt hboot screen after "checking sappimg.zip". Any suggestion?
Flash the sappimg.zip from the site. It has to work or you have a faulty goldcard.
Redo goldcard and reflash.
The links i provided is only ment to be flashed using custom recovery.
Sent from my SGS-I9000 using XDA App
goldcard
So now suppose i have a faulty goldcard and now i cant access the phone.
Should I format the sd card in windows in fat32 format and then paste my goldcard.img to the reformated sd card again?
PS: I haven't changed anything on my goldcard since the first time i successfully flashed the sappimg.zip the first time. but back then i was stupid and flashed the non-perfect spl one. now i cant flash any sappimg.zip anymore with this same sd card. But now yea i better try to redo it see if that helps.
Thanks.
Check your pm...
I have seen my goldcard change after i use it for some time..
So i have to redo it every time i was gona flash just to make sure!
But you redo yours anyway... it done properly, maybe for the last time :0)
I have the sapphire pvt 32a ship s-on G
hboot-1.33.0013 sapp31000
cpld-13
Radio--6.35.16.19
oct. 21 2009, 22:33:27
RUU USB
Has a microchip with a circle and x through it on the bottom.
I am not clear what happened. I had flashed to this radio and had a eng hboot and Couldn't get recovery to work. So I used the flash tool and flashed the old radio the old hboot and the old recovery back on, and it booted into recovery. Still couldn't flash with out new Radio so I flashed back everything, than it wouldn't boot into recovery so I tried to flash back radio and put a stock rom on it, all the sudden it wouldn't flash the radio or anything so I tried to update with and a tmobile ruu and it got stuck at this screen I cant get out of it.
HELP PLEASE!
I
You got radio/spl mismatch....
What version nr do you have?
Code:
fastboot getvar version-main
fastboot oem h
Main version
version-main 2.10.531.4
I ran the other command and got a list of commands?
Good.... i want that list please :0)
Also, do this command:
Code:
fastboot getvar cid
Also, download this:
https://rapidshare.com/files/454052569/2.10.531.4.zip
https://rapidshare.com/files/450996411/special_sappimg.zip
https://rapidshare.com/files/436753940/2.53.707.2_-_sappimg.zip
Also do a GOLDCARD.
I got your PMs.
I'm extremely busy with my bachelor + work + my new baby-daughter.... so expect some reply-delays :0)
Got your PMs...
I have found a solution for your problems..
Ok... here it goes.
Download these to begin with while you READ (if you not already downloaded them from above post).
https://rapidshare.com/files/454052569/2.10.531.4.zip
http://rapidshare.com/files/450996411/special_sappimg.zip
http://rapidshare.com/files/436753940/2.53.707.2_-_sappimg.zip
IT IS IMPORTANT THAT YOU READ EVERYTHING I WRITE.
The problem is: the device has conflicting spl and radio combo. The spl has an idea of where the radio should be and how big it is ect. When they are not matching the flash of a new radio will most likely fail.
To fix this problem, we need to flash a spl compatible with the 6.35 radio.
But the problem lies in the following. All the RUU/sappimg with a spl compatible with the 6.35 radio has a higher version than yours(starts with 3 something). If we update the version, we cannot flash the desired sappimg which follows. The goldcard will only update up in verion nr, NOT down.
Here comes the trick: I have found a special rom, which is part of a 2-part update which will not update your version nr...
Once the spl is updated and the system restarted, we can now flash any ruu we want using the goldcard. I recommend to flash one with a eng spl inbuilt like the 2.53.707.2 sappimg. But if the device would not accept that sappimg(don't ask me why), try the 2.10.531.4.zip which is the same version nr as you have now.
The steps to follow:
1) Read and understand the above.
2) Rename special_sappimg.zip to sappimg.zip
3) Make sure that you have a working goldcard and flash the sappimg.zip
4) Once the device has rebooted, you should rename the 2.53.707.2_-_sappimg.zip to sappimg.zip and flash it using the goldcard. This image should give you an eng spl. If you device will not accept it, then rename the other rom to sappimg.zip and flash it using the goldcard.
5) If you indeed get the eng spl, then you have full control and we can do almost anything we want. Just post here and we can take it from there. The eng spl has the following nr: 1.33.2010.
If you flashed the stock rom, then you only need to flash custom recovery and you should almost be there... also here post the progress and we will take it from there.
Hope that you will succeed... :0)
I am having this same problem!!! I can't flash any of these and I am stuck in Ruu mode.
SPL/hboot version: 1.33.0013.
Radio version: 6.35.08.29.
Main software version: 2.10.531.4.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
I can't get past updating the radio it hangs and will not continue. Is there any help you can offer me?
Don't necropost... You already posted your problem here: http://forum.xda-developers.com/showthread.php?t=1359940
If you will post your question in whole forum and all topics - i don't want to help you...
I have the HTC MAGIC
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)( OLD )
CPLD-12
RADIO-6.35.08.29 (NEW )
Oct 21 2009,17:27:03
on the recovery, fastboot, but not on the android, HTC logo hangs at MAGIC
Not the brick is it?
rom which have error "main cũ version" or "Partition update fail"
What your version nr?
Code:
fastboot getvar version-main
version-main: 3.04.401.2
machines are now hanging in the HTC MAGIC logo
[1] BOOTLOADER - OK
[2] SPLASH1 - OK
[3] RECOVERY - OK
[4] BOOT - OK
[5] SYSTEM - Fail-PU
[6] USERDATA - OK
Partition update fail!
Update Fail!
help me !!!
You have radio/spl mismatch...
You got to fix that before you can proceed.
Follow my instructions:
Download this to begin with while you READ.
http://rapidshare.com/files/45099641...al_sappimg.zip
IT IS IMPORTANT THAT YOU READ EVERYTHING I WRITE.
The problem is: the device has conflicting spl and radio combo. The spl has an idea of where the radio should be and how big it is ect. When they are not matching the flash of a new radio will most likely fail.
To fix this problem, we need to flash a spl compatible with the 6.35 radio.
Here comes the trick: I have found a special rom, which is part of a 2-part update.
Once the spl is updated and the system restarted, we can now flash any ruu we want using the goldcard.
The steps to follow:
1) Read and understand the above.
2) Rename special_sappimg.zip to sappimg.zip
3) Make sure that you have a working goldcard and flash the sappimg.zip
4) Once the device has rebooted, we need to flash the stock rom and you should almost be there...
Post the progress and we will take it from there.
Hope that you will succeed... :0)
thank you very much, I will try and report back
what is "we need to flash the stock rom and you should almost be there..." ?
Can you give me a rom link fit?
a bit sorry for bad english, I'm a Vietnam
you should probably use this tool next time: forum.xda-developers.com/showthread.php?t=794450
Hi,
I have the same kind of problem.
I have a 32A and I installed the wrong radio/SPL
I have the SPL : 1.33.0013d and the Radio 2.22.27.08.
Can I do this manipulation too ? :
mumilover said:
You have radio/spl mismatch...
You got to fix that before you can proceed.
Follow my instructions:
Download this to begin with while you READ.
IT IS IMPORTANT THAT YOU READ EVERYTHING I WRITE.
The problem is: the device has conflicting spl and radio combo. The spl has an idea of where the radio should be and how big it is ect. When they are not matching the flash of a new radio will most likely fail.
To fix this problem, we need to flash a spl compatible with the 6.35 radio.
Here comes the trick: I have found a special rom, which is part of a 2-part update.
Once the spl is updated and the system restarted, we can now flash any ruu we want using the goldcard.
The steps to follow:
1) Read and understand the above.
2) Rename special_sappimg.zip to sappimg.zip
3) Make sure that you have a working goldcard and flash the sappimg.zip
4) Once the device has rebooted, we need to flash the stock rom and you should almost be there...
Post the progress and we will take it from there.
Hope that you will succeed... :0)
Click to expand...
Click to collapse
For information, my version is 2.16.181.1
Thank you !
7ictor said:
you should probably use this tool next time: forum.xda-developers.com/showthread.php?t=794450
Click to expand...
Click to collapse
Thank !
My phone is the S-ON should not apply the above method
anhvaem_n2s said:
thank you very much, I will try and report back
what is "we need to flash the stock rom and you should almost be there..." ?
Can you give me a rom link fit?
a bit sorry for bad english, I'm a Vietnam
Click to expand...
Click to collapse
Just do the first step and the rest will come... i don't want to overload you with information....
7ictor said:
you should probably use this tool next time: forum.xda-developers.com/showthread.php?t=794450
Click to expand...
Click to collapse
anhvaem_n2s said:
Thank !
My phone is the S-ON should not apply the above method
Click to expand...
Click to collapse
As he states, the tool (which is programmed by me and a newer version is to be found in my signature) is only valid if you have an eng spl or s-off.
The steps i gave is to fix the mismatch which is the primary problem now... all other solutions will be futile until the issue has been dealt with.
As he states, the tool (which is programmed by me and a newer version is to be found in my signature) is only valid if you have an eng spl or s-off.
The steps i gave is to fix the mismatch which is the primary problem now... all other solutions will be futile until the issue has been dealt with.[/QUOTE]
If my machine is the S-ON SHIP I can do approach of you?
sorry i read but not understand much
mumilover said:
You have radio/spl mismatch...
You got to fix that before you can proceed.
Follow my instructions:
Download this to begin with while you READ.
http://rapidshare.com/files/45099641...al_sappimg.zip
IT IS IMPORTANT THAT YOU READ EVERYTHING I WRITE.
The problem is: the device has conflicting spl and radio combo. The spl has an idea of where the radio should be and how big it is ect. When they are not matching the flash of a new radio will most likely fail.
To fix this problem, we need to flash a spl compatible with the 6.35 radio.
Here comes the trick: I have found a special rom, which is part of a 2-part update.
Once the spl is updated and the system restarted, we can now flash any ruu we want using the goldcard.
The steps to follow:
1) Read and understand the above.
2) Rename special_sappimg.zip to sappimg.zip
3) Make sure that you have a working goldcard and flash the sappimg.zip
4) Once the device has rebooted, we need to flash the stock rom and you should almost be there...
Post the progress and we will take it from there.
Hope that you will succeed... :0)
Click to expand...
Click to collapse
Success!
Thank you
Now you help me how to root, I tried z4root, flashrec were unsuccessful,
OK... sense you want root, i can determine that you have a working system...
For root and other stuff, read my guide found in my signature :0)
how to change my machine S-On the way S-OFF
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.76.0013 (SAPP10000)
CPLD-12
RADIO-6.35.08.29
Oct 21 2009,17:27:03
Again.... do you have a working system?
Do you have a custom recovery?