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!
Related
Hi everyone,
My phone is magic (TIM).After I flashed the new radio(6.35.10.18) and SPL(1.76.2007), I don't know why my ENG S turned ON automatically, and I can't solve it (even if I reflash the SPL in recovery).
Also there is a more serious problem, After I flashed any new ROM such as SuperHero, Eclaire, Villian,Robomix v0.1 and rebooted it, it keeps frozen at the first boot screen(splash screen). At last I tried to use a CM ROM, it can be started finally!
I'm very confused, the CM ROM is Android 1.5, so does it mean that I can only use the ROM with 1.5 for now? Cannot be!^%%$#@@!%$...
You used a CM rom with a 6.35 radio and 1.76 spl? And can't use the roms that require the new radio and spl? I'm pretty sure you DIDNT FLASH the new radio and spl.
Yes, I did! I pressed BACK+POWER to boot into fastboot model, it displays 1.76 and 6.35 with ENG S-ON!
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
KAwAtA said:
That's so strange that you can use a CM rom with that radio and SPL. Switching to S-OFF won't make much of a difference for this situation (correct me if I'm wrong)
Did you flash a new recovery when you updated your radiospl
Click to expand...
Click to collapse
er...it's CursorSense32A-1.2.6.1 and recovery 1.6.2(the hero version)
Wow, you're using cursor sense? that would've been nicer to know rather than CyanogenMod
xaueious said:
Sigh... Wrong forum... But this is not that common of a problem...
http://forum.xda-developers.com/showthread.php?t=643291
Click to expand...
Click to collapse
I don't get it, how does that help his problem? I know he wants to change to S-OFF but the main problem is his roms don't load up. But like the other guy, I notice that they can only use CursorSense soo im not sure
Show me step by step on how you flashed the ENG 1.76.2007 SPL (although this shouldnt affect it at all)
pyee0124 said:
You should still be able to flash custom ROMS regardless of S-ON. One of the other things you should try is formatting your SD card again.. Try a full FAT32, then try partitioning afterwards. I found that I could only boot Ahmgsk with FAT32/Swap/Ext2.
Click to expand...
Click to collapse
Do you have any swap/ext partitions?
First I flashed Engineering SPL 1.33.2010 in recovery, and reboot into fastboot, I saw I'm ENG S-OFF at that moment, so I flashed new SPL and radio then. Maybe the problem comes with the old incompatible recovery, after I reboot my phone this time, it beame bootlooping(see my thread posted:http://forum.xda-developers.com/showthread.php?t=658220), I was almost thought it was bricked! But luckily the phone fixed itself(I thought), I could enter fastboot, at that time I noticed that my ENG changed S-ON.
That's my whole story, hope it can help you to help me fix the problem.
I have a ext3 partition but in order to protect my TF card I didn't partition a swap
Sorry man, hope someone else can help you. I just dont even understand how you got an S-ON SPL if you followed the thread ppl provided in the other one cause an ENG SPL was provided. Dunno how you got perfect, and I am completely not sure why you can't flash other new radio Roms. Hopefully someone else can help
It doesn't matter bro, I'll find another way to solve it, still thank you!
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
xaueious said:
Damn it do I have to spell out everything? I even linked to the thread. All you had to do was read -_-
1)
You just need to run the following command to get S-OFF again:
fastboot oem enableqxdm 0
That was the title of the thread.
2)
Dude you sound clueless about your ROMs. Cyanogenmod has been 1.6 since forever, but there's no way that run actually boots properly with new radio. Plus Cyanogenmod doesn't even boot on 32A Magics without a kernel port, which I doubt you flashed.
Do yourself a favor and get your lazy ass to Cyanogenmod irc and ask there. It isn't just a matter of getting your phone working. If you are flashing ROMs you need to know what the hell's going on.
http://www.cyanogenmod.com/irc
Click to expand...
Click to collapse
Um he made an error and he said it was CursorSense, not CM.
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
xaueious said:
fastboot oem enableqxdm 0
There's been quite a few SD card problem forum threads. Try harder next time.
Click to expand...
Click to collapse
and after reading that thread, I read that you posted this command for sd card problems. Please point out where He is supposed to read, I'm either blind or you're wrong (Seeing as how you missed his CursorSense mistake and stating that the title of the other thread is fastboot oem enableqxdm 0, lol, I don't think I'm blind)
Sorry if I sound like a douchebag here but seriously, you although this guy posted in the wrong section *sigh*, if you wanna be a douche, at least read over his problems properly. You're not helping at all right now and again, he made a mistake about cyanogenmod which was already cleared up and you failed to read that. You should really, get your lazy ass to read this thread more clearly (LOL I don't evne know if that made sense, its 3am and since u live in toronto, oh same time there i assume!) But yeah, if you wanna be a douche, you gotta at least be right or something. But whatever, I just find it totally ridiculous how you're flaming this guy. But if I'm wrong, then go for it and flame me! I haven't seen anything helpful from you here
KAwAtA said:
Second, doesn't fastboot oem enableqxdm 0 fix sd card problems? I've never heard of that turning S to OFF, interesting.......
Click to expand...
Click to collapse
I think so too, it's a forum to discuss about technic, not complain.
I have the same situation as you, the ENG SPL changed from S-OFF to S-ON.
Also, can't boot any 2.0/2.1 roms.
I did a lot of flash and try to fix the SPL to S-OFF, but no luck. Such as:
Flash ENG SPL 1.76.2007 again and again;
Flash back to 3.22 radio and 1.33 SPL, then flash the 1.33 ENG SPL;
Flash the device from 3.22 radio and 1.33 SP to 6.35 radio and 1.76 SPL;
A month after, I noticed that my phone can't turn on the Bluetooth. The Bluetooth only can be turned on while first time I boot up the phone, when you disable it and try to enable again, no go...
I send the phone back to HTC for repair, and HTC said that my motherboard was damaged...
I notice more and more people have the same issue as me (and you), I am afraid that some of the 2.1 rom might have some wrong drivers that make my phone go wrong.. (because I didn't flash any rom, I only restart my phone while my phone can't boot and SPL changed to S-ON....)
Be careful everyone, hope my finding is wrong..
I've seen the oem command fix the S-ON to S-OFF before, which is why I posted it. Sd card disabling and s-on happen together in those cases.
Come to think of it, the time I got S-ON too was with battery pull and hard rebooting. Maybe S-ON is activated with memory debugging as a flash corruption protection scheme.
littlestrong try checking the integrity of your file system and reflashing your ROM entirely. Sometimes flash just wears out.
There's also the issue of flashing the radio and spl from recovery, as sometimes it causes issues. The best way is to do it with fastboot. I know your SPL is locked so you can't do that though. Your best bet was the oem command with 1.76 HBOOT versions. Other than that it would be playing with serial cables and JTAG.
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
nabor said:
So you mean mabe the currupted ROM makes S-ON, and my system files have been destoried. But I've flashed many ROMs, none of them works. I can only do is to run the command "fastboot erase system -w" before flash to give my phone a most CLEAN status.
Second, can oem commands flash SPL and recovery? May you tell me how?
Click to expand...
Click to collapse
I've never heard of "oem" commands flashing spl/radio/rec. But you can give the command he gave you a try
The best way would be to use fastboot commands. I don't think a corrupted rom makes it S-ON. I got S-OFF as soon as I flashed my eng spl
O.K. thanks. Got it, seems no solutions yet. I think I should learn the kernel first, it is fundamentally to know how a ROM, a system works!
And sorry for my poor English, I fund I missed a "y" above in "mabe"
can somebody tell me, how in this case I can install a new SPL, or recovery?
Mod. edit: not dev related, moved to general
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
I tried to root mytouch 1.2 (t-mobile) using "theunlockr" sappimg.zip way but when I reached the recovery step, the device didn't boot into recovery. Then I tried a lot of flashes and things but ended up with this:
-booting hangs with htc magic screen and can't get into recovery
-can use fastboot but the sappimg.zip (from theunlockr for rooting mytouch 1.2) hangs on unzipping system and other sappimg.zip version says it's an older version and can't update.
-can't flash anything from fastboot because it says: FAILED (remote: signature verify fail).
-SAAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
any ideas please?
up up up up
It looks like either the sappimg failed to flash after doing the radio, or you didn't flash the stock radio back after flashing the recovery. Your only hope that I can think of is to redownload the sappimg and try the whole process over again.
i concur :0)
Thanks for your replay.
I redownloaded the file but it starts updating the system not the radio and as I said before it hangs on unzipping system. Is there any way to make sappimg.zip starts with radio?
Not that I know of. The only way I could imagine would be to extract just the radio image and flash it, but you would need the rest of the sappimg to do that. You could try finding a proper RUU for your device and running that from your computer with your goldcard in your phone, and then start over with rooting.
Sent from my HTC Magic using XDA App
DonJuan692006 said:
You could try finding a proper RUU for your device and running that from your computer with your goldcard in your phone, and then start over with rooting.
Click to expand...
Click to collapse
please more explanation
thanks for your fast replay
Possible Fix?
I have a similar problem, but unlike mine, yours can be fixed. You do not have a perfected spl, so I think that you accidently flashed a 32B sappimg for your 32A. I think this is the solution: http://www.askabouthugo.com/general/solved-android-phone-stops-on-fastboot-with-remote-signature-verify-fail/
Let me know.
TheBladeofFate said:
I have a similar problem, but unlike mine, yours can be fixed. You do not have a perfected spl, so I think that you accidently flashed a 32B sappimg for your 32A. I think this is the solution: http://www.askabouthugo.com/general...n-fastboot-with-remote-signature-verify-fail/
Let me know.
Click to expand...
Click to collapse
How do you figure the OP doesn't have a perfected spl?
Sent from my HTC Magic using XDA App
any other suggestions?
place this on your goldcard and flash it.
http://www.4shared.com/file/-wzTZgdP/RUU_Sapphire_T-Mobile_US_21053.html
I'm assuming your tmobile mytouch 1.2 right? Should flash over your stuff since i'm assuming you do have a perfected SPL.
MrShides said:
place this on your goldcard and flash it.
http://www.4shared.com/file/-wzTZgdP/RUU_Sapphire_T-Mobile_US_21053.html
I'm assuming your tmobile mytouch 1.2 right? Should flash over your stuff since i'm assuming you do have a perfected SPL.
Click to expand...
Click to collapse
Please tell me how he's going to flash a .exe file from his phone? If you go this route, you download it, then run the .exe from your computer with the phone hooked up via USB and in fastboot. You also need to put your goldcard in your phone. Problem is, if it fails, you'll be stuck at the RUU screen on your phone (which is basically fastboot) and you'll be kind of hosed.
Hey guys,
I have myself a situation here.
I have a 32A Magic device, running the 1.76.2007 ENG SPL and the latest 6.35 Radio.
Not sure about the exact version as I don't have the phone with me at the moment, but it's the last one. 19 I think.
It is running the RA Hero Recovery. Version 1.6.2.
I received the phone with a Taiwanese RUU installed and with a Perfect 1.76.0007 SPL. Followed some steps and managed to install a custom recovery and SPL/Radio.
The thing is, that the device was always S-ON. Now, I want to downgrade to the old radio because of a battery drain issue I am having all of a sudden and realize that if the Security is ON, I can't downgrade directly from FASTBOOT.
I looked all over for a way to make the S-OFF, but was unable to find a definite way of achieving this. All of the guides referred to a device which had the old radio/SPL.
I also found This guide from Cyanogenmod which seems to address the 6.35 devices, but I get a USB error when trying to install the RUU. Maybe it's because I skipped the Goldcard method?
The device has been on here for a long time and I was wondering if there wasn't an easier way to achieve the S-OFF or should I go and follow the whole Goldcard/RUU/Custom recovery/Radio/SPL method?
The problem in the Goldcard is that I don't have a card reader and I don't think that my card is good for Gold.
I've flashed numerous ROMs but all were using the new radio/SPL.
Any help would be appreciated.
Flash a different spl from recovery?
tvall said:
Flash a different spl from recovery?
Click to expand...
Click to collapse
Flash a different NEW SPL or flash a different OLD SPL?
Because I think that Flashing an OLD SPL from recovery will brick my phone since I have the NEW radio.
Godzi said:
Flash a different NEW SPL or flash a different OLD SPL?
Because I think that Flashing an OLD SPL from recovery will brick my phone since I have the NEW radio.
Click to expand...
Click to collapse
I was thinking a new spl. On the 32b if you have an eng spl you have s-off. It might be diffrent on 32a... wait for someone with experience with 32a devices to reply
Run this command in fastboot mode and restart into fastboot again.
Code:
fastboot oem eraseconfig
The fastboot oem eraseconfig command did the trick. 3 days of looking all over the place and it was as easy as a fastboot command. Strange thing is that I didn't see it anywhere.
Thank you. Old Radio and SPL are on there, let's hope the battery doesn't drain in 15 hours anymore.
Glad i could assist :0)
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