[Q] Can't flash anything over CM6... even after wipe - Droid Incredible Q&A, Help & Troubleshooting

So I downloaded Skyraider 3 thru ROM Manager, did a backup and fill wipe, when it reboots, the CM6 splash is stuck in a loop.
So I rebooted back to recovery, did a manual full wipe, and installed the SR3 .zip from the menu, and STILL CM6 boot loop.
Maybe related to the problem is that I also can't get the droid2 keyboard mod to "stick" I'll install it and it works until I reboot -- then I'm back to the android keyboard with FC's every other word.
Help!

hometoast said:
So I downloaded Skyraider 3 thru ROM Manager, did a backup and fill wipe, when it reboots, the CM6 splash is stuck in a loop.
So I rebooted back to recovery, did a manual full wipe, and installed the SR3 .zip from the menu, and STILL CM6 boot loop.
Maybe related to the problem is that I also can't get the droid2 keyboard mod to "stick" I'll install it and it works until I reboot -- then I'm back to the android keyboard with FC's every other word.
Help!
Click to expand...
Click to collapse
What all did you wipe? Factory reset, wipe cache, wipe Dalvik?

From Clockwork recovery, "wipe data/factory reset" which does system/data/cache/sd-ext.
Update: I'm redownloading the SR3 mod -- there might have been an issue with the zip file. (this still wouldn't explain the keyboard reverting on reboot though)

I know it sounds redundant but I've found issue when I don't wipe cache seperately. You also need to go into advanced and wipe Dalvik cache.
Sent from my HTC Incedible via XDA App.

I'm either an idiot (likely) or the .zip I was flashing was corrupt.
Either way, this idiot is up and running.

Related

[Q] Salvage Mod 1.2.1 won't boot.

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!

[Q] can't run any new rom, hangs at white htc incredible screen on boot

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.

[Q] [HELP] Borked up phone!

Ouch. Been running various ROMs and various kernels. Had a ROM installed with imosyons exp2 kernel and touch recovery. Was trying out 1.42GHz. All of a sudden phone spontaneously rebooted. Hung repeatedly on Google screen. OK, no problem. Will wipe cache and dalvik cache and reinstall kernel. Hung on the dalvik cache wipe. OK, will skip the wipe and just load kernel. Opps, hung looking for .zip files. Opps, will reload recovery. Still hanging everywhere.
Used Galaxy Toolkit to reload stock images. It did do 1 bootloop, but then acted normally.
Reloaded everything. Left 1.42 alone! Worked all day and then I installed ROM Manager to make a nandroid backup. It wanted to install CWR so I let it. Upon a reboot it went into bootloops. Now I cannot do a factory restore (all my data is there upon a reboot). Tried the ODIN solution but it's still not clearing data. Apparently no PIT available to reparition? Shoot, what do I do!

cm9 and gapps?

so i loaded cm9 ics on my fire and everything worked great. then i flashed the gapps zip and when i turn on the fire the prompt screen comes on that comes on everytime you buy a new device, the one where you are prompted to touch the android and then you will enter your info and stuff. well, everytime i touch the android, it says "unfortunately the setup wizard has stopped" with a force close button. any ideas how to get gapps on?
May not have wiped everything properly, or flashed a corrupt gapps zip.
Either way, you can get around the issue from TWRP by deleting the file /system/app/SetupWizard.apk using the built-in file manager or ADB.
Dasanko said:
May not have wiped everything properly, or flashed a corrupt gapps zip.
Either way, you can get around the issue from TWRP by deleting the file /system/app/SetupWizard.apk using the built-in file manager or ADB.
Click to expand...
Click to collapse
Agreed, first try to wipe again. Factory reset (2x) for good measure, wipe cache, wipe Dalvik, Flash ROM, flash Gapps, boot. May even wipe cache/dalvik again after flashing. Not usually needed, but sometimes KF can get stubborn.
chemo1191 said:
Agreed, first try to wipe again. Factory reset (2x) for good measure, wipe cache, wipe Dalvik, Flash ROM, flash Gapps, boot. May even wipe cache/dalvik again after flashing. Not usually needed, but sometimes KF can get stubborn.
Click to expand...
Click to collapse
Question...I am too having this issue. Only difference is something happened to my USB and my computer can't install the device files anymore so I'm flashing the ROMs thru ROM manager now since I can't connect my phone to the computer. I know I'm using the right gapps but if I delete the apk for the setup wizard how will i be able to sign into my google account?

Stuck in boot loop after flashing CM7

Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!

Categories

Resources