Database Users

Trouble getting 32B roms on my MT3G

I rooted my MT3G early on using the goldcard method - it is currently running the RAv1.1.0h rom from the original rooting thread. It has the 1.33.2005 SPL and the 3.22.20.17 radio. In fastboot I can see that it the SPL is an HTC version (I think that is what PVT 32B ENG S-OFF H means, right?).
I'm having trouble moving to a 32B rom, and no matter what I try, I can't get the damn recovery image to switch from the current RAv1.2.1H to the G - which is (I assume) why I can't install any 32B roms.
Any foolproof way to change my recovery image from H to G? I've followed all the steps listed on how to do this in Fastboot and using ADB to switch it over, but no matter what I do, it has no problems booting correctly with an H recovery image, but not with a G.
Any 32B roms just makes the phone hang at the splashscreen, so I know it's a rom issue.
OR - Am I missing a step here - is there a different spl I need in order to get my MyTouch 3G to think it is a G edition again. OR easier yet, should I stop whining and just find a reliable 32A rom that works on it (assuming something without too much HERO stuff?).
YES - I searched everywhere, I spent countless hours on it, but I can't help feel I've missed something really stupid, so feel free to call me names and point out the obvious (just don't say "try Google).

Are you still able to use flashrec? If yes try to flash this one>> cm-recovery-1.4 works fine if you want 32B roms. Enom uploaded latest version yesterday.
http://forum.xda-developers.com/showthread.php?t=549754 nd if you want version prior to this then go to http://www.4shared.com/file/129108782/3953f016/HTC__crc1__Android_rooted_Rom_32B_TMobile.html
unzip and make sure to install one after the other. Large one first and rename as update ,put in your sd card. Once that is performed then go to the next small one about 14mb. Rename as update and put it in sdcard. Dont forget to delete the large one if already there.
Let us know how you go on.

No - Flashrec won't run since the rom I'm currently using has the exploit patched.
Good tip though, thanks! Any other thoughts on why I can't get the 1.2.1G recovery image on my phone? Or an alternative way to get it to install?
EDIT: Took a few steps back, installed the sappimg for the MT3G, then did flashrec and then did the update with the rom you posted. Thanks so much for the tip and inspiration!

Yes, well done.Thanks for letting us know.And yes flashrec wont work on these rom also. I tried many times to flash with RAv 1.2.1image but it seems it was not possible. I asked emon in his T Mobile rom thread where he gave me a tip as to how to go about RAv.... but that hasnt worked.
But there is a solution if al you want is to make 3 partitions.
I followed Paaragon method as described on http://forum.xda-developers.com/showthread.php?t=512873
and it worked. So try that.
I tried many different roms and finally settled on enomther's
because it is very fast, not too cluttered and just perfect for 32B boards. And further more, there isnt anything that doesnt function.
PS: I prefered the one prior to current as on 4shared. But thats personal.

unroot completly by re insttalling the saphimg and go with the oneclick root method from the unlocker thats what i did and TITS! perfict running hero and full 32 b envierment raido and roms ... be carefull with the 32 a 32 b mixup could be the end of your touch....

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 ;-)

Downgrading from DangerSPL?

Now that Firerat has figured out how to easily fit stuff on G1 and T-mobile MT3G phones without DangerSPL, I'm thinking of downgrading to the base engineering SPL. I have a few questions though, since I don't feel like bricking my phone.
First off, fastboot info:
SAPPHIRE PVT 32B
HBOOT - 1.33.2005 (Danger, I believe)
Radio - 2.22.23.02
First off, where would I find a non-danger engineering SPL? Are the SPL's in this thread the ones I should be looking for? http://forum.xda-developers.com/showthread.php?t=529019
Also, are there any benefits of sticking with Danger SPL (other than extra 30 megs system) and since it's now easier to fit this stuff on non Danger, will there be more benefits in reverting back to the original Engineer SPL?
In addition, if I DO decide to flash back to a non-danger SPL, would I have to use recovery or fastboot? I'm assuming they'd be a match, but I'd like to do whichever way is more safe.
Edit: Oh crap, just noticed I posted this in the wrong section. I own a MT3G, but I installed danger way back when they first rooted it when following a tutorial. Should I be looking at a different engineering spl?
Sorry for all of the stupid questions.

DangerSPL is not required for the MT3G in the first place, so I'm not sure why you installed it in the first place.
From what I know, there is no downside to being on Danger, so I don see why downgrading to an engineering spl is necessary
If you do decide to do it, do it through recovery not fastboot

PurpleFries said:
DangerSPL is not required for the MT3G in the first place, so I'm not sure why you installed it in the first place.
From what I know, there is no downside to being on Danger, so I don see why downgrading to an engineering spl is necessary
If you do decide to do it, do it through recovery not fastboot
Click to expand...
Click to collapse
You got it the wrong way bud.
Read the Brick confirmation thread by lbcoder.
flashing radios and recoveries (incompatible ones) through recovery is how bricks happen.

cal3thousand said:
You got it the wrong way bud.
Read the Brick confirmation thread by lbcoder.
flashing radios and recoveries (incompatible ones) through recovery is how bricks happen.
Click to expand...
Click to collapse
Probably, but I've never had a bad experience flashing an SPL through recovery. Never once used fastboot. I very rarely actually can. Also, you run the risk of a brick ANY TIME you flash one. As for OP, just flash a new Engineering SPL. There's no real brick with those. I mean, yes you CAN, but just make sure it's not corrupted when you download it new SPL. Check MD5 Sum. There's no radio-spl brick with those. (As far as I know.) And, yes, those are the SPLs you want if you have a myTouch.

PurpleFries said:
DangerSPL is not required for the MT3G in the first place, so I'm not sure why you installed it in the first place.
Click to expand...
Click to collapse
I don't know. I followed the tutorial word by word when it was first figured out how to root the MT3G. I literally had that handset for a week before anyone had done anything with it.
Thanks for the responses.
Edit: Bit the bullet and did it. No problems. Made sure to check the MD5 every time I moved the file, used fastboot. Couldn't have been easier and everything is working perfectly.

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!

A little help would be great.

So my wife just upgraded her phone and i was left with a stock MyTouch 3g with 3.5mm headphone jack and I thought I would expand my Android knowledge base and see what I could do with it. I am not knew to Android and I have a Samsung Vibrant that I can pretty much do whatever I want with. The Galaxy line is extremely easy compared to this device.
So I did my fair share or reading and research and was able to root the phone with Universal Androot and installed busybox via titanium backup. I downloaded ROM manager from the market and flashed clockwork recovery. I used recovery to installl CM 5.0.8 DS and once it reboots in wont load past the mytouch splash.
This is what I started with:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013
CPLD-13
RADIO-2.22.23.02
Oct 21 2009, 22:33:27
And this is what it reads now:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Jun 2 2009, 17:27:03
I read that Binary said that it is really a 32B not an A so to stick with the B ROMs. I can also access fastboot and recovery.
The easy part with the Vibrant is that if I screw up the phone you can just simply Odin back to stock and start over, but the mytouch is a little more complex than that. So basically I want to get back to stock and start over. There are so many threads and links that say user friendly but I didn't find it quite user friendly. I must just be spoiled with the Galaxy.
Any help would be greatly appreciated. It's not a rush or it's not my daily driver. Just a toy phone now to learn on.
Thanks!

mod edit because of inaccurate information.

So you are saying if I just follow the normal root guide for the fender 1.2 that I should be good?
Sent from my GT-I9000 using XDA App

CBATESY said:
usually any of the 3.5mm jack phones are 32a devices. 32b is the original mt3g. ones with the jack in the top is a mt3g 1.2 or 32a. If you have recovery working you can use that to restore back to factory or installed sapping.img
here something to help you out .
http://wiki.cyanogenmod.com/index.php?title=HTC_Magic
Click to expand...
Click to collapse
NO! Damn it! Listen to me everybody! The 1.2 device (Fender, etc) are a 32A/32B hybrid. The ONLY thing that makes this phone ANY different than the regular 23B MyTouch devices is the additional ram. That's it! You CANNOT fit a 32A ROM on the device because it lacks the internal storage. Even if you COULD the kernel for that rom would require a 32A radio. You cannot use a 32A radio because the 1.33.0013 32A s-ON spl requires the 32B radio. And it requires a 32B radio else it will brick. The 1.33.0013 is the S-ON stock SPL that the phone requires to use the memory map. If you try the Engineering SPL (1.33.2010 32B S-ON) the phone might boot, but you will not have touch screen or the use of the headphone jack because of the different drivers and memory map. When you flash the Engineering SPL it will read 32B because that is what is needed to flash the custom recovery and roms. However your device will not work properly because it's a 32A/32B hybrid. You need the 32A stock firmware (1.33.0013 S-ON) for the phone to operate. You also need the appropriate 32B radio and rom as well.
I have the phone and I've had it since it's release. I started off by making custom roms for it and ports before roms were using VoxLuna's driver patch. Trust me when I say that I know a little about this damn phone!
You know what... to hell with it. Do whatever you want. Don't be sending me private messages begging for help when you brick your device because you think it's a 32A.
custom ported rom #1
custom ported rom #2
custom ported rom #3
custom rom #1
They all require 1.33.0013 S-ON with 32B radio.

offdutyninja808 said:
SAPPHIRE UNKNOWN 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
Click to expand...
Click to collapse
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.

Binary100100 said:
NO! Damn it! Listen to me everybody! The 1.2 device (Fender, etc) are a 32A/32B hybrid. The ONLY thing that makes this phone ANY different than the regular 23B MyTouch devices is the additional ram. That's it! You CANNOT fit a 32A ROM on the device because it lacks the internal storage. Even if you COULD the kernel for that rom would require a 32A radio. You cannot use a 32A radio because the 1.33.0013 32A s-ON spl requires the 32B radio. And it requires a 32B radio else it will brick. The 1.33.0013 is the S-ON stock SPL that the phone requires to use the memory map. If you try the Engineering SPL (1.33.2010 32B S-ON) the phone might boot, but you will not have touch screen or the use of the headphone jack because of the different drivers and memory map. When you flash the Engineering SPL it will read 32B because that is what is needed to flash the custom recovery and roms. However your device will not work properly because it's a 32A/32B hybrid. You need the 32A stock firmware (1.33.0013 S-ON) for the phone to operate. You also need the appropriate 32B radio and rom as well.
I have the phone and I've had it since it's release. I started off by making custom roms for it and ports before roms were using VoxLuna's driver patch. Trust me when I say that I know a little about this damn phone!
You know what... to hell with it. Do whatever you want. Don't be sending me private messages begging for help when you brick your device because you think it's a 32A.
Click to expand...
Click to collapse
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.

DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Exactly, all he needs is a custom G recovery (which he should have) and then flash the 1.33.0013 stock spl BACK on. Afterwards, he can flash any 32B rom he wants and it should work as long as it's later than CM-4.2.15.

DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Thank you for the non-violent approach. I know how it is when you have a new guy just blowing his phone up and he goes screaming for help. Not what I was trying to do. Just tinkering with a new device to get some more know-how under the belt.
Much appreciated, Don!
I will let you know what I can get accomplished with your advice.

offdutyninja808 said:
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
Click to expand...
Click to collapse
He wasn't fussing at you, he was getting at the other guy for feeding you false information.
Sent from my HTC Magic using Tapatalk

My apologies, Binary. Following forums over time you tend to see so much hostility over pretty much nothing. It's a learning experience. Just as I had to learn my other phone, some things the hard way, I will be able to steer people in the right direction and help others after I get this one down.

offdutyninja808 said:
And I thought the Vibrant forums were hostile. I am glad that you have had your phone for so long and I am quite sure you know what you are talking about. Like I stated, this phone is just sitting around the house collecting dust and thought I would mess with it. If I brick it... great. If I make it the fastest MyTouch it can be... great.
Don't get me wrong, I appreciate what you and all the other developers and contributors do for random users like myself, but give a guy a break. You have to admit that this phone is a little dated and it's like knowing how to run Windows Vista and 7 then going back to do the same things on a Commadore.
Click to expand...
Click to collapse
I'm not trying to be hostile but all of the information is available here in the forums. The developers, senior members and moderators like myself have spent HUNDREDS OF HOURS making sure it can be referenced one way or another. They are in stickies and even in MY SIGNATURE. The only other thing we can do for you is do it ourselves! Yet even with a clean and clear explaination this still comes up. We even get some people that post threads saying that they bricked their phones because they thought for sure it was a 32A and they try to hold me responsible. I will be happy to forward some hateful e-mails to you that I get at least 2 or 3 times a week average because people couldn't find the information... yet... if they followed rule #1 of the forums... they wouldn't have the problem.
Look... at least you got the right information and avoided bricking your phone. But I really hate repeating myself over and over again with the same information so I need to be tougher to get my point across otherwise other members will likely use the wrong information and end up breaking their phones... which I will not be held liable for!

DonJuan692006 said:
He wasn't fussing at you, he was getting at the other guy for feeding you false information.
Sent from my HTC Magic using Tapatalk
Click to expand...
Click to collapse
Right on Don. I'm not angry at you OffDutyNinja808 however the other guy (CBATESY) should be warned that I could give him an infraction for giving out bad information.

Binary100100 said:
Right on Don. I'm not angry at you OffDutyNinja808 however the other guy (CBATESY) should be warned that I could give him an infraction for giving out bad information.
Click to expand...
Click to collapse
On another note, Don, I made a new sticky thread just for this issue.
Feel free to add your wisdom to it.
http://forum.xda-developers.com/showthread.php?t=893004

Okay... so I followed Don's instructions and the phone now says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23. 02
I tried flashing the same CM and it gets past the mytouch splash but doesn't go past the next loading X screen.
From what you guys said everything is looking right. Any thing look out of ordinary or sound crazy from what i'm saying?
Thanks again!
Sent from my GT-I9000 using XDA App

offdutyninja808 said:
Okay... so I followed Don's instructions and the phone now says:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23. 02
I tried flashing the same CM and it gets past the mytouch splash but doesn't go past the next loading X screen.
From what you guys said everything is looking right. Any thing look out of ordinary or sound crazy from what i'm saying?
Thanks again!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Loading X screen?
What rom are you trying to install?
What kernel?

And now i'm in like tube socks! I just woke up and tried it again and it booted right up.
Binary, it was the same CM 5.0.8-DS. As far as the kernel goes, I didn't flash any separate. The X boot screen I mentioned is the Nexus One load screen (I believe).
The only thing that I did differently this morning was wipe/factory reset, then davlik.
Okay... so from my understanding now:
I have to have a perfected SPL, not an engineering SPL.
I have to use the custom (AMAN RA) recovery and never use ClockworkMod.
Ensure that any other roms I want are 32b.
Now as far as the radio goes, is it best to stay with the radio it came with?
Again, thanks for the advice!
Sent from my GT-I9000 using XDA App

DonJuan692006 said:
The problem. You forgot to mention that you also flashed a non-perfected SPL at some point before flashing CM 5.0.8. You need to get that fixed. Luckily you can fix it without a goldcard since you've already got S-OFF.
Download these:
hboot.nb0 for myTouch 1.2 only
Amon Ra 1.7.0-G Recovery
Go to this URL and follow the steps to get ADB setup if you don't already have it. Then go here and follow steps 7, 8, and 9. In step 7, you should only need to run:
fastboot flash hboot hboot.nb0 (the 0 at the end of this line is a zero not an oh).
fastboot flash recovery recovery.img
fastboot reboot-bootloader
After that just reflash CM 5.0.8, although I'm using CM 6.1 and it's just as good, but with the perks of Android 2.2. I would suggest reading through that thread I linked to get more familiarity.
Lastly, I will warn you that this isn't the easiest way to get your phone fixed, but this is the way that I learned about my phone, so it should help you out in that aspect. I'm sure mumilover or someone else may come along with a simpler solution.
If you have any problems, let us know here.
Click to expand...
Click to collapse
Don, two things...
1. I searched through the ROM bible and didn't find any place to download 6.1.
2. When I try to download the Google Apps from the page you sent me the link to yesterday, it asks for a user name and password. I have 5.0.8 up and running, but with no market and things like that.
Thanks!

Okay... I am now running FroyoRedux-1.9.5 with the Galaxy theme. Everything is smooth as butter.

I fixed the links in the post I pointed you to and updated them to what you news for CM 6.1
Sent from my HTC Magic using Tapatalk

offdutyninja808 said:
And now i'm in like tube socks! I just woke up and tried it again and it booted right up.
Binary, it was the same CM 5.0.8-DS. As far as the kernel goes, I didn't flash any separate. The X boot screen I mentioned is the Nexus One load screen (I believe).
The only thing that I did differently this morning was wipe/factory reset, then davlik.
Okay... so from my understanding now:
I have to use the custom (AMAN RA) recovery and never use ClockworkMod.
Now as far as the radio goes, is it best to stay with the radio it came with?
Again, thanks for the advice!
Click to expand...
Click to collapse
You can use clockwork. I use it without any problems. Some people like AmonRa better though. If you run CM6 there have been issues about people not being able to flash the recovery for some reason. Just keep trying and it will stick eventually. Just make sure that you flash the one for MyTouch/Ion devices.
Radio - keep the one that your using.
Roms - 32B ONLY