I have a question I'm on an old old BACKside-IHO build can I install CWM-Green w/BacksideUpdater Auto-Install and update to most recent ROM from there or do I have to flash the newest ROM first?
Last edited:
[Recovery] CWM-Green w/BacksideUpdater Auto-Install
- Thread starter JerryScript
- Start date
I would recommend installing the latest version of the ROM first, then using that to install the new recovery. The new ROM makes it almost effortless to install the recovery.
You have to flash a BACKside IHO ROM before you can use the AutoUpdate, that function is inside the Android ROM.
Sent from my LG-VM670 using Tapatalk 2
No, you don't. You can replace the apk in current ROM and update from it.
Oh my bad, I didn't even read the first part of dude's post :/
Sent from my LG-VM670 using Tapatalk 2
Sent from my LG-VM670 using Tapatalk 2
FYI- Once you have updated to a ROM with BacksideUpdaterV3.2, you can install CWM-Green-Recovery completely safely. Open the updater, press your menu key, select Show All Versions, then scroll all the way down.
You can just click Install A Recovery, but that method doesn't have md5sum checks to insure the package is not corrupt (I wanted to leave the ability to install any recovery).
Choosing from the Show All Versions menu will give you the download link, and check the downloaded file for the proper md5sum, and if it accidentally was downloaded as a txt file (happens all the time on phones), it will change it to an img file automatically.
You can just click Install A Recovery, but that method doesn't have md5sum checks to insure the package is not corrupt (I wanted to leave the ability to install any recovery).
Choosing from the Show All Versions menu will give you the download link, and check the downloaded file for the proper md5sum, and if it accidentally was downloaded as a txt file (happens all the time on phones), it will change it to an img file automatically.
You can just click Install A Recovery, but that method doesn't have md5sum checks to insure the package is not corrupt (I wanted to leave the ability to install any recovery).
Choosing from the Show All Versions menu will give you the download link, and check the downloaded file for the proper md5sum, and if it accidentally was downloaded as a txt file (happens all the time on phones), it will change it to an img file automatically.
Very, VERY nice!
[NOTE]Small bug in BacksideUpdater I wanted to let everyone know I'm already fixing:
Bug: sometimes the display window appears blank, hiding the android logo
Cause: large amount of text being replaced by small amount, and gravity not set
Workaround: if black box appears over the android logo with no text, flick it up to scroll the hidden text into view
Status: fixed in code, should work properly in next release
[/NOTE]
Bug: sometimes the display window appears blank, hiding the android logo
Cause: large amount of text being replaced by small amount, and gravity not set
Workaround: if black box appears over the android logo with no text, flick it up to scroll the hidden text into view
Status: fixed in code, should work properly in next release
[/NOTE]
Need some opinions:
I'm working on the automatic backup process, and I'm trying to decide if I should include wiping cache/dalvik before making the nandroid backup. I always wipe cache/dalvik before I make a nandriod, because it makes the backups smaller, and the backup and restore processes are faster. First boot after restoring a wiped backup takes as long as first boot after flashing a ROM update/install.
I don't see any reason not to wipe cache/dalvik before an automatic backup, but would like opinions.
I'm working on the automatic backup process, and I'm trying to decide if I should include wiping cache/dalvik before making the nandroid backup. I always wipe cache/dalvik before I make a nandriod, because it makes the backups smaller, and the backup and restore processes are faster. First boot after restoring a wiped backup takes as long as first boot after flashing a ROM update/install.
I don't see any reason not to wipe cache/dalvik before an automatic backup, but would like opinions.
Jerry: I was always on the fence myself about whether to wipe cache and dalvik before nandroid, for the exact pros & cons reasons you mention.
I guess when testing and messing around, sometimes it's nice to preserve an exact backup including cache & dalvik - warts and all.
But for typical ROM updates, I think wiping makes sense.
Edit: I see, I am sorry. Not sure what for, but nevertheless...
I guess when testing and messing around, sometimes it's nice to preserve an exact backup including cache & dalvik - warts and all.
But for typical ROM updates, I think wiping makes sense.
Edit: I see, I am sorry. Not sure what for, but nevertheless...
Last edited:
Need some opinions:
I'm working on the automatic backup process, and I'm trying to decide if I should include wiping cache/dalvik before making the nandroid backup. I always wipe cache/dalvik before I make a nandriod, because it makes the backups smaller, and the backup and restore processes are faster. First boot after restoring a wiped backup takes as long as first boot after flashing a ROM update/install.
I don't see any reason not to wipe cache/dalvik before an automatic backup, but would like opinions.
i always do the wipe process before backup. makes sense to do it for smaller backup size,as for first boot times,i dont see a few extra seconds at first boot upon restore as a big issue.
Wiping would work for me just fine. Great that you are working on this.
It might be nice to be given the option for those rare times you want the dalvik and files cache.
It might be nice to be given the option for those rare times you want the dalvik and files cache.
pbailey212
Well-known member
- Mar 20, 2011
- 765
- 219
- 0
Also when backups get bad md5 sums its usually in the cache partition that it occurs. I had the issue a couple times but I haven't had any problems since I started wiping caches before backup
Sent from my LG-VM670 using Tapatalk
Sent from my LG-VM670 using Tapatalk
There is no reason not to wipe it first.
Dalvik will rebuild itself if there is an issue and cache does so as you work.
Dalvik will rebuild itself if there is an issue and cache does so as you work.
Recovery issue: I have had no problems with the new BACKside, but still would like ICS. I have been reading that the AOKP version has working wireless (I am wireless only) so I downloaded it and proceeded to go through the complete wipe and flash. Wiping was no problem, but I was unable to flash the ROM. I am going to try going back to the stock one used for the radio and see if that works.
[edit] bad md5 sum, my bad. Sorry 'bout that...
[edit] bad md5 sum, my bad. Sorry 'bout that...
Last edited:
quattrimus want to see thunderc in the default.prop. this recovery shows thunderc_VM670. working on fixing this in mine (its a simle fix, but my phone doesnt like it when i unpack then repack stuff)
That shouldn't be too difficult to fix when building from source. I'll try to have it fixed in V3.3 due out mon-tues.
I'm working on the automatic backup/restore functions, and realized I'm changing things ROM Manager probably uses. I believe I've made the appropriate changes so that it will fail gracefully with CWM-Green, but I'm not 100%.
Sorry, I should have mentioned this before, I've edited the OP with the following:[WARN]
Sorry, I should have mentioned this before, I've edited the OP with the following:[WARN]
Do Not Use ROM Manager With CWM-Green!!!
ROM Manager depends on a particular set of functions in CWM
CWM-Green may have changed some if not all of these functions!
This Could Brick Your Phone!
[/WARN]ROM Manager depends on a particular set of functions in CWM
CWM-Green may have changed some if not all of these functions!
This Could Brick Your Phone!
Similar threads
Facebook
Twitter
Instagram