Related
Let me explain to you the whole story. I obviously know im going to get flamed for this one. I will give you the short short version
I had a rooted MT3G fender with this Rom installed
http:/forum.xda-developers.com/showthread.php?t=669911
It worked all good until i started messing with stuff. I wanted this rom installed
http:/forum.xda-developers.com/showthread.php?t=673394
Since it said 32a and MT3G fender is 32a i assumed that it will install and no problems. So i used the gold card to change radio and spl to the 3.22 series. only to find out that they dont work for my phone. based on this post
"You are now screwed with a downgraded SPL and radio that do not work on this phone YAAAAAAY." -crypysmoker-
[THUNK AND FIXED] Rooting Mytouch Fender LE 32a/ Mytouch 1.2 DONT!!
http:/forum.xda-developers.com/showthread.php?t=622530
So now im thinking great i didnt catch that so let me just move back to where i was before. using the last section of that previous thread to install the stock radio and spl. i have done this already and know it works. so i install the stock radio and spl and the custom recovery. Boot up into recovery and restore nandroid. everything is going ok utill.....it locks up in a boot loop. i then boot back up into recovery and erase data. after that i tryed another nandroid restore and to my wonderful surprise i now lost the ability to mount the sdcard. i restarted and tryed many different cards and all failed. I then boot up into hboot restore with the goldcard and it then locks up at system.
Great now im looking for something to fix this whole mess. after that i try to reinstall the original spl and radio. I then have an error "signature verify failed." Now im thinking WTF!!!!!
I then find a thread about the RUU and how to turn off "S-on" if i install this official HTC app. However come to find out its the asia version. WONDERFUL FOR ME!!! I then found the Official T-mobile MT3G RUU, installed it and now i have a fastboot installed with a memchip with a red circle around it, not the 3 skate droids, and cant boot into HBOOT ,with the volume down button. All that i see is "RUU USB." I have adb but now get the error "remote not allowed." it used to be "signature verify failed." i have no recovery, no HBOOT, just fast boot with RUU USB.
How to i fix this mess up and get back to this?
T-Mobile MyTouch 3g Fender Edition Stock ROM with ROOT!
http:/forum.xda-developers.com/showthread.php?p=5451898&posted=1#post5451898
This is what i have and show
Sapphire pvt 32a ship s-on G
Hboot-1.33.0013 (sapp31000)
cpld-13
radio-2.22.23.02
oct 21 2009,22:33:27
RUU USB
This is definitely a snowball effect right here.
Oh also i cant go and exchange the MT3g fender because im past my 14 days and i already did it on the first day. LOL
I actually am stuck on the same screen with the same phone. I hope someone has been able to get this fixed
Damn, not trying to be mean, but you screwed up a lot.
I have the same version device as you, and I upgraded my radio/SPL. and did a lot of stuff, i semi-bricked it, but i got it working again. I suggest you re-root your whole entire phone. including flashing all the radios, spl,recovery, and etc.
Try following this theunlockr[DOT]com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The problem is that the phone is stuck in a bit of an interesting state. You can't flash from an RUU at this point because the engineering SPL used to root the phone is version 2.53.x, while the RUU's ROM is 2.10.x. You also cannot flash any images to the phone because the SPL is locked (S-ON). So the only way to fix the phone at this point would be to somehow get an HTC-signed 2.53+ ROM for the SAPP31000 (mytouch 3g 1.2/fender) or find a way to unlock the SPL. I had a nice chat with some of the Modaco guys and we went through a lot of options with none of them working. The phone's basically in a bit of a chicken vs. egg state. So personally, I will be building a serial cable to manually unlock the SPL so that I can flash images back on manually.
So, while I wish it was as easy as just re-flashing the phone, you can't do that with a locked SPL and no HBOOT mode available. Onward to a serial/TTL cable advendure!
Once I get the parts in to build it, I'll follow up here with my results
shintokun said:
I suggest you re-root your whole entire phone. including flashing all the radios, spl,recovery, and etc.
Click to expand...
Click to collapse
Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).
knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.
so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814
lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App
knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App
knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit
NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.
Possibly try to re download the sappimg from the mgic spl thread?
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.
NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!
hi guys, i have a Fender Mytouch - which was running roms nicely till i booted back into recovery then selected restart/reboot and it went straight to the HBOOT screen - i press back to go to fastboot but nothing happens, i tried all key combos to get into recovery or fastboot but nothing. Completly stuck on this HBOOT screen :-(
PVT 32A SHIP S-ON G
HBOOT - 1.33.0013
CPLD-13
RADIO - 2.22.23.02
Oct 21 2009
please ive tried to look other posts but they all can get into fastboot i cant, can someone help i didnt flash any spl or anything but 32a/32b roms over the last month - oh and it was running recovery-RA-sapphire-v1.6.2G before this happened
Is there a way to flash a recovery image from the HBOOT screen ? I really dont know what the fook happened - grrrr crazy
please can one of the smart guys on here give me assistance - been trying to look for the solotuion for 3 hours now
zerodi said:
Is there a way to flash a recovery image from the HBOOT screen ? I really dont know what the fook happened - grrrr crazy
Click to expand...
Click to collapse
Yes, if you have an engineering SPL, which you do not. You'll need to flash a stock ROM.
do not flash an eng spl. Our phones do not run on anything other then stock radio and spl. Also, even though it is a 32a board, only g1 /32b roms and recoveries work.
What happened to you makes no sense unless your leaving something out or tried to flash an ota Rom.
Take battery out, put it back in /hold home and power, should go into recovery. If not, I would say follow my guide in Sig to start over but you'll probably screw up on flashing the radio and spl.
you flashed a wrong radio, man
"PVT 32A SHIP S-ON G
HBOOT - 1.33.0013
CPLD-13
RADIO - 2.22.23.02"
2.22.23.02 is the radio for google branded, my touch 3g = PVT 32B .... not your 32A
turop said:
you flashed a wrong radio, man
"PVT 32A SHIP S-ON G
HBOOT - 1.33.0013
CPLD-13
RADIO - 2.22.23.02"
2.22.23.02 is the radio for google branded, my touch 3g = PVT 32B .... not your 32A
Click to expand...
Click to collapse
lol Oops Didnt catch that. HEs right, you have the G1 radio going. Ours should be .12 at the end... I think lol. I havent had to mess with it for a while since Universal Androot works now. But again, you may want to start over if you know what your doing. Otherwise, time to go get a replacement because flashing the radio and spl, your probably going to brick it anyway.
crypysmoker said:
do not flash an eng spl. Our phones do not run on anything other then stock radio and spl. Also, even though it is a 32a board, only g1 /32b roms and recoveries work.
What happened to you makes no sense unless your leaving something out or tried to flash an ota Rom.
Take battery out, put it back in /hold home and power, should go into recovery. If not, I would say follow my guide in Sig to start over but you'll probably screw up on flashing the radio and spl.
Click to expand...
Click to collapse
Thanks encouraging as your words are i didnt do anything / screw anything up all i did was reboot into recovery from the sparks rom then reboot/restart and it gave me this problem !!!
turop said:
you flashed a wrong radio, man
"PVT 32A SHIP S-ON G
HBOOT - 1.33.0013
CPLD-13
RADIO - 2.22.23.02"
2.22.23.02 is the radio for google branded, my touch 3g = PVT 32B .... not your 32A
Click to expand...
Click to collapse
Umm..what?
Your radio/SPL are fine. As for your situation, did you root using the goldcard method? If you did, try doing it over and see if it'll let you into fastboot after loading the engineering sappimg.
Sent using Tapatalk.
hey guys , i got into recovery now and wiped everything then flashed a rom but its stuck on the rom boot screen now, cannot boot into the rom
I just flashed [MT3G 1.2/LE Fender] CR_Slide2G1_v1 and it works ! My LE is back up and running
i really dont know why that happened stuck on the Hboot screen
zerodi said:
I just flashed [MT3G 1.2/LE Fender] CR_Slide2G1_v1 and it works ! My LE is back up and running
i really dont know why that happened stuck on the Hboot screen
Click to expand...
Click to collapse
Some roms take 10-15 min to boot up so you just gota have patience .
Also, any roms built with a Cyan kernel after 5.0.8 will work on our phones also.
IS the location working on that rom for you?
When it first cam eout I used it for months with no problems.. but then I tried to go back a few days ago and the weather/clock will not find me.
yeah with wifi it picks up my location for the weather just fine
zerodi said:
yeah with wifi it picks up my location for the weather just fine
Click to expand...
Click to collapse
only on wifi? thats weird. That would explain why it keeps asking for wifi to be on though lol.
You wont belive it but this f***in ohone has just gone and done the same problem again.....
I was charging it then powered off the device then turned it on after 30mins and its now stuck on the HBOOT screen AGAIN - grrrrrr i cant belive this thing
So now im completey stuck again - if this happens everything i charge this thing then thats not gonna be cool.
Im trying this method here http://forum.xda-developers.com/showthread.php?t=734617 , posted by DonJuan692006
but because the phone cant boot up into the OS adb doesnt see it as list of devices so i cant do the goldcard and start again.....
hmmmm i might throw this thing outta the window
Without a goldcard your not going to be able to go that route. If you've still got your Hero, you can use it to make the goldcard, or any Android powered device for that matter. Maybe just wait it out and see if it just starts working as before?
i have a successful goldcard.img from my Hero will take be ok to use for the Fender you thinks ?
damm-it just tried that and SAPPIMG gives an Incorrect Model ID - because im using the Hero goldcard
damm i dont know what else to try
does anyone have a Fender Goldcard img they would like to share with me - proberly wont work but you never know i might get lucky
cheers
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
So I was "flashing" a new ROM via ClockworkMod Recovery v2.5.07 earlier on my phone, and the battery was near dead, so I decide to plug it in. I didn't bother to think/realize it was plugged into the USB port on my computer, and as I did so, the installation stopped and the phone turned off. I turned it back on, to find the "MyTouch 3G" green splash screen either stuck and the phone eventually turns off, or it loops, and the phone keeps rebooting. I've tried flashing flashing the ROM again and some different ROMS I believe, with no luck. Yes I can get to the recovery screen and I can get to hboot/fastboot. Any direct troubleshooting would be very much appreciated. I don't really care what ROM I have on my phone at the moment, I just need something that works. My old blackberry is missing several keys and the rest barely work, so it would be nice having this one back up and running I've searched other threads and other forums with no luck so far. PS I don't have a Nandroid backup...thought I did, guess not though.
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP30000)
CPLD-10
RADIO-2.22.28.25
Thanks,
Shane
Flash recovery AmonRa 1.7.0G first
Code:
fastboot flash recovery recovery.img
Then search 1.33.0013 or 1.33.0013d and flash it via
Code:
fastboot flash hboot hboot.img
You will have
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP30000)
and able to install new 32B roms (for radio 2.22.28.25) via recovery...
p.s. Don't flash anything when battery at 30% or less
Most roms require the new radio and spl that came with the froyo update. You have the radio, but you need the 1.33.0013 or 1.33.0013d spl.
tvall said:
Most roms require the new radio and spl that came with the froyo update. You have the radio, but you need the 1.33.0013 or 1.33.0013d spl.
Click to expand...
Click to collapse
Thx for comment, i updated mine...
So a problem, I accidentally flashed the recovery-RA-sapphire-v1.7.0G-cyan.img, then flashed the spl, and now of course I don't have the ability for fastboot...problem?
Shano56 said:
So a problem, I accidentally flashed the recovery-RA-sapphire-v1.7.0G-cyan.img, then flashed the spl, and now of course I don't have the ability for fastboot...problem?
Click to expand...
Click to collapse
Do you have ability to load recovery?
p.s. fastboot commands are locked in hboot 1.33.0013 (1.33.0013d)
yeah I know they were blocked, but I figured out how to access via adb
so I got the proper recovery image on...and flashed CM6, however it's still looping on the MT3G splash screen
Edit: Weird - I tried the 5.0.8-DS and it worked. I appreciate your help..any clue why 6 don't work?
Shano56 said:
yeah I know they were blocked, but I figured out how to access via adb
so I got the proper recovery image on...and flashed CM6, however it's still looping on the MT3G splash screen
Edit: Weird - I tried the 5.0.8-DS and it worked. I appreciate your help..any clue why 6 don't work?
Click to expand...
Click to collapse
May be need special kernel for radio 2.22.28.25? What requirements for CM6?
Not sure, but it says I'm running 6.1 now. And I downgraded my radio to 2.22.23.02.
Shano56 said:
yeah I know they were blocked, but I figured out how to access via adb
so I got the proper recovery image on...and flashed CM6, however it's still looping on the MT3G splash screen
Edit: Weird - I tried the 5.0.8-DS and it worked. I appreciate your help..any clue why 6 don't work?
Click to expand...
Click to collapse
Ezterry released a different cm6 for people that had problems with the first one, I think it was a kernel issue
Sent from my HTC Magic using XDA App