[Q] Help: bootlooping and bad recovery - myTouch 3G, Magic General

Hi Everyone,
I tried installing an update of COS-Gingerbread for my T-Mobile branded MyTouch 3g. The ROM installed correctly and seemed to be running fine, but for some reason I wanted to revert to a stable version of Cyanogen so I decided to boot into recovery and use one of my older backups. Well my recovery stopped working when I tried to do this, and then my phone started bootlooping so I could not boot normally. The only thing I was able to do was boot into hboot. So I did this and I kind of panicked and tried flashing SAPPIMG.nbh in fastboot because I figured at the very least I just wanted my phone to work. However this resulted in a bootloop and this is the state that I am currently in.
Is there a way I can still fix my phone?
If anyone has any suggestions as to how to restore functionality to my phone, that would be awesome. I feel like I'm not completely hosed because I can access hboot.
Here's some information about my phone from the bootloader:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
May 27 2009, 19:06:41
It is a T-Mobile branded MyTouch 3g, definitely a 32B. Thank you for any help and please let me know of any other information I can gather to help out. Thanks!

You are in good shape...
Run this command:
Code:
fastboot getvar verion-main

Thanks for the help!
I ran the command and the console returned this:
version-main: 1.88.531.1

Just to be sure... run this command:
Code:
fastboot getvar cid
Depending on you answer, i will upload the right sappimg for you to flash :0)

As far as I can tell the output of the command yielded this:
T-MOB010, but there's some symbols after it.
I've attached a screenshot of the console output. Thanks!

Download this:
https://rapidshare.com/files/433519738/1.94.531.1.nbh
Rename it to sappimg.nbh (not sappimg.nbh.nbh)
Put it on an empty sdcard... Start the device by holding volume - (decrease) down together with power button. Let the sappimg load and restart and you should be back in stock software... you can then root, and get custom recovery following my guide found in my signature...
If the above image fails(it should not)... try this image:
https://rapidshare.com/files/454052569/2.10.531.4.zip
Both images should work without the use of goldcard...
remember to hit that "thank-you" button or donate :0)

I tried the first file and that seemed to load fine, except the phone still bootlooped. I am waiting on my download for the second file right now and I will post again with those results. Thanks!

I take it I should rename the second file to SAPPIMG.zip?

I first tried the .nbh file, and this seemed to load fine however it still resulted in a bootloop.
I tried the .zip file and this did not work. When fastboot ran the file, it loaded correctly, however it then says "Model ID incorrect! Update Fail!".
The SPL now says:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP30000)
CPLD-10
RADIO-2.22.23.02
Jul 31 2009
Any next steps? Thanks!

Did you give it time to load?
It can take around 10 min to boot the first time...

Yeah, its definitely bootlooping. It takes about 30 seconds on the MyTouch3g image and then goes black, vibrates and keeps repeating.

Yeah I did. The loop actually only takes about 30 seconds to complete. Its about 20ish seconds on the MyTouch3g screen, then it goes blank, vibrates and repeats.
[Sorry for the repeat]

Hmm...
Boot into fastboot and then type this:
Code:
fastboot oem boot
See if it helps... also post here the outcome

Alrighty, I just ran that command. Attached is a screenshot of the output. After this ran, the phone was rebooted, but it still looped.

looking at this thread:
http://forum.xda-developers.com/showthread.php?t=659403
The nbh file i gave you is the right one...
I have no idea why it's not working...
Maybe somebody else have an input?

I will try over there. Thanks a ton for the help! I'll keep this thread updated if any progress is made.

Is there a possibility that this is bootlooping because I haven't been wiping the partitions before running the files? Should I try running something like fastboot erase system -w, and then letting the bootloader run SAPPIMG.nbh? Any suggestions along those lines? I was a little scared to try that on the chance of killing the bootloader since I can't use flash in fastboot. Thanks!

The command is harmless... it will just delete the system and cache partitions.
They will be rewritten when flashing the sappimg....
But there are 2 issues:
1) The spl running now may not permit erase commands
2) As stated above, those partitions are overwritten... so an erase before a write is not necessary. But give it a try.. it may help :0)

Yeah, the spl doesn't permit that command. Is it worth creating a Goldcard to try get the .zip file to run?

Why not...
We also have other possibilities by flashing images containing eng spl.
Goldcard is always a good tool to have..

Related

[FIXED!] HTC Magic need help! phone bricked?

Hey guys
I'm so desperate and you are my last hope. I was looking for hours in several forums but didn't find any solution.
What I did:
I updated the phone to 6.35 Radio and 1.76.2007 SPL and installed a Eclair ROM. Everything went well until I installed ROM Manager app. Then I installed Cyanogen mod through ROM Manager and since then nothing works!
What's the problem:
When I switch phone on it sticks on the HTC boot screen and nothing happens.
I can go to fastboot mode but ADB doesn't recognize my phone.
I also can go to recovery mode and ADB sees the device but I cannot install any image and I cannot choose any item from the menu.
What I tried:
connect with fastboot usb: phone isn't recognized
flash via fastboot in recovery mode: <waiting for device> no response.
Install a sappimg.nbh from sdcard: Fail! main version is older.
My version:
SAPPHIRE PVT 32A SHIP S-ON G (why G??? isn't that the 32B version?)
HBOOT-1.33.0013 (SAPP10000)
RADIO-6.35.10.18
Thank you very much for your help!
LOL, I almost started cracking up. "Help me, you are my only hope" (Star Wars)
Anyhow.
Start over. Download the stock Rom, radio and spl for your MT3G. I ran into something similar with mine. I had to erase system from the CLI (command line) fastboot and wipe the phone. Then used the stock sappimg.img to get mine functioning again.
This will "Unroot" your phone
I had to plug the phone in via usb. Go to terminal or dos, and fastboot.
fastboot erase system -w
fastboot erase boot
fastboot flash boot boot.img
from there I turned the phone off, and then I copied sappimg.img to the memcard, and then booted using the vol down + power and let it install the factory rom, radio, spl and recovery.
Or you also stated that you have yours rooted. You're going to have to download the original radio, and rename it to radio.img and then flash it over using fastboot. (fastboot flash radio radio.img). This would get you to the original radio. Then I would revert back to the original ROM w/root ROM.
This worked for me. Im hoping that someone else will chime in and say if this is the correct method to use. Im not an expert. I did this at my own risk.
Someone else want to chime in?
Thanks for your help!
I wasn't conscious that I cited a Star Wars quotation :-D
First I tried to follow your steps but without succes. When I run "fastboot erase system -w" it says: remote not allow. It seems my phone isn't rooted anymore.
Also the command "fastboot flash radio radio.img" doesn't work.
Where can I get the stock ROM? Is there a possibility to extract these files from the RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe tool?
Nevertheless I keep going on although I'm a little bit tired of this issue. However, it's my mistake.
The reason why I wanted to flash my device was because I was sick of this old, boring and lame Android 1.5. Why isn't HTC getting ahead and supplies us more up to date software? An ambitious single programmer is able to provide Android 2.1 but HTC with its high-paid engineer team isn't. That's weird!
It looks like you have to put on one of the engineering SPL's first in-order to wipe the device. By the way, mine is a 32A board, and has "G" also. Weird I know.
I believe the RUU ROMS are stock. So flashing these to the phone should unroot your phone. There is a list of all the RUU ROMS and guides here:
http://forum.xda-developers.com/showthread.php?t=659403
or
http://forum.xda-developers.com/showthread.php?t=682243
These are great sources of information. I'm not an absolute expert, more of a novice. I'm new to the AC but, reading guides and such, you should get your answer and you can try a few things (within reason).
BTW, when you said that fastboot flash radio radio.img doesn't work, have you downloaded the stock radio and spl and copied them to the AndroidSDK\Tools folder? That's probably the reason it isn't working. You have to have the SDK downloaded and installed. (Read The Guides provided to help you) "Use the Force!" HAHA!
So I tried many different ways to save my htc. But by now no success!
As I described I can go into fastboot but I cannot run any commands (remote not allow). I haven't root anymore!
When I go to recovery mode it sticks. I cannot choose any item from the menu.
The only way to get the phone working is via the sdcard. It's possible to install a sappimg.zip but it says: "Fail! Main version is older!" So i have no chance to downgrade. I need a sappimg that has a higher version than my current one.
Also rooting seems not to be possible due to I have to access recovery mode (which isn't working).
Finally, the only way I see at the moment is trying some stuff that works only via the sdcard.
Thank you guys
If you are getting that sort of error that indicates that you have not created a correct goldcard. You need to have that in order to flash these devices.
Go to theunlockr.com and read that tutorial about how to create one. Or click here:
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
Are you really sure that`s because of a wrong goldcard? I´ve tried 2 different sdcards several times but every time with the same error (Main version is odler).
No further ideas?
I can't do anything. recovery mode always crashes, no root access, goldcard doesn't work.
Finally I'm back on Android!
I could solve my problem. I found a sappimg.zip (http://rapidshare.com/files/266290371/sappimg.zip) that turned my phone to:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
RADIO-6.35.10.18
After that, I was able to flash trough the _HTC Magic_RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_CH_release_signed_NoDriver.exe.
Now I'm running on a stock ROM
madboy87 said:
Finally I'm back on Android!
I could solve my problem. I found a sappimg.zip (http://rapidshare.com/files/266290371/sappimg.zip) that turned my phone to:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
RADIO-6.35.10.18
After that, I was able to flash trough the _HTC Magic_RUU_Sapphire_HTC_Europe_2.20.401.2_HTC_CH_release_signed_NoDriver.exe.
Now I'm running on a stock ROM
Click to expand...
Click to collapse
Good to hear.
I'll take the liberty of modifying the title of your original post and close this if you will no longer be needing any assistance. Should you or anyone else decide to need it re-opened, just send me a pm. Thanks!

Trouble Rooting Mytouch 1.2

Hello,
I'm not an expert at modding and hacking but I can definately follow directions. I used a G1 for about a year and flashed it plenty of times with different roms, radios, and spls. I ended up getting a MyTouch 1.2 and proceeded to try to root it so that I can enjoy CM's great roms.
Followed the directions on the unlockr
Made the gold card and went to flash the sappimg.img from the site. The flash went through fine but the phone just got stuck at the HTC Magic screen. Now I know what my mistake was there. I didn't think it was a big deal and continued with the steps. Mainly because I didn't see any infomation on what to do if it doesn't go through. Flashed the radio, then went to the hboot. Received image update failed error message. Long story short, I experienced what having a brick feels like.
The reason I am explaining all of this is for people to learn from my mistakes and to get some clarification on what I am writing next.
I got the phone exchanged (only had it for a day) and began researching more to find out what I did wrong. I found this crypysmoker's thread.
And then I found the message:
READ READ READ. DO NOT download the SAPPimg.zip file it says on that page.
Get the top fixed SPL file 2010 from here
Click to expand...
Click to collapse
In my research, I discovered that the mytouch 1.2 has several spl's that have been hacked and not. I figured out that the file on theunlockr wasn't the fixed spl and that is mainly the reason for my brick and the frozen HTC Magic screen.
I want to enjoy the gifts that CM has to offer. Being stuck on normal 1.6 is well saddening to say the least. But I am worried about flashing the wrong spl and have the situation repeat again as I would figure I would be screwed this time around and wouldn't be able to get it replaced.
Can anyone provide more information about this? Can I flash the Engineerings SPL v1.33.2010 and not run into the same problem? I understand that there isn't a 100% certainty of working. Most of my searches show that more people have bricked this phone than any other.
Thanks in advance and sorry for the length.
Phone Info:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Well, I did it all again. Redownloaded all the files. Setup a new goldcard. This time I let it sit for over 45 mins. Never got past the HTC Magic Screen. Adb doesn't see it nor does the light come on to say that it is charging. Which would show me that it has indeed locked up.
Anyways it shut off on its own since it wasn't getting usb power and I guess the battery died. I'm still able to reboot back to hboot. I attempted to reflash the sappimg.zip file. Right now its going on 10 mins sitting on the
[1] SYSTEM - Unzipping
What I will add tho is that my info changed.
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I tried reformatting the SD and recreated the Gold Card as I noticed some of the Hex changed but still getting the same issue.
the phone won't run anything other than spl 1.33.0013 and radio 2.22.23....w/e x)
Get the sappimg you had before and flash it in hboot mode which should give you spl 1.33.0013. In fastboot mode, flash your spl to 1.33.2010again, then flash radio 2.22.23 or w/e, then flash amon ra recovery, then flash stock spl (1.33.0013).
All the files you need are here: http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The reason it wont boot up is because you have engineering spl and the wrong radio on. Again, it will only boot up with the stock radio and spl~!!!
hacker01 said:
the phone won't run anything other than spl 1.33.0013 and radio 2.22.23....w/e x)
Get the sappimg you had before and flash it in hboot mode which should give you spl 1.33.0013. In fastboot mode, flash your spl to 1.33.2010again, then flash radio 2.22.23 or w/e, then flash amon ra recovery, then flash stock spl (1.33.0013).
All the files you need are here: http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
The reason it wont boot up is because you have engineering spl and the wrong radio on. Again, it will only boot up with the stock radio and spl~!!!
Click to expand...
Click to collapse
I don't know where I would find the original stock sappimg. The one that is on the website is the sappimg that needs to go on when you are stock at the beginning.
Also my HBoot doesn't seem to be unzipping cause that is where it gets stuck. Is there a way to do it all from fastboot? Since I am currently stuck in the 2010 spl, can I flash the stock spl through fastboot without the radio?
I just don't get why I am having this problem. I followed that website to the letter. And I know that at this point if I attempt to flash the radio back to stock, I will completely brick it.
Since you dont want to flash the radio, flash the amon ra recovery FIRST. Then flash the stock spl. If it doesn't boot up, then you'll need to get the engineering spl back on again and flash stock radio (the one in the link).
hacker01 said:
Since you dont want to flash the radio, flash the amon ra recovery FIRST. Then flash the stock spl. If it doesn't boot up, then you'll need to get the engineering spl back on again and flash stock radio (the one in the link).
Click to expand...
Click to collapse
I couldn't flash the recovery in fastboot.
Tried Fastboot boot recovery recovery.img
Got an error message Recovery not found.
Wasn't sure if I wanted to try flashing the recovery before finding out if it can brick it. Like the original post says, my first MT1.2 I flash the spl from unlockr screen locked up but could get into fastboot so flashed the radio and then tried the spl like the directions say and I completely bricked it.
I don't want to make the same mistake twice.
Unfortunately, there's a chance of bricking every time you flash anything.
Anyways, this might be redundant but is the recovery imaged named recovery.img? Like you actually renamed it? If not, you'll have to type out the exact name.
hacker01 said:
Unfortunately, there's a chance of bricking every time you flash anything.
Anyways, this might be redundant but is the recovery imaged named recovery.img? Like you actually renamed it? If not, you'll have to type out the exact name.
Click to expand...
Click to collapse
No it wasn't named recovery.img, was just using it to save time. I did spell out the recovery's full name.
When you enter the command "fastboot devices" it shows a serial number right? And the recovery image is in your tools folder of your androidsdk folder?
Sorry for the redundant questions, we're just going back to the basics really quick right now.
hacker01 said:
When you enter the command "fastboot devices" it shows a serial number right? And the recovery image is in your tools folder of your androidsdk folder?
Sorry for the redundant questions, we're just going back to the basics really quick right now.
Click to expand...
Click to collapse
yup and yup
I see the problem. Your mobo is recognized as 32a S off H. You're recovery image is probably the G version. What you could do is download the H version and flash it although i doubt your phone will still boot up at that point.
You could try flashing the H version of amon ra's recovery image and afterwards, see if it boots up. Then, if it doesnt boot up, flash stock spl (1.33.0013) and see if it boots up.
I'm pretty sure your phone will end up not booting up and you'll eventually have to flash stock radio as well and then flash the G version recovery back on.
The reason your mobo is recognized as the H version and not the G version is because of the radio.
EDIT: I just realized I made a mistake. I meant to say the mobo is recognized as the H version because of the SPL, not the radio.
EpikFail said:
I couldn't flash the recovery in fastboot.
Tried Fastboot boot recovery recovery.img
Got an error message Recovery not found.
Wasn't sure if I wanted to try flashing the recovery before finding out if it can brick it. Like the original post says, my first MT1.2 I flash the spl from unlockr screen locked up but could get into fastboot so flashed the radio and then tried the spl like the directions say and I completely bricked it.
I don't want to make the same mistake twice.
Click to expand...
Click to collapse
Heres your problem. If recovery is not found then you didnt put it in your Androidsdk\tools folder did you? or did you rename it? Oooorr, you put it in there while adb was running and didnt restart it to see the file itself
crypysmoker said:
Heres your problem. If recovery is not found then you didnt put it in your Androidsdk\tools folder did you? or did you rename it? Oooorr, you put it in there while adb was running and didnt restart it to see the file itself
Click to expand...
Click to collapse
He already said that its in the tools folder.
hacker01 said:
I see the problem. Your mobo is recognized as 32a S off H. You're recovery image is probably the G version. What you could do is download the H version and flash it although i doubt your phone will still boot up at that point.
You could try flashing the H version of amon ra's recovery image and afterwards, see if it boots up. Then, if it doesnt boot up, flash stock spl (1.33.0013) and see if it boots up.
I'm pretty sure your phone will end up not booting up and you'll eventually have to flash stock radio as well and then flash the G version recovery back on.
The reason your mobo is recognized as the H version and not the G version is because of the radio.
Click to expand...
Click to collapse
Sorry for the last reply, I do all my hacking at work so my adb setup is there. So I did this.
fastboot devices
XXXXXXXXX fastboot
fastboot boot recovery recovery-RA-sapphire-c1.6.2G.img
cannot load 'recovery'
fastboot flash recovery recovery-RA-sapphire-c1.6.2G.img
send OKAY
write OKAY
Click to expand...
Click to collapse
Holding home+power, wouldn't boot into recovery. Seems to still be stuck. Went back to fastboot
fastboot flash hboot hboot.nb0
send OKAY
write OKAY
Click to expand...
Click to collapse
Still same thing so back to fastboot I go
fastboot radio radio.img
sending 'radio' <21504 KB>... FAILED <remote: not allowed>
Click to expand...
Click to collapse
My phone now reads
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I can tell that the radio is still the old one. It seems the spl worked and put it back to stock but still no recovery and I guess I can't fastboot anything either.
So I assume I need to flash back eng spl and see if it will boot, right?
Even as the recovery and spl are compatible, you see that it still won't boot up. What you gotta do now is flash the engineering spl and do the same as before except flash the radio as well.
In the end, your mytouch should read:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
The same as stock before EXCEPT this time, you'll have amon ra's recovery. That's when you know you're done. Just follow the guide from before and you'll be fine.
hacker01 said:
Even as the recovery and spl are compatible, you see that it still won't boot up. What you gotta do now is flash the engineering spl and do the same as before except flash the radio as well.
In the end, your mytouch should read:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
The same as stock before EXCEPT this time, you'll have amon ra's recovery. That's when you know you're done. Just follow the guide from before and you'll be fine.
Click to expand...
Click to collapse
So I flashed the eng spl again. Still wouldn't boot. Got the same SAPPHIRE UNKNOWN 32A ENG S-OFF H
did:
fastboot flash recovery recovery-RA-sapphire-v1.6.2G.img
send OKAY
write OKAY
fastboot boot recovery
cannot load 'recovery'
Click to expand...
Click to collapse
I'm still worried about flashing the radio....
but I should fastboot the radio and then the hboot.nb0, right?
Solved
I would like to start out by saying, Thank you so much hacker01 for your help! You don't know how much I appreciate everything.
I was able to get it back working and fully running CM5.0.7
After I reloaded the eng spl, like I said, I was running into the same problems. Wouldn't boot, goes into fastboot, etc.
I grabbed the stock radio and spl NOT from the unlockr page this time but from the link on crypysmoker's thread.
fastboot flash radio radio.img
fastboot flash hboot hboot_7201A_1.33.0013G_091021.nbo
fastboot flash recovery recovery-RA-sapphire-v1.5.2G.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Just like it said and sure enough got into recovery! Flashed a rom and it booted up.
I know this technically isn't solved cause I really don't know what went wrong in the first place. I can ensure you that I can follow directions and did. The only thing that makes any sense is the files on theunlockr's website is bad. Guess we can just chalk it up to bad luck.
But if anyone wants to root their mytouch 1.2, crypysmoker's thread is definitely the way to go.
Thank you again hacker01! I hope I can pay it forward.
You did it right, it's just that any radio that is not 2.22.23 won't work with the mt3g 1.2/Fender LE right now. And no problem! Glad you got it up and running. Enjoy your mytouch
Mod. edit: not dev related, moved to general
Please, help!
I have the exact same problem: I was following the Unlockr's instructions, made the goldcard, flashed the sappimg without getting any errors, and now the phone is stuck on the htc magic boot screen. I am not experienced and now I am scared sh**less, because the phone belongs to my girlfriend Please, give me step-by-step instructions how to fix it, because I really dont want to improvise. The phone is MyTouch 1.2...
Thank you in advance!!!
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17

Help! "Semi-" bricked. FASTBOOT gives Signature errors

Hi all,
Hopefully someone knows the answer to this one. I am completely screwed here and need some help.
I rooted my MyTouch 3G 3.5mm (32a) with no problems and tried several ROMS. So, I was going to try a ROM with a required radio and tried following this http://forum.xda-developers.com/showthread.php?t=605239 to do so.
It seemed ok, but then all heck broke loose.
Now I am stuck with the following:
HBOOT-1.33.2010
CPLD-13
RADIO-3.22.20.17
And nothing else.
I tried to unroot it and everything I could think of. That was probably a mistake (#2) because that replaced the recovery. So, now I can FASTBOOT and that's it.
If I try to replace the SPL or recovery or anything, I get a "Signature Verify Fail" from ADB and if I try using the SD card, it loads the img, checks it, and then does nothing.
Any ideas?
Your SPL is perfected so you cannot fastboot. Do you have a recovery that you can boot into?
As far as your fast boot problem goes look at this :
http://forum.xda-developers.com/showthread.php?t=548218
Click to expand...
Click to collapse
Does that translate into "I am screwed"?
can you enter any kind of boot, try volume + power, home + power, if you can, then use droid explorer to reflash the system
Do you a recovery you can boot into?
No recovery. :-(
I can get into the system via down vol+Power and Back+Power, but that's it.
I'll see if Droid Explorer can see anything.
From what I see, Droid Explorer requires the system be booted.
TheForgotten said:
Your SPL is perfected so you cannot fastboot. Do you have a recovery that you can boot into?
As far as your fast boot problem goes look at this :
Click to expand...
Click to collapse
Will I tried that to see if it would work. It actually gives me the option to start the flash.
The first section to flash is SYSTEM. It starts unzipping and stops right there and hangs.
Oh, I am not sure if this changes things, but the entire top data when at FASTBOOT is:
SAPPHIRE UNKNOWN 32A ENG S-ON H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
Jun 2 2009, 17:27:03
Any ideas or advice?
Have you tried entering recovery through AndroidSDK?
If you mean
"fastboot boot recovery.img", yeah. Is there a good recovery img I should use?
It doesn't seem to do anything when I try it. No error. It appears to work, but the phone does nothing.
Armon_Ra's recovery Heres a link: http://forum.xda-developers.com/showthread.php?t=530492. You have a 3.22 version radio so dont use the Hero recovery like he tells you even though you have a 32a (hero version is meant for 6.35 RaDIO)

Ok... kinda stuck in vodafone limbo [myTouch 3g w/ headphone jack]

Alright, newb here.
Now that that is out of the way, let me get to the issue.
History: I was following a howto on theunlockr.com (or however it's spelled) for rooting my myTouch 3g w/ 3.5mm headphone jack. Created goldcard, put sappimg on it, booted phone into bootloader, nothing, didn't recognize the image file. Thinking that the file was bad, I downloaded another sappimg.zip file (which I realize now was a bad mistake). After realizing that the card needed to be empty (no files other than sappimg.zip), put JUST sappimg.zip on goldcard and it worked. It uploaded the zip to memory and flashed. Then it rebooted and was stuck at a Vodafone logo. No bootup, just hangs at logo (I've left it at that for a good 10 minutes, still nothing). I can't flash from fastboot, as the SPL does signature checking. I've tried fastbooting into a recovery image, but the four I've tried so far, won't get past the three droids skating logo (and that's if I use fastboot to erase system, boot, userdata, and cache, otherwise, they'll hang at the Vodafone logo too). I've also wiped every partition on the flash other than the bootloader.
Yesterday, I've even tried to run a couple of RUU's for the thing. I had a friend try all three T-Mobile RUU's for the myTouch (from the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread), all failed with some version (Different failures for each though).
Oh, also, I can't do the goldcard trick anymore, because when it tries to flash the rom, the SPL hangs on the system partition.
So, gentlemen, I do believe I'm screwed.
Any help towards getting it unscrewed (even back to stock) would be greatly appreciated.
Details:
Bootloader screen banner:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
May 8 2009, 21:02:32
Recoveries tried:
recovery-RAv1.0H
recovery-RA-hero-v1.6.2
recovery-RA-magic-v1.3.2H
recovery-RA-sapphire-v1.7.0G
recovery-RA-sapphire-v1.7.0H
Nothing?
So, nothing???
Nevermind.
Sent from my HTC Magic using XDA App
ZeroSigea said:
So, nothing???
Click to expand...
Click to collapse
I also have a MT3G 1.2 with the symptoms you describe - hangs on unzipping the system image in sappimg.zip (2.10.531.3) and (2.10.531.4). Don't even think about trying to flash sappimg.nbh (1.94.531.1) - that got me a brick semi-recoverable via JTAG.
I have also seen the Fail-PU message appear when it tries to flash the system partition (when radio 2.22.23.02 was installed).
I found that you can successfully flash sappimg.zip (2.53.707.2 including eng spl 1.33.2010), but fastboot is useless since you get the (remote: signature verify fail) message. Needless to say, this rom doesn't boot successfully.
In addition to the symptoms you describe, the USB is also broken on my MT3G 1.2, so I would need a solution that doesn't use fastboot.
Has anybody else experienced this problem or something similar with their MT3G 1.2? I would like to collect as much information as I can about this problem. I have so far been unsuccessful in finding a solution
I have working JTAG on my MT3G 1.2, so I can easily softboot any SPL. See wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic for more details.
I had an idea to edit the SPL so that it skips the signature check on any sappimg.zip file you give it, and easily flash a custom sappimg.zip. Another idea I had was to get it to skip checking the main version on any sappimg.zip file you give it.
Does anybody have any ARMv6 (ARM11) disassembly experience? I could only ever get arm-none-eabi-objdump to disassemble the SPL as a ARMv5 binary...
Does anybody have any idea what I'm talking about? Am I crazy?
stewdk said:
I have working JTAG on my MT3G 1.2, so I can easily softboot any SPL. See wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic for more details.
I had an idea to edit the SPL so that it skips the signature check on any sappimg.zip file you give it, and easily flash a custom sappimg.zip. Another idea I had was to get it to skip checking the main version on any sappimg.zip file you give it.
Does anybody have any ARMv6 (ARM11) disassembly experience? I could only ever get arm-none-eabi-objdump to disassemble the SPL as a ARMv5 binary...
Does anybody have any idea what I'm talking about? Am I crazy?
Click to expand...
Click to collapse
I have some ideas that I would like to bounce off you...and I would be willing to provide a phone to try them on...then we could have something to offer because this seems to be a big problem for this phone. Please PM me.
Dude, the post is from September 2010... :0)
Good luck..
mumilover said:
Dude, the post is from September 2010... :0)
Good luck..
Click to expand...
Click to collapse
It may be an old post, but I'm still having the problem I described above
My phone is sitting right here collecting dust, JTAG still hooked up and everything.
jonk26.2, I got your PM. I'm interested.
I just need to get a working openocd installation up and running again - shouldn't take too long.
EDIT: I mean I'm interested in trying your ideas. No need to send me a phone.
Let me tell you where I am and what I am thinking.
I bought a 3.5mm phone on ebay that had this issue...stuck on fastboot screen. I could get into USB fastboot just fine...and could try the goldcard root process just fine...but had the same freeze on unzipping files that everybody else had. I had the brilliant idea that I could use fastboot to erase the bad files so it could unzip files...and in my haste I erased EVERYTHING...no fastboot no nothing...dead. Then I started looking around the site for JTAG and found your post and then I thought...maybe this is the way to start...absolutely wipe the slate clean and start over.
Anyway...my mobo is dead on this phone and I would like to try to fix it if you are game.
jonk26.2 said:
and in my haste I erased EVERYTHING...
Click to expand...
Click to collapse
If you erased the radio, then I'm afraid that even the current JTAG procedure won't help you much... Try seeing if blue LED light mode works - if it does, then you might still have hope. This is discussed in the JTAG thread http://forum.xda-developers.com/showthread.php?t=591048 and also at http://wiki.cyanogenmod.com/index.php?title=JTAG_for_Dream/Magic
I know the JTAG thread can be a bear to sift through, but it has a lot of good information, including what kind of equipment they use (I'm using a Stellaris EKC-LM3S6965 eval kit which doubles as a USB-serial adapter if you program it right).
Remember that the MT3G 1.2 3.5mm jack / Fender LE won't boot anything without the stock SPL and a known compatible radio (2.22.23.02 is one).
Yes...Blue LED...nothing else.
jonk26.2 said:
Yes...Blue LED...nothing else.
Click to expand...
Click to collapse
Then in theory un-bricking is possible via jtag and serial cable.
I'm not sure about this, but if your phone is in a condition like mine, then JTAG may only be able to bring it back to the limbo state we've been seeing. Symptoms of this are: 1. seeing something like fastboot remote signature verify fail when fastboot worked (even with an engineering SPL) and 2. stuck at unzipping the system image or getting Fail-PU when installing a sappimg.zip. And as far as I know this only applies to the MT3G 1.2 3.5mm jack.
Wow...
Haven't been on in a while and I come back and see that the thread did blossom into a full discussion. Nice. Sorry to leave y'all out in the dark for so long, but I've been busy (and distracted).
So, my solution was to get it replaced. Cheap, I know, but something had to be done. So, I got another MyTouch 3G and when I was feeling brave again, I tried a different route and went with Universal Androot to root the stock ROM in place and use ClockworkMod to flash CM6 onto the device. Awesome, it worked. So we (me and the girlfriend) enjoyed our MyTouch's until we got fed up with T-Mobile's service (crappy signal, where I live). Switched to AT&T and got a HTC Aria, which I suppose is the MyTouch's cousin.
I feel hopeless
I am also suffering the same problem.
I can access fastboot but I can do nothing [Perfect SPL].
I have created a working gold card but all I'm seeing is the frozen system extraction.
tried almost any possible howto's I can find on the net but to no avail.
due to my experiment on flashing sappimg.zip, I seem have a mutated radio/spl combo!
phone info(s):
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0000 (SAPP31000)
CPLD-13
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
Phone CID: T-MOB010E
Phone version-main: 2.53.707.2
having the same problem
I have tried every combination of firmwares known to man. I have got several to begin flashing, but all stick on the unzipping system. I messed it up by originally following another post for rooting the phone and didnt realize that this my touch 1.2 is special. Apparently the firmware I flashed it with is a 32A firmware and the spl and radio are no good for this phone. So now nothing will flash. Probably have to Jtag it...
I have the same problem.
Using eng spl 1.33.2009 and 1.33.2005 through JTAG on MT3G 1.2,
At first, if I used eng spl 1.33.2009, fastboot flash [partition] [partition.img]
I got: FAILED (remote: image update error).
After that, I switched to eng spl 1.33.2005, somehow I could use fastboot flash hboot boot.nb0 from T-Mobile_US_2.10.531.4. But I only flashed that and rebooted the system to see what happened. Then I cannot do it again.
(Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
Now using eng spl 1.33.2005, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash radio.img.
using eng spl 1.33.2009, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash hboot, boot, radio.img. splash, but stuck at sytem image.
Using eng spl 1.33.2009 through JTAG on MT3G 1.2,
1. Stuck at unzipping the system image.
Or
2. (Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
When the system was stucked at unzipping the system image, the serial cable continues to give message:
[MDDI_HW_ERR] mddi_queue_image timeout
[MDDI_HW_ERR] mddi_queue_image timeout
Something is broken.
I can only flash sappimg.zip with eng 1.33.2010, but it doesn't a working system.
Can anyone shine light on this one?
hubh98 said:
I have the same problem.
Using eng spl 1.33.2009 and 1.33.2005 through JTAG on MT3G 1.2,
At first, if I used eng spl 1.33.2009, fastboot flash [partition] [partition.img]
I got: FAILED (remote: image update error).
After that, I switched to eng spl 1.33.2005, somehow I could use fastboot flash hboot boot.nb0 from T-Mobile_US_2.10.531.4. But I only flashed that and rebooted the system to see what happened. Then I cannot do it again.
(Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
Now using eng spl 1.33.2005, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash radio.img.
using eng spl 1.33.2009, fastboot flash zip T-Mobile_US_2.10.531.4.zip, it only can flash hboot, boot, radio.img. splash, but stuck at sytem image.
Using eng spl 1.33.2009 through JTAG on MT3G 1.2,
1. Stuck at unzipping the system image.
Or
2. (Remote) signature verify fail, when using
fastboot flash [partition] [partition.img]
When the system was stucked at unzipping the system image, the serial cable continues to give message:
[MDDI_HW_ERR] mddi_queue_image timeout
[MDDI_HW_ERR] mddi_queue_image timeout
Something is broken.
I can only flash sappimg.zip with eng 1.33.2010, but it doesn't a working system.
Can anyone shine light on this one?
Click to expand...
Click to collapse
man, if this IS thru JTAG..., I am losing hope
I still have hope.
I was able to bring it back to work once.
After fastboot flash zip T-Mobile_US_2.10.531.4.zip, stucked at unzipping the system image, I took off the battery and was able to flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully. And system was working but SD card reader was disabled in android system, so I read that I need to root the system, and I followed the
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
and installed the sappimg.zip with (eng spl 2010). Then eng spl 2010 flashed sappimg.zip (T-Mobile_US_2.10.531.4) and stuck at unzipping the system image. [However, it was worked at the very beginning when the MT3G 1.2 with froyo,~~~ Wrong! I didn't use the SAPPIMG with eng spl 2010 at that time, and I only used the universal androot to root the phone~~~ and before I bricked the phone when I used RUU to downgraded it back to Donut.~~This is true. ]
This can explain why I can flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully at first place. So the sappimg.zip with (eng spl 2010) is halmful, because it updates the main version.
When I rebooted the system and used the stock spl 1.33.0013G to reflash (T-Mobile_US_2.10.531.4), I have the "main version is older" error.
It looks like each time it becomes worse, there are some kind of watchdog programs in the system?
Because of the hybrid nature of the MT3G 1.2 (32A hardware/32B ROM), the partitions probably messed up, because I saw "partition update failed".
I just cannot repeat the process, when I jtag the phone,
I also saw
[ERR] partition_read::Failed to read page 19072 or it is empty, when soft boot the system as
http://forum.xda-developers.com/showpost.php?p=5715534&postcount=214.
hubh98 said:
I still have hope.
I was able to bring it back to work once.
After fastboot flash zip T-Mobile_US_2.10.531.4.zip, stucked at unzipping the system image, I took off the battery and was able to flash sappimg.zip (T-Mobile_US_2.10.531.4) on SD card through hboot (stock 1.33.0013G) successfully. And system was working but SD card reader was disabled in android system, so I read that I need to root the system, and I followed the
http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
and installed the sappimg.zip with (eng spl 2010). Then eng spl 2010 flashed sappimg.zip (T-Mobile_US_2.10.531.4) and stuck at unzipping the system image. [However, it was worked at the very beginning when the MT3G 1.2 with froyo, and before I bricked the phone when I used RUU to downgraded it back to Donut.]
When I rebooted the system and used the stock spl 1.33.0013G to reflash (T-Mobile_US_2.10.531.4), I have the "main version is older" error.
It looks like each time it becomes worse, there are some kind of watchdog programs in the system?
Because of the hybrid nature of the MT3G 1.2 (32A hardware/32B ROM), the partitions probably messed up, because I saw "partition update failed".
I just cannot repeat the process, when I jtag the phone,
I also saw
[ERR] partition_read::Failed to read page 19072 or it is empty, when soft boot the system as
http://forum.xda-developers.com/showpost.php?p=5715534&postcount=214.
Click to expand...
Click to collapse
ok bro, I wish you luck on unbricking your phone, let us know if you succeeded!
Can any one help me check the main version of the original MT3G 1.2 before using the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2)?
fastboot getvar version-main
Even after I flashed back to T-Mobile_US_2.10.531.4 (stopped at system), the main version is still 2.53.707.2. I think the main version of T-Mobile_US_2.10.531.4
is 2.10.531.4. So the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2) is potentially harmful at least for some MT3G 1.2.
hubh98 said:
Can any one help me check the main version of the original MT3G 1.2 before using the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2)?
fastboot getvar version-main
Even after I flashed back to T-Mobile_US_2.10.531.4 (stopped at system), the main version is still 2.53.707.2. I think the main version of T-Mobile_US_2.10.531.4
is 2.10.531.4. So the SAPPIMG.ZIP with eng spl 2010 (main version 2.53.707.2) is potentially harmful at least for some MT3G 1.2.
Click to expand...
Click to collapse
I don't hold the unit now, but I hope someone here could lend a hand on this

[Q] Cant boot into recovery.

Hello, have a mytouch 3g 1.2 seems to be semi bricked, cant boot into recovery, or boot into actual rom, pretty much just hboot and fastboot. At the moment it's flashed with:
Sapphire Unknown 32A ENG S-ON H
HBOOT-1.33.2010 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I've been searching the forums for hours and cant seem to fix this. When I try and revert back to the stock sappimg or any sappimg for that matter it generally gets stuck at the system part where it's unzipping.
When I try and fastboot boot a recovery it just hangs as if i was trying to enter it through a normal method, Im assuming the problem has something to do with the fact that it's S-ON and not S-OFF, but i dont know how to remedy that without being able to get into the OS or Recovery.
Also when i do a fastboot getvar version-main it's 2.53.707.2, not sure if that makes any difference.
Any help would be much appreciated, thanks in advance.
i dont know
What ever you do, don't flash anything before we tell you...
Read this thread: http://forum.xda-developers.com/showthread.php?t=734617
Continue from step 4 i believe... or wait until DonJuan692006 comes to the rescue :0)
Thanks for the response.
When I attempt to flash the radio.img, it sends it, says OKAY then as it starts writing it gets to (bootloader) signature checking....FAILED (remote: signature verify fail).
Any other ideas?
You have s-on. You need to switch that to off.
Try to run this command in fastboot mode:
Code:
fastboot oem eraseconfig
It should set you back to s-off and then you can flash the radio.
Thanks man, you are a huge help, was able to get everything up and running perfectly!
Glad it worked out :0)
Guess I'm too late to come to the rescue, lol. Just bought my first house and have been moving and such all week.

Categories

Resources