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

did i kill my epic?

i was running odin and download mode closed my phone now wont boot up or anything......
Euhmmmmm.... *poo*
just loaded and it has a pic of a cell a caution sign then a pc
*end heart-attack it decided it would work* i love the epic even more now....
PyRo
*please lock*

Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.

bullet2300 said:
Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.
Click to expand...
Click to collapse
I sort of had the same issue, but nothing I do will get the unit to power on. Plugging it in to the charger does not turn the charging light on. And no three button method is working. The screen stays black, no charging light. Suggestions?

Never mind, it did come back.

same problem
epic wont boot, charge, etc
please help

You're going to have to give us info if you want any help.
ROM, What you did right before it happened, etc.

RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.

903tex said:
RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.
Click to expand...
Click to collapse
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App

XtaC318 said:
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah we need a new word for soft bricking. Softing? Broft? Oops?

heathmcabee said:
Yeah we need a new word for soft bricking. Softing? Broft? Oops?
Click to expand...
Click to collapse
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?

How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Sent from my SPH-D700 using XDA Premium App

XtaC318 said:
How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Click to expand...
Click to collapse
you think with all the disclaimers on each and every rom,root,theme,ect that people would understand the risks involved in modding whether its a ps3 xbox360 phone router anything but all logic seems to disappear.

kennyglass123 said:
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?
Click to expand...
Click to collapse
lol
BTW its is thrown around how about saying in your thread title like stuck on a screen, errors in clockwork or other nice terms to help u more,
It is really hard to brick this thing believe me ive done it all, FCs, errors in clockwork, stuck on samsung screens boot loops and yesterday officially bricked!!!
The only reason it bricked is some charge card in a beta bonsai rom, but thats what tep is for.
And remeber if you can see something on your screen of your phone use odin or heimdell to go back to stock if you phone wont charge,gointo download mode or go on or go into recovery then its time to take it in and replace it.

Mnhertz26. Did you fix your epic too or is it another real brick?¿

I know what a brick phone is. Im just tired of people not knowing what to do asking questions that are already explanied and sticky on top of the page. Not researching will cause this problem until people realize that if you dont understand this then you need to read, read, read. I had a wm phone and if you flashed the wrong file...DONE. Atleast with the epic as long as it can get in download mode you should be fine.

brendan802 said:
Mnhertz26. Did you fix your epic too or is it another real brick?¿
Click to expand...
Click to collapse
Another real brick? So far there haven't been any Epic's that weren't recoverable.

Ouch I am so glad I did not run Bonsai on my phone yet I was waiting for i dunno what but dodged that issue.
For those who jacked thier phones but didnt brick persay make sure you have a charged battery before starting and if unabl to charge after the incident you can charge in an external charger to get back into dload mode to odin back to stock or CW flash a back-up
Peace

did i brick my phone?

used unrevoked 3 to root my phone, did a backup, then attempted to install CM6. during the process, my phone shut off (i dont believe it was the battery, as it was fully charged and plugged in). now once in awhile (rarely) if i attempt to boot into recovery, the white htc evo screen will appear for a second or two, then the phone will shut back up.
what are my options?

i wouldn't expect anyone to reply with any real answers until you are more clear about your problems & what you've done already to try & fix them. not to mention, hardware specifics..

exempt said:
used unrevoked 3 to root my phone, did a backup, then attempted to install CM6. during the process, my phone shut off (i dont believe it was the battery, as it was fully charged and plugged in). now once in awhile (rarely) if i attempt to boot into recovery, the white htc evo screen will appear for a second or two, then the phone will shut back up.
what are my options?
Click to expand...
Click to collapse
Put this on your SD card. http://db.tt/uo4mOhh remove "_RA_2.2.1" and place on the root of your SD card. Once you get the "white screen" it will re install a recovery. Just make sure you go with it in bootloader (white screen) prompts.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

drdrewdown said:
i wouldn't expect anyone to reply with any real answers until you are more clear about your problems & what you've done already to try & fix them. not to mention, hardware specifics..
Click to expand...
Click to collapse
Figured since this was the EVO forums it would be assumed I have an EVO
I havent attempted any solutions yet, as I wanted to be sure of something before trying. As for the problems, what is unclear? Rooted successfully, attempted to flash CM6 and phone went dead and no longer turns on.
So I should use something else to get it on the SD card, then try to start phone?

exempt said:
Figured since this was the EVO forums it would be assumed I have an EVO
Click to expand...
Click to collapse
Damn...I thought this post was for a BlackBerry Storm. But on a serious note, he was asking about what hardware version, hboot, etc... Hardware version 002? 003? 004? 007...wait, James Bond?

exempt said:
Figured since this was the EVO forums it would be assumed I have an EVO
I havent attempted any solutions yet, as I wanted to be sure of something before trying. As for the problems, what is unclear? Rooted successfully, attempted to flash CM6 and phone went dead and no longer turns on.
So I should use something else to get it on the SD card, then try to start phone?
Click to expand...
Click to collapse
Card reader or other phone.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!

tgruendler said:
Damn...I thought this post was for a BlackBerry Storm. But on a serious note, he was asking about what hardware version, hboot, etc... Hardware version 002? 003? 004? 007...wait, James Bond?
Click to expand...
Click to collapse
ah, that does make more sense. HW 003, HBOOT is 2.10

Rydah805 said:
Cars reader or other phone.
Sent From My HTC Evo 4G On The Now Network From Sprint Using Tapatalk Pro!
Click to expand...
Click to collapse
that fixed it! thank you!

exempt said:
that fixed it! thank you!
Click to expand...
Click to collapse
no problem. glad i could save your sanity and save you a trip to going to the sprint store then waiting an hour for diagnostics then getting a replacement when you really didn't need anything but a recovery re-flash. =]

[Q] In Desperate Need of Help! Touchscreen is Non-Responsive After Update.

Greetings to all. Last week while powering up my phone, I accidentally entered into the Bootloader screen. It found the last T-mobile update that I had done (I forgot to remove it from the SD) and I hit yes to update (at the time thinking it was a new update). After it finished with the update, my phone booted back up to the familiar "zebras" T-mobile stock lock screen. At this point, my touchscreen was, and still is, completely non-responsive.
With the very basic knowledge that I have with Androids, I searched for and downloaded many different PD15IMG.zip files (always re-named PD15IMG properly), dropped them onto my SD (one by one of course), booted into the Bootloader screen and applied the update. In every instance, when my phone finished updating and loaded the familiar zebras, same problem. I even tried a Factory Restore (several times) with the same result. Also, USB Debugging was never turned on on the phone.
Now, here is where it gets interesting: when I was looking closer at my lock-screen, I noticed that the date is set to: Jan. 6, 1980!? I am at the "end of my rope" here and am only repeating the same steps at this point as if something magical is going to happen....
Any and all help would be most appreciated!
Brian

Are you S-On of S-Off?
Sent from my HTC Glacier using XDA App

I am not sure what that means, my knowledge with these things is elementary at best. I was running a stock T-mobile rom if that answers your question.

noah1127 said:
I am not sure what that means, my knowledge with these things is elementary at best. I was running a stock T-mobile rom if that answers your question.
Click to expand...
Click to collapse
when you boot into the bootloader... at the top
does it say Glacier PVT S-On or S-Off?

Ok, just looked it up; I believe I am S-off, because I have had custom roms installed before.

....actually, it says: Glacier PVT S-On

noah1127 said:
Ok, just looked it up; I believe I am S-off, because I have had custom roms installed before.
Click to expand...
Click to collapse
you have a custom recovery installed?

I had at one point installed Clockworkmod if that is what you are asking, but to be honest, realized that it was beyond my understanding and never used it. I did never uninstall it however....I hope I am answering your questions correctly, sorry.

noah1127 said:
I had at one point installed Clockworkmod if that is what you are asking, but to be honest, realized that it was beyond my understanding and never used it. I did never uninstall it however....I hope I am answering your questions correctly, sorry.
Click to expand...
Click to collapse
You did have it installed, but you flashed other PD15IMGs right? That flash would replace the recovery to stock recovery, so I'm guessing you don't have a custom recovery.

Ok, right, that makes sense. So I would say everything is stock again.

...any advice at all?

If you are not rooted and can't get it to boot then your options are few. Warranty exchange a possibility?
Sent from my HTC Glacier using xda premium

It does boot, everything looks fine (except for the date of 1980!?), I can see the wallpaper and the "lock/unlock-bar", battery status, etc. I just can not swipe the "lock-bar" down to unlock the phone, the touchscreen is completely non-responsive.

noah1127 said:
It does boot, everything looks fine (except for the date of 1980!?), I can see the wallpaper and the "lock/unlock-bar", battery status, etc. I just can not swipe the "lock-bar" down to unlock the phone, the touchscreen is completely non-responsive.
Click to expand...
Click to collapse
Does it respond to any touches on the screen or does it just timeout and turn the screen off?
Sent from my HTC Glacier using xda premium

No response what-so-ever, it just times out and goes blank.
My gut tells me it has something to do with the date being 30 years off (1980) ...but I am new to all this!
BTW, there has been no physical damage, I have not dropped it or anything like that.
I really do appreciate your time!

noah1127 said:
Ok, right, that makes sense. So I would say everything is stock again.
Click to expand...
Click to collapse
That would be correct! Still unsure about the touchscreen unresponsiveness though...sorry.

No problem, I appreciate your time!
What about the 1980 date, have you ever heard of anything like that before?

noah1127 said:
No problem, I appreciate your time!
What about the 1980 date, have you ever heard of anything like that before?
Click to expand...
Click to collapse
I wouldn't get too hung up on it. Could just be a messed up setting... Unless you believe someone from the past is trying to communicate with you.
Sent from my HTC Glacier using xda premium

..."Unless you believe someone from the past is trying to communicate with you." I wish!
No, I just thought that like on a computer, if the date is far in the past it can mess up the "communications" within the device. The date was correct before and then after the "update" is went back to 1980, was just wondering if that is "confusing" the phone...I know it worked on me!!

eqjunkie829 said:
I wouldn't get too hung up on it. Could just be a messed up setting... Unless you believe someone from the past is trying to communicate with you.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
lmao, obviously HE'S from the past, where the MT4G doesn't exist! reason why his touchscreen won't work
well... i would wait... sometimes it might magically work again O_O