-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Update to 4.2.2 without wiping
- Thread starter kushelduv
- Start date
-
- Tags
- galaxy nexus
Booting into recovery shows CWM v6.0.1.2, so it looks like it is installed.
Should have specified though, that I'm not trying to install it from in CWM, I just clicked on the "Install Now" window that popped up showing the update is available.
And when it rebooted, it gave a message about the update being unsigned or something (don't remember the wording) and asked if I wanted to continue.
When I did, that's when the dead android came up.
I cleared the framework data and redownload the update to try again, but same effect.
Is there a way to apply it from in CWM?
Should have specified though, that I'm not trying to install it from in CWM, I just clicked on the "Install Now" window that popped up showing the update is available.
And when it rebooted, it gave a message about the update being unsigned or something (don't remember the wording) and asked if I wanted to continue.
When I did, that's when the dead android came up.
I cleared the framework data and redownload the update to try again, but same effect.
Is there a way to apply it from in CWM?
jhawkkw
Chinchillin'
Yes, use this and choose the manual zip file that you downloaded.
jhawkkw
Chinchillin'
Alright, at this point because of the error, there's 3 options that we can do. 2 are a little more difficult but will save your data. The third one is to flash the whole factory image through wugs and thus lose your data.
The first option is move the zip file to a computer, edit the script file to remove those assert checks, move it back + rezip and flash that result.
The second option is to partially flash the factory image through bootloader manually. Basically we would manually update the bootloader & radios & kernel, flash the system through fastboot, then boot into cwm and clear out the dalvik cache. Then after first boot we would re-root.
The third option is a full factory image flash through wugs. This would be the easiest and potentially quickest, but will result in loss of data.
The choice is yours.
The first option is move the zip file to a computer, edit the script file to remove those assert checks, move it back + rezip and flash that result.
The second option is to partially flash the factory image through bootloader manually. Basically we would manually update the bootloader & radios & kernel, flash the system through fastboot, then boot into cwm and clear out the dalvik cache. Then after first boot we would re-root.
The third option is a full factory image flash through wugs. This would be the easiest and potentially quickest, but will result in loss of data.
The choice is yours.
Any potential problems with removing the assert checks?
If it's safer to just do a wipe/full flash, I'll go ahead and do that.
I don't care about the files on it, have those backed up.
Just have a couple games I've done in app purchases on, and I don't know if Titanium will properly restore the full game data.
But if I have to lose them to avoid screwing my phone, then so be it.
If it's safer to just do a wipe/full flash, I'll go ahead and do that.
I don't care about the files on it, have those backed up.
Just have a couple games I've done in app purchases on, and I don't know if Titanium will properly restore the full game data.
But if I have to lose them to avoid screwing my phone, then so be it.
jhawkkw
Chinchillin'
CWM does seem to cause issues if it's installed on the device. However updating while rooted if the stock recovery is installed doesn't seem to be a problem for most, other than losing root in the process.