Thankfully I have nandroids of Vaelpak and Myn2.2. I have tried synergy, stock rooted GB, and I can't remember the other two over the last couple days. Each time, it goes like this:
-Nandroid (typically from Rom manager out of laziness)
-Reboot into recovery
-wipe data/cache/dalvik (last few times I did this over and over)
-install zip of new rom
-boot loop
-pull battery and restore backup
I use CM 3.0.0.5 and have also tried RA 2.2.2.
I'm s-off (unrevoked forever).
My SD card is the last thing I can think of. I think I have to format and partition it (I know there are guides here...just never needed it). I just don't get it, I went through a phase where I was doing a new ROM every couple days and never had this issue. Thoughts?
Download Amon Ra 2.3, use as PC36ING.zip. Back up SD card to desktop. Format SD card, then partition it. Look in General or Development for a guide. Mount as MS (mass storage) and transfer files back, leaving out Android.secure, Android, RosieScroll, GoSMS and similar temporary folders and files. Nandroid, wipe system, data, dalvik, cache, factory reset, boot, android.secure and SDext twice. I would suggest VR Superwipe too. Flash new ROM and tweaks (if it is 2.3 Sense probably keep stock kernel). Reboot, enjoy new ROM.
Clockworkmod and AmonRa backups are not compatible.
Sent from my PC36100 using XDA Premium App
tropicalbrit said:
Download Amon Ra 2.3, use as PC36ING.zip. Back up SD card to desktop. Format SD card, then partition it. Look in General or Development for a guide. Mount as MS (mass storage) and transfer files back, leaving out Android.secure, Android, RosieScroll, GoSMS and similar temporary folders and files. Nandroid, wipe system, data, dalvik, cache, factory reset, boot, android.secure and SDext twice. I would suggest VR Superwipe too. Flash new ROM and tweaks (if it is 2.3 Sense probably keep stock kernel). Reboot, enjoy new ROM.
Clockworkmod and AmonRa backups are not compatible.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Other than getting amon 2.3 and copying the files back this was pretty much my plan. I was only going to restore my astro app backups after I get things running again. I do have VR superwipe...never worked with CM on the version I have.
Any reason other than preference for amon 2.3 (maybe the VR superwipe)? If I leave the SD blank but partitioned and just put the ROM back on it, is that an ok idea? I have it backed up...don't know if I have to have the file structure there.
also downgrading CWM down to 2.6.0.1 helped me flash the newer files and scripts as well if you dont like Amon 2.3. Just a thought!
As someone else suggested, you should either use a 'superwipe' script (flashable in recovery) or include /system in your wipe routine.
I don't get why people never wipe /system. That's where the entire ROM lives. If you don't wipe /system, then you are just flashing all kinds of ROMs on top of each other and you end up with a jungle of files from various ROMs all mixed together.
You might get lucky, many ROM devs account for this and wipe your /system partition for you before flashing the new files.
github said:
As someone else suggested, you should either use a 'superwipe' script (flashable in recovery) or include /system in your wipe routine.
I don't get why people never wipe /system. That's where the entire ROM lives. If you don't wipe /system, then you are just flashing all kinds of ROMs on top of each other and you end up with a jungle of files from various ROMs all mixed together.
You might get lucky, many ROM devs account for this and wipe your /system partition for you before flashing the new files.
Click to expand...
Click to collapse
Agreed. I don't believe in superwipes. But I DO agree to manually wile each category, except SD Card, including system.
What worked for me..
I had to upgrade my HBOOT from:
EVO_HBoot_0.76.2000
to
EVO_HBoot_0.97.0000
to load the Synergy ROM.
No wipe, wipe utilities, formats or partitions would work. Upgrading the HBoot fixed the boot loop issue... for me.
2k6_tx_dad said:
I had to upgrade my HBOOT from:
EVO_HBoot_0.76.2000
to
EVO_HBoot_0.97.0000
to load the Synergy ROM.
No wipe, wipe utilities, formats or partitions would work. Upgrading the HBoot fixed the boot loop issue... for me.
Click to expand...
Click to collapse
I am on the older HBOOT also. I will try this if the SD wipe and partition fails me. It could be this since it's recent ROMS giving me issue.
To the wipe /system comments...I did that one time for sure. Not each.
Related
hey guys,
i have one (very important to me) question.
I´m using MIUI ROMs on my HD2 and as you might know every week a newer version is comming out.
Yesterday i created a knew ext3 partition for my current ROM.
Can i flash the new ROM like an update or something else ? So i don´t have to create a new partition and install all apps again ?.... I am using of course MAGLDR and Clockwork Mod....
I would be glad to get an answer to this ...
Thanksss....
As long as it's just a newer version of the same rom, just go into CWM, go to backup/restore, and make a backup. Then flash the new rom, and then in CWM, go into backup/restore again, and do a custom restore, restoring only data and sd-ext.
Then the only difference you will notice is the new rom, not the loss of apps and data.
To update version of same MiUi Rom:
copy the new ZIP file to SD card.
reboot to recovery
Wipe Cache and Dalvik Cache
DON'T WIPE DATA
Flash the new Zip file.
All your apps are there with the new ROM.
pc2058 said:
To update version of same MiUi Rom:
copy the new ZIP file to SD card.
reboot to recovery
Wipe Cache and Dalvik Cache
DON'T WIPE DATA
Flash the new Zip file.
All your apps are there with the new ROM.
Click to expand...
Click to collapse
As long as it's just a newer version of the same rom, just go into CWM, go to backup/restore, and make a backup. Then flash the new rom, and then in CWM, go into backup/restore again, and do a custom restore, restoring only data and sd-ext.
Then the only difference you will notice is the new rom, not the loss of apps and data.
Click to expand...
Click to collapse
Okay thanks guys for your help
i will try both solutions
Thank you very much
I was using twrp and kept getting into bootloops so here is advice from a few hours ago. I suggest using RA to wipe boot, system, cache, dalvik, and data before flashing from stock. It stopped the bootloops and now im on cm 7.0.3.1
Sent by breaking the sound barrier
Wiping system is something that is often overlooked. The factory reset options in the recoveries do NOT wipe system. You have to do it manually. System is where the ROM gets stored. Typically upgrading is safe (check with the ROM dev), but changing ROMs (esp Sense -> CM7 and back) should get a system wipe.
Some ROMs do this automatically, some don't.
Also, use what ever recovery you like the best. Amon_RA is tried and true. Mature and proven. CWM has a shady history and while it might be fine now, many people avoid it. TWRP is the baby. It's freshly born and not as full featured as Amon_RA just yet.
Enjoy.
Thanks for the info. I will be flashing my first ROM on my newly rooted Evo 4G tonight!
Use" calkulins format all " before flashing any new rom
You really don't need to use those format all programs, if you use Amon Ra. Just wipe everything except the SD Card, really, and that should be done before you flash any ROM (Although SOME people will disagree). Better to erase all doubt than to leave a chance that an improper wipe caused issues.
Indirect said:
I was using twrp and kept getting into bootloops so here is advice from a few hours ago. I suggest using RA to wipe boot, system, cache, dalvik, and data before flashing from stock. It stopped the bootloops and now im on cm 7.0.3.1
Sent by breaking the sound barrier
Click to expand...
Click to collapse
Before you flash crazy you should think about partitioning your SD card(with amon ra2.3)that way you have that out of the way incase you wanna try a kingdom Rom, its something I wish I would have done before I went any further with flashing, just make sure you back up your SD to your computer before hand. Have fun!
Hey,
I tried installing Android using cwm rec., everything goes well, but the android does not boot, it gets stuck on the booting screen, i tried several time, diff roms, still no results, can any one help me if im missing something? :S
make sure you are removing any leftover stuff from a previous rom on the SD card.
So in CWM, before you go to flash the rom, do a 'wipe data/factory reset' which should clear out the ext partition and the .androidsecure (or whatever its called) folder on the FAT32 partition.
I have done that, but it wont work, i've cleared cache too,
Btw how much time does it take on the first boot?
dont know, sorry, i've never used a sense rom, but i've seen posts referring to a good ten minutes or more, depending on the sd card and teh rom being installed, and how much stuff is moved to sd. Some roms just put just the app and dalvik folders there, some put much much more.
If it were me, i recon id be pulling teh battery at 10 mins.
do you have a 1gb partition on your sd card?
is the partition information for the rom correct?
are you using magldr or clk?
I have Tried wit a 2GB and a 1GB partition, I have Magldr 1.13, The Cwm size is also correct, 400mb for a 300mb rom.
amigo max said:
I have Tried wit a 2GB and a 1GB partition, I have Magldr 1.13, The Cwm size is also correct, 400mb for a 300mb rom.
Click to expand...
Click to collapse
You're absolutely sure the ROM you're trying to use is correct for the type of Android bootloader you have? (clk/magldr)
Did you check the MD5 sum of the rom.zip you downloaded? Maybe you got a bad download.
Did you wipe EVERYTHING? (full wipe, then in advanced, wipe dalvik and cache)
What method did you use to partition your sd card?
For now i Have followed the exact instructions from the DHD Desire rom, and it seems to work, I think the problem was wit the CWM recovery, I downloaded it from the Rom's page and it worked.
When I tried installing another Rom, I encountered the same prob, so I installed recovery again and it worked. Do I have to keep changing the recovery every time I put another Rom?
Sent from my HTC HD2 using XDA App
Yeah, some roms require different partition layouts, which are made when you flash CWM recovery.
If you are going from one rom to another and they both require the same partition layout, or if the new rom you're flashing requires a smaller system partition than your current rom, then you won't have to re-flash CWM. In that case, you'd just have to do a full wipe and then flash ur new rom.
The required/recommended CWM partition size is usually somewhere in the first few posts of the thread you download the rom from.
Sent from my HTC HD2 using XDA App
Just an small tip, but I hope it would useful to somebody.
I was using cm7-based custom rom(KGPNEOK 3.0 FINALE), and tried re-partitioning with Blackrose hboot.
I was using DTAPPS2SD(cachesd and zipalign), and used Amon-Ra 2.2.1 recovery to make a nandroid backup, And followed the instructions on Blackrose thread to repartition internal storage.
I partitioned my Nand size system-150 cache-10 data-all the others.
After making an backup I applied repartitioned .nb0 file, and restored the nandroid backup that I made just before repartitioning.
And all the things worked flawlessly, with 200mb of data space.
I plan on doing this sometime soon, But need to read more about it before I am willing to try it. I am still fairly knew with all this. I have already bricked 2 Samsung Captivates lol. Luckily AT&T's device center takes them back and replaces them with new ones with 90 day warranties.
Was hoping to do this for my n1 for the new alpha9 of ics.
does this affect rom performance?
So if I Nandroid my current miui rom, then partition, I can restore my backup like normal after its partitioned? What are the recommended settings for miui?
do you need to wipe system before nandroid restore?
my nexus one with amonra (latest) and cm7nightly, can't mount /system after applied custom partition. Saw errors regarding mtd in dmesg. OK after i fastboot erase system.
cache and data were mounted with new size automatically without the wipe.
Sent from my Nexus One using XDA App
I used Blackrose to repartition my N1 to S/C/D=220/16/200 for an ICS try (see texasice thread). Then i went back to my previous rom (nandroid bckp) and with a full wipe everything was OK.
This has been bugging me and I can't seem to find anything on here to explain it.
I have installed custom ROMs on my N7. Problem is most ROM instructions say to do a full wipe/factory reset. When I do that, the downloaded ROM that was sitting on the SDCard gets wiped out as well.
I then have to go back and search for info on how to reset/restore the N7 and start all over, because the recovery (both CWM and TeamWin) don't let me mount the SD card to copy the needed zip over.
How can I do the recommended data wipe without losing the sd card contents?
Failing that, what's easiest way to get the ROM zip back on the N7 when the recovery won't allow it?
Thanks
dont wipe data...
just do a 'factory reset' in custom recovery...then flash a rom
I use TWRP & don't wipe everything, just System & Factory (to delete installed apps).
This is after wiping Cache & Dalvik Cache.
Unless I'm missing something a data wipe will wipe everything except recovery.
I don't think we have the option to exempt the media folder like on other devices.
(you type faster than me PG)
I appreciate the suggestions, and I've done the factory wipe. It wiped out the /SDcard folder contents where the zips were.
How do I get zips back on the N7? tried ADB, tried sideload from TWRP, nothing works.
Having many more problems than the last time I did this.
jneg123 said:
I appreciate the suggestions, and I've done the factory wipe. It wiped out the /SDcard folder contents where the zips were.
How do I get zips back on the N7? tried ADB, tried sideload from TWRP, nothing works.
Having many more problems than the last time I did this.
Click to expand...
Click to collapse
factory reset in TWRP doesnt touch /data/media
are you sure you are on the most recent version of recovery?
updated to latest recovery version, that seemed to be my issue. sd card now untouched.
Pirateghost said:
factory reset in TWRP doesnt touch /data/media
Click to expand...
Click to collapse
Pirateghost speaks the truth.
The stock recovery however, wipes everything with it's "factory reset".
It's a little bit unfortunate that the identical terminology is used. No doubt new folks will occasionally get bit by assuming they are the same.
I haven't used cwm yet; not sure what it means by "factory reset" - or even if it uses that terminology.