Related
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
I would like to know the same thing
Naruto101 said:
I am currently on stock rom but rooted. An Ota update popped up can I update without bootloop
Click to expand...
Click to collapse
stkman32 said:
I would like to know the same thing
Click to expand...
Click to collapse
No you can't take an OTA if you have any modifications to /system (root). Have a look at my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Thanks for answering my question
roughriduz said:
I got an 8MB update for the november patch. Being on TWRP and root i need to convert back to stock before i can have it leave me alone? Is there a way to flash the patch without doing that?
Click to expand...
Click to collapse
No way around it, any modifications will cause the update to fail.
Heisenberg said:
No way around it, any modifications will cause the update to fail.
Click to expand...
Click to collapse
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
User data should never be affected during an OTA anyway.
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I am rooted now so I'll wait a while before updating an ota until there's a big deal of info. However, in the past if I was sticking with stock there's usually at least one developer who posts the updates with root and stuff built in so you can easily flash with twrp. So I'm kind of waiting for that. That or cataclysm or another awesome rom that's close to stock.
GloriousGlory said:
This is actually the first time I've unlocked a phones bootloader and stuck with the stock rom. I usually use some kind of popular rom with it's own built in OTA (CM/Viper One)
How often do you guys actually update your phones for OTA? It seems like a real hassle
Click to expand...
Click to collapse
I wait for factory image for that build and flash over the new images when they become available (provided that root can still be achieved). Some will do a clean wipe and start fresh with the new build and reload in their apps and user data, others will just dirty flash the updated system (and boot/bootloader or whatever else was changed too).
If you think about it, it really isn't all that different from taking an OTA, the difference is that we're applying the commands to flash instead of having it automated. It's not that big of a trade off in my book.
I have 2 questions...
What is the easiest way to make flashing updates a breeze if I have mods in /system partition? I have heard of "freezing" them. Or is the only option... to delete every mod and flash updates? If so, should I keep a note of every change I make to/system?
And last... Should I make a backup of any file i am replacing or overwriting in /system? And if so, do I have to put them back how they were before flashing an update?
Delete
If you're rooted then you need to download the full factory image, extract system and vendor and flash those. Reflash SuperSU.
roughriduz said:
@amoeller had me flash the modified boot.img for MDB08M then flash the MDB08M system.img and vendor.img from the factory image. I rebooted bootloader, the booted to TWRP and re-flashed supersu. I am now on the November patch without having to remove TWRP and all works well. My user data was also untouched.
Click to expand...
Click to collapse
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit.
This method gives you the latest stock build rooted with TWRP while keeping your data because I hate having to redo my phone.
Click to expand...
Click to collapse
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. Latest factory image is the latest factory image from the nexus factory images page. It's not an update like ota, but rather the entire image they would return you to stock if all is flashed.
2. Flashing a modified boot does not give you root. You still have to flash SU, so saying the modified boot contains root isn't right.
3. I flash boot first unless there is an updated bootloader.
JimmyJunk said:
A couple questions:
1. Step 1 refers to the latest factory image that contains the update, correct?
2. Step two refers to the boot.img that contains root?
3. At what point in this process do you flash the modified boot.img, before or after applying the other images?
Thanks for your help!
Click to expand...
Click to collapse
1. This can be whatever the latest factory image is at the moment. It’s currently MDB08M. All the OTA does is update your phone to whatever build it was made for. Factory images already have previously released updates built into them. You can upgrade but avoid downgrading unless you want to factory reset your phone.
2. I’m referring to the boot.img without root by @mrRobinson found https://www.androidfilehost.com/?fid=24269982086992320 although this process can be used for systemless root also. For systemless root you wouldn’t flash SuperSU in TWRP but instead sideload the SuperSU APK as per Chainfire’s instructions and use the matching systemless root boot.img
3. I don’t think it matters but as long as you have the matching modified boot.img with the system.img installed before you restart, you should be fine.
amoeller said:
It’s probably easier and quicker just to flash stock factory images separately instead of having to jump through hoops with OTAs. Like I told @roughriduz just flash the updated partition(s) that were updated like system.img, vendor.img, or whatever and just flash SuperSU in TWRP after.
The steps @roughriduz took was
1. Download and extract latest factory image.
2. Download matching modified boot.img for that build (For example MDB08M).
3. Flash system, vendor, and any other partitions (like radios, etc) with fastboot if they were updated in the OTA. Don’t bother to flash stock recovery because we’re not using an OTA. Flashing userdata.img is just like a factory reset.
4. Boot directly into TWRP and flash SuperSU.
5. Reboot and profit..
Click to expand...
Click to collapse
What the heck did I do wrong here? I just tried to apply the November OTA update to my MBD08K build, it didn't work, and now I am in the process of doing a full reset and rebuild of my phone (flash-all of factory images from Google)
Here are the notes I made as I attempted to follow the procedure in this thread:
Code:
- Download latest build for MBD08K from https://developers.google.com/android/nexus/images?hl=en
- Extract boot.img, system.img, vendor.img to C:\adb (or wherever where adb and fastboot are
installed). You have to
- Right-click, open command window here
- Ensure USB debugging is enabled on phone (grant permissions on phone if you get the popup)
- In command prompt, "adb devices"
- Should see serial number and "device"
- type "adb reboot bootloader"
- Should get to bootloader screen with little android man lying down with hatch open
- type "fastboot devices" - should see your serial # again and "fastboot" beside it.
- type "fastboot flash boot boot.img"
- type "fastboot flash system system.img"
- type "fastboot flash vendor vendor.img"
- Use volume keys to boot into recovery (in my case TWRP)
- Swipe to allow modifications
- Install -> SuperSU.zip that you should have on your phone from last time.
- Reboot system
I saw a red "your phone is corrupt" scary message on startup... took a while to boot. Couldn't get past the dancing circles.
Interrupted boot, rebooted to fastboot, tried to flash old modified boot.img
Booted again, got encryption unsuccessful warning
Flashed most recent boot.img again, stuck booting forever
try again:
- flash system.img
- flash vendor.img
- flash boot.img (modified)
reboot to recovery - your device can't be checked for corruption (yellow warning instead of red)
- swipe to allow modifications
- reboot with TWRP, swipe to install SuperSU
- Encryption unsuccessful. Prompt to factory reset. Click OK. Boots through TWRP.
Give up, start flashing factory images.
EDIT: I might be the stupidest person alive. I think I should have been using the files for MDB08M. Arggghhhh. Someone please confirm I am an idiot.
Edit 2: Factory reset worked, I am at MDB08M. Now rooting again... grr. At least I backed up all my apps & settings to Google Drive with TB.
Edit 3: Rooted and restoring all apps with TB. If anyone has any insight into where I F'ed up I'd appreciate it.
I just receveid an OTA update, but the installation stuck because the system is rooted.
I found the update.zip file on my Handy, but it contains some directory (Meta-inf, patch and system) and a big file update.app that I believe contais all the update file.
Is it possible to extract the file from update.app and then create an update that can I launche from TWRP? And if so how could I do it?
Thanks
You can't.
flash back a stock recovery.
After ulocking bootloader and root the OTA didn't work with original recovery that's why I wanto to create an update that works with TWRP
did you try?
ItalianWolf said:
did you try?
Click to expand...
Click to collapse
Yes I reinstalled the original recovery that you can find in t he root package and I completely unroot the phone using the unroot command in SuperSu.
Then I launch the update but after reboot it stuck at 11%, so I create the dload folder in my handy memory and copied there the content of update.zip and then forced the update. In this case, after reboot, it load until 99% that it reboot, but the installed version is still the 170 and not the 188.
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
ItalianWolf said:
Here worked, from post #393 to # 397 and #400
Stock recovery in root zip maybe too old.
Edit:
Ops perhaps it work on full update packages.
Click to expand...
Click to collapse
What does here mean?
Which thread?
Thanks
Harlock1978 said:
What does here mean?
Which thread?
Thanks
Click to expand...
Click to collapse
Sorry, forgot link: http://forum.xda-developers.com/p8l...-lite-android-6-0-marshmallow-t3305550/page40
You need the Huawei Update Extractor Tool, and do the following:
Load the UPDATE.APP file inside the HUET
Extract boot.img, system.img, and cust.img, from UPDATE.APP inside the HUET
Flash the respective files via Fastboot
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
AmINoS007 said:
so if I am on Marshmallow beta, should I flash the recovery that comes with the marshmallow or the recovery of the B052 rom ?
Click to expand...
Click to collapse
If you have to, flash the B052 recovery... you can always flash the Marshmallow recovery if it doesn't let you update.
I only flashed boot.img, cust.img, and system.img, when I upgraded; didn't flash Marshmallow's recovery at all.
Don't think you can even get OTA updates on the Marshmallow beta anyway (even via a normal bootloader-locked device).
Sorry for my late answer but I was travelling only with a Mac and I couldn't use Huaweu Update extractor.
This are the file that you can find in UpdateApp 188:
00.SHA256rsa.img
01.crc.img
02.curver.img
03.verlist.img
04.efi.img
05.fastboot1.img
06.boot.img
07.recovery.img
08.recovery2.img
11.cache.img
13.dtimage.img
14.dsp.img
15.fastboot.img
16.hifi.img
17.mcuimage.img
18.modemimage.img
19.modemnvm1.img
20.teeos.img
21.trustfirmware.img
And also the following directory:
META-INF
patch
system
Which file should I install, I didn't find a system.img and there are two different recovery
Thanks
You should not install any OTA with TWRP...
Flash back the stock recovery, update, then flash the twrp again, it's way easier and more secure, than doing a flashable zip from an OTA update without knowing what to do with the file within.
The OTA updates usually doesn't contain the SYSTEM.IMG file you are looking for, it contains individual files and scripts to patch up the current system partition to work with the new update.
From the two recoveries you should use the RECOVERY.IMG (the one without the 2 in it).
But again, I do recommend to flash the original recovery(not the one in the update), do the update, and put twrp back.
Where can I find the original recovery from ALE-L21C432B170, so that I can flash the original recovery again?
TIA
I found the original recovery and flashed it then I did a complete unroot and tried again to do the OTA update but it stopped at 11%.
Is there a different way to update?
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:
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.