Phone is unstable - Desire Q&A, Help & Troubleshooting

All of a sudden my phone has become unstable. The phone locked up, and now I cannot boot into recovery. Sometimes I can boot into the phone but then it freezes on reboot. It then cycles on the first splash image, when trying to get into recovery or ROM.
I have S-OFF and am able to use it, I have tried Fastboot reflashing recovery, S-OFF hboot, splash img and wipe userdata
Does anyone have any ideas?

deeeez said:
All of a sudden my phone has become unstable. The phone locked up, and now I cannot boot into recovery. Sometimes I can boot into the phone but then it freezes on reboot. It then cycles on the first splash image, when trying to get into recovery or ROM.
I have S-OFF and am able to use it, I have tried Fastboot reflashing recovery, S-OFF hboot, splash img and wipe userdata
Does anyone have any ideas?
Click to expand...
Click to collapse
This should not be posted in the Development section but in the Q&A section.
Can you flash an RUU? Remember to have a goldcard.
If that does not work, then follow this.
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck

deeeez said:
All of a sudden my phone has become unstable. The phone locked up, and now I cannot boot into recovery. Sometimes I can boot into the phone but then it freezes on reboot. It then cycles on the first splash image, when trying to get into recovery or ROM.
I have S-OFF and am able to use it, I have tried Fastboot reflashing recovery, S-OFF hboot, splash img and wipe userdata
Does anyone have any ideas?
Click to expand...
Click to collapse
Oh yes, i also have this problems with certain roms. If your recovery cannot work thus no way to flash another rom, then just follow the above and root again.

How do I access my SDcard I cannot see it when in bootloader or fastboot

deeeez said:
How do I access my SDcard I cannot see it when in bootloader or fastboot
Click to expand...
Click to collapse
use a card reader and your pc

Related

Stuck in Hboot, pc36 & recov not working

Hello,
I've been rooted for over a year now. Have flashed back and forth roms around hundreds of times now. Unfortunately an hour after flashing synergy godmode and some of the godmode tweaks, my phone rebooted while idling and bootloops.
Now i am stuck in hboot and can not enter recovery. I am using hboot 0.76.2000 (pc3610000) and s-off. I have tried flashing seperate clockwork and amon-ra embedded pc36img.zip, these say that they will complete updating but then will bootloop after i try to enter recovery. I have tried these updates with a different sd card (as my current sd card w/godmode may be an ext2 partition?) but that has not changed anything either.
As i understand, I can only push files with adb through recovery; which i can not get into.
If anyone can please help it would be very much appreciated.
Thank you in advance
try this way? its how i flash my recoveries when im switching or testing...
remove any pc36img.zip files from your sd and boot to your bootloader...
when you bootloader boots up let it scan for the pc36img whatever thing and let it say not found...
now highlight fastboot and click the power button and wait for FASTBOOT USB to show up...
then type in these codes...
Code:
fastboot devices
it should output some info, if you get some serial number then your good
then type in...
Code:
fastboot flash recovery *whatever the name of the recovery your using is*
so like for amon_ra 2.3 (which is what i use is)
Code:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
just make sure that the recovery img file is in the same directory as the fastboot.exe file on your comp (its should be with all your other sdk stuff like adb.exe and such)
if all goes well then itll say
pushing recovery OKAY
writing recovery OKAY
and the amount of time it took...
then click back into your bootloader and go to the newly written recovery
(i apologize in advance if you already tried this with no avail)
I've set up fastboot usb and done this. Everything wrote ok and finished, however i still bootloop when trying to access recovery. I have tried multiple recoveries including clockwork 3, recovery-RA-supersonic-v2.3.img, and doing entire nandroid restores using nandroid recovery batch script. In both cases everything passes and nothing seems to be functional afterwards.
Any other ideas?
dunno man.. im just trying to visualize how it bootloops going to recovery.. it should be the white htc screen (or any other splash you may have set on there) and then boink recovery... does it like just sit there on the splash and thats it?
try letting it boot normal and then when it goes to the rom loading screen type in
Code:
adb reboot recovery
other than that something is totally askew bro
When booting, i'll get the white htc screen for 4-5 seconds, then it'll power off and reboot, unless i boot to hboot. When i hit recovery, it goes black for a second, then reboots to htc screen and repeats.
I've also tried complete wiping recovery and reloading using fastboot commander, and doing full pc36img.zip that include hboot, radio wiimax updates etc http://forum.xda-developers.com/showthread.php?t=830153&highlight=wimax
I may just go into a sprint store today. Was trying to avoid it as I really don't want to be stock again.
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
the only hboot that allows fastboot commands is 0.76 unfortunately
try running an ruu maybe? other than that i havent the slightest idea
I used this RUU - http://forum.xda-developers.com/showthread.php?p=7529500
It passed every step, but still bootloops when booting to ROM and Recovery.
I'm out of ideas....
I'm going to go with hardware problem.
Sent from my PC36100 using XDA Premium App
bad sector on the internal flash memory ?
My brother has the same problem and i have been trying to fix it with no luck. When i boot the phone up its beeps/vibrate 5 times, then sits on a black screen. I can get into hboot and load pc.....whatever files, it says they work but still reboot, 5 beep, ect. I was going to try an RUU next i see that didnt work for op.
i just ran into this problem today. I was at work when it randomly rebooted and now is stuck in a bootloop. i have tried everything even using the latest RUU. it finished but still bootloops. I am also not able to get into recovery. Sucks because im out of warranty.
So let me get this straight...you can't go into recovery because there's no recovery? You've installed drivers and ran RUU and still nothing? That seems weird because i had the same issue when i first rooted my phone with unrevoked, all i did was run the RUU and it restored my phone back to "stock" and i re-rooted again but this time using z4 root. You might just have to take the phone back to Sprint
Same issue but worse
I'm having the same issue as the OP except that my buttons (power and volume up/down) will not respond. I have scoured these and other forums for a situation like mine and have found none.
I have tried flashing recoveries, RUU's and jsut about anything someone says.
First screen says:
supersonic evt3 ship s-off
hboot-2.10.0001
touch panel atmelc03_16ac
oct 15 2010 12:01:00
hboot
fastboot
recovery
clear storage
simlock
hboot usb
then it scans the sd card for the pc36img zip. It will load but will freeze on the next screen:
parsing...... [sd zip]
1. boot loader
2. radio
3. boot
4. recovery
5. system
6. user data
7. splash
8. wimax
it will stick here and I am completely lost. My old Palm Pre will only suffice for a day.... max.
If anyone has come across a situation like this that might help me, would you please point me in the right direction. Thanks!
kdbrown5 said:
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
Click to expand...
Click to collapse
If you look in autoroot thread in my sig the "tools" zip has something that will let you flash different partitions from fastboot. If you use that to flash the PC36IMG from here it will give you the eng hboot back and possibly reflash whatever got corrupted.
Keep in mind, that will only work properly if you are not using one of the 2.xx hboots. Only phones with a 0.9x hboot will let you use it.

[Q] Boot loop, can't enter recovery

I'm in need of some expert help for my wifes Droid Incredible. It is rooted, s-off running Cyanogen 7.xxx
She woke me in a pannic this morning saying her phone wasn't working. When I took a look, it keeps booting to the white screen with the "htc Incredible" words. I can press volume down and power to get into hboot, but when I select recovery or factory reset, it just boots back to the white screen with "htc Incredible"
I can't seem to get anywhere from here and the search I did seems to bring up other issues with people at least able to get into the recovery.
Any help or advice on where to go from here would be greatly appreciated.
Thank you.
Droinc said:
I'm in need of some expert help for my wifes Droid Incredible. It is rooted, s-off running Cyanogen 7.xxx
She woke me in a pannic this morning saying her phone wasn't working. When I took a look, it keeps booting to the white screen with the "htc Incredible" words. I can press volume down and power to get into hboot, but when I select recovery or factory reset, it just boots back to the white screen with "htc Incredible"
I can't seem to get anywhere from here and the search I did seems to bring up other issues with people at least able to get into the recovery.
Any help or advice on where to go from here would be greatly appreciated.
Thank you.
Click to expand...
Click to collapse
You need to try to reflash recovery thru hboot. Download CWM 5.0.2.0 http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and place the file on your sdcard in no folders. Boot into hboot (vol down and power) and it should find the file after a couple secs and prompt you to press vol up to update. Do so and then when prompted to reboot do so. Now remove or rename the PB31IMG.zip on your sdcard and then pull the battery and boot to hboot and see if you can access recovery.
cmlusco said:
You need to try to reflash recovery thru hboot. Download CWM 5.0.2.0, and place the file on your sdcard in no folders. Boot into hboot (vol down and power) and it should find the file after a couple secs and prompt you to press vol up to update. Do so and then when prompted to reboot do so. Now remove or rename the PB31IMG.zip on your sdcard and then pull the battery and boot to hboot and see if you can access recovery.
Click to expand...
Click to collapse
I got the message to hit volume up to update and then after that it asked if I wanted to reboot the device. I selected yes (volume up) and it still loops the white screen with the "htc Incredible" words. I never got to the point where it rebooted fully.
SHOOT!!! Was hoping this would have done it. Thank you for the help though. I appreciate it.
Anything else I might be able to do?
As a side not, the phone does not get recognized when I connect it to my computer. I had to use another phone to place the PB31IMG file on the SD card.
Droinc said:
I got the message to hit volume up to update and then after that it asked if I wanted to reboot the device. I selected yes (volume up) and it still loops the white screen with the "htc Incredible" words. I never got to the point where it rebooted fully.
SHOOT!!! Was hoping this would have done it. Thank you for the help though. I appreciate it.
Anything else I might be able to do?
As a side not, the phone does not get recognized when I connect it to my computer. I had to use another phone to place the PB31IMG file on the SD card.
Click to expand...
Click to collapse
No you misunderstood, it will still boot loop at this point, that was just the first step. Boot to hboot and see if you can access recovery now.
If you can access recovery, either restore a backup or flash a new rom.
cmlusco said:
No you misunderstood, it will still boot loop at this point, that was just the first step. Boot to hboot and see if you can access recovery now.
If you can access recovery, either restore a backup or flash a new rom.
Click to expand...
Click to collapse
Oh, gottcha. Sorry about that, my fault.
After hitting volume up to reboot, I took out the SD card and placed it in the other phone to remove the file. After that I put it back in the Incredible and booted it into hboot, but when I selected recovery, it did the same thing and just loops the "htc Incredible" screen.
Ok the next step to try would be to do an ruu. It will restore the phone to stock, but you will still have s-off.
Download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip and place it on the sdcard in no folders, boot to hboot, vol up to install. This time though when prompted to reboot select no, and then select factory reset. Hopefully when its done it will boot normaly.
cmlusco said:
Ok the next step to try would be to do an ruu. It will restore the phone to stock, but you will still have s-off.
Download this file and place it on the sdcard in no folders, boot to hboot, vol up to install. This time though when prompted to reboot select no, and then select factory reset. Hopefully when its done it will boot normaly.
Click to expand...
Click to collapse
OK, going to give it a shot. Will be back soon with good news hopefully
Question...... After selecting "no" to the reboot option after it's been updated with the file, do I delete or rename the file and THEN try to get into recovery?
Droinc said:
Question...... After selecting "no" to the reboot option after it's been updated with the file, do I delete or rename the file and THEN try to get into recovery?
Click to expand...
Click to collapse
After selecting no to reboot, select factory reset from the hboot menu. When the factory reset is done it should automaticly reboot and boot up like normal.
Then you can delete the file and reflash cwm recovery as the ruu left you with the stock recovery.
OK, I must be doing something wrong. Here are the steps I have done:
* I put the SD card into a phone recognized by my computer
* I then place the RUU file onto that SD card
* I then take the SD card out and place it in the DInc
* I then hold the volume down button and power button to get into hboot
* The phone recognizes the file and starts the update (takes a bit)
* Once the update is done it asks if I want to reboot and I select no
* It then goes to a screen with a few options (bootloader, reboot bootloader etc...) I don't select anything and then pull the battery
* I then take the SD card out of the DInc and place it in the other phone so I can remove the file
* Once the file is deleted I take the SD card out of that phone and place it back into the DInc
* I go into hboot and select recovery and it just boot loops again with the "htc Incredible" screen
Am I missing something?? I know it can be recovered. Even it's back to stock, it would be great. My wife just wants her phone back.
cmlusco said:
After selecting no to reboot, select factory reset from the hboot menu. When the factory reset is done it should automaticly reboot and boot up like normal.
Then you can delete the file and reflash cwm recovery as the ruu left you with the stock recovery.
Click to expand...
Click to collapse
Damn, you're fast cmlusco.
When I select no to the reboot, it does not present me with the screen that has the recovery option. It's a different screen with, I think, 4 options: bootloader, reboot bootloader, and 2 others I can't recall
Just notice this thread is on page 2 now. Check the last post on page one for steps on what I did.
When you boot to hboot there should be an option to do a factory reset, do that, you may have to select bootloader first. Then see if it boots normaly.
cmlusco said:
When you boot to hboot there should be an option to do a factory reset, do that, you may have to select bootloader first. Then see if it boots normaly.
Click to expand...
Click to collapse
no go.
I assume once I apply the RUU I don't need to do it every time?
I went back into hboot and selected factory reset and it just did the same boot loop. Should I try wiping the SD card 100% clean and then try the RUU file?
Droinc said:
no go.
I assume once I apply the RUU I don't need to do it every time?
I went back into hboot and selected factory reset and it just did the same boot loop. Should I try wiping the SD card 100% clean and then try the RUU file?
Click to expand...
Click to collapse
You could try it, but it sounds like the recovery partition may be messed up. The stock recovery dosent work, cwm recovery dosent work, but ruus and recoverys flash fine without error. Sounds like a messed up partition table. Do you have ADB setup on your pc?
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Droinc said:
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Click to expand...
Click to collapse
gotta download android sdk
http://developer.android.com/sdk/index.html
this should help http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html
Droinc said:
I don't have ADB on this PC. Been a while since I've even done anything with ADB. Could you point me in the right direction on what to do to get set up?
Once set up, what steps need to be taken?
Thanks for all your help with this. It's very much appreciated.
Click to expand...
Click to collapse
Download this http://dinc.does-it.net/ADB/ADB-Fastboot-USB-Drivers_v4_(x86)(x64).zip, and extract the contents to C:\ADB.
Connect the phone to the pc and on the pc go to device manager and look for an entry called unknown or android 1.0. Right click on it and select update driver. Select browse for driver and navigate to C:\ADB\drivers and select the adb folder. It should find the driver and update it.
Then open a cmd prompt on your pc and navigate to the C:\ADB folder. At tje prompt type adb devices , it should return a string of numbers and letters.
From there if it finds the phone you need to fastboo flash your misc partition.
Its gonna get a little complicated and require a bunch of steps. It sucks but it may fix it. I know there are already threads out there on how to fix this issue but i cant seem to find one.
When I plug the phone into the computer and power the phone on it just boot loops and the computer doesn't acknowledge it at all. In device manager there is not entry under any of the categories that says "Android..." or "unknown"
Droinc said:
When I plug the phone into the computer and power the phone on it just boot loops and the computer doesn't acknowledge it at all. In device manager there is not entry under any of the categories that says "Android..." or "unknown"
Click to expand...
Click to collapse
Crap i forgot you need to be able to boot the phone to enable usb debuging for the pc to see it. Um now im not sure what to do. Mabey format the sdcard fat32 and try the ruu again. I need to think about it, it will come to me.

Bootloop, Recovery loop!!! ADB/FASTBOOT/HBOOT HELP!

Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message <bootrom> [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
ragus15 said:
Hey guys,
Here's the basic situation. I got this phone from a friend who knows nothing about flashing/rooting/etc. And yet he had flashed the phone with MUIU and ended in a bootloop. I fixed it for him. A month later my friend decided to flash it from Verizon to Frawg. Apparently a customer rep did the whole thing for him, long story short, it is stuck in a boot loop with the white HTC screen.
I figure the boot.img is corrupt. It also goes straight to a the white HTC screen loop whenever you select recovery or factory reset from HBOOT.
I have tried PB31IMG.zip flashing (multiple stock/recovery imgs/ROMS with no luck) - its S-ON btw.
I have tried fastboot adb which I am fairly knowledgable in, I know the environmental paths, and the drivers are correct, it all works with my other androids.
When flashing any ROM/recovery image/anything, I always get a failure message stating its missing signatures. This occurs when using fastboot recovery (path) commands to flash individual recovery images as well as the fastboot boot and fastboot update PB31IMG.zip commands.
I have tried to S-Off using HTCDEV method. But even when attempting the fastboot oem get_identifier_token I get a failure bootrom message [ERR] Command error!!!
RUU is no luck... even charged it says I have less than 30%battery error, when I get it to work after erasing cache on adb, it will say resetting bootloader, and once it has reset the phone, the phone ends up connecting via USB with a black screen as CDMA technologies to my pc. RUU then says USB has been disconnected. I can only access the USB driver while in HBOOT and FASTBOOT.
So basically the microsd flash method, adb flash method, and RUU are no goes at this point unless there's something I am doing wrong (I have been researching so many different forums, and discussions and have found a handful like my situation with no solution.
This is a last cry before I render my friends phone a paperweight. Thank you for anything! :good:
SPECS:::
INCREDIBLEC XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.10.07.07
JULY 23 2010,10:06:51
Click to expand...
Click to collapse
Try this ruu its the newest officially signed ruu, so it will work with s-on. http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Trygon said:
I'm having a similar problem, but after using the PC-side RUU program, the PC reported the installation as failed while the phone hung on black screen with a full progress bar and 'htc', along with a single exclamation point at the end of the bar. When I unplugged the phone from the computer, it returned to the HBOOT screen where there were a number of phone elements and 'OK' in blue text, above a partition error and write failed message.
I did a battery pull to try the RUU's 'advanced recovery', and the phone now no longer boots.
I have no idea what shenanigans this is. No kernel screen, HBOOT is inaccessible, no charging light while plugged in, I've tried different SD cards and without any... I can't get it to respond at all.
Halp?
Click to expand...
Click to collapse
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
cmlusco said:
Sorry but it sounds like the phone is bricked, and unrecoverable. If it wont boot, or boot to hboot, there really is no way to even try anything. Does it turn on at all?
Click to expand...
Click to collapse
Holy cow, props on the quick reply. You're pretty much confirming my fears. I've tried a few combinations of battery and usb connections, but there's no vibration nor ADB signal.
I can't say I've ever seen a stock utility behave this way, so user beware. It's also worth noting that I have no history on this phone's modifications - Just that it was S-ON and locked when I got it, in bootloops between kernel and ROM, and attempting to access recovery looped it too.
cmlusco said:
Try this ruu its the newest officially signed ruu, so it will work with s-on. Place it on your sdcard in no folders and boot to hboot. It should find the file and prompt to press vol up to install. If it errors or dosent find it backup and format your sdcard fat32 with a pc and try again.
The reason the fastboot identifier dosent work is because you need to be on the 1.02 or 1.07 hboot to be able to unlock it. The ruu above will give you 1.07.
From there you can unlock the bootloader, fastboot flash recovery, and flash su thru recovery, then you will be rooted. Then if desired you can downgrade and get s-off.
Click to expand...
Click to collapse
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
ragus15 said:
Good news and bad news,
Good news: upgrade worked, and I was able to unlock the boot-loader via HTCDEV.
Bad news: I can flash recoveries all day long, boot images, etc via fast-boot and it shows the bars when flashing on my phone. But when I click recovery, I still get a white HTC splash screen. I think that the NV.img was messed up being that they flashed Frawg or Straight talk over to the network. What can I do? As far as I know there is no way for me to S-OFF, am I softbricked? Maybe there is a way to repair the kernel? IDK, any suggestions at this point would be amazing.
Click to expand...
Click to collapse
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
cmlusco said:
The ruu should have flashed a correct nv img. Have you tried flashing amon ra recovery, or did you see if you could access the stock recovery after you did the ruu?
Click to expand...
Click to collapse
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
ragus15 said:
I can retry the RUU to make sure it was correctly downloaded. After the 1st RUU attempt, I still had a straight to white htc screen loop when choosing the recovery. I have tried Clockwork, stock, and Amon Ra recoveries via the fastboot flash recovery recovery.img method and also the fastboot boot recovery.img methods.
Click to expand...
Click to collapse
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
cmlusco said:
Did you try erasing recovery before flashing?
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Can you boot to the os or no?
Click to expand...
Click to collapse
I have tried fastboot erase recovery followed by the flash and still get the white HTC image. I am not able to boot the os... i get white HTC splash image over and over, and the USB driver that tries to mount to my desktop in the bootloop is not Android 1.0, it is CMDA technologies. I have no idea what that is or if that has to do with the previous frawg/straight talk flash attempts.

[Q] Revolutionary Rooted stuck in boot loop no recovery

Help. My phone is stuck in a boot loop. No recovery, won't take one even when I flash multiple ways. Won't take a rom. S-off. Was rooted with Revolutionary, but since it wouldn't take a ROM or recovery I tried to unroot. Was able to remove the "Revolutionary" watermark, change hboot from 6.16 to 2.16.0001. Tried installing ruu which is what removed the Revolutionary and changed back hboot.
Here's what I have now:
Supersonic evt2-3 ship s-off
hboot 2.16.0001
Radio 2.15.00.0808
Any help! Thanks.
Looks you might have to get a PC36IMG.zip on your sdcard and then flash that through bootloader
Ideally, put on a froyo PC36IMG so that rerooting is easier if you want to do it again
So what happens when you try to select Recovery from Hboot?
The advice is free....the bandwidth, not so much
Still boot looping...
CNexus said:
Looks you might have to get a PC36IMG.zip on your sdcard and then flash that through bootloader
Ideally, put on a froyo PC36IMG so that rerooting is easier if you want to do it again
Click to expand...
Click to collapse
Already tried that...
FinZ28 said:
So what happens when you try to select Recovery from Hboot?
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
All I get is the white "HTC EVO 4G" boot screen. When I flash a custom recovery, everything goes as expected, but still can't access recovery.
You will have to go through all the bootloader ruu's till you find the one that works. Good luck I had the same issue and ended up selling it on eBay and the buyer finally got it working.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
You will have to go through all the bootloader ruu's till you find the one that works. Good luck I had the same issue and ended up selling it on eBay and the buyer finally got it working.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Ok. I tried every ruu I could find. Problem remains. Also, s-off never turns to s-on. Tried flashing contents of stock rom separately. Everything appears to flash ok, but same result: no recovery, no rom. Any ideas?
What I think I need is a method to nand unlock via fastboot or hboot. Anyone know of such a thing? Anyone have any other ideas? Besides what I've already done? Thanks...
mabulok said:
What I think I need is a method to nand unlock via fastboot or hboot. Anyone know of such a thing? Anyone have any other ideas? Besides what I've already done? Thanks...
Click to expand...
Click to collapse
S-off is nand-unlocked...run an ruu (any version), as soon as it opens, press windowsKey+R and type "%temp%" then *enter
Now sort the files by date modified and search in the most recent folders for a file called "rom.zip", as soon as you find that copy it to your desktop
Rename the rom.zip to "PC36IMG.zip" and place it on the root of your phones sdcard (you may need to reformat your sdcard to FAT32, make a backup if you need to do this)
Now put the sdcard in your phone, pull out the battery and go into bootloader (VolDown+Power) , the bootloader should find it and commence the update process back to stock unrooted, follow the prompts and press power when necessary
Okay, tried that...
CNexus said:
S-off is nand-unlocked...run an ruu (any version), as soon as it opens, press windowsKey+R and type "%temp%" then *enter
Now sort the files by date modified and search in the most recent folders for a file called "rom.zip", as soon as you find that copy it to your desktop
Rename the rom.zip to "PC36IMG.zip" and place it on the root of your phones sdcard (you may need to reformat your sdcard to FAT32, make a backup if you need to do this)
Now put the sdcard in your phone, pull out the battery and go into bootloader (VolDown+Power) , the bootloader should find it and commence the update process back to stock unrooted, follow the prompts and press power when necessary
Click to expand...
Click to collapse
Tried your method using the rom from an ruu. Still s-off, although everything appeared to have updated. I've done this previously, but not extracting the rom.zip from an ruu. Each time the hboot updates, or downgrades, depending on the ruu, but s-off remains. No rom, no recovery...
Next...
Sometimes the problem is solved by wiping the recovery partition first, and then re-flashing it. To do that, you would need a Hboot where you could run fastboot commands, since you cannot boot into a Rom.
You can try upgrading your Hboot, then unlocking the bootloader using the Htcdev site, so that you can run the fastboot commands. If it fails on the new Hboot, then it can probably be flashed back to whatever Hboot you have, since you're S-OFF.
I've included the Hboot file that you would need for the upgrade. You would first run the PC36IMG file throught the bootloader, then reboot the phone. If the Hboot changes, then you should go to the Htcdev site and try to unlock the bootloader.
There are some other steps that follows, but there's no point of giving them to you now and complicating things unless the initial steps work first.
Update
shortydoggg said:
Sometimes the problem is solved by wiping the recovery partition first, and then re-flashing it. To do that, you would need a Hboot where you could run fastboot commands, since you cannot boot into a Rom.
You can try upgrading your Hboot, then unlocking the bootloader using the Htcdev site, so that you can run the fastboot commands. If it fails on the new Hboot, then it can probably be flashed back to whatever Hboot you have, since you're S-OFF.
I've included the Hboot file that you would need for the upgrade. You would first run the PC36IMG file throught the bootloader, then reboot the phone. If the Hboot changes, then you should go to the Htcdev site and try to unlock the bootloader.
There are some other steps that follows, but there's no point of giving them to you now and complicating things unless the initial steps work first.
Click to expand...
Click to collapse
Ok. This didn't work. I was able to flash the hboot, but fastboot commands did not work. I can unlock, and relock the bootloader, flash any ruu, but s-off remains, and still unable to flash a rom or recovery.
Try this and see what happens: Unzip the fastboot.zip file in side a folder on your computer and place the recovery.img file in that same folder on your computer, then open a command prompt from that folder (shift + right click+"open command window here"). From the FASTBOOT USB menu on the phone (Hboot + click on FASTBOOT): type
fastboot erase recovery <ENTER>
fastboot flash recovery recovery.img <ENTER>
fastboot reboot-bootloader <ENTER>
shortydoggg said:
Try this and see what happens: Unzip the fastboot.zip file in side a folder on your computer and place the recovery.img file in that same folder on your computer, then open a command prompt from that folder (shift + right click+"open command window here"). From the FASTBOOT USB menu on the phone (Hboot + click on FASTBOOT): type
fastboot erase recovery <ENTER>
fastboot flash recovery recovery.img <ENTER>
fastboot reboot-bootloader <ENTER>
Click to expand...
Click to collapse
That didn't work either...

Htc 10 , No Rom Installed Help

Good Day, first time posting so here is the huge problem i have.
1 - My power button no longer works
2 - No ROM installed
3 - Vol buttons work
So due to an error on my part i wiped my system , data, delv/cache , and because i was rushing i rebooted the phone before installing the new rom. Now normally i would just boot into recovery and flash a rom, but my power button no longer works. I can get into download mode if the phone dies by holding vol down and plugging into a pc, and such can use fastboot commands, but with no Rom i cant get USB debugging to use "adb reboot recovery" . Is there anyway that i can get into recovery or a way to flash stock recovery, system and such. thanks in advance.
Bloodx32 said:
Good Day, first time posting so here is the huge problem i have.
1 - My power button no longer works
2 - No ROM installed
3 - Vol buttons work
So due to an error on my part i wiped my system , data, delv/cache , and because i was rushing i rebooted the phone before installing the new rom. Now normally i would just boot into recovery and flash a rom, but my power button no longer works. I can get into download mode if the phone dies by holding vol down and plugging into a pc, and such can use fastboot commands, but with no Rom i cant get USB debugging to use "adb reboot recovery" . Is there anyway that i can get into recovery or a way to flash stock recovery, system and such. thanks in advance.
Click to expand...
Click to collapse
Have tried an ruu? I suggest using the sdcard method. Safest.
andybones said:
Have tried an ruu? I suggest using the sdcard method. Safest.
Click to expand...
Click to collapse
i havent tried that, i thought i need stock recovery and to relock the bootloader for RUU, can you explain "SD card method" .
Bloodx32 said:
i havent tried that, i thought i need stock recovery and to relock the bootloader for RUU, can you explain "SD card method" .
Click to expand...
Click to collapse
No you don't need to lock bl. Or need stock recovery, That's outdated info.
Sure:
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
andybones said:
No you don't need to lock bl. Or need stock recovery, That's outdated info.
Sure:
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
thanks alot, i will give this a try. i can just get the latest RUU from HTC website and be fine right?
Bloodx32 said:
thanks alot, i will give this a try. i can just get the latest RUU from HTC website and be fine right?
Click to expand...
Click to collapse
Absolutely. Are you soff or son?
If son Id have to double check about locking bl but I'm quite sure that's very old info, and ruu has the stock recovery and just overwrites w.e you have
And soff you 100% don't need to mess w anything.
I'm soff/locked bl and flash ruu all the time. :good:
HTC website may even have directions but not sure.
RUU wiil wipe internal ste
andybones said:
Absolutely. Are you soff or son?
If son Id have to double check about locking bl but I'm quite sure that's very old info, and ruu has the stock recovery and just overwrites w.e you have
And soff you 100% don't need to mess w anything.
I'm soff/locked bl and flash ruu all the time. :good:
HTC website may even have directions but not sure.
RUU wiil wipe internal ste
Click to expand...
Click to collapse
i am s-on
Bloodx32 said:
i am s-on
Click to expand...
Click to collapse
Oh shoot I was thinking backwards, sorry. You need be stock ruu to turn from soff to son.
You can flash ruu np son, but it must match your cid/mid - Carrier ID / Mosel ID.
well its like a brick now anyway, im not sure if i did the CID "111111" , something like that a long time ago. well ill see what i can do, thanks for all your help
Bloodx32 said:
well its like a brick now anyway, im not sure if i did the CID "111111" , something like that a long time ago. well ill see what i can do, thanks for all your help
Click to expand...
Click to collapse
That's "SuperCID" and iirc you need soff to achieve, I have it as well set to that. It allows you to flash any ruu to your device.
Very welcome, mention me if you are in need of anything else.
andybones said:
That's "SuperCID" and iirc you need soff to achieve, I have it as well set to that. It allows you to flash any ruu to your device.
Very welcome, mention me if you are in need of anything else.
Click to expand...
Click to collapse
so i just tried "fastboot flash zip ruu.zip" and got security error , so i did "fastboot oem lock" but now i cant lock the bootloader cuz i cant press power to confirm, i will try to put it on the SD card and try to see if it'll auto flash. but other than that any other ideas? just for educational know how, im planning on ordering new a new power/vol flex cable anyway.
Bloodx32 said:
so i just tried "fastboot flash zip ruu.zip" and got security error , so i did "fastboot oem lock" but now i cant lock the bootloader cuz i cant press power to confirm, i will try to put it on the SD card and try to see if it'll auto flash. but other than that any other ideas? just for educational know how, im planning on ordering new a new power/vol flex cable anyway.
Click to expand...
Click to collapse
Dang yea I think you did f need the vol for SD method... Shoot.
But you don't need to lock bl..
That's not correct line: you need to be in rebootRUU mode.
I'm just gunna copy and paste this from vzw thread, applies to all.
"Option 1
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!"

Categories

Resources