i rooted my mytouch and was trying to revert to the 32b board and preformed all of these commands, all of which were successful,
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.2.0G.img
but now my phone is stuck at the red vodaphone screen, please if anyone can help it would be greatly appreciated.
how long has it been stuck at that screen for? did u keep it on for a few minutes? try taking out the battery for a few minutes, then re inserting it.
run fastboot into recovery on computer and it will wait for device. plug phone in without battery then put battery in phone and it should throw phone into recovery .
alrite i was able to get into fastboot an i reflashed sappimg, hopefully all will be good i think i'll just stick with 32a until i figure out what i did wrong, thanx all
Hang on, Firstly you said reverting back to 32B. Then you said you'll stick to 32A? Which do you have? You run a risk of bricking the phone putting the wrong firmware on it.
I have a t-mobile mytouch, when i rooted it the board ends up being 32a (im pretty sure everybodys is like that) so i started to follow the "daredevil steps" to change the board to 32b but that created the stuck vodafone screen
adelco93 said:
I have a t-mobile mytouch, when i rooted it the board ends up being 32a (im pretty sure everybodys is like that) so i started to follow the "daredevil steps" to change the board to 32b but that created the stuck vodafone screen
Click to expand...
Click to collapse
Yeah I think it was stuck because you need to install a ROM first.
MOD EDIT
Moved to general forum as not related to android development
Breakthecycle2 said:
Yeah I think it was stuck because you need to install a ROM first.
Click to expand...
Click to collapse
Is there any solution?
robotician said:
Is there any solution?
Click to expand...
Click to collapse
ya bro. he didnt flash a 32b rom. thats all that was left. when you dont have a rom and revert back it sits at the splash because the phone is looking at you or whoever saying "ummmm ya i dont know what to do now?? rom???" lol. its an easy fix. have fun all!!!! yeah!!!!!!!!!!!!!!!!!!!!!!!!!!
One problem is that you can not see the red text "Recovery Mode" on the red background. Someone had the same problem on another forum.
Slick_42 said:
One problem is that you can not see the red text "Recovery Mode" on the red background. Someone had the same problem on another forum.
Click to expand...
Click to collapse
Can you provide a bit more info on this? This might lead to somewhere. I read some folks have red background with blur logo (maybe mean the recover text is hidden there)? I will be happy if it is in deed in recovery mode with red background. However, my bricked phone has red background with clear logo.
I have this from a german site
http://www.android-hilfe.de/vodafone-htc-magic-forum/3419-nach-flash-handy-startet-nicht-mehr-2.html
roughly translated: he thought that he stuck on the start screen but actually was in fastboot mode. he just couldn't see it trough the red Vodaphone screen. He pressed home+power and could load the backup from th PC into the phone.
Related
Heloo, while y was trying to update my perfect spl, i meka a mistake and put inside spl for 32A instead o B
now, when I press power on button, it makes a little vibration and after that HTC MAGIC appears on the screen and nothin happens.
I have try to make fast boot commands, when starting with back and power, but computer foesn't recognize it.
Any suggestions??
the problem is the first splash is changed and is not vodafone's one, and I cannot access to it
What spl did you get? If you got it from Amon_Ra, his spl's work for both 32A and 32B. Are you sure you didn't flash a 32B radio?
What commands did you use?
recovery-RA-magic-v1.3.2H.img I use this one and it works, but on the next step, when i was trying to put
update.Engineering-SPL-HBOOT-1.33.2010-signed
using the recovery, it ask me for press 2 keys for rebooting. I read that in a wrong way and I press menu and use the menu for reboot the magic. After that it hangs on the first screen and I cannot use the fastboot commands, trying to boot with back+power.
I read it can be done if the first splash freezes but it is not my case.
Thanks a lot for your reply
Hmm, try installing HTC sync with the drivers again.
And download a recovery rom 1.4 with nandroid backup and download that into your fastboot.
No way to do a fastboot or recovery so I think that we can't download into our fastboot...
I have same problem and reading in the forum I think that we have Total bricked phone.
I have tried this solution http://forum.xda-developers.com/showthread.php?t=571457 but the cmd still "waiting for device" so i can't acces to my magic with my pc...
I hope that i am wrong
yes, I have try what people says on that post and waiting...
is not possible to make anything to allow the computer to recognize the device??
I just rooted my Mytouch a couple days ago and everything worked perfect and i did it without bricking my phone. I was trying to get the supercsdiv4 rom, but i needed to flash the lateset radio and heres where the problem started. the radio tried to flash was 2.22.23.02. I used the recovery image to flash it and then when i rebooted the phone it stayed stuck at the splash screen and i cant get into fastboot or recovery anymore. it just boot to the splash screen and stays there. I know i cant get my phone back but i want to know what i did wrong so that i dont ever do it again. maybe it was because the radio i had was a 32a radio and this radio i tried to flash might have been 32b but im not sure why that wouldn't work if my phone is 32b
here was my system
pvt 32b
Hboot 1.33.2005
radio 3.22.20.17
have you tried taking the battery out for a bit.. relax a while, then put it back in and try to get into recovery mode (home and power)
this actually happened yesterday and my phone was off the whole time so it has had plenty of time to rest. My phone is truly bricked
well im sorry to hear that, but i have no idea what you did wrong, unless you did flash a 32a over a 32b or the other way around, im sure that could really mess up the phone.
may be a useless idea but have you tried a hard reset
1. With the phone turned off, press and hold the HOME and BACK buttons.
2. Briefly press the END CALL/POWER button while continuing to press the HOME and BACK buttons.
3. When you see the screen with the 3 Android
images, release the HOME and BACK buttons, and then press the TRACKBALL.
i have no idea if it will do anything but might as well explore EVERYTHING.
Similar Problem (Partial Brick?)
Not to take anything away from clint1225 but
I have a similar problem and didn't want to start another thread.
I tried unrooting my devices using the method
described at theUnlockr.com. Everything was fine up until I tried using
their sappimg file (said it worked for all old magics).
At the hboot stage, it found the sappimg but the update failed.
However, the magic now says:
SPL-1.33.0006 (SAP50000)
Radio- 2.22.19.261
Ship S-On G.
It's a 32A version.
I had an engineering spl and 6.35xx radio before I attempted to unroot.
Oh I'm not able to access recovery but I can access
fastboot (computer can't find it though under "fastboot devices")
Other than that, it's stuck at the first splash screen.
Any advice/tips?
Sorry for the long post and thank you.
Good luck to you too, clint1225!
UPDATE *Similar Problem (Partial Brick?)*
In the adb, the serial number
of the htc magic is coming
up under "fastboot devices".
However, if I try to
flash a recovery for example, the adb
returns "remote access not allowed".
I've read about the gold card method
but my phone won't boot up properly
(stuck at splash screen) and I can't
access recovery. Only fastboot seems to be
working.
Any help is greatly appreciated.
Thanks!
Take it for what it's worth coming from a newb. But from my understanding if you can reach your phone with Fastboot your a NOT bricked. But this is what I have heard here on XDA, I haven't proven this myself.
Check around and hopefully with fastboot you can get your phone back. Good luck.
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Update *Similar Problem (Partial Brick?)*...again.
MasterColdSoul and koolpre,
Thanks for the tips and luck!
I figured it wasn't a total brick so I searched
the whole day on google and xda.
What I can tell you is that I now have a functional phone.
I used the rogers "mandatory" update (2 sappimgs) to
get my phone (rogers 32a) working again (boots fully).
However, I now have the SPL 1.76.0010 which means
I've lost root functionality and it's harder to get root.
But I could use the phone to make a gold card and get root again.
Boy I'm glad this worked! I should have learned my lesson
but I will probably try to root, hehe!
Thanks to google search and xda community!
koolpre said:
I did the exact same thing a few weeks back. I flashed a 3.22 radio over my 2.22 radio, thinking it's an upgrade but after it reboots, it wont get past the logo screen. I spent the whole day trying to find ways to recover it but cannot find any. Thank god I have warrenty on it so I went to the Tmobile store, told them I updated it and when it restart, it got stuck on the logo screen. They gave me a new phone and told me dont f-up this one. Now I'm afraid of updating my phone to the 6.something radio.
Click to expand...
Click to collapse
just because the radio starts with bigger numbers doesn't make it an update. 3.22 was the old radio and 2.33.23.02 is the latest radio so you were actually downgrading your radio and thats why your phone brick. Just letting you know because you seem to be under the wrong impression. Dont make that mistake again. just do a little research to find the latest radio.
my phone wont come off the the spalsh screen, even when i try to bootinto recovery or fastboost its just stuff on the green screen and the pixels are funny for some reason. i dont know exactly what i did but i tried to flash a new radio and spl is there any hope?
itsomaryo said:
my phone wont come off the the spalsh screen, even when i try to bootinto recovery or fastboost its just stuff on the green screen and the pixels are funny for some reason. i dont know exactly what i did but i tried to flash a new radio and spl is there any hope?
Click to expand...
Click to collapse
You can't get into bootloader at all?
If you can't get into bootloader or recovery then yes... you are bricked.
What did you do?
im not trying to hijack this thread but i didnt want to create a duplicate. mine also gets stuck on the splash screen. It wont load my recovery files and the adb interface on my computer wont work. im at a loss. Previously it was rooted with cyanogen mod 6.0
bassdroid said:
im not trying to hijack this thread but i didnt want to create a duplicate. mine also gets stuck on the splash screen. It wont load my recovery files and the adb interface on my computer wont work. im at a loss. Previously it was rooted with cyanogen mod 6.0
Click to expand...
Click to collapse
can you get in to the SPL? (vol - and power)
AdrianK said:
can you get in to the SPL? (vol - and power)
Click to expand...
Click to collapse
yes. i can do vol- and power and the white screen comes up with radio and spl showing.
I don't know what did but I fixed it. All I did was keep trying to flash the newest cyanogen rom and I wiped all caches and somehow it finally took I am sending from it now. But my hd2 will still remain primary phone
Sent from my HTC Magic using XDA App
I did it through the h boot and installed zip from sd card
Sent from my HTC Magic using XDA App
How did you do it?
bassdroid said:
I did it through the h boot and installed zip from sd card
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Hello,
How did you do it? I cannot pass the splash screen but I can enter the FASTBOOT menus with the 3 skaters
Thanks
All I did was wrote every cache and try installing a fresh rom a few times and somehow it worked. I was kinda surprised myself.
Sent from my Nexus One using XDA App
my solution on 10 second your magic will be alive (100% PROVEN & TESTED)
if u have problem with your magic (stuck on logo screen) maybe my solution it's work...
pls see this video make sure you condition same like this
youtube.com/watch?v=hPoxMzm0MVU&hd=1
Pls follow my sollution (it work on my magic) for fix your magic first u don't panic because your magic will be have the recovery on the internal disk. u should be only recovery rebort your magic to earlier condition before your magic stuck on logo boot screen.
1.put off your magic battery (5 second) then put on again.
2.pls hold home button and then hold off button (power on) "until u see the screen cyanogen recovery bootloader" and then it's automaticly booting and pls chooses rebort recovery then recovery will started.
3.after that your magic freezed on recovery clockworkmod.
4.put your battery off on your magic and put on again.
5.your magic will be back alive
pls responsed my solution
Hey everyone.
I was rooting my MyTouch 3g w/3.5mm this morning. I'm following the instructions from here ( http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ ). I had apparently messed up when I was at the restart after flashing sappimg.zip onto the phone and was stuck at the HTC Magic Screen. I restarted my phone by holding down the Reject Call + Volume Down key and told it to flash sappimg.zip onto the phone again so I could redo it correctly. Unfortunately, it's stuck at the "[1] SYSTEM - UNZIPPING" stage. I'm afraid to turn it off because it says to not power off the device.
So, yeah, have I bricked my phone or is there a way to restart this process so I can successfully root?
Thanks much, and have a happy holiday.
EDIT: This sort of resolved itself, but now I can't get into recovery mode. :/
Rhaseo said:
Hey everyone.
I was rooting my MyTouch 3g w/3.5mm this morning. I'm following the instructions from here ( http://theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/ ). I had apparently messed up when I was at the restart after flashing sappimg.zip onto the phone and was stuck at the HTC Magic Screen. I restarted my phone by holding down the Reject Call + Volume Down key and told it to flash sappimg.zip onto the phone again so I could redo it correctly. Unfortunately, it's stuck at the "[1] SYSTEM - UNZIPPING" stage. I'm afraid to turn it off because it says to not power off the device.
So, yeah, have I bricked my phone or is there a way to restart this process so I can successfully root?
Thanks much, and have a happy holiday.
Click to expand...
Click to collapse
So your flashing the engineering spl for the first time or are you flashing the stock spl back?
Binary100100 said:
So your flashing the engineering spl for the first time or are you flashing the stock spl back?
Click to expand...
Click to collapse
I'm flashing the engineering spl onto there for the first time.
It appears that being stuck at the Magic screen is normal according to a different (but similar) guide from the Cyanogen Wiki. Would it irreparably damage my phone if I removed the battery despite it being at the "Unzipping" screen for Sappimg (as I was unzipping sappimg for a second time) and proceeding with CyanogenMod's guide instead?
EDIT: It appears my phone just turned off on it's own (battery probably died). I'm going to try CyanogenMod's instructions and see if that works.
EDIT 2: So, I reflashed it with the sappimg that Cyanogen has on his wiki. So everything was smooth sailing until I got to the Recovery step. I cannot, for the life of me, to get it to boot in recovery mode. I hold HOME+POWER but nothing pops up.
EDIT 3: And it appears as if I've bricked it.
Rhaseo said:
I'm flashing the engineering spl onto there for the first time.
It appears that being stuck at the Magic screen is normal according to a different (but similar) guide from the Cyanogen Wiki. Would it irreparably damage my phone if I removed the battery despite it being at the "Unzipping" screen for Sappimg (as I was unzipping sappimg for a second time) and proceeding with CyanogenMod's guide instead?
EDIT: It appears my phone just turned off on it's own (battery probably died). I'm going to try CyanogenMod's instructions and see if that works.
EDIT 2: So, I reflashed it with the sappimg that Cyanogen has on his wiki. So everything was smooth sailing until I got to the Recovery step. I cannot, for the life of me, to get it to boot in recovery mode. I hold HOME+POWER but nothing pops up.
EDIT 3: And it appears as if I've bricked it.
Click to expand...
Click to collapse
Will the rom start? If so, you didn't brick it.
Do you have the Engineering SPL on it? What SPL version do you currently have on there? Remember that if you have the T-Mobile US MyTouch w/3.5mm jack then you MUST have 32B recovery and radio and STOCK (1.33.0013) SPL before flashing a custom rom.
Best way to do it is to flash your custom recovery (I suggest Clockwork Recovery for Mytouch/ION devices) by fastboot.
Afterwards then flash your stock (S-ON) SPL back and then boot to recovery to flash your rom.
REMEMBER!!! YOU DO NOT HAVE A 32a DEVICE! DESPITE WHAT THE SPL SAYS... IT'S NOT TECHNICALLY A 32a DEVICE!!! You MUST treat is as a 32b.
Binary100100 said:
Will the rom start? If so, you didn't brick it.
Do you have the Engineering SPL on it? What SPL version do you currently have on there? Remember that if you have the T-Mobile US MyTouch w/3.5mm jack then you MUST have 32B recovery and radio and STOCK (1.33.0013) SPL before flashing a custom rom.
Best way to do it is to flash your custom recovery (I suggest Clockwork Recovery for Mytouch/ION devices) by fastboot.
Afterwards then flash your stock (S-ON) SPL back and then boot to recovery to flash your rom.
REMEMBER!!! YOU DO NOT HAVE A 32a DEVICE! DESPITE WHAT THE SPL SAYS... IT'S NOT TECHNICALLY A 32a DEVICE!!! You MUST treat is as a 32b.
Click to expand...
Click to collapse
Oh, wow. That explains why I bricked the phone. The Amon_RA Recovery I put on there was 32a... I'm an idiot.
The phone won't start up at all. :/ Looks like I'm out $100 or so.
Thanks for that, though. I was going to give you a "Thanks" but it appears the button has disappeared for me.
Rhaseo said:
Oh, wow. That explains why I bricked the phone. The Amon_RA Recovery I put on there was 32a... I'm an idiot.
The phone won't start up at all. :/ Looks like I'm out $100 or so.
Thanks for that, though. I was going to give you a "Thanks" but it appears the button has disappeared for me.
Click to expand...
Click to collapse
Can you still get into fastboot?
Binary100100 said:
Can you still get into fastboot?
Click to expand...
Click to collapse
Nope. It won't turn on at all.
Rhaseo said:
Nope. It won't turn on at all.
Click to expand...
Click to collapse
Won't boot, no recovery, no fastboot.
If it looks like a brick, if it sounds like a brick then it's probably...
I have a similar problem. I purchased this phone and it just almost works. It boots into fastboot just fine but not recovery. Here are the specifics as they stand now.
Sapphire unknown 32A ship S-on H
CLD 13
Radio 3.22.20.17
May 8 2009, 21:02:32
I made a good gold card...tried the 2010 spl...still hangs during unzip step of the flash process. Any other ROM and I get a main version older error.
Fastboot info version main 2.53.707.2
cid T-MOB010
Any help would be greatly appreciated.
Nice job on probably bricking your phone. You've got the myTouch 1.2 which means you just flashed an incompatible radio. Congratulations!!! I honestly not sure what to tell you. Which sappimg are you trying to use to get the engineering SPL?
Like i said...it was like this when I bought it.
I'm going to try to do a poorman's JTAG...wish me luck.
jonk26.2 said:
wish me luck.
Click to expand...
Click to collapse
Good luck! You can do it!
If you have any questions along the way, please don't hesitate to ask.
JTAG did in fact de-brick my MT3G 1.2 (bought from ebay) the first time I tried it. I made the mistake of flashing the stock ROM, so I would get to the "touch the android to begin" screen and couldn't get any further without a data plan. It wasn't until I probably flashed the wrong sappimg in a root attempt that I started experiencing the stuck at unzipping/FAIL-PU/remote signature verify fail problem...
FYI, I tried flashing radio 2.22.28.25 (the one from the OTA) using JTAG and the radata command, and it fixed my USB. I haven't experiemented much beyond that, but I'm planning to try some more things this weekend.
Moderators, I'd like to suggest merging this thread with http://forum.xda-developers.com/showthread.php?t=773368 and http://forum.xda-developers.com/showthread.php?t=771622 since they all seem to be discussing the same problem.
I went though some of the forums and didn't quite find what I was looking for, BUT a friend on Reddit pointed me over to this forum for help. I loaded Engineerings SPL on to my phone and when I booted up the phone I got a totally new boot screen saying "HTC Magic" After about 20 minutes I realized my phone isn't going to boot at all, I thought no big deal and tried to unroot my phone with the unlocker website and the sapping.nbh file failed during installation. (The last two items had an odd error) BUT when I rebooted my phone it now had the green mytouch 3g loading screen but again failed to boot. And thats it, this is where I am stuck.
I Have a My Touch 3g 3.5MM jack phone and I was simply trying to load a custom rom onto my phone, I can access fastboot and the android recovery console (Thing for wipe and update.zip from sdcard) But everything I have tried fails! I am really starting to stress out about this but a I was told it doesn't seem to be very serious if I can access all the menus like that. If you need anymore info I will be checking the thread regularly. Sorry for causing the trouble I am probably just another pest who made a dumb novice error , for that I am sorry. But if anyone could help me out it would be much appreciated.
EDIT!: Also I forgot to add I have GoldCard from before my phone broke, not sure if this will still work but it might help.
Post there all fastboot info, ALL.
Also the outcome of this command done in fastboot mode
Code:
fastboot getvar version-main
When you refer to "the android recovery console (Thing for wipe and update.zip from sdcard)" do you mean android stock recovery or custom recovery?
Im trying to get the data from that fast boot thing but Im kinda new to all this in order to get that data I hook my phone up to pc with usb cord start up cmd prompt and type
cd\
AndroidSDK\tools\adb
then type in that command? Kinda lost on what im doin there.
And how do I find out if it is stock or custom? it has the symbol for the FlashRec app in the backround though if that helps.
But the stuff on the top of the fast boot is.
Sapphire PVT 32A Ship S-ON G
HBoot-1.33.0013 (SAPP31000)
CPLD-13
Radio-2.22.19.26I
Oct 21 2009, 22:33:27 (Some weird date?)
Trying to type it into cmd prompt straight from cd\ doesn't work. I need some way to mount the device from fast boot it seems
http://forum.xda-developers.com/showthread.php?t=734617
mumilover said:
http://forum.xda-developers.com/showthread.php?t=734617
Click to expand...
Click to collapse
What does this do for me? My phone is stuck in an unusable state almost I cant root it at this point.
THANK YOU!!!!
THANK YOU SO MUCH! My phone is 100% fixed and running a shiny new OS! I can't thank you enough!
LemonFondler said:
THANK YOU SO MUCH! My phone is 100% fixed and running a shiny new OS! I can't thank you enough!
Click to expand...
Click to collapse
Good to hear. Now make a nandroid backup and don't fix what isn't broken.
LemonFondler said:
THANK YOU SO MUCH! My phone is 100% fixed and running a shiny new OS! I can't thank you enough!
Click to expand...
Click to collapse
What did you do after getting that link to get your phone fixed? That way if someone else gets stuck in the same boat they'll know what you did.