I have a few questions which I am a little unclear after rooting my Eris:
What is the purpose of partition sdcard option on the Android Sys Recovery Menu? Within it, there are 4 options and what are they?
is Nand backup sufficient or do I need Nand + ext backup? I am getting an error when running Nand + ext.
When installing custom rom, do I have to do the amon's recovery image step or do I just boot the phone with the system recovery, wipe and flash zip from sdcard?
Thanks.
Aman Ra replaces the default recovery. IE when you hold volume up while powering on you are in Aman Ra, this will be a permanent change unless you unroot I think. Essentially as long as you installed it when you rooted, you never install it again.
The partitions are used for Apps2SD. as is the ext partitions. Unless your using Apps2SD you only need to do a nand backup. Once you start using Apps2SD you will want to do both.
Lastly often enough when a nand+ext back up will not work, it is because you are missing a /sys/sd folder.
thx for the info
I got it now, so for installing custom rom, all I have to do is boot to the recovery, do a wipe, flash sd card. I am glad I rooted
Related
I used to flash roms all the time but its been a while and i forgot the order of flashing
1. put rom on sd
2. boot into recovery
3. wipe/factory reset
4. choose zip to install
5. flash rom
6. reboot
where does the partition fat32/swap/linux and convert ex2 to ex3 go in that order?
thank you!!!
It doesn't matter.
What if you have apps2sd, it won't make any difference even though you're wiping whatever is in your ext once you flashed the rom when you partition?
really? for some reason i thought it had to go in a particular order to avoid fc's and speed. but it doesnt matter if its before or after flashing the rom?
Sorry I lied, no really it doesn't matter.
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.
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
I wanted to make a nand backup but to my surprise I can't start CWM... I boot into MAGDLR then select option 8 and it says:
Android load raw
some numers
load done!
123456
GO GO GO!
Smallbandversion
15.42.50.11u_2.15.50.14
and then it hangs... is it save to reinstall CWM? or will i lose all my data?
realy.need this i think its simple !
Go to the "clockwork 5.0.2.6 yes/no" thread, get the SD version and nand version of cwm, unpack the SD version to SD root, and copy the nand version.zip to SD, start magldr, 'boot ad sd, will start cwm from your SD card, use it to flash the nand version.zip
samsamuel said:
Go to the "clockwork 5.0.2.6 yes/no" thread, get the SD version and nand version of cwm, unpack the SD version to SD root, and copy the nand version.zip to SD, start magldr, 'boot ad sd, will start cwm from your SD card, use it to flash the nand version.zip
Click to expand...
Click to collapse
Thanks! But will it preserve my rom and data? Or will I lose everything?
It'll save it all. Its just flashing the recovery.img to the recovery partition. The only possible fly in the ointment would be if your recovery partition is too small for the latest recovery.(unlikely, but possible) but even then you can use the SD cwm to take a backup, reflash the partition layout with recovery, then reflash your rom and selectively restore sd-ext and data.
Thanks for the report so far, will try to reflash the recovery tomorrow !
Edit:
that did it (lol forgot this)
I was trying to install a custom ROM, the first thing that should've made me stop is the fact i couldn't install TWRP and i only could boot from one specific img.
Anyways i proceeded, wiped everything, as always no backup, because YOLO, but this time TWRP didn't install the zip (zip file format error), the custom recovery i can boot from seem to be bad or something. Then i tried to install stock to get my phone to work, but it cannot install anything, /data is weirdly mounted, using the whole disk and leaving no space for other partitions.
Anyone has an idea? or do i have a brick for a phone now?