Database Users

Stuck at vodafone screen< HELP?!?!?!?!?!?

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.

Bricked Magic 32A - need help what picture means

Hi all,
I managed to brick my device during radio upgrade (check my last post on http://forum.xda-developers.com/showthread.php?t=632869&page=2) so now my magic is showing some picture after powering on which i do not understand what it means - after few seconds this picture blacks out and that's it (display is lit but it is black).
Fastboot, recovery and goldcard process are not available.
Help is appreciated, and also suggestions to revive it as well.
P.S. I tried to give it to the service, they said "Tampered boot" and returned the unit back to me as is so I am on my own here :-(

over 100 reads and no answers? C'mon people, I am sure that there has got to be someone who knows what this picture means

The picture is a system screen. It's in the background while updating roms and what not. What version of android are you running and can you get into any boot screens ie. powering on using back and home at the same time?

To be quite honest I do not know which version of android was on before - i just know that it happened during uploading radio 6.35.08.29.
Back + Home + Power on shows same picture.
If I put same radio as update.zip on the SD card would it have any sense??

mjagar said:
To be quite honest I do not know which version of android was on before - i just know that it happened during uploading radio 6.35.08.29.
Back + Home + Power on shows same picture.
If I put same radio as update.zip on the SD card would it have any sense??
Click to expand...
Click to collapse
Well it's been a while for me, but it seems like that pic is from the original recovery, you require amon's recovery.
Have you gone through the steps from Cursordroid, upgrading/downgrading SPL and Radio? Follow his procedure, grab all the correct files and use Fastboot.

Bedeadu said:
Well it's been a while for me, but it seems like that pic is from the original recovery, you require amon's recovery.
Have you gone through the steps from Cursordroid, upgrading/downgrading SPL and Radio? Follow his procedure, grab all the correct files and use Fastboot.
Click to expand...
Click to collapse
Can't use fastboot because i cannot bypass this part with boot picture :-(
I also noticed this thread: http://forum.xda-developers.com/showthread.php?t=632102 - exactly happened to me, semms like this radio version 6.35.08.29 when uploading from SD card is bricking a phone sometimes - BEWARE !!!
Please explain how to do recovery from cursordroid - have in mind that I only have SD card, I cannot reach fastboot, recovery or anything... If it can be done by putting some files to sdcard please describe it and if successfull i am buying beer... Hell, if it works i might introduce you to my younger sister ;-)

As you now have a 6.35* radio, can you do this?
Code:
adb shell
flash_image hboot hboot-1.76.2007.img

sindrefyrn said:
As you now have a 6.35* radio, can you do this?
Code:
adb shell
flash_image hboot hboot-1.76.2007.img
Click to expand...
Click to collapse
"error: device not found"

A few days ago my 32a did the same thing. I tried to use fastboot and didm't work. I had 6.35 radio and I had updated it like it said in the instructions.. I took the batery off several times, and it booted properly.. Try to do that.. Sorry for my english..

Sorry for my bad english ,
It's happen to me too. Yesterday I had my friend’s htc magic . He gave me that because he said that it was briked. When I press back+power or voldown+power or home+power , the result is same like picture in first post.
no adb and fastboot worked . How about you ? Is your phone normal again ?
thanks before .

Hi, no unfortunatelly my phone is still bricked - i removed baterry at least hundred times but no change... :-(

mjagar said:
Hi, no unfortunatelly my phone is still bricked - i removed baterry at least hundred times but no change... :-(
Click to expand...
Click to collapse
I think your phone is 99% bricked. Press hang + back, if you can entry hboot mode. Then try the attachment files.
Please be sure your phone is rooted and not perfect SPL.
GOOD LUCK!
View attachment 292085
View attachment 292095
View attachment 292096
View attachment 292098

hm.....that pic was displayed after I upgraded Radio, too. but then it was back to recovery mode, and I reboot & my phone work normaly w radio updated... So I think it's not danger pic :-?

once youre in that recovery mode, if you hit the home + back again anything happen?
i know if i get that screen on the Dream, I hit home +back again it changes my screen with options.. On your phone it may be vol dn + home try it out, mine gives me the option to flash update.zip from my SD card again.

Unfortunatelly I cannot get to hboot (home + red button), nor fastboot (back + red button) nor even volume DN + redbutton...
Looks like it is bricked 100%.
So guys, be carefull when upgrading radio 6.35.08.29 :-(

mjagar said:
Unfortunatelly I cannot get to hboot (home + red button), nor fastboot (back + red button) nor even volume DN + redbutton...
Looks like it is bricked 100%.
So guys, be carefull when upgrading radio 6.35.08.29 :-(
Click to expand...
Click to collapse
Read carefully and follow the instruction here: http://forum.xda-developers.com/showthread.php?t=605239
then i don't think there is to much to worry about!
For me it sounds like you updated the radio and restarted the mobile before updating the SPL. OR you forgot to check the m5dsum of the radio and flashed a broken radio file to your mobile.
It's IMPORTANT that you guys remember to check md5sum of the files before flashing em cause a broken radio/spl file can brick the phone!

same pictrue on my magic
My magic have same picture. I try to study Android for help it.

I see more and more threads like this and no movement in direction which could unbrick the phone without changing the motherboard...

Seems like I'm in the same situation as the OP. Got the same picture and can't do anything about it.

What's wrong with the new radio?

What's wrong?
I mean I've tried to flash it 4 times. It failed all of these. When I flash it, it gets stuck on "writing radio...", the screen gets black and nothing happens. Then whatever radio I want to flash, it will do the same. The only solution is to use an RUU, which will fail the same way, but then you reboot the phone and continue.
What's up with this? Any idea?

Please provide SPL info (Turn the phone off, turn on by pressing Back + Power)
If you have 1.76.2007 ENG S-OFF - you can flash new radio
If you have other info - anybody will write you right instruction)

5[Strogino] said:
Please provide SPL info (Turn the phone off, turn on by pressing Back + Power)
If you have 1.76.2007 ENG S-OFF - you can flash new radio
If you have other info - anybody will write you right instruction)
Click to expand...
Click to collapse
It *was* S-OFF, but 1.76.2010 I think. Now I reflashed the RUU, I'll try with this.

wrong section! moving to general.

Ok, I now believe I've bricked it. I downloaded an update for the radio from http://www.theandroidkitchen.com/fileshare/Sapphire-32A-Updates (a zip), flashed it from recovery and bam. Now the phone reboots and shows an HTC screen (with its logo). Then it becomes black and that's it. It can't boot from fastboot, hboot, recovery, nothing. Even the RUU can't do something.
Holy crap, HELP!

[Q] Help with my MT3g 1.2 I think its bricked?

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

[Q] Stuck At Unzipping Screen (Now It Won't Go Into Recovery Mode)

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.