i rooted my deviced. Used systemless root. in the hope OTA would work when a update arrived.
Now there is a update but.... it says the update fails. (in dutch).
I used supersu unroot, but it still says update failed.
I tried using the MDM tools as here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91996
... but that is giving a bogus cannot connect to internet message (I think it just means that there is no server for the g4 phone, internet is fine and fast on phone and pc)
I want the update but Now i am stuck:
-I do not want to re-lock the phone
-I do want the update. (euret -> may to juli security update)
Questions:
-Are there any meaning full error messages.. anywhere?
-are there other ways to flash the OTA?
-I see flashing stock should work. But is my unrooted rom different from stock?
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
Edit: and maybe logo.bin when you had removed the unlocked warning
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
downloading XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip now.
is only option anyway because after trying to flash supersu it won't boot anyway. (but still boots into fastboot mode.. no brick yet)
thx
have you used xposed? or custom kernel?
Bender1987 said:
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
Thank you for this information Bender. I was wondering the exact same thing. I am rooted on a Moto G4 and i was wondering if a OTA update, or reflashing stock would wipe my data + all installed apps.
If i do it your way it shouldn't be any concerns?
srgudhka said:
have you used xposed? or custom kernel?
Click to expand...
Click to collapse
no only supersu and modified hosts file with adaway (main reason for root is titanium backup)
flashed boot, recovery and system with
Code:
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
system boots now with all user data intact in may 2016 update.
However system update nows says it is up to date. .... maybe they retracted the update temporary? ... patience.... (reteu).
@leuk_he
I have a RETEU version here in germany and download the XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip file, which had the same build no as my g4+.
If you try to flash files from the wrong rom, you get an error while flashing or lost temporary your WiFi and IMEI till you find and flash the right one.
So compare the build no on your phone and the stock rom file.
@Zajbot
As long as you don't wipe cache or data or use fastboot erase userdata, all your data should be there.
I have done the same yesterday and all data is still on my phone
---------- Post added at 13:16 ---------- Previous post was at 13:11 ----------
You don't need the OEM fb_mode_set.
Try it again in few hours or reboot, the update should pop-up again, don't worry.
Wifi and imei info are correct(NL) I checked the XT1642_ATHENE from the bootloader screen (did not know this number)
but... patience is a hard one.... :crying::crying: ... and if people say "don't worry... i worry..." bad habit.
Build number accorindg to phoneinfo is MPJ24.139-48 ... but i think that is what i just flashed. Not sure if that is what was in the phone before.
i added the oemset becuase it cried about wrong signature on boot.img it still did afterwards.
@leuk_he
Then you have maybe the wrong ROM. I flashed boot recovery and system and had no errors. But my build no. matches before the update.
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
How does the sideload works?
Thanks
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Bender1987 said:
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Click to expand...
Click to collapse
Didn't work for me. I get the bootloadermenu and when I switched to RECOVERY I got the ANDROID-Picture with "No Command".
Flashing a new recovery.img don't change anything.
Is a sideload flah with adb possible?
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Bender1987 said:
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Click to expand...
Click to collapse
I think there is a problem with my recovery. I flashed the recovery from rom-zip
Edit: get the recovery
Edit 2.: Give up, get with my and yours OTA.zip a sideload mistake (number 7). Now I wait for the next OTA, next days will be hard without ROOT
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Bender1987 said:
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Click to expand...
Click to collapse
thanks for your hint, I start it tomorrow, have a good night
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
SoNic67 said:
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
Click to expand...
Click to collapse
I haven't flash the TWRP, I always boot by mfastboot to TWRP
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
Tried sideloading with twrp , but it gave error 7 on build number. "this device has . "
thx anyway for sharing.
I will now try load older system images with older build number.
/edit:
Flashed MJP-..23 like bender and it now says a update is availble.
interesting side note. when using the build-48 it already showed battery indicator on motowake screen but still at may-2016 security update.
Related
Greetings -
I have an unlocked TF700 (twrp v 2.5.0.0) and I was running cromi-x. it began to crash a lot so i tried to flash a new rom and i must've done something wrong because now the tablet will not boot up. I can get into twrp and perform the options listed (install, backup, restore, wipe, mount, settings, advanced, reboot) but nothing seems to help. I haven't played with this in probably 6 months so i'm not sure where to start. Navigating these forums is like reading latin to me. I'm sure there is an explanation for this but I can't find it. Can some one link me to an existing thread if this has been discusses previously or help me out? I can't seem to get anything working on this and it's driving me crazy. I know I need to provide extra information to help identify this issue but i'm not sure what that info that is. Any help would be appreciated!
Also, I've tried a factory reset from twrp as well and it gives me the following messages
E:unable to mount '/external_sdcard
Updating partition details...
E:Mount: Unable to find partition, for path '/'
When I reboot following this, it takes me directly to TWRP.
I'm guessing my tablet can't find my SD card? Maybe that's an easy fix?
Thanks everyone for looking at this and thanks for anyone that takes some time to educate me.
Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.
berndblb said:
Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.
Click to expand...
Click to collapse
Thank you for the reply. My bootloader is "<1.00 e> released by 10.6.1.14.8-20130514"
It also says "key driver not found" immediately before the bootloader data upon turn on
Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?
berndblb said:
Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?
Click to expand...
Click to collapse
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.
Hoggs17 said:
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.
Click to expand...
Click to collapse
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.
berndblb said:
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.
Click to expand...
Click to collapse
When i enter the bootloader, it stays on the screen. If i reboot without entering the bootloader, it goes directly into TWRP. I am not sure if i used the wipe data option or the factory reset (it has been probably 6 months). I will install fastboot on my PC now.
Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.0?
berndblb said:
Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.5?
Click to expand...
Click to collapse
Correct, i don't need any data on this tablet; i can wipe it clean. I think the last thing i flashed was Cromi-X (not sure the number; was back in August probably. My TWRP is 2.5.0.0; i haven't updated that one. I will try to do the fast stuff tomorrow morning; too late tonight. Thanks for all your help.
Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow
berndblb said:
Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow
Click to expand...
Click to collapse
I have installed the fastboot on my PC, ran it figured out my serial number as well. I will wait for your next instruction so that I don't mess anything up (again).
Hoggs17 said:
I have installed the fastboot on my PC. I will wait for your next instruction so that I don't mess anything up (again).
Click to expand...
Click to collapse
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891
das chaos said:
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself
Hoggs17 said:
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself
Click to expand...
Click to collapse
Ok, here's my thinking:
I don't know why the tablet reboots to recovery if you try to boot Android - never seen that before.
That it refuses to boot the rom - seen that plenty
That it only boots to recovery and not even to the bootloader - seen that quite a few times if the user used Wipe Data or factory reset from settings.
You seem to a have a mix of both which makes it unique.
So my advice is:
to clear the misc partition (where a "format data" request may still be lurking) in fastboot
wipe the data partition in fastboot - just general housekeeping
flash a new bootloader and recovery using your current recovery
Use the new recovery to flash the rom of your choice - which one do you have in mind?
So let's start. First make sure you have a fastboot connection:
Code:
fastboot devices
Then erase misc and user data
Code:
fastboot erase misc
fastboot erase userdata
You are still in the bootloader menu, push the Vol Up button on the flashing RCK to enter recovery
Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom
Good luck!
"Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom"
I have successfully completed the steps preceeding the above suggestions; I am not sure how to flash the bootloader. I am trying to follow the guide posted here (http://forum.xda-developers.com/showthread.php?t=2688891) by using the command code
fastboot -i 0x0B05 flash recovery twrp.blob
however, i cannot rename my blob file (contained in the 10.6.1.14.10 bootloader "second zip from the bottom" that you linked me to) to twrp.blob. it is simply called blob. am I doing this wrong? i tried using the above command with just blob and it didn't do anything.
on another thread (http://forum.xda-developers.com/showthread.php?t=2688891) you recommend visiting (http://techerrata.com/browse/twrp2/tf700t) and downloading the latest version of twrp. Should I download this file (openrecovery-twrp-2.8.5.0-tf700t.blob) and rename this to twrp.blob?
Also I am not sure on a new custom rom; i've been out of the game for a while; any suggestions?
No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...
berndblb said:
No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...
Click to expand...
Click to collapse
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...
Hoggs17 said:
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...
Click to expand...
Click to collapse
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external
berndblb said:
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external
Click to expand...
Click to collapse
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.
Hoggs17 said:
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.
Click to expand...
Click to collapse
..... which means the file got corrupted during download or copy to the card.
That's what signature verification is for.
Download it again.
The issue I am having is that my honor 8 (FRD-L14) is stuck on "your device is booting now.." and it does not shut down. If I hold the power button until it shuts down then it restarts by itself and it keep doing the same thing over and over.
When it first starts and the blue screen and the logo come up the phone vibrate twice and then it displays "your device is booting now..." and it gets stuck there
Here is what I can and cant do:
I can go into fastboot and it shows that the phone is unlocked and the FRP is unlocked
I can flash TWRP from there and I can go into TWRP
When I check in TWRP for partitions I can see CUST or DATA and it shows that the INTERNAL STORAGE size is ZERO
I was able to create the system partition but I am not sure if I did it right.
the dload folder on the SD Card has the role back but the three finger thing (vol+ and vol- and power does not start the system restore from update.app) instead it gets stuck on " your device is booting now..."
I tried Huawei_Multi-Tool and I chose the "unbrick option"...I extracted system.img, boot.img, recovery.img and cust.img and the tool was able to push all images to the device but still the device does not start.
The original stock recovery is not accessible either even if I flash the stock recovery image from TWRP
Any tips on how to resolve this?
Thanks in advance guys
fidzi_1981 said:
The issue I am having is that my honor 8 (FRD-L14) is stuck on "your device is booting now.." and it does not shut down. If I hold the power button until it shuts down then it restarts by itself and it keep doing the same thing over and over.
When it first starts and the blue screen and the logo come up the phone vibrate twice and then it displays "your device is booting now..." and it gets stuck there
Here is what I can and cant do:
I can go into fastboot and it shows that the phone is unlocked and the FRP is unlocked
I can flash TWRP from there and I can go into TWRP
When I check in TWRP for partitions I can see CUST or DATA and it shows that the INTERNAL STORAGE size is ZERO
I was able to create the system partition but I am not sure if I did it right.
the dload folder on the SD Card has the role back but the three finger thing (vol+ and vol- and power does not start the system restore from update.app) instead it gets stuck on " your device is booting now..."
I tried Huawei_Multi-Tool and I chose the "unbrick option"...I extracted system.img, boot.img, recovery.img and cust.img and the tool was able to push all images to the device but still the device does not start.
The original stock recovery is not accessible either even if I flash the stock recovery image from TWRP
Any tips on how to resolve this?
Thanks in advance guys
Click to expand...
Click to collapse
You said you can go into TWRP right. Just rebrand the device to L19 :angel:
First format data
Then flash the rebrand.zip
Then reboot and if it doesn't boot first go into recovery and factory reset then let it boot up again.
Try flashing stock recovery.img using fastboot. Can you now enter into the 3-button combination mode?
wasiq224 said:
Try flashing stock recovery.img using fastboot. Can you now enter into the 3-button combination mode?
Click to expand...
Click to collapse
He said he tried to enter recovery with no luck, and he also tried the 3 button dload method.
wasiq224 said:
Try flashing stock recovery.img using fastboot. Can you now enter into the 3-button combination mode?
Click to expand...
Click to collapse
I tried flashing the stock recovery but it does not work. I also tried the 3-buttons and it did not work either
when I go into TWRP it shows that the size of the internal storage is ZERO
damenbm said:
You said you can go into TWRP right. Just rebrand the device to L19 :angel:
First format data
Then flash the rebrand.zip
Then reboot and if it doesn't boot first go into recovery and factory reset then let it boot up again.
Click to expand...
Click to collapse
Where can I find the rebrand.zip file?
Here are the full instructions :victory:
https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
damenbm said:
Here are the full instructions :victory:
https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
Click to expand...
Click to collapse
Thanks. I will give it a try and flash it and see if it can re-create the missing partitions :fingers-crossed::fingers-crossed:
fidzi_1981 said:
Thanks. I will give it a try and flash it and see if it can re-create the missing partitions :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Best of luck :angel: let me know how it goes please!
damenbm said:
He said he tried to enter recovery with no luck, and he also tried the 3 button dload method.
Click to expand...
Click to collapse
Yes, but he tried the dload method before flashing stock recovery, and he was flashing stock recovery using twrp rather than fastboot.
Thanks but I tried dload after I flashed the stock recovery.
And I tried flashing the stock recovery using facebook and twrp and neither ways succeeded
fidzi_1981 said:
Thanks but I tried dload after I flashed the stock recovery.
And I tried flashing the stock recovery using facebook and twrp and neither ways succeeded
Click to expand...
Click to collapse
Did the rebrand work? Did it make you go back to stock?
damenbm said:
Did the rebrand work? Did it make you go back to stock?
Click to expand...
Click to collapse
Not yet. I'm at work. I'll give it a go tonight
For me it worked after trying to get my FRD-L09 back to work again after I couldnt flash system and not boot anywhere but twrp.
Thanks for the help!
fidzi_1981 said:
Not yet. I'm at work. I'll give it a go tonight
Click to expand...
Click to collapse
I had the same exact issue 5 days ago.
Here's what I did to solve it
NOTE - This is FRD-L14 SPECIFIC
First, Download these files -
1) FRD-L04 Original Recoveries and Boot Image
2) FRD-04 Rollback Package from Huawei
3) FRD-L04 Official MM ROM from Huawei
4) FRD-L14 Specific Stock MM ROM Update.zip
Assuming Bootloader is unlocked
Here's what you should do
-Unzip the Recoveries and Boot image folder
-Unzip Rollback Package
-Make a folder called "dload" (without the quotes) in the root of your SD Card
-Place the Update.app from the Rollback Package in there
-Make sure you have ADB and Fastboot installed - Installer
-Boot into fastboot by Plugging in your USB Cable and Holding Power + Volume Down. This may take multiple tries and multiple reboots to get it right depending on the reboot loop.
-Once phone is in Fastboot, go into the Recoveries and Boot folder, hold Shift and right Click. Click on open Command Window Here.
-If the option says "Powershell" instead, open Command prompt manually, and cd to that directory, or change this option in your settings.
-With command prompt open, do -
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery2 recovery2.img
Code:
fastboot flash boot boot.img
IMPORTANT - Make sure you unplug the cable from the phone and are ready to press both volume buttons at the same time after it reboots
If you dont get it the first time,hold all 3 buttons at the same time to make it reboot and go into that mode.
Code:
fastboot reboot
-Remove cable, press both Buttons at the same time
-It should go into stock recovery and start flashing the Rollback package
-Wait for it to finish, it should reboot automatically
-After it reboots, you should notice that it went back to the same state it was, so reboot into fastboot and flash recovery, recovery2, and the boot image again.
-This time, put the Update.app from the Official L04 Rom you downloaded from the Huawei website in the "dload" folder of the SDCard
-Fastboot Reboot, Remove cable, and Press buttons again. This time it will flash the Official ROM, so it will take longer.
-If it says error right at 99%, reboot, it flashed correctly but it displays an error.
-If it says error anytime before the end of flash, reboot and try again.-After it reboots, you will notice you are able to boot again. BUT, you are not able to update due to it being branded as L04, sooooo
-Place the Update.app from the 4th link (L14 Specific ROM) in the "dload" folder of SD Card
-Three button method into the recovery flash again.
-It will start to flash the L14 Specific ROM on top of the L04 one.
-After it flashes it and reboots, reboot one more time once you are inside android so it encrypts the ROM.
-(Optional) Update to Nougat, apply other updates after that (There's like 3 Updates I think)
-At this point you have a 100% Stock FRD-L14 Honor 8 but, you can also
-(Optional) Reunlock Bootloader
-Profit?
JvaOneShotzXprX said:
I had the same exact issue 5 days ago.
Here's what I did to solve it
NOTE - This is FRD-L14 SPECIFIC
First, Download these files -
1) FRD-L04 Original Recoveries and Boot Image
2) FRD-04 Rollback Package from Huawei
3) FRD-L04 Official MM ROM from Huawei
4) FRD-L14 Specific Stock MM ROM Update.zip
Assuming Bootloader is unlocked
Here's what you should do
-Unzip the Recoveries and Boot image folder
-Unzip Rollback Package
-Make a folder called "dload" (without the quotes) in the root of your SD Card
-Place the Update.app from the Rollback Package in there
-Make sure you have ADB and Fastboot installed - Installer
-Boot into fastboot by Plugging in your USB Cable and Holding Power + Volume Down. This may take multiple tries and multiple reboots to get it right depending on the reboot loop.
-Once phone is in Fastboot, go into the Recoveries and Boot folder, hold Shift and right Click. Click on open Command Window Here.
-If the option says "Powershell" instead, open Command prompt manually, and cd to that directory, or change this option in your settings.
-With command prompt open, do -
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery2 recovery2.img
Code:
fastboot flash boot boot.img
IMPORTANT - Make sure you unplug the cable from the phone and are ready to press both volume buttons at the same time after it reboots
If you dont get it the first time,hold all 3 buttons at the same time to make it reboot and go into that mode.
Code:
fastboot reboot
-Remove cable, press both Buttons at the same time
-It should go into stock recovery and start flashing the Rollback package
-Wait for it to finish, it should reboot automatically
-After it reboots, you should notice that it went back to the same state it was, so reboot into fastboot and flash recovery, recovery2, and the boot image again.
-This time, put the Update.app from the Official L04 Rom you downloaded from the Huawei website in the "dload" folder of the SDCard
-Fastboot Reboot, Remove cable, and Press buttons again. This time it will flash the Official ROM, so it will take longer.
-If it says error right at 99%, reboot, it flashed correctly but it displays an error.
-If it says error anytime before the end of flash, reboot and try again.-After it reboots, you will notice you are able to boot again. BUT, you are not able to update due to it being branded as L04, sooooo
-Place the Update.app from the 4th link (L14 Specific ROM) in the "dload" folder of SD Card
-Three button method into the recovery flash again.
-It will start to flash the L14 Specific ROM on top of the L04 one.
-After it flashes it and reboots, reboot one more time once you are inside android so it encrypts the ROM.
-(Optional) Update to Nougat, apply other updates after that (There's like 3 Updates I think)
-At this point you have a 100% Stock FRD-L14 Honor 8 but, you can also
-(Optional) Reunlock Bootloader
-Profit?
Click to expand...
Click to collapse
Thanks! i will give this a try since flashing the rebranding zip file that was suggested in one of the posts did not work out for me.
However, do you think that this w=method will work despite the fact that I do not have a valid DATA or CUST partitions?
Thanks again for responding to my post!!
fidzi_1981 said:
Thanks! i will give this a try since flashing the rebranding zip file that was suggested in one of the posts did not work out for me.
However, do you think that this w=method will work despite the fact that I do not have a valid DATA or CUST partitions?
Thanks again for responding to my post!!
Click to expand...
Click to collapse
No problem!
That shouldn't matter, this will get you to 100% stock, so all of those partitions will be reflashed.
JvaOneShotzXprX said:
No problem!
That shouldn't matter, this will get you to 100% stock, so all of those partitions will be reflashed.
Click to expand...
Click to collapse
It worked!!!
Thanks a lot!
but this is what happened:
After i flashed recovery, recovery2 and boot images, I rebooted the phone and it went straight to stock recovery and it asked me download stock firmware and stock recovery which was 1.66GB so I allowed and it downloaded it and flashed everything and did a reset and the phone booted normally.
The stock firmware that it downloaded and flashed was B122 MM.
One question though, does the flashing sequence of the recovery, recovery2 and boot matter?
Before you posted your post, I had tried flashing these three files in the following order: boot, then recovery then recovery2 but it never worked.
Also, the three images that tried to flash were extracted from the update.app from this firmware (FRD-L14C567B162_FULL) so I was not sure what was going wrong.
Thanks again for your help!! :victory::good::highfive:
fidzi_1981 said:
It worked!!!
Thanks a lot!
but this is what happened:
After i flashed recovery, recovery2 and boot images, I rebooted the phone and it went straight to stock recovery and it asked me download stock firmware and stock recovery which was 1.66GB so I allowed and it downloaded it and flashed everything and did a reset and the phone booted normally.
The stock firmware that it downloaded and flashed was B122 MM.
One question though, does the flashing sequence of the recovery, recovery2 and boot matter?
Before you posted your post, I had tried flashing these three files in the following order: boot, then recovery then recovery2 but it never worked.
Also, the three images that tried to flash were extracted from the update.app from this firmware (FRD-L14C567B162_FULL) so I was not sure what was going wrong.
Thanks again for your help!! :victory::good::highfive:
Click to expand...
Click to collapse
It shouldn't matter, but I included it because sometimes those get corrupted like what happened to me. I'll probably be testing it out completely and making a guide. Looks like you had it better than I did though! I'm glad you got it fixed! :highfive:
JvaOneShotzXprX said:
It shouldn't matter, but I included it because sometimes those get corrupted like what happened to me. I'll probably be testing it out completely and making a guide. Looks like you had it better than I did though! I'm glad you got it fixed! :highfive:
Click to expand...
Click to collapse
Thanks for the help again. I would not have been able to rescue the phone without your tips. :good::highfive:
So I have and Unlocked bootloader, TWRP for Android Oreo, and Root. I did a backup of the existing system but like an idiot when I was clearing the DAVLIK and User space I also formated the MicroSD and subsequently my backup.
I tried following the different guides to reload the base system but I'm not having any luck I must have done something royally wrong but at this point I don't even care if I revert back to stock I just want something other then the endless boot loop that is currently my reality.
I've tried downloading the update.zip files from http://pro-teammt.ru/firmware-database/ but the images are not posting properly when I try from TWRP or Fastboot. I tried reverting the recovery back to stock and trying to use OpenKirin and again no luck. Can someone point to the proper firmware with what ever recovery.img, kernal ramdisk.img, and or system.img I need to extract.
I'm missing something or am I using old guides with newer software release.
Thanks in Advance
Okay so I finally figured out why I was receiving errors when I tried to extract the kernel.img, system.img, and recovery.img from the update.app files in Huawei Update Extractor. Apparently Huawei turned off CRC checks on the newer files and once they are disabled in the settings they images open up fine. Going to try and flash a build with fastboot.
Process I'm going to undertake to try and restore the system.img for my MHA-L29C567 device. Currently my Bootloader is Unlocked, and I am able to access Fastboot&Rescue Mode so I intend on manually updating the MHA-L29C567B367 (8.0.0.367) Update using Fastboot.
1) Go to http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C567&firmware_page=0 and Download MHA-L29C567B367 (8.0.0.367) Update.zip
2) Unzip/decompress update.zip and use HuaweiUpdateExtractor_0.9.9.5 with CRC checks turned off in setting to avoid error opening Update.app.
3) Extract System.img and Kernel.img and apply to phone using following commands in windows command terminal with Phone in Fastboot&Rescue Mode (Hold Power and Volume Down)
fastboot flash system SYSTEM.img
fastboot flash kernel Kernel.img
4) Reboot phone with command fastboot reboot
5) Wipe DAVLIK User Space and cross my fingers it boots.
smtelegadis said:
Process I'm going to undertake to try and restore the system.img for my MHA-L29C567 device. Currently my Bootloader is Unlocked, and I am able to access Fastboot&Rescue Mode so I intend on manually updating the MHA-L29C567B367 (8.0.0.367) Update using Fastboot.
1) Go to http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C567&firmware_page=0 and Download MHA-L29C567B367 (8.0.0.367) Update.zip
2) Unzip/decompress update.zip and use HuaweiUpdateExtractor_0.9.9.5 with CRC checks turned off in setting to avoid error opening Update.app.
3) Extract System.img and Kernel.img and apply to phone using following commands in windows command terminal with Phone in Fastboot&Rescue Mode (Hold Power and Volume Down)
fastboot flash system SYSTEM.img
fastboot flash kernel Kernel.img
4) Reboot phone with command fastboot reboot
5) Wipe DAVLIK User Space and cross my fingers it boots.
Click to expand...
Click to collapse
That didn't work so I reapplied TWRP and tried to apply the update.zip file and that did not work either. Having a hard time of things at this point just need to take a break for tonight.
So I'm getting an error message with the following when I try to update using the MHA-L29C636B368 (8.0.0.368) rom:
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update package from zip failed. Screenshot attached or link below:
https://photos.app.goo.gl/VGbh86ddthsU8kdt8
From what I've read in other forum post is that repairing the system partition can fix this. I used the Wipe>Advance Wipe [toggled "System"]>Repair or Change File System>Repair File System. I also tried to format the partition and again no change. I know the partition is not toggled read only and I even did that and reverted just to see if it was not presenting properly. Can't figure out what is going on here. Would really appreciate some advice. I rebooted into recovery after each attempt.
Thanks in Advance
So I followed the thread in this forum for how to downgrade back to nougat and now I have my phone running again. In the process of resetting the system and updating back to EMUI 8 now.
Device will be wiped if your bootloader isn't already unlocked.
Obviously, before doing this, you should enable OEM unlocking and ADB debugging in Developer Options. Also you should have ADB and Fastboot on your system (meaning they work on any directory). I use this version, just accept the installation of both the ADB/Fastboot drivers and the Google Device Drivers and you should be good to go.
Below you can find the untouched boot.img for the version you are on (or you can extract them yourselves, guide at the bottom of the thread):
2018:
March (V9.5.9.0.ODHMIFA) (OTA)
April (V9.5.10.0.ODHMIFA) (OTA)
May (V9.5.11.0.ODHMIFA) (OTA)
June (V9.6.2.0.ODHMIFE) (OTA)
June (V9.6.3.0.ODHMIFE) (OTA)
July (V9.6.4.0.ODHMIFE) (OTA)
August (V9.6.5.0.ODHMIFE) (OTA)
September (V9.6.6.0.ODHMIFE) (OTA)
October (V9.6.7.0.ODHMIFE) (OTA)
November (V9.6.8.0.ODHMIFE) (OTA)
December (V10.0.3.0.ODHMIFE) (OTA)
2019:
January (V10.0.4.0.ODHMIFE) (OTA)
January (V10.0.4.0.PDHMIXM) (OTA)
February (V10.0.5.0.PDHMIXM) (OTA)
March (V10.0.7.0.PDHMIXM) (OTA)
April (V10.0.8.0.PDHMIXM) (OTA)
May (V10.0.9.0.PDHMIXM) (OTA)
June (V10.0.10.0.PDHMIXM) (OTA)
July (V10.0.11.0.PDHMIXM) (OTA)
August (V10.0.12.0.PDHMIXM) (OTA)
September (V10.0.13.0.PDHMIXM) (OTA)
October (V10.0.14.0.PDHMIXM) (OTA)
November (V10.0.15.0.PDHMIXM) (OTA)
December (V10.0.16.0.PDHMIXM) (OTA)
Here we go:
GENERATING THE PATCHED BOOT.IMG
0. Download a suitable UNTOUCHED boot.img from above or extract one yourself by using the OTA links and dumping the image using the guide on the bottom of this thread.
To check which one is suitable for you go to Settings -> System -> About phone and check your build number. (e.g September 2019 one should be PKQ1.180917.001.V10.0.13.0.PDHMIXM)
1. Install Magisk Manager
2. Open the app and press Install on the prompt (It should prompt you to install the latest version).
3. Tap on Install on the prompt and then "Patch Boot Image File".
4. Select the untouched boot.img through your File Explorer. Wait for it to do its thing.
The patched_boot.img was created and it should be located at /storage/emulated/0/Download/patched_boot.img.
UNLOCKING THE BOOTLOADER
1. Move the patched_boot.img to your PC
2. Connect the device to your computer and open a Command Prompt
3. Check that ADB works with:
Code:
adb devices
Should say:
Code:
XXXXXXXXXXXX device
where the X's are a unique ID.
4. Boot into fastboot mode with:
Code:
adb reboot bootloader
(Yes you can obviously boot into bootloader by using Volume Down+Power Button etc)
5. You should be in fastboot mode. Check that it works properly:
Code:
fastboot devices
Should say:
Code:
XXXXXXXXXXXX fastboot
The device will be wiped after the next step.
6. Now we are going to unlock the device's bootloader with:
Code:
fastboot oem unlock
7. At this point the device is unlocked. Now do:
Code:
fastboot reboot
And let the phone boot
8. After booting, go into fastboot mode again with:
Code:
adb reboot bootloader
BOOTING INTO THE PATCHED IMAGE AND INSTALLATION
You should now be in fastboot mode from the last section.
1. Boot into the patched_boot.img that you generated earlier with:
Code:
fastboot boot patched_boot.img
The phone should boot normally and shouldn't take too long. For me it was the same boot time as always.
2. Now open Magisk Manager and press Install
3. When prompted tap onto Install and then choose "Direct Install (Recommended)"
Let it do its thing and then choose Reboot.
You should now have a rooted phone with Magisk without using TWRP.
Do not relock your bootloader or your device probably won't boot because you are rooted.
PAYLOAD DUMPING
Requirements: python3, protobuf (do python -m pip install protobuf after having installed python3)
1. Download the desired OTA (full OTA needed, not incremental ones, should probably be 1GB+)
2. Download the zip of the python script on github
3. Extract the script (both .py's) and inside the folder extract the payload.bin from the OTA archive
4. Now run:
Code:
python payload_dumper.py payload.bin
Wait for it to be done and you should have all the images in the same directory. With those, you can either just use the boot.img or even create a fastboot flashable OTA with a script.
Cheers!
Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Update: I have done it, I could not generate my own patched image, so I had to use the one in the provided post. I still opted to install magisk beta instead of the normal one and there was no problem, now I'm rooted. Thanks again.
---------- Post added at 05:22 AM ---------- Previous post was at 05:21 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
clau1996 said:
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
Click to expand...
Click to collapse
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.
sipollo said:
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.
Click to expand...
Click to collapse
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk
I guess I should have included that if you boot into any recovery after doing the "bypass" procedure, the device will get wiped, as mentioned by the rest of you guys.
This "guide" is only if you don't intend to ever use TWRP or something similar. Anyway, will add it to the OP, sorry if anyone got screwed up because I didn't mention it.
sgloki77 said:
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I guess if someone wants to start off with a new install it's better and faster to just boot into TWRP and flash Magisk as you just said.
Guide is mainly targetted to people who don't want to wipe for whatever reason (whether that is data or anything).
clau1996 said:
Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.
Click to expand...
Click to collapse
The resulting image should actually be a .img (or a .img.tar if you choose so in the settings) ?
Maybe you didn't look in the correct directory for the image (?)
Double check, because I did this procedure twice on my device and it worked that way.
Thanks for using the guide btw!
EDIT: whoops, should have merged with the other reply..
Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?
fernoct said:
Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?
Click to expand...
Click to collapse
I suppose it should be possible but I guess I will have to test it on the next OTA we get just to be sure.
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.
michkost858 said:
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.
Click to expand...
Click to collapse
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader
lord bim said:
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader
Click to expand...
Click to collapse
Oh, yes it does. By the way, just to clarify; it's not a problem, it's a safety measure which Xiaomi implemented on the May Update and on. Otherwise your data would be at risk and easy to steal.
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
Yes, nothing special about it
lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
After unlocking bootloader with vol- trick, if you want i uploaded last Fastboot Rom with a modified script.
You won't lose data and your bootloader will remain unlocked.
A Backup is strongly recommended (just in case).
Use Miflash.
https://1drv.ms/u/s!AnNVEh3KeCSVj94TW6xkP6Xj-CDeRg
lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
ProchyGaming said:
Yes, nothing special about it
Click to expand...
Click to collapse
I would recommend generating your own if possible.
Not sure if there's a difference tbh, however I think that, that one was patched for 16.0 and not 16.7 which makes it freeze up sometimes during boot.
thanks to all the valuable inputs the op and other have given here, so conclusion in you can install magisk without wiping data by this method, but your data will be erased the next time you boot into recovery. Also, one cannot be sure about otas as ota might trigger recovery for some stuff and then the data will be wiped. The only viable option is to just backup your data, either by titanium backup after installing magisk like mentioned in the op or just manually save necessary stuff somewhere, permanently unlock, flash twrp and then flash magisk.
One question though, why do we need to update Magisk into the beta version? Now that we have 17.0 is it necessary?
There's a method on Magisk to let you to revert boot and apply OTA, and install root again.
This method applied to most Moto phones.
1. Check for update. Settings >>> System >>> update.
2. If you found a new version available, go to Magisk and "uninstall" and revert to original boot.
3. Install OTA system update. DO NOT REBOOT!
4. Go back to Magisk and install on "unused partition". Reboot when finished
If there's an error "unable to revert", you need to get ROM matched the build number, and get the boot.img, copy the boot to the phone and let Magisk "install and patch". This method will give an original boot to revert, and run step 2 again.
If the method above didn't work, you need to do the following.
1. Assume you have original boot and updated boot. Reboot in fastbootd (only for models shipped with Android Q, R, S) or bootloader (shipped with Android P or earlier)
Code:
fastboot reboot fastboot
or
Code:
adb reboot fastboot
2. From there, you can flash original boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot into command window, and press enter.
Reboot when finished
3. Install OTA, and hopefully you have updated boot with matched build number. When OTA installation finished, copy updated boot to the phone and patch it with Magisk, and copy back to host computer, and reboot.
4. Once the phone finished post update, reboot to fastbootd
Code:
adb reboot fastboot
, and flash patched boot.
Done
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
noobtoob said:
Wish it would have worked. After reverting to stock boot it still wouldn't install. Had to LMSA the phone and then patch and fastboot the patched image. *sigh*
Regardless, this may work for others, but my phone was jacked up after reverting to stock boot.
Click to expand...
Click to collapse
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing.
gullzway said:
I've never had success trying to revert Magisk, update with OTA, then restoring Magisk.
I've tried before on my Z3 Play and Moto G Stylus.
I just don't do updates anymore and don't have to mess with it. Seems like these days updates just block things I want to do anyway, like Screen2Auto working and hotspot bypassing
Click to expand...
Click to collapse
Well, fastest method for me was:
1. Boot to twrp>backup data. Copy backup off phone.
2. Update phone from LMSA.
3. Follow previous root guide to patch the boot.img (extract from LMSA folder on computer).
4. Fastboot flash the patched boot image.
5. Boot to twrp>copy backup to twrp folder on device>restore data.
You don't have to setup your phone for any of this.
Edit: Obviously you have to setup your phone to install magisk and patch the boot.img. I mean minimal, like skipping all the account .