Related
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?
Hey mates, here is a simple guide to root all your future updates that come for our beloved Mi A1.
Requirement
should have bootloader unlocked
some knowledge of fastboot mode
latest updatesupersu.zip in hand (can be downloaded from xda)
prerooted one system with flasfire installed
Stepwise guide to root new updated system
If anybody have old system rooted he can root new updated system very easily by using flashfire and super su recovery flashable file.
Steps are
1. Go to rooted old system. Install flashfire.
2. Download update supersu 2.82 sr4
3. Start flashfire and press instal zip and select supersu sr4
4. Select the system which you want to root and click ok
5. Now select boot option and select the system you want to boot after flashing (most likely updated system)
6. Press flash
7. Voila. Its done
8. You will boot into new rooted system
9. This will also apply for all future updates too.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Working great.
I tried and succeeded.
Looks really easy method even to root all future updates.
You are a genius
Thanks bro
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Please tell me what should I do next
I am now on September update which is on slot b
I went to fastboot and activated slot a and rooted using cf root and installed flashfire
In flashfire I selected Magisk 14.2 and flashed it on slot b
I rebooted
Right now I have the update prompt asking me whether to download and install the September update
What should I do?
Ex-Hunter said:
Please tell me what should I do next
I am now on September update which is on slot b
I went to fastboot and activated slot a and rooted using cf root and installed flashfire
In flashfire I selected Magisk 14.2 and flashed it on slot b
I rebooted
Right now I have the update prompt asking me whether to download and install the September update
What should I do?
Click to expand...
Click to collapse
make slot A active using fastboot
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
s0917 said:
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
Click to expand...
Click to collapse
I have personally checked supersu v2.82 sr4.
If you are facing bootloop go to old slot and flash supersu using flashfire
s0917 said:
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
Click to expand...
Click to collapse
Please get the logs and post them here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page372
The developer of Magisk is wanting logs so they can fix the A1.
s0917 said:
Got stuck in bootloop after flashing magisk 14.2 to new slot any idea why?
Click to expand...
Click to collapse
For how much time you have been in bootloop. Is bootanimation running.
I think after flashing root you have to wait for about 10 minutes before start of phone.
Otherwise do whatever op suggested.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
Mr.Crucial said:
For how much time you have been in bootloop. Is bootanimation running.
I think after flashing root you have to wait for about 10 minutes before start of phone.
Otherwise do whatever op suggested.
Click to expand...
Click to collapse
So my phone keeps rebooting on its own like
Vibrate then the "Lock your bootloader warning" then the bootanimtion * reboot
Mr.Crucial said:
For how much time you have been in bootloop. Is bootanimation running.
I think after flashing root you have to wait for about 10 minutes before start of phone.
Otherwise do whatever op suggested.
Click to expand...
Click to collapse
Confirmed: With Magisk 14.2 you get stuck in a bootloop.
Ex-Hunter said:
Confirmed: With Magisk 14.2 you get stuck in a bootloop.
Click to expand...
Click to collapse
Can you help submit the log? I'm having trouble getting the log files.
Desire 1007 said:
Go to fastboot mode.Enter command in ur pc fastboot set active b or a (which will have old firmware)and boot it.Root your old slot containing august security patch using old cf root and install flashfire
in flashfire load the latest magusk or supersu (which you can download from google)(recovery flashable),select new slot and click flash.
Thats all you get your phone rooted with september security patch.
Click to expand...
Click to collapse
By your guide, you mean, In fastboot active august slot, & boot it. root it using cf root method.
then load flashfire & flash supersu on slot september, then reboot.
Will the phone automatically boot the september slot, or do we have to go again in fastboot, & set active september slot ?
osrox said:
By your guide, you mean, In fastboot active august slot, & boot it. root it using cf root method.
then load flashfire & flash supersu on slot september, then reboot.
Will the phone automatically boot the september slot, or do we have to go again in fastboot, & set active september slot ?
Click to expand...
Click to collapse
There are two methods
1. you have to set active system in fastboot
2.Before flashing ,cluck reboot and select updated slot
s0917 said:
Can you help submit the log? I'm having trouble getting the log files.
Click to expand...
Click to collapse
Me too. I'm not able to get any logs
Deleted
Hi, can i relock bootloader after root?
Harry Tang said:
Hi, can i relock bootloader after root?
Click to expand...
Click to collapse
Why you want to relock
You should not relock device after rooting as it can bootloop.
Still if you wish, then try it
Can any one help me ?
How to make slot B active ?
rex28818 said:
Can any one help me ?
How to make slot B active ?
Click to expand...
Click to collapse
Put your phone in fastboot mode and send command from pc
fastboot set_active b
I am rooted now.. Can I enable camera 2 api?? Someone please confirm
WARNING:
Please do every preparation that could fix your phone to original state before doing this trick.
DOING THIS MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
I managed to unpack the official firmware of Nokia 7 and 8, and patched their boot.img with SuperSU Systemless Root.
But I don't know if it works on them.
Patched boot.img can be downloaded at:
https://mega.nz/#F!igsBmarT!3rIjD4ZaZN8ueOTVmciGwg
Here's the method you need to do:
1. Install OST LA and patch it, and OPEN IT FROM INSTALLATION DIRECTORY DIRECTLY.
2. Flash required firmware before proceed. If you don't do that, you won't be able to access Wi-Fi after the boot.img flashed.
For Nokia 7, you need to use the firmware "C1N-0430-0-00CN-B05" which I haven't released to public for some reason.
For Nokia 8, you need to use the firmware "NB1-435J-0-00WW-B01" which released in this topic: https://forum.xda-developers.com/showthread.php?t=3678487
If you've already flashed required firmware before proceed, you can skip this part.
Click to expand...
Click to collapse
3. Use the Service Purposed Bootloader trick I've mentioned in the Nokia 6 Root Guide: https://forum.xda-developers.com/showthread.php?t=3702354
4. Type these commands:
Code:
fastboot-android flash boot_a E:\NB1-435J-Boot-Patched.img
fastboot-android flash boot_b E:\NB1-435J-Boot-Patched.img
fastboot-android reboot
For Nokia 7, use C1N-0430-Boot-Patched.img instead. I've attached the Firehose, rawprogram0 and patch0 for Nokia 7 in case you want to use EDL Mode on Nokia 7.
Click to expand...
Click to collapse
5. If it's accepted by the system, the phone will reboot twice, and you'll see SuperSU appeared.
However, if "Verification Failed" appeared on your phone, then the trick failed. You have to flash original firmware to restore your phone to factory state.
If anyone know how to fix that in boot.img, that's a breakthrough of Nokia Android Devices.
You may want to use Flashfire to flash Xposed Framework or something else, but DO NOT RECEIVE ANY OTA UPDATES after your phone rooted.
I'm looking forward to a boot.img manual patcher on PC or Phone available, which could patch boot.img to achieve Systemless Root either SuperSU or Magisk and bypass Verification Boot.
This looks exciting. I have to look deeper into recovery options before I dare this kind of experiment...
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Click to expand...
Click to collapse
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
hikari_calyx said:
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
Click to expand...
Click to collapse
Nope. SuperSU said "Root not available"
Many thanks for your efforts on this patch, I would love to be able to root my Nokia 8.
Having an unlocked bootloader I am not really worried about, but having root access is a big feature for me.
Any chance this patch will become available to firmware version 00WW_4_390 which is the current latest? (And what my phone is currently running)
Not sure if I can downgrade it to NB1-435J-0-00WW-B01 or not, but I can try that if it is not able to be patched to the latest firmware image.
Thnx hikari_calyx for your hard work!
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
Click to expand...
Click to collapse
Did anyone else but ansoncleung tried this meanwhile?
@hikari_calyx I have a self prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
2WildFirE said:
@hikari_calyx I have a prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
Click to expand...
Click to collapse
Log
Op please pm me i am developer too we can do this together.
TheKsM said:
Op please pm me i am developer too we can do this together.
Click to expand...
Click to collapse
Hey we need developers here on Nokia!
And what we need to is a dev who build twrp for Nokia8. The recovery is inside the boot. IMG.
If you want build a one for the community. Thanks
Powered by Nokia 8
ASUS still blacklisting phones with unlocked&relocked bootloader (no OTA updates)?
I read that was the case with previous iterations of ZenFones. Apparently phones that had their bootloader unlocked can't receive OTA updates, even if the bootloader has been relocked. But what about now? Is it the same for the Zenfone 7 series?
Also if anyone wants to relock their bootloader, for whatever reason, it's the same command as the one for the ROG Phone III. Big thanks to @THEHOLYG0D and @IDunnoLookatXDA https://forum.xda-developers.com/asus-rog-phone-3/help/relock-bootloader-t4152057
Code:
fastboot oem asus-lock
However... WARNING!
I did this command and my Zenfone 7 Pro was completely bricked, until I applied an update via SD card. That was the only thing that worked. "Apply update via ADB" just didn't work, neither did flashing boot.img, system.img and others one by one... So re-lock the bootloader, AT YOUR OWN RISK!
I think this is still the case. There was an OTA released 30th September and it still hasn't come through to my phone so I am now downloading it from the ASUS website.
What's the best procedure for applying an update downloaded from the Asus website?
- EDIT- Never mind, found the answer. Copy the .zip to the root of the phones internal storage and reboot
Minotaur said:
What's the best procedure for applying an update downloaded from the Asus website?
- EDIT- Never mind, found the answer. Copy the .zip to the root of the phones internal storage and reboot
Click to expand...
Click to collapse
Are you stock? Wouldn't recommend this process if you have TWRP & magisk installed.
Here is the process I followed:
Flash rom update from within TWRP, don't reboot.
Flash TWRP - both A & B slots.
Reboot recovery.
Flash Magisk.
Reboot system.
crumble6 said:
Are you stock? Wouldn't recommend this process if you have TWRP & magisk installed.
Here is the process I followed:
Flash rom update from within TWRP, don't reboot.
Flash TWRP - both A & B slots.
Reboot recovery.
Flash Magisk.
Reboot system.
Click to expand...
Click to collapse
Ahhhh so just flash the downloaded zip from twrp? Don't need to extract anything from it?
Minotaur said:
Ahhhh so just flash the downloaded zip from twrp? Don't need to extract anything from it?
Click to expand...
Click to collapse
Yep just flash it, no need to do anything else. Make sure you have latest version of TWRP if using an OTA, but for full zip from website any version should work.
I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)