I realize this is a *common* problem but I can't find any way to resolve this! I have been searching the forums for reboot threads and haven't been able to solve this problem yet. I am quite a noob but I apologize for the length of this thread, I'm just trying to be as detailed as possible.
It all started when I flashed CM 6.0.2 stable. It ran fine for weeks and then it started to reboot occasionally on its own. It appears as though it reboots when I am doing something intensive like watching NFL mobile or starting several downloads. I tried the nightlies as well as 6.1 RC2, same problem.
I decided to try another ROM..I have tried Virtuous, Redemptive, and SkyRaider, all of which reboot a couple times the phone first boots after installation and then, they reboot randomly on their own while I'm doing various things.
I've tried the stock and custom kernels for Virtuous as well as King's Kernel BFS #5 with Virtuous. "Stock" kernels for SkyRaider and Redemptive.
Before you say anything of course I have cleared data/factory reset EVERY time before flashing a ROM. I've also cleared cache as well as Dalvik cache before I flash a ROM.
I've tried removing the SD card before the phone boots and it seemed to have helped Redemptive but it still rebooted at one point.
I rooted it with unrevoked 3 but never used unrevoked forever, although HBOOT shows S-OFF, do I still have to use unrevoked forever?
Incredible (AMOLED)
HBOOT: 0.92
ClockwordMod Recovery: 2.5.0.5
Baseband Radio: 2.15.00.09.01 (I tried 7.28 with CM, but it also had the problem, I haven't tried it again since then)
My main questions are:
(1) Should you clear the data/factory reset, clear cache, clear Dalvik, format SD-card or any combination AFTER the ROM is flashed for the first time? Is there something I'm missing here?
(2) What is the most stable ROM and/or kernel. I really don't want to go to stock but from what I remember I never had this problem on stock. I could try it again just to see if it has the problem.
(3) Should I try unrevoked forever, does it do anything differently than unrevoked 3?
(4) Would setting up ADB/logcat help diagnose the problem?
Any other input would be appreciated on how to stop these reboots. Thanks.
same here. i'm running uncommon & KK#5 and i get reboots while listening to pandora and browsing apps.
its gotten progressively worse over the past couple days, not sure what to try. going to try flashing another rom and see how that works
SD?
Couple ideas, and answers to some of your questions.
Answers:
Unrevoked3 does S-Off for you, so you don't have to do that. If it shows S-Off in HBOOT, it is S-Off.
You don't need to format the SD card w/ ROM flashes. If you do, you lose what's on the SD card. This is typically only done once - see below.
Ideas & a question/something to think about:
1] Make a Titanium Backup of all your user apps - also d/l appbrain if you haven't already, set up the appbrain account and sync it with your device. Now you have a picture of what apps are on your device.
2] With the device on, unmount the SD card, power down, and take the SD out of the device. Copy the entire SD card contents into a folder your PC so you'll have them. Format the SD card as FAT32 on the PC. (assuming you are not a mac user, in which case I cannot help...) Put the newly formatted/clean SD card back in the device.
2]Download from ROM Manager + Virtuous' stable stock ROM/kernel (included), but do not install it from ROM Manager. Reboot into recovery. In CWM, not ROM Manager, wipe data/cache & factory data reset and clear Dalvik before flashing. (you have already formatted the SD card, no need to do it again) See if issue(s) keeps happening. If so, try flashing the radio off to 7.28, then do the Virtuous +all wipes from CWM again, reload Virtuous and again and see if the issue keeps happening.
3] Go to Settings>Applications>Manage Applications ~ look thru each/every app and see if one (or many) have a ton of info in their data and/or cache. If so, clear out the data and/or cache in those apps.
4] Once you have a stable Virtuous ROM/kernel, take a look at the handy list of apps you have on appbrain - incrementally in/uninstall them to see whether any of these may be the culprit... If once you reinstall XYZ app on Virtuous' stable ROM/kernel, you may have your culprit.
5] Try a different SD card - solving for whether the SD you have is wonky.
Yep, it's a lot to do, but you want to know what is causing the reboots; ya gotta start w/ a clean slate and diagnose incremetally.
Let us know what worked (or didn't) so others can benefit from your experience.
2] With the device on, unmount the SD card, power down, and take the SD out of the device. Copy the entire SD card contents into a folder your PC so you'll have them. Format the SD card as FAT32 on the PC. (assuming you are not a mac user, in which case I cannot help...) Put the newly formatted/clean SD card back in the device.
Click to expand...
Click to collapse
I noticed that (at least in) Virtuous the browser as well as other apps use the SD card for cache. When I tried downloading files off the internet with the browser then it would crash. I changed the cache location to the phone and then it has worked fine since.
I did as you suggested, unmounted the SD card and then formatted with FAT32. My SD card was actually FAT beforehand, I think I had heard somewhere that it needs to be FAT in order to flash radios so when I was installing 9.01. Although I did have a minor rebooting problem before with 7.28, that may have been attributed to Cyanogen itself since that was the ROM I was using at the time.
So far it has been good but unless I get an uptime of at least 3 days we won't know for sure (that was about the average uptime when I had Cyanogen). If I still run into problems I'll follow your other recommendations. Thanks a lot smtom.
You are most welcome! There's a very good "Official Radio Thread" here on XDA. If you decide to flash the radio (my personal recommendation, but ymmv) read thru that thread before you flash the radio.
Also, I didn't mention, but implied via flash in CWM, to read the notes you see when the various areas are wiped. Why? ROM Manager doesn't show you all the notes, nor can you see what exactly may be erroring, if anything. Flashing in CWM is more cumbersome, but it is a LOT more informative if/when you have issues w/ your device.
I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.
AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason
Hi all,
I had CM7 on my phone (nightly build #3), which worked just fine. Today, after a reboot, the phone wouldn't start. The CM7 logo shows up, stays there for a while, after which the screen turns black and nothing happens. I tried going into the recovery menu to do a restore of a working backup, I've tried wiping the data and cache, I've tried pretty much anything. Nothing seems to work. When performing the restore, I get the following error: "error while erasing boot image", along with some other errors about the phone not being able to mount the cache partition or something (see image below). The only thing that I've done before this happened, was to delete some stuff from the SD card, but it should've been nothing important, just some backups and downloads.
Any help would really be appreciated, as I can't use my phone at all right now.
Okay download an new rom on your computer. Go to recovery and mount sd card then tranfer the new rom to your sd card. Then flash new rom. See if that works
Sent from my HTC Vision using XDA App
always flashed and never had a problem, hadnt done ot for a few months so today decided to flash -[ROM][Jun 22]RCMix3D KINGDOM v1.7 Evolutionary Sense! THE ORIGINAL SENSE 3.0 DHD. when i rebooted it was stuck on the boot screen forever, even tried clearing all the data and cache and dalveks cache, still did the same, so i followd a guide to formatting the sd card now its empty :/ which i guess would happen, but i dont have a card reader, is there a way to get into my sd card from my pc with the lead connected and could someone guide me on how to get the rom on there, really dont fancy a bricked phone, im pretty amateur at this, im ok with flashing and stuff but all this artsy stuff goes over my head, guess thats what i get for rooting anyway, im guessing i need to format properly, if someone could tell me how and that i need to access my sd card to put a rom on it so i can finally flash corrupt free, can someone tell me how, or is my phone bricked.
Boot into recovery, plug phone into PC, head to "mounts and storage" in recovery, select "Mount USB".
Copy over your new ROM, wipe & flash. Easy.
thanks, was looking for something like that, couldnt find it, copying over a rom now, did i do the right thing by choosing size 512 then swap 0 ? hopefully its all rectified now and will boot without looping ! will report back, thanks for the instant reply
and we have success thankyou
Hello. My HTC Desire, that was rooted and flashed to a LeeDroid ROM back in July, just stopped working today. I was listening to music earlier today when all of a sudden it stopped. I took a look at my phone and it says "Unable to play file" or "File not supported"
My phone restarted and it was just stuck in a boot loop. I tried going into recovery but everytime I got there, it restarts again. I was out of options so I went to recovery and erased data and then went and tried to flash a new ROM (CM7). It installs but again it gets stuck in a bootloop.
Any ideas what's wrong?
How is your sd card partitioned? I had the same problem when my 8gb sandisk was damaged. It would still work as an external fat partiton, but forget about using it as an extention to the internal storage.
It has happened to me too, just as you described.
I was able to revert to some old nandroid backup of leedroid 3.0.8.2
Any new rom results in reboots, or something doesnt load completely and im stuck on the unlock screen.
I suspected the SD card but it wasnt it... Replaced and same result
I now suspect the internal nand mem (flash) but couldnt find a way to test it...
If anyone knows the source or solution to this problem please post it
Thanka
Hey, I think I fixed it.
I took out my SD Card, and in my computer, I formatted it (quick format). I put in another rom's zip file in there (I used Cyanogen Mod).
I booted into recovery, went to install zip from SD Card, chose the CM zip, installed it. After installing, while in recovery, I went back and selected clear data and memory (something along those lines). That will remove everything currently on your phone.
From there, I rebooted and everything seems to be working okay.
What if you try some other mod?
Something with sense 3.5 for example ?
junkgoesto said:
What if you try some other mod?
Something with sense 3.5 for example ?
Click to expand...
Click to collapse
go for it. But I think the key here is that in recovery, after installing your rom, you need to clear the memory.
Or try doing that first before installing a new rom
Yes, after flashing a ROM do a FULL wipe.. and everything will be okay.... you can trust me! after all you're taking advice from a drunk man!