Unexpected Android system update, booted into TWRP - X Play Q&A, Help & Troubleshooting

Hello,
Today I received a Motorola Android system update. I did not expect this to happen, because my device has an unlocked bootloader and is rooted, and I have TWRP installed. I never received a system update before in the 1,5 years that I have it.
After the update was downloaded, it started installing by verifying the update and then initiated a reboot. The reboot however ended up in TWRP.
What should I do now? Just reboot? Will that cancel the update or break anything?
Is there any way that I can manually complete the installation of the update?

if you are rooted with twrp installed, just copy update file from /cache to your internal storage. Then unroot your device (discard any changes in /system partition via flashing stock system.img), flash stock recovery and apply update from recovery.
I suppose, file you have being downloaded is just security update.
Please pm me, if this file large than 500MB ;

The update file is named Blur_Version.24.61.52.lux_reteu.reteu.en.EU.zip. It is 69,5 MB (69514015 bytes).
This is the first time I receive a system update (I unlocked the bootloader and rooted my phone right at the start). Strange thing is that the contents of the file all have a timestamp of 14 februari 2014 17:43. I can't believe I received a three year old update. The Moto X Play did not even exist three years ago.

I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.

gewe said:
I installed the update. It was 24.201.5.en.EU, containing the security patches of october 2016. So your assumption was right. Still strange that this is the first update I received in 1,5 year.
Click to expand...
Click to collapse
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks

gamoraw said:
Hello there, could you let me know how you installed the update (step-by-step if possible), I am having the same problem while updating as my moto x play tries to reboot during the install and I get the TWRP interface. Thanks
Click to expand...
Click to collapse
I followed the instructions I found here, with the following changes:
skip flashing bootloader.img and logo.bin (unlocked bootloader);
skip flashing recovery.img (you want to keep TWRP);
skip erase userdata (keep your data).
Some people advise against not erasing useradata, but I never had a problem skipping that step.

Related

Moto G 4G/LTE 4.4.4 OTA - 21.1.46.en.EU (XT1039)

Motorola 4G 4.4.4 Kitkat for EUROPE/AUSTRALIA aka XT1039
Updates from Android 4.4.3 (21.1.31.peregrine_reteu.reteuall.en.EU) to Android 4.4.4 (21.1.46.peregrine_reteu.reteuall.en.EU)
Update brings:
Android 4.4.4 Kitkat
SD Card Fixes
Requirements:
21.1.31.en.EU peregrine (Moto G 4G) --> WILL NOT WORK IF en.US, en.BR, OR en.UK
Locked bootloader ONLY:
1. You should get the OTA notification. Otherwise go to Settings --> About Phone --> System Updates to Download & Install.
2. If it says latest (and you are on 4.4.3), Download the OTA here and place in root internal SD directory.
3. Repeat Step 1
4. Done
Unlocked bootloader + Root/Recovery ONLY
1. Follow this thread and flash the latest 4.4.4
OR MANUALLY
1. You should get the OTA notification. Otherwise go to Settings --> About Phone --> System Updates to Download & Install. If you have recovery error (stock recovery) or nothing happens in recovery and it keeps restarting (custom recovery) then go to Step 2.
2. You may have altered your system partition (e.g. modified hosts file, uninstalled system apps). If it's reversible (try disabling Xposed, restoring hosts file) you can try and undo it and attempt to install again. If this does not work, you will need restore /system partition to stock by flashing just the system.img chunks through fastboot (from stock firmware).
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
NOTE: If you feel uncomfortable to do this and are happy to stay with 4.4.3, then fastboot erase cache to stop phone restarting and trying to update.
3. Once flash is complete, reboot and go back to Step 1 to reinstall OTA.
4. Still no luck?? Download the OTA here and place in root internal SD directory. If you have stock recovery go to Settings --> About Phone --> System Updates to Download & Install. Otherwise go to CWM/TWRP and Install the OTA.
Well, first of all, my sd card worked fine on 4.4.3, I had no single problem with it...
Wenn I updated to 4.4.4 and rebooted the phone, the first messagge I saw was: sd card unexpectedly removed, I really was in shock...
Motorola, what the hell did you do??????
So now I think I'm gonna downgrade te 4.4.3 again...
jkoetsier said:
Well, first of all, my sd card worked fine on 4.4.3, I had no single problem with it...
Wenn I updated to 4.4.4 and rebooted the phone, the first messagge I saw was: sd card unexpectedly removed, I really was in shock...
Motorola, what the hell did you do??????
So now I think I'm gonna downgrade te 4.4.3 again...
Click to expand...
Click to collapse
Can't say I've had any problem with Android 4.4.3 or 4.4.4 with SD card. So it hasn't affected me that way. Did you try reinserting and rebooting?
Ok, so I tried this, and when trying to flash Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip using cwm-touch I get this:
Code:
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/peregrine_reteu/peregrine:4.4.3/KXB21.14-L1.31/27:user/release-keys or motorola/peregrine_reteu/peregrine:4.4.4/KXB21.14-L1.46/42:user/release-keys; this device has .
E:Error in /data/media/0/Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip
(Status 7)
Installation aborted
I looked the compilation number in about phone, and it's this: KXB21.14-L1.31
And the system version is: 21.1.31.peregrine_retgb.retgball.en.GB retGB
The only system modification I had done was install Xposed, and some modules. But I disabled the modules and uninstalled it before trying this.
Some help would be great =)
Edit: Tried with TWRP and I get a similar error.
Got it installed thanks to your guide.
Had to root again after the update, and reinstall busybox.
Thanks again !
Seems that there are even different versions of soft for Europe, I have vs 21.1.31.pregrine_retgb.retgball.en.GB.retgb (XT1039) and my phone does not provide any update yet. Anyone here with this system version?
gartzen said:
Ok, so I tried this, and when trying to flash Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip using cwm-touch I get this:
Code:
Finding update package...
Opening update package...
Installing update...
Package expects build fingerprint of motorola/peregrine_reteu/peregrine:4.4.3/KXB21.14-L1.31/27:user/release-keys or motorola/peregrine_reteu/peregrine:4.4.4/KXB21.14-L1.46/42:user/release-keys; this device has .
E:Error in /data/media/0/Blur_Version.21.1.31.peregrine_reteu.reteuall.en.EU.zip
(Status 7)
Installation aborted
I looked the compilation number in about phone, and it's this: KXB21.14-L1.31
And the system version is: 21.1.31.peregrine_retgb.retgball.en.GB retGB
The only system modification I had done was install Xposed, and some modules. But I disabled the modules and uninstalled it before trying this.
Some help would be great =)
Edit: Tried with TWRP and I get a similar error.
Click to expand...
Click to collapse
Appears to be a mismatch. I would not advise to install this OTA if you do not have en.EU even though you have the same model number....
I believe there are many variations sold around the world including US (XT1045), BRAZIL (XT1040), EUROPE (XT1039), and now UK (XT1039). Here in Australia we use en.EU because of the same LTE bands.
I guess I'll have to wait my OTA to tell me there's an update, or a CM version for our phone!
Thanks anyway
Work in XT1045?
Luckily I fixed the sd card issue by formatting it...
Incredible, all 3g 444 versions are out, the 444 eu lte is out, the only missing yet is the 444 eu 3g
It works, sadley I had to restore the system partition. Afterwards most systemfiles fc's. Gladly I had my downloaded OTA backed-up. Afterwards I could only flash the OTA with a custom recovery.
Now everything works again and is updated.
reef2009 said:
It works, sadley I had to restore the system partition. Afterwards most systemfiles fc's. Gladly I had my downloaded OTA backed-up. Afterwards I could only flash the OTA with a custom recovery.
Now everything works again and is updated.
Click to expand...
Click to collapse
Recommend to clear cache and dalvik cache after restoring system partition. The OTA download is provided in the OP if required. Glad it worked out.
vpnair said:
Recommend to clear cache and dalvik cache after restoring system partition. The OTA download is provided in the OP if required. Glad it worked out.
Click to expand...
Click to collapse
I did clear cache and dalvic, So I don't know what's the problem.
Besides that 4.4.4 fixes all fc's.
Since last year I don't have the time to figure out what's wrong but it works and that's the thing
AlbertoJOG said:
Work in XT1045?
Click to expand...
Click to collapse
I don't think it does. I have one too but we have the US version and they have the EU. Guess we just gotta wait.

[OTA] Moto G 2014 XT1064 v22.21.25.en.us (5.0.1)

I just got the new OTA for Lolipop 5.0.1. I used ADB to pull the URL for the download and downloaded the attached ZIP using my browser. The URL pulled from ADB was an extremely long randomized string of characters that expired the moment my device was done updating. It seems the link is only active during the update process, so the only way to leave the link active longer is to battery pull or something in the middle of the update. I love you guys... but not that much
Keep in mind that this OTA was offered to me on 22.21.16, so I am assuming that you probably need to be on that update before you can use this OTA.
Let me know if you guys have any questions or run into any issues!
I'm rooted and running TWRP on my XT1064 with 22.21.16. Is there a way to just fastboot flash this update? I don't mind losing root. Thanks!
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Edit: I went ahead and flashed stock recovery and rebooted. After boot looping several times it rebooted into the system and gave me the message "Software update unsuccessful. There was a problem ....blah, blah, blah." But I still show an update available when I check.
I suspect it is because I am unlocked and rooted, even though I have stock recovery installed. Any thoughts on this guys? I am going to hold fast until I know for sure.
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
DoubleIk said:
I may sound like a noob, but just to be sure..
Name of update says ".en.us".
Is it ok to use it for a french moto G 2d generation?
French will be available?
Thanks!!
Click to expand...
Click to collapse
Not sure if it makes a difference or not. I just put what the build was listed as when I got the update notification.
I put that there in case that was why some people couldn't update from 22.21.6 to 22.21.16
shishir95 said:
The update failed because you were rooted. You need a 100% stock /system since updates after 5.0 check the integrity of the filesystem before updating.
Click to expand...
Click to collapse
Nice theory, but I am now totally restored back to stock with stock recovery and unrooted. Still no luck with the update. Same thing happens.
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
thisisjason said:
I'm still stuck on 22.11.6, so I'm assuming I can't install this update until I'm on 22.21.16?
Click to expand...
Click to collapse
From what I've seen, that is correct.
Any news XT1068 android 5.0.1 #India?
Moto G 2014 5.0.1
Hello good day friends will have some manual to perform the installation ?? and try it for apply update from ADB and I mark error in sideload package , installation aborted
How do I can install this update?

Stop !!! Do not upgrade to lollipop via twrp !!!

Update : Oct 24, 2015 It looks like the bricking scare is over, and there is an updated guide on how to upgrade to the latest Lollipop without bricking :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
PUBLIC SERVICE ANNOUNCEMENT :
There are now several reports of super hard bricks (not even Amazon logo shows up) when people attempted to load 5.2.2 version via TWRP.
My best guess is that it has something to do with the 5.x update from Amazon that people request before downgrading to 4.5.3. If Amazon is providing a newer 5.x. update, it can be blocking the older 5.2.2 from working after the downgrade-upgrade procedure. When it bricked before, it would at least show "Amazon" logo, but now even the logo is gone.
One would have to capture this current 5.x update, and see what's in it. It's probably updating another partition out of those that were previously untouched :
http://forum.xda-developers.com/fire...idden-t3122246
All the downgrade-upgrade guides are on hold for now ... You are still safe to exist in the 4.5.x space (with root).
bibikalka said:
One would have to capture this current 5.x update, and see what's in it.
Click to expand...
Click to collapse
I assume I can capture file by reversing rename of DeviceSoftwareOTA.apk but leaving OTA updating blocked. Is that the method?
EDIT: Well, just did rename. No download yet. I've got otaverifier blocked. If nothing soon, I'll enable that and block dcp.
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
All that downloaded for me were apk update files, no .data, but device>updates shows:
10.0.42-D-20150925-NA-4 is ready to install
I ran logcat during download and a couple of manual installs (pressing Install button, but I do have updates blocked). I didn't see anything obviously related to update in the logcats, but not sure what to look for. Since I didn't get the .data, will I find anything helpful in logcat? What should I look for? thx
p.s., Or must I unblock updating to capture?
siegesoldier said:
This update was strange and left a very small .data file in cache after saying a download was complete, ready to upgrade. Could not locate a bin file. I will/would try capturing a link via adb logcat.
could be a small update that just preps us to move back to the normal releases.
Just educated guesses.
Click to expand...
Click to collapse
Yep, this is weird. I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Another poster indicated that the tablet rebooted about 3 times, and then he got new icons and Amazon launcher :
http://forum.xda-developers.com/showpost.php?p=63116048&postcount=141
bibikalka said:
I wonder if one should flash 4.5.3 bootloaders with TWRP in Lollipop first as per this post http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2 , and let it try to upgrade. This way whatever files it downloads, they will be sitting in /cache. But nothing will be run as it is a non-Amazon recovery.
Click to expand...
Click to collapse
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
DoLooper said:
I'm more than willing to try to capture this if one of you can tell me how.
I don't quite follow the above. I'm running rooted 5.2.2. So I'd flash bootloaders and TWRP per guide, install OS 4.5.5, boot to OS and try to upgrade? Is this any different from someone already on 4.5.5 trying to upgrade? thx
Click to expand...
Click to collapse
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
bibikalka said:
Not this complicated. I think you could flash 4.5.3 bootloaders + TWRP under 5.2.2, enable OTA updates, and continue working. When it decides to self-reboot (after the update is copied to /cache), it won't find stock 5.2 recovery. Instead, it'll hang (4.5.3 bootloaders cannot boot 5.2.2). At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
OK, I'll try this later or tomorrow. Still wonder though, couldn't you--anyone on 4.5.5--leave OTA package blocked but rename OTAsoftware extension back to apk, allowing the update to download but not install?
)':
Hello, I am french sorry for my english
My kindle fire is bricked
how to repair !! :crying::crying:
help me please :/
bibikalka said:
. . . At this point you can manually reboot into TWRP, and see what's in /cache. Then you just reapply 5.2.0 bootloaders + 5.2.0 recovery, and boot back into 5.2.2 (and do disable OTA here !!!) Hopefully it does not write into recovery partition before auto-rebooting, so that TWRP survives intact.
Click to expand...
Click to collapse
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks! (Edit: NVM--I see your explanation above.)
EDIT @bibikalka, @everyone Thought the update was out for my region, but guess not: With DeviceSoftareOTA.apk named as originally and otaverifier enabled, Device>Updates just returns "no updates." Disabled otaverifier again and will wait on this.
I believe the update will download with DeviceSoftwareOTA.apk properly named--and hope it won't update with otaverifier disabled. So maybe I can get it. Anyway, I'll check for it over next few days, but maybe someone else will try this method first. (I am west-coast US and it seems always last to get updates.)
DoLooper said:
@bibikalka OK, ready to do this and (more or less) prepared to get replacement Fire . Just one question: Why do you think there will be anything in cache after the update and reboot attempt? i.e., wouldn't deleting it be part of the update process? Thanks!
Click to expand...
Click to collapse
I think it will prepare to update by staging the required files in /cache, but then it'll try to reboot to apply those files (usually updates are applied in recovery ...). So when reboot fails (as it should with TWRP & 4.5.3 bootloaders which don't boot Lollipop), you intercept the stuff in /cache and see what it has.
Added: If this works, do wipe /cache before leaving TWRP (when you restore 5.2 bootloaders). This way it won't pick up the scripts and run them ...
See edit here. Forgot that I'm always last to get an upgrade. Hope someone who might get it sooner will use bibkalka's method so we can get this show back on the road.
After downloading the 5.0.1 update once I have been unable to get it again. My build number has not updated so its possible they pulled it. Root etc still works so it doesn't look like it applied.
Hello, just wanted to say that I can testify to the fact that after updating to 5.2.2, then downgrading and going into TWRP, flashing all the zips, and then wiping cache before rebooting..... gets you a BRICK!! I've stupidly done it.... to my replacement from Amazon! Hopefully sometime in the future someone can get me out of this one....
hello there recently my rooted fire os 5 with xposed playstore just updated to 5.0.1 by it self and i swear i did have com.amazonotaverifier blocked its weird because it updated when i left my fire hd 6 on charge
it just updated itself to fire os 5.0.1 il stay on that fire os because people are saying you get bricked if you do the whole procedure like downgrade back to 4.5.3 and root and get custom recovery and flash all the zips = brick
2nd try to get 5.0.1 update
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
------------------------
EDIT: NVM below! I'm getting # prompt because I recently set "adbd insecure" app to start at boot <doh> .
Second, I decided to start over and see if there was a different update waiting. So:
1. Went to twrp and flashed 5.2.0_stock_recovery_uboot.zip (for 5.0 stock recovery and bootloaders, i hope), wiped cache, and booted to OS.
2. Got l o o o n g startup. When OS finally loaded, "adb shell" hung CMD. I had to run TASKKILL /F /IM adb* >nul 2>&1 before adb shell was recognized. And when it was, it consistently returned # prompt: ([email protected]:/ #)
I'm definitely rooted, all google works, version still shows 5.0.0, build date July 20, but even after rebooting both tablet and computer, "adb shell" still always returns # prompt.
Can anyone tell me what's going on here? (Sorry this is tldr; hope a few of you slog through.) Thanks.
EDIT: it's late, maybe I'm nuts, but seems "adb shell" should return $ prompt, then "su" returns #.
DoLooper said:
I didn't capture the update, but maybe learned something about OTA. Two things I hope someone can explain.
First, I've had extension of DeviceSoftwareOTA.apk renamed back to (plain) .apk since last attempt to capture update. Today:
1. "Check for updates" returned: 10.0.43.-D-20151007-NA-5 is ready to install
(last week there was one named: 10.0.42-D-20150925-NA-4)
2. I dd'd the 4.5.3 bootloaders and twrp (with otaverifier blocked)
3. Unblocked otaverifier, but the only thing that downloaded to /cache was "amazonmp3_10004310.apk" (update to mp3 player, i guess).
(last week they were apks for map and photo apps)
4. Hit "check for updates" again, but now it said "none" and /cache was empty.
(same thing last week)
Does anyone know about updates named like "10.0.43.-D-20151007-NA-5?" I've only seen them since I "corrected" the deviceSoftwareOTA.apk extension, and only apk files get downloaded. A couple logcats I got, however, have many more update entries than I've seen before, but I don't understand logcats very well. If someone who knows logcats could have a look, I'd appreciate it. Just tell me where to post. I think it would help us to know if these updates do more than update the accompanying apks.
.
Click to expand...
Click to collapse
These updates appear to be just individual apps, nothing to do with the system. You can google the version numbers, and it'll find that stuff.
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
bibikalka said:
The only hope is to checksum all partitions, and find the one that was updated in the latest version 5, but otherwise does not change in earlier versions. One could right a script for that. Then we could overwrite it.
But I suspect the new update may have written into one of the partitions that have other stuff, so the checksum identification won't help.
Click to expand...
Click to collapse
Would that mean 5.0.1 would not be rootable?
Hello, I am curious, would it be possible to use "fastboot boot recovery.img" instead of actually flashing it in order to get root in the new 5.2.2 (build date sep 23)? It seems this would solve the hard brick problem with flashing twrp.
I'm on a never-rooted 2014 HD6 with gapps & OS 5.2.2. Very interested in rooting this tablet.
hi,
my Eng is not good, i don't understand the title
Stop !!! Do not upgrade to lollipop via twrp !!!
on today i'm receive Fire HD 7 from my phone provider. This is free.
i was rooted it with kingroot. It was succesfull. But i want setup it with android with vietnames because my boy are 10 age.
it run fire os 4.5.3 now.
can i upgrade to android 5.x?
thank for read

Help with new update and Magisk

Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.
faddys123 said:
Hey guys
so initially i rooted partition B using magisk now i got the new update of 75mb. I switched to partition A where it was still on august security patch and i made update of 1gb followed by 75mb update.
So i switched back to partition B and it was unrooted but the update did not install on this partition and told me to make update of 75mb again but i tired to update and it gave me an error but safetynet was not passed ctsproilfe:false
can someone help me? i tried to flash boot.img of stock but same result.
Click to expand...
Click to collapse
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.
cmk7128 said:
I ended up having to flash the previous Oct (7.10.14) fastboot ROM using MiFlash, rebooted back into the stock ROM and then took the single 1GB OTA update which has the Oct 30 kernel and build number. Booted into TWRP and reflashed Magisk 14.4 and Safetynet passed.
BTW, did you try booting into partition A and check whether the Oct 30 kernel and build OTA (75MB) update was installed? Just thinking this might be the case since you took 2 OTA updates.
Click to expand...
Click to collapse
using miflash did you do this without the data being wiped?
faddys123 said:
using miflash did you do this without the data being wiped?
Click to expand...
Click to collapse
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.
cmk7128 said:
I selected the "save user data" option before flashing in MiFlash but somehow all my data was erased when the phone rebooted. Not sure why that happened.
Click to expand...
Click to collapse
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?
faddys123 said:
if i just download the stock rom extract boot.img and system.img and flash manually via fastboot it should return to stock? with my app data etc still intact then i can run the update and then flash magisk for root?
Click to expand...
Click to collapse
Not sure, but worth a try. What about booting from partition A?
cmk7128 said:
Not sure, but worth a try. What about booting from partition A?
Click to expand...
Click to collapse
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct
faddys123 said:
i booted into A and it is updated with build 30 oct not rooted, but if i root this using new magisk 14.4 for future updates i won't be able to update and partition b is still on update from 14 oct
Click to expand...
Click to collapse
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?
Yesterday, I run into problems updating my phone to 30 oct version too. At the end I stuck into bootloops. This is how I solved it:
- boot into fastbootmode
- flash 14 oct Image with MiFlash (option: save user data)
- reboot
- download and install update 30 oct
- reboot into fastbootmode
- fastboot oem unlock
- fastboot boot recovery.img
- flash Magisk 14.4
- reboot Phone
cmk7128 said:
If I am not mistaken, you can boot into partition B (which is unrooted) for future OTA updates. Being on 7.10.14 updates would just mean the OTA files will be bigger in size compared to the OTA file for updates from 30 Oct?
Click to expand...
Click to collapse
well partition B was the one originally rooted, but i could not install the new update, so switched partition to A and did the update but booting into partition b still has build of 14th oct whereas partition A (unrooted) is on 30th oct build. so both partitions are not getting updated together

How to OTA a Moto G6 plus when rooted with Magisk?

My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following:
- Magisk Manager > Uninstall > Restore Images
- Settings > System > System Update
The phone started to download the OTA (about 300 MB), but afterwards said something like "sorry, that didn't work out".
I then did:
- Magisk Manager > Install > Install
and then phone is fine for now.
I can probably catch the download URL for the OTA by using the logcat method. But what would I do with an OTA zip? The OTA is significantly smaller than a complete firmware (about 2 GB).
bornheim2 said:
My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following:
- Magisk Manager > Uninstall > Restore Images
- Settings > System > System Update
The phone started to download the OTA (about 300 MB), but afterwards said something like "sorry, that didn't work out".
I then did:
- Magisk Manager > Install > Install
and then phone is fine for now.
I can probably catch the download URL for the OTA by using the logcat method. But what would I do with an OTA zip? The OTA is significantly smaller than a complete firmware (about 2 GB).
Click to expand...
Click to collapse
I'm not sure if that's possible, but I wouldn't try it. The best way is to reflash stock and then accept the OTA. Afterwards, you can reinstall Magisk.
See if the firmware update has been posted here. In either case do a backup with Titanium Backup first. If the complete firmware update has been posted, flash it with fastboot in the bootloader. If it had not been posted, flash the latest version available and then Ota. After your up to date reflash magisk in twrp.
Sent from my moto g(6) plus using Tapatalk
Hi,
At time, is no solution to update with OTA with a rooted MotoG6+ with Magisk.
I'm working on a workaround.
Regards.
You can also use Lenovo Moto Smart Assistant and "Rescue" your device. It basically downloads the firmware and flashes it for you (wiping everything on the device (excluding External SD). That's what I did.
New OTA update arrived today. Is there already a solution for this? I thought that the new systemless Magisk would "fix" this, but OTA update still fails. No clue why. I even ended up in a bootloop, but switching active partition back to b fixed that...
I don't get why we should be excluded from updates, just because we want to be root on the devices we own. It just doesn't make sense.
This time I tried removing Magisk and restoring boot and system partition (from backup before installing Magisk) before starting the OTA because someone said that when you start the OTA it switches A_B partitions and restoring from backup doen't restore them in the right place and thats why it might fail (or something like that) BUT same result. OTA fails! I guest every month I'll have to flash stock (losing everything on the phone in the process) -> install OTA -> reinstall everything.
WHY exactly the OTA fails? It shouldn't detect that the partitions are modified because they're not (restored from backup before Magisk).
ivailogeimara said:
You can also use Lenovo Moto Smart Assistant and "Rescue" your device. It basically downloads the firmware and flashes it for you (wiping everything on the device (excluding External SD). That's what I did.
Click to expand...
Click to collapse
I have XT1926-3 and Lenovo Moto Smart Assistant says that my device is not supported. Do you have the same device?
joris1977 said:
I have XT1926-3 and Lenovo Moto Smart Assistant says that my device is not supported. Do you have the same device?
Click to expand...
Click to collapse
I used LMSA when I was running OPW113.89 to update to OPW113.89-2 (via the Recovery option). It asked me to select the product and model of the phone. I selected "Moto G Plus (6th Gen)" for the product and for the "Model Name" I had XT1926-2,XT1926-3,XT1926-5,XT1926-6,XT1926-7,XT1926-8,XT1926-9. The new version of the LMSA has 3 buttons at the top of the rescue screen: "Lenovo Phone", "Lenovo Tablet", "MOTO Phone". Make sure that you select "MOTO Phone"
I'll try it again because I just tried to recover system partition backup (made with TWRP) with TWRP and bricked my phone. And for some reason I can't flash the images from the firmware with fastboot. For some of the images that have A and B partitions it tries to flash them to non existent partitions. For example:
Code:
fastboot flash boot boot.img
or
Code:
fastboot flash system system.img_sparsechunk.0
tries to flash them to boot__b or boot__a or system__b or system__a (with double '_')
The annoying thing is that I don't have Windows outside VM so every time I need to run LMSA I have to create WINTOGO usb just to run LMSA.
ivailogeimara said:
I used LMSA when I was running OPW113.89 to update to OPW113.89-2 (via the Recovery option). It asked me to select the product and model of the phone. I selected "Moto G Plus (6th Gen)" for the product and for the "Model Name" I had XT1926-2,XT1926-3,XT1926-5,XT1926-6,XT1926-7,XT1926-8,XT1926-9. The new version of the LMSA has 3 buttons at the top of the rescue screen: "Lenovo Phone", "Lenovo Tablet", "MOTO Phone". Make sure that you select "MOTO Phone"
I'll try it again because I just tried to recover system partition backup (made with TWRP) with TWRP and bricked my phone. And for some reason I can't flash the images from the firmware with fastboot. For some of the images that have A and B partitions it tries to flash them to non existent partitions. For example: or tries to flash them to boot__b or boot__a or system__b or system__a (with double '_')
The anoying thing is that I don't have Windows outside VM so every time I need to run LMSA I have to create WINTOGO usb just to run LMSA.
Click to expand...
Click to collapse
Why did you try to update with lenovo assist? Was your rom clean as in no Magisk?
What TWRP did you use, and was your device encrypted?
Need much more info to be able to help, also what is your main OS because you don't need windows for fastboot.
Have you tried booting original boot.img through fastboot?
Maybe changed active slot?
Coldstream said:
Why did you try to update with lenovo assist? Was your rom clean as in no Magisk?
What TWRP did you use, and was your device encrypted?
Need much more info to be able to help, also what is your main OS because you don't need windows for fastboot.
Have you tried booting original boot.img through fastboot?
Maybe changed active slot?
Click to expand...
Click to collapse
Uninstalled Magisk from Magisk manager. Device is encrypted. The TWRP I use is from this thread.
The previous time I used LMSA was because uninstalling Magisk (which flashed boot partition backup) didn't help with installing the OTA (it still failed). And flashing the images from firmware with fastboot gave error. It tried to flash them to boot__a or boot__b, system__a or system__b (with double underscore). I was gonna try updating with LMSA again but decided to try flashing images from the firmware manually with mfastboot this time and it worked. It'll be good if in the guide for "how to return to stock" it said that the included fastboot is mfastboot.
I just flashed the stock images (without data,cache) with mfastboot and I'm trying to update again via OTA.
Update: OTA installed successfully!
PS: Can I check if some partition is modified in some way like OTA does?
ivailogeimara said:
WHY exactly the OTA fails? It shouldn't detect that the partitions are modified because they're not (restored from backup before Magisk).
Click to expand...
Click to collapse
Yeah I am asking myself the same question. I grabbed a log file and it shows a lot of:
Code:
/system/bin/update_engine: [libfs_mgr]Error finding 'slot' in device tree
I am clueless, but it seems that Magisk somehow disabled the ability for the phone to see slot A. An error that stays even after Magisk is fully removed; I even flashed the untouched boot.img back. But that made no difference.
I also tried sideloading the OTA with ADB on the recovery screen, but that fails too & I see the same error on the screen.
BTW You can grab the OTA with help of this website: http://erfanoabdi.000webhostapp.com/
I am always a bit hesitant in posting log files with a lot of stuff that I don't understand, but as an attachment I add here the lines of the log that contain messages about the update_engine.
joris1977 said:
Yeah I am asking myself the same question. I grabbed a log file and it shows a lot of:
Code:
/system/bin/update_engine: [libfs_mgr]Error finding 'slot' in device tree
I am clueless, but it seems that Magisk somehow disabled the ability for the phone to see slot A. An error that stays even after Magisk is fully removed; I even flashed the untouched boot.img back. But that made no difference.
I also tried sideloading the OTA with ADB on the recovery screen, but that fails too & I see the same error on the screen.
BTW You can grab the OTA with help of this website: http://erfanoabdi.000webhostapp.com/
I am always a bit hesitant in posting log files with a lot of stuff that I don't understand, but as an attachment I add here the lines of the log that contain messages about the update_engine.
Click to expand...
Click to collapse
I think this:
Code:
12-20 13:31:48.480 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1099)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
12-20 13:31:48.480 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1104)] Expected: sha256|hex = 66305C30BC5570791036FFC5B57E620D516B35664C3EE5B27F97FBFD5E288817
12-20 13:31:48.481 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1107)] Calculated: sha256|hex = E2D46DB42162711333E99BF1CBD0224F5867F6E7387FA276D30EC54755AF454B
is where the update fails. I'm not sure though what partitions is the OTA checking.
I flashed every partition listed in servicefile.xml (in the stock firmware files that you can flash) and after that I was able to install the OTA. Next I made backups/images (not restorable though) with dd of all the partitions that are listed in servicefile.xml because clearly one or multiple of those get changed after installing Magisk and that's why the OTA fails. After that I installed magisk and made backups with dd again and compared the two to see what changes after installing Magisk. These are the partitions that were changed after Magisk and are in servicefile.xml:
Code:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
I guess uninstalling Magisk only restores the boot partition and one of the others fails the check. Probably oem_b.
PS: Well I guess for now the solution will be to flash everything listed in servicefile.xml (except system and system_b) via mfastboot before each OTA.
Thanks for your informative post @ivailogeimara
Lenovo fixed their Lenovo MOTO smart assistance, so now you can reflash your device. with the help of this app. I just reflashed my device and everything is working as expected.
If you use LMSA it downloads a zip file with the full OS where the new OTA is already included. Probably you can cut off the rescue operation after the full zip has arrived and you can just use that zip to flash the boot partition and that oem_b. partition I didn't try that, because I had limited time, had already backed up all my data and I needed a working phone. This is probably what I will try next time an OTA arrives.
Maybe we should make the magister developers aware about the troubles with the Moto G6 plus. It is probably I bug somewhere that uninstalling Magister does not fully restore the old install.
ivailogeimara said:
These are the partitions that were changed after Magisk and are in servicefile.xml:
Code:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
I guess uninstalling Magisk only restores the boot partition and one of the others fails the check.
Click to expand...
Click to collapse
This is exactly what I get on my phone. For the last two OTAs these are the partitions that fail the checksum verification. As you mentioned this is fixed by flashing the partitions from a known good source.
I used TWRP via "mfastboot boot twrp.img" to dump boot.img, modify it via Magisk-Manger and then flash it using mfastboot. I don't see any way how I would modify the other partitions (except boot, of course) this way.
I looked into the oem-partition and it has its "last mounted" timestamp changed to something very, very recent. This is why I rule out TWRP. My best guess is that Magisk mounts those partitions shortly as rw maybe on boot? That would already be enough to make the hash fail
So basically to be able to install the OTA:
1. after clean stock reinstall (before magisk installation) backup the above mentioned partitions
2. install magisk, etc.
3. later when an OTA update comes restore the backed up partitions + remove magisk and then install the OTA
4. back to step 1
I suppose the partitions can also be restored if you find the firmware that is identical to what the phone is currently running.
Or???
axsdenied1 said:
I suppose the partitions can also be restored if you find the firmware that is identical to what the phone is currently running.
Or???
Click to expand...
Click to collapse
Yes, that's what I did. Never thought to pull a backup of a partition that would only "ever" be changed by the OTA process I googled a bit for my version number until I found a matching stock ROM.
Moto g6 + rooted with twrp and magisk. I have an OTA update.
The OTA gets errored out right after I download the update and it tries to install it.
Phone version: XT1926-7
Using latest twrp 3.2.3
Magisk v18.0 installed.
Successfully enabled root just the other day.
Now I get the OTA update ppw29.116-11 wanting there pie update to rollout, was so happy. Except it keeps saying unsuccessful right after it's done downloading and tries to install I guess.
Has anyone found a safe workout for this?
It is outlined in the post just before the one you made...
So
before installing Magisk you should have made a backup from the following partitions:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
when an OTA update comes, remove magisk and restore the backed up partitions.
then install the OTA
make a backup again.
This should work, but I didn't test it yet.

Categories

Resources