Related
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
Hey all, I hope I've posted this in the right place.
Since rooting, my Wildfire has been behaving rather oddly. The most noticable problem seems to be that if my handset is off, and I connect the charger, even in the battery is full, the orange light comes on. Following this, if I remove the charger, the light stays on permenantly, and I cannot turn the handset on until I remove the battery.
Is this a side effect of rooting, or a sign of something more sinister? If so, are there any guides to "un-root" my handset so that HTC do not recognise I voided my warranty?
Many thanks all
This happened to me as well after rooting.
I'm not sure if there is any way to fix this problem apart from unrooting.
To unroot:
Make a backup of all your apps and settings with Titanium Backup (from the market).
Download the correct ROM for your Wildfire from http://shipped-roms.com/shipped/Buzz/ (Buzz is the codename of Wildfire if you didn't know) and run the RUU.
This will restore your phone to how it was when it was new.
Restore your backup of your apps and settings with Titanium.
Cheers for the reply, just wanted to make sure that my phone isn't defective really. Only concern now is that the battery is still receiving charge even when it's full.
mine does the same.
chrispy_212 said:
Cheers for the reply, just wanted to make sure that my phone isn't defective really. Only concern now is that the battery is still receiving charge even when it's full.
Click to expand...
Click to collapse
This isn't the case with me as the light will still turn green once it is charged. It could still be charging but I highly doubt it.
Same here. What Rom are you running? i am using 1.14.405.2 (now 1.37)
Sent from my HTC Wildfire using XDA App
Try the 1.25 rom
Sent from my HTC Wildfire using XDA App
I'm on 1.14.110.1. Upgraded to WildPuzzle last night, but completely fudged my contacts and the backup was completely screwy, so I restored my nandroid backup cos I need a functioning phone today. Didn't get chance to check the charge behaviour, that's my job for tomorrow probably. Have you tried 1.25? Did it fix it?
I would but im away without my pc
Sent from my HTC Wildfire using XDA App
I upgraded to the new ROM (1.25) last night but haven't tried charging it yet. When I get in I'll try charging it and see what happens.
Sent from my HTC Wildfire
I will try to check this tonight, im on the new rom.
I can confirm that it does exactly the same thing on rooted 1.25. I am wondering if it is a problem with clockwordmod. If anyone who is having this problem could try unrevoked with amon ra recovery and report back that would be brilliant.
Sent from my HTC Wildfire
I expected as much. The ROM is mostly too high-level to impact things like the PSU. I expect you're right in that it is the recovery image. Interesting that we seem to be the only people who have experienced it. Or we're the only ones who care! I'm still getting to grips with this whole rooting business, so I'm not the best guy to install Amon Ra.
EDIT: OK, very interesting development. When the handset is off, connecting to a PC to charge produces the "stick in charging" behaviour. However, when connected, the device is detected by the PC as "My HTC," despite the handset being off.
Same thing for me after doing unrevoked3. Just funny that with original rom when turning off and charging I can turn on, but when I used unrevoked3 on the same conditions I can't turn it on. Maybe people from unrevoked3 could help us, I will try to send them email with this question.
Please do
Sent from my HTC Wildfire using XDA App
Any updates on this? I'm planing on rooting a buzz later today. Am doing all my homework now
My phone is having the same effects as your having after using the unrevoked tool.
The same here
Sent from my HTC Wildfire using XDA App
Is anyone not having this problem or is it a problem with everyone who has used unrevoked?
After unroot, my HTC works flawless. I already spoke with unrevoked dev team and they told me this is a ClockworkMod recovery problem. But, yesterday, I spoke with koush and he told me this is not a recovery problem. Now I'm confused. LOL
This only happen with rooted devices.
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
Ok so my phone was bricked and Ive been trying these past few days to fix it with odin. Odin doesnt work on my computer though. Today I connected it and odin started to work and it started to flash, it got to the factoryfs part and then froze, so I disconnected it.
Now my phone won't enter download mode and it won't turn on anymore.. what can I do?
EDITL: So i got into the sprint store and tell them that some update made my screen turn off and it wouldnt turn back on/nor charge. They were working on it for like an hour then they came to me and said that i have to pay 35$ then i can pick up a new one on tuesday. Yay and I was able to ad insurance because I didnt have it before.
I'd try just taking it back to Sprint and tell them that you were performing an OTA update and it just died in the middle of it and you don't know what to do.
Is your battery charged? Because it should at least power on
Sent from my SPH-D700 using Tapatalk
hayabusa1300cc said:
Is your battery charged? Because it should at least power on
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Im not sure but it doesnt charge even if I plug it into the wall =( And yeah ill try to go to the sprint store tomorrow, if they question me about rooting should I deny everything? Can they check if the phone is rooted?
Yeah, just play dumb and act like you don't know what happened with it, and it just went blank during an OTA update. They can't see if the phone is rooted or not as far as I'm concerned, but if you bring it to a Sprint repair shop, I'm pretty certain that they won't know.
Actually just try pulling the battery for 3 minutes,then download mode should work,then re-odin...This has happened to me 3 times,really thought it was bricked the first time.
Sent from my Frankenstein FROYO ROM using XDA App
ecooce said:
Actually just try pulling the battery for 3 minutes,then download mode should work,then re-odin...This has happened to me 3 times,really thought it was bricked the first time.
Sent from my Frankenstein FROYO ROM using XDA App
Click to expand...
Click to collapse
same thing happened to me when i first started flashing roms with this phone.. just give it alittle time, plug it in with the battery to make sure its getting a charge and it should boot back into download mode.
kalico17 said:
same thing happened to me when i first started flashing roms with this phone.. just give it alittle time, plug it in with the battery to make sure its getting a charge and it should boot back into download mode.
Click to expand...
Click to collapse
I did that and nothing happens, it doesnt charge anymore i think. Im pretty sure its hard bricked now :/
The Sprint store is going to try another battery first before they throw the towel in on the phone. If that doesn't work then yes play dumb and do exactly as previously stated by @brianhuangbh.... "Was doing an OTA and it just froze". Good luck and let us know what they said
sasha101 said:
Ok so my phone was bricked and Ive been trying these past few days to fix it with odin. Odin doesnt work on my computer though. Today I connected it and odin started to work and it started to flash, it got to the factoryfs part and then froze, so I disconnected it.
Now my phone won't enter download mode and it won't turn on anymore.. what can I do?
Click to expand...
Click to collapse
same thing happened to me, that i ended up getting another phone. anyway i was fooling around with my brick epic when i decided to put in a fully charged battery in. nothing happened but i noticed after a while that the phone was warm. i pulled the battery then waited a couple of minutes then put it back in and held the power and 1 button and what do you know, it went to download mode. i used Odin CORRECTLY this time and now it works. when using odin make sure reboot is the only box checked and that u start Odin first then plug the epic in.
So i went to the sprint store and everything turned out good
Awesome congrats hopefully the new phone doesn't act up on ya if you decide to root lol
Sent from my SPH-D700 using XDA App
tphillips78 said:
Awesome congrats hopefully the new phone doesn't act up on ya if you decide to root lol
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Im gonna stay away from rooting haha, came too close this time. Plus my computer refuses to co-operate with odin so i cant unbrick it.
Good stuff if u do decide to root feel free to pm me if u have questions. The people of xda were very helpful to me so I'm returning the favor lol.
Sent from my SPH-D700 using XDA App
First off, my tone is from frustration. I've experienced this snafu now on both versions of clockwork recovery. The phone won't completely shut off while charging. If I power the phone down unplugged, then plug it in while off, recovery boots up. If it's plugged in while powering down, recovery boots up after a few seconds.
I suppose I could flash cwm when I need it then flash back to stock recovery. I guess that's what I'm going to have to do until it might get fixed. I thought going to version 3 would fix the bug but apparently not. I've tried to flash a new recovery with rom manager but an error always happens.
I flashed version 2 the way the root guide said and flashed 3 with fastboot. I forgot if thats the way it was done with 2 or what. I am starting to wonder if I'm doing something wrong because I don't see anyone else complaining about this.
herbthehammer said:
First off, my tone is from frustration. I've experienced this snafu now on both versions of clockwork recovery. The phone won't completely shut off while charging. If I power the phone down unplugged, then plug it in while off, recovery boots up. If it's plugged in while powering down, recovery boots up after a few seconds.
I suppose I could flash cwm when I need it then flash back to stock recovery. I guess that's what I'm going to have to do until it might get fixed. I thought going to version 3 would fix the bug but apparently not. I've tried to flash a new recovery with rom manager but an error always happens.
I flashed version 2 the way the root guide said and flashed 3 with fastboot. I forgot if thats the way it was done with 2 or what. I am starting to wonder if I'm doing something wrong because I don't see anyone else complaining about this.
Click to expand...
Click to collapse
Are you looking to bump charge? You've asked this issue a multitude of times and each time its been responded to. (at least in my mind, might be others too) and it is a known issue with CWM recovery and from what I've read Koush isn't really looking at fixing it.
I can't speak for what'll happen in the future but it's not you. That is a known issue with the recoveries we currently have. I believe most of the complaints are in the how to root thread.
^ Shift Faced
I am not talented enough to "fix" the problem but it is discouraging to hear that it isn't deemed important. Maybe I was spoiled with my moment, evo, and epic. It seems as if the shift has the smallest developer base so far. When the evo came out, the devs were all over the place.
Come to think of it, I don't think I've even seen anyone besides myself that has a shift.
You don't think not being able to charge while turned off isn't really a minor problem? And you're using the Moment as a model of progress??
^ Shift Faced
That's what I started on
Yeah, me too. And every ROM was basically themed stock. No CM7, no MIUi, no cool ish like the New Sense. Jeez, they just finally got 2.2 working on it! I'd be using CM7 right now if the headphone jack worked. That ish there excites me.
^ Shift Faced
herbthehammer said:
I am not talented enough to "fix" the problem but it is discouraging to hear that it isn't deemed important. Maybe I was spoiled with my moment, evo, and epic. It seems as if the shift has the smallest developer base so far. When the evo came out, the devs were all over the place.
Come to think of it, I don't think I've even seen anyone besides myself that has a shift.
Click to expand...
Click to collapse
First..the facts show the shift as a far more superior platform to any samsung..probably even the tab..let alone its not that your problem isn't important...it just isn't to anyone but you so there is some importance..with everyone complaining about all these issues and the limited dev support maybe we should figure out whether we want a rom..a kernel..a recovery fixed or a genie in the bottle..patience is the virtue here because everyone keeps flaming about support for this and that..maybe the devs have a life..maybe they died..maybe they think its funny to see people whine and complain like they owe us some kind of development
Sent from my PG06100 using XDA App
google gave everyone a evo that went to the I/O when it comes to the devs the all had a free one from jump i too want cyanogenmod on my shift for the reason i love cyanogenmod BUT its not supported by him oficially
everydaysince87 said:
google gave everyone a evo that went to the I/O when it comes to the devs the all had a free one from jump i too want cyanogenmod on my shift for the reason i love cyanogenmod BUT its not supported by him oficially
Click to expand...
Click to collapse
Toastcfh has a CM7 where everything works but sending MMS and the headphone output. And he's been working on it everyday. And Cyanogen responded to someone asking him on Twitter if there'd be CM support for the Shift and he said "Yes, soon". I think it was on 2/17.
I have a feeling my Shift is gonna be very happy soon
^ Shift Faced
Soon isn't official yet tho I may look into a way to donate to toastcfh then
jesusice said:
Toastcfh has a CM7 where everything works but sending MMS and the headphone output. And he's been working on it everyday. And Cyanogen responded to someone asking him on Twitter if there'd be CM support for the Shift and he said "Yes, soon". I think it was on 2/17.
I have a feeling my Shift is gonna be very happy soon
^ Shift Faced
Click to expand...
Click to collapse
Sent from my PG06100 using XDA Premium App
My clockwork recovery hasn't gaven me any problems
Rob_ec said:
My clockwork recovery hasn't gaven me any problems
Click to expand...
Click to collapse
+1 and I use cwm 3
Sent from my HTC Knight using XDA App
Rob_ec said:
My clockwork recovery hasn't gaven me any problems
Click to expand...
Click to collapse
How did you install yours? Maybe your hardware version of the phone is different than mine? I bought my phone the day after it went on sale. Hardware version 4
This is the tutorial I had to follow to install my recovery..at the bottom of the page someone rewrote the 2nd command to enter and it worked for me..but I had to follow this tutorial & not the one stickied..let me know if this works..
http://forum.xda-developers.com/showthread.php?t=908267&page=6
Sent from my PG06100 using XDA App
herbthehammer said:
How did you install yours? Maybe your hardware version of the phone is different than mine? I bought my phone the day after it went on sale. Hardware version 4
Click to expand...
Click to collapse
They didn't read your post. The boot to recovery from power off while charging is univeral. Its just that very few people care very much.
Jeezimus said:
They didn't read your post. The boot to recovery from power off while charging is univeral. Its just that very few people care very much.
Click to expand...
Click to collapse
Lol +1 to not caring much
Sent from my PG06100 using XDA App
You actually turn your phone off?
there is at least now an official release of clockwordmod:
http://forum.xda-developers.com/showthread.php?t=979778
grandebob said:
You actually turn your phone off?
Click to expand...
Click to collapse
I turn it off and on no problem..I haven't tried while its plugged in..why would I even do that unless I want to boot to recovery which is what people complain about so actually its a benefit to me..
Sent from my PG06100 using XDA App