[Q] Flashing Cyanogen when I have Skyraider - Droid Incredible Q&A, Help & Troubleshooting

I am running Skyraider 2.5.2 Sense (Froyo) on my HTC Incredible with Clockwork Mod 2.5.0.1 recovery with Baseband 2.05.00.06.11 & Kernel 2.6.32.15g5e1ad8b. PRI 1.28_002.
I tried to flash the Android DSP equalizer (http://bel.fi/~alankila/android-dsp/) and my phone locked up and I had to nand & Titanium restore.
My phone's happy now but I'd really like the DSP - which is supposedly working on Cyanogen 6.0 RC2.
I have no idea what might happen if I use ROM Manager to download and flash Cyanogen 6.0.0-RC3 at this point.
Sorry if this is a moronic question but any illumination would be welcome. Thanx!

As a rule of thumb, ALWAYS wipe before flashing a rom. The only exception to the rule is when a dev Specifically says otherwise.
My rule of thumb is to manually change roms (not using rom manager). Backup, wipe 2x each (data + cache), wipe dalvik cache,then flash. I have NEVER had boot loops or anything else happen after following that.
As to the dsp, I can confirm that the dsp with eq is NOT working with skyraider. It does work with CM6 though.
Hope this helps.
Sent from my ADR6300 using Tapatalk

what he said. ^^^ ditto. nandroid backup, wipe wipe wipe, install new rom.

I usually backup current rom, download new rom and wipe before installing all from rom manager. I have not had a problem yet.
Sent from my ADR6300 using Tapatalk

Related

ClockworkMod 3.0.0.5 not fully wiping?

I upgraded to the latest clockworkmod 3.0.0.5 and when I switch ROMs, I notice some of my item's are still "cached". For example, I was using Evervolv and then did a wipe of data, cache, and davlik, and flashed the RC1 for CM7. GApps are not packaged with either of these ROMs but when I booted up CM7 for the first time after flashing, GApps are installed, without me doing so. Is there an issue with the latest version of deleting cache or am I not doing enough wiping?
I am running into exactly the same problem. Works fine for flash over but the minute you choose wipe in ROM Manager of do a data wipe in recovery it does not make any difference. Not sure it is clearing anything in cache or data or at least consistently.
None of the other ROM devs have posted this so I am not sure what is going on
I am still messing with it
EDIT: You may want to post this in the ROM thread also so the devs are aware
i had the same problem.. From what i have been ready downgrade to cwm 2.5.1.2 and it should help..it did for me. the new cwm isnt running as good with some of the roms out there.

CM7 final bootloop

So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.
eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?
teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!
I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.
Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.
SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu
Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk

ROMs won't boot unless gapps is flashed

So I've been using Savage-Zen RC2 and was trying to flash a few ROMs over the past few days (SalvageMod1.2.1 and Savaged-Zen RC3) and I've notice that both will throw me into bootloops unless I flash gapps along with them. This makes me think I'm not getting a really thorough wipe through Amon_Ra and that I might need to try something different. Any suggestions?
I believe both of them inlcude other things in their Gapps. I know the Gapps files specific to those two ROMs are bigger than the standard one. Might be that it includes something that you need.
How are you wiping though? Did you try Calk's format all?
That should not be occurring. I am currently running SalvageMod 1.2.1 and it loaded fine before and after I flashes gapps. I usually flash the rom first, boot to my honescreen and then go back inti recovery, wipe cache and dalvik and then flash gapps. I've never had a problem. If your recovery is RA v2.3, go to the wipe menu and wipe EVERYTHING except the SD card itself and then flash the SalvageMod 1.2.1 rom. After that, boot into your homescreen BEFORE flashing gapps. You should be able to do so. Also, make sure you use the gapps zip from the SalvageMod thread.
posting & replying via the XDA Premium app.
dougjamal said:
That should not be occurring. I am currently running SalvageMod 1.2.1 and it loaded fine before and after I flashes gapps. I usually flash the rom first, boot to my honescreen and then go back inti recovery, wipe cache and dalvik and then flash gapps. I've never had a problem. If your recovery is RA v2.3, go to the wipe menu and wipe EVERYTHING except the SD card itself and then flash the SalvageMod 1.2.1 rom. After that, boot into your homescreen BEFORE flashing gapps. You should be able to do so.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Actually I gave it a few more minutes because I had to step away from my desk and it was all good...if anyone could hook me up with calk's format all script it'd be much appreciated...googling returned nothing.
calk's is short for calkulin. Probably why. Have to flash it in Amon RA or Clockwork 2.5 or less though.
jstalford said:
calk's is short for calkulin. Probably why. Have to flash it in Amon RA or Clockwork 2.5 or less though.
Click to expand...
Click to collapse
Thanks!!! 10char
If you wipe everything in amon RA v2.3 wipe menu (the SD card being the exception) you should not have to use the format-all zip.
posting & replying via the XDA Premium app.
dougjamal said:
If you wipe everything in amon RA v2.3 wipe menu (the SD card being the exception) you should not have to use the format-all zip.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I figure it can't hurt. Either way I've gotten salvage to boot now so it's fine. Currently dealing with apps not installing after downloading them from the market. Any ideas?
Correct, but technically it's less wear on the hardware keys. Although I usually do both just to be safe so I'm really just killing my phone faster . Some people do have issues with it, although they may be having other things going on or a bad dl. I use it like every friggin day.
I think there was some residual stuff left over from Savaged-Zen, which I think is a fantastic ROM but not yet sturdy enough for prolonged daily use. Can't wait 'til it's finished...anyway
After running Calk's format all and wiping again I booted into Salvage with NO bootloops and NO market issues and all my old apps downloading automatically. Sounds like a winner.
Either way I'm gonna let the SZ guys know about this because it might be something on their end.
Go to applications in the settings Menu, find the market and clear the cache for it. If that doesn't help, wipe the data from the Market too.
Sorry, didn't realize you fixed it. That goes for all AOSP GB ROMs right now though. If the market doesn't work, clear the cache. Usually fixes it for me.

[Q] Question about installing CM7 steps

I have an incredible running sock 2.2
I have radio version 2.15.00.07.28
I rooted my phone with unrevoked
I installed rom manager and clockwork recovery
I used rom manager to take a backup of the current rom
I used rom manager to download CM7
Now can I just go into rom manager and pick install rom from SD card and browse to the CM7 download? Should I check "Wipe Data and Cache" when installing CM7? Do I need to do anything special to make sure the GPS works once CM7 is installed?
If I decide I don't like CM7 can I boot into recovery and apply the clockwork backup and my phone will be in the exact same state as before the backup? Apps and everything?
Am I missing any steps?
Thanks.
Yep you've got everything right. You can install using rom manager but alot of people have better luck doing it manually through recovery. Make sure you wipe data and cache, also flash the Google apps zip right after CM7.
Sent from my ADR6300 using XDA App
When coming from a non CM7 Rom, it is better to go into cwm and clear system as well as everything else before flashing.
That's a good point. When I do a full wipe I go into mounts and storage>format boot, format data, format system, format cache, in addition to wipe data, wipe cache, and dalvik cache wipe.
Sent from my ADR6300 using XDA App
Thanks for the info guys
What you type is right.just doit
Sent from my Optimized Inc using XDA App

CM7.2 - Reboot on GPS Lock after all GPS Fix methods

Alright after all what I have done, I am still getting reboots when I open Google Maps and GPS is just about to lock to a location.
Things I have done:
1. Start from scratch - Format and wipe /system, /data, /cache, /sdcard, /sd-ext, delvick cache, run Caulkin's Format ALL, again wiped everything above, and last did VR_SUPERWIPE.zip
2. Flashed STOCK Sense Rom 4.67.651.3 (new ota update)[ROM] and rebooted into Stock Rom.
http://forum.xda-developers.com/showthread.php?t=1455340
3. Used MSL Reader + ##GPSCLRX# (##4772579#) method. Updated PRL while in SENSE Rom, and everything under settings > about phone > updates
4. Repeated Step 1
5. Flashed CM7.2 supersonic
6. Used Titanium backup to install only apk files for applications, not data files. Nothing from system was restored.
7. Did the Google Play updates to all apps, rebooted, Did more updates.
8. No task killers were installed, only major change is I went from ADW Launcher to GO Launcher EX.
Now I open the maps, I am on 3G speeds, maps load up, but within 5 seconds the GPS Locks, and booom Reboot.
Sometimes after the reboot, while in the middle of the CM7 boot animation, it will reboot again.
Only way to get everything back to stable is to wipe delivk cache again.
Extra steps taken:
Method 1 - Failed
1. Wipe Delvik cache
2. Flash Qualcomm Vision GPS Driver v1.1 (Flash 3.zip)
Method 2 - Failed
1. Wipe Delvik cache
2. Flash GPS_Supersonic_FIX_Flash2.zip http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
I am really fed up now with my Evo 4g.... I need someone to help me out:crying:
UPDATE 08-24-2012
Roms Tried:
CM7.2
CM7.1
CM6.1
Decks ReLoaded
{LOTK]ReLoaded
Senseless_EVO v.1.1 (not asop)
Stock RUU 1.32.651.1
Shooter Rom on Sense3.0
Team DIRT's Rom
MIUI
CIUI
Lewa OS
Now on Nitrous ROM
Recoveries Tried:
CWM 5.2.*
Team Win's - TWRP
Now on RA-supersonic-v4.3-smelkusMOD
GPS Fix'sTried:
GPS_Supersonic_FIX_Flash2.zip - Qualcomm Vision GPS Driver v1.0
GPS_Supersonic_FIX_Flash3.zip - Qualcomm Vision GPS Driver v1.1
GPSCLRX Sense Workaround with CWM flash of CM7.2
Last try was on GPS_Supersonic_FIX_Flash3.zip
WIPE method:
Factory Reset
Cache
Delvik Cache
Data
SDCARD - ext3
SDCARD - .android_secure
BOOT
System
DATA:Battery Stats
DATA:Rotate Settings
Cache again
Delvik Cache again
Repeat ALL above again - (Yes, I know its excessive):cyclops:
Any other suggestions?
________________________________________________________________________
Device: HTC Evo 4G
Rom: CyanogenMod 7.2
Kernel: 2.6.37.6-cyanogenmod-g0799e00
Hardware: 0003
Baseband: 2.15.00.12.19
PRI: 2.15_003
NV: 2.15_003
PRL: 60683
HBOOT: 2.10.0001
Recovery: CWM 5.0.2.2
Have u attempted using another aosp rom like reloaded to see if the problem lies in cm7.2. I can verify that gps is flawless with reloaded.
Also, switch to amonra or smelkus recovery. Clockwork always causes problems
fitz420 said:
Also, switch to amonra or smelkus recovery. Clockwork always causes problems
Click to expand...
Click to collapse
how would flashing another recovery resolve issues at this point of time?
Whats the latest AMONRA version?
rcatank said:
how would flashing another recovery resolve issues at this point of time?
Whats the latest AMONRA version?
Click to expand...
Click to collapse
It wont fix anything. It will eliminate a bad flash/wipe from possible problems. Just do the sense ##gpsclrx# and flash to a different aosp like decks or reloaded and see if the problem persists.
still having issues
So I have been through most AOSP roms lately.. And I am still stuck on the reboot when I load up maps. Now though its getting worst.
Maps works for may be 10 seconds, get a good lock, but then within 10 seconds it reboots. Then gets stuck in a boot loop, until the battery is burning hot.
Another issue is now I get random reboots even while surfing the internet, loading and restoring from Go Backup / Titanium. All Google Inc apps are always fresh from Play store though. Since I moved to AmonRA and then TWRP, it didn't help what so ever. So finally I moved to RA-supersonic-v4.3-smelkus. I replaced my Samsung 32gb class 10 card with what came with the phone which was Sandisk 16gb class 4, but same issue. BTW, I always used 1gb of ex3 partition for A2SD when I loaded up any of the roms like MIUI, CM7.2, CM7.1, most any of the ICS beta's posted in the past month, and finally also tested Revolver, and the latest Deck's Reloaded GB2.3.5 with Mason G d15rc3 kernal. I found Saveged Zen to be no good with any of the roms, nor did I find Tiamat any help.
Now I am with RA 4.3 smelkus recovery, and Deck's latest rom with Mason Gd15 kernal, and the GPS Flash 3 zip. Still issues
I have been trying to produce logcat's but, the reboots are not letting me save anything before the dump to file happens.
try a sense rom and see if you are still having issues. I have run CIUI and GTR twinturbo, which are both cm7.2 based and have NO gps issues after flashing the GPS supersonic flash3.zip
Try unrooting and see if you have the same issue, it could be a hardware issue you could get replaced with sprint. Otherwise re root and try again.
Sent from my PC36100 using xda premium
BigSmoke53 said:
Try unrooting and see if you have the same issue, it could be a hardware issue you could get replaced with sprint. Otherwise re root and try again.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
id try a stock rooted rom before going through unrooting and rerooting .

Categories

Resources