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

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

[Q] Bricked phone?

I was running Core Droid 1.2. I WASNT flashing a rom, I WASNT flashing anything or messing with anything. I was just watching a youtube video. The phone froze. I didnt want to remove the battery as i thought it was bad. I tried finding a way to emergency shutdown my phone like volume up and down and power or something but it seems there wasnt one. I took out the battery and put it back in. I turned the phone on but all that came up was a black screen. I took it out and put it back in again. It won't turn on period.
Any ideas?

tradejak66 said:
I was running Core Droid 1.2. I WASNT flashing a rom, I WASNT flashing anything or messing with anything. I was just watching a youtube video. The phone froze. I didnt want to remove the battery as i thought it was bad. I tried finding a way to emergency shutdown my phone like volume up and down and power or something but it seems there wasnt one. I took out the battery and put it back in. I turned the phone on but all that came up was a black screen. I took it out and put it back in again. It won't turn on period.
Any ideas?
Click to expand...
Click to collapse
Read my sticky in the general section
Sent from my Infernalized Glacier!
-Team Inferno

saranhai said:
Read my sticky in the general section
Sent from my Infernalized Glacier!
-Team Inferno
Click to expand...
Click to collapse
Yeah I did. And its funny cause when i read it 2 days ago I got scared that my bad eMMC chip would die any second... now it looks like it just did.
I just posted this anyways cause I was desperate >.> but t-mobile says my warranty hasnt run out yet. And since it cant boot up whatsoever they cant tell its rooted. SO I get a free replacement
I was kind of hoping they'd claim the phone was defective and give me a sensation or something

This doesn't look like eMMC failure at all.

Jack_R1 said:
This doesn't look like eMMC failure at all.
Click to expand...
Click to collapse
what would you think it is then? My new phone comes today and i have to ship this one off to tmobile, so its too late. But I still want to know

Most likely - corrupted SBL. It doesn't necessarily mean eMMC failure - though it could be. Pulling the battery out while there is some eMMC activity could have caused it.

sorry im nooby. whats SBL and can it be fixed easily?

SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.

Jack_R1 said:
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Click to expand...
Click to collapse
I don't think that was it. He obviously could get to HBOOT by flashing PD15IMG.zip and getting failed-pu error. But I may be wrong, feel free to correct.

To flash PD15IMG, he needs HBOOT running - it's the HBOOT that flashes these files, it's the first screen on your phone that you can actually see and interact with. If HBOOT is gone, you don't boot - because you have nothing to boot to. Or actually, the phone boots to some state, but you don't know it - because you can't interact with it anymore.

invasion2 said:
I don't think that was it. He obviously could get to HBOOT by flashing PD15IMG.zip and getting failed-pu error. But I may be wrong, feel free to correct.
Click to expand...
Click to collapse
Nope. I cant flash PD15 if i cant get to HBOOT. the phone doesnt turn on at all, just a backlight for one second. Which looks like its attempting to turn on but failing.

Jack_R1 said:
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Click to expand...
Click to collapse
hmm. you'd think these phones would have some sort of fail-safe feature when it comes to pulling the battery, cause people obviously do it alot.

tradejak66 said:
Nope. I cant flash PD15 if i cant get to HBOOT. the phone doesnt turn on at all, just a backlight for one second. Which looks like its attempting to turn on but failing.
Click to expand...
Click to collapse
Ahhh my bad, sorry. Didn't read Definitely seems like you are bricked! >.<

Phone Arrived in "Factory Mode" What do I do?

So my sprint S4 arrived today and when i first booted it up it was in Factory mode... I called Tech support and they guided me to hard resetting it by going into settings and doing a factory reset, but that didnt work, also by holding volume up, home button, and power button at the same time during boot up, but that also did nothing. My only options apparently are to wait for a sprint store to get spare ones to replace mine with or pay up front for another one, and get one shipped to me and ship this one back... I'd much rather attempt to fix it myself, If i can.
Anyone know if I can root it or do a recovery with a stock rom or anything else? Ive only ever rooted one android phone and that was years ago, so im pretty rusty but I think i can handle it, im a comp science major and took an intro to unix class so i got this! haha just looking to get guided the right way, in the meantime i will continue reading rooting threads. PS: IDK if this means anything but while messing around with the buttons during boot up I entered Odin mode or something asking if i was sure i wanted to download a custom OS then it hung on Downloading... Also I navigated through the settings menu and there was no sign of a developement or USB debugging option :[ Below are screens of what it looks like.

xxdekuxx said:
So my sprint S4 arrived today and when i first booted it up it was in Factory mode... I called Tech support and they guided me to hard resetting it by going into settings and doing a factory reset, but that didnt work, also by holding volume up, home button, and power button at the same time during boot up, but that also did nothing. My only options apparently are to wait for a sprint store to get spare ones to replace mine with or pay up front for another one, and get one shipped to me and ship this one back... I'd much rather attempt to fix it myself, If i can.
Anyone know if I can root it or do a recovery with a stock rom or anything else? Ive only ever rooted one android phone and that was years ago, so im pretty rusty but I think i can handle it, im a comp science major and took an intro to unix class so i got this! haha just looking to get guided the right way, in the meantime i will continue reading rooting threads. PS: IDK if this means anything but while messing around with the buttons during boot up I entered Odin mode or something asking if i was sure i wanted to download a custom OS then it hung on Downloading... Also I navigated through the settings menu and there was no sign of a developement or USB debugging option :[ Below are screens of what it looks like.
Click to expand...
Click to collapse
AOSP???
Dude ship it back man. More edits to it will break it i think
Also it is in factory mode right ? @Chainfire lets pull Exynos Factory Sources

mithun46 said:
AOSP???
Dude ship it back man. More edits to it will break it i think
Also it is in factory mode right ? @Chainfire lets pull Exynos Factory Sources
Click to expand...
Click to collapse
Yeah its in factory mode. I guess im going to have to... :[ damnit. Gonna take forever. Oh well.. If anyone else has ideas let me know... ill be waiting a while for return packaging to arrive.

Tap on build number 10 times to get development options. Then pull me the system using adb
Sent from my GT-I9500 using Tapatalk 2

papi92 said:
Tap on build number 10 times to get development options. Then pull me the system using adb
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
Well that worked to get me developer access and enable usb debugging but can you be a bit more specific on how to pull up the adb? all i remember is having to use command line prompts to pull it up

xxdekuxx said:
Well that worked to get me developer access and enable usb debugging but can you be a bit more specific on how to pull up the adb? all i remember is having to use command line prompts to pull it up
Click to expand...
Click to collapse
adb pull /system

Why does it have AOSP theme?

mithun46 said:
adb pull /system
Click to expand...
Click to collapse
Thanks, I pulled the system folder onto my hard drive... is it safe to give this out? Its a lot of files obviously and about 250 MB :/

xxdekuxx said:
Thanks, I pulled the system folder onto my hard drive... is it safe to give this out? Its a lot of files obviously and about 250 MB :/
Click to expand...
Click to collapse
its safe. dont give the /data out
it should be more than 250 mb man

mithun46 said:
its safe. dont give the /data out
it should be more than 250 mb man
Click to expand...
Click to collapse
There's hardly anything on the Factory ROM, it isn't very surprising.
Sent from my HTC One using Tapatalk 2

humzaahmed155 said:
There's hardly anything on the Factory ROM, it isn't very surprising.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I think its AOSP

Well i uploaded my system folder onto dropbox but apparently i cant post outside links until i have 10 or more posts :/
Anyone else have any ideas on what I can do?

Post a few times?

This phone of yours is what the devs need, so they can reverse engineer it and put AOSP, CM, AOKP, etc on it.
This thread should go to some where people/devs would visit more often, so it gets more exposure and have more productive work done faster.
Here's an idea: those, who bought the qualcomm version and hoping to run CM on it, should chip in to buy this phone, so this guy can buy another phone, then send this phone to some dev.

ste1164 said:
Post a few times?
Click to expand...
Click to collapse
I guess.. easier said than done.. i dont have much to say around here except for this problem hahaha:/

jk0l said:
This phone of yours is what the devs need, so they can reverse engineer it and put AOSP, CM, AOKP, etc on it.
This thread should go to some where people/devs would visit more often, so it gets more exposure and have more productive work done faster.
Here's an idea: those, who bought the qualcomm version and hoping to run CM on it, should chip in to buy this phone, so this guy can buy another phone, then send this phone to some dev.
Click to expand...
Click to collapse
Id potentially be willing to let go of it... if people are interested in it... I have to wait til tomorrow for preorders to stop anyways and to start the order process for a replacement.. Shouldve went with the htc one :/

xxdekuxx said:
Id potentially be willing to let go of it... if people are interested in it... I have to wait til tomorrow for preorders to stop anyways and to start the order process for a replacement.. Shouldve went with the htc one :/
Click to expand...
Click to collapse
Enjoying the HTC One so far I agree with the others they can all chip in and pay for the device so it can be shipped to a dev who can pull the AOSP source off it and build a CM ROM / Standard AOSP ROM.
Sent from my HTC One using Tapatalk 2

It's a 9500 or a 9505?
Thanks.

Chuck Bartowski said:
It's a 9500 or a 9505?
Thanks.
Click to expand...
Click to collapse
He said its from sprint so I'm going to say its a 9505
Sent from my A500 using Tapatalk HD

Chuck Bartowski said:
It's a 9500 or a 9505?
Thanks.
Click to expand...
Click to collapse
Tell me how to check which one it is, and I shall

[Q] Huawei AT&T impuls 4G (U8800-51) - Flashed CM 7.2 0228 build but -

After what appears to be a successful flash of the CM 7.2 build from 02282013 all my phone will do is go to the at&t logo and sit there. Never completes the boot. I wiped data, factory reset and cache to no avail. I was on Froyo before flashing. I used CWM to flash. Never completes the bootup. I have to pull the battery to get it to shut down. I tried flashing twice with no luck.
I then tried to restore my CWM backup but it boots back into the recovery screen with the following errors:
Can't open /cache/recovery/log
Can't open /cache/recovery/log/last_log
Any ideas anybody?

pastorbob62 said:
After what appears to be a successful flash of the CM 7.2 build from 02282013 all my phone will do is go to the at&t logo and sit there. Never completes the boot. I wiped data, factory reset and cache to no avail. I was on Froyo before flashing. I used CWM to flash. Never completes the bootup. I have to pull the battery to get it to shut down. I tried flashing twice with no luck.
I then tried to restore my CWM backup but it boots back into the recovery screen with the following errors:
Can't open /cache/recovery/log
Can't open /cache/recovery/log/last_log
Any ideas anybody?
Click to expand...
Click to collapse
Are you on 2.2?
Sent from my SGH-T769 using Tapatalk 4 Beta

Somcom3X said:
Are you on 2.2?
Sent from my SGH-T769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I was on 2.2. I'm on nothing now. My last attempt totally bricked my phone and it won't even turn on.

pastorbob62 said:
Yes, I was on 2.2. I'm on nothing now. My last attempt totally bricked my phone and it won't even turn on.
Click to expand...
Click to collapse
1. Remove battery, plug in usb power cable. (means no battery in the phone)
2. Press power button, volume up, and volume down button. All three at the same time, and hold.
Did it turn on?

badiyee said:
1. Remove battery, plug in usb power cable. (means no battery in the phone)
2. Press power button, volume up, and volume down button. All three at the same time, and hold.
Did it turn on?
Click to expand...
Click to collapse
No. It does the same as when the battery is in. It vibrates as if it is going to turn on but the screen stays black and nothing else happens.

pastorbob62 said:
No. It does the same as when the battery is in. It vibrates as if it is going to turn on but the screen stays black and nothing else happens.
Click to expand...
Click to collapse
if what i read from other forums is correct, it sounds like you need a motherboard replacement.

badiyee said:
if what i read from other forums is correct, it sounds like you need a motherboard replacement.
Click to expand...
Click to collapse
That is what I figured to be the case as well. Unfortunately I am not able to locate one. Not sure if I would do that anyhow since it only cost me $140.00.

pastorbob62 said:
That is what I figured to be the case as well. Unfortunately I am not able to locate one. Not sure if I would do that anyhow since it only cost me $140.00.
Click to expand...
Click to collapse
Look on ebay. Buy one with a broken screen and replace it yourself.
Sent from my SAMSUNG-SGH-T769 using Tapatalk 4 Beta

Good suggestion
Somcom3X said:
Look on ebay. Buy one with a broken screen and replace it yourself.
Sent from my SAMSUNG-SGH-T769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've already tried that. Several times. Lots of new screens but no used phones that I can pick up for parts. I am leaning toward buying a new phone from my provider. Different model, Samsung Galaxy Exhilarate, better phone all around for only $150.00.
I'm done tweaking and modding my phones. It's okay for PC's and tablets but I think I'll stick to stock phones from now on. Lesson learned the hard way.

pastorbob62 said:
I've already tried that. Several times. Lots of new screens but no used phones that I can pick up for parts. I am leaning toward buying a new phone from my provider. Different model, Samsung Galaxy Exhilarate, better phone all around for only $150.00.
I'm done tweaking and modding my phones. It's okay for PC's and tablets but I think I'll stick to stock phones from now on. Lesson learned the hard way.
Click to expand...
Click to collapse
The exhilarate is a beautiful phone with good dev support. My blaze is compatible with the exhilarate.
Sent from my SGH-T769 using Tapatalk 4 Beta