For whatever reason I couldn't get the ota to install on my wife's rooted/unlocked M. It failed at verifying apos, though I had used matts utility to go back to fresh stock, rooted and used stock recovery to install she hasn't or even knows how to mess with apps or bloat like that. If I'm not mistaken it's something with the maps app, so I left her on the 9.8.1q-66 and just flashed baseband. Froze updater as well.
I however got the ota to install on my phone, can I restore my twrp backup, then wipe data and factory reset on her phone to get her on a working update path?
Sorry if that is a stupid question, seems logical.
CamoCustom said:
For whatever reason I couldn't get the ota to install on my wife's rooted/unlocked M. It failed at verifying apos, though I had used matts utility to go back to fresh stock, rooted and used stock recovery to install she hasn't or even knows how to mess with apps or bloat like that. If I'm not mistaken it's something with the maps app, so I left her on the 9.8.1q-66 and just flashed baseband. Froze updater as well.
I however got the ota to install on my phone, can I restore my twrp backup, then wipe data and factory reset on her phone to get her on a working update path?
Sorry if that is a stupid question, seems logical.
Click to expand...
Click to collapse
Yes.
Related
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
wiredwrx said:
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
Click to expand...
Click to collapse
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
RMarkwald said:
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
Click to expand...
Click to collapse
Thanks. I will look into that. Any thoughts on the update?
wiredwrx said:
Thanks. I will look into that. Any thoughts on the update?
Click to expand...
Click to collapse
You'd have to get stock Android recovery on there somehow, but if you're doing the official update and you removed any /system/app apps with Titanium Backup or anything, it'll also fail. If you flashed a custom kernel, it'll fail as well. Official updates run system checks to see that the stock files are all there and the correct versions.
You could backup everything you want to save on internal sd card (pictures/music etc), and flash the official factory Google images via fastboot. Or flash custom recovery and flash a 4.2.2 ROM. Either way, you'll have to wipe everything so you'll loose apps and app data, which you'll have to re-install again.
wiredwrx said:
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
Click to expand...
Click to collapse
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
bftb0 said:
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
Click to expand...
Click to collapse
Thanks for the detailed breakdown. I may just update with your instructions. Are you aware of a way to suppress the nag screen.
Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.
I have a rooted 1575 with Marshmallow; however, my camera is not shooting video. Except for the video not working, the phone works fine. I may have a hardware issue, but will probably need to verify that there's nothing about my modified set up that is causing this. I've cleared caches and rebooted, also tried Google stock camera with same results.
Root wise, I went through some maneuvers to initially get root with Marshmallow, which involved flashing a modified version of boot.img (discussed here: https://reformedmusings.wordpress.c...ure-2015-to-android-6-0-marshmallow-on-linux/ and here http://forum.xda-developers.com/showpost.php?p=64107089&postcount=290).
Is it just a question of replacing boot.img with the stock Marshmallow boot.img, If so, where should I get that?
I have a good TWRP backup on my desktop from today...
I would just do a full wipe in twrp.
lafester said:
I would just do a full wipe in twrp.
Click to expand...
Click to collapse
As "Swipe to Factory Reset" under Wipe? Forgive my ignorance, but does this "unroot" the device? and given that I have inbuilt Google auto backup, will my apps get restored?
I have a Sprint Note 3 and I am having the dreaded "Unfortunately, the process android.process.media has stopped" problem.
I tried every single fix I found online. Even the stupid ones I knew wouldn't work. I finally caved and did a full wipe. Low and behold, on the very first setup screen the error message immediately popped up.
I am stock (whatever the latest version is) and rooted.
If factory reset doesn't work I don't know what else would work. That's usually the last recourse. Any suggestions? HELP!
Do I maybe need to re-flash the stock rom? If so, can someone please provide a link?
Suggest you ask in the SPRINT forum .
uscpsycho said:
I have a Sprint Note 3 and I am having the dreaded "Unfortunately, the process android.process.media has stopped" problem.
I tried every single fix I found online. Even the stupid ones I new wouldn't work. I finally caved and did a full wipe. Low and behold, on the very first setup screen the error message immediately popped up.
I am stock (whatever the latest version is) and rooted.
If factory reset doesn't work I don't know what else would work. That's usually the last recourse. Any suggestions? HELP!
Do I maybe need to re-flash the stock rom? If so, can someone please provide a link?
Click to expand...
Click to collapse
Yes, you need to re-flash stock ROM (search in updato). I'd also suggest you do a full DATA wipe with TWRP before and THEN flash stock ROM. Make sure you backup everything before anything.
ShaDisNX255 said:
Yes, you need to re-flash stock ROM (search in updato). I'd also suggest you do a full DATA wipe with TWRP before and THEN flash stock ROM. Make sure you backup everything before anything.
Click to expand...
Click to collapse
Holy crap. I downloaded a stock ROM from Updato and my phone isn't bricked but I'm worse off now.
Somehow, nothing at all changed on my phone after I flashed the ROM. All my apps, data, screens, everything is still there. However, I lost root and I lost my custom recovery and I still have the problem I had before.
Two questions:
1) I still have a Nandroid backup of my rooted phone from before I flashed the stock ROM. Can I restore this Nandroid backup with the stock recovery?
2) If not I will install TWRP again. At that point can I just restore the rooted Nandroid and gain root again or do I have to root first and then restore the Nandroid?
What a mess. Why did everything stay the same after flashing the stock ROM? Is updato a legit website?
uscpsycho said:
Holy crap. I downloaded a stock ROM from Updato and my phone isn't bricked but I'm worse off now.
Somehow, nothing at all changed on my phone after I flashed the ROM. All my apps, data, screens, everything is still there. However, I lost root and I lost my custom recovery and I still have the problem I had before.
Two questions:
1) I still have a Nandroid backup of my rooted phone from before I flashed the stock ROM. Can I restore this Nandroid backup with the stock recovery?
2) If not I will install TWRP again. At that point can I just restore the rooted Nandroid and gain root again or do I have to root first and then restore the Nandroid?
What a mess. Why did everything stay the same after flashing the stock ROM? Is updato a legit website?
Click to expand...
Click to collapse
It's a legit website but you need to wipe everything before flashing stock ROM. The order would have been: Boot into TWRP -> Wipe/Factory reset -> Format Data -> Reboot to download mode -> Flash stock
Yes, you will have to re-install TWRP again and restore your nandroid backup.
Hey,
I didn't updated my phone for quite some time and today I had some free time and I decided to update it to the latest version. I performed the first OTA update, and the process wen't really smooth. The phone booted after a few minutes, however it told me there's another system updated so I installed it as well.
However, after installing the second OTA update, my phone never booted again. it stucks in bootloop for a few minutes and then just boots to recovery.
I don't really know what to do, and although most of my data is backed up I really want to avoid wiping all the data.
The phone was never rooted and has stock recovery. How can I make it boot without wiping all the data? I did try to wipe cache already and it didn't help.
I see that there is a method called 'adb sideload' but I want to be sure it doesn't wipe data and to know which zip I should give it... Thanks!