Related
SOLVED
So, I did a silly thing
I rooted my new Incredible using Unrevoked 3.21 and it worked like a dream. Super impressed with how easy it was compared to when I rooted my original Droid. I decided I wanted to run Cyanogen Mod, since I loved it on the Droid.
The mistake I made was thinking I could install like I did on my Droid - I juts downloaded Rom Manager and downloaded and told it to install the latest version. Now I know that was bad.
My phone now boots only to the white HTC Incredible splash screen and sticks. The only way to power down is to pull the battery. If I pull the battery, and boot using the volume + power button, it vibrates 3 times and the screen goes black.
If I plug it into my computer while it's stuck on the white splash screen Unrevoked will pick it up and start the push. I thought awesome, because it rebooted it back to the hboot screen -- but then it restarted again and stuck on the white splash.
Then I tried stoping unrevoked at the hboot screen and trying clear storage and i tried recovery when that didn't work. Pushing the power button to select the option makes the phone vibrate once and go back to the white splash.
Am I doomed? I tried a Froyo RUU and it can't find it via USB. I'm feeing antsy with no phone and a little nervous I wrecked my Incredible.
Hmm, I've heard there are ways to manually recover via USB, but I'm not sure of how to do it. Also, how long have you let it sit at the HTC screen. Many roms take about 7-10 mins on the first boot and may seem like they are frozen.
If I try booting using power + volume it pulses (vibrates) 3 times and the screen stays black.
Maybe take a look at this.
androidforums.com/incredible-support-troubleshooting/187107-3-vibrates-no-recovery.html
Thanks, so now I can get into hboot - when I volume down to select 'recovery' it vibrates one and goes to the white splash screen again. Then, it goes black with white bars on the right and left sides
jensenist said:
If I try booting using power + volume it pulses (vibrates) 3 times and the screen stays black.
Click to expand...
Click to collapse
Holding volume up and power enables Qualcomm diagnostics (vibrates three times). Pull the battery and put it back in then hold volume down and power. That should get you to hboot.
Sent from my ADR6300 using XDA App
Yea I've made it into hboot now, but it doesn't seem to do anything? It goes to the white HTC Incredible screen, or a black screen with two white bars.
Are the some zip files I should have on my SD Card?
Ok, I found this thread: http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=806734
But the recovery file linked is a dead link?
EDIT: Think I found the file needed: http://www.dougpiston.com/files/Recovery/
in there. Trying to put that on the card now.
Update: I used the file from the thread I found and this time it actually came up withs ome prompts. once I opted yes, though, it went back to the white HTC Incredible screen.
Am I missing anything else? That recovery file is the only thing I've put on the SD card. Do I need any other images?
Call *611 and get a refurb. something happened. same thing happened to me. I flashed shadowrom(not blaming this rom) and instead of booting up i hear 3 beep, black screen flashing green notification light. only way to pull batt. then i try turn on, 3 beep same ****.. weird enough, i could plug it in, get a red light turn it on, and use it fine, i was s-off, this turned me to s-on somehow, and when i had the phone booted finally from having it plugged in, once rebooted, samed 3 beep, and if i tried turning it on while plugged in and pulling the cord before fully booting, it would do the 3 beep, i just got a refurb for this, just flash the signed PB31IMG.zip file to set it back to s-on and stock recovery...
I've got recovery working. Now I just need a backup file to restore to or a stock image or something, I think.
If you have recovery working you're good to go
jensenist said:
I've got recovery working. Now I just need a backup file to restore to or a stock image or something, I think.
Click to expand...
Click to collapse
Step 1: Download this file: http://www.mediafire.com/?n3bmd2bkz55k1b9
Step 2: Connect your phone to your computer.
Step 3: Save all of the files on your sdcard to a folder on your computer.
Step 4: Format your sdcard to fat32.
Step 5: Place the "PB31IMG.zip" file that you downloaded onto the sdcard in the bottom directory.
Step 6: Power down the phone.
Step 7: Hold the volume button down while pressing the power on button. (This will place you in HBOOT)
Step 8: HBOOT will find the file on the sdcard named "PB31IMG.zip" and ask if you wish to update with it. Answer yes. (It will start to load and restart HBOOT and scan for the file again, don't panic, let it do it's thing.)
Step 9: When it is finished it will ask you to reboot the device, press volume up to reboot.
Step 10: Remove "PB31IMG.zip" from the sdcard.
Courtesy of dadicus at http://forum.xda-developers.com/showthread.php?t=760306
I just cleaned it up a bit and made sure it works. This will revert your phone to complete stock 2.1 to include the recovery, radio, splash, etc, ready to receive the 2.2 OTA. After this, just run unrevoked again. Any problems/questions, let me know.
Well. Doomed I think.
It was going through the install like you described, I left the room. Came back to a black screen. Let it sit for a bit. After awhile I decided to go ahead and try a restart. Now, joy of joys, the buttons on the bottom light up but the screen stays black like it's booted up but unresponsive. Can't use the volume + power reboot at all now, I don't think. I'll keep trying.
jensenist said:
Well. Doomed I think.
It was going through the install like you described, I left the room. Came back to a black screen. Let it sit for a bit. After awhile I decided to go ahead and try a restart. Now, joy of joys, the buttons on the bottom light up but the screen stays black like it's booted up but unresponsive. Can't use the volume + power reboot at all now, I don't think. I'll keep trying.
Click to expand...
Click to collapse
Since you already did a restart, tried a battery pull? Detected in adb?
I read a quote once (forget from where), it's not doomed till it doesn't power on.
I haven't tried adb -- I'll have to wait til I get home. battery pull doesn't seem to make a difference. Buttons at the bottom vibrate as I run my finger over them and are responsive - just can't see anything on the screen :\
Ha, I like that quote. And while it sucks breaking stuff, I always learn the most when I've wrecked something to the point I don't think I'll be able to ever recover lol
Not sure how I'm going to try ADB though. Looking at this post: http://forum.xda-developers.com/showthread.php?t=709220
I need access to my phone, and I can't get it. I might actually be doomed now. I'll keep researching. If anyone has tips, they're appreciated.
jensenist said:
Ha, I like that quote. And while it sucks breaking stuff, I always learn the most when I've wrecked something to the point I don't think I'll be able to ever recover lol
Not sure how I'm going to try ADB though. Looking at this post: http://forum.xda-developers.com/showthread.php?t=709220
I need access to my phone, and I can't get it. I might actually be doomed now. I'll keep researching. If anyone has tips, they're appreciated.
Click to expand...
Click to collapse
adb is good to know. It'll let you edit your phone and manipulate it when it's connected to the computer. Very good if your screens broke, and it's quicker than just typing in commands on your phone. Assuming your device is detected, at least. Once you get it up and running, try the command
Code:
adb devices
Well it looks like it's detected. I'm at work, and while they block the USB ports so I can't do anything with the device it is saying "Hey you've connected something, it'll charge but you can't use it"
So hopefully when I get home I can ADB in and fix this nonsense.
I am a little confused why volume+power doesn't do anything, but oh well. Onward!
So I'm not super certain what I did. But I pushed volume and power until it booted, I now appear to be back to stock 2.2 thanks to the img PonsAsinorem linked -- but when I try and make a call it says verizon can't validate my phone.
They give a #8899 number to dial, but I want to ask here what's up before I call it and get an operator that's like "YOU ROOTED AND MESSED UP YOUR PHONE, DIE!" or something less or more severe
EDIT: Nevermind, I called anyway and it took 2 seconds for them to get it back on. I am back at stock 2.2 and working!
I was switching from Skyraider 3.3 to CM and I accidentally hit Restart Recovery while in Clockwork.
The phone vibrated 5 times then black screen and flashing green light.
Every time i try to get into recovery I get 5 vibrations, a black screen, and a flashing green light. Sometimes I can see the recovery screen for a split second.
I can do a battery pull and get into Hboot from optical, but that's it.
I cant flash any PB31IMG's for some reason.
I tried flashing both a Clockwork recovery and a RUU, but no go.
I tried using the RUU exe and it game me a error about not connecting to phone even though I was in Hboot with usb connected.
Also, today Rom Manager notified me about an update to Clockwork and I told it to update, but this was only supposed to take effect when i boot into Clockwork from Rom Manager.
What should I do? (besides call Verizon for a refurb)
K... so i tried using unrevoked to push a new recovery and it wont run from hboot.
but, i can get into recovery now IF the phone is plugged into usb and unrevoked is at "waiting for device."
if i unplug usb then it does the 5 vibrations w/ black screen and flashing green blinker.
problem is the phone wont mount sdcard.
i saw other people having problems with new CW, but mine still says 2.5.0.5
Bad SD Card?
RMarkwald said:
Bad SD Card?
Click to expand...
Click to collapse
Tried three.
daftlush said:
Tried three.
Click to expand...
Click to collapse
the vibrations/green light typically are Qualcomms diagnostic signal and comes from pressing vol UP/ power.........what cures this for me is a battery pull and making sure my fat fingers press vol DOWN / power to get into recovery properly. not sure if this is a fix for your problem, but worth checking.
wwjdd44 said:
the vibrations/green light typically are Qualcomms diagnostic signal and comes from pressing vol UP/ power.........what cures this for me is a battery pull and making sure my fat fingers press vol DOWN / power to get into recovery properly. not sure if this is a fix for your problem, but worth checking.
Click to expand...
Click to collapse
It's a Qualcomm mode or error code for sure since the phone comes up as "Qualcomm something something" in device manager. Still, dont know what happened to it but I'm damn sure it's fkkked.
I already have another refurb on the way. So my new question is...
If I had the "dev hboot" that i think allows fastboot, would I have been able to fix this phone by flashing a rom from my comp instead of sdcard.
If so, what are the down sides of having a dev hboot?
Same problem here. Rooted fine, then tried to load CM7 on it and it wouldn't boot afterwards.
I can get it to boot while the USB cable is plugged in but as soon as I pull the cable the phone vibrates and shuts off. Tried everything I could find to fix it, no luck. Going to have to go back to verizon.
The phone shouldn't be broken but there seems to be no way to bring it back
daftlush said:
It's a Qualcomm mode or error code for sure since the phone comes up as "Qualcomm something something" in device manager. Still, dont know what happened to it but I'm damn sure it's fkkked.
I already have another refurb on the way. So my new question is...
If I had the "dev hboot" that i think allows fastboot, would I have been able to fix this phone by flashing a rom from my comp instead of sdcard.
If so, what are the down sides of having a dev hboot?
Click to expand...
Click to collapse
FinalBoss said:
Same problem here. Rooted fine, then tried to load CM7 on it and it wouldn't boot afterwards.
I can get it to boot while the USB cable is plugged in but as soon as I pull the cable the phone vibrates and shuts off. Tried everything I could find to fix it, no luck. Going to have to go back to verizon.
The phone shouldn't be broken but there seems to be no way to bring it back
Click to expand...
Click to collapse
Literally just got the green light of death last weekend, it's most likely toast. YOu can turn your phone on and flash a rom when the phone is plugged in to the computer. For me, SD was unreadable (phone defect, sd is fine), and emmc wouldn't mount via usb, and adb wouldn't work either.
They refurbed me no questions asked.
BTW, the .77 fastboot-enabled hboot is only for AMOLED Incredibles. You'll really have a brick if you flash to an SLCD phone. I don't think fastboot would help anyway, as it's most likely a hardware malfunction.
wdfowty said:
Literally just got the green light of death last weekend, it's most likely toast. YOu can turn your phone on and flash a rom when the phone is plugged in to the computer. For me, SD was unreadable (phone defect, sd is fine), and emmc wouldn't mount via usb, and adb wouldn't work either.
They refurbed me no questions asked.
BTW, the .77 fastboot-enabled hboot is only for AMOLED Incredibles. You'll really have a brick if you flash to an SLCD phone. I don't think fastboot would help anyway, as it's most likely a hardware malfunction.
Click to expand...
Click to collapse
I don't know about that...I have an SLCD handset and I flashed .92 with no issues whatsoever.
daftlush said:
I was switching from Skyraider 3.3 to CM and I accidentally hit Restart Recovery while in Clockwork.
The phone vibrated 5 times then black screen and flashing green light.
Every time i try to get into recovery I get 5 vibrations, a black screen, and a flashing green light. Sometimes I can see the recovery screen for a split second.
I can do a battery pull and get into Hboot from optical, but that's it.
I cant flash any PB31IMG's for some reason.
I tried flashing both a Clockwork recovery and a RUU, but no go.
I tried using the RUU exe and it game me a error about not connecting to phone even though I was in Hboot with usb connected.
Also, today Rom Manager notified me about an update to Clockwork and I told it to update, but this was only supposed to take effect when i boot into Clockwork from Rom Manager.
What should I do? (besides call Verizon for a refurb)
Click to expand...
Click to collapse
Sounds like your SD card isn't formatted fat32..... it has to be or hboot won't read the PB31IMG.zip try reformatting
Sent from my Incredible using XDA App
I have hboot 0.92 on there now, I think I have the SLCD version (about a month old). Not home right now, will check when I get there.
I tried running urevoked while it's plugged in and functional but it says "communication issue" so I can't flash a custom rom or restore a backup. There has to be a way to bring it back, it's quite unlikely that it's damaged in any way.
As a last resort I'm going to try the RUU with HTC Sync Found steps in this thread.
http://forum.xda-developers.com/showthread.php?t=864858&page=2
FinalBoss said:
I have hboot 0.92 on there now, I think I have the SLCD version (about a month old). Not home right now, will check when I get there.
I tried running urevoked while it's plugged in and functional but it says "communication issue" so I can't flash a custom rom or restore a backup. There has to be a way to bring it back, it's quite unlikely that it's damaged in any way.
As a last resort I'm going to try the RUU with HTC Sync Found steps in this thread.
http://forum.xda-developers.com/showthread.php?t=864858&page=2
Click to expand...
Click to collapse
I have an ruu that I know works because I had to use it once if you want it just make sure you are formatted right....
http://db.tt/8YWjgVF
Here you go.....
Sent from my Incredible using XDA App
I have the five vibrate + green led problem as well.
Sounds like I'm super lucky though, I can boot into everything fine afterwards.
Running CM7, 9.01, .92, AMOLED.
-CM7 ADR6300
newtoroot said:
I have an ruu that I know works because I had to use it once if you want it just make sure you are formatted right....
http://db.tt/8YWjgVF
Here you go.....
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
No go.
I can boot the phone if the USB cable remains plugged in or if I unplug it during boot (at HTC logo). I can use it, call *228, etc. Once I plug in the USB cable, if I unplug it the phone vibrates x5/green light. I cannot mount it as USB drive on my PC, cannot run unrevoked, cannot run RUU.
I can flash it using a PB31IMG.zip through hboot. It's S-ON. It boots into default OS (2.2), it booted into CM7 before I flashed it but only with the USB cable plugged in. As soon as I unplug the cable it vibrates x5 + green light.
RUU is reporting a connection issue (error 170 USB) so I can't flash it through there.
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
FinalBoss said:
No go.
I can boot the phone if the USB cable remains plugged in or if I unplug it during boot (at HTC logo). I can use it, call *228, etc. Once I plug in the USB cable, if I unplug it the phone vibrates x5/green light. I cannot mount it as USB drive on my PC, cannot run unrevoked, cannot run RUU.
I can flash it using a PB31IMG.zip through hboot. It's S-ON. It boots into default OS (2.2), it booted into CM7 before I flashed it but only with the USB cable plugged in. As soon as I unplug the cable it vibrates x5 + green light.
RUU is reporting a connection issue (error 170 USB) so I can't flash it through there.
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
Click to expand...
Click to collapse
I hate to say it but it sounds toast bro.... if the ruu didn't fix it then it had to be a hardware problem sorry I couldn't help.....
Sent from my Incredible using XDA App
Had this happen to 3 INCs already, call for a refurb.
I'm going to get another one from VZW. Is there any way to make sure this doesn't happen again? I'll start off by not flashing CM7 in the mean time. Anybody have any suspicions on what could cause this?
I just had the same thing happen to mine this morning after flashing the HeyItsLou #9. I can only access ClockworkMod Recovery when I'm plugged in but can't access the sdcard. I've scoured multiple forums for hours and nothing seems to work. I just tried the RUU and it says "wrong image". There seems to be no reason why this happens and there's no one thing that causes it, I've read that it happens to both rooted and non-rooted users.
I filed a claim with Asurion and my new one will be here on Tuesday. It worries me a little that I can't get CWM off of it.
dpwhitty11 said:
I have the five vibrate + green led problem as well.
Sounds like I'm super lucky though, I can boot into everything fine afterwards.
Running CM7, 9.01, .92, AMOLED.
-CM7 ADR6300
Click to expand...
Click to collapse
Same here.
I just pulled the battery, rebooted into recovery then did a recovery from one of my backups.
Now I'm worried there might be a issue with CWM 3.0.0.8 or something causing this to happen to people....? I just read that CWM 3.0.0.8 is known to have issues clearing data or something when installing new ROMs ..
FinalBoss said:
Anybody else have anything I can try? So far I've:
1) Rebooted it 30 times using various button combinations (pwr+vup, pwr+vdn, pwr+v+touchpad, etc).
2) Flashed stock firmware on it.
3) yelled at it
4) Tried to flash various recovery PB31IMG.zip through hboot (fails)
5) yelled at it some more
6) listened to my gf complain about how much "Battle of LA" sucked
7) posted this
Click to expand...
Click to collapse
It would appear that it's for sure bricked if you've tried this.
OK.
I will put in a detailed info about what happened.
A week back, my wildfire's touchscreen started to function abnormally.
I was rooted and on Cyanogenmod 7.0.3
So, I flashed the phone with DK custom FROYO to make it look like sense so that the warranty is not void and took it to the HTC store.
They replaced the touchscreen for a flat fee (It was water damage according to them. But the phone was never used in wet conditions nor exposed to water)
But anyway, the phone was working fine when I brought it home from their store.
Then I flashed CM7.0.3 again.
And everything was working fine.
I OCed acc. to CM's settings to 652-352 Mhz.
And left the phone to charge in charger overnight.
When I woke up, the phone was off and there was just the red LED light blinking.
I tried to boot it again, but nothing works.
Pressing the power button does not do anything.
The phone still boots into recovery. At times.
I don't know what makes it boot into recovery. But at times it does, at times it doesn't. (Right now it's not booting into recovery no matter what I do)
Just the red LED keeps on blinking.
Please help.
I am not familiar with pushing commands onto the wildfire since I use a mac.
Please suggest any methods. If they involve using command line, I can use my windows PC for that. But please give a how-to of length enough for a noob ) ) to understand.
Thank you.
Pulz
EDIT :
I got to boot into recovery once. Tried to reflash CM7.0.3
It came to "Installing update" and then failed to go further.
Tried to install DK Custom Froyo 4.5
And it went to opening package and then failed to go further.
Now entering into a panic mode !
Red light blinking generally occurs when phone is hot and plugged in to wall socket. Is it so at that time ?
Unplug the charger or usb. Remove the battery and reinstall the battery. Try to boot into hboot mode (volume down + power) or fastboot mode (trackpad + power) . If your phone can boot into hboot/fastboot mode and has no restarts or power offs, then I think you can solve it.
Try to clear storage from hboot menu. Or factory reset from recovery once you enter it. If still it is not solved, try using "pc49img" method of flashing an RUU from the hboot menu. Hope it helps. Shouldn't help if there is hardware issue.
Sent from my Blade using XDA App
hye another noob here running on cm7.
actually i have the similiar problem my wildfire start rebooting over and over again but the cause is different.
this problem happen after i want to know what class my micro sd is.
what i do is i go to settings>storage>unmount sd card.
so after knowing the class were i insert back the card then the problem happens.
my phone start to crash then cm7 logo appear after that i enter my pin no so brought me back to the home screen after few seconds the logo appear again so i have 2 repeat the same steps...
this happen many times what i do is i remove the battery wait few hours then turn back on..
so help me if someone have the similiar problem and solutions.. thanks!!
Hey guys
I'm running MrGarak's fantastic MIUI rom however I've found that the kernel is booting my phone into that white HTC diagnostic screen by default. Unfortunately my volume down button is dead and so I can't navigate the menu; the only way I can boot my phone at the moment is to boot it connected via USB as that makes it boot to Recovery and I can reboot from there.
Any ideas? I think this and another rom I tried both used LordMUE's kernel, could that be the reason the boot preferences don't default to just booting the OS?
Any help and/or pointers would be greatly appreciated
So you can access bootloader and recovery!
So just flash another kernel. What's your problem?
Put a zip on your SD (with a SD reader or ADB pull), then go in recovery, navigate with the 4 keys under the screen (or vol+ and power)... and flash.
What is strange for me is that it seems to happen sudenly... so how do ou know it's the kernel. Anyway...
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
_david_94 said:
I have clockwork recovery, and can navigate it using the soft keys (home menu etc). You should also he able to use the vol up key to get to the bottom of the list, (depending on the recovery you're using I suppose)
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Unfortunately it boots into the white HTC area (dunno what it's called). The one where you can see if your phone is S-OFF or not.
Also, I'm not sure what is to blame... but I've only just recently noticed that my phone cold boots this way so I assumed it was a recent rom that I applied. Will test this theory later.
Sounds to me like your volume down button is stuck in.
Definitely not a ROM issue, as it has nothing to do with the bootloader.
Sent from The App that Time Forgot.
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
xtremedelta said:
Hey, i had this issue like a month ago. You can check my previous threads. It's hardware I'm 100% sure. Basically if you're in warranty you need to flash the stock rom with S-On so you can get a new phone. You can get it to boot but it's really a pain. You have to play with the volume up when first turning on your phone. It took me about an hour. Then when it boots you'll be in a "Safe Mode" (no clue whats limited all seemed fine to me). Then do your backup if you wish.
Also note: Flashing the S-On rom is a PAIN, took me about 2-3 hours of rebooting, holding vol up, tapping vol up, to get it to boot right, but with patients you'll get it to go.
Good luck to ya.
Click to expand...
Click to collapse
Ah, I'm definitely beyond warranty. The thought of vol+down being stuck down makes a lot of sense!
I'll just take it to one of the dodgy Asian repair shops, if it's a hardware issue I'm sure they'll know what to do.
Cheers for your help everyone!
hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Same problem
tekweezle said:
try a factory reset.
hold down -volume and hit power button. a menu should pop up and factory reset should be one of the choices
Click to expand...
Click to collapse
My incredible started doing this yesterday, Ive tried this option it doesn't work for me. I can get the menu but it when I choose factory reset or any of the other options it flashes the htc incredible screen and starts the loop again, any more suggestions would be appreciated.
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Htc loop
wanted167 said:
hey xda
my droid incredible won't start up.. it keeps looping on the boot up ... what can I do to solve this problem ?
Click to expand...
Click to collapse
tekweezle said:
Is your phone unlocked and rooted/s-off?
It will say so on that menu screen.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
No I was getting ready to root it the day this started. Will rooting help this problem?
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Htc loop
tekweezle said:
having CWM recovery on the device would help you clear the memory and load the OS easily. but that requires your device to be rooted.
whats strange about this case is that my understanding is that the OS is read only and the only thing that changes is data and user data held in a separate partition. so the 2 possibilities is that your user data is corrupted(probably due the space getting exhausted-were you getting a low space warning?) or less likely but possible-the OS corrupted in some way-perhaps from repeated reboots and phone use.
i guess if a factory reset isn't helping there is little i can suggest. that should do the trick if the OS isn;t corrupt because all it does is wipe away the user data so you can resetup the device as if you bought it brand new.
if you have an micro sd card in the device, try removing it. if that doesn;t work, try reformatting it and putting it back in.
Click to expand...
Click to collapse
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
SuzyQangel said:
I tried all that and nothing seems to work can I root it like this? Ive tried taking the sd out and putting it back in reformatting it still it just loops and I get the boot menu but it wont do anything in the boot menu only the power down option everything else when highlight it and hit the power button to select it just goes right back to the loop Im ready to throw it out the window lol
Click to expand...
Click to collapse
This sounds quite a bit like an Inc I have lying on my shelf. It was a friend's and he gave it to me to see if I could fix it. As far as I can tell, the phone's emmc storage simply failed. These phones are aging and that happens sometimes. Anyway, I tried all the usual stuff, including running RUU's (flashing signed PB31IMG.zip's since the thing had never been rooted and was still s-on), and yeah, just boot looped.
I did get the phone working, but it was complicated and messy. Here's more or less what I did: I was able to successfully run the RUU that updates HBOOT to 1.02 (or 1.07, either one works), which allowed me to unlock the bootloader via HTCdev. (see one of the root / s-off guides if this doesn't make sense.) This made it possible to flash ClockworkMod recovery using fastboot, and boot into recovery. From there, I was able to get to a root shell through adb (plugged into my computer) and proceeded to downgrade and get s-off, following the guide. It now works, though it's running Froyo and there is hardly any space for apps due to the messed up storage. I've been wanting to try this hack on it but I haven't gotten around to it yet.
stuck in boot loop, keys dead
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
spappy said:
I have an HTC incredible. One day the power button decided to quit working. Everything else worked fine, except when the phone went to sleep, the only way to wake it up was to plug in the charger. That was all fine and dandy til I was using it one night to listen to TuneIn and forgot to shut it off. When I plugged in the charger the next morning, it went into boot loop. I can get it out of boot loop by holding the power and/or volume down buttons, but when the hboot (?) screen comes up, I am helpless to do anything, as the power and volume buttons are unresponsive. It is not recognized when I plug it into my laptop, either. For whatever it's worth, it does say "S-on" on the hboot screen, if that helps. Is it junk or fixable?
Click to expand...
Click to collapse
Sounds hosed to me. You could try to flash an RUU zip but that'd require use of the keys in HBOOT. If there is an RUU option that does not involve touching the phone, it's possible. Otherwise, no. I guess you could open the phone and check the button connections are there but it may be locking up at the HBOOT screen. Give it a chance to charge up a bit. However, I believe this phone is a lost cause. I seem to be seeing more frequent bootloop phone reports lately.