Related
Hi, I've recently bought a HTC Magic and since then I've been reading into how to root my phone. Before I start I would like to know if it's possible on my phone.
Details:
HTC Magic Vodafone Uk (32B)
Hboot: 1.33.0007
Firmware version: 1.5
Build: CRC24
I've read from a thread in another section of this forum
that it would be impossible because of 1.33.0007 being a perfect spl BUT my phone is running the firmware version 1.5, with a CRC24 build. Would this mean I will be able to root my phone or not?
Also I've been reading up on how you either have cupcake or donut. My version is 1.5 so would that mean I have cupcake?
I'm worried that I might brick my phone so would prefer to use the one click tutorial at theunlockr (would add link but I can't) which is for htc magic running on cupcake.
Would it work?
Sorry for all my questions and I probably will end up asking more
Thanks if anyone can answer these for me!
You should be able to root using the relentless rooter or by following the guide on the unlockr. You are lucky you are running cupcake and don't need to downgrade
I think you are only really at risk when you flash radio and spl. Using the unlockr's stuff shouldn't be too bad. But read eveerything a bajillion times incase
same boat
Hey bunnybag
Was in the same boat as you until yesterday.
Also had a perfect SPL (0010) on a 32A.
I was also reading up a lot wrt getting a new ROM on my phone, and was also afraid of bricking it...
The gold-card method seemed quite involved, and that QMAT application doesn't exist anymore, and the newer version of it, does not run in XP or Vista...
Yesterday, I used the one click method from theunlockr, and after a few mistakes, it worked! Now I have a shiny CyanogenMod running with a 1.6 donut
It seems with the one click method -that you do not need to change the radio or SPL (which I guess are the most dangerous flashes to attempt)
Quicky summary of what I did, and where I deviated:
1) Read the one click method from theunlocker, and some of the comments at the bottom. Also - very importantly - watch the YouTube video at the top of the one click method page a few times!!
2) Downloaded the FlashRec apk (follow link on the one click method's page)
3) Installed FlashRec (the latest version of FlashRec looks slightly different to the one in the YouTube video but functions the same)
4) Did a backup of the existing recovery image via FlashRec. After the backup, you can copy the backed up .img to your PC...
5) Copied the latest Amon RA recovery image (v1.5.2) onto the SD card. Make sure you get the right one... there is a different one for 32A/32B... [Deviation from the one click method- which uses an older version of the RA recovery image]
6) Attempted to flash the new RA recovery via FlashRec. Here is where I struck a problem - the thing just stalled - for a good 10mins - and said 'do not interrupt' :|
I hooked up the USB cable, and from the command prompt ran: adb catlog
From here, scrolling up, I could see that FlashRec gave some message of invalid recovery image... Bit of a bummer - I checked the CRCs of the recovery image after copying it to the SD, and also tripple-checked the filename I typed into FlashRec! In the one click method page, they also warn about inadvertently adding spaces to the end of the filename when you type it in. I also checked for that.
I attempted it once more as follows:
-Rebooted phone
-Deleted the RA recovery .img from the SD
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
-Flash succeeded! maybe FlashRec can't handle very long file names?
7) After the recovery was flashed, I booted into recovery mode (HOME & POWER). Seems like the Amon RA recovery image takes slightly longer to boot that the stock recovery... so - don't crap yourself if it takes a few seconds. This is also a good point to stop, and watch the second video from theunclockr on how to load a new ROM...
8) After verifying that the new recovery image was working I booted back into Android, and I copied my ROM's files onto the SD. I used the Cyanogen Mod. The Cyanogen wiki has a page on how to load it for a 32A and also 32B.
Basically, you need the latest stable cyanogen mod, an Android 1.6 "defanged" ROM (link available on the Cyanogen wiki), and a new kernel. The kernel is 32A/32B specific, so get the right one.
9) With the 3 files on the SD, I booted back into the new RA recovery I just flashed.
10) Did a Nandroid backup
11) Did a wipe/factory reset [Deviation from theunlockr method: I did not format my SD card, or partition it into Ext & Swap. I prefer not to have a Swap partition on the SD, nor do I think I'll need to swap any apps out to the SD card... I think the 32A has enough space... you can read further about it in the xda-developers wiki, under page: HTC_Sapphire_Hacking_2]
12) Still in RA recovery, I applied (in order) a) the defanged 1.6 ROM, b) the Cyanogen mod, c) the new 32A kernel
13) Flashing it takes a while - there is a progress bar...
14) Reboot after all 3 were flashed. The first reboot takes a looong time... couple of minutes... don't worry, or try to reboot again... just give it time.
15) Once inside - tested everything: GPS, Wifi, Phone, Market, G-sensor, Gtalk, Gmail.
16) It might be worth while to note that once the phone is booted, and you've entered your SIM PIN, and the Android desktop is displayed, it can still take a few seconds - 4 or 5 I guess, before you are able to interact (swipe desktop left/right). Give it time to settle down, and all is well
//TODO: still need to flash a new splash-image...
Good luck - post back here with your results!
How to root Magic (32A) with Europe ROM ROM Version:3.05.401.3 with Sense?
Have somebody any idea, how to root Magic (32A) with Europe ROM Version:3.05.401.3 with Sense? Thanks!
bogo_mips said:
Hey bunnybag
-Re-copied it onto the SD, and this time renamed it to something easy: ra.img
-Checked the CRC
-Ran FlashRec, and specified the path as: sdcard/ra.img
Good luck - post back here with your results!
Click to expand...
Click to collapse
Ah, I tried using the unlockr's method and failed at flashrec. The unlockr kept saying that the reason was because I was already on Donuts but that is not true. I ended up using the relentless rooter software (looking back, his method is basically an automation of the original method).
Maybe you should post this also in the unlockr so that people who have "backup failed" messages know what to do?
Thanks for the info. It will be very helpful for other members trying to use the unlockr method.
Thanks for the post guys.
@bogo_mips: Great advice and I'll more than likely use this along with the unlockr one click tutorial.
Oh and there's one thing I'm worried about. My phone has somehow automatically downloaded the 1.6 upgrade and it keeps asking me to install it. Anyone know of a way to delete it so that it won't upgrade?
I'm worried that it might install if I turn my phone off.
@bunnybag: that 1.6 download sounds like a problem... if it takes, you'll no longer be able to do to the one-click method...
Check around the forum for advice. I'd guess - since the download would have had to happen in user-space, that the downloaded file might be sitting on the SD card or possibly the phone's flash. Get that Linda Filemanager app from the market and poke around... I guess if you could find the file, and delete / rename it - you could avert an install?
Alternativley, I'm guessing that if you can attempt the one-click method, that you'll have a new recovery image before you power down your phone, so - I think that will keep you safe...
@visitador02: according to the FlashRec page, there are 1.5 cupcakes out there which have been patched, so - FlashRec can't work on them... maybe that is what happened to you...
Hey guys, I have spent the last 8 hours trying to figure this out.
I have a MyTouch 3g 1.2 and I want to root it and install Cyanogen's new ROM. I have been following the rooting guide from TheUnlckr.com.
I am able to complete everything fine (I needed to substitute the sappimg for the Sapphire one to make it work), but it finally completed.
When I go to fastboot with SDK, I can see my device, so everything looks fine. However, when I go to flash the radio, hboot, and recovery images, I get a error that says:
Code:
C:\AndroidSDK\tools>fastboot flash radio radio.img
sending 'radio' <21504 KB>...FAILED <remote: not allow>
finished. total time: 0.016s
This is the pattern for each of the files I try to flash...
This is where I'm at, and I haven't even gotten to flashing the ROM yet. So, I currently just have a stock device. Can someone please help me out?
I tried using the following sappimg:
2.53.707.2_-_sappimg
SAPPIMG_Sapphire_T-Mobile_US_2.10.531.4_release_signed
the following SPL:
update.Engineering-SPL-HBOOT-1.33.2010-signed
the following recovery images:
recovery-RA-sapphire-v1.6.2G.img
flashrec-1.1.2-20090909.apk
flashrec-1.1.3-20091107-2
flashrec-20090815
I'm clearly all over the place now. Someone please point me in the right direction. I tried several different ways to fix it, but none of them worked. The most reason I tried was the method of using the flashrec to flash a recovery image while the phone is on, instead of fastbooting it. That didn't work because it kept saying it was the wrong image for the phone.
Thanks in advance guys. And believe me, I've been searching and searching.
Dane
before you can flash anything with fastboot, you have to shoehorn that engineering SPL into the phone somehow (probably have to make a goldcard, but I don't know for sure on the 1.2 mytouch)
which rooting guide are you using? (there are many different ones on unlockr, some of which are terribly obsolete)
also, flashrec isn't a recovery image, its a one-click rooting app that only works on android 1.5 (pretty sure the 1.2 mytouch only runs 1.6)
adavis159 said:
before you can flash anything with fastboot, you have to shoehorn that engineering SPL into the phone somehow (probably have to make a goldcard, but I don't know for sure on the 1.2 mytouch)
which rooting guide are you using? (there are many different ones on unlockr, some of which are terribly obsolete)
also, flashrec isn't a recovery image, its a one-click rooting app that only works on android 1.5 (pretty sure the 1.2 mytouch only runs 1.6)
Click to expand...
Click to collapse
This was the guide I was using. (I can't link to outside sites, so I'll just copy it as text) http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
I also successfully created a goldcard, and installed all the ADB stuff. The part that's hanging me up is the flashing of the recovery image via fastboot usb.
I'm so close! I have successfully rooted two other mytouch devices, but they were not the 1.2 version.
Any more help would be great!
Dane
danegerous said:
I am able to complete everything fine (I needed to substitute the sappimg for the Sapphire one to make it work), but it finally completed.
Click to expand...
Click to collapse
what "sapphire" image did you substitute? and what happened when you tried to use the sappimg that they gave you in the instructions?
When I tried using that image, it just said "wrong file for this phone" or something like that. I know the goldcard was done right, though, because it works with another sappimg. I'm trying to follow cryptsmoker's guide now. I'm going to try and use the engineering img/SPL now. We'll see how it goes.
Ok, now I'm getting frustrated.
Here is my info:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
I just got the Model ID incorrect!
Update Fail!
This happens with every sappimg I use except T-Mobile 2.10.531.4. I'm sure that's the stock one, so that's probably why. I'm just so ticked.
To clarify again, After I hboot the sappimg, I reboot and instead of being taken to the Magic screen, I'm taken to a standard MyTouch splash, then Android splash, then MyTouch setup screen. My touchscreen works the entire time. Is this because I basically just reinstalled the stock ROM?
I just can't seem to get ANY other sappimg to work beside the stock one. I've used three different goldcards and all of them work the exact same way.
Please help!
Dane
yeah, you are just reinstalling the stock files (stock SPL and radio)
just because the t-mobile sappimg works doesn't mean you made the goldcard right.
the point of the goldcard is to trick the phone into installing a non-stock sappimg, you could take a brand new SD card, put the stock sappimg on it and you would still be able to flash it using vol-down+power
open the goldcard.img in HxD and make sure it contains all the lines (including all of line 170), if it doesn't then you need to start over from the beginning (get cid again, reverse it again, get a new goldcard.img)
If goldcard.img is ok, open the sd card in HxD again and make sure all of the first 170 lines of the sd card match the goldcard.img
also, some SD cards just don't work for making goldcards. I used a lexar 1gb, and kingston 2gb cards are reported to work
I didn't paste over the entire 170 line while making the goldcard. I used the "select" feature and chose 0-170...that could be my mistake. Here we go again!
I actually never got this to work the first time. I was really excited since I heard I would be getting the T-Mobile update soon, but then I read a little further and saw that the 2.1 is not yet included...so, I will be figuring this out today, mark my words!
Wish me luck!
Dane
I had a similar problem and it was the goldcard. Although I had made the goldcard and it worked before, using the same goldcard I get the same error message as you. I made a new goldcard and it worked flawlessly to flash using fastboot. Make sure you are using one of the brands that are know to work.
OK, new problem now. I installed everything and got it all to work. I actually had the stock cm rom working (an out of date version from the unlockr). Well, I tried to update and I started by flashing the 6.35.16.19 radio. Apparently that worked but now nothing else will.
In the HBOOT screen, I see this:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-6.35.16.19
Oct 21 2009,
Every time I try and update the Sappimg file, I get stuck at the updating phase of the radio_v2 portion. Please help guys, I don't know enough about this to figure it out and it's really killing me!
I figure I need to get back to the stock radio I started with (3.22 or whatever), but I can't. Even when I try to flash the radio in fastboot, it takes way too long and never finishes.
Your speedy replies are greatly appreciated.
Thanks
Dane
Got your pm.
Facts: STOP MESSING UP YOUR DEVICE.....
You are working in the blind... mixing bad spl and radio combos.....
So STOP what you doing and read and understand before you continue.
You can't just take any sappimg.zip and apply it... I has complete partitions layout... like the spl, radio, recovery ect...
So if you take whatever you find on the net and apply it, you will **** your device up... just like you did now...
Having the 6.35 radio and a perfected 1.33 spl... Just bad for business!
What is your current status:
Access to adb?
Access to fastboot?
Access to recovery?
Access to rom/system?
Also post fastboot info...
Then we can take it from there :0)
And for gods sake... STOP flashing stuff.
I have access to adb, fastboot, and hboot. No ROM/system or recovery.
Clarification: Since I cannot access the system of the phone, I do NOT have access to ADB. I cannot see the device when I type in 'adb devices' within the AndroidSDK\tools path.
Fastboot info:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
Aug 21 2009
The radio used is: Radio_HTC_PVT_32A_6.35.10.18.img
the hboot: hboot-1.76.2007.nb0
the recovery: recovery-RA-hero-v1.6.2.img
I have since tried to go into one of your other threads and at least match up my SPL/Radio combo. Any and all help is greatly appreciated.
OK.... you are now in a god situation...
You have a good combo and eng spl...
We can work with this....
1) boot into fastboot
2)download the fastboot commander (magic).... check my signature
3)start the tool... does it print the device info?
If yes, do this:
Go to the magic 32A tab.
Push "flash old".
IF all successful, then go to "misc" tab and push "reboot device".
When device has rebooted, push "print device info".
Now copy all text and posted here...
IF you get ANY errors... DO NOT REBOOT, DO NOT CLOSE THE TOOL...
Just take the output + the content of the "actual tab" and post here....
Again, IF you get ANY errors... DO NOT REBOOT, DO NOT CLOSE THE TOOL!
If the tool does not print the device info, then post here...
mumilover said:
ok... don't do **** until i post back here... give me like 15 min.
Click to expand...
Click to collapse
I'm seriously just sitting here waiting. Thanks a ton. I'll buy you a beer.
just updated my last post
look up :0)
Now i'm the one waiting :0)
Sorry, my battery died, I'm running around to trying to piece everything together. Here I go...
Just do what i wrote.... Read, understand, read, understand, execute.
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!
Does your new MyTouch have a 3.5 mm headphone jack?
Are you confused on wether it's a 32A or a 32B?
Do you need to know how to root it?
Do you need to know how to flash a custom recovery and which one?
Do you have the right radio?
Are you afraid that you might brick your phone?
THEN THIS IS THE THREAD FOR YOU!!!
HURRY!!! HURRY!!! HURRY!!!
For a limited time only! Get your questions answered without having to post a new thread!*
Good while supplies last!
*XDA-Developers and it's members are not held responsible for any damages and encourages all readers (members and non-members) to read thoroughly before attempting any modification of any device. Proceed with caution and at your own risk.
More information
crypysmoker said:
Universal Androot confirmed working. This method is no longer needed and is to dangourous for some people so please use universal androot 1.5.3+
IF READ CORRECTLY YOU WILL NOT BRICK. BUT, Since a few of you dont have that ability, I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR PHONE. There are no pros to rooting this phone yet, leave it alone if you dont know what your doing PLEASE. I beg you. You are in essence almost bricking your phone in order to root it in the first place. These arent fun and games, It is dangerous to rush this stuff
Listen.. Im more then happy to help people. BUt I fully understand why so many devs have left this place. Some of you are so utterly ridiculous with your questions, wanting someone to hold your hand. I cant sit on gtalk for hours helping you go through what should take 10 min , I have a life and kids and other things to do. I did this because I was bored and wanted to see if I could. There is not point in rooting it yet, there are no roms, nor will there be for at least a month. Please, if you cant even understand simple questions, have never rooted or even used an android phone before, please.. do not bother me. This place is insane with stupidity. I will change the tutorial in a little more detail later, but fo rnow, DO NOT DO THIS IF YOU DONT KNOW WHAT YORU DOING. IF YOUR BREAK YOUR CRAP< I DONT CARE, BECAUSE IT WASNT MY FAULT.
I am in no way an angry or mean person, but you people have given me a migraine. I see why all the rom devs hide from here so much
THERE IS NO POINT IN ROOTING THIS PHONE YET PEOPLE, SO STOP.. OMG PLEASE STOP LOL
IT HAS BEEN DONE!!! lol
After 3 days, sleepless night and 5 min from returning the phone, Together with the Awesome Cursordroid We have achieved full root of the fender mytouch/ Mytouch 1.2 revision.
Now.. Understand.. not many will have the fender Mytouch.. but this is the hardware they WILL be using in the fully confirmed Mytouch 1.2
If you do not follow my instructions fully, NOTHING WILL WORK.
Start by making a working gold card, pay VERY CLOSE attention to what the instructions for making a gold card say
http://theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/
READ READ READ. DO NOT download the SAPPimg.zip file it says on that page.
Get the top fixed SPL file 2010 from here
http://forum.xda-developers.com/showpost.php?p=4332591&postcount=1
Once you have you working goldcard (remember, apply to PHYSICAL not LOGICAL) rename the fixed SPL/rom you just downloaded to SAPPIMG.img
Put that file on your gold card
Hold volume down while hitting power
You will boot into Hboot, and if goldcard was made correcly and file is in root, it will begin to read. MAke sure battery is full or chargeing. follow on screen directions for flashing. Reboot into Hboot.
You are now screwed with a downgraded SPL and radio that do not work on this phone YAAAAAAY.
Now grab the stock radio and SPL from Cursordroid here http://forum.xda-developers.com/showthread.php?p=5451898&posted=1#post5451898
From there on follow hiw directions for reupdating your radio and spl, plus give yourself a new recovery making ROOT.
Im not good at tutorials or typing on a tiny netbook keyboard so please forgive. Anyquestions please ask and I will go into more detail
In order
Goldcard
Amen ras fixed spl rom renamed SAPPIMG.img
Boot into Hboot volume down/power
let rom install saying yes to what it says. If it works..
Now boot into your recovery through fastboot
Flash phone with stock fender rom
reboot into fastboot
back out of update when it asks and flash STOCK radio and SPL back, now reboot
your splash screen for fender IS GONE, get over it. You can make a new one later if you realllly need to.
Click to expand...
Click to collapse
Yet, even more information.
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Fender/1.2
Installing CyanogenMod on the 32A (myTouch 3G 1.2 / Fender LE (3.5mm jack) version) requires an additional step whereby a "gold card" is created as part of the installation process.
The process of upgrading from a stock ROM is fairly simple, following the instructions below.
Click to expand...
Click to collapse
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced your phone with your Google account, your contacts, calendar, Gmail, and some Google data will not be lost and will come back after the next sync; However, you should backup anything you want to keep that is not stored on your SD card.
SMS/MMS messages
Call Log
Bookmarks
Applications; use Titanium Backup or the Astro file manager, for example
Any application data not on the SD card
It would also be a good idea to back up everything stored on your SD card in the rare case the card must be formatted to resolve any major problems.
Click to expand...
Click to collapse
Before you begin
What You'll Need:
1.Your myTouch 3G 1.2 or Fender LE.
2.Mini USB cable.
3.microSD to SD adapter for your computer.
Prep
1.Get the latest Amon_Ra recovery
Make sure you chose the G version
2.Create a "Gold Card". It is recommended (but not necessary) to use a spare microSD card.
3.Back up all your microSD card contents to your computer.
Creating the Gold Card
Create a Goldcard
Click to expand...
Click to collapse
Rooting
Downgrading
1.Download the sapping.zip file from here: Link Mirror 2.Place the zip file on your newly created Gold Card. If it isn't already, shut the phone off and place the microSD card back into the phone.
3.Then turn the phone back on by holding down Volume Down and Power. It should boot into bootloader mode and automatically find the sappimg file and ask you to push the trackball (action) to begin the update. Push the trackball and let it update.
4.Once it finishes flashing, it should ask you to reboot. Reboot and let it load to the new "htc Magic" boot screen.
5.Chances are at this point that the phone will not successfully boot. THIS IS NORMAL. Simply remove and re-insert the battery, as we're not done yet!
6.Download the following zip file (the stock myTouch SPL and Radio) and extract it: [1]
7.Copy the two files inside the zip to the root of your SD Card
8.Take the latest Amon_RA recovery you downloaded earlier and copy it to the root of your SD Card.
9.Download terminal emulator from the market and run the following commands:
flash_image flash radio /sdcard/radio.img
flash_image flash hboot /sdcard/hboot_7201A_1.33.0013G_091021.nb0
flash_image flash recovery /sdcard/recovery-RA-sapphire-v1.7.0G-cyan.img
WARNING: Do NOT upgrade the SPL (hboot) with anything other than the 1.33.0013G version! Otherwise, You will lose audio to your earpeice.
1.Press MENU to power down the phone.
2.Reboot holding down the Power and Home buttons until the recovery menu appears.
Click to expand...
Click to collapse
Easiest method!
Easiest method!
candymanmike said:
This is a guide on how to root your phone and install a custom ROM using Universal AndRoot. It supports several phone models and is the simplest way to root a phone I have ever seen. It features a 1 click root and a 1 click unroot option. Rooting with this method does NOT affect your bootloader, therefore if your phone needs serviced you can (theoretically, I have not verified this to be true) simply unroot and restore to normal.
As always myself, XDA, ROM developers, your friends, your mom, the rulers of the world and the developers of this app are NOT responsible for any bricks YOU create by taking the risk of rooting your phone. Also there are no guarantees that your warranty will not be null and void. If you NEED your warranty, DO NOT root your phone. Use at your own risk!
First we will gather the items needed to complete this process.
Universal AndRoot Version 1.6.1 is the newest STABLE release. The newest version is 1.6.2 beta 5, which is where the updated list above comes from and is said to be very close to the final release version.
Next go to the Android Market and install AppInstaller (there are a few versions including appsInstaller by modmymobile, all are free)
While in the market, also grab ROM Manager (also free)
Next download the ROM you would like to use. I personally recommend CyanogenMod 6.0.0 DS - stable. This link will take you to the Cyanogen downloads section where you will have to select your phone and search for the ROM you want.
While you are there, also grab the Google Addon pack for your phone.
Of course it is up to you to choose a ROM you like. You can also keep your stock ROM if you choose.
Lets Begin!
Install the Universal AndRoot .apk file, the ROM you chose and the Google Addon to the root of your microSD card
Open AppInstaller and let it locate your AndRoot .apk on your microSD. Select it and install it to your phone.
Open Universal AndRoot from you app menu. It should read your phone and show your firmware version. Click the "Root" button and let it do it's thing. It really only takes a minute or 2. When finished it will let you know. Congratulations, at this point you are now rooted.
Now for a custom ROM!
Open ROM Manager. Install Recovery. The default recovery for ROM Manager is ClockworkMod Recovery (which is what I am using) but a lot of people seem to like RA Recovery. This option is at the bottom of ROM Manager under "Flash Alternate Recovery". Whichever you choose, let the Recovery flash.
Next choose "Backup Current ROM", then "Reboot Into Recovery" (for future reference, you can also get into recovery mode by turning your phone off, then hold down the "home" button hit the power button. continue hold home as it powers on.)
Chose "wipe data/factory reset" then "wipe cache partition". This step is important. I know from personal experience if you don't do this you may end up in a bootscreen loop!
Choose "install zip from sdcard". Navigate to the ROM you loaded on your microSD and flash it.
After the phone reboots (which can take a few minutes the first time after flashing a new firmware version) go back to ROM Manager and again choose "Reboot Into Recovery". Once in recovery, again choose "install zip from sdcard". Navigate to the Google Addon pack on your microSD and install it.
Once you are rooted and running your new ROM, go into ROM Manager and partition your sd card. This is optional.
That is it. You should be good to go! Way easier and faster than the old goldcard method!
This is my first XDA guide. I hope it is up to your standards!
Click to expand...
Click to collapse
Will all 32a/nr roms work on the 1.2?
Sent from my HTC Magic using XDA App
soub31 said:
Will all 32a/nr roms work on the 1.2?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
NO! 32A roms WILL NOT WORK!!!!
As Amon Ra put it:
"The following instructions :
will void all warranties of your phone!
will erase all your userdata!
will change your current ROM/SPL!
will change your current splash screen!
could brick your phone!
Proceed at your own risk!"
So I've taken the guide that I used to root my myTouch 1.2 with T-Mobile, updated some of the information, and added some explanations. All thanks is owed to The Unlockr for the guide, I'm merely going to attempt to explain what your actually doing in the process and just try make the whole ordeal easier. If I would have known what i was actually doing, it would have taken me 45 minutes to root my phone, vice the good 7-8 hours I put into it. I am by no means an expert on rooting, so feel free to critique what I put in here, and I'll make adjustments as needed.
What's unique about the myTouch 1.2 and the Fender edition is that both phone's have a "perfected" SPL, that does not allow for fastboot access via USB. This means that you can't push any command prompt commands to the phone from your computer, which is what you have to do to get the phone rooted. With these instructions, you'll flash a "non-perfected" SPL onto your phone, load up a custom recovery (which is how you will load up ROM's and do a few other things in the future), and then reflash the phones original "perfected" SPL. Without the original SPL, your phone will not function correctly.
I would suggest opening all the links before continuing so you won't have to wait for the downloads to start as your going. Make sure you remember which link is which tab!!!
From The Unlockr:
I. Setup ABD/Create a Goldcard
Follow this procedure completely to create a working goldcard, then return to this procedure and continue:
How to Create a Goldcard
Follow these instructions without fail. If anything get's messed up here then you won't be able to flash a new SPL and you'll have to attempt to remake the Goldcard again. If you attempt to load the sappimg without using the Goldcard or without a properly done Goldcard, you will get either "Incorrect model ID" or "Main Version is Older". The Goldcard basically tricks the phone into not checking these two parameters, which is what let's you get the "unperfected" SPL on to your phone. ADB is the program that allows you to have a command prompt interface from your computer to your phone.
Note for Windows Vista and Windows 7 users: When your setting up your phones drivers during the ADB setup process, be sure to allow Windows Update to check for drivers. It will allow your computer to automatically install the drivers vice having to manually install them yourself. The option to turn it on should come up when Windows gives the notification that it was unable to install drivers for your device
II. Flash the Sappimg file
1. Download the Sappimg File and save it to your newly created goldcard (NOT in any folders, just on the Goldcard itself).
sappimg.zip
2. Once the sappimg.zip file is on your goldcard, turn off the phone and put your Goldcard SD into your phone. Then turn it back on by holding down Volume Down and Power. It should boot into bootloader mode and automatically find the sappimg file and ask you to push the trackball to begin the update. Push the trackball and let it update.
*If it tells you Error – Wrong Model ID or anything similar, the goldcard was not created correctly, go back to that procedure and try again.
Here your loading an Engineering SPL, so that we'll be able to get access to the phone via Fastboot USB and load up your new recovery. Be patient once you turn your phone back on, as it will unzip the file, then check the contents. If you get an error, you've got a problem with your Goldcard and need to redo it.
3. Once it finishes flashing press the "Send" button to reboot and you will notice your touchscreen does not work (don’t panic). Turn off the phone, then turn it back on by holding down Back and Power (to get into fastboot mode).
4. Download these two files and save them into C:\AndroidSDK\Tools folder you setup during the ADB setup procedure:
Stock MyTouch SPL
and Radio
5. Then download the Custom Recovery Image and save it to the C:\AndroidSDK\Tools folder you setup during the ADB setup procedure as well:
Amon Ra’s Recovery
6. Now that you have the recovery, spl and radio all saved in the tools folder of the Android SDK (same folder as the adb program), plug in your phone (while in fastboot mode from step 3).
7. Open the command prompt on your computer and type the following with hitting enter at the end of each line:
cd\
cd AndroidSDK\tools
fastboot devices
A serial number should come up, indicating that your computer can see the phone in fastboot mode. If so continue by typing in the following with hitting enter at the end of each line:
fastboot flash radio radio.img
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
8. Once the phone starts to turn back on begin holding home and power (do not let go until you see the recovery mode) to boot into recovery mode.
This could take a while. I believe the first time I tried to get in I had to hold them down for ~1 minute before getting in. You should see the HTC Magic splash screen pop up first. There is a guide to changing out the splash screen (which is just a picture) within these forums but I'll leave it to you guys to search for it.
9. You should end up in Amon Ra’s recovery mode.
10. At this point, you want to plug your ORIGINAL SD card into your computer and copy the "DCIM" and "Music" folders (if you have them) over to your computer to backup your pictures/video/music. Then take the Goldcard out of your phone and put your ORIGINAL SD back in.
11. With your phone connected via USB to your computer and in Amon Ra's Recovery, highlight USB MS and press the trackball. This should mount your SD card to your computer so that you can move files to it.
12. Download these three .zip files:
Cyanogen 6.1
Google Apps
614 MHz OC/UV Kernel
You need the OC kernel because there's a known issue with CM 6.1 having a green tint without flashing a new kernel.
13. Copy those three files over to your phone's SD within Windows, "Safely remove hardware" in Windows, then disable USB MS by pressing the Home button. Back out to the main screen.
14. In the recovery select "Wipe" and you want to wipe "data/factory reset" then "Davik-cache".
15. Back out to the main menu and select "Flash zip from sdcard". First you want to select " update-cm-6.1.0-DS-signed.zip" and hit Home to confirm. Once complete, select "Flash zip from sdcard" and this time select "gapps-mdpi-tiny-20101020-signed.zip" and hit Home to confirm. Once complete, one again select "Flash zip from sdcard" and this time select "oc614-cm-2.6.34.1-6.0.0rc2-signed.zip" and hit Home to confirm.
16. Back at the main screen select "Reboot system now". This will load your phone back up as normal and you should now have a working rooted phone with the Cyanogen 6.1 ROM! Jump in there and check it out.
If you want to try out a different ROM, check this thread out. Go to the section called "MT3G 1.2 / LE Fender".
Credit to DonJuan692006 for this.
Thanks to Amon Ra for his recovery images!
Thanks to Unlockr for the original How To!
Thanks to the Cyanogen team for an awesome ROM!
LINK Resources:
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
http://forum.xda-developers.com/showthread.php?t=530492
http://forum.xda-developers.com/showthread.php?t=529019
wouldn't it better to recommend to use Pershoots OC/UV/XTRA kernel? It does OC to 614, is more current than Dumfuq 2.6.34.1 kernel.... honestly been pretty stable.
the previous builds of 2.6.35.9 and lower did not have the 3.5mm audio support.. but it was re-added in the 2.6.35.10. It also resolved the green tint issue of CM6.1-DS
NetrixTardis said:
wouldn't it better to recommend to use Pershoots OC/UV/XTRA kernel? It does OC to 614, is more current than Dumfuq 2.6.34.1 kernel.... honestly been pretty stable.
the previous builds of 2.6.35.9 and lower did not have the 3.5mm audio support.. but it was re-added in the 2.6.35.10. It also resolved the green tint issue of CM6.1-DS
Click to expand...
Click to collapse
Yeah I use pershoots myself from the rom manager.
Another OP made the thread actually and sent me the HTML via e-mail.
614 isn't stable for me though.
My Thoughts and Things to Know
READ ME BEFORE DOING ANYTHING TO YOUR PHONE OR STARTING A NEW THREAD!!!!!
The myTouch 1.2/Fender is a rather unique device. If you boot into fastboot you will notice that the following information is displayed:
Code:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
Let's break that down a little bit.
You see in the first line 32A...but this is very misleading. The myTouch 1.2 is actually a 32B device, just with 32A memory and controller, but it IS a 32B device for pretty much all intents and purposes.
Secondly, you'll notice S-ON. This means that remote security from the bootloader is enable. What does that mean for the user??? Simple, you'll never be able to run a remote fastboot command.
Second line, 1.33.0013. This is your SPL and the ONLY SPL that will allow the phone to function properly. This, as well as the radio, will always need to be the stock versions or you'll either brick your phone or never get a ROM to work.
Also to note, this is considered a perfected SPL. What does "perfected" mean? Remember the "S-ON"?? That is what makes it perfected.
Lastly, the radio, 2.22.23.02. There is actually now a newer radio, 2.22.28.25 available, however, I personally have noted no real performance gain/loss. Again, along with the SPL, you will never want to change this unless you absolutely know what your doing or an expert tells you to.
Now, on to the good stuff.
How do I root my phone???
The first few posts of this thread are the various methods to go about rooting the myTouch 1.2/Fender. The easiest and least dangerous method would be to use one of the one-click root programs such as Universal Androot or SuperOneClick. These methods will give your phone permanent root permissions (permanent until you do a factory reset or receive certain OTA updates later on down the road). The big deal here is that with root permissions you are able to download a nice little application from the Market called ROM Manager that allows you to flash a custom recovery onto your phone. The custom recovery is the bread and butter of modifying your phone. It allows you to flash custom ROM's, flash new kernel's for overclocking, etc.
What radio should I use?/What's the best SPL?
Simply put, don't mess with your radio or your SPL ever except for under very specific circumstances. Those circumstances being, your rooting your phone using the goldcard method or you need an engineering SPL to be able to run a command from fastboot. Even in either of those cases, this should be done very carefully and you will always need to revert back to the original SPL/radio. If you ever need to run something from fastboot and are thinking about flashing an
engineering SPL to do so, make sure you ask an expert first before proceeding. The number one reason for people bricking their phone is because they have taken it upon themselves to try flashing random file they've found via Google.
What ROM's can I use?
This is an easy one. Pretty much any ROM made for 32B phones that does not require a specific radio. I haven't personally tried this out, but I've had reports from a few people that just about every ROM for the G1 not requiring a specific radio works for the 1.2/Fender. Worse case scenario if you flash a ROM that isn't going to work, you'll get stuck in a boot loop and will just need to flash a new ROM or restore a backup.
What is a backup?
A backup essentially saves the state of your phone. For those computer savvy, it's like creating an image of a hard drive. The easiest way to create a backup is via a custom recovery. Both ClockworkMod and Amon Ra's recovery's include backup applications (e.g. Nandroid, Bart, ClockworkMod). Immediately after achieving root, getting your custom recovery installed, and verifying that your ROM boots properly, you should create a backup. This way, if your phone ever starts going down the tube or you manage to hose something up with your ROM, you can simply restore your backup and be back up and running. This will not fix a truely bricked device however, so don't get your hopes up.
Is my phone bricked?
The basic definition of a bricked devices is one that will not boot into a ROM, will not enter the bootloader, and will not enter recovery. If you still are able to boot into any of the three mentioned, your not bricked and there's a chance to save your device. The problem is that when most people get close to this state (they can only get into fastboot for example) they'll go into a panic and start trying any and everything to get their phone back up and running. This is NOT the thing to do. If you ever are stuck in a similar situation, please come ask for help and don't do anything else with guidance.
How do I get into the bootloader/recovery?
All of these steps are to be completed with the phone powered off.
For fastboot - hold back+power until your loaded into a white screen with the Android dude skateboarding.
For hboot - hold Volume Down+power until your loaded into a white screen with the Android dude skateboarding.
For recovery - hold the home button+power until your loaded into your recovery. For the stock recovery it'll be a triangle with an exclamation mark in it and an error pointing to a box. Hitting the home button again will get you the rest of the way into the stock recovery. If you have a custom recovery you will be loaded into a basic menu.
It's essential to familiarize yourself with these menu's. Before you do anything to start rooting, you should boot into fastboot and right down the information there and keep it somewhere. If your run into problems later on and you can still get into fastboot, make sure you get in there and right down what it's showing then. Make sure you include whatever your fastboot information is whenever your posting about a problem in the forums.
That's all I can think of for now. So good luck!
kernels and spls
Could anyone help with two (or four) nagging questions I've been trying to find answers to?
1.a. what is the difference between droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-120810.zip
and
droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810.zip
?
1.b. I have successfully flashed the first one on my device to fix the green hue issue on CM6.1. Is there any benefit to flashing the second?
2.a. I would like to change my splash1, but can't use fastboot because I don't have the Engineering SPL. Is there any easy way to change the splash1 without having to do the 3-step process of a) flash to Engineering, b) update the splash screen, and c) flash back to stock SPL?
2.b. OK this may be a long shot, but as a programmer, I'm kind of curious: if the answer to 2.a. is "no", then, is the "splash1" image saved in any recovery files anywhere when you do a backup (e.g. if I go into ClockWordMod ROM Manager and choose "Backup Current ROM", does the backup include the splash1 data?), and, if so, would it be feasible to search the recovery image for the splash1 data (e.g. with a program that looks for a binary string matching the raw data of the current splash screen)-- of course, the data would have to be raw and unencrypted and uncompressed-- replace it with the new splash1 data, and then do a restore from the resulting modified recovery file, in order to change the splash screen?
-------
Androot + ClockworkMod ROM Manager + CM6.1
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
mattewong said:
Could anyone help with two (or four) nagging questions I've been trying to find answers to?
1.a. what is the difference between droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-120810.zip
and
droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810.zip
?
1.b. I have successfully flashed the first one on my device to fix the green hue issue on CM6.1. Is there any benefit to flashing the second?
2.a. I would like to change my splash1, but can't use fastboot because I don't have the Engineering SPL. Is there any easy way to change the splash1 without having to do the 3-step process of a) flash to Engineering, b) update the splash screen, and c) flash back to stock SPL?
2.b. OK this may be a long shot, but as a programmer, I'm kind of curious: if the answer to 2.a. is "no", then, is the "splash1" image saved in any recovery files anywhere when you do a backup (e.g. if I go into ClockWordMod ROM Manager and choose "Backup Current ROM", does the backup include the splash1 data?), and, if so, would it be feasible to search the recovery image for the splash1 data (e.g. with a program that looks for a binary string matching the raw data of the current splash screen)-- of course, the data would have to be raw and unencrypted and uncompressed-- replace it with the new splash1 data, and then do a restore from the resulting modified recovery file, in order to change the splash screen?
-------
Androot + ClockworkMod ROM Manager + CM6.1
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
Click to expand...
Click to collapse
droidbasement.com/g1/kernels/ram/2635/17/boot-cm_2635.9_ds_32b_radio2708-oc-uv-xtra-ram-fp-120810.zip is for the 2708 radio which you DON'T have so don't flash it.
No. Flash the Engineering SPL, flash the splash screen, flash the stock spl back. Only way.
No. Splash files are not saved or effected by nandroid. So you can flash the splash screen and restore a nandroid backup (or clockwork backup, whatever) and you'll still have your splash screen.
ok, thank you
can we install the new radio or spl on our phones?
soub31 said:
can we install the new radio or spl on our phones?
Click to expand...
Click to collapse
I've heard that we could but I wouldn't recommend it because it really doesn't benefit.
Binary100100 said:
I've heard that we could but I wouldn't recommend it because it really doesn't benefit.
Click to expand...
Click to collapse
also one last thing i guess we use 32b roms on our phones what about roms the use 2708?
could we just flash an appropriate kernel afterwards?
soub31 said:
also one last thing i guess we use 32b roms on our phones what about roms the use 2708?
could we just flash an appropriate kernel afterwards?
Click to expand...
Click to collapse
If you're referring to CM 6.1.0 and the like, yes.
Binary100100 said:
If you're referring to CM 6.1.0 and the like, yes.
Click to expand...
Click to collapse
not just cm6 roms like yoshi and enomothers when ever i flash them and then the right kernel i just get stuck at the splash screen
I've flashed Yoshi and it did not work at all. It boots to the spalsh1 then to the Android but bootloops from there. So no on Yosi. As for Enomothers, I have successfully flashed this rom and and enjoyed it. However, read all the information before flashing. He has certain requirements that are not compatible with our phones.
Which version of Yoshi are you guys trying?
Good evening viewers, I'm an amateur, but experienced android rooter and I've accidentally worked myself into a tight spot with this dag-blasted MT3G. I was rooting for a friend, thinking it would be simple (like my HTC Hero) and then about halfway through the process, somehow I ended up flashing a different Sappimg and now it's stuck and unusable. It's a T-Mobile MyTouch, with the 3.5mm jack, and I ONLY have access to HBOOT and fastboot. somehow, the recovery has disappeared. it will not boot up into the phone's software at all. I can't seem to find the correct SAPPIMG file for it, and I've been looking extensively. I'll post the info for the phone below.
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT 1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18
and after running the getvar command as the expert suggested, my version is this:
2.10.531.4
My CID is T-MOB10
any assistance would be appreciated.
Ok... here it goes.
Download these to begin with while you READ.
http://rapidshare.com/files/450996411/special_sappimg.zip
http://rapidshare.com/files/436753940/2.53.707.2_-_sappimg.zip
https://rapidshare.com/files/454052569/2.10.531.4.zip
IT IS IMPORTANT THAT YOU READ EVERYTHING I WRITE.
The problem is that the device has conflicting spl and radio combo. The spl has an idea of where the radio should be and how big ect. When they are not matching the flash of a new radio will most likely fail.
To fix this problem, we need to flash a spl compatible with the 6.35 radio.
But the problem lies in the following. All the RUU/sappimg with a spl compatible with the 6.35 has a higher version than yours(starts with 3 something). If we update the version, we cannot flash the desired sappimg which follows. The goldcard will only update up in verion nr, NOT down.
Here comes the trick: We don't let it update the version nr :0)
The special sappimg.zip is part of a 2 step update from HTC. The first part (which i have given you) will update spl, radio and boot partitions only and then restart. It will not touch the version nr until the second part is applied. Well.. we don't need the second part, because by now we have matching spl/radio combo.
Once the spl is updated and the system restarted, we can now flash any ruu we want using the goldcard. We could flash the sappimg.zip with a eng spl inbuilt like the 2.53.707.2 sappimg. Or, just flash stock MT3G 32A 3.5 MM rom.
The steps to follow:
1) Read and understand the above.
2) Rename special_sappimg.zip to sappimg.zip
3) Make sure that you have a working goldcard and flash the sappimg.zip
The device should reboot by it's self. If you get any error saying model id is no correct, you have a faulty goldcard. Also, please verify that the spl has changed to 1.76.xxxx. (flash by holding volume decrease (-) together with power and wait for the hboot to automatically pick up the file)
4) Once the device has rebooted, you should rename the 2.53.707.2_-_sappimg.zip to sappimg.zip and flash it using the goldcard. This image should give you an eng spl. If you device will not accept it/or you wish to have stock image, then rename the stock sappimg(2.10.531.4) to sappimg.zip and flash it the same way as the special sappimg.
5) If you indeed get the eng spl, then you have full control and we can do almost anything we want. Just post here and we can take it from there. The eng spl has the following nr: 1.33.2010.
If you flashed the stock sappimg, then you only need to root and flash custom recovery and you should almost be there... also here post the progress and we will take it from there.
Hope that you will succeed... Good luck :0)
I wish I could tell you that this worked, but it hasn't. I'm only on the first step, because it flashes the bootloader ok, but then hands at the very end of flashing the radio update. No idea why.
Quick update: It actually did flash the bootloader, so I'm on the SPL you suggested, but the radio is still 6.35 and S-On is still there. I'm attempting to flash the second image now, it's been 4 minutes and it's still unzipping system. It might be low battery or something, so I'll charge it tonight and attack it in the morning. Just in case, do you want me to retry flashing the first sappimg, since it hung while installing the radio and eventually shut down?
gundamwfan said:
since it hung while installing the radio and eventually shut down?
Click to expand...
Click to collapse
Thats what we WANT.
I quote: "When they are not matching, the flash of a new radio will most likely fail."
We are only interested in the spl/bootloader. The spl and radio should match by now (spl 1.76 and radio .6.35) .. that's all... and the main version should not had changed. So, it's all as we want, and it SHOULD restart as i stated earlier :0)
Okay. Well, it installed the bootloader as I said, but didn't finish the rest of the process. So I'm trying the second sappimg now, and it's been 2 minutes and it's still unzipping the first part, but the progress bar isn't moving. I'll keep you updated.
Still no luck Mumilover, it just hangs at unzipping the SYSTEM.
have you tried the stock image ?
I have, and it too hangs while updating the radio. I don't know what it is, but that's the same thing that happened with the first sappimg like I told you, installs the bootloader just fine, then hangs at the radio.
what is your fastboot info now?
The same thing it was before, it hasn't changed. And S is still on.
I have this exact same problem, to the T. Please let me know if you can figure out anything else because i'm at a loss.
You are not reading what i write.
It's imperative that the spl CHANGE before you can do ****....
I think the better question is how at this point tho..plus, how did you make that special sappimg.zip file? Can we make a custom .zip to install an older spl version? There has to be a way to get past this. I would take a working anything if I could at this point :/
veritas17 said:
I think the better question is how at this point tho..plus, how did you make that special sappimg.zip file? Can we make a custom .zip to install an older spl version? There has to be a way to get past this. I would take a working anything if I could at this point :/
Click to expand...
Click to collapse
Get a job at htc and leak the keys to us
Try this file instead of the special sappimg... remember to rename it to sappimg.zip :0)
https://rapidshare.com/files/3671633756/3.05.421.3_1.zip
Also, try this file if the above did not work:
https://rapidshare.com/files/531578080/Rogers_3.05.631.7_pt1.zip
The only way you can continue, is when your spl change to 1.76.00XX, where you XX can be 08,09,10 or what ever...
Hey, mumilover, I really appreciate what you've done so far, but I must tell you I've read everything. Your tips, so far, show promise. I've yet to try the last two files, so I'll try those now. But the thing is, when I flashed the first file in the process to get the proper HBOOT (1.76) that worked, but the second image would hang at the unzip, and the third is what changed my bootloader back to 1.33. For now, I will try the two images you've just posted.
UPDATE: the first image you posted above DID flash a new radio, but when it got to the section where it flashes the boot, it read "Fail - iE" and explained it as an image error fail. Could the zip have possibly been corrupted? At least the radio has been changed.
sigh...
As I was typing this, I rebooted and saw that the radio had indeed not changed, even though the flasher said it had been updated. Guess it didn't finalize.
Nope, same thing for both, though hopefully this assists in helping diagnose the problem. The second image you posted, also gets to the part where it flashes the bootloader, then gives me the generic Image Error Fail again and doesn't flash the bootloader. Oddly enough it did take me from 1.76.0008 all the way up to .0010 with those two flashes. No idea what that means at all, or if any revision of the 1.76 is preferred to the .0008 revision. Let me know, I'm waiting here on your advice.
That's funny. You should not be able to update the radio if the spl is mismatched....
Well... now that you have a new radio, try the special image again. The good thing with that special image is, that it will flash the spl FIRST, then the radio. Giv it a try... This approach has WORKED before... on multiple devices... When i can find the posts, i'll link to them