Hello All,
OK so i bought a used HTC MAGIC. When i bought it, it was already rooted, and had the ROGERS HTC ROM. But i wanted to load a different ROM onto the phone and in order to do that i had to unroot the phone and start from scratch to be able to root my phone in one click, as instructed by theunlockr.com
On the same site i found a method to unroot the HTC Magic, the link provided gave me a "sappimg.nbh" that ended up unrooting my phone while flashing the My Touch 3G from T-Mobile onto the phone.
In order to root my phone again i followed the steps on theunlockr.com "How-to root the magic in one click". it said that if your motherboard is 32A download the Amon_RA's "recovery-rav1.2.1h.img". my phone specs are:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006 (SAP50000)
CPLD-12
RADIO-2.22.19.261
BUT after multiple attempts and fails i tried flashing the Amon_RA's "recovery-rav1.2.1g.img", which is designed for 32B motherboards, and it was a success.
BUT once again i tried to load a different ROM and seeing that my motherboard is 32A i tried to load ROMs designed for 32A. It would NOT work, the MY TOUCH 3G screen would pop up and stay there forever.
I then tried to load ROMs designed for 32B motherboard and guess what it worked.
Plus when i load HERO ROM's onto my phone it goes very very slow, and right now i have a cyanogen ROM on the phone and it is working perfectly fine.
SO i hope by now you can understand where the confusion lies...the motherboard is 32A but only ROM's desgined for 32B work on the phone.
I would prefer to start from scratch and put my phone back to the ROGERS ROM, rooted or unrooted doesn't matter. So if anyone can provide me a "sappimg.nbh" for the HTC Magic that will flash the ROGERS ROM to my phone i would greatly appreciate it.
Even when i load ROGERS ROM's onto my phone i still get the MY TOUCH 3G boot image.
Im afraid i might encounter problems later due to all these different ROM flashings, so i would like to start from scratch.
Please help me in this matter either by explaining what is going on with my phone, and/or providing me with the correct files ("sappimg.nbh") to reset my phone back to the ROGERS ROM.
Were you able to figure this out? I have a similar issue.
aziz831 said:
Hello All,
OK so i bought a used HTC MAGIC. When i bought it, it was already rooted, and had the ROGERS HTC ROM. But i wanted to load a different ROM onto the phone and in order to do that i had to unroot the phone and start from scratch to be able to root my phone in one click, as instructed by theunlockr.com
On the same site i found a method to unroot the HTC Magic, the link provided gave me a "sappimg.nbh" that ended up unrooting my phone while flashing the My Touch 3G from T-Mobile onto the phone.
In order to root my phone again i followed the steps on theunlockr.com "How-to root the magic in one click". it said that if your motherboard is 32A download the Amon_RA's "recovery-rav1.2.1h.img". my phone specs are:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006 (SAP50000)
CPLD-12
RADIO-2.22.19.261
BUT after multiple attempts and fails i tried flashing the Amon_RA's "recovery-rav1.2.1g.img", which is designed for 32B motherboards, and it was a success.
BUT once again i tried to load a different ROM and seeing that my motherboard is 32A i tried to load ROMs designed for 32A. It would NOT work, the MY TOUCH 3G screen would pop up and stay there forever.
I then tried to load ROMs designed for 32B motherboard and guess what it worked.
Plus when i load HERO ROM's onto my phone it goes very very slow, and right now i have a cyanogen ROM on the phone and it is working perfectly fine.
SO i hope by now you can understand where the confusion lies...the motherboard is 32A but only ROM's desgined for 32B work on the phone.
I would prefer to start from scratch and put my phone back to the ROGERS ROM, rooted or unrooted doesn't matter. So if anyone can provide me a "sappimg.nbh" for the HTC Magic that will flash the ROGERS ROM to my phone i would greatly appreciate it.
Even when i load ROGERS ROM's onto my phone i still get the MY TOUCH 3G boot image.
Im afraid i might encounter problems later due to all these different ROM flashings, so i would like to start from scratch.
Please help me in this matter either by explaining what is going on with my phone, and/or providing me with the correct files ("sappimg.nbh") to reset my phone back to the ROGERS ROM.
Click to expand...
Click to collapse
when you flashed over the nbh for the mytouch, you basically made your phone a 32B. the radio and spl for a 32B is different than a 32A. That's why only 32B roms work on your phone. To fix this, all you have to do is flash over the 32A radio and spl, then you are good.
This thread will get you back to a 32A setup. All your problems will be fixed from there.
http://forum.xda-developers.com/showthread.php?t=544761
What surprises me is that flashing over the nbh didn't brick your phone because of the different spl's. You lucked out I guess.
That link will get put the 32A radio and recovery on your phone. From there, you should be able to hopefully flash the spl over without any problems. can't guarantee it though since I have never seen a similar situation as yours is.
Fixed: I couldn't flash using adb, but was able to get into fastboot. As a last resort, from fastboot I ran the executable from the HTC website (RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe from http://www.htc.com/ca/support/magic-rogers/downloads).
It reset everything to default, including perfected SPL, but from there it was easy to re-root.
i have the same problem
i have the same problem with u now, please tell me how you fix it, cause i cant update the official RUU with the current condition, it wont recognize the device.
TIA
Let me explain to you the whole story. I obviously know im going to get flamed for this one. I will give you the short short version
I had a rooted MT3G fender with this Rom installed
http:/forum.xda-developers.com/showthread.php?t=669911
It worked all good until i started messing with stuff. I wanted this rom installed
http:/forum.xda-developers.com/showthread.php?t=673394
Since it said 32a and MT3G fender is 32a i assumed that it will install and no problems. So i used the gold card to change radio and spl to the 3.22 series. only to find out that they dont work for my phone. based on this post
"You are now screwed with a downgraded SPL and radio that do not work on this phone YAAAAAAY." -crypysmoker-
[THUNK AND FIXED] Rooting Mytouch Fender LE 32a/ Mytouch 1.2 DONT!!
http:/forum.xda-developers.com/showthread.php?t=622530
So now im thinking great i didnt catch that so let me just move back to where i was before. using the last section of that previous thread to install the stock radio and spl. i have done this already and know it works. so i install the stock radio and spl and the custom recovery. Boot up into recovery and restore nandroid. everything is going ok utill.....it locks up in a boot loop. i then boot back up into recovery and erase data. after that i tryed another nandroid restore and to my wonderful surprise i now lost the ability to mount the sdcard. i restarted and tryed many different cards and all failed. I then boot up into hboot restore with the goldcard and it then locks up at system.
Great now im looking for something to fix this whole mess. after that i try to reinstall the original spl and radio. I then have an error "signature verify failed." Now im thinking WTF!!!!!
I then find a thread about the RUU and how to turn off "S-on" if i install this official HTC app. However come to find out its the asia version. WONDERFUL FOR ME!!! I then found the Official T-mobile MT3G RUU, installed it and now i have a fastboot installed with a memchip with a red circle around it, not the 3 skate droids, and cant boot into HBOOT ,with the volume down button. All that i see is "RUU USB." I have adb but now get the error "remote not allowed." it used to be "signature verify failed." i have no recovery, no HBOOT, just fast boot with RUU USB.
How to i fix this mess up and get back to this?
T-Mobile MyTouch 3g Fender Edition Stock ROM with ROOT!
http:/forum.xda-developers.com/showthread.php?p=5451898&posted=1#post5451898
This is what i have and show
Sapphire pvt 32a ship s-on G
Hboot-1.33.0013 (sapp31000)
cpld-13
radio-2.22.23.02
oct 21 2009,22:33:27
RUU USB
This is definitely a snowball effect right here.
Oh also i cant go and exchange the MT3g fender because im past my 14 days and i already did it on the first day. LOL
I actually am stuck on the same screen with the same phone. I hope someone has been able to get this fixed
Damn, not trying to be mean, but you screwed up a lot.
I have the same version device as you, and I upgraded my radio/SPL. and did a lot of stuff, i semi-bricked it, but i got it working again. I suggest you re-root your whole entire phone. including flashing all the radios, spl,recovery, and etc.
Try following this theunlockr[DOT]com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The problem is that the phone is stuck in a bit of an interesting state. You can't flash from an RUU at this point because the engineering SPL used to root the phone is version 2.53.x, while the RUU's ROM is 2.10.x. You also cannot flash any images to the phone because the SPL is locked (S-ON). So the only way to fix the phone at this point would be to somehow get an HTC-signed 2.53+ ROM for the SAPP31000 (mytouch 3g 1.2/fender) or find a way to unlock the SPL. I had a nice chat with some of the Modaco guys and we went through a lot of options with none of them working. The phone's basically in a bit of a chicken vs. egg state. So personally, I will be building a serial cable to manually unlock the SPL so that I can flash images back on manually.
So, while I wish it was as easy as just re-flashing the phone, you can't do that with a locked SPL and no HBOOT mode available. Onward to a serial/TTL cable advendure!
Once I get the parts in to build it, I'll follow up here with my results
shintokun said:
I suggest you re-root your whole entire phone. including flashing all the radios, spl,recovery, and etc.
Click to expand...
Click to collapse
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!
Hello...
Fairly new here...
Also new to this rooting/rom business...
but, to the point.
I have a Rogers Magic 32A, with the stock Rogers rom.
my fastboot specs are
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76. 0010 (SAPP50000)
CPLD-12
RADIO-6.35.10.18
Jan 14 2010, 00:14:58
I am using the universal androot app, and running ROM Manager.
Whenever I boot into recovery, it either freezes after a few seconds, or resets the phone back to the first splash screen, and continues to work as normal (no bricking or any of that jazz.)
So anyway, my question is...
Does anyone know why it's doing this?
I got it to flash Cyanogenmod 6.0 once, but it didn't actually install.
Do I need a different radio and SPL?
I've tried searching, and I found nothing... but if there is already a thread with this issue, I'll gladly revert to that, and delete this thread.
TL;DR
-Phone is involuntarily restarting when I go into recovery mode
-Running stock Rogers rom, ROM manager, rooted with universal androot app
-New to android customization
-Am I doing anything wrong?
Thanks for reading.
I have the same problem!!
What I can do to fix it?
I'm really scared ...
the problem likely is you are loading the ebi1 recovery (magic 32a running 3.x radio) on you "hero like" magic (magic 32a running 6.x radio)
The hero recovery will work but you may find few roms.
I'd reccomend these rooting instructions
The process will work from the top I believe but since you ran androot after placing the files onto the phone you can skip to where I run exploid (with the seceetlol password) and run 'su' instead of exploid.
Once you have a 3.x radio with working rom and recovery if you want to checkout rom manager you can hopefully with less issues and if an issue happens you can always flash a recovery via fastboot.
I did end up fixing my issue.
Great Big Dog on the androidforums helped me out...
I tried to look for my thread that I posted on the androidforums, but I guess it got deleted...
pretty much... I followed GBD's quick root guide for the post 911 update for rogers magics, with a tiny bit of a switch for flashing the amonRA rom.
I can't remember exactly what it was, and I really wish that thread didn't get deleted.
And I can't link in any posts, so I can't really help you out.
I usually always just suggest installing a fresh RUU, especially if you don't know what you're doing... like me.
you can probably find one on the htc website.
So.. I had CM6.0.0 Stable running on my 32A HTC Magic. All fine and dandy. Then I saw the Smoki ROM and I decided I wanted to flash that, but only one problem. It required a different radio and SPL. So no problem, right? I flashed the required SPL and Radio through fastboot. Looks good right now! Then I turn off the phone and boot into recovery.. but wait.. it just doesn't boot into recovery and just decides to hang at the HTC Magic logo.
I no longer have a ROM installed since I wiped. So I can only go into fastboot. Is there any way I can fix this, or did I just brick the **** out of my phone?
You should be able to still have a Rom running. That happened to me I wiped, I forgot to go into recovery and it loaded the phone and everything was fine
Sent from my PC36100 using XDA App
Try to flash different recovery from the flashboot. It seems that the latest Hero recovery doesn't work with the new radio, get a previous version.
There is a comment in red from Amon_RA:
"Only flash recovery-RA-hero-v1.6.2.img if you have a 32A Sapphire with 6.35.x.x radio and 1.76.x SPL, recovery-RA-hero-v1.7.0.1.img will NOT boot! I'll create a new Sapphire version soon."
Post here ALL fastboot info. ALL.
I see you have posted in different threads but the info you provide contradict each other!!!
Start by doing NOTHING MORE and post here all fastboot info so we can get an overview of what you have been doing.
Also which recovery image you have on and which roms you have used.
DON'T WORRY.. as long you can boot into fastboot you are NOT bricked :0)