Develop Bugs

[Q] How to update to 4.4.3 with root

Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.

UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.

UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.

charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.

Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.

Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.

You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.

I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?

Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.

Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.

Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.

Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.

You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).

is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!

droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.

thanks

Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.

Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..

mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.

Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:

Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are

Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

[HOW-TO] Revert from an Oreo Custom ROM to stock and install Official Oreo via OTA

I decided to make this thread so people won't brick their devices/lose their IMEI/explode their phone when trying to update to the recently leaked/released Oreo Motorola ROM.
This is very information dense. Please, read this and the linked threads carefully and do not miss any step unless told so.
WARNING: This will erase all your data, reset all your settings. MAKE BACKUPS.
I also do not hold responsibility for any negative outcomes out of following this tutorial.
Always look for as many sources of information as you can. There is always something that isn't 100% correct in every tutorial.
Also, making it clear. This is for those who are currently on an Oreo CUSTOM ROM such as Lineage, Pixel Experience or other.
Preparation Steps:
Backup all your important files to your PC. You should do that since everything will be reset.
Make sure your phone is well charged. 80% at least. You want to be safe.
Boot into fastboot.
Install Minimal ADB and Fastboot.
In the command prompt of Minimal ADB and Fastboot, type:
Code:
fastboot getvar all
You will see a bunch of lines come up on the screen. Scroll and look for
Code:
(bootloader) ro.build.fingerprint[0]
.
This will tell the last version of the Stock ROM (Nougat) you had installed.
Example: "NPNS25.137-92-4" Yours won't/may not be the same.
Write it down somewhere. You will need this version number.
Open this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ to download the exact version you found. If anything, download a version above the one you found. Never an inferior. Those are Motorola's Official Nougat ROMs.
Keep it somewhere accessible in your PC and extract the zip. Remember where you put it, you will need it later.
You will now proceed to check your persist partition. Aka: The thing everyone overlooks and screws your IMEI.
IMPORTANT: Take a look at https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 to find out if your persist partition has permission issues and see if it's recoverable. It is 99% likely that if you are on a custom Oreo ROM that the permissions won't be intact.
If that is the case (most likely), download NZedPred's TWRP Persist Restore zip into your phone.
Feel free to skip these last steps if you have a backup of your persist and efs.
Reboot into recovery and using the most recent TWRP make a backup of your persist and efs. (Information about this can be found on the second post of the "Fix Persist" thread. I am not willing to write a thousand instructions on one thread for the sake of not overcomplicating things.) //****ty steps: have/flash most recent TWRP > backup > select persist and efs > profit
These backups should be on a TWRP folder of the internal storage of your Moto G5. Reboot the phone (or mount USB) and copy that folder to your PC. In case anything goes wrong you will have a copy of your persist.
Steps:
Reboot into recovery (TWRP) using your preferred method. (Be it by the buttons, or via ADB (adb reboot recovery)).
Flash the TWRP Persist Restore zip.
Reboot into bootloader
Open (on your PC ofc) the folder with the extracted files of the Stock ROM zip (NOUGAT).
Open the extracted files folder then press Shift+RMB (Right Mouse Click/Button) and select "Open Command Prompt here" (It may work with Powershell??? If anything, write a post here)
For a quick test, type
Code:
fastboot
In case an error pops-up and tells you that it can't recognize such a command. Follow this article https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ to add Minimal ADB and Fastboot to your system environment variables
Now, make sure that the path to the left of the typing cursor is the path of the folder where you have your extracted Nougat ROM files.
Please, for your phone's OTA update ability sake. Make sure that you are flashing the exact version you had before. The version you found by running fastboot getvar all.
The commands below will attempt to update the bootloader and gpt. You should NEVER flash an older version of the bootloader.
If you wish, you can skip the GPT/Bootloader commands. I haven't done myself because I flashed the correct version I had before anyway.
Copy and paste these commands and press enter in the CMD.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will flash the Stock Nougat ROM you have downloaded and will reboot your phone. If all goes well you will be back on Nougat, set up your device as normal.
Attention, everything has been reset, erased, wiped.
Oreo OTA Steps:
After setting up everything, check for OTA's. You should be safe to install them. If you are on a recent firmware, you may only need to install security ones. Keep installing and checking until it says there are no more updates available.
This is where people **** up when they downgrade their bootloader by flashing an older Stock ROM than the one they had before.
Before proceeding, double check that there aren't any OTAs available or that Oreo is available at the time of reading this.
If Oreo is officially available, skip all of these steps and be happy.
Otherwise, if at the time of reading, there is a ZIP of the Oreo ROM that matches your region. Download it.
In case of RETLA, RETBR, and RETIN, at the time of writing, this is the correct file:
https://mega.nz/#!DxdSVaJb!5VEht-s6HYCNOZ2hXXVIPdFBqmWCuAvQL1Wzmp7rhZk or https://drive.google.com/open?id=1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY
In case you are on RETUS, RETAPAC, RETEU, etc. You may need another file that may not be available. The best course of action would be to wait for the Official OTA. :good:
Download it and put in the root of the internal storage of your Moto G5 Plus.
Go to the Settings app. In the Settings app, you'll want to find the OTA App (Motorola Update Services) by showing System apps and enable storage permissions.
Before you proceed: This is apparently indeed the official OTA that they will ship, which seems to be the same as the Soak 4. It's seemingly stable here, so, you should be fine to use that.
Check on your phone for an OTA.
Reboot it.
Check for an update again. There will be a prompt telling you about copying "system" files. Accept it.
After a while, another prompt will ask you about the update. There won't be a changelog, this is normal. Make sure your device is charged and install it.
Wait for the update to complete and you're done.
Tips:
You can also refer to this thread for some more information about fastboot flashing:
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Refer to this thread if you need persist information:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Google and XDA are your friends.
It's good practice to wipe/reset your phone after you're done. Updates usually leave dirt behind. I haven't personally done this myself and everything is OK, but still...
Feel free to correct me on any mistake. It took me about an hour (or more) to write this and I could have potentially overlooked an important detail.

I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo , what do you think? Thanks!

TheGameExtreme said:
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo, what do you think? Thanks!
Click to expand...
Click to collapse
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92

I had hardbricked my phone and am using a tarp flashablr stock ROM. Can I use this method to go back to stock?

BlackScout said:
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
Click to expand...
Click to collapse
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch

TheGameExtreme said:
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
Click to expand...
Click to collapse
Yeah, your bootloader is still from Nougat. One day, that could become a problem (hard brick) when taking OTA's.
You can easily fix that by going back to Nougat. (Just make sure to flash the exact version (or one above) the one you had before. Remember, never downgrade your bootloader.).
I think you can just fastboot flash NPNS-25.137.92-14 (since the difference between that and the base 92 patch is just security patches...), download the OTA zip that's been posted around and follow the last set of instructions here (The ones labeled Oreo OTA Steps)
Remember, flashing those TWRP zips made by NZedPred is technically not the same thing as fastboot flashing or taking an OTA. These zips don't upgrade your bootloader and the OP of those threads do not recommend you to take any OTAs.
Quoting from the source: https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The partition table and bootloader are not included, which makes it safer to up/downgrade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
So if you want to take the Oreo OTA and have an upgraded bootloader (C0.92), don't flash these. Flash the official Stock ROM (Nougat) images using fastboot then take the OTA.

I got all the information from this guide thanx but one doubt is there , i have my own efs nd persist and i have also backed it up so do i need to restore the restore zip or m i good to just fastboot flash nougat rom and update it via OTA to oreo? I m using custom oreo rom right now and i have never lost 4g or imei that means my efs and persist is my original..

I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.

karan3660 said:
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
Click to expand...
Click to collapse
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update

psychopac said:
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
Click to expand...
Click to collapse
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.

karan3660 said:
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
Click to expand...
Click to collapse
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.

psychopac said:
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
Click to expand...
Click to collapse
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide

karan3660 said:
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
Click to expand...
Click to collapse
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Click to expand...
Click to collapse
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.

NZedPred said:
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
Click to expand...
Click to collapse
That would be a nice move from Moto/Lenovo.
So I should have said:
So you probably won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs

The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?

nvrpayretail said:
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
Click to expand...
Click to collapse
This Oreo OTA requires the Brazil or Indian firmware to flash onto (possibly Latin America firmware). As you've found out, this OTA is NOT compatible with US devices as they're on a different stock build. You'd have to wait for the EU, APAC or US OTA updates to be leaked or released. You'd also have to be on the NPNS25.137-93-14 update to apply the OTA update when it arrives.

The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip

nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version28.potter.retail.en.US.zip
Click to expand...
Click to collapse
Yup, I've checked the link and it's linking to the Brazil Oreo OTA update. Despite the suffix 'en.US', this does not necessarily mean this update is for the US devices.
Furthermore, looking at the OTA updater script, it specifically requires NPNS25.137-92-14 or OPS28.85-13:
Code:
Package expects build thumbprint of 8.1.0/OPS28.85-13/b8ea:user/release-keys or 7.0/NPNS25.137-92-14/16:user/release-keys
Since you have mentioned you have NPNS25.137-93-14 this OTA simply will not flash to your device. You must wait for the compatible OTA to be released.

nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
Click to expand...
Click to collapse
Despite its name, it is not the us ota.

[Question] How to apply security patch to rooted device.

Hey, I previously rooted my phone and would like to apply new the January Security update. I am wondering if someone can outline the steps to apply this new update without wiping any of the data off my phone.
From what I understand I need to do the following.
Download OTA image from google
Download newest Magisk image
Download TWRP
Extract OTA (Radio, Update and Bootloader)
Extract TWRP
Copy Magisk to Phone
Copy TWRP Installer (Optional)
Then the work on the phone
1.
Code:
fastboot-devices
fastboot flash bootloader new-bootloader-image (then reboot into bootloader)
fastboot flash radio new-radio-image (then reboot into bootloader)
fastboot flash update new-update-image (then reboot into twrp)
fastboot boot twrp-image
2.
In TWRP Decrypt data and install Magisk newest release
3.
Profit now it works?!
I just wanted some confirmations before I go and do this before I make a mess. Also has anyone had issues with TWRP being able to decrypt data with this security update

ericedg said:
Hey, I previously rooted my phone and would like to apply new the January Security update. I am wondering if someone can outline the steps to apply this new update without wiping any of the data off my phone.
From what I understand I need to do the following.
Download OTA image from google
Download newest Magisk image
Download TWRP
Extract OTA (Radio, Update and Bootloader)
Extract TWRP
Copy Magisk to Phone
Copy TWRP Installer (Optional)
Then the work on the phone
1.
2. In TWRP Decrypt data and install Magisk newest release
3. Profit now it works?!
I just wanted some confirmations before I go and do this before I make a mess. Also has anyone had issues with TWRP being able to decrypt data with this security update
Click to expand...
Click to collapse
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + January 2019 Security Patch
'If Stock'
Do #4 'keep data'' then do #8 to root/Reroot
'If Custom ROM'
Read #11

The above instructions are very ambiguous for a patch upgrade, i'm finding all kinds of inconsistencies with the directions. Currently stuck trying to flash payload.bin from the ota and it's saying cannot determine image filename for payload.bin.

dhufford81 said:
The above instructions are very ambiguous for a patch upgrade, i'm finding all kinds of inconsistencies with the directions. Currently stuck trying to flash payload.bin from the ota and it's saying cannot determine image filename for payload.bin.
Click to expand...
Click to collapse
Download stock factory image, decompress, open terminal or cmd line and change directories into the decompressed folder, remove -w from flash-all script, and run the script.
Then fastboot boot twrp on use booted twrp to flash twrp, kernel, & magisk.

smartymcfly said:
Download stock factory image, decompress, open terminal or cmd line and change directories into the decompressed folder, remove -w from flash-all script, and run the script.
Then fastboot boot twrp on use booted twrp to flash twrp, kernel, & magisk.
Click to expand...
Click to collapse
Thank you for clearing up that i shouldn't be trying to flash the OTA download, that's where i got hungup. Cheers!

dhufford81 said:
Thank you for clearing up that i shouldn't be trying to flash the OTA download, that's where i got hungup. Cheers!
Click to expand...
Click to collapse
TWRP had the ability to flash the OTA update on P2XL. It might be something that works again P3XL in the future.

[guide] OTA update when rooted ( revert to non-rooted , update—>root again)

Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Step 2:
so the phone booted, and I ran the update again. This time I had no issues installing it.
Step 3:
i extracted the new Boot.img from the rom downloaded by LMSA
I re patched the new boot.img with magisk, rebooted again, and and the update was complete.
this was done on the eu g8 power , for update qpe30.79.124 , but i guess this will work on all versions since the process is the same ...
for people reading this, and don’t have root / want root, just read this thread:

Confirming success with this. I downloaded the whole ZIP, extracted boot.img and used Magisk App's built-in feature to mod the boot img. Afterward, I reflashed boot partition via fastboot. Thanks, all!

Success on Sophia RETUS 80-51-5. Flashed 80-51-3 stock boot with fastboot, took update, extracted BOOT from 80-51-5, modified with Magisk and flashed the mod with fastboot. Back up and running.

I have twrp installed. Will this work?

No, I don't believe so.
3dekstron said:
I have twrp installed. Will this work?
Click to expand...
Click to collapse
As far as I know you will also have to flash the stock recovery before updating... not sure if the recovery has to match the stock rom build, like the boot.img does. You could also flash the entire latest stock rom using LMSA to update.

pjottrr said:
Since you are rooted, you probably found out the OTA update won’t install.
after 3 % it crashes, and no update is installed.
So this is what I did to get the latest update:
step 1: remove root access;
- reboot and hold volume down to get into fastboot mode
- connect to pc, and load original boot.img , I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
- I connected to LMSA, to make a backup, and download the new rom.
- I went to fastboot mode again and flashed the boot by using the command “fastboot flash boot boot.img ( the “old/current” one, not the one from the downloaded new image”
“fastboot reboot”
Click to expand...
Click to collapse
What does this mean (from above) and what results are to be expected?
I checked if that was the proper one by using “fastboot boot
boot.img” ( I checked if magisk was no longer installed, this was merely to find out if I used the proper boot.img, I knew
chances the update would install were slim, I tried… but no luck as expected…. )
Click to expand...
Click to collapse
I'm guessing that a fail is expected since original boot.img is no longer installed (ie, rather the patched version is installed). Hopefully someone can elaborate

Also in the case of the Magisk systemless root method, will OTA announcements occur even though they can't be installed without first unrooting?

I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?

TaZeR369 said:
I wonder if there is not a few steps that could be cut off and streamlined this method, for example why isnt uninstalling magisk enough, since magisk restores the boot.img, also it backs up the original boot.img so instead of going through the whole LMSA thing it can be just copied to storage and flashed in fastboot, right?
Click to expand...
Click to collapse
I just did that with a sofia retus phone on Android 11 for the new security update.
RPM31.Q1-54-13 to RPMS31.Q1-54-13-2.
1. Uninstall all Magisk modules and reboot
2. Uninstall Magisk and hit restore image
3. Uninstall Magisk completely and phone reboots
4. Accept OTA update (nervously)
5. Patch boot image with Magisk
6. Flash patched image with minimal adb and fastboot
7. Success!
this process does replace vanced youtube with factory youtube and youtube music, but it's easy to just replace them again in vanced manager.