Hey everyone,
Ok, here's the deal. I flash new ROM's by CM or Amon and I get the message saying SD card unmounted. Go to settings to mount it, it shows as no SD card installed. Reboot into recovery, SD available. I've read clearing cache and davlik a few times usually clears up any initial load problems for new ROM's. Nope, doesn't help. Reboot shows no SD installed
Back into Recovery.
Mount SD card?
Tried it. Still unmounts on boot.
BUT...
Not on ALL ROM's.
I'm running Myn's Warm 2.2 fine (well, some laggyness)
I'm running 1975jamie's King Cocoa II True Blue just fine
I ran Cyogen fine (just don't like AOSP ROM's)
MIUI ran great.
I'm dying to keep the new line of Sense 3 ROM's.
They all install, load, and boot just fine.
I get to the initial "new user" setup stages and they all connect and sync just fine, then POOF! I get the little SD card symbol in the upper left hand corner saying SD card unmounted...
I ignore that to check out the ROM's and they scroll just fine, everything opens and closes fine.
Any ideas?
Jack
Are you flashing in recovery or with ROM Manager?
Last flashed ROM was Warm 2.2
Used ROM Manager to D/L ROM, add on's, and flash them.
All boxes checked prior to flashing (Backup, Cache, Cache/Davlik)
Previously was running Warm 2.2 (prior to King Cocoa II), but flashed through CM.
Both flashing methods yielded no problems.
Flashed MIUI in Recovery AND ROM Manager to test.
Both yielded no problems.
Every other ROM, but the 4 I listed in my OP, shows no SD card.
So basically, list of WORKING Rom's installed and run, in order, were:
Warm 2.2 then
New install of King Cocoa II then
New install of Cyogen then
New install of Warm 2.2 (deleted backup for fresh start) then
New install of MIUI then
Backup of Warm 2.2
Only backups I still have are KC 2, Warm, and MIUI.
In between some of those I tried flashing other ROMS, but all croaked with no SD message...
Jack
I don't recommend using Rom manager for flashing roms. Rom manager and clockwork mod tend to not wipe cleanly. You should gave better luck using only amon ra. Wipe everything 3 times(except sd) before flashing. If you still have issues, try formating your sd card on your computer.
Sent from my PC36100 using XDA App
That's all well and good, but doesn't explain why only 4 ROM's flash "right" on my phone regardless of what method I use, lol
Gotta tell ya though, as much as I've liked this Evo...
The Samsung Galaxy S II is looking better and better every day.
I can't promise, but I can assure that you'll have better results using Amon Ra and flashing in recovery.
The best method is do a nandroid of you current working ROM. Backup everything but cache (arguable), then go to wipe and wipe every setting there is once, except the SD card itself, and the battery stats, if you're not fully charged.
Then wipe Dalvik cache and cache 2 times.
Then flash your ROM.
If you REALLY wanna do it up right, before you flash the new ROM, back up your SD Card to your computer, format it in Windows with a card reader, then put it back in the phone, go to partition, in Recovery.
Partition using 64mb for swap (arguable.. some people put 0) and 1024 for EXT partition.
When it's done, convert to EXT3.
Then copy all your stuff back to your SD Card.
Flash your ROM and then flash DT APS2SD before you reboot. I know a lot of ROMS have it baked in, but I still flash it manually.
Once your ROM boots (if it does) let the phone just sit til the screen shuts off, then reboot to Recovery and do another Nandroid, so you have a backup of a stock/working version of your ROM. Flash a custom kernel if you want to (wipe cache and Dalvik Cache first), then reboot. Let your phone settle again (til the screen turns off) then start setting things up, Google acct., apps, etc.
If you use Titanium backup to restore your apps, ONLY RESTORE apps/Data that you put on your phone. No Google apps, no System apps, No HTC apps.
Then reboot again, when you're done.
Yes, it will take some time to do all this.
Yes, you will have very little chance of problems like force closes, reboots, etc.
Now if you REALLY REALLY want to do it right, do a nandroid of your current setup, and then flash a stock/Sense ROM in recovery and Nandroid that so you have a stock setup for flashing GPS fixes, updating your profile, etc.
(BTW, having a stock setup means you can probably just flash that and not unroot if you have to take your phone in at all)
Is your card partitioned if so did you partition it after you backed up warm 2.2 .
You may need to fix sdext in recovery or run a fix using your computer I had something like that happen and I fixed it by mounting to my PC in recovery then started to copy some files then just stopped it in the middle of coping and when I plunged it back in my PC recognized there was a problem and ran a fix for it .
I know that sounds kind of geto.
Sent from my PC36100 using XDA App
Just thought I put in my 2 cents. I Used to use Rom Manager to download roms but I experienced a lot of force closes. Now, I always flash thru recovery. I Factory wipe 3 times, I also use calkulin's format 3 times, clear cache 3 times and clear delvick cache 3 times... then flash. Also, read thru the forums on the roms you are using this maybe a problem with that rom. I personally have not the issue you have.
Related
Hi,
I was hoping some of the smart people here might be able to point me in the right direction for a solution to a problem I am having.
As the thread subject says; I've flashed several ROMs based on the official 2.2 release and I end up with a boot loop at the first HTC logo, it never makes it to the quietly brilliant screen, it just re-boots continuously until I pull the battery.
However, ROMs based on 2.1 boot fine, both official ones and modified ones obtained here on the forum. Also, the 2.2 based DeFrost ROM boots fine.
The actual flash process seems to go fine, with no errors being reported.
I've tried wiping/factory reset before I flash, after I flash, but the result is always the same.
I've tried with and without the latest radio installed.
I've tried booting with the SDCard and SIM removed, but no luck.
I've even tried downgrading from bootloader 0.80 to 0.75, again with no difference.
A bit of background info;
My Desire is a generic unbranded model.
Yesterday, I did try to install the OTA 2.2 update, but something messed up during the flash process and I ended up with a corrupted recovery partition and (once again) a boot loop.
Thankfully, I managed to flash an older RUU file and things are back to normal, except for the in-ability to boot any ROM based on the official 2.2 release.
If anyone can help I would be forever in your debt, as this really is driving me crazy.
I had the same problem when I installed the new 2.2 HTC ROM without wiping...
Anyway try to wipe both factory reset and all caches with both amon ra recovery port and clockwork recovery...
Same problem... but fixed I fixed it installing this: http://forum.xda-developers.com/showthread.php?p=7483900
I have same same loop like that
I dont know why? I use r5 modaco custom rom. it seems well. but when I try to use edge/3g, it starts loop booting. if turn off edge/3g, the phone works perfectly.
after that, I tried to flash another ROM, Wipe Factory reset, Wipe Cache, Wipe Dalvik, even wipe ext but it still happens
I put out SIM, the phone boot correctly( maybe just reboot one time). but put SIM in, it reboots.... sometime the phone vibrate 5 time at HTC screen .
somebody can help me?
ps: how to know wipe dalvik work perfectly? I cant see any info about it done
I had the same problem with the first rooted official rom I tried to install, then I restored to my modaco mcr-r5 (2.2) rom, updated to the new radio and then installed the rom from nickiberli via rom manager and it worked.
btw, I selected wipe data in rom manager when prompted, lost all my apps and data but the setup wizard ran when it booted up first time.
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
raz2133 said:
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
Click to expand...
Click to collapse
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
ratykat said:
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
Click to expand...
Click to collapse
Thanks for the suggestion, but I just tried this ROM and it wont boot for me either.
bakedecake said:
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
Click to expand...
Click to collapse
I do have an ext partition on my SDCard and I have tried ROMs with and without A2SD. In fact, the ROM I have used for most of my tests is "Rooted Official HTC Android 2.2 (FroYo) ROM [Market issue fixed]", which I don't think has A2SD.
I have tried booting with 3 different SDCards so far, and of-course I have tried with no card.
so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!
That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.
Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App
I rooted the incredible using unrevoked, no problem.
Installed and ran root apps, no problem, backed up everything using titanium backup and rom manager (nandroid) and so forth, installed cw recovery 3.0.0.8.
When I install the skyraider 4 rom from rom manager, it reboots and installs, but then when it reboots again it hangs at the white htc incredible screen (and I've let it wait as long as a half an hour). I have to take out the battery to be able to reboot it.
I can boot back to recovery and then re-install and boot back to the stock rooted rom just fine. But I can't get a new rom installed and working.
I've looked at previous threads about this problem:
http://forum.xda-developers.com/showthread.php?t=1038402
http://forum.xda-developers.com/showthread.php?t=1023358
http://forum.xda-developers.com/showthread.php?t=991953
http://forum.xda-developers.com/showthread.php?t=739646
http://forum.xda-developers.com/showthread.php?t=620621
and several other threads on other sites.
The only suggestions to come out of those, other that starting over from scratch (which I've done multiple times now), were to reformat the sd card, which I've also done, and to downgrade to cm recovery 2.5.1.2. Rom manager only shows versions as old as 3.0.0.5. I have put the PB31IMG.zip file on the sd card and loaded that before to help recover but I don't see how that helps with installing a new rom.
Any other suggestions? The main reason I even need a new rom is because bluetooth doesn't work in the stock rom (known issue: http://community.htc.com/na/htc-forums/android/f/91/p/2336/8570.aspx )
It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe
patsfan1130 said:
It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe
Click to expand...
Click to collapse
appreciate your help, yeah I've been doing that everytime in rom manager. I tried it several times manually in cm recovery, too, and still the white screen.
I'll just see if verizon can exchange it, or else I'll sell it for another phone with working bluetooth.
Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App
when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.
when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.
k_nivesout said:
Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
.
There is a flash of CWM 2.5 that temporarily lets you use that to flash the rom then when you reboot it will revert back. Try that.
Since I keep getting the same dumb error LOW DISK SPACE, I decided to start over and go to an older nandroid backup.
I tried it and it flashed, but there were no icons on the screen, just the wall paper. NOTHING, no phone, apps, no buttons worked.
I tried to reflash the MIK G Rom that I used. SAME THING. No icons..nothing. I was getting text messages on the task bar coming through but NOTHING ELSE.
Any suggestions how to fix this?
Bottom line, I do nandroid restores and reflash the MIK G Rom and the screen is completely blank except the wallpaper and the task bar...??? Strange
Thanks
Mike
PS
Using AMON RA
I had the same issue happen to me when using amon-ra 2.3 recovery back in the day. Install smelkus 4.3 recovery and do a full wipe of sd card and repartition if necessary. Basically start over new and flash a fresh copy of your rom of choice. Nandroid should backup properly and eliminate any further issues.
I agree. Start over, repartition, wipe everything, flash the ROM and then use A2SD to move your Dalvik Cache to your SD Card
I have been going back and forth between Quantum, SlimHalo and Task's and I have never had a problem. I would wipe all but SD and storage, flash away, let the apps download and that was it.
Now, regardless of ROM, I wipe everything including data, flash the ROM, GAPPS, reboot and it all works but if I reboot or if the ROM crashes, the phone will get stuck at the kernel's boot screen.
Other than the SD card I don't think there is anything else I can wipe before flashing. Even when I restore a backup that used to work, the phone won't reboot. It'll get stick on the underwear if I have tasks' ROM or the SlimRom logo for SlimHalo. Those are both ROMs that worked perfectly. In fact they seemed to work better before I formatted the data partition.
I redownloaded the ROMs, GAPPS, same thing every time. I can't get a ROM to reboot even if I wipe everything.
I use TWRP 2.6.3.0
I'm having the exact same problem. Even flashed stock rom back via Odin, but no luck. Gets stuck at "Samsung" screen indefinitely. And I mean it, I've left it going for a few hours.
Maybe you should try one of the older TWRPs from the Team Win website and see what happens.
Sent from my SAMSUNG-SGH-I747 using xda premium
I managed to fix the issue by flashing the stock image via Odin and factory resetting right afterwards.
I am having very similar issues trying to update to several different 4.3 ROM's. I have a thread going in the Q&A section already. I haven't had time to grab a logcat yet but am confused so far. I am also on TWRP and usually after the "freeze" I have to wipe the internal memory completely, reboot recovery and then flash my backup other wise the restore just "fails". Starting to question if TWRP is the culprit here but have no time to experiment lately.
Galloway said:
I am having very similar issues trying to update to several different 4.3 ROM's. I have a thread going in the Q&A section already. I haven't had time to grab a logcat yet but am confused so far. I am also on TWRP and usually after the "freeze" I have to wipe the internal memory completely, reboot recovery and then flash my backup other wise the restore just "fails". Starting to question if TWRP is the culprit here but have no time to experiment lately.
Click to expand...
Click to collapse
Here is how a managed to fix the issue.
Downloaded slimhalo and its gapps again.
Put the 2 files on my external SD
Booted to recovery
Formatted data
Wiped the usual plus internal storage
Installed the ROM and gapps from the SD card
Took the SD card out
Booted.
I then unchecked the option to download the google backed up apps
Downloaded and installed apps.
I haven't put my SD card back but that phone reboots fast and it had no issues rebooting 10 times in a row.
I hope this helps other people
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I tried formatting an SD card, putting ROM and GAPPS on it. Booted to recovery, wiped all internal complete. Flashed ROM and GAPPS. Powered off and pulled SD card. Booted up and unchecked Google back up settings and then set up accounts and such. Tried rebooting and same problem. Just freezes at Samsung logo... Good thought but still no go... Flashed back to backup now.