- 7 Posts
Phone in boot loop - please help
Hi guys. Need some help.
This afternoon my phone began force closing random applications (widget locker, sms stuff, etc). When I got home, I attempted a restore using ROM manager and using my last (and only) saved restore.
Now when the phone attempts to reboot, it just goes back to ClockwordMod Recovery.
I've tried to use the "backup and restore" option in there as well, but aside from it saying sd-ext.img missing at the end of the process, the restore seems to go as planned.
I know this seems general, but I'm kind of at wit's end trying to figure this out.
Thanks in advance.
- 06-19-2011, 10:03 AM #3
- 06-19-2011, 12:22 PM #4
Some additional information....
Once the continous reboots start, if I can get the phone into airplane mode... the reboots will stop.
Then after a period of time, I can turn the airplane mode off.. and the reboots will stop. I have just noticed this effect, I have not yet figured out how much time is required.
Its happens on both Rooted Stock Froyo / and Cyanogen 7.03.
- 06-20-2011, 12:38 AM #5
First thing that comes to mind: are you absolutely sure you are using ROMs, kernals, and radios for the HTC Incredible?
The only reason I mention this is because just recently we saw someone who was trying to use something specifically for a Sprint phone (NOT something modded for the DI).
- 06-20-2011, 08:39 AM #6
I've been on the " Rooted froyo"
For a while now. I has downloaded it from this forum in one of the incredible posts.It has been working for at least 7 months and this is a recent development.
Wondering if it was just time for a hard reset, I just went ahead and downloaded cyanogen using rom manager.
If I had to take a stab at it, I would guess this weirdness started right around when verizon had their lte outage.
Twice so far I've had to call support to get the phone "re authenticated" and manually enter some access key. 228 will not work for this.
Any help is appreciated.
Sent from Tapatalk
- 06-20-2011, 09:45 AM #7
- 06-20-2011, 10:02 AM #8
I agree that would be the next step. But it's weird that the system can't authenticate you in the normal fashion.
FWIW, I don't know that going with Cyanogen is going to help. You might want to just flash back to stock, including the stock kernal, and get things working normally before doing a nandroid backup and then test-driving other ROMs.
- 06-20-2011, 10:51 AM #9
I've gone back and forth between the rooted froyo that I have and cyangen a few times.
Always selecting wipe cache and dalvik.
Isn't loading Cyanogen "equivalent" to essentially doing a "hard reset" and then loading another ROM?
I had to run all the setups over... thats why i'm thinking its considered a hard reset.
Thanks in advance guys.
- 06-20-2011, 11:18 AM #10
This could indeed be the cause of your problems.
- 06-20-2011, 03:08 PM #11
- 1,470 Posts
- HTC One (Verizon) Stock
I agree with the post above. When you install a new ROM, whether it be sense based or AOSP, you ALWAYS need to perform a factory reset. Just wiping the cache partition and the Dalvic cache are not enough.
If you are using ROM manager to install the ROM then I would say that is where the problem is. Do it manually through recovery and do the data/factory reset, cache partition, and Dalvic. If your still boot looping you may have a bad download.
- 06-20-2011, 08:05 PM #12
- 06-20-2011, 08:11 PM #13
- 06-20-2011, 08:12 PM #14
- 06-20-2011, 08:31 PM #15
- 06-20-2011, 08:35 PM #16
- 06-20-2011, 09:17 PM #17
I found the "original" rooted froyo that i'd used those long months ago.
I've also re-partitioned the sd card.. since it was already empty. NOw i'm re-downloading the images, and getting ready to do several hard resets and then loading up that original image.
I'm kinda wondering if the phone is borked... as it does seem to happen when it does any type of cellular data for any extended period. It also happens after I've been on a call for a bit and then hang up.
otherwise... thunderbolt/inc 2 etc etc...
- 06-20-2011, 11:29 PM #18
Ok its still resetting.
I've hard reset multiple times before loading cyanogen and still it resets.
I tried to load the froyo that I have and clockwork tells me its not a gingerbread version that I got to downgrade or something, anybody know the right version?
Sent from my ADR6300 using Tapatalk
- 06-20-2011, 11:34 PM #19
The really simple solution would be to flash a temporary version of Clockworkmod 220.127.116.11. Just drop it onto the root of your SD card, flash, then go ahead and flashCM7. Once you've got that up and running you can downgrade permanently if you need to (many thanks to Wanda for originally pointing this out to me). Good luck.
- 06-21-2011, 08:53 AM #20
Boot to recovery
Flash this version of clockwork
Reboot to recovery
Flash cm7 (or my Rooted froyo? )
I would think it's the froyo version but I'm not sure.
Also, if someone could tell me if I'm on the right radio. (see first post).
Thanks again guys you are great!
Sent from Tapatalk
- 06-21-2011, 09:24 AM #21
The downgraded recovery is for your rooted Froyo.
Yes you are on the correct radio.
If this does not work, you might want to punt and run the RUU (Directions in the Rooting sticky and in the preparing for Gingerbread OTA sticky) and then re-run Unrevoked.
- 06-22-2011, 09:25 AM #22
The downgrade worked to install the rooted froyo version.
Unfortunately, the rooted froyo version still does the reboot thing.
When I get a little more time, I'll have to read up on the RUU and revert to stock.
Keep you all posted.
If anyone find the magic bullet before I go that route, I'd appreciate it.
Sent from Tapatalk
- 06-23-2011, 09:20 PM #23
here is the twist... in the "how to root unroot etc " thread.. the link to the ruu pb img.zip file is broken..
in the gingerbread thread.. the file is there...
in the root/unroot.. it says I need to run someting to put s-on, but there is no mention of this in the gingerbread thread.
Is it safe to:
1 - use the s-on instructions in the first thread
2 - use the pbXXXimg.zip in the second thread
and then i'll be at froyo ota?
- 06-23-2011, 10:23 PM #24
If you run the RUU it will take you to unrooted Stock with S-Off which makes it easier to re-root. If you want the S-on zip it's in IncBits from the market as well as on unrevoked
For what you're trying to solve the RUU should be enough.
- 06-24-2011, 02:31 PM #25
Forgive my thickness.. I figure its better to ask questions and "Look Stupid", than it is to pretend I understand and do something and "be stupid" LOL.
Running the RUU will return my to a stock OS, but will leave the recovery as clockworkmod correct?
So... after I RUU, I can "just" load another ROM should I want to?