Related
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 some sort of sd-ext error when restoring a nandroid backup. At the moment my phone is stuck at the cyanogen boot loop. I've wiped everything, i tried to format the sd-ext but it will not mount. i've tried fresh installs, everything I can think of but nothing seems to be working.
sd-ext error is normal, that's actually referring to the partition where you would install apps2sd, I get that error all the time because I don't have any as well and no need to have that partition.
In ClockworkMod Recovery, the sd card is just called "sdcard"
SynbiosVyse said:
sd-ext error is normal, that's actually referring to the partition where you would install apps2sd, I get that error all the time because I don't have any as well and no need to have that partition.
In ClockworkMod Recovery, the sd card is just called "sdcard"
Click to expand...
Click to collapse
Okay. So how do I go about getting my phone operational again? As I said i've wiped everything and tried to restore backups and did fresh installs and still am stuck at the looping boot screen.
You're using clockwork mod recovery right? Format your sd card using Windows to FAT32.
Boot into recovery..format all your other partitions. Mount USB storage, put a ROM in there, try stock Virtuous seems to be more stable than CM.
Clear data/factory reset, clear cache, then clear Dalvik cache. Install Virtuous .zip.
You should be able to boot. If you still can't try taking unmounting the sd card after the ROM finishes installing, try taking it out as well.
SynbiosVyse said:
You're using clockwork mod recovery right? Format your sd card using Windows to FAT32.
Boot into recovery..format all your other partitions. Mount USB storage, put a ROM in there, try stock Virtuous seems to be more stable than CM.
Clear data/factory reset, clear cache, then clear Dalvik cache. Install Virtuous .zip.
You should be able to boot. If you still can't try taking unmounting the sd card after the ROM finishes installing, try taking it out as well.
Click to expand...
Click to collapse
I got this error trying to install Virtious:
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.
Click to expand...
Click to collapse
I successfully installed the MIUI ROM however it doesn't even get to the boot screen. It stays on the white background HTC Incredible screen.
I saw this guy had a similar problem:
http://androidforums.com/incredible-all-things-root/181337-backup-problems-ud-cm6.html
He said that Cyanogen Mod seemed to be better for him. But he was also clearing data/cache and Dalvik AFTER he installed the mod.
It's ok to do that after, but you better make sure to do it before. Have you tried clearing both before and after? If it gets stuck on the white incredible screen I am not sure, but if it goes beyond that and then crashes right before the boot is finalized then that might be an SD card problem.
SynbiosVyse said:
I saw this guy had a similar problem:
http://androidforums.com/incredible-all-things-root/181337-backup-problems-ud-cm6.html
He said that Cyanogen Mod seemed to be better for him. But he was also clearing data/cache and Dalvik AFTER he installed the mod.
It's ok to do that after, but you better make sure to do it before. Have you tried clearing both before and after? If it gets stuck on the white incredible screen I am not sure, but if it goes beyond that and then crashes right before the boot is finalized then that might be an SD card problem.
Click to expand...
Click to collapse
Yes i've tried before and after. With cyanogen it loops the boot screen, with MIUI that I installed it doesn't get past the white screen and i cannot install virtuous at all
Anyone? I'd really like to be able to save $300 here
last loop i had with cyanogen was because i had the wrong kernel. make sure u flash a kernel that supports asop. its simple but it slips minds alot i usually use kings kernels (#2)
akawings said:
last loop i had with cyanogen was because i had the wrong kernel. make sure u flash a kernel that supports asop. its simple but it slips minds alot i usually use kings kernels (#2)
Click to expand...
Click to collapse
ive tried kings and ziggy's aosp
The phone is totally screwed up, it wont even accept unrooting and putting the stock ROM back onto it. I have *NO* idea what happened. I just got this phone replaced and did a restore and it was working fine, then it froze so i removed the battery and put it back in and then this.
http://androidforums.com/incredible...16-how-revert-back-earlier-version-hboot.html
try using that to unroot, itll take you back to 2.1 (or you could use a different ruu for whatever version youd like to revert to)
Fixed! I went out and bought a new class 6 SD card and used berserkers method to go back to stock. Thank all of you for your help!
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
I'm hoping someone can help me with rom installation problems, I have reached a stalling
point and have not found a similar problem in the forums.
My phone is an SCLD Desire, pvt3, rooted and s-offed, cwm 3.0.0.5, radio
32.49.00.32U_5.11.05.27. The SD card is a transcend 8Gb class 6 with a 1.5Gb ext4
partition, formatted with gparted. Stock hboot.
I have so far tried to load both RcMix InsertCoin A2SD versions with no success.
I am following the instructions for both Roms to the letter;
1. Wipe data
2. wipe cache partition
3. wipe dalvik cache
4. reboot recovery
5. install rom from sd card
Both roms tell me that they have loaded successfully from zip, then I reboot the system.
Both start to load, show their respective logos and then do the following:
InsertCoin will get me to the sim unlock screen, I unlock the sim and screen says loading,
then I get to a screen with wallpaper, notification bar and sense bar, but no icons or widgets.
When the screen times out and I wake it, I get wallpaper and notification bar only.
The phone will not even power down.
RcMix starts to load, shows the rcmix animated logo for a while, then the logo ceases
its animation. If the screen dims and I wake it, it shows the static rcmix logo only.
I have left the phone alone for over a half an hour on each attempt to see if the roms
would load successfully.
I use Ubuntu and have found that I cannot transfer files to and from the ext4 partition. I get a permission denied every time I try. I'm not sure if this is normal or not.
Can anyone please help , this is driving me nutz.
Thank you.
I see the problem. Your radio is too old, flash the latest one
merizim said:
(...)
1. Wipe data
2. wipe cache partition
3. wipe dalvik cache
4. reboot recovery
5. install rom from sd card
(...)
Can anyone please help , this is driving me nutz.
Thank you.
Click to expand...
Click to collapse
I think it has nothing to do with the radio. You just forgot to wipe /system, too. Do this and try to flash again.
MatDrOiD said:
I think it has nothing to do with the radio. You just forgot to wipe /system, too. Do this and try to flash again.
Click to expand...
Click to collapse
I had same radio+ same problem
Not saying it without reason, but if you wipe ALL USERDATA? it's the same right? and i forgot to see that one But anyway if that doesn't work it's most likely the radio
Yes you are right. It's the same. We'll see what helps.
Swyped from my HTC Desire using XDA App
Updated Radio
I've upgraded to the latest radio version 5.17.05.23 and tried again, making sure everything was wiped. The installation gets further than last time and after a couple of reboots I get the setup screen but there is no keyboard to input the details, and sense constantly force closes. There was also no sim unlock screen. When I tried to shut down the phone it went into a bootloop.
I will try another install to verify.
Tried fresh install again but am getting partially loaded rom: sense ui is working but force closes on any interaction, when I tried to go to settings it says "the linked program is no longer on your phone", no sim unlock screen, no keyboard. Bootlooped again on powering down.
I read some where in XDA forum that the CWM 3.0xxx is buggy.
Try to use CWM 2.5.0.7 and see.
Sent from my HTC Desire
It seems like a silly question, do you have an ext partition? If not make one with gparted, or use AmonRa recovery(that is able to partition you sd), i find it much better than CWM
If you already have an ext partition is it 1GB?
merizim said:
I'm hoping someone can help me with rom installation problems, I have reached a stalling
point and have not found a similar problem in the forums.
My phone is an SCLD Desire, pvt3, rooted and s-offed, cwm 3.0.0.5, radio
32.49.00.32U_5.11.05.27. The SD card is a transcend 8Gb class 6 with a 1.5Gb ext4
partition, formatted with gparted. Stock hboot.
I have so far tried to load both RcMix InsertCoin A2SD versions with no success.
I am following the instructions for both Roms to the letter;
1. Wipe data
2. wipe cache partition
3. wipe dalvik cache
4. reboot recovery
5. install rom from sd card
Both roms tell me that they have loaded successfully from zip, then I reboot the system.
Both start to load, show their respective logos and then do the following:
InsertCoin will get me to the sim unlock screen, I unlock the sim and screen says loading,
then I get to a screen with wallpaper, notification bar and sense bar, but no icons or widgets.
When the screen times out and I wake it, I get wallpaper and notification bar only.
The phone will not even power down.
RcMix starts to load, shows the rcmix animated logo for a while, then the logo ceases
its animation. If the screen dims and I wake it, it shows the static rcmix logo only.
I have left the phone alone for over a half an hour on each attempt to see if the roms
would load successfully.
I use Ubuntu and have found that I cannot transfer files to and from the ext4 partition. I get a permission denied every time I try. I'm not sure if this is normal or not.
Can anyone please help , this is driving me nutz.
Thank you.
Click to expand...
Click to collapse
Flash RaRecovery. Do full wipe, reinstall rom. I use RCMix for months and don't have any issues.
It gets stranger???
In reply to previous posts:
Firstly thank you all for your suggestions.
Genie4all:
There is a post which says that cwm 2.5.?? does not handle ext4 and recommends cwm 3.0.0.5, I was previously on 2.5.?? and was getting the same problem.
TopGear63z:
Yes I have a 1.5Gb ext3, previously ext4 partition
I thought I would see if changing from ext4 to ext3 would make any difference, also ran melethron's alignment script before reinstalling RcMix again. It made no difference.
However I also decided to try LeeDroid 3.0.8 and it loaded and ran perfectly.
This is making so sense (no pun intended) now, after all there should be no difference in the way a rom is loaded on a stock hboot. Could it be that LeeDroid is Sense 1 and the others are 1.9/2.1/30 hybrids?
Would AmonRa recovery really make a difference?
Any other suggestion would be greatly appreciated as I really want to experience those new sense 3.0 goodies.
Thanks.
Resize your ext partition to 1GB with gparted see if that work.and also try to flash it with amonra i read it somewhere on rcmix thread that this rom works great with amonRa though i flashed this rom on both cmw and amonra without any issue.
which rom version did you tried bravo or cm7?
I had the partition at 1Gb previously but in linux it reported only 974Mb free, journalling took the rest so then I decided to resize to 1.5Gb to ensure that at leat 1Gb was free.
I've been trying the Bravo versions of both Roms. Now I think it's time to try Ra recovery and see if that works, I'll report back on the results.
Thanks
if that don't work then change your partition to cm7r2 and flash the cm-7 version and Rcmix cm7 version is fast and smoother than bravo.
You know that 1GB is not the least, it's recommended maximum, you should at least have 512mb to let the rom work. I have 1.1GB ext and no problems but i had when i used 1.8GB, so i actually think that's the problem. Only if it still doesn't work after using AmonRa's recovery ofcourse
I'm on RcMix with ext4 and CWM 2.5 and it works like charm.
Try formatting your card to FAT32 and use gparted to create a 1gb ext portion at the end and try.
Also do a full wipe.
Sent from my HTC Desire
1.5 gb ext3 is really good and will make no problem.. it might be caused by bad mounting the ext3 partition... go to applications then Manage Applications and see if any grey applications there...
Solved
Changed my recovery to AmonRa 2.0.1 as suggested and am now running RcMix successfully.
Thank you all for your help and suggestions.
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?