Database Users

[HELP] Hboot becomes S-ON 1.76.2007

Please help!
My magic (32A) suddenly changed its hboot to S-ON!!
Info in fastboot mode:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Now I can't flash anything in fastboot, I have RA recovery v1.5.3.1.
But I can't mount the sdcard for updating the hboot again.
I have goldcard, but usb connection error show up while verifying the phone..
Can anyone has same issue?
Thank you

littlestrong said:
Please help!
My magic (32A) suddenly changed its hboot to S-ON!!
Info in fastboot mode:
SAPPHIRE PVT 32A ENG S-ON H
HBOOT-1.76.2007 (SAPP10000)
CPLD-12
RADIO-6.35.10.18
Now I can't flash anything in fastboot, I have RA recovery v1.5.3.1.
But I can't mount the sdcard for updating the hboot again.
I have goldcard, but usb connection error show up while verifying the phone..
Can anyone has same issue?
Thank you
Click to expand...
Click to collapse
Damn, I hate members like you.
a) You don't even tell us what you did wrong
b) What does this have ANYTHING TO DO TO BELONG IN THE MAGIC DEVELOPMENT?

I am sorry that I did not mention the whole story.
Where should I post this message to? myTouch 3G, Magic General?
I am using "Super-Hero (Build By AhmgskMod)" before came into this situation, I found that the phone can boot, and looping in the htc Magic screen.
Show I tried to wipe and flash the rom again. I flashed the rom for 5-6 times, but it still won't boot..
At the last one I tried to flash another rom from XDA, I found the sdcard can't mount in recovery mode. And I go to fastboot mode, S-ON is observed.
I flash my phone with sappimg.zip in hboot mode (Sdcard file can be loaded). Now I am with the rom in (RUU_Sapphire_HTC_Europe_304401), but the sdcard is not mounted after I boot up my phone.
I believe that this issue is due to the S-ON hboot, I am finding some way to flash the hboot again (I tried -- fastboot NOT OK, recovery can't mount sd)
Seek for help. Thank you very much.

littlestrong said:
I am sorry that I did not mention the whole story.
Where should I post this message to? myTouch 3G, Magic General?
I am using "Super-Hero (Build By AhmgskMod)" before came into this situation, I found that the phone can boot, and looping in the htc Magic screen.
Show I tried to wipe and flash the rom again. I flashed the rom for 5-6 times, but it still won't boot..
At the last one I tried to flash another rom from XDA, I found the sdcard can't mount in recovery mode. And I go to fastboot mode, S-ON is observed.
I flash my phone with sappimg.zip in hboot mode (Sdcard file can be loaded). Now I am with the rom in (RUU_Sapphire_HTC_Europe_304401), but the sdcard is not mounted after I boot up my phone.
I believe that this issue is due to the S-ON hboot, I am finding some way to flash the hboot again (I tried -- fastboot NOT OK, recovery can't mount sd)
Seek for help. Thank you very much.
Click to expand...
Click to collapse
u still hav hero recovery??? ( custom recovery)

Yes, I have the hero recovery (custom), I flash in by boot the hero recovery in fastboot, and flash using:
adb push recovery.img /
adb shell flash_image recovery /recovery.img
The problem is I cannot access to sdcard in recovery mode, also can't use the sdcard when I boot up the phone.
Updated: I copy the rom.zip and rom1.zip from RUU update. The rom.zip container radio and hboot. Should I flash the rom.zip in hboot, to recovery the radio and hboot?

s-on + no sd card.
This problem seems to be experienced by many people in the process of upgrading to the new radio. I have experienced it myself and i never managed to solve it. Luckily i manafed to get a replacement phone. I am still afraid of upgrading the radio on my new device in fact. I think that this seems to be a common problem which deserves to be given more attention by the devs. I. Believe there were a couple of people on the forum who managed to fix it but they are few and far between.

fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.

xaueious, Thank you very much! Now I can access the sdcard! I will try harder to search in forum before asking question next time.
And thank you for the support of everyone in this post too.

This command was not recognized by the phone in my case. It's not always that simple to solve. It would be better to know what causes it in the first place so that people can avoid it.
xaueious said:
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
Click to expand...
Click to collapse

Now I can use the rom in (RUU_Sapphire_HTC_Europe_304401), I use hboot mode and flash the rom1.zip from the captioned rom (renamed to sappimg.zip)
But I can't start any custom rom for new radio from XDA here (installed in recovery mode, update from zip). It just stuck at the htc Magic screen, can't boot into phone.
My SPL/Hboot is still 1.76.2007 S-ON. I have tried flash the "update-hboot-1762007-signed.zip" in recovery mode, but the Hboot is still S-ON.
I believe the problem is due to the S-ON Hboot, so I can't start any custom rom. Any way I can turn the Hboot to S-OFF?
Thank you!

Update to Amon_RA's newest hero recovery. You should be able to mount your SD card in that.

Thank you sindrefyrn. I updated to the latest RA hero recovery.
I can mount sdcard with hero recovery 1.5.3.1 too.
But problem is I can't boot my phone with custom rom, only stock rom will work.
My ENG SPL 1.76.2007 is S-ON instead of S-OFF.
I will tried to flash the RUU update to replace my existing radio and SPL tomorrow, my home PC using win7 and can't verify my phone while RUU update, I will tried it tomorrow in office with winXP.
Hope it works, will report here.

littlestrong said:
Thank you sindrefyrn. I updated to the latest RA hero recovery.
I can mount sdcard with hero recovery 1.5.3.1 too.
But problem is I can't boot my phone with custom rom, only stock rom will work.
My ENG SPL 1.76.2007 is S-ON instead of S-OFF.
I will tried to flash the RUU update to replace my existing radio and SPL tomorrow, my home PC using win7 and can't verify my phone while RUU update, I will tried it tomorrow in office with winXP.
Hope it works, will report here.
Click to expand...
Click to collapse
You can flash a RUU with higher manversion then your previous ROM.

I often find that when I go into recovery my sdcard is not mounted. The solution (for me) is to:
adb shell
mount /sdcard
exit
And that's it.
No idea why the sdcard is mounted sometimes but not other times though

sindrefyrn said:
You can flash a RUU with higher manversion then your previous ROM.
Click to expand...
Click to collapse
Is that mean I can't downgrade my SPL and radio?
I can't use fastboot to flash my SPL and radio, because S-ON SPL not allow me to do so.
Could I copy the rom.zip from RUU which contain SPL and radio, then renamed it to sappimg.zip and flash in Hboot mode?
The only thing I want to do is change my SPL back to S-OFF. What can I do?
Thank you for your help.
update: Is there any SPL.zip I can use to flash my SPL in recovery mode?
update 2: I tried flash the ENG SPL 2007.zip in recovery mode, but it can't change my SPL back to S-OFF. Is it because the SPL are in same version, so, I am not upgrading my SPL by this action?

littlestrong said:
Is that mean I can't downgrade my SPL and radio?
I can't use fastboot to flash my SPL and radio, because S-ON SPL not allow me to do so.
Click to expand...
Click to collapse
No reason you can't downgrade your SPL and radio that way, as long as the mainver of the RUU you're flashing is newer than your current.
Could I copy the rom.zip from RUU which contain SPL and radio, then renamed it to sappimg.zip and flash in Hboot mode?
Click to expand...
Click to collapse
Yes, that's possible. However, the mainver still needs to be higher than your current.
The only thing I want to do is change my SPL back to S-OFF. What can I do?
Click to expand...
Click to collapse
If you haven't yet tried, apply this as normal trough recovery.
update: Is there any SPL.zip I can use to flash my SPL in recovery mode?
Click to expand...
Click to collapse
Yes, see above.

etibon said:
This command was not recognized by the phone in my case. It's not always that simple to solve. It would be better to know what causes it in the first place so that people can avoid it.
Click to expand...
Click to collapse
That only works with the 1.76.xxxx SPL, which he has.
From personal experience, I can tell you that I screwed my phone up by flashing hboot and radio in the wrong order.. Ultimately, it prevented me from flashing the Hero recovery... So basically, I was stuck with new SPL/Radio with Sapphire recovery for a while. But here is where things got worst: I attempted to flash BACK to the OLD SPL/Radio, which worked. However, somewhere along the way enableqxdm(1.76.x only) was turned ON, and stayed on. The only thing I was able to do was go back to the stock Rogers RUU (old radio), but left with no SD card which really sucks. When Sense was released for Rogers, I flashed the new ROM and Radio (via USB) and turned enableqxdm off. All fixed at the cost of being rooted
littlestrong; which ROMs are you trying to flash? There could be a really simple explanation as to why they don't work.
1. Did you WIPE data/dalvik/ext before flashing? <- this is pretty important
2. Flash a ROM specific to the new radio?
And if you're trying to reflash your radio and SPL, what errors do you get?

sindrefyrn:
I have tried update your SPL 1.76.2007 from recovery. It remain S-ON afterward.
So, I downgrade my SPL to 1.76.0007 and raido 6.35.07.xx from HK stock sense rom (Hboot mode -> sappimg.zip). The SPL and radio are successful downgraded. Then, I flash the SPL the 1.76.2007 in recovery. No luck.. SPL has been upgraded to 1.76.2007, but it is still S-ON..
pyee0124:
I flash all roms below with full wipe (all 5 wipes in recovery), they all are for new radio:
--[ROM][32A][6.35] SenseUI 2.1 based on DROID Eris dump. Both v01 and v02.
--Super-Hero (Build By AhmgskMod) [Based On Eris Dump].
--Eclair AME [Android 2.1] MADE BY ME [Only For New Radio] [28th Feb]
I also restore a nandroid backup which it was backup with Eclair AME rom, when my phone in good condition.
All the above roms can't boot up, all stop at htc Magic screen..
I search this forum and found 2 topics about making ENG SPL to S-OFF from S-ON.
1. Flash the nandroid backup boot.img file to the phone, might be one of them will make the SPL to be S-OFF.
2. Remove the battery for a couple of day, and leave the phone as it is .The phone might change to S-OFF itself.
Another problem, I can't flash my magic in RUU. ERROR 170 was found both in XP and win7. I tested it in computer with and without htc sync. I have install proper driver.
I have one more question, I can flash custom rom for new radio here in recovery mode. But all 3 roms I had tried won't boot up and stuck in htc Magic screen. Can anyone flash custom rom with S-ON SPL and found no problem in boot??

You should still be able to flash custom ROMS regardless of S-ON. One of the other things you should try is formatting your SD card again.. Try a full FAT32, then try partitioning afterwards. I found that I could only boot Ahmgsk with FAT32/Swap/Ext2.

pyee0124: I have flashed the [ROM][32A] CursorSense32A-1.2.6.1, it can boot up with my S-ON SPL.
I will test flashing others rom and see if I can use Android 2.1.

[FIXED!] HTC Magic need help! phone bricked?

Hey guys
I'm so desperate and you are my last hope. I was looking for hours in several forums but didn't find any solution.
What I did:
I updated the phone to 6.35 Radio and 1.76.2007 SPL and installed a Eclair ROM. Everything went well until I installed ROM Manager app. Then I installed Cyanogen mod through ROM Manager and since then nothing works!
What's the problem:
When I switch phone on it sticks on the HTC boot screen and nothing happens.
I can go to fastboot mode but ADB doesn't recognize my phone.
I also can go to recovery mode and ADB sees the device but I cannot install any image and I cannot choose any item from the menu.
What I tried:
connect with fastboot usb: phone isn't recognized
flash via fastboot in recovery mode: <waiting for device> no response.
Install a sappimg.nbh from sdcard: Fail! main version is older.
My version:
SAPPHIRE PVT 32A SHIP S-ON G (why G??? isn't that the 32B version?)
HBOOT-1.33.0013 (SAPP10000)
RADIO-6.35.10.18
Thank you very much for your help!

LOL, I almost started cracking up. "Help me, you are my only hope" (Star Wars)
Anyhow.
Start over. Download the stock Rom, radio and spl for your MT3G. I ran into something similar with mine. I had to erase system from the CLI (command line) fastboot and wipe the phone. Then used the stock sappimg.img to get mine functioning again.
This will "Unroot" your phone
I had to plug the phone in via usb. Go to terminal or dos, and fastboot.
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
from there I turned the phone off, and then I copied sappimg.img to the memcard, and then booted using the vol down + power and let it install the factory rom, radio, spl and recovery.
Or you also stated that you have yours rooted. You're going to have to download the original radio, and rename it to radio.img and then flash it over using fastboot. (fastboot flash radio radio.img). This would get you to the original radio. Then I would revert back to the original ROM w/root ROM.
This worked for me. Im hoping that someone else will chime in and say if this is the correct method to use. Im not an expert. I did this at my own risk.
Someone else want to chime in?

Thanks for your help!
I wasn't conscious that I cited a Star Wars quotation :-D
First I tried to follow your steps but without succes. When I run "fastboot erase system -w" it says: remote not allow. It seems my phone isn't rooted anymore.
Also the command "fastboot flash radio radio.img" doesn't work.
Where can I get the stock ROM? Is there a possibility to extract these files from the RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe tool?
Nevertheless I keep going on although I'm a little bit tired of this issue. However, it's my mistake.
The reason why I wanted to flash my device was because I was sick of this old, boring and lame Android 1.5. Why isn't HTC getting ahead and supplies us more up to date software? An ambitious single programmer is able to provide Android 2.1 but HTC with its high-paid engineer team isn't. That's weird!

It looks like you have to put on one of the engineering SPL's first in-order to wipe the device. By the way, mine is a 32A board, and has "G" also. Weird I know.
I believe the RUU ROMS are stock. So flashing these to the phone should unroot your phone. There is a list of all the RUU ROMS and guides here:
http://forum.xda-developers.com/showthread.php?t=659403
or
http://forum.xda-developers.com/showthread.php?t=682243
These are great sources of information. I'm not an absolute expert, more of a novice. I'm new to the AC but, reading guides and such, you should get your answer and you can try a few things (within reason).
BTW, when you said that fastboot flash radio radio.img doesn't work, have you downloaded the stock radio and spl and copied them to the AndroidSDK\Tools folder? That's probably the reason it isn't working. You have to have the SDK downloaded and installed. (Read The Guides provided to help you) "Use the Force!" HAHA!

So I tried many different ways to save my htc. But by now no success!
As I described I can go into fastboot but I cannot run any commands (remote not allow). I haven't root anymore!
When I go to recovery mode it sticks. I cannot choose any item from the menu.
The only way to get the phone working is via the sdcard. It's possible to install a sappimg.zip but it says: "Fail! Main version is older!" So i have no chance to downgrade. I need a sappimg that has a higher version than my current one.
Also rooting seems not to be possible due to I have to access recovery mode (which isn't working).
Finally, the only way I see at the moment is trying some stuff that works only via the sdcard.
Thank you guys

If you are getting that sort of error that indicates that you have not created a correct goldcard. You need to have that in order to flash these devices.
Go to theunlockr.com and read that tutorial about how to create one. Or click here:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/

Are you really sure that`s because of a wrong goldcard? I´ve tried 2 different sdcards several times but every time with the same error (Main version is odler).

No further ideas?
I can't do anything. recovery mode always crashes, no root access, goldcard doesn't work.

Finally I'm back on Android!
I could solve my problem. I found a sappimg.zip (http://rapidshare.com/files/266290371/sappimg.zip) that turned my phone to:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
RADIO-6.35.10.18
After that, I was able to flash trough the _HTC Magic_RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_CH_release_signed_NoDriver.exe.
Now I'm running on a stock ROM

madboy87 said:
Finally I'm back on Android!
I could solve my problem. I found a sappimg.zip (http://rapidshare.com/files/266290371/sappimg.zip) that turned my phone to:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
RADIO-6.35.10.18
After that, I was able to flash trough the _HTC Magic_RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_CH_release_signed_NoDriver.exe.
Now I'm running on a stock ROM
Click to expand...
Click to collapse
Good to hear.
I'll take the liberty of modifying the title of your original post and close this if you will no longer be needing any assistance. Should you or anyone else decide to need it re-opened, just send me a pm. Thanks!

Ok... kinda stuck in vodafone limbo [myTouch 3g w/ headphone jack]

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

1.76.0010 S-ON boot and 3.22.20.17 Fastboot working stuck in Ruu usb scr

My device is a HTC MAGIC 32A, the phone cid is HTC__038
Hey I had flashed Rogers RUU 2.1 update over a rom with old radio and old spl
The update failed and I had to take out the battery
Now my phone only opens in the ruu white screen where its written SAPPHIRE 32A SHIP S-ON
HBOOT- 1.76.0010 s-on H
CPLD-12
RADIO-3.22.20.17
Jan 14 2010,00:14:58
And there is a chip with a cross at the bottom
I have fastboot acces but have tried almost all the known commands but to no avail
TRIED FASTBOOT FLASH RECOVERY XXXX... but gives signature fail
fastboot flash zip rom.zip gives main version older in case of official roms and signature error even in extracted roms
fastboot boot recovery xxxx... nothing happens just after the cmd shows booting
tried fastboot erase recovery/system /booot all of them give remote not allow
I have tried to run other official ruu(all of these found here forum.xda-developers.com/showthread.php?t=659403 ) with goldcard butr all of them give error 140 bootloader version error and show main version older on phone screen
I have tried to run the official rogers 2.1 ruu again but it gives error 132- signature error
When running ruu the current device image shows version 3.54.631.7
Tried everything in this thread http://forum.xda-developers.com/showthread.php?t=793704&page=5
and this one
http://forum.xda-developers.com/showthread.php?t=824633
PLEASE HELP ME!!
Either a signed rom(hex edited) with image version greater than 3.54 or a way to get adb working or turn s-on to s-off through fastboot would do the trick

Or simply if somebody could tell me how to revive a phone with S-ON with rom version 3.54 using FASTBOOT Thanks

If you are getting an error main version older with goldcard, then it is not a goldcard. If you can get another goldcard, or still have the numbers to get another goldcard image and remake your goldcard it will work. I have been in the same position and remade the goldcard and it worked. I don't know why or if it happens all the time or with just certain brands, the goldcard no longer works after using it. I don't have a Kiingston only a Samsung microSD and have had to remake it twice. I would get the remote:not allow when trying to flash or boot recovery from fastboot, but when I remade my goldcard it worked.

housry23 said:
If you are getting an error main version older with goldcard, then it is not a goldcard. If you can get another goldcard, or still have the numbers to get another goldcard image and remake your goldcard it will work. I have been in the same position and remade the goldcard and it worked. I don't know why or if it happens all the time or with just certain brands, the goldcard no longer works after using it. I don't have a Kiingston only a Samsung microSD and have had to remake it twice. I would get the remote:not allow when trying to flash or boot recovery from fastboot, but when I remade my goldcard it worked.
Click to expand...
Click to collapse
Hey I dont have a spare phone to check the above, but with the current goldcard I have I am able to pass the CID check with any rom(otherwise get cust id error) but am not able to get past the Main version check so will making a goldcard again help

hEY MY CURRENT ROM VERSION IS 3.54 AND THE OTHER RUU'S AVAILABLE HAVE MAX UPTO 3.05 AND I AM UNABLE TO DOWNGRADE EVEN WITH A PROPER GOLD CARD. PLEASE HELP!!

i have same problem, did you fixed?

primux said:
i have same problem, did you fixed?
Click to expand...
Click to collapse
Almost, got access to adb with su priveleges but by mistake flashed wrong flash_image file and ruined it, now my phone is lying with HTC care who are thieves and say the "Phone is EXITING while we are trying to update your software" then they call me and say that that they will have to change my motherboard despite my hardware being completely fine(I think they have taken out all my original parts and initially say my warranty has expired, then do something that makes my phone not even boot and then say i have warranty, just hope they give back my phone soon ) ..
My advice would be to try the below else perform JTAG as HTC care are greedy, unprofessional, illiterate cheats.
Type fastboot oem boot or fastboot boot oem while in fastboot and your phone will boot and keep restarting every 2 min
Good Luck

i see, can you tell me how you got adb access? i just have RUU MODE and when i tried to upload a new flash stuck in SYSTEM - unzipping, my phone it's same version as yours. i'll appreciate any help

[help needed]HTC magic PVT 32A: wrong radio (3.22.XX) and SPL (1.76.0008)

The whole story is a little bit long.
I still can access to fastboot. On the RUU screen, I can read the following information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
Here is how it happened. I flashed the radio to 3.22 and run a wrong RUU file (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe). The problem comes: after unsuccessfully flash the RUU file (as the radio in the RUU is 6.35), the security is turned ON (S-ON). Those RUU files with radio 3.22.XX have different version of SPL from 1.76.XXX. I cannot find a RUU file with SPL 1.76.008 and radio 3.22.XX. Therefore, I cannot use any RUU file to change the situation (I got a goldcard).
The security is turned on and I cannot change the radio, SPL or recovery in fastboot (cannot pass the infoSignature checking).
Now I still can access to fastboot (such as fastboot devices).
I don't know why I cannot use fastboot to boot a recovery (fastboot boot recovery-RA-sapphire-v1.7.0H.img). I was able to send the recovery img to the device. But the booting of recovery takes for ever.
I can only enter fastboot mode now using any combination of buttons.
Please give your comment and help to solve this.
Thank you very much!

htchd2sg said:
The whole story is a little bit long.
I still can access to fastboot. On the RUU screen, I can read the following information:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0008(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Nov 3 2009, 15:56:29
Here is how it happened. I flashed the radio to 3.22 and run a wrong RUU file (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver.exe). The problem comes: after unsuccessfully flash the RUU file (as the radio in the RUU is 6.35), the security is turned ON (S-ON). Those RUU files with radio 3.22.XX have different version of SPL from 1.76.XXX. I cannot find a RUU file with SPL 1.76.008 and radio 3.22.XX. Therefore, I cannot use any RUU file to change the situation (I got a goldcard).
The security is turned on and I cannot change the radio, SPL or recovery in fastboot (cannot pass the infoSignature checking).
Now I still can access to fastboot (such as fastboot devices).
I don't know why I cannot use fastboot to boot a recovery (fastboot boot recovery-RA-sapphire-v1.7.0H.img). I was able to send the recovery img to the device. But the booting of recovery takes for ever.
I can only enter fastboot mode now using any combination of buttons.
Please give your comment and help to solve this.
Thank you very much!
Click to expand...
Click to collapse
Many of this was answered, search the forum.
Here is the thing you have wrong spl radio combination,you have perfected spl. You can do a fastboot boot xxxxxx.img and enter recovery. Then you must flash eng spl 1.33.2010.And you will be unbricked

Thank you for the reply.
I tried fastboot recovery-RA-sapphire-v1.7.0H.img. But after the sending of the image is over, it will stay in booting for ever. I don't understand why I cannot boot the recovery.

htchd2sg said:
Thank you for the reply.
I tried fastboot recovery-RA-sapphire-v1.7.0H.img. But after the sending of the image is over, it will stay in booting for ever. I don't understand why I cannot boot the recovery.
Click to expand...
Click to collapse
You cant boot that recovery try the one hero recovery Ra-magic1.6.2H smthing recovery

I downloaded the 1.6.2 recovery from http://forum.xda-developers.com/showpost.php?p=4549551&postcount=1
But I still cannot boot the recovery(I can send the recovery)

htchd2sg said:
I downloaded the 1.6.2 recovery from http://forum.xda-developers.com/showpost.php?p=4549551&postcount=1
But I still cannot boot the recovery(I can send the recovery)
Click to expand...
Click to collapse
Hmm did you try the sappimg.nbh to restore your magic???

Updated: I tried to use sappimg.nbh in fastboot mode. However, it responses that the main version is older. This is because I have run the RUU (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_No Driver.exe), whose main version is 3.05 while the sappimg.nbh is older than this number.
Now I can access fastboot and the hboot, but not the recovery. Of course, I cannot boot the android OS either. Is there a method to root just in the fastboot mode? I have the security turned on (S-ON)?
Anyone got suggestion? Thanks!

Can anyone help on this? really get frustrated

htchd2sg said:
Updated: I tried to use sappimg.nbh in fastboot mode. However, it responses that the main version is older. This is because I have run the RUU (RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_No Driver.exe), whose main version is 3.05 while the sappimg.nbh is older than this number.
Now I can access fastboot and the hboot, but not the recovery. Of course, I cannot boot the android OS either. Is there a method to root just in the fastboot mode? I have the security turned on (S-ON)?
Anyone got suggestion? Thanks!
Click to expand...
Click to collapse
You need to create a goldcard www.theunlockr.com at How to's and then use sappimg.nbh

I got gold card already. . Thank you!

Do you solve this? I got the exactly problem with you =(

I actually had this same issue months ago and nothing worked. Unfortunately I ended up getting another phone.
Sent from my SGH-T959 using XDA App

r3v4N said:
I actually had this same issue months ago and nothing worked. Unfortunately I ended up getting another phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
What a bad news =( I had sent this phone to repair, but all of their experts cannot fix as well.

That's lame.... did you try the unroot process?
Sent from my SGH-T959 using XDA App

You could try unbricking by flashing the Rogers or Brazilian Android 2.1 RUU. The main version is newer and a goldcard should make it work.
Please make sure your battery is full and that you have a PROPER GOLDCARD!!! Otherwise this will most likely fail.
I've uploaded the sappimg to http://www.multiupload.com/WO0S35S53S
Rename it to sappimg.zip, copy it to the root of your SD card and boot into fastboot (vol-down and power). That SHOULD fix your phone. Then again, it could also brick it even worse, but what do you have left to lose?

After loaded sappimg, it checking sappimg, then went back to HBOOT. Nothing happened. I've tried to recreate my gold card, no luck with it =(