rooted but running stock image... how to upgrade? - Moto G4 Plus Questions & Answers

A while back i rooted my 4g plus and ran CyanogenMod for a while... it had a few small issues and people were raving how stable the stock image was so i downloaded and applied a stock image and have been running since.
Recently started getting the update notice but when i try to apply it the reboot just dumps me into TWRP, if i reboot from TWRP my phone boots back up and tells me the update has failed.
I have been googling around like crazy but am finding alot of different answers:
The download of the image is stored in cache and you just need to point TWRP to that temp image and it will upgrade
Where is the cached image stored on the phone?
Will this keep my phone rooted?
Download the latest release and apply it via TWRP like i did originally.
Will this update or wipe my phone like new?
Will the phone stay rooted?
Thanks!

I may have misinterpreted what you wrote - however, if you're referring to the stock (i.e. images from Motorola), you cannot update via OTA whilst you have TWRP recovery; the OTA updates only will flash via a stock recovery. Furthermore, the OTA update will fail if you're rooted or have other modifications to your system/recovery. Having an unlocked bootloader does not appear to matter.
In order to apply an OTA update, you'll have to un-root and flash a stock recovery onto your system, or flash a stock image (such as this Nougat fastboot image: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) which will remove root and TWRP on your system. Depending on what options you choose with the fastboot ROM, you can elect not to wipe your internal storage (but still a wipe of your cache and Dalvik at least is advised), check the linked topic for more information.
Then you should be able to update. Failing that, perhaps someone will be able to provide a TWRP backup of their system with the latest updates included, but from what I've seen, you may have to clear cache and data to boot.
If you wish to find the OTA update, it's not in your cache, it's actually hiding in '/data/data/com.motorola.ccc.ota/app_download'. You'll need root access to see the OTA file though.

Related

[Q] Cannot install OTA 5.1 on 5.0.2 rooted

I have 5.0.2 (LRX22G) rooted + TWRP.
I flashed the original stock recovery from LRX22G, and still I cannot sideload OTA, I'm getting error "/system/bin/app_process32 has unexpected contents".
Is this because I'm rooted?
Is there another way to upgrade to 5.1 ? Can I just flash new bootloader, system, boot and recovery images (from the factory image LMY47D) and erase cache?
(Obviously I want to preserve my apps and data while upgrading...)
Found answer here:
http://www.theandroidsoul.com/fix-e...img-android-5-0-factory-images-nexus-devices/
The only missing (last) step for my setup:
flash latest TWRP, reboot into it, flash latest SuperSU, erase Dalvik and cache, reboot.
You can flash every partition for itself. No need to wipe. But I haven't done this so far so I can't tell if it will work.
But here is a guide.
http://highonandroid.com/android-sm...-android-5-1-manually-on-nexus-4-5-6-9-and-10
I always just manually flash all the images from the new factory image EXCEPT USERDATA. Never had any issues, and all my data stays the same as it was before flashing/updating.
And HOW exactly do you DO that (on a Zenfone 2e) because I cant find any Definitive Info on the phone variant. It seems that ASUS uses the same tools for the 2e as they do for the 2 (16 Gig) but they never say FOR Sure. I have a 2e and I'd REALLY like to be able to put the newer rom on it. I keep getting the same ...app_process32 Status 7 error.
So How would I go about GETTING the Factory Rom from ASUS ,
and 2 Where can I find the "Tools" i keep hearing about
Also, Im not a noob, I've used Fastboot and ADB before, I'm just not quite a "Pro"
hippopo said:
I have 5.0.2 (LRX22G) rooted + TWRP.
I flashed the original stock recovery from LRX22G, and still I cannot sideload OTA, I'm getting error "/system/bin/app_process32 has unexpected contents".
Is this because I'm rooted?
Is there another way to upgrade to 5.1 ? Can I just flash new bootloader, system, boot and recovery images (from the factory image LMY47D) and erase cache?
(Obviously I want to preserve my apps and data while upgrading...)
Click to expand...
Click to collapse
Hello,
you can flash yourself the content of the factory image.
Unzip the content , and then the newly extracted archive you will find.
you can do such tings ...
Code:
fastboot flash <partition> <path_to_img_file>
replace <partition> with system or bootloader
<path_to_img_file> should be the absolute path to your img fileSo if i were you I would simply flash the system partition and erase cache

Stuck on patching system image unconditionally when flashing oxygen

Hello
I had a problem with my phone earlier today where it would reboot one or two minutes before it started, so I install twrp recovery and tried installing Ota 009 which I found here on xda, how ever now I'm stuck when I'm trying to install it?
Thanks in advance
Did you flash the whole ROM or only the OTA file?
For the latest version (2.1.2), as there is no full zip, only the incremental file, you need to flash the FULL 2.1.1 and then directly the 2.1.2 in TWRP.
You can flash only the OTA file alone if your system is stock and untouched (no root / TWRP).
In your case you need to flash the whole ROM then the OTA.
Check this thread -> http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I'm trying to flash Oxygen OS 2.1.1 the full rom but it just get stuck in TWRP nothing happens. Im using the rom from that thread you just liinked
Try wiping dalvik cache, cache, system, and data. (NOT INTERNAL STORAGE) then flash again.

Cannot update to 4.5.14

Hi,
I have a rooted OP5 with 4.5.13.
I tried to install the flashable zip (from here) via TWRP without wipe, but ended up in a bootloop.
I've restored to the nandroid backup, wiped data, and tried again. This time the OP5 managed to boot only to recovery.
I've verified the md5 of the file I've used.
Do you know why this is happening? Do you know how I can upgrade to 4.5.14?
Thanks.
Did you download the full ROM or just the update?
I tried both. I didn't succeeded to install the update (as it is not intended for rooted devices).
The full rom is what caused the bootloop.
If you are doing a dirty flash you wipe cache and system. If you are doing a clean flash you wipe cache, system and data. It doesn't sound like you wiped the correct partitions when doing your flash. You also need to flash Magisk or SU after the ROM flash and before booting up or you will lose TWRP and root. If your phone is decrypted for some reason you also need to flash a no verify zip or your phone will boot loop because OOS is made for encrypted phones.

Should I flash twrp?

I'm currently running magisk, I've been trying to do everything systemlessly but it's getting frustrating, failed boots, bugs, limitations... I want to stick with systemless so I can count on my warranty which I can get back with two commands. Now, my question is, how hard and risky is to get stock recovery and lock back the bootloader once twrp is installed. Another thing I'm concerned about is if OTA update kicks in, I uninstall magisk and update it and it fails, I'm stuck, can't get any data or backup. Twrp would help a ton and I'm pretty sure I can just flash the new OTA image from twrp. But how hard and risky is restoring factory phone image (system+bootloader+recovery) once lord twrp is installed?
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Daydreamaway said:
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Click to expand...
Click to collapse
That's great, and fastboot is always available no matter how corrupt the system is, right? What do you recommend for a full backup and what about allowing system modifications when twrp boots?

OTA Installation fails after restoring STOCK TWRP backup

Hi. I have a Moto G Plus US variant XT1644. I did a clean backup (stock ROM) when I was on NPJS25.93-14.7-3 (boot, system and data).
After that I installed many custom ROMs, all of which caused my phone to drain battery and heat up so I decided to go back to stock by restoring my backup.
After I restored my backup I instantly received a new update via OTA (build NPJS25.93-14.7-5). So in order to install it "officially" I grabbed a stock recovery.img (in this forum) and flashed it before tapping on INSTALL so that everything keeps unmodified before applying the update. But when it reboots and tries to install the update I get a message "Error!".
Please any help would be much appreciated.
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
echo92 said:
1)When you took the TWRP backup, do you remember if swipe to allow modifications was allowed in TWRP? If so, then the system partition in your backup might be flagged as read write, which would prevent the OTA from flashing.
2)Is the recovery from the same build as NPJ25.93-14.7-3?
3)Do you have a custom logo.bin to hide the bootloader warning?
Click to expand...
Click to collapse
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Danny1976 said:
I think he can flash the 14.7 US Retail without deleting the Data Partition to get back to Stock and then do the OTA updates.
He can check this thread out:
https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page15
Click to expand...
Click to collapse
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
hernaner28 said:
1) I definitely took the backup after allowing modifications so this is probably why.
2) yes
3) no
Yeah, I´ve been following that thread. I will try to do that and try to make clean backups (without allowing modifications). BTW how should I make a backup of the recovery and bootloader with TWRP ? Thanks.
Click to expand...
Click to collapse
You don't have to flash TWRP, just boot to it. Use the command fastboot boot twrp-3.1.1.0-athene.img and keep it read only. Make a backup of the system and boot. Root with ElementalX and Magisk. Then use Flashify to backup recovery, if you have not flashed TWRP.

Categories

Resources