Unable to flash with RUU - EVO 4G General

I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?

Hold power and volume when turning on phone, then select fastboot and have the selection for bootloader highlighted, then start the RUU it should work then.

OK, so I tried the volume down + power btn deal, but still no dice. I really don't undestand wtf happened, cause before doing the 2nd part of root, I was able to load Damage ROM, now anything I load besides the PC36IMG.zip from part 1 just bootloops. Crazy

control_logic said:
I did all the steps to root the phone, 1 and 2, but got stuck in a bootloop. The sprint log stuff would come up, the the 4g, then back to sprint etc. I flashed the PC36IMG.zip of the shipped version, but now I can't get the RUU to take the phone into a fully factory state. It starts, then gets stuck waiting for bootloader with a black screen and htc on it. I really just want to make it factory again and start over with the root process. Any ideas?
Click to expand...
Click to collapse
ive seen this answered in the RUU threads. they mentioned the RUU doesn't automatically reboot the phone into the correct mode, i think it was bootloader? manually booting it into the correct mode, then connecting the USB, resolved the issue.
you might want to search/reference the RUU threads for more details as i never had the issue and am only recalling off the top of my head what ive read, which cant be 100% accurate!

When RUU stops/freezes and your phone has the black screen with "HTC" on it.... do not restart your phone or anything leave it the way it is. What you do is exit out of the RUU program by clicking "exit" when it freezes up. Then without doing anything to the phone, just restart the RUU program and it should pick up where it left off and complete the process. I found this fix in "Q and A" part of the Evo forum and it worked for me.
Sent from my PC36100 using Tapatalk

You need to format the phone rest and format cashe then install the rooted image and it will boot. I had the same problem.

Thanks for the responses, it is working again, YEAH!

Related

Help needed to fix rooting gone wrong

First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.

stuck at splash screen, have tried all the solutions.

Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.

Is my HTC Magic totally bricked?

I bought a Rogers HTC Magic for a pretty cheap price. It had The Rogers 1.5 Sense UI update on it. I decided I wanted to root it and load other ROMs, etc. So I read that the easiest method was to use Universal Androot to root it, and ROM Manager (from the Market) to flash the appropriate recovery image.
So, I installed both apps. I first ran Universal Androot and rooted. I confirmed root through ADB and also Super User permissions. I then restarted the phone just for peace of mind. After the restart, I ran ROM Manager. It automatically popped up and asked me if I was running an Ion/My Touch or an HTC Magic. I selected HTC Magic, because that's what this is. So then it flashed the recovery image and restarted the phone. When it restarted it went to the Rogers boot screen for a few seconds, and then started a loop of restarts. That's all it does now. It shows the Rogers screen for a few seconds, goes black and reboots over and over. I have tried booting into HBOOT, Fastboot, and into recovery. I cannot boot into any of them. One thing I did notice is that when I'm pressing any of the combinations (volume down + power, home + power, menu + power) for a very brief half a second right before the phone restarts, the bottom of the screen says "ClockwordMod ..." where ... is the version of the image (I'm at work without the phone, so I don't recall the exact number there).
So, is this thing officially a paperweight now, or is there some sort of hope?
Thanks.
Paul
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
adrift02 said:
Well, I don't know if you are full-bricked but here is what went wrong. The HTC Magic recovery is incorrect for the mytouch3g (at least the 32b). There was a top option for "saphire/mytouch 3g" which is what you should have chosen. So, you can't load the incompatible recovery. Can't you boot back into the rom you were using? The recovery flash shouldn't have messed with it. If you can, boot back in and flash the correct mytouch3g recovery in rom manager.
Click to expand...
Click to collapse
Okay. That's weird. I mean, my phone is a Magic so choosing the option for the Magic instead of the Ion/MyTouch seemed to make sense.
Anyway, I cannot get anywhere. Holding vol+ and power does nothing, neither does home and power or back and power. Are there any other tricks to getting anywhere beyond this endless restart loop?
Thanks.
Starting to think I'm screwed.
PaulieORF said:
Starting to think I'm screwed.
Click to expand...
Click to collapse
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
ezterry said:
You may be, I'm not sure exactly what state you are in but the recovery you installed was for a magic 32a (that you have) with a 3.x radio (that you don't have)
The rogers sense rom uses the 6.x hero radio and needs a hero recovery.
The mt3g uses a 2.x radio thus yet another recovery.
Try booting with volume down to see if you can get into the hboot/fastboot screen, but I think you tried this already.. you may also try letting it loop unplugged until the battery drains it may error out giving you access again..
Besides that there is the option of jtag and fixing the software stack that way.
Click to expand...
Click to collapse
Thanks for the reply!
Right, I cannot get into fastboot or hboot. I'll try running the battery down when I get home today. Interesting idea.
Unfortunately running the battery dead with restarts didn't do the trick.
Any idea if there's any place I can send it to who has the smarts to jtag recover this thing?
Thanks.
me too
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
tmokeith said:
I did the same thing on a 32B. Rooted. loaded ROM Manager. Ran the recovery, I choose the Ion/MT3G option. tried to load CM6-FroyoRedux-v1.7-32b-blk.zip. Now it's stuck in the boot screen.
Click to expand...
Click to collapse
I don't think it's the same thing.
I rooted, loaded ROM Manager and installed the recovery. I was never even able to get into recovery in order to try to load any ROMs.
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
nate_benji said:
I have a Rogers magic, and its a 32a. One way to fix it is to go to the HTC website and punch in your serial number and download the rogers update. Only problem is that will make it a pain to root again. But should fix that reboot loop. But do that as a last resort to get the phone running again.
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
The phone does not identify itself to the computer, so this doesn't work.
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
nate_benji said:
The program should try to put the phone into fastboot mode, and install the upgrade. Have you tried pulling the battery and pressing the power button + back, once the battery is installed again?
Sent from my HTC Magic using XDA App
Click to expand...
Click to collapse
Oh yes. I've gone crazy trying every key combination with every combination of taking battery out, plugging it in, USB cable attached, detached, etc.
The phone never identifies itself as a piece of hardware to the computer in the 5 seconds between reboots.
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
naparstekk said:
I had the same problem yesterday, and i was doing the same rooting with Universal Androot and flashing recovery witch Rom Manager (choose the same options). I tried to go into recovery and then it started to bootlooping the whole time.
I was pretty scared when that happens, can't open fastboot menu and the only thing that my phone was showing was HTC logo and a quick blink of clockwork sign over and over.
I don't know exactly how i managed to fix it, but it started to work when i quickly plug off baterry and i immiediatly plug it in (I was doing it at the exactly time when the phone reboots) while holding the power button.
Now my magic turns on, but recovery won't work (just flash for a moment, and reboots) and it always say at the beginning of booting system that SD card was removed which means i can't use any SD card.
I hope it somehow helped you.
Click to expand...
Click to collapse
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
I wasn't able to get hboot or fastboot. I pluged off and on the battery in the exact moment when the Logo came out after restarting. The logo was on the screen for the whole time, even while battery plugged off. I guess, i've done it so quickly that phone didn't switched off.
I think i was holding the power+home or power+back buttons all the time.
Can't really rember the exact way, sorry.
PaulieORF said:
I tried doing this quickly for about 5 minutes this morning but didn't get it to go anyway. I can try some more after work today.
When you say it booted after this battery pull thing, do you mean the phone booted right into Android, or you were able to get to hboot or fastboot?
Thanks.
Click to expand...
Click to collapse
Try removing the SD card and booting if its not restarting due to the wrong radio too soon that may help.. if you get into android restore the SD card and run the exploid process I posted a bit back for rogers magics, or the older goldcard method.
I've played around with taking the battery out and putting it right back in at all different times during the booting and can't get the phone to behave any differently. Iv'e tried it with SD card in and SD card out, USB cable in and USB cable out. I can't get anywhere.
I did notice that the phone does show up as an Android device for a second when it's booting. Tried to catch it in adb but no luck.
Starting to think this thing is shot. Any other ideas?
Just so everyone can see what's happening, I recorded a video and uploaded it. Linked below:
http://www.youtube.com/watch?v=hPoxMzm0MVU&hd=1
try to hold and KEEP holding the back + power... Not volume down!
Don't push and release like you did in the video.

[Q] my htc magic keeps rebooting after flashing an old recovery image

Hi
I had a problem with my htc magic after trying to flash the RA-sapphire-v1.0.0 recovery image into the phone. Before the problem occurred I rooted my phone and flashed RA-sapphire-v1.6.5, but because I had an issue with it I tried to flash an old version " RA-sapphire-v1.0.0".
Now my phone keeps rebooting endlessly and I can not access recovery mode, fastboot or anything else?
Is it bricked? Can I fix this issue?
The phone is 32A
Radio is 6.35 (I can not access fastboot so this is from my memory)
If you have no access to fastboot nor recovery, then you are pretty bricked!!!
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
DonJuan692006 said:
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
Click to expand...
Click to collapse
I tried both method and it did not work. The phone is still rebooting endlessly. I used the old recovery since the new one kept restarting the phone to the actual system after I go into recovery mode after 2-3 seconds.
1.6.5 isn't the new one. The newest version is 1.7.0. Well if that didn't work, then year your bricked.
so is there anything i can do to fix it?
JTAG is your only option.
Where are you from ?
usernome said:
Where are you from ?
Click to expand...
Click to collapse
I am from Australia
I have HTC Magic Vodafone (32B) and have a similar issue with phone in a reboot loop, however, i can get into fastboot but not sure what next to do. Is there a guide anywhere on what to recover my phone.
Depends, what is your current fastboot information?
Not sure what info you want from Fastboot screen so this is everything i can see
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Oct 21 2009,22:33:27
Is this the right kind of information?
Two options. Downgrade to 1.5, then update to 1.6, then root, flash a custom ROM, reinstall the 1.33.0013 SPL and 2.22.28.25 radio, and then flash a new custom ROM. Optionally, you can downgrade to 1.5 and upgrade back up to 2.2.1. Either way just let me know and I can assist.
Thanks for you help with regards to the approach, is one easier than the other? If they are both roughly the same then would go for the Downgrade to 1.5 and upgrade back up to 2.2.1. route as it may be easier to sell in a few weeks when the Galaxy S2 out.
So, here we go, please read through all the steps before starting and then reading each step as you go along:
1. Go here and download "sappimg.nbh" and "update1-5.zip".
2. Put all of them on your SD card. I would suggest downloading to a folder on your computer, then copying them over. Have had issues in the pass with people downloading files directly to their SD card and it corrupting the file.
3. With the phone turn off and the SD card in it, boot holding (volume down+power) to get into hboot. The phone should detect the sappimg.nbh, check the file (you'll see a progress bar in the upper right-hand corner), and then ask you to hit "ACTION" to continue. (ACTION being pressing the trackball)
4. The phone will start flashing the different parts of the phones partitions. You'll see the progress bar in the upper right-hand corner a few more times, then after about 5 minutes, it'll ask you to hit "ACTION" again to reboot.
5. Let the phone boot all the way up (this may take a few minutes) and then turn it off without signing in.
NOTE: Unless you need the phone to access the SD card from the computer, in that case sign in and do the next step.
6. Access the SD card, find "update1.zip" and rename it to "update.zip".
7. With the phone off turn it back on by holding (home+power) to get into recovery. You'll see a triangle with an ! in it, press (home+power) again to bring up the menu.
8. Using the trackball, scroll to the "wipe data/factory reset" option and press the trackball to select it. After it completes, scroll to "apply update.zip from SD card" and select it. It should pickup the update file on the SD card and flash it, then reboot.
9. When you get to the login screen again, turn the phone off.
Note: Again, as before, you can optionally login to get into the ROM for access to the SD card from your computer.
10. Repeat steps 6-9 for the "update2-update5.zip" files. You will need to remove the old "update.zip" before renaming the next update file. When you get to the login screen the last time (after flashing "update5.zip") you can sign in and use the phone.
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Geffen22 said:
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Click to expand...
Click to collapse
Crap gave you the wrong sappimg. What country did you get the phone from?
Sent from my LG-P500 using Tapatalk
I got phone from Vodafone in the UK.
Geffen22 said:
I got phone from Vodafone in the UK.
Click to expand...
Click to collapse
Need the specific country.
United Kingdom or England to be exact.

mytouch s-off in bootloader nothing else works..bricked?? fixable??

I had freezing issues, my mytouch 4g would just end a call and id have to take out the battery and restart it or it would freeze on a screen, even the start screen ans wouldnt do anything and id have to take out the battery and restart it. I tried deleting apps to make it stop doing this but nothing was working. I talked on my phone the other night and as soon as i hung up it froze, i tried restarting it and now all it will do is go to the mytouch 4g boot screen, but it wont boot up. usually it would flash that screen and go to the sceen with the green dot the wrote my in the center then reboot, but it wont go past the mytouch 4g screen.
I have tried holding the volume down button and set back to factory settinfs, but all that did was sit on the skateboarding androids screen until the battey died, I have tried this many times both with and without my sim and SD cards in.
I have tried recovery and my phone acts like its going to restart then flashes and phone with a red triangle and exclamation point on it and wont do anything, wont even come back on until i take the battery out and put it back in and turn it on again.
things to note: i am able to get into the bootloader screen via power and volume down but anything after that such as factory reset and recovery fails, i rooted the phone and it is S-off. I wont mind sending it back to tmobile but i need to get s-off in order to do so. I would do adb but i am unable to get into recovery so i cant. i also would flash the pd15img.zip but the phone while in hboot i keep getting failed pu on everything then nothing happens.
any help on possible solutions would be greatly appreciated. I dont even really need it working i just need s-off so even if it wont work i can send it back to tmobile. thanks in advance
if you are getting the 'fail pu' message your phone may be bricked. unfortunately there are a lot of other people that have experienced this. I'd send it back to t-mo anyway, they are aware that this problem exists.
Sent from my HTC Glacier using xda premium
Ok so I wont be charged anything by the insurance company although I rooted it last year. I don't want to send it in and then get a a crazy bill for
like $400 because they receive the phone and find out that it was rooted.
Hi, did you try and go to T-Mobile site and select your phone and download the OTA through their program in the support section. It will restore it. Then redo the downgrade if u don't have s-off
Sent from my HTC Glacier using xda premium

Resources