To install the new 2.7.1 Whompasaurus MA7 rom, do you have to be updated to MA7 already? I'm currently running a stock rooted deodexed LJC rom by Team Venum, and I'm just wondering if there's anything else I have to do before flashing the Whompasauraus Rom?
Nope.
MA7 is included in the Rom. All you need is to do a complete Nandroid backup (so you can restore if you don't like it). Then a complete wipe (follow the instructions in the first couple posts). Flash 2.7.1 and enjoy.
Your system will have MA7 when you've completed the flash. Reinstall your programs and data from Titanium backup and you should be good to go. You could possible restore data only from your Nandroid backup, but I'm not sure how well that would work coming from a different Rom. I wouldn't risk it.
I actually flashed 2.7, didn't like it and restored 2.6 and it was still updated to MA7. When 2.7.1 came out, I updated and have been running ever since.
Whompasaurus 3.0 should be out shortly from what I've been reading on the Dev thread. You might want to wait a few days.
TMPOOLE said:
MA7 is included in the Rom. All you need is to do a complete Nandroid backup (so you can restore if you don't like it). Then a complete wipe (follow the instructions in the first couple posts). Flash 2.7.1 and enjoy.
Your system will have MA7 when you've completed the flash. Reinstall your programs and data from Titanium backup and you should be good to go. You could possible restore data only from your Nandroid backup, but I'm not sure how well that would work coming from a different Rom. I wouldn't risk it.
I actually flashed 2.7, didn't like it and restored 2.6 and it was still updated to MA7. When 2.7.1 came out, I updated and have been running ever since.
Whompasaurus 3.0 should be out shortly from what I've been reading on the Dev thread. You might want to wait a few days.
Click to expand...
Click to collapse
For some reason in clockworkmod recovery when I try to install zip from sdCard the zip file doesn't show up. Checked root explorer and it shows it in the /sdcard/ file slot. Tried installing from external sd card but that just froze up after the first step of basic aroma install.
justcallmejohan said:
For some reason in clockworkmod recovery when I try to install zip from sdCard the zip file doesn't show up. Checked root explorer and it shows it in the /sdcard/ file slot. Tried installing from external sd card but that just froze up after the first step of basic aroma install.
Click to expand...
Click to collapse
Sorry to hear that. Did you try the full recovery? Did you wipe everything before trying to install? I'm using the current version of TWRP, but I wouldn't think CWM would be the culprit. They have 2.9 out now. Haven't found any problems.
Related
So, I've decided I'm going to use ROM Manager to flash a previous version of CWM (2.5.1.4). I'm currently running the 3.0.0.2 but feel stuck from all the reports I've been reading about the latest version not being compatible with older hboot and partitions. I'm scared to do anything...
Anyways, while in 3.0.0.0 I did a back up. Is this going to be compatible with the older version or should I do another one after flashing back?
Also, I don't remember it actually saying "nandroid". It just said "backup". This is the same I'm assuming as it took quite a while to do???
Ok, never mind. Apparently I'm trying to flash that older version and it keeps coming back with an error.
Worked for me.
I restore a 2.x.x backup trough 3.x.x and had CWM 2.x.x then after I backed up some apps with titanium backup I went back to the rom I backed up with 3.x.x and all went fine.
Little confusing but yes I believe you can.
Sent from my PC36100 using Tapatalk
If you want 2.5 again go to post #7 in this thread. Put the file on your sd and power down into bootloader. It will scan the card then ask if you want to update, hit volume up for yes and you're done. Thread- http://forum.xda-developers.com/showthread.php?t=894227
Sweet!!! I just flashed back to the older 2.5.x.x CWM and then flashed a ROM with no problems at all. The only thing that's weird is that ROM Manager still says I have CWM 3.0.0.2.
I was running Android Revolution HD 6.1.5, updated to 6.3.1
without wiping any cache, just download 6.3.1 and
flash it into my phone, just asking is it a correct method?
And, how do i flash mod into desire hd?
Like the same as flashing rom?
Help is appreciated.
Thanks.
With ARHD (and most other ROMs), it's a good idea to wipe before flashing a major new version of the ROM.
For ARHD, this means when either of the first two digits in the version number changes. So from 6.1.x to 6.3.x, you should wipe, or from 6.x.x to 7.x.x (when it's released). Use the superwipe script provided in the ARHD first post. But from 6.3.1 to 6.3.2 you won't need to wipe anything.
The reason for this is that a change in either of the first two digits in the ARHD version number means a new version of Android or a new base firmware from HTC. Some of the key system files will be different, and you're much more likely to have problems if you just upgrade without wiping in between.
Wiping does mean you have to set up your apps again, or you can use Titanium Backup to restore them (user apps or data only, don't restore system apps or data). But wiping is worth it to avoid having any problems later on.
Most mods are in flashable zips and you can flash them in Recovery the same way as the ROM. It's always a good idea to take a backup in Recovery first, just in case something doesn't work or you decide you don't like the mod. The mods overwrite system files, so you can't uninstall them - you have to restore a backup.
Hope that helps, and happy flashing.
preacher65 said:
With ARHD (and most other ROMs), it's a good idea to wipe before flashing a major new version of the ROM.
For ARHD, this means when either of the first two digits in the version number changes. So from 6.1.x to 6.3.x, you should wipe, or from 6.x.x to 7.x.x (when it's released). Use the superwipe script provided in the ARHD first post. But from 6.3.1 to 6.3.2 you won't need to wipe anything.
The reason for this is that a change in either of the first two digits in the ARHD version number means a new version of Android or a new base firmware from HTC. Some of the key system files will be different, and you're much more likely to have problems if you just upgrade without wiping in between.
Wiping does mean you have to set up your apps again, or you can use Titanium Backup to restore them (user apps or data only, don't restore system apps or data). But wiping is worth it to avoid having any problems later on.
Most mods are in flashable zips and you can flash them in Recovery the same way as the ROM. It's always a good idea to take a backup in Recovery first, just in case something doesn't work or you decide you don't like the mod. The mods overwrite system files, so you can't uninstall them - you have to restore a backup.
Hope that helps, and happy flashing.
Click to expand...
Click to collapse
Thanks alot, Just wondering. do i do a advance or a normal backup for the Recovery backup nanodroid
VinFinalist said:
Thanks alot, Just wondering. how do i back up my mods from the Revovery
Click to expand...
Click to collapse
Power down the phone and then hold volume down while you press power on to get into recovery. When you're in recovery there should be a backup/restore menu that has everything you need.
When you backup it basically takes a snapshot of your phone and saves it with a filename that has the date & time (and for 4EXT recovery, it also has the ROM name). When you restore that backup, your phone goes back to the exact state it was when the backup was made.
So for titanium backup is to restore apps and etc
While the Recovery nanodroid is to restore back to everything + rom
i did super wipe and install 6.3.1 and install some custom mod
CRT and BlueHD, Thanks alot !
VinFinalist said:
So for titanium backup is to restore apps and etc
While the Recovery nanodroid is to restore back to everything + rom
Click to expand...
Click to collapse
Exactly right.
Hmm, if i reformat my sd card, will the nanodroid backup
wipe out together?
Yes, but you can copy the folder to your PC and then copy it back afterwards. It's the clockworkmod/backup folder on your card.
preacher65 said:
Yes, but you can copy the folder to your PC and then copy it back afterwards. It's the clockworkmod/backup folder on your card.
Click to expand...
Click to collapse
Oh i see, Thanks a lot, Seriouesly without your help,
My phone won't get to so far. Right now
The Theme BLUEHD is so awesome, Super smooth,
And my Battery life seems to Increased!
No problem, glad you're enjoying the ROM and theme.
Had two backups created with clockwork mod and flashed a diff ROM and after a bit decided it wasn't for me. So i decided to go back to my previous backup which was beanstalk and when I tried to restore it I got error message saying md5 match failed so i tried to restore the other backup i had from a couple weeks back of a diff rom and got the same error message..anyone know why? Only thing I did was rename the backups so I identify them apart.
Never had a issue restoring backups using twrp which is recovery I preferred but a lot of the newer ROMs mostly 4.4 are requiring cwm.
sent from a note taker w/beanstalk 4.4
Nvm please close thread
sent from a note taker w/beanstalk 4.4
booma428 said:
Had two backups created with clockwork mod and flashed a diff ROM and after a bit decided it wasn't for me. So i decided to go back to my previous backup which was beanstalk and when I tried to restore it I got error message saying md5 match failed so i tried to restore the other backup i had from a couple weeks back of a diff rom and got the same error message..anyone know why? Only thing I did was rename the backups so I identify them apart.
Never had a issue restoring backups using twrp which is recovery I preferred but a lot of the newer ROMs mostly 4.4 are requiring cwm.
sent from a note taker w/beanstalk 4.4
Click to expand...
Click to collapse
I had a similar issue. This is how I fixed it
In recovery...
1.) Wiped the device 3x
2.) Wiped Cached 3x
3.) Wiped Delvik cache 3x
4.) Installed TWR through Odin
5.) Flashed CWM 6.0.4.3
6.) Flashed cm11 4.4
7.) Flashed Odexed Gapps
8.) Flashed SuperSU
Hope it helps
Hello everyone,
I have rooted and unlocked my bootloader, and installed CWM 6.0.2 I believe (summer 2012). I was using 4.3 Deodexed ROM and decided to upgrade to 4.4, so I mad a nandroid backup through CWM. Then I found out that 4.4 required me to update my CWM to 6.0.4.3, so I did. After upgrading CWM, I was unable to restore my old 6.0.2 backup. Is there any way to restore it, or do I have to downgrade CWM?
If I need to downgrade CWM, can I first perform a backup of my current 4.4 ROM and then downgrade, or is there a chance it will mess with old CWM?
Thanks in advance,
silentz0r
Sorry for bumping, I have noticed that after upgrading CWM, it made new directories into /sdcard and moved my old directories into /sdcard/0. I tried copying the contents of the old CWM directory into the new one (/blobs and /backup) and tried to restore, but still got the same error message notifying me that no backup is found. Is there no way to restore an old CWM backup with newer CWM?
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
silentz0r_ said:
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
Click to expand...
Click to collapse
Thanks for the heads up!
But shouldn't you just have made a back-up before CWM upgrade, then upgrade CWM, make another backup (just in case) and then install 4.4?
I am still on 4.3 and I will do it this way in the near future.
Any reason to choose one method over the other?
I'm running rooted stock 4.3 (MK1) on SM-P600 and I've done a nandroid backup in TWRP (which I'm assuming I can restore if I don't like KK).
drdoombot said:
Any reason to choose one method over the other?
I'm running rooted stock 4.3 (MK1) on SM-P600 and I've done a nandroid backup in TWRP (which I'm assuming I can restore if I don't like KK).
Click to expand...
Click to collapse
Odin is clean install (wipe everything flash a fresh O/S). OTA is upgrade or dirty flash, you still able to keep your setup and all your installed apps. If your phone is running smooth without any issue then OTA should be fine. If you have weird issues, then Odin is recommended. I see you already have TWRP and probably already rooted that means you can not use OTA method and if you use Odin you will wipe out everything including TWRP, root, your setup all the download apps, system/user data and so on. Your phone will be like a new one. This bring us to the point that you will NOT able to restore 4.3 (you will need to reflash TWRP and so on..) and we have mix reports about once you on Kitkat it's not possible to flash back 4.3 due to different bootloader.
buhohitr said:
Odin is clean install (wipe everything flash a fresh O/S). OTA is upgrade or dirty flash, you still able to keep your setup and all your installed apps. If your phone is running smooth without any issue then OTA should be fine. If you have weird issues, then Odin is recommended. I see you already have TWRP and probably already rooted that means you can not use OTA method and if you use Odin you will wipe out everything including TWRP, root, your setup all the download apps, system/user data and so on. Your phone will be like a new one. This bring us to the point that you will NOT able to restore 4.3 (you will need to reflash TWRP and so on..) and we have mix reports about once you on Kitkat it's not possible to flash back 4.3 due to different bootloader.
Click to expand...
Click to collapse
I updated via Odin and it was a dirty flash and everything works fine. I can still create a folder on the external sd and copy a file from the internal sd to the folder that I created on the external sd.
Regards
colin
colint3 said:
I updated via Odin and it was a dirty flash and everything works fine. I can still create a folder on the external sd and copy a file from the internal sd to the folder that I created on the external sd.
Regards
colin
Click to expand...
Click to collapse
The same for me, but I had to root it again. The root was lost, but everything alse working fine. ( I have sm-p601)