EDIT: I got past the original issue. Please see post #4 instead,
I'm trying to determine if my hardware has gone bunk or whether it's repairable system errors.
_____________________________________________________
Original post:
Hi guys,
I see several recent posts about similar topics but I can't begin to troubleshoot because I can't get past the bootloader.
Here are my specs from the bootloader screen:
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.10.07.07
Jul 23, 2010, 18:06:51
I use ClockworkMod recovery, but I can't remember the last ROM I had installed, it might have been MIUI 2.3.2.
___________
When I try to start the phone normally it just hangs at the first white "htc Incredible" screen. Tried without an SD card inserted: same behavior.
If I boot into hboot instead and try to launch Recovery, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
If instead, from hboot, I try to Factory Reset, it goes to the white "htc Incredible" screen and hangs indefinitely, whether SD card is in or out.
At this point I can't get past the white "htc Incredible" screen no matter what I do.
____________
I issued the "oem enableqxdm 0" command through fastboot to ensure the SD card could be mounted, then took a fresh SD card and loaded the Stock_inc_4.08.605.15 image from dinc.does-it.net and flashed it in hboot. It loaded the image, went to "Parsing…" for a few seconds, then reset to the main hboot screen (not sure if that means it was successful). Still the same outcome: stuck on the first white "htc Incredible" screen, whether simply powering on, launching recovery, or trying to factory reset.
The phone had some previous issues I can describe if anyone thinks it would help (bootlooping unless I held the phone in the freezer long enough to launch AnTuTu and underclock the CPU way down, suggesting a heat issue).
Really I would just like to get some data off of a few saved Nandroids, if I can get the phone working again as a toy for tinkering with that would just be a bonus.
Can anyone tell what my problem is?
Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.
PonsAsinorem said:
Sounds like your recovery is borked somehow. Try fastboot flashing your recovery again (I recommend latest TWRP), and start over.
Click to expand...
Click to collapse
Thanks for the reply.
I tried flashing the stock recovery image (4.08.605.2) through fastboot but I kept getting the "FAILED (remote: not allowed)". I was able to load it as a .zip through the bootloader though. After rebooting and entering recovery through hboot the recovery partition would flash open, then immediately restart to the white "htc Incredible" screen again where it would hang as long as I let it.
I did notice it was getting really hot just sitting at that white screen so I popped it in the freezer to cool off for a minute. When I opened the freezer a minute later BOOM it's sitting at the home screen, fully booted. Keeping the phone in the freezer, I've since been able to reflash CWM 5.0.2.0 recovery and load my saved Nandroids. As soon as the phone is out of the freezer for 1-2 minutes it does and goes back to the white "htc Incredible" screen and either hangs or bootloops.
So right now I'm running back and forth between the freezer and the charger trying to load each of about a dozen Nandroids, backup my photos, call and sms logs, and move on to the next one. Seems like this method will at least allow me to get my saved data out of the Nandroid backups even if it takes all night.
Two questions:
1) It seems like the phone has a hardware overheating issue. After rescuing my data, I'll probably try to load an undervolted/underclocked kernel to see if it will stay alive under a reduced load...any input on the best choice for such a ROM & kernel?
2) To access my nandroid backups, do I need to load them on to this specific phone? Is there a runtime environment or can BlueStacks or something allow me to virtually load a nandroid backup from my dinc for purposes of getting the data off?
Thanks again.
Here's the situation now:
EDIT: phone went in the trash, life is less stressful.
Related
I was playing with my splash screen and boot animation, and I changed the PB31IMG file on my sd card to a custom splash image. I went to hboot (.92 i think) and it gave me the error "no image found" or something like that. I turned off the phone, and tried to boot up into hboot again by holding volume down+power. As soon as I did, my phone vibrated maybe four times and stayed at a black screen. I can't turn the phone on now, or boot into recovery. Has this happened to anyone else? More importantly, does anyone know how to fix it?
Just to add more information (Im really not sure what's relevant), I was running virtuous 2.6 with hydra #1, 2.15 radio. Also, the image error happened before when I was trying out a different splash screen. That time I deleted the file and re-transfered it my sd card. Hboot was able to recognize it as a splash screen when I rebooted it that time. I'm not sure, but my phone might have booted into clockwork recovery after hboot checked the img file.
One other thing that might be a problem was that I might've been running low on battery. I didn't check, but it was the end of the day and I'm usually almost dead by the time I charge it again.
Never mind.
(Unrevoked forever wiki)
When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Hi, got a serious that I can't figure out, on day 8 with no change. Here's the details
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.16.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.00808
Mar 8 2011, 17:02:15
The phone is unrooted. This is my sisters phone and I took out the battery without turning off the phone. (I do it all the time with my touchpro2, will never do it again!) I put my SD card in and turned it back on and now it's in a reboot loop. It starts up, shows the white screen with the htc EVO 4G then reboots to the same thing over and over. I could get into the bootloader. I tried all of the options. Recovery just goes to the white screen again with the htc evo 4g logo and starts the reboot loop. I did clear storage, and when it reboots it starts the loop too.
I tried loading the PC36img.zip file to a formatted sd card and the phone reads it but doesnt give me any prompts to install or anything, it just goes to the regular bootloader screen, and recovery still doesn't work. I tried loading some shipped roms but I think Im on the latest rom so it won't let me install any roms because I'm not rooted. I get an error 140 -bootloader version error. What else can I do? I am so stressed over this and my eyes are killing me from all of the seaching. I tried setting up sdk and adb but couldnt get it to work and don't think it would read my phone cause it won't start up to set up the debug mode.
nuffstylez said:
Hi, got a serious that I can't figure out, on day 8 with no change. Here's the details
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.16.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.00808
Mar 8 2011, 17:02:15
The phone is unrooted. This is my sisters phone and I took out the battery without turning off the phone. (I do it all the time with my touchpro2, will never do it again!) I put my SD card in and turned it back on and now it's in a reboot loop. It starts up, shows the white screen with the htc EVO 4G then reboots to the same thing over and over. I could get into the bootloader. I tried all of the options. Recovery just goes to the white screen again with the htc evo 4g logo and starts the reboot loop. I did clear storage, and when it reboots it starts the loop too.
I tried loading the PC36img.zip file to a formatted sd card and the phone reads it but doesnt give me any prompts to install or anything, it just goes to the regular bootloader screen, and recovery still doesn't work. I tried loading some shipped roms but I think Im on the latest rom so it won't let me install any roms because I'm not rooted. I get an error 140 -bootloader version error. What else can I do? I am so stressed over this and my eyes are killing me from all of the seaching. I tried setting up sdk and adb but couldnt get it to work and don't think it would read my phone cause it won't start up to set up the debug mode.
Click to expand...
Click to collapse
Use 4.65 RUU
Try the latest 4.54 RUU and run it through FASTBOOT USB (click on fastboot with your phone connected to your computer.
http://www.filesonic.com/file/40834....15.00.0808_NV_2.15_release_220182_signed.exe
okay, I downloaded the latest RUU which is the one I am on now 4.54.651. Ran it and it loaded up and went through the whole process. I got so happy. When it finishes, it reboots and starts the loop again. I also put the correct PC36IMG file on my SD card and it found it and the phone loaded it. But still the same thing. I dunno what to do next. I also tried the UnlockBootloader thing from HTCDEV. But when I get to step 8 to enter the command, the phone gives an error. But the computer finds the phone in fastboot. Now I definitely see why people S-Off their phones
if the phone is under 1 year old then you have the warranty which is still good unless theres water damage or proof of you internally modifying the phone or intentionally broke it physically.. tell them it froze so you pulled the battery and it got in a loop and factory reset doesnt work
Yeah, pretty simple. it's an unrooted phone. Just trade it in
the phone shows water damage even though it works perfectly. From what I read, I think the boot file is corrupted but I can't load a new one. Why is it when I load a factory RUU, it doesnt load the new boot and recovery file to get the phone working again.
nuffstylez said:
the phone shows water damage even though it works perfectly. From what I read, I think the boot file is corrupted but I can't load a new one. Why is it when I load a factory RUU, it doesnt load the new boot and recovery file to get the phone working again.
Click to expand...
Click to collapse
When you loaded the factory RUU, it probably did flash a new boot image and the stock recovery (which is useless at this point). The RUU was a last resort (the reason why I said try it), and if it did not fix the issue, then the problem is more likely hardware related.
Is there anything I could do with a program I found online called CDMA workshop. Looks like it has lots of features to work with.
Update: I thought I got it fixed. I downloaded a 4.54 rom from scottsrom.com and put it on a SD card and renamed it PC36IMG. It actually loaded it up this time, then said Parsing... [SD ZIP] and had [1] RADIO_V2
[2] RECOVERY, all the way to [8] SYSTEM. This never happenend before. So I got all happy and it updated all 8. But when it rebooted, it still did the reloop over and over. I got so happy that I finally got it fixed but it didnt do anything. What could it be? If anyone is in Queens, NYC and could fix this for me, I am willing to pay.
At this point, it seems like you have the bad blocks error, which is not fixable
I have a rooted (S-OFF) Droid Incredible running CM7. Just yesterday it started to get very laggy. I decided to reboot, which it did. However, upon reboot it failed to recognize the SD card. The phone then timed-out to the lockscreen, and I could not get it to wake up. Ocassionally, when pressing the power button, the 4 capacative touch buttons will light up & give feedback, but the screen remains off.
I started it into HBOOT & attempted to boot from Recovery, but it simply looped back to the main menu. It also briefly flashed a screen with green text stating "No Image!" in a number of directories. (This screen lasted for less than a second, so it is hard to recall exactly what it said).
I rebooted normally and was able to operate a few apps, but the SD card remained unrecognized. Once it timed-out to the lockscreen, I was back to the unresponsiveness. All I can do is remove the battery & reboot, but I get the same results every time.
Any help or guidance you may be able to provide is GREATLY appreciated!!
First i would reformat the sdcard fat32 with your pc. Then i would reflash cwm recovery thru hboot http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip, and then wipe everything in the mounts and storrage menu. Then restore a known good backup or flash a fresh rom. If that dosent fix it i would do an ruu.
What possibly went wrong (you can skip it if you guys like, I'm not entirely sure if it'll be helpful but I just wanted to be thorough.)
My G2 was working fine for the past year and I had it rooted and running CM since I can remember having it. No problems have ever occurred for me on this phone until today. I woke up and was checking my email on the gmail and yahoo mail app but the yahoo mail app kept crashing so I decided to force close it with Manage Applications and tried to reopen it, but then my phone froze. This was all going on while some of my other apps were updating. I waited for a good 30 minutes but nothing happened so I decided to pull the battery out.
My issues and what I've tried:
So my issue now is that whenever I boot my phone up again the HTC logo would show up like usual but when it transitions to the Cyanogenmod logo with the arrow circling around the Droid icon it becomes a black screen instead or it might be that the phone turns off (I cant tell but to be more specific no lights are on when this happens such as the home or menu button, etc.).
The next thing I tried is to boot into Hboot and do a recovery, but when I run recovery the same thing happens as above. The HTC screen shows up and then it goes into a black screen (I'm almost certain this isnt a hardware issue because I've never damaged my phone enough for the screen to have issues).
Seeing that recovery was hopeless, in a desperate attempt I tried to factory reset the phone through hboot, but it restarts my phone and just hangs at the HTC logo screen indefinitely. On top of all this, whenever I plug the phone to an outlet, the orange led light lights up for a few seconds and then turns off which indicates my phone isnt charging or loses connection with the cable so maybe it's a hardware issue after all?
I've spent the past 4-5 hours trying to find posts with people who've had similar situations, but either the issue was unresolved or the solution provided wasn't specific enough for me to follow (I am next to clueless with software mods). Please help me, I cannot afford a new phone at the moment and will be pretty screwed if I don't get this fixed by Monday. Thank you guys so much in advance!
A little info:
I'm running Cyanogenmod 7.2 I believe, it's the recently updated one.
This is what I see (excluding the options like fastboot, etc.) when I boot my phone while holding vol-
Vision pvt eng s-off
hboot-0.76.2000 (pc1010000)
microp-0425
radio-26.02.01.15_m2
eMMC-boot
Aug 20 2010, 16:51:01
see if you can pull a logcat while booting lopping/black screen
also you can try fastboot. try this
you need fastboot.exe from sdk (in tools or wherever)
open cmd from here (windows hold shift then right click in that folder)
in cmd type
fastboot devices
if your phone pops up you good to proceed if you get waiting for device we need to test some more
if good, continue (in the same folder as fastboot.exe have a recovery image, name it recovery.img)
in cmd type
fastboot -w
then
fastboot flash recovery recovery.img
then
fastboot reboot bootloader
(maybe its fastboot reboot-bootloader)
any way once back to hboot on your phone see if recovery works
Sent from my HTC Vision using xda premium
I'm pretty sure I tried this already, but I just tried it again. Rebooting bootloader makes my phone hang at the HTC screen. I used the img from the clockworkmod site directly and everything worked fine up until the reboot so I guess technically nothing worked :/.
I pulled the battery out and booted into Hboot and then recovery. It still becomes a black screen. Thanks for your help though. I would make a log but I dont know how, mind showing me the steps? Also I'm not 100% sure, so correct me if I'm wrong, but my case isn't with boot loops right? My phone doesnt restart over and over again by itself, it just sort of goes into a black screen and stays there for eternity. It's probably a distinction without a difference though, nothing works.
Would love some help, please. I have a completely stock HTC One M8 for Sprint. Last night I plugged in the phone to the AC charger (still had ~70% charge) and went to sleep. This morning the charge indicator was green as usual, but pressing the power button did nothing. Unplugged the phone from the charger and the LED remained green.
Tried press-hold power button for 10 seconds: no effect.
Tried press-hold power button and volume down. Select HBOOT, then RECOVERY. The phone vibrates and shows me the skateboarding androids, then reverts to the FASTBOOT menu.
Tried press-hold power button and volume down. Select HBOOT, then FACTORY RESET. The phone vibrates and shows me the skateboarding androids, then reverts to the FASTBOOT menu.
Tried requesting an Unlock_code.bin from HTCDev, then use fastboot to flash that. I see the transfer bar on my phone for an instant, but otherwise the display does not change. Still indicates *** LOCKED *** even though the fastboot command returned "OKAY".
Tried using abd.exe to list devices - none listed. Though fastboot.exe does return my serial number.
:fingers-crossed: Tried pres-hold power+volUP+volDWN for 2 minutes. Phone booted as normal, I swiped my unlock on the touchscreen, HTC Sync saw my phone, then the screen went black and I couldn't get it to boot. Sorry I did not notice what charge level the battery was in the GUI for the ~10 seconds the phone was on.
S-On
HBOOT-3.16.0.0000
RADIO-INVALID_VER_INFO
OpenDWP-INVALID_VER_INFO
OS-1.54.651.8
update - still won't boot, but ...
Update: still won't boot, but now I can get recover mode to run. Tried wiping cache partition and rebooting. Now it boots to the HTC (android) logo, then the Sprint animation plays, then the HTC One animation plays, though the audio portion only plays for the 1st second and cuts off suddenly. Then it just hangs there forever. I left it for an hour at that point just to make sure it wasn't booting really slowly.
Any way to boot from something on an SD card so that I can at least get my userdata partition backed up?
astaples said:
Update: still won't boot, but now I can get recover mode to run. Tried wiping cache partition and rebooting. Now it boots to the HTC (android) logo, then the Sprint animation plays, then the HTC One animation plays, though the audio portion only plays for the 1st second and cuts off suddenly. Then it just hangs there forever. I left it for an hour at that point just to make sure it wasn't booting really slowly.
Any way to boot from something on an SD card so that I can at least get my userdata partition backed up?
Click to expand...
Click to collapse
Sorry to say this, but all your data is gone since you factory reset from bootloader, that always wipe your phone. What recovery you had when you pressed it, if it was custom like trwp your internal sd is more likely corrupted. The easier option to get the phone back to working state is to run ruu if there is any for Sprint.
tominozh said:
...all your data is gone since you factory reset from bootloader, that always wipe your phone. What recovery you had when you pressed it, if it was custom like trwp your internal sd is more likely corrupted.
Click to expand...
Click to collapse
Thanks for the reply. Actually I listed my attempted fixes in order... i.e. I was able to get the phone to boot once for a few seconds - long enough to see my personal home screen and photos - after I had clicked on that factory reset option.
I have a theory. The RAM is bad. That would explain why sometimes it will partly boot and then get stuck, other times it will get stuck in a bootloop to the fastboot menu, and other times (only one time so far) it will completely boot. Also, if I go to the RAMDUMP option, at the bottom of that screen it shows mostly non-ASCII characters and vibrates every ~5 seconds. If I go to IMAGE CRC, it sometimes instantly shows 0x0 next to each device, other times takes a while to calculate believable values for each, and other times won't display anything and freezes.
Think that's plausible? Suppose there is any way to boot from sdcard and retrieve my userdata partition? I did not have a sdcard in when this originally happened, so all my family photos are in userdata and I haven't backed up since my 4-year old's birthday party last weekend.
Any way to get my userdata off this phone, or do an in place upgrade without hosing m
Anyone? Help?