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!
Hello,
I have a problem when installing the MIUI V4 Marange ROM 2.6.8
The installer stuck on "Setting permissions" (in aroma).
For installing it, i make this different steps :
1/ Wipe all
2/ Fix permissions
3/ install: choose a2sd, ext4, no swap, shaky kernel
My phone is a HTC Desire with 4EXT Recovery Touch.
I have a 16GB SD Card with a 1024Mo Ext4 partition.
Thank you for your help
Best regards
Please, paste here the log of your installation.
You need to use the button in bottom left of the screen, the file will be saved in the same directory of the rom.
It can help discover what's your problem.
The problem is that i can't use this button because when the installation have a problem, i can't click anywhere.
In fact, when i install this rom, the installation goes until "Setting permissions". After a few minutes, the installer closes and shows an error with status 0.
What HBoot are you running? Is it Data++?
Yes! Why?
I know this may not sound like a solution to you, but try installing with Stock hboot. Here's why:
I had the exact same thing as you do now, and in every way I tried, I couldn't get MIUI to install on Data++ and on Sence hboot it installed, but gave me alot of errors.
I tried alot of things, such as installing on Stock hboot, taking backup, switching to Data++, perform a factory reset and let MIUI re-install itself... google application services started failing left, right and center.
I ended up ordering a Class 6 Ultra 32GB Micro SD Card, so I can use Lennox's LX-D2X script (cause my current card is too slow and caused alot of lag). Until the card arrived, I'm trying to live with just 140MB of internal memory (with Dalvik and App Data on sd-ext). Here's my setup:
PC-A2SD
EXT-3
Internal Swap File
Shaky Kernel
smartassV2 governor
Hope this helps.
Hi
I have a Desire GSM rooted and S-ON RA-Desire v2.0.1 stock HBOOT Ext 4 1Gb latest radio ends in 23
Have been running on a custom rom for over a year now and want to install the latest copy of the same rom. The md5sum is identical for the zip file to the source.
Booted into recovery wiped all data, cache and then devlik-cache.
I have turned off signature verification and then selected my rom zip on SD card.
Installed the rom rather there were no errors and it took about 20 seconds (seemed too fast).
Next in recovery I did a reboot.
Now the screen went white with green HTC logo in centre for about 1 minute then after this a black screen with android written logo for about another 2 minutes.
Eventually phone boots into rom but it is not the new rom it is the exact same old rom.
I can see from applications listed that I am still super user so not lost root.
In settings software information everything is listed identical to what I had before.
The contents of the zip files are different so it is not the same rom being flashed.
Choosen rom is
[ROM][Cool Sense][5 April]Cool Droid v3|2.3.4|FASTEST|Data++/Stock (currently have Icecream sense v2 installed which is an earlier version of the same rom)
I did not install the alignment zip as I had already setup to use an earlier rom version and ext4.
What have I done wrong in trying to install my choosen rom please?
I feel like I must have missed something.
Not sure which recovery you have, with 4ext I boot to recover, format everything except sd then install zip and it seems to work, obviously everything then needs reinstalling from the backup you'll have made
Sent from my HTC Desire using Tapatalk 2
Hi
Unrevoked 3, as I have one of those odd PVT4 Desire phones 4000 erase size using RA Recovery. (something like that sorry if technical references are not super clear).
I use Titatium backup so reinstalling wont take long just need the ROM to install.
This is a fast glitch free rom using sense so I do not want to try a different rom as it gave me a year without trouble. Only doing this to start again with the space issue needing a refresh.
I have cleared delivk cache again and flashed my original v2 rom and that worked showing expected progress reports.
So I thought would try flashing the new v3 rom, and see if I got any joy this time.
Still no joy, it looks like it starts as two lines appear then it says complete with no obvious error.
So I reflashed the original v2 rom again and will go with that as I need a phone more then I need to play.
Odd.
Maybe the new v3 rom needs sOFF but as far as I could read it does not.
Even installing the previous rom things are still not right.
The apps that normally come with the rom are not installed such as Demon controller, No adds and Busy Box. I can see that they are in the zip file they are just not been added.
I can manually install Busy Box from the market so I know it is not a permission thing.
Titatium Backup is seeing my Ext4 partion (it calls it an ap2sd but it is showing) so I don't think there is a problem with my SD car arrangement.
I stupidly do not have a nandroid of the previous install I can restore.
So any ideas please why the previously working and installed rom is not reinstalling fully with all it's built in apps?
Anything I could try please?
Looks like I have identified the problem, my SD card is flakey and Gparted reports sick partion table that wont fix so the Ext4 partion was not been seen which is probably why the install failed and the apps were not installing.
New Sd card will be ordered and then start again.
Thankfully I dod have an uptodate SD card backup.
Phone is working just as a phone for the next few days.
These micro SD cards do not last long at this rate I get 1 year from them as this will be my third ordered.
Go to S-OFF, is better and mandatory for a lot of rom.
New card and more fiddle work with Gparted and now waiting for setup to complete as old v2 rom is installed. It works fast and is smooth plus has HTCsense so I can keep my sync capability so will be staying with it so I can live without S-OFF
Gparted when I followd the recommendations I kept getting a corrupt card on my phone so this is what worked for me.
Format card on phone
Then put card into usb card reader and place in PC
Reboot PC onto Gparted CD
Select SD card and then I resized the fat32 partion already there and then added a new EXT4 partion.
This worked for me.
Dump gparted, format the card through 4ext recovery
Sent from my HTC Desire using Tapatalk 2