Database Users

Need clarifications about radio/SPL/ROMs on 32A

Hi,
I've posted pretty much the same yesterday in the development section in Amon_RA recovery thread, but figured it wasn't the best thing to do, so I'm moving my questions here, where they have probably belonged all along...(and I'll edit my post there)
I'm not exactly noob when it comes to PC, Linux, phones and stuff, but I've been trying to make some sense of this SPL and radio stuff for days for the fear of bricking my phone (it's rather expensive, after all) and the more I read, the more confused I in fact become. It seems to me there's a lot of contradicting info available here in the forums.
First, I've got the 32A european HTC branded Magic:
PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009, 21:02:32
Now, on the thread about Amon_RA recovery, it says in big red letters "Make sure your phone is rooted and that you are using an engineerings SPL". Also, a few pages into the very same thread, there's this:
skittleguy said:
If you can confirm it works through fastboot, then you can also do this:
Code:
fastboot flash recovery recovery-RAv1.1(G or H, depending on your version).img
This will flash it to your phone. Note that you'll need an engineering SPL for this.
Click to expand...
Click to collapse
However, when I rooted my phone a few weeks back, I used Amon_RA recovery 1.2.0 - the latest at the time - without flashing it permanently to make nandroid backup of the unrooted phone and then to apply the necessary patches to root my phone succesfuly. Then I flashed the Amon_RA recovery without any problems directly into the phone and been using it since, even did some nandroid backups and restores without any problems at all. Should this even be possible without the engineering SPL (which I figure I don't have, it being .0009 and S-ON)? If I understood the SPL info correctly, it shouldn't, but I was still able to do it...So how come?
Also, can I perhaps try to flash some custom ROM for 32A without the risk of bricking the device? Am I right in my understanding that pretty much the only way to brick the phone is to start messing with radio and SPL? So is there any risk involved in just downloading a ROM, wiping the phone, flashing the update to see if it works without tampering with radio/SPL?
As for the Hero ROMs, once again, do I need to update radio and/or SPL to make them work or can I just try? And if I DO update them (I gather the .2005 SPL should work in my Magic, not really sure about radios, though) and I want to go back to my original ROM for some reason (given that I have nandroid backup available), will I be required to downgrade radio/SPL back as well (therefore be once again exposed to the risk of bricking the phone)?
Thanks for any clarifications on these. If someone can direct me to some clear info on the issues, I'll gladly take that, but as I've said, most of the informations I've dug out the past few days (and weeks, actually) only deepen my confusion. I'm quite sure my questions have probably been answered a lot of times before, but this forum is so packed with information it's becoming hard to actually find exactly what you're looking for, even if you try to do so. Thanks again.

WTF is an SPL?!

LOL I have this:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
Radio-2.22.19.261
May 27 2009, 19:06:41
Click to expand...
Click to collapse
I think it's a perfected SPL but who knows.. Satan?
I want to update my lame ass SPL to one of these bad boys:
Haykuro's "Death" SPL
OR
Magic SPL HBOOT Collection
From these Awesome Website and Also Awesome, I've narrowed down the steps to Victory!
Here's what my Brain thinks:
1.) Download an SPL (i.e Haykuro's "Death" SPL).
2.) Transfer to SD Card.
3.) Go into Recovery Mode (Amon_Ra-v1.5.2G)
4.) Scroll down to "Flash zip from sdcard".
5.) Flash Haykuro's "Death" SPL.
6.) Reboot system now and wait for it to enter Recovery Mode again.
8.) Check for new SPL, and you're done?
My Q's:
1.) Are my steps horribly wrong and could possibly brick my phone?
2.) No wiping required?
3.) If it gets stuck on Formatting CACHE for a long long long time..what to do?

your rooted
SAPPHIRE PVT 32B SHIP S-ON G
so i doubt you can get to recovery

sitimber said:
your rooted
SAPPHIRE PVT 32B SHIP S-ON G
so i doubt you can get to recovery
Click to expand...
Click to collapse
Yes, I know I'm rooted. I just want to update my spl to the latest. And I can definitely get to recovery mode, was just flashing a couple of roms earlier.
Give me some help, bro!

i am also confused. I have a mytouch 3g with a "perfect" (1.33.0006)SPL... what does that mean? what cant I do with this SPL that I can do with a danger SPL? I already have CM Recovery 1.4 + latest Cyanogen Mod rom...

Man, if you don't know what an SPL is, then you're "so 2000 and late." Haha sorry, I had to man

k but instead of sounding smart cause you know something us people who are late dont... how bout explaining?

kareeem said:
Man, if you don't know what an SPL is, then you're "so 2000 and late." Haha sorry, I had to man
Click to expand...
Click to collapse
Hahahaha and that beat goes zoooom zoooom zooom
kareeem stop making jokes help us out, LOL
What's your current SPL, and how did you install it?

melterx12 said:
k but instead of sounding smart cause you know something us people who are late dont... how bout explaining?
Click to expand...
Click to collapse
I only said that line because it was the only one i could find that fit with the lyrics I don't even have an Android device so there's your answer.

this is so frustrating ive googled this for almost an hour and I still cant find anything that explains exactly what a non perfect SPL does and how to go about flashing it and which one to flash!

melterx12 said:
this is so frustrating ive googled this for almost an hour and I still cant find anything that explains exactly what a non perfect SPL does and how to go about flashing it and which one to flash!
Click to expand...
Click to collapse
Haha yeah same here bro.
Hope someone can enlighten us about how they upgraded their spl.

All I know is that its short for "splash image" and has something to do with the boot up process. My dad is a programer (during a coversation about android and linux) explained the SPL to me during Fourth of July but I was a little too drunk to care and pay attention.

well actually SPL stands for Second Program Loader. That much i know for sure. I also know that its the equivalent of a bootloader. what i DONT know and neither does anyone else by the looks of it (lol), is what the difference is between a perfect SPL and a Danger SPL, and how to go about flashing a danger SPL for mytouch 3g? and which danger SPL is the best?

BoomBoomPOW said:
LOL I have this:
I think it's a perfected SPL but who knows.. Satan?
I want to update my lame ass SPL to one of these bad boys:
Haykuro's "Death" SPL
OR
Magic SPL HBOOT Collection
From these Awesome Website and Also Awesome, I've narrowed down the steps to Victory!
Here's what my Brain thinks:
1.) Download an SPL (i.e Haykuro's "Death" SPL).
2.) Transfer to SD Card.
3.) Go into Recovery Mode (Amon_Ra-v1.5.2G)
4.) Scroll down to "Flash zip from sdcard".
5.) Flash Haykuro's "Death" SPL.
6.) Reboot system now and wait for it to enter Recovery Mode again.
8.) Check for new SPL, and you're done?
My Q's:
1.) Are my steps horribly wrong and could possibly brick my phone?
2.) No wiping required?
3.) If it gets stuck on Formatting CACHE for a long long long time..what to do?
Click to expand...
Click to collapse
Some people can be d!cks in this forum. Your steps are right from all that I know. Changing your SPL is an at your own risk sort of venture, though. Haven't even had the balls to do it myself yet. But, first, do try to use the search function in these forums. Pretty new myself but have good luck finding the resources I need through search. Lastly, here are a couple of links that have helped my in regard to SPL research. The first is more general and worth reading through the comments. The second one specifically relates to you...
http://forum.xda-developers.com/showthread.php?t=548218
http://forum.xda-developers.com/showthread.php?t=570659&highlight=hboot
Good Luck. Hope it helps.

melterx12 said:
this is so frustrating ive googled this for almost an hour and I still cant find anything that explains exactly what a non perfect SPL does
Click to expand...
Click to collapse
your google-fu is weak old man!!
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec01
"Perfect" SPL Revisions (that prevent us hacking)
Currently HBOOT-1.33.0006 and HBOOT-1.33.0010 are the known 'Perfect SPL' revisions on the Sapphire handsets that we know of.
It is not possible to fastboot a ROM using these and you need to wait until someone has hacked it.
Edit (12 Aug 2009) : Now you can! Refer to How-To - Fix that perfected SPL - Root the T-Mobile myTouch 3G
So what is an SPL anyway? What does it do?
The SPL, or Second Program Loader, is essentially the Android bootloader. It's job is more than just loading the Android OS - it also offers several other boot options, including Recovery mode, Fastboot, and HBOOT modes, and ultimately it's the SPL that allows manipulation of the flash nand on your device. Part of the SPL's job is to ensure that the data flashed to the device is correct. Most of the current shipping SPLs (apart from the "Perfect SPL's) let us flash a complete ROM image, but don't let us flash a recovery rom or boot image as it checks the verification signature. Haykuro has modified the SPL's available to remove this check and this is what the Engineering SPL's available offer. As the SPL is so crucial to the handset though, you have to be very careful when flashing it as if it's updated incorrectly then you may be incapable of restoring it without specialised hardware and knowledge. You essentially have a very expensive brick
Click to expand...
Click to collapse

looktall said:
your google-fu is weak old man!!
Click to expand...
Click to collapse
Off topic, but thanks for posting. I wish more people were this patience and helpful. Kudos. Especially on the comedy inoffensive flame.

ive already seen that article, but it still does not explain what i want to know. I already know what an SPL does, but what does a Danger SPL do that my perfect SPL cant. is it worth flashing my SPL? which one should i flash and how? I cant find answers to these questions.

ok ive just foudn a bit of info saying that a danger SPL allows you to flash hero ROMS onto your mytouch.. but WTF??? Ive already flashed 2 different Hero ROMS onto my mytouch with no problems and I have a Perfect SPL. the only reason i didnt keep em was cause the device was slow! So wtf is going on with my phone? what am I missing here rofl

The "Danger" (or "Death") SPL is Haykuro's 1.33.2005 and there is only one. It changed the nand partitions sizes (or sth like that) on the G1 and that was why it is required to run Hero ROMs on it. It's not required to run Hero ROMs on the Magic though. What you're talking about are "Engineering" SPLs and the main difference with stock SPL is that, AFAIK, they bypass security checks to allow the flashing of unsigned update packages. Also, I think only Engineering and non-perfected SPLs allow the use of the fastboot protocol, the possibility to flash recovery images directly and the use of Nandroid to make backups.
To me it's all about unlocking everything but I could have lived with my stock non-perfected SPL as I could already do everything I wanted.
Signature checking is not necessary a bad thing. Perfected SPL is a different story as it really reduces you possibilities but I know there are workarounds.

swissp said:
The "Danger" (or "Death") SPL is Haykuro's 1.33.2005 and there is only one. It changed the nand partitions sizes (or sth like that) on the G1 and that was why it is required to run Hero ROMs on it. It's not required to run Hero ROMs on the Magic though. What you're talking about are "Engineering" SPLs and the main difference with stock SPL is that, AFAIK, they bypass security checks to allow the flashing of unsigned update packages. Also, I think only Engineering and non-perfected SPLs allow the use of the fastboot protocol, the possibility to flash recovery images directly and the use of Nandroid to make backups.
To me it's all about unlocking everything but I could have lived with my stock non-perfected SPL as I could already do everything I wanted.
Signature checking is not necessary a bad thing. Perfected SPL is a different story as it really reduces you possibilities but I know there are workarounds.
Click to expand...
Click to collapse
Very informative. I was able to perform a Nandroid backup successfully while still on the "perfected SPL" so what's up with that? I guest I'll just stick with my perfected stock SPL for now, until I find a really great rom I want to flash but requires a non-perfected/eng spl.

BoomBoomPOW said:
Very informative. I was able to perform a Nandroid backup successfully while still on the "perfected SPL" so what's up with that? I guest I'll just stick with my perfected stock SPL for now, until I find a really great rom I want to flash but requires a non-perfected/eng spl.
Click to expand...
Click to collapse
That's why I said "I think"... fortunately I've never had a perfected SPL and I can only repeat what others have been saying about it. Can you restore the backup too?
As you'd already noticed, information on the subject is quite vague but you are right anyway, the only reason to change SPL should be if the ROM you want to install requires it ;-)

SPL Confusion

I'm a little confused on some of the specifics of SPLs.
When I rooted my MT3G I used the one-click method and didn't have to worry about doing anything with the SPL.
I'd like to try some of the other ROMs out there - but I see that they either require an Engineering SPL or the Death/Danger SPL. I know that the SPL changes the partitions on the internal memory of the phone - but I can't seem to find any info on what those new sizes are.
I've been told that the D/D is an Engineering one - but that I don't need it? So I'm a little on the confused side now.
Can someone help me get some clarity?

Your spl is not a Eng one it's a Perfected spl.
Try using the goldcard method http://forum.xda-developers.com/showthread.php?t=548218

silvertag said:
Your spl is not a Eng one it's a Perfected spl.
Try using the goldcard method http://forum.xda-developers.com/showthread.php?t=548218
Click to expand...
Click to collapse
1.33.0006 is a perfected SPL but as they stated, they're already rooted. Luckily with that SPL you can still use the one-click method. Ignore this post about using the goldcard method.
Eng and Death/Danger SPLs increase your internal ROM, allowing you to flash larger custom ROMs onto your phone. However, you have a MT3G which has much more internal ROM space than the G1, so you DONT need to flash an Eng or Death/Danger SPL. Doing so will only increase you chances of bricking your phone. One bad flash and your screwed. So, if you already have a custom recovery installed, find a custom rom that looks good to you, boot into recovery, perform a full wipe, and flash the rom. However, make sure you pay attention to rom specific installation instructions before you flash it. Some will require that you flash the DRC83_defanged_base.zip before flashing for legal issues, and others, mainly eclair roms, will require you to partition your SD card. Good luck! Also, I recommend using Super D, its a great rom!

Thanks sombionix!
Yeah, I used the one-click method about a week after I got the phone and have been rocking the current CM and A-Ra recovery ever since... this was late 2009.
So...
If something says it needs an Eng/D/D SPL I can ignore that and try flashing anyways? The perfected SPL that you and I have is pretty much an all-purpose SPL (for lack of a better term)? The worst that will happen is that it won't work and I can just restore a BART save of my current working CM?
Damn us geeks for being so fickle.

tsheeley said:
Thanks sombionix!
If something says it needs an Eng/D/D SPL I can ignore that and try flashing anyways?
Click to expand...
Click to collapse
Pretty much. Most of the ROMs I use are for the G1, which has a smaller partition than the default MT3G. The SPL is what changes this, so if the G1 requires a different SPL, chances are it'll still work fine on the MT3G.

Awesome!
Thanks somb & cougar for the help! I'll be doing some happy flashing sometime in the near future.

The G1's original SPL, and the Engineering SPL and Hard SPL, had less onboard space to store ROMs. The Magic has more onboard space, so Haykuro took the Magic's SPL and backported it to the G1.
This was called the Danger SPL or Death SPL as you needed to be running the latest radio for it to work. Many people did not work this out till later and bricked their G1s. Now we know this, so flashing Danger SPL is not really dangerous at all.
Every Magic already has as much space as a G1 with Danger SPL, so Magic users can use any ROM marked "Danger SPL" without concern.

How to switch ENG S-ON to S-OFF?

Hi everyone,
My phone is magic (TIM).After I flashed the new radio(6.35.10.18) and SPL(1.76.2007), I don't know why my ENG S turned ON automatically, and I can't solve it (even if I reflash the SPL in recovery).
Also there is a more serious problem, After I flashed any new ROM such as SuperHero, Eclaire, Villian,Robomix v0.1 and rebooted it, it keeps frozen at the first boot screen(splash screen). At last I tried to use a CM ROM, it can be started finally!
I'm very confused, the CM ROM is Android 1.5, so does it mean that I can only use the ROM with 1.5 for now? Cannot be!^%%$#@@!%$...

You used a CM rom with a 6.35 radio and 1.76 spl? And can't use the roms that require the new radio and spl? I'm pretty sure you DIDNT FLASH the new radio and spl.

Yes, I did! I pressed BACK+POWER to boot into fastboot model, it displays 1.76 and 6.35 with ENG S-ON!

That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl

Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291

KAwAtA said:
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Click to expand...
Click to collapse
er...it's CursorSense32A-1.2.6.1 and recovery 1.6.2(the hero version)

Wow, you're using cursor sense? that would've been nicer to know rather than CyanogenMod
xaueious said:
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
Click to expand...
Click to collapse
I don't get it, how does that help his problem? I know he wants to change to S-OFF but the main problem is his roms don't load up. But like the other guy, I notice that they can only use CursorSense soo im not sure
Show me step by step on how you flashed the ENG 1.76.2007 SPL (although this shouldnt affect it at all)
pyee0124 said:
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.
Click to expand...
Click to collapse
Do you have any swap/ext partitions?

First I flashed Engineering SPL 1.33.2010 in recovery, and reboot into fastboot, I saw I'm ENG S-OFF at that moment, so I flashed new SPL and radio then. Maybe the problem comes with the old incompatible recovery, after I reboot my phone this time, it beame bootlooping(see my thread posted:http://forum.xda-developers.com/showthread.php?t=658220), I was almost thought it was bricked! But luckily the phone fixed itself(I thought), I could enter fastboot, at that time I noticed that my ENG changed S-ON.
That's my whole story, hope it can help you to help me fix the problem.
I have a ext3 partition but in order to protect my TF card I didn't partition a swap

Sorry man, hope someone else can help you. I just dont even understand how you got an S-ON SPL if you followed the thread ppl provided in the other one cause an ENG SPL was provided. Dunno how you got perfect, and I am completely not sure why you can't flash other new radio Roms. Hopefully someone else can help

It doesn't matter bro, I'll find another way to solve it, still thank you!

Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc

xaueious said:
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
Click to expand...
Click to collapse
Um he made an error and he said it was CursorSense, not CM.
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
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
and after reading that thread, I read that you posted this command for sd card problems. Please point out where He is supposed to read, I'm either blind or you're wrong (Seeing as how you missed his CursorSense mistake and stating that the title of the other thread is fastboot oem enableqxdm 0, lol, I don't think I'm blind)
Sorry if I sound like a douchebag here but seriously, you although this guy posted in the wrong section *sigh*, if you wanna be a douche, at least read over his problems properly. You're not helping at all right now and again, he made a mistake about cyanogenmod which was already cleared up and you failed to read that. You should really, get your lazy ass to read this thread more clearly (LOL I don't evne know if that made sense, its 3am and since u live in toronto, oh same time there i assume!) But yeah, if you wanna be a douche, you gotta at least be right or something. But whatever, I just find it totally ridiculous how you're flaming this guy. But if I'm wrong, then go for it and flame me! I haven't seen anything helpful from you here

KAwAtA said:
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
Click to expand...
Click to collapse
I think so too, it's a forum to discuss about technic, not complain.

I have the same situation as you, the ENG SPL changed from S-OFF to S-ON.
Also, can't boot any 2.0/2.1 roms.
I did a lot of flash and try to fix the SPL to S-OFF, but no luck. Such as:
Flash ENG SPL 1.76.2007 again and again;
Flash back to 3.22 radio and 1.33 SPL, then flash the 1.33 ENG SPL;
Flash the device from 3.22 radio and 1.33 SP to 6.35 radio and 1.76 SPL;
A month after, I noticed that my phone can't turn on the Bluetooth. The Bluetooth only can be turned on while first time I boot up the phone, when you disable it and try to enable again, no go...
I send the phone back to HTC for repair, and HTC said that my motherboard was damaged...
I notice more and more people have the same issue as me (and you), I am afraid that some of the 2.1 rom might have some wrong drivers that make my phone go wrong.. (because I didn't flash any rom, I only restart my phone while my phone can't boot and SPL changed to S-ON....)
Be careful everyone, hope my finding is wrong..

I've seen the oem command fix the S-ON to S-OFF before, which is why I posted it. Sd card disabling and s-on happen together in those cases.
Come to think of it, the time I got S-ON too was with battery pull and hard rebooting. Maybe S-ON is activated with memory debugging as a flash corruption protection scheme.
littlestrong try checking the integrity of your file system and reflashing your ROM entirely. Sometimes flash just wears out.
There's also the issue of flashing the radio and spl from recovery, as sometimes it causes issues. The best way is to do it with fastboot. I know your SPL is locked so you can't do that though. Your best bet was the oem command with 1.76 HBOOT versions. Other than that it would be playing with serial cables and JTAG.

So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?

nabor said:
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
Click to expand...
Click to collapse
I've never heard of "oem" commands flashing spl/radio/rec. But you can give the command he gave you a try
The best way would be to use fastboot commands. I don't think a corrupted rom makes it S-ON. I got S-OFF as soon as I flashed my eng spl

O.K. thanks. Got it, seems no solutions yet. I think I should learn the kernel first, it is fundamentally to know how a ROM, a system works!
And sorry for my poor English, I fund I missed a "y" above in "mabe"

can somebody tell me, how in this case I can install a new SPL, or recovery?

Mod. edit: not dev related, moved to general

Seeking advice rooting MyTouch 1.2 (HTC Magic 32a)

Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.

Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App

You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.

NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).

knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.

so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814

lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.

lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18

You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App

knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?

I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App

knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.

If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App

knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.

it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit

NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.

Possibly try to re download the sappimg from the mgic spl thread?

I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...

NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.

NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!