Database Users

HTC incredible endless boot loop

i have a non-rooted HTC incredible, however it's stuck in an endless boot loop. I can enter recovery, but that's about it.
any suggestions as to what i can do?

hard reset may work
Sent from my Incredible using XDA App

i tried hard resetting it. this did not solve the problem.

ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App

jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
i am the second owner of the incredible, and apparently, the warranty only applies to the original owner.

Are you root?
When and how did this start happening?

jdkoreclipse said:
ok. if you are not rooted, take ot back to big red and get a replacement. from what i hear, the incredible is not that well made. i know that on my inc-- sometimes haptic feedback gives out, sound gives out, amd it overheats
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sounds like you got a bad one. Mine is perfect. No issues.

JaydenR said:
Sounds like you got a bad one. Mine is perfect. No issues.
Click to expand...
Click to collapse
im actually thinking of taking it back and getting a moto droid. i love the dinc, but it is poorly made.
Too bad i cant return, as i got it on release day. maybe if i can pick a good fight with the vzw guy, i could swap it out.
Sent from my Incredible using XDA App

JaydenR said:
Are you root?
When and how did this start happening?
Click to expand...
Click to collapse
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?

RUU
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.

theanswer said:
i'm not rooted. i was just using the phone normally and then it randomly rebooted. now it's stuck in a loop.
do you guys think if i apply a manual non-rooted update it would fix the problem?
if yes, where can i get a link to download this?
Click to expand...
Click to collapse
edit: post is useless.
Sent from my Incredible using XDA App

Try the RUU that was posted.

jdmba said:
You should try running any of the stock RUU's; maybe even the most recent one (although I make no warranty; and this is at your risk). Perhaps your reboot loop is a heat related issue due to a faulty radio which is working too hard.
http://www.shipped-roms.com/shipped/Incredible/
has the RUU's although it is not clear as to how long.
I am on my 2nd incredible; first one overheated and would then would do a 4-13 white screen / black screen / white screen / ... until it would move on.
Click to expand...
Click to collapse
these RUUs require the phone to be turned on though. i cant get past the boot screen

theanswer said:
these RUUs require the phone to be turned on though. i cant get past the boot screen
Click to expand...
Click to collapse
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App

jdkoreclipse said:
download the downgrade image. it will be found in the ota thread in the dev section.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html

theanswer said:
just want to confirm, you want me to follow this:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App

jdkoreclipse said:
put this on the root of ypur sd card, boot into bootloader, and let the phone do the rest. YOU MAY LOSE ALL DATA
http://www.mediafire.com/?yum40znzwmmmtyl
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.

theanswer said:
just tried this, and it did not solve the problem. any other suggestions?
thanks for the help btw, i really appreciate it.
Click to expand...
Click to collapse
ruu, hard reset, and stock img, that is it. Your dinc is hosed. I hope you have insurance??? (this is the part where you say yes)
Sent from my Incredible using XDA App

Welp
While it may not help you, it can't hurt to say. I was having huge reboot issues ... highest number was 13 initial white screen / black screen cycles. I could also NEVER get into Recovery (I could get into HBOOT but when I chose recovery, it would do TWO reboots, the second being full). A battery pull was usually needed.
However, the one thing that allowed me into recovery, etc., was to let the phone charge overnight to 100% and let it be. In the morning, the phone was charged and cool. At that point, I could easily get into recovery, start up, etc.
While I am sure you have tried this; just wanted to note to make sure your phone is cool and you did a battery pull for at least 10 minutes.

I too have this issue
I also have a stock incredible that I bought second hand, which when i bought it, I checked to make sure the device was ok. When I activated it like 2 minutes later it entered a reboot loop. I thought it might be a botched PRL so I went to the Verizon Rep (I met the seller at vz store) and he performed a forced activation. It continued the reboot loop so I took it home. I noticed that if I was outside or near a window, the phone would act normally. I used this discovery to root it and install a recovery. I flashed a few kernel/rom/radio combinations including stock rooted but there was no luck. I flashed back to RUU and it continued to reboot loop. The next day I reversed the activation back to my Eris. 20 minutes later the phone is perfect. I reactivated the device and it commenced rebooting immediately. I took it back to the store and they noted the same behavior. I'm pretty sure it's a faulty radio but since it wasn't activated on the original # they couldn't warranty it. They did tell me if the original owner activates it, they will warranty it so were gonna do that. I hope nobody else has this issue, but if you have this problem, try RUU, and if that doesnt fix it, it's likely hardware failure

Day one and im bricked..

Just jumped ships from sprint and got my facinate. Today rooted with one click and tried installing clock work. Thmanage rom manager. All seems well then suddenly my phone freezes for ten minutes I have to do a battery pull. Phone wont boot in anyway or form now. No lights or signs of life other than if I hold the power button as long as its pressed. A device labeled SEC S5PC110 Test B/D appears in device manager. And that'd all it will do. Thinking about exchanging it tomorrow afternoon. Just letting the community know what happened to me any thoughts as how or what happened might be able to help future mishaps

I'd try doing an odin flash. Just search the forums for the step by step. If u can get the phone into flash mode.

Yeah dude, definitely try Odin. Did you try flashing cwm from within ROM manager? I ask because that doesn't work for our phones yet, and it wouldn't surprise me if that could cause problems. I would use Odin to flash it back to stock, and then use the very thorough guide on here on how to get cwm going.
Sent from my SCH-I500 using XDA App

hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major

illtema said:
hilarious post title.. good luck tho man. my only word of advice (tho it won't help u now) is to run back ups before you do anything major
Click to expand...
Click to collapse
Hard for him to do a backup when he got bricked installing CWM LOL

Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....

I would think that if newer fascinates were boot locked, so would mesmerizes and I first flashed the stock files for Verizon on my phone then went to elements zinc (which is awesome BTW) installed voodoo 1200 kernel and everything is working great for me. Could just be that he got a bunk phone or something

PhoenixPath said:
Possibly bootlocked.
Newer Fascinates seem to be locked. Don't know if there is any way to tell which you've got without attempting a modification of the system....which would of course, result in the above nastiness....
Click to expand...
Click to collapse
I'm thinking it's just Noob users who are bootlocked...

My phone is only a week old everything went fine root,cwm...

wisconsinated said:
I would think that if newer fascinates were boot locked, so would mesmerizes
Click to expand...
Click to collapse
Why would you think that? Same hardware!=same software...or we'd all be running USC's kernel/ROM.
Could just be that he got a bunk phone or something
Click to expand...
Click to collapse
Could be...which is why I said "possibly" instead of "definitely".

Couldn't get to the flash mode even to use odin, went back today and bestbuy swapped it out for me thinking I just got a bad phone, I could also shake the thing and hear raddling with the usb door shut to so im not really surprised. The new one seems to be working better already, eill try root tonight,

Jwahlg said:
I could also shake the thing and hear raddling with the usb door shut
Click to expand...
Click to collapse
Volume toggle. I bet the new one does it.
good day.

chopper the dog said:
Volume toggle. I bet the new one does it.
good day.
Click to expand...
Click to collapse
He's right, the volume rockers rattle like a sumbitch.
Sent from my SCH-I500 using XDA App

My Fascinate is just twp weeks old and One Click and CWM worked just fine for me. BTW I am running JTs super clean rom. Lovin this phone!
Sent from my SCH-I500 using XDA App

This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App

ksizzle9 said:
This is why manufacturing companies are locking down phones now. That phone wasn't bricked it could have easily been fixed. OP. Please read and try to learn what u r doing. As well try to have a semi understanding of how u can fix ur phone if u mess it up. I would bet that your phone could have been up and running in 15 minutes.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
x10
This is counter development long term.
I further submit that in the future, all root processes require a ten question exam on the users knowledge to work.
Sent from my SCH-I500 using XDA App

Mine crashes sometimes. Even with all original OS. I just pull the battery and all is good.
My volume rocker doesn't rattle, so there is that plus.
Sent from my SCH-I500 using XDA App

HELP! I think I bricked my phone...

I need help before I go to my last resort of taking my phone to Verizon to be replaced. I have rooted my droid 2 and was running and old version of fission 2.1 I think. Tried flashing the new version of fission after wiping data, cache, dalvik, battery status etc. I followed the directions perfectly and when it was done it was stuck on Moto logo. Tried a few things like pulling battery etc and decided I needed to resort to SBF. I have SBFed this phone before with no problems but this time I think I may have pulled the USB cable out at the very end of the SBF process without realizing it. The screen went black and no longer had the transferring info on it so I thought it was done. When I tried to boot it up the screen will flash on for a second or so with no text and then shut off. I tried holding the UP key while booting to get back to SBF again and the screen just shuts off...
Is there ANYTHING else I can try or might work before I take this back to verizon? I really dont want to resort to that and dont want them to think I have been rooted and deny me a new device... PLEASE HELP....

RammiKan said:
I need help before I go to my last resort of taking my phone to Verizon to be replaced. I have rooted my droid 2 and was running and old version of fission 2.1 I think. Tried flashing the new version of fission after wiping data, cache, dalvik, battery status etc. I followed the directions perfectly and when it was done it was stuck on Moto logo. Tried a few things like pulling battery etc and decided I needed to resort to SBF. I have SBFed this phone before with no problems but this time I think I may have pulled the USB cable out at the very end of the SBF process without realizing it. The screen went black and no longer had the transferring info on it so I thought it was done. When I tried to boot it up the screen will flash on for a second or so with no text and then shut off. I tried holding the UP key while booting to get back to SBF again and the screen just shuts off...
Is there ANYTHING else I can try or might work before I take this back to verizon? I really dont want to resort to that and dont want them to think I have been rooted and deny me a new device... PLEASE HELP....
Click to expand...
Click to collapse
Thats really bad, i think at the end SBF flashs the bootloader and the recovery modules and such. i cant think any other ways of recovering, if im wrong, someone please correct me

Ouch... never even heard of that happening. My D2 fell off my desk a few weeks back, while I was in the middle of an sbf, and it was fine afterwards. The sbf failed but I ran rsd lite again and it was good. Guess I got lucky.
Instead of going to the store, you can call to try and get a replacement. I called after the incident above, and told them my micro usb port wasn't working anymore. They overnighted me a replacement with no questions asked...
Sent from my DROID2 using Tapatalk

YOU DONE GOOFED.
No but seriously, this doesn't sound too good. Hopefully someone knows how to get you out of it. Good luck.

Hold down x+power on.
Sent from my Squidlied Droid 2 using Tapatalk Pro

What kind of backup are you running. Can you absolutely rule out a dead battery at this point, I don't know how long you've been messing with it. I've heard of some d2 users using charge only instead of pcmode. What mode were you in. What does it do when you plug it in to a wall charger. Sorry if this is redundant just trying to get a good feel for your problem and rule a few things out till maybe somebody more of a help than me comes along.
Sent from my Squidlied Droid 2 using Tapatalk Pro

lizard1 said:
What kind of backup are you running. Can you absolutely rule out a dead battery at this point, I don't know how long you've been messing with it. I've heard of some d2 users using charge only instead of pcmode. What mode were you in. What does it do when you plug it in to a wall charger. Sorry if this is redundant just trying to get a good feel for your problem and rule a few things out till maybe somebody more of a help than me comes along.
Sent from my Squidlied Droid 2 using Tapatalk Pro
Click to expand...
Click to collapse
You are a genius. My battery must have died in the middle of the SBF. I swapped out the battery with a charged one and it booted to the bootloader. The SBF said that it was corrupt but I plugged it back in and ran it again and it worked. Thanks for saving my droid!

Even a blind squirrel finds a nut every now and then!
Glad I could help out. Best of luck with the phone.
Sent from my Squidlied Droid 2 using Tapatalk Pro

[Q] <Issue><Please Help> Droid X at Bootloader Screen

I tried installing the Gingerbread update, and when I installed both Parts 1 & 2, then rebooted, my phone only goes to the bootloader screen. Tried using RDS and that, and couldn't find my phone. So I'm stuck.
My phone boots now with a red Moto logo and then goes to the error screen.
My question is, what will Verizon say when they see it? I'm going to take it there later today. I'm under insurance but hacking voids that I believe.
What should I say to get it replaced at no cost?
I was going to say that I put it down, and then when I checked it later it was off, and then when I tried to boot it, this happened, saying I didn't hack it, maybe someone else got it.
Would that work?
Speedy answers would be great.
Thank you so much.

DO NOT TAKE IT TO VERIZON.
Look at the stickies, there is a thread about fixing your phone. You need to find the stock firmware and flash it with RSD.
Sent from my DROIDX using XDA Premium App

Also, the "I put it down" excuse will only work if you get a retard. Anyone who knows about Android will know what you did
Sent from my DROIDX using XDA Premium App

Did you install the Motorola drivers before attempting an SBF, just Google "Motorola drivers".

Well I have funny news for you guys.
I actually saw your messages after I got back..but thank you for your time.
But the guy...bought the story. He said I was probably recieving a bad update, and was able to fix the phone.
The guy was awesome though, after, he could tell it had ben rooted, and said, "yeah just know that root won't work on Gingerbread", which he installed for me.
So problem solved.
The extent of how lucky I was is amazing.

Well good deal. I'm glad he was cool. You can root, you just have to sbf back to froyo first
Sent from my DROIDX using XDA Premium App

If you mess up your phone when you are messing with it, you are responsible for fixing it. Not Verizon.

salsabettis said:
If you mess up your phone when you are messing with it, you are responsible for fixing it. Not Verizon.
Click to expand...
Click to collapse
Not sure why you're posting this now.
And I think i'm gonna stay away from rooting right now.

If you do ever decide you want root get the bootable linux cd with the automated scripts to sbf with. It is totally painless.
My DroidX Thrives on the DarkSlide!!

Atrix Warranty work? (GPS not locking)

I think my GPS is fubar... I've reinstalled my custom rom and from fresh the GPS is still having problems locking to satellites. It sees them, but can't lock for a long time, then it only locks 4/5 my xoom and my gf's atrix gets to lock on within seconds and 9/10 and i'll be at 4/9
sooo, I'm gonna put a stock ROM on and see what happens... if still problems, I want to take it back and have them try to replace it or something...
but here is the problem. it's unlocked boot, and also got CWM and stuff...
how can I bring the phone back to it's factory setting? just like how I got it from AT&T...
I want to see if I can have AT&T just replace it with warranty or something...

Before you get into any of that, here's a fix that worked for me. I was experiencing the same problem, until about a week ago when I tried this:
Go to settings --> Location and security --> uncheck "Use Wireless Networks".
Now, just turn on GPS like normal and see if it locks.
My guess is that the phone should override using wireless networks while locking on GPS, but it doesn't.
Sent from my MB860 using XDA App

razorseal said:
how can I bring the phone back to it's factory setting? just like how I got it from AT&T...
I want to see if I can have AT&T just replace it with warranty or something...
Click to expand...
Click to collapse
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.

I have the same issue and I just started the warranty exchange process (second time, first time was due to the phone rebooting constantly). I tried all sorts of things to troubleshoot - wifi on/off, removing battery for 15 minutes, running GPS utility apps, etc. Nothing worked - the GPS does not provide a fix.

henrys01 said:
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
Click to expand...
Click to collapse
Even if it is unlocked? I'm afraid they might see the "unlocked" message on boot and reject my warranty. I have muffled sound issue so I need to do an exchange.

bleuiko said:
Even if it is unlocked? I'm afraid they might see the "unlocked" message on boot and reject my warranty. I have muffled sound issue so I need to do an exchange.
Click to expand...
Click to collapse
The unlocked text will be gone

henrys01 said:
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
Click to expand...
Click to collapse
After all sorts of Magic, it still wont work.
Is there an sbf file you can link me to?
iirc its done via RSD
If anything ill do it and see how the gps acts.
I do have an sbf file but honestly i dont know if its ginger or froyo, so imdont wanna risk it. Lol

my GPS takes forever to lock now when it used to only take a few seconds.
But after a few minutes it locks on. still though..annoying. Ive gone back to using my old garmin

Thank you for your kind comment. Lol
But does anyone have link to gb sbf? And i think I need radio along with it?
Sent from my Xoom using Tapatalk

If you have to send it in, I don't think they care about it unless it is liquid or physical damage. I've sent in two unlocked and rooted phones no prob. Even told them I had done it to make sure that I didn't get the replacement charge.

Would they give me a replacement at att store? I assume not. They probably do t have them anyways...
There is no way I'm paying that deductible either far as I know rooting does void the warranty so...
Sent from my Xoom using Tapatalk

henrys01 said:
You can flash the stock gingerbread SBF and you'll be 100% back to stock. I've done this on two different phones (coming from cm7) and was able to warranty. You'll only hard brick if you flash a froyo SBF once you've upgraded to gingerbread. Gingerbread to gingerbread is OK.
Click to expand...
Click to collapse
I just SBF'd a 2.3.4 and now i'm stuck on boot loop... it goes to ATT logo and then resets to the moto one...
crap.

No. They have to send it out, and they send out a refurbished phone, but at least it works. Just call and try it. They never charged me any fee. They told me all that they we're concerned about was liquid and physical damage. Just tell them up front. You might be surprised.

chrism.brunner said:
No. They have to send it out, and they send out a refurbished phone, but at least it works. Just call and try it. They never charged me any fee. They told me all that they we're concerned about was liquid and physical damage. Just tell them up front. You might be surprised.
Click to expand...
Click to collapse
So there is a DSC in certain areas (Device Support Center) and what they do is, if they can't fix your phone on the spot, they give you a new one. which is what they did for me.
sweet!