I have always had random reboots with the phone, however they were mostly infrequent.
Fastforward to yesterday, I was running the latest stable version of CM7 (7.0.3.1 or something to that effect). Everything was working out okay, and so I decided to flash the latest WiMAX and Radio updates. First I did the WiMAX, everything went fine and the phone rebooted and I used it without issue for a couple hours. At this point I flashed the latest radio from Caulkin's thread. After rebooting, the phone makes it through the splash screen, and into the rom splash screen, then once actually booting the rom it boot loops. If I get lucky, and manage to turn the phone into Airplane mode before the boot loop, I can prevent it from occurring.
So I have tried to re-download and reflash this version and the last version of the radio many times, without success in stopping the boot loops. I have reflashed the ROM as well as gone back into old Sense nandroid backups and the problem persists. I have flashed the FORMAT_ALL.zip file and the problem still persists! I have tried to update PRL and Profile, and the problem still persists!
Any help would be greatly appreciated.
Do the following in order:
1. Download and flash the PC36IMG.zip for amon RA v2.3 from the bootloader screen. You can download it from http://forum.xda-developers.com/showthread.php?t=705026
2. After amon RA is flashed, connect your device to your computer, reboot into your new recovery, select the MS-USB option and copy a freshly downloaded radio, PRI and NV over to your SD card. Do not use the combo zip. This is also a good time to transfer a freshly downloaded stock rom. You can get the radio stuff from http://forum.xda-developers.com/showthread.php?t=715485 and the rooted stock odexed rom from http://forum.xda-developers.com/showthread.php?t=874251
3. After you've transferred the above items over to your SD card, select the MS-USB option again to unmount your card.
4. Go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Afterwards, do not reboot.
5. Go to the flash menu and flash the PRI. Be patient. When it is complete, you will automatically reboot into recovery and see the words "clearing cache". Go to the wipe menu and wipe the dalvik. Afterwards, flash the radio and NV. Remember to wipe the dalvik between flashes.
6. Flash the rom. Do not flash any kernels, themes or mods. Afterwards, reboot. Be patient because the initial boot will take a while. When you've entered your homescreen, update your profile in the settings menu. If all went well and no reboots, go into recovery, wipe cache and dalvik and then create a nandroid backup. After that, if you want to flash CM7, wipe Everything in the wipe menu except the SD card and flash it. Hopefully, this will work for you.
posting & replying via the XDA Premium app.
I followed each of your instructions without success. Before I could even set up the phone fully, it rebooted. But this did help lead to a new theory I have. It didn't reboot until I got to the "location" settings, once I hit next allowing Google to use location settings it rebooted. So after 5 or 6 boot loops I managed to get back in to the OS long enough to turn off location settings. For the last 30 minutes or so I haven't had a reboot as long as the GPS and other location methods are off. Just a theory, we'll see if something changes... Meanwhile I wonder what the real issue is. *Edit* Scratch that, just boot looped.
dougjamal said:
Do the following in order:
1. Download and flash the PC36IMG.zip for amon RA v2.3 from the bootloader screen. You can download it from http://forum.xda-developers.com/showthread.php?t=705026
2. After amon RA is flashed, connect your device to your computer, reboot into your new recovery, select the MS-USB option and copy a freshly downloaded radio, PRI and NV over to your SD card. Do not use the combo zip. This is also a good time to transfer a freshly downloaded stock rom. You can get the radio stuff from http://forum.xda-developers.com/showthread.php?t=715485 and the rooted stock odexed rom from http://forum.xda-developers.com/showthread.php?t=874251
3. After you've transferred the above items over to your SD card, select the MS-USB option again to unmount your card.
4. Go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Afterwards, do not reboot.
5. Go to the flash menu and flash the PRI. Be patient. When it is complete, you will automatically reboot into recovery and see the words "clearing cache". Go to the wipe menu and wipe the dalvik. Afterwards, flash the radio and NV. Remember to wipe the dalvik between flashes.
6. Flash the rom. Do not flash any kernels, themes or mods. Afterwards, reboot. Be patient because the initial boot will take a while. When you've entered your homescreen, update your profile in the settings menu. If all went well and no reboots, go into recovery, wipe cache and dalvik and then create a nandroid backup. After that, if you want to flash CM7, wipe Everything in the wipe menu except the SD card and flash it. Hopefully, this will work for you.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Very interesting, indeed. Good catch, by the way......Since you are using CM7, you may have to apply a GPS fix of some sort. Does the smell thing occur with other AOSP roms like Salvage-Mod? What about Sense-based roms?
posting & replying via the XDA Premium app.
/bin/bash said:
I followed each of your instructions without success. Before I could even set up the phone fully, it rebooted. But this did help lead to a new theory I have. It didn't reboot until I got to the "location" settings, once I hit next allowing Google to use location settings it rebooted. So after 5 or 6 boot loops I managed to get back in to the OS long enough to turn off location settings. For the last 30 minutes or so I haven't had a reboot as long as the GPS and other location methods are off. Just a theory, we'll see if something changes... Meanwhile I wonder what the real issue is. *Edit* Scratch that, just boot looped.
Click to expand...
Click to collapse
You're installing it fresh, with the gapps, correct. And it only reboots when you use the location settings?
teh roxxorz said:
You're installing it fresh, with the gapps, correct. And it only reboots when you use the location settings?
Click to expand...
Click to collapse
I haven't put CM back on the device, as directed above I put on a stock rooted rom to "bug track", so gapps is installed, yes, but by default in Sense / HTC.
From the last two hours or so it still reboots after location settings are off, but less frequently than if they are on. Perhaps this is a heat issue? The more radios and things on the quicker it overheats into bootloop?
Also, stressing the phone in any way, such as running linpack, triggers a reboot.
Related
Okay, so earlier today I rooted my evo and flashed the CM6 ROM. A little later I tried to install Google apps.
I followed a tutorial on youtube on how to install gapps using rom manager.
Now my Evo is stuck in the Clockworkmod recovery screen and when I click reboot system now it reboots and goes back to the clockworkmod screen. I tried wiping data/factory reset and then re-installing the CM6 ROM, it did not work.
I really need some help here, I'm not too experienced and I don't want to brick my Evo. How do i fix this?? I am freaking out. Thank you!
I use AmonRA recovery personally and flash everything through recovery. I had too many problems when I tried flashing things through Rom Manager app. Do you have a nandroid backup? If so install the backup and then boot into recovery and reinstall CM6 and gapps back to back in the same recovery session. If no backup, download PC36IMG that corresponds with your hboot version and put it on the root of your sd card. Boot into bootloader by holding volume down and power at the same time. It will scan the sd card for PC36IMG and then verify it. It will then ask you if you want to update. Select yes and let it do its thing and then when it asks if you want to reboot select yes. This will put you back to stock and may unroot, so you may have to do the root procedure again. Then install CM6 and gapps in same recovery session.
Before all this try wiping cache and davlick cache and reboot. If that doesn't work try powering off phone through clockwork and then boot into bootloader. It will scan for PC36IMG and not find it then you will have options to boot into different things. Select recovery, and it will boot into Clockwork. Wipe cache and davlick cache and reboot. See if this works. If not you will have to nandroid or go back to stock probably unless someone that has had this problem and comes along to help you fix it. Always wipe cache and davlick when installing something new like gapps or kernels and full wipe when installing a new Rom, unless you are updating a Rom then just Davlick and Cache.
As long as the phone turns on it is not bricked.
housry23 said:
I use AmonRA recovery personally and flash everything through recovery. I had too many problems when I tried flashing things through Rom Manager app. Do you have a nandroid backup? If so install the backup and then boot into recovery and reinstall CM6 and gapps back to back in the same recovery session. If no backup, download PC36IMG that corresponds with your hboot version and put it on the root of your sd card. Boot into bootloader by holding volume down and power at the same time. It will scan the sd card for PC36IMG and then verify it. It will then ask you if you want to update. Select yes and let it do its thing and then when it asks if you want to reboot select yes. This will put you back to stock and may unroot, so you may have to do the root procedure again. Then install CM6 and gapps in same recovery session.
Before all this try wiping cache and davlick cache and reboot. If that doesn't work try powering off phone through clockwork and then boot into bootloader. It will scan for PC36IMG and not find it then you will have options to boot into different things. Select recovery, and it will boot into Clockwork. Wipe cache and davlick cache and reboot. See if this works. If not you will have to nandroid or go back to stock probably unless someone that has had this problem and comes along to help you fix it. Always wipe cache and davlick when installing something new like gapps or kernels and full wipe when installing a new Rom, unless you are updating a Rom then just Davlick and Cache.
As long as the phone turns on it is not bricked.
Click to expand...
Click to collapse
Where can I download the pc36img? Also, it seems that when I try to wipe dalvik cache, it doesn't do anything.
try here
http://forum.xda-developers.com/showthread.php?t=884060&highlight=unroot
If you are having issues getting the img on your SD card, if you have a card reader handy just use that to transfer it over
Tower1972 said:
try here
http://forum.xda-developers.com/showthread.php?t=884060&highlight=unroot
If you are having issues getting the img on your SD card, if you have a card reader handy just use that to transfer it over
Click to expand...
Click to collapse
I did find the correct one for my hboot version, but another question I have is do I need to flash unrevoked-forever-son.zip since I rooted using unrevoked 3.32? Or do I just put the PC36IMG on the sd card and flash it? Thanks.
Okay, I seem to have gotten it back to stock. Thank god, thought I lost my evo for a minute! Thanks to those who helped me out, its 4:45 in the morning and now I can finally go to bed! ;]
LOL glad ya got it back.. Yeah thats where I was heading before I seen your post..Its 5:46 am and Im not sure how many Evo people are actually on at this time so...anyway nite
I stayed on to help as long as I could, but had to go to work. Sorry I couldn't be here to help with more questions. Funny I was just getting up for work and you guys were just going to bed.
Glad you got it fixed for now. Remember to flash CM6 from recovery and not Rom Manager. Also, flash Gapps from recovery and not Rom Manager app. Flash CM then gapps and reboot. Make sure you do a full wipe first though. You could also look for Calkulin's tools thread in Dev section of EVO forum and find his wipe all zip. You just flash it like any other zip but it formats data, cache, boot and system partitions so that when you flash a new ROM nothing is left over from old one. Good luck my friend and happy flashing.
PS. I don't think the stock rom would give you s-on since you already had s-off, so you should be good to go. I could be wrong, but as long as you still have a custom recovery and s-off you should be good to flash any Rom.
evo camera
ok i have a root evo but my camara dosent work ... can some body help me to fx that problem
What rom are you using? Do they list camera issues or camera not working in the initial post with the rom?
Camera
Lets talk about the camera not working here:
http://forum.xda-developers.com/showthread.php?p=10983385
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
it is salvage mod 1.2.1.
JerenOtt said:
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
Click to expand...
Click to collapse
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
JerenOtt said:
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
Click to expand...
Click to collapse
No problem man. It will boot up after a doing a full wipe, most likely.
JerenOtt said:
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
Click to expand...
Click to collapse
Can you boot into the bootloader? Power off your device. Simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text should scroll across the screen and then you will see a few options. One of the options will be recovery. Anyway, at the top of the screen, you should see either S-ON or S-OFF. Hopefully, it displays S-OFF. Anyway, select recovery from the set of options and then, as k2buckley has instructed, go to the wipe menu and wipe EVERYTHING except the SD card itself. When you're done, do not reboot. Go to the flash menu and flash the rom you want to flash. Do not flash the gapps zip yet. Reboot after flashing the rom. I want to make sure you're able to boot into the homescreen. If you're successful, reboot into recovery, wipe cache & dalvik and then flash the gapps.zip. afterwards, reboot. When you're all setup, go back I to recovery and make a nandroid backup.
posting & replying via the XDA Premium app.
also, make sure you got the full ROM, not just the patch for going from 1.2 to 1.2.1. I did that
I was having similar issues, mine went into a boot loop about twice before getting hung up at the initial setup with FCs. I was coming from CM7 Nightly 41 that was acting weird with FC's, I always double wipe cache/dalvik/factory reset. I thought that I might have had a bad download so I re-downloaded, wiped and flashed. I couldn't get past the initial setup so I went back to Ultimate Droid and have been running that for the last 4 days or so with out any major problems except for the Facebook update dicking things up and one random reboot that I had today... I really want to give Salvagemod a shot though since it's Evo-centric.
still not working for me
hey guys... i been trying to boot into salvage mod for the past 2 days... i get it to install just fine i do get the salvage screen up too...
then when the rom is supposed to be loaded up i get the Android dude with emergency call and a crash u keep pressing ok then it goes away and comes back right away... i just wiped everything again and reflashed it and now i am stuck with salvage screen re looping..
any help would be appreciated
thanks
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3? (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Glad you got him going Doug. I had asked him to use RA in a PM, and he responded that he liked clockwork and rom manager better, and wouldn't use RA, lol. I'm glad you convinced him otherwise.
Sent from my PC36100 using XDA App
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
dougjamal said:
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thank you Doug, happy Easter to you as well.
Sent from my PC36100 using XDA App
dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
k2buckley said:
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yup did everything... weird but i got it working now..did everything the same way as b4...its really sweet.. and really fast... thanks a bunch for the help
nxtstep said:
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Click to expand...
Click to collapse
You're very welcome, my friend. I'm glad I was able to help. Take care and have a great day....
posting & replying via the XDA Premium app.
k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
You're a genius. I was doing a data/factory reset, cache, and dalvik, but not boot and system. When i did those, it worked. Thanks!
Here's the deal. I got a new 16GB sd card, copied everything over (including hidden files) and it worked fine for about two hours. Then the screen went black but the LED and soft buttons stayed lit. I did a Clockwork recovery (with a version that I've used successfully before) but it couldn't find SD-EXT so it would boot up to the red Droid "eye" thing (right before loading the homescreen) and then just keep showing that animation.
So I put the old card back in, tried again, and it still couldn't find the SD-EXT file so I've got a phone now which is stuck at this animation.
My question is, can I just boot into Clockwork and install Cyanogen (because I couldn't find a DINC custom recovery file anywhere) from a zip on the SD and have everything start working again? Don't want to mess it up more than it already is.
Unless you have made an SD-EXT partition, it will give that "error" in recovery. Its not actually messing anything up. I'm not sure why its bootlooping but you can try wiping data and cache then reboot or you can download a zip from www.dougpiston.com to take your phone back to stock.
Sent from my ADR6300 using XDA App
I actually discovered that in further research after I posted.
Clearing the cache was a no-go so of DP's site should I go with PB31IMG or with one of his recovery images? I'm think of going with the one with CWM 2.5 on it.
I would try either doing a complete wipe and reflash of whatever rom you choose or you can use the PB31IMG.zip to get back to stock and flash a rom from there. Make sure you're doing a complete wipe as well (wipe data/factory reset, cache, dalvik cache) and do it manually in recovery, not with rom manager.
Sent from my ADR6300 using XDA App
My phone is rooted and I have had many custom roms on my phone, but now when my phone boots, it gets to the lock screen, and reboots automatically... I can get in to the recovery mode, and I flashed couple of different roms, but it ends up the same way - the moment it boots, it starts restarting itself... Any help??
If you flashed without wiping, that might be a problem. I know that when this happened on my old G1, clearing the dalvik cache helped. To do this, go into recovery, then go to "Advanced > Wipe Dalvik Cache". Also, while your in recovery, Fix permissions (same menu as clear dalvik cache), then reboot. The boot should take as long as a first boot, maybe a little quicker, but it should stop it.
another thing it could be is the wifi, on CM7 for example i'd get bootloops if i enabled the wifi on the 1st boot, dunno if the current nightly still does it coz i dont enable my wifi until i done one complete reboot after flashing a new ROM.
Or flash http://forum.xda-developers.com/showthread.php?t=868720
Full wipe 1.3 for ext3 and 1.5 for Ext4 roms , then re flash the Rom ur having problems with.
hmohammed43 said:
If you flashed without wiping, that might be a problem. I know that when this happened on my old G1, clearing the dalvik cache helped. To do this, go into recovery, then go to "Advanced > Wipe Dalvik Cache". Also, while your in recovery, Fix permissions (same menu as clear dalvik cache), then reboot. The boot should take as long as a first boot, maybe a little quicker, but it should stop it.
Click to expand...
Click to collapse
I tried all of this... still no luck... It's the same - boots up, the lock screen shows it self, and then it keeps rebooting...
Any new ideas?
Hmmmmm
What rom are you on at the moment?
It doesn't matter. I've changed couple of them. It started on ARHD, but it's the same when i flash cyanogen... Maybe I should try flashing radio? Because, when it boot's up, just before restarting, i see that it's not connected to the mobile network... And it first started happening when I landed in Turkey... Can it have something to do with their network??
I wouldn't think it's anything to do with the network....but i would flash the reccomended radio (the one from the 4th of january)
http://forum.xda-developers.com/showthread.php?t=877295
Also, wipe every partition manually (except /sdcard !) from the advanced menu in clockworkmod recovery, then use the wipe/factory reset option in the main menu, then flash the rom. If that doesn't work, the only thing i could suggest is using a WWE RUU from here:
http://forum.xda-developers.com/showthread.php?t=824357
Make sure you flash one for either 1.32.405.3 or 1.32.405.6 (those are the only rootable firmwares, and the unbranded ones don't like being downgraded, so you'll need a goldcard if you flash higher). When the RUU finishes, it'll bring you back to stock, then you can root the phone again
As I thought, flashing radio helped!! Thank you very much!!
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.