Related
My device is European L04, currently running North Africa release (the earliest Marshmallow build uploaded) - L04_2016_0316_0900 (B820)
I'd like to unlock the bootloader and root my Honor 6. I've never done it (on this particular device), because I've read enough here to know it's slightly more risky than on other devices, especially when you plan to update the stock rom soon, so I preferred to wait until I have the last important update the device is likely to receive - Android 6.0.
What I want to know (some of the answers are in the topics which I listed below):
MultiTool - I've seen reports of bricks when using MultiTool with EMUI4/Marshmallow - why does it happen? My understanding is that MultiTool is a bundle of adb/fastboot and some recovery images for older Android versions, so my theory is that instead of using MultiTool, I should simply get the proper recovery for Marshmallow and flash it manually with fastboot, right?
unlocking bootloader, rooting, flashing recovery - I think I understand the process; in a nutshell: 'fastboot oem unlock X', 'fastboot flash recovery imagename.img', then flash the proper SU.zip in recovery. Where do I find the code, the Marshmallow recovery image, the SU.zip file?
will recovery backup in TWRP work without any problems?
what is the procedure to go back to stock completely after rooting? Unroot, (then wipe if it's needed?) so I am able to safely flash stock firmware again (since, from what I know, flashing stock on a rooted phone makes itself brick permanently, right? or is it just a soft-brick and it can be fixed?)
is there anything else I should know before proceeding?
What I found so far:
http://forum.xda-developers.com/showpost.php?p=66615082&postcount=502 - two recovery images, TWRP and another one (stock?) for the Marshmallow release
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060/page50 some rooting instructions for the L02 beta, see posts 494 and 498; no idea whether this is applicable to final Marshmallow or L04 at all
http://forum.xda-developers.com/honor-6/general/huawei-honor-6-plus-unlock-bootloader-id-t3357259 an app to get the unlock code, seems a bit shady to me though on the first glance
http://forum.xda-developers.com/honor-6/development/honor-6-rooting-method-t2962795 alternate methods for bootloader (through a website or by email), in case the app won't work; also, detailed instructions on unlocking and rooting
Basically, I need to know whether my procedure is more or less right before I proceed. I think the information is quite hard to find and the risks are quite high, so I'd like to make a promise - when I'm done rooting it and I know the correct process, I'm going to make a "Update to Marshmallow, unlock, root" how-to thread for all the people that will need it in the future.
Another two questions...
1. Where do I get proper SuperSU for Marshmallow? I get a boot loop (yeah, I know I have to wait and I did, but it's a pretty obvious bootloop from watching the logcat content, and nothing new happens...) after flashing http://download.chainfire.eu/supersu-stable (2.65).
2. I have unlocked my bootloader and installed TWRP, so recovery and fastboot are functional. I didn't make a backup before flashing the zip and now I'm in a bootloop. How do I restore working Marshmallow? I assume I can either beg somebody to upload a TWRP backup for my H60-L04, or somehow flash the stock over what I have now. Can I simply use manual update from SD? Can I somehow flash Marshmallow again with fastboot? I'm too scared of bricking my device right now so I guess I'll brace myself for a few days without a phone until somebody helps me :/
I just flashed the Marshmallow release I had before the bootloop (I used Huawei Update Extractor and flashed boot, cust, system and recovery with fastboot; then open up Huawei recovery and factory reset for good measure, I'm not sure it was even needed) and the device is working. I'll restore my stuff, install TWRP, make a backup then try out your ZIP. Thanks
edit: thanks again - your zip works indeed. So after the initial hurdles, now I've got working root and a reasonable way of restoring in case I screw something up along the way.
Before making a new topic with the tutorial I have a few more questions.
First of all, why exactly we weren't supposed to update the rooted devices? I'm not currently interested in OTAs (it's pretty obvious that it needs a functional Huawei recovery, and you need to unroot cause an update can make a mess in a rooted system, making it bootloop for example), but can we flash extracted images with fastboot on rooted devices? Logically, we should be able to... How about sdcard update method?
Can we flash Marshmallow on Kitkat? (fastboot, sdcard, local update methods?) Or do we need to update to Lollipop along the way?
Can I flash stock roms in general (evenbetween different Android versions) by using fastboot with {boot, cust, recovery, system} images only? There's a lot of images that you can extract with Huawei Update Extractor - why there's so many if they're not needed?
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
Hello there.
I unlocked my bootloader a long while ago, then flashed TWRP on my TW U11+. Now recently I have seen that there's an update and I get the popup from my updater.apk on my HTC U11+.
My phone is on 1.24.709.7 update. And it's I think most definitely the ASIA_TW version.
Mid - 2Q4D10000
Cid - HTC__621
So I try to update but of course fail because my recovery was TWRP so of course that it did not work. Then I hear that you need to have stock recovery, so what I do is I get stock recovery.img, go to download mode and flash it through the command "flashboot flash recovery recovery.img. I get the success command and I reboot and try download the OTA once again, then I try to update it. It does go to stock recovery but then it "updates" til 25% and then it's stuck. Then after like 10 seconds it just simply gives my this Red Triangle with an exclamation mark in the middle of it. So I press power button and vol down to get off that mode and that's it. It won't update to the newest OTA.
I flashed 1.24.709.7 recovery at first. It didn't work then I flashed 1.24.709.8 recovery but still no avail.
Can you guys please help me? I really don't know what I am doing wrong.
Thanks in advance
I am having the exact same problem. I wish I had the HTC__621 recovery, but I haven't been able to find the correct one.
Hopefully somebody will see this. Every link that looks like the right thing is dead.
Same problem
I had the same problem, too.
But I find a way to update to 1.24.709.8.
That is: I decide to flash the 1.24.709.8 version's RUU .
Hope this can help you.
U11+ All TW version's image and OTA :
//drive.google.com/drive/folders/1kNE8rN8yUBPo9vux9G3CMvUzg3cg0lQ3
Thanks for the link.
However the problem that I'm experiencing is that whenever I flash either 1.24.709.7 or 1.24.709.8 RUU. It just won't flash over fastboot. So what I do is I put it on my SD card then put the file and rename it to like 2Q4DIMG.zip and go to recovery and still won't flash it correctly.
I'll try it again today to see what error code I get from it.
Did you unlocked or rooted your u11+?
Sorry for the late reply man.
My HTC u11plus is unlocked and I also have rooted my phone via magisk.
You can't update with official ota if unlocked, you need to relock and have the stock recovery. Relock will wipe your data I think
You can OTA with unlock, but you must run pure stock ROM. I RUU my phone and successfully apply the OTA.
Magisk did modify /boot partition so OTA wont apply with Magisk. You have to restore stock boot, OTA, then patch the boot again to preserve Magisk. Also if you use 3rd party recovery you have to restore the stock one.
All partition image can be found in the RUU with https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928 but you must make sure you flash the version match your current system. If not the only way might be RUU your phone.
I have also had the exact same issue with updating the latest OTA update. I have TW model, it was unlocked and rooted with magisk. I relocked bootloader, stock boot img and still the update wouldn't install. I even tried flashing 1.24.709.7 RUU in downloader mode but failed remote: 22 RU_HEADER_ERROR.
Would love any ideas or help.
*UPDATE*
Finally was able to update to 1.24.709.8 OTA. I needed up unlocking the bootloader again, then downloaded the 1.24.709.7 full image from
drive.google.com/drive/folders/1kNE8rN8yUBPo9vux9G3CMvUzg3cg0lQ3
Extracted the rar file and manually installed the boot, recovery and system images separately and rebooted. Downloaded the update and installed, everything worked sweet!!
xymopen said:
You can OTA with unlock, but you must run pure stock ROM. I RUU my phone and successfully apply the OTA.
Magisk did modify /boot partition so OTA wont apply with Magisk. You have to restore stock boot, OTA, then patch the boot again to preserve Magisk. Also if you use 3rd party recovery you have to restore the stock one.
All partition image can be found in the RUU with https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928 but you must make sure you flash the version match your current system. If not the only way might be RUU your phone.
Click to expand...
Click to collapse
Thank you very much for this. I will try this tomorrow or something.
I will post my results here.
Btw is there any update for Emea region? They did one a month ago for TW models and since then no words about Europe and Middle East
Does anyone have a link to 1.24.401.7 9.0_CL1010171 ? I'm trying to find stock recovery that matches with stock rom and can't find it anywhere.
Magisk and TWRP installed at the moment.
I've got stock boot.img backed up before installing Magisk but there was no way to boot (without flashing) TWRP in order to backup stock recovery that came with U11+.
Cheers
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
ichigodango said:
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
Click to expand...
Click to collapse
You can downgrade to 9 but you'll need to do a full wipe. Instead download the full factory image for the latest update and edit the flash-all batch file you'll find in it to remove the -w. Then run the batch file. You'll need to copy the boot.img file in the factory image to your device and then patch it with magisk to root. That patched image will need to be flashed to your device using fastboot from your pc.
I ran into the same issue as you when trying to update with the ota.
ichigodango said:
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
Click to expand...
Click to collapse
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
You should be able to flash the full factory image of either 9 or 10, but that will wipe your phone. Here is a link to a thread regarding downgrading from 10 to 9. That thread is for an XL, but it is still applicable.
https://forum.xda-developers.com/showpost.php?p=80206785&postcount=31
Complete flashing instructions are here: https://developers.google.com/android/images#instructions
You can flash the factory image without wiping your phone by editing flash-all.bat, and removing -w from the last line. That may not fix your problem, though. You may need a wipe to fix it.
Make sure to download the latest platform tools if you decide to flash. https://developer.android.com/studio/releases/platform-tools
I would not relock the bootloader. It may be impossible to recover from a bricked phone with a locked bootloader, and the relocking process may brick the phone. You must be on a stock image to relock the bootloader.
jd1639 said:
You can downgrade to 9 but you'll need to do a full wipe. Instead download the full factory image for the latest update and edit the flash-all batch file you'll find in it to remove the -w. Then run the batch file. You'll need to copy the boot.img file in the factory image to your device and then patch it with magisk to root. That patched image will need to be flashed to your device using fastboot from your pc.
I ran into the same issue as you when trying to update with the ota.
Click to expand...
Click to collapse
I managed to figure it out, updated ota and am now back on 9 with no problems I used flash-all without removing -w but didn't lose anything important so it's all good!
dcarvil said:
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
You should be able to flash the full factory image of either 9 or 10, but that will wipe your phone. Here is a link to a thread regarding downgrading from 10 to 9. That thread is for an XL, but it is still applicable.
https://forum.xda-developers.com/showpost.php?p=80206785&postcount=31
Complete flashing instructions are here: https://developers.google.com/android/images#instructions
You can flash the factory image without wiping your phone by editing flash-all.bat, and removing -w from the last line. That may not fix your problem, though. You may need a wipe to fix it.
Make sure to download the latest platform tools if you decide to flash. https://developer.android.com/studio/releases/platform-tools
I would not relock the bootloader. It may be impossible to recover from a bricked phone with a locked bootloader, and the relocking process may brick the phone. You must be on a stock image to relock the bootloader.
Click to expand...
Click to collapse
You're totally right that my problem had nothing to do with bootloader. I realised that by rooting with Magisk, the boot.img was modified, so I downloaded the image of the version that I had, extracted boot.img, flashed it to my phone, which got ota working.
I then updated ota to the latest Android 10 just in case, before flashing Android 9 followed by root - this was probabaly more complicated than necessary and I probabaly could have skipped the ota update, but everything is working as intended
dcarvil said:
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
Click to expand...
Click to collapse
What's the difference between this method and simply flashing the phone with the stock boot.img? I just flashed stock boot.img, got ota working on 10, updated, before downgrading to 9. Will I run into any issues because I didn't use Magisk's restore image?
ichigodango said:
What's the difference between this method and simply flashing the phone with the stock boot.img? I just flashed stock boot.img, got ota working on 10, updated, before downgrading to 9. Will I run into any issues because I didn't use Magisk's restore image?
Click to expand...
Click to collapse
Flashing the stock boot image removes root, so you must re-root the phone after updating. This method removes root from the active slot, but preserves it on the alternate slot. After the OTA root is restored from the alternate slot.
The end result is the same for both cases, but following the OTA procedure is simpler and faster.
dcarvil said:
Flashing the stock boot image removes root, so you must re-root the phone after updating. This method removes root from the active slot, but preserves it on the alternate slot. After the OTA root is restored from the alternate slot.
The end result is the same for both cases, but following the OTA procedure is simpler and faster.
Click to expand...
Click to collapse
That makes sense, thanks!
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.