Hi, I'm really hoping someone can help me. I've spent the last hour searching on here and although I've found lots of posts addressing similar issues to mine, I've not managed to solve it.
Before things went wrong I was running MoDaCo r5 without any issues. A2SD+ with an ext3 partition on the SD card (but no dalvik to sd). ClockworkMod recovery.
Decided to flash CyanogenMod 6.1.0 RC1 using ROM Manager. Downloaded it to the SD along with the Google apps, backed up my current ROM, wiped cache and data, installed CM... phone booted but then stuck on the CM boot screen for about 10 minutes. Did battery pull, rebooted, same thing. Tried several times more, no luck.
So booted into recovery and tried to restore my previous ROM. It goes through all the usual stuff then says its finished. Reboot. Stuck on the pink circle loading screen.
Wiped data, wiped cache, tried factory reset, clear storage.... Just gets stuck on the pink circle screen every time I reboot.
One thing I noticed - when I first boot into recovery (hboot screen) it briefly flashes up something about SD...Loading... No image (its too quick to read it all). Not sure if that means anything.
Also, at some point (I'm afraid I can't remember exactly when, but it was while I was doing something in recovery) it said something about 'not enough space on device', or something like that.
Sorry that's all a bit muddled - I thought I was more competent at all this stuff than I clearly am! PLEASE can someone help walk me through what I need to do to get things working again.
(I can't use adb with my computer - got into all sorts of problems trying to install/use it in the past, so if there's a solution that doesn't involve that it would be great. I have access to a Linux machine if that helps.)
UPDATE: After trying everything I could think of, I decided to try the nuclear option - Backed up everything on my SD card to my computer, then formatted it, copied the CM 6.1 zip back onto the SD and installed it, and it booted fine. Maybe had something to do with there not being enough space on the SD card? Does the ROM get unzipped onto the SD card during installation? If so I guess that could have been the sticking point as I only had about 250MB free!
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
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!
My HTC Desire started misbehaving earlier in the year, it would crash and reboot, when it rebooted the SDCard would not be detected, a few days later, it would crash again and the SDCard would re-appear.
When it was visible, the SDCard would work ok a long as you didn't use it much, listening to music for any length of time would cause it to fail again. The SDCard will stop working a day or so after boot, all by itself without any use.
Sometimes it was visible but apparently needed formatting (which isn't true). The card tests fine in computers and I've used two different cards with the same issues.
I figure the issue is with the SDCard controller, although I'd like to get other's views on what the issue might be. I'd like to repair the phone by replacing whatever is necessary, but my knowledge of the hardware build is non-existant right now, could anyone advise where I might start?
dnel said:
The card tests fine in computers and I've used two different cards with the same issues.
Click to expand...
Click to collapse
Do the cards misbehave in recovery also? Have you tried a different rom ?
handy5876 said:
Do the cards misbehave in recovery also? Have you tried a different rom ?
Click to expand...
Click to collapse
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I've wiped and reloaded the rom, recently I successfully updated to the latest Cyanogenmod 7 but the procedure is too risky if I lose the card while flashing so I wouldn't do it again.
A link for HTC Desire disassembly if you are up to it
http://www.formymobile.co.uk/desiredisassembly.php
Never opened my desire. More details in this Nexus one teardown also http://www.ifixit.com/Teardown/Nexus-One-Teardown/1654/2
dnel said:
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I/QUOTE]
check the contacts first before doing a disassembly . it might just need a spray contact cleaner on both card and phone.
Click to expand...
Click to collapse
or you could try this before disassembling your phone http://forum.xda-developers.com/showthread.php?t=691187
it might be an "usb brick".
Thanks for the replies, I decided to try a few things before I took a screw-driver to my phone and so far it's good news but I'm not sure why...
I remembered that a couple of weeks before the SDCard failed, I used alpharev to s-off and flash hboot to CM7r2. So a few days ago I reverted this change.
I re-flashed the stock hboot and then switched from Cyanogen 7.2.0.1 to the last MIUI gingerbread. This process nearly bricked my phone, at one point it wouldn't even boot into recovery and then the 4GB SDcard I was last using in the phone failed completely, but interestingly it failed while it was in my computer and not my phone. After this I switched to a 32GB class 10 SDCard that was in my phone when the SDCard originally started to misbehave so although the 4GB SDCard failed I don't think this is related to the problem because the problem presents with both cards.
After I flashed stock hboot and loaded MIUI, the problem hasn't presented itself, not once.
I then flashed back to CM7r2 and reloaded MIUI and the SDcard worked but I couldn't install any market apps, complaining of a lack of storage. This is with nothing in /data except for the dalvik cache and 250MB of "free space".
I then flashed to the Data++ hboot and reloaded MIUI and the market now works and the SDcard is working.
I don't know how the partition table on the MTD may have caused my SDCard to fail, the best I can guess is there is some bad memory area which when CM7r2 is loaded, corrupts an important system memory area.
I'm leaving it stable right now and will see whether the problem arises again before making further changes. I would be interested to know if there's any fsck-like apps that I could used to check the MTD for errors?
Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.