Database Users

Instruction for TWRP, rooting and updating T-Mobile G5 H830

Hi,
If this is the wrong place, please move it.
I'm new to LG G5. Bought from eBay with a modified ROM H83020i_un. Below are the steps I took to root this device and upgrade it to the latest stock Android 7 ROM
Notes about rebooting into recovery
1. Power off device.
2. Hold power and vol down button.
3. Wait until lg logo appears.
4. Release power button only for one second while continuing to hold vol down. After the second elapsed press and hold the power button until it boots into recovery.
Click to expand...
Click to collapse
Notes
NEVER use Settings -> factory reset. It will end up in TWRP loop
If you ended up in TWRP loop, never wipe misc partition. It will result in MAC Address changes every time you reboot . The correct method is [FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)
1. Install 20a. This is the last version I can install TWRP and root. Instruction is [STOCK][N][ARB01] H830 20A ROM + Flashable ZIPs + IMGs + KDZ. I used LG UP method and this is fairly painless
2. Unlock the bootloader, install TWRP and root. Instructions are now with TWRP!. However, the adb posted in the link can't ever trigger the Allow USB Debug prompt on the phone. I wasted 2 hours on trying all kinds of combination of settings. Eventually, I download version 1.4.3 Minimal ADB and Fastboot Tool and it worked as expected. I flashed SuperSU. And formatted the data to disable encryption. Now I have 20a with TWRP and root
3. Upgrade to the latest (20m as of now). Instructions for 20k is [STOCK][N][ARB01] H830 20k ZIPs + IMGs + KDZ (2017-07-01 Security Patch), following Install via TWRP Directions -> Stock ROOTED. I had to do quite a bit reading to make sure the correct step (keep TWRP and root).
autoprime's post https://forum.xda-developers.com/showpost.php?p=72537357&postcount=21
recovery-from-boot.p is contained in the system partition and returns any time you flash a stock system.img (such as my COMPLETE zip).. so if you were on, for example, 20f and then renamed/deleted recovery-from-boot.p.. and then flash 20i COMPLETE zip.. you would have to rename/delete the file again... and when you flash the next update you'll have to do it again etc. The reason I leave this file inside the system file is because I'm providing 100% stock images so users can go back to 100% stock or mod/customize things to their liking.
Click to expand...
Click to collapse
There is also another advice from him in https://forum.xda-developers.com/showpost.php?p=73343155&postcount=40
am now suggesting people wipe cache after flashing my COMPLETE zip but before they flash a root zip. This may help with the random people who seem to lose TWRP after flashing Magisk/SuperSU.
Complete zip -> wipe cache -> flash root zip -> finished
Click to expand...
Click to collapse
So I followed the TWRP stock rooted step. Wipe cache -> flash complete zip -> wipe cache -> flash SuperSU zip -> Mount system -> File Manger rename /system/recovery-from-boot.p to /system/recovery-from-boot.p.bak. Reboot (no need to format data)
To get into TWRP, you would need to boot into recovery, and choose Yes twice (it won't reset your device)
4. Disable OTA update as it will break my phone.
The instruction is in LG G5 ALL-IN-ONE THREAD in the section of "Disable OTAs". I've also found another method which was posted for G4 but the menu is also available in G5 at https://www.androidexplained.com/lg-g4-disable-ota-updates/
Hidden Menu Method
Launch the Dialer Application
Enter the Following Code to Access the Hidden Menu. . .
277634#*#
. . .Then Scroll Down and Tap on ‘WiFi Test’
Tap on the ‘OTA Setting’ Option
Then Tap on the Big ‘Disable’ Button
Reboot the LG G4
Click to expand...
Click to collapse
It contains some other methods but none worked on non-root devices.
On rooted device, I can find LG Update Center and FOTA and disabled them.
However, Google Play Service still show the notification for Android System Update. The only option is to disable notification from it.
Hopefully, this is helpful

[DEC 2017 to JAN 2018 Update] How I updated successfully

UPDATE:
In the thread @Pianobeats and @Telperion have successfully updated with less steps.
They flashed the newest Jan update flash-all without removing Magisk, Kernel, or TWRP. This eliminates the need to flash the current security update you are on and reduces the number of steps dramatically.
Clarification:
In the factory image zip you'll drill down through the files until you find flash-all.
Open that in a text editor.
Near the end you'll find "-w"
Delete it and save the flash-all.
This will make it so the update does not wipe your device.
_______________________​
I felt adventurous and decided to try updating.
I updated to latest adb & fastboot from here: SDK Platform Tools Release Notes
At first I tried using the Magisk Uninstaller Zip; it did not work.
In bootloader, I used the DEC 2017 flash-all (-w removed). This worked to get me out of the bootloader and Magisk was uninstalled.
I recommend just uninstalling Magisk from the app.
EDIT: On my second Pixel 2 ( I have two), uninstalling Magisk from the app did not work.
It stuck me into the same error in the bootloader as my first phone.
Flash-all (-w removed) worked to return me to the system.
No need to flash stock boot or dtbo.
In cmd window:
Code:
adb devices
Verify serial number (working adb & fastboot)
Code:
adb reboot bootloader
Cycle through to recovery.
Once in recovery hold PWR and press volume up once
Volume down to highlight "Apply update from ADB"
Code:
adb sideload <walleye-ota-opm1.171019.013.zip>
NOTE: Go to the where you saved the OTA zip "walleye-ota-opm1.171019.013". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: adb sideload and *Ctrl +v* to paste (Much easier)​
I rebooted to bootloader; I verified the change from boot slot b to boot slot a.
After boot > Notification: Android System - "Finishing Android Update..."
System is sluggish. Probable background processes.
Code:
adb reboot
Significantly longer reboot at Google Icon with Progress bar than normal (about 4 full minutes)
Code:
adb reboot bootloader
Code:
fastboot boot "twrp-3.2.1-0-walleye.img"
NOTE: Go to the where you saved the OTA zip "twrp-3.2.1-0-walleye.img". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: fastboot boot and *Ctrl +v* to paste (Much easier)​
TWRP > Install > twrp-pixel2-installer-walleye-3.2.1-0.ZIP
Wipe cache > Reboot system
Code:
adb reboot recovery
TWRP > Install > Snoke R1
Wipe cache > Reboot system
Code:
adb reboot recovery
TWRP > Install > Magisk V15.2
Wipe cache > Reboot system
After reboot > "Android is starting" for a half second
NOTES:​
Magisk = V15.2
ctsProfile: true
basicIntegrity: true
(Screen shot attached)
Viper4Android 2.5.0.4 = Installed and Processing properly (Screen shot attached)
Magisk Notification > DTBO Patched, please reboot > "Android System internal problem pop up"
(No, this does not affect anything.)
Also, this proves that even after mounting /system via TWRP OTAs are still usable.
NOTES #2:​
I have two Pixel 2 phones.
One for work and one for personal.
I performed the above on my personal, though havrt not had the time to update my work phone.
An OTA pushed to your device will not work on phones that have TWRP, Magisk, custom Kernel.
Screen shots attached.

Diesel_Jeremiah said:
I felt adventurous and decided to try updating.
I updated to latest adb & fastboot from here: SDK Platform Tools Release Notes
At first I tried using the Magisk Uninstaller Zip; it did not work.
In bootloader, I used the DEC 2017 flash-all (-w removed). This worked to get me out of the bootloader and Magisk was uninstalled.
I recommend just uninstalling Magisk from the app.
In cmd window:
Verify serial number (working adb & fastboot)
Cycle through to recovery.
Once in recovery hold PWR and press volume up once
Volume down to highlight "Apply update from ADB"
NOTE: Go to the where you saved the OTA zip "walleye-ota-opm1.171019.013". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: adb sideload and *Ctrl +v* to paste (Much easier)
I rebooted to bootloader; changed from boot slot b to boot slot a
After boot > Notification: Android System - "Finishing Android Update..."
System is sluggish. Probable background processes.
Significantly longer reboot at Google Icon with Progress bar than normal (about 4 full minutes)
NOTE: Go to the where you saved the OTA zip "twrp-3.2.1-0-walleye.img". On the top menu you should see "copy path" or alternatively you can right click > properties > Location. Copy that string (IE "C:\Users\you\desktop\...")
Type: fastboot boot and *Ctrl +v* to paste (Much easier)
TWRP > Install > twrp-pixel2-installer-walleye-3.2.1-0.ZIP
Wipe cache > Reboot system
TWRP > Install > Snoke R1
Wipe cache > Reboot system
TWRP > Install > Magisk V15.2
Wipe cache > Reboot system
After reboot > "Android is starting" for a half second
NOTES:
Magisk = V15.2
ctsProfile: true
basicIntegrity: true
(Screen shot attached)
Viper4Android 2.5.0.4 = Installed and Processing properly (Screen shot attached)
Magisk Notification > DTBO Patched, please reboot > "Android System internal problem pop up"
(No, this does not affect anything.)
Also, this proves that even after mounting /system via TWRP OTAs are still usable.
Click to expand...
Click to collapse
Are you on a Verizon branded one? Or Google Store came unlocked?

Google unlocked with Verizon SIM.
Sent from my Pixel 2 using Tapatalk

Thanks a ton for this tutorial. This is my first Google device and I'm really worried that I'm going to mess something up. I came from an HTC 10 which seemed so much easier to navigate around and flash on. I plan on using your method tomorrow morning once I have all of the related files downloaded and some quality time to spare.
I have the same set up as you. Google bought with a Verizon Sim. I currently have TWRP and Magisk 15.2 installed so I think your instructions should apply to me perfectly.
Thanks again.

jascolli said:
Thanks a ton for this tutorial. This is my first Google device and I'm really worried that I'm going to mess something up. I came from an HTC 10 which seemed so much easier to navigate around and flash on. I plan on using your method tomorrow morning once I have all of the related files downloaded and some quality time to spare.
I have the same set up as you. Google bought with a Verizon Sim. I currently have TWRP and Magisk 15.2 installed so I think your instructions should apply to me perfectly.
Thanks again.
Click to expand...
Click to collapse
Best thing to do is download the factory image and remove -w from flash-all. (removing -w keeps your device from wiping)
This gives you something to fall back on if all else fails.
Ensure you use the flash-all for your current build & security patch.
Sent from my Pixel 2 using Tapatalk

Diesel_Jeremiah said:
Best thing to do is download the factory image and remove -w from flash-all. (removing -w keeps your device from wiping)
This gives you something to fall back on if all else fails.
Ensure you use the flash-all for your current build & security patch.
Click to expand...
Click to collapse
Does flashing the factory image replace the kernel too?

doublej713 said:
Does flashing the factory image replace the kernel too?
Click to expand...
Click to collapse
Yes.
Sent from my Pixel 2 using Tapatalk

Diesel_Jeremiah said:
Yes.
Click to expand...
Click to collapse
If I flash-all with the -w included, is that basically a factory reset? Also, does that flash both slots and/or do you need to flash both slots?

doublej713 said:
If I flash-all with the -w included, is that basically a factory reset? Also, does that flash both slots and/or do you need to flash both slots?
Click to expand...
Click to collapse
Yes, if you do not remove the -w, it will reset your device.
It flashes both slots A & B.
Sent from my Pixel 2 using Tapatalk

Diesel_Jeremiah said:
Yes, if you do not remove the -w, it will reset your device.
It flashes both slots A & B.
Click to expand...
Click to collapse
Last question, if I'm willing to lose all my data, can I just flash the latest factory image? This is my first pixel device, and while all of this seems the same as other phones, the terminology seems to be a little different.

doublej713 said:
Last question, if I'm willing to lose all my data, can I just flash the latest factory image? This is my first pixel device, and while all of this seems the same as other phones, the terminology seems to be a little different.
Click to expand...
Click to collapse
Yes
Sent from my [device_name] using XDA-Developers Legacy app

Edited original post with Note #2.
OTAs will not work on modified phones.
Screenshots added.

I'm kind of new so here are some questions.
So the first step is essentially getting rid of Magisk by flashing the December patch by using the "flash-all.bat" batch file, right? This is essentially unrooting your phone.
Then you sideloaded the January OTA. But it says that you switched from Boot Slot B to Boot Slot A. Is there a reason for that?
Also is Snoke R1 a custom kernel? If we're not installing a custom kernel we just skip that step right?
Sorry for all the questions. You're the only person who actually made a proper guide. Thanks!

Pianobeats said:
I'm kind of new so here are some questions.
Click to expand...
Click to collapse
Welcome, and questions are always ok.
Pianobeats said:
So the first step is essentially getting rid of Magisk by flashing the December patch by using the "flash-all.bat" batch file, right? This is essentially unrooting your phone.
Click to expand...
Click to collapse
You are mostly correct. OTA cannot verify the system with Magisk installed. OTA cannot install without the stock recovery.
Flash-all is returning your system boot & dtbo, and returning the stock recovery.
This must happen so when the new OTA verifies the system it will meet all of the checks.
Pianobeats said:
Then you sideloaded the January OTA. But it says that you switched from Boot Slot B to Boot Slot A. Is there a reason for that?
Click to expand...
Click to collapse
I will update the OP to say I verified the boot slot switched.
Before you start, your phone will be on Boot slot B or slot A.
Google improved the OTA system; there are two boot slots. When the OTA is installed, it installs first on the non-booting slot. Once it's complete, your phone switches the boot slot until the next OTA it will switch again. So, it will go A to B, or B to A, depending on the current slot. This makes the transition to new OTA easier and faster.
Pianobeats said:
Also is Snoke R1 a custom kernel? If we're not installing a custom kernel we just skip that step right?
Click to expand...
Click to collapse
The Snoke kernel is a custom kernel. R1 is the build for 8.1
If you do not want a custom kernel, yes you will skip it.
Alternatively, you will have to use Magisk patched boot method with the Stock boot image.
Look here if that's what you want to do: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Steps and process are the same for patching the stock boot.
Pianobeats said:
Sorry for all the questions. You're the only person who actually made a proper guide. Thanks!
Click to expand...
Click to collapse
:good:

Diesel_Jeremiah said:
Welcome, and questions are always ok.
You are mostly correct. OTA cannot verify the system with Magisk installed. OTA cannot install without the stock recovery.
Flash-all is returning your system boot & dtbo, and returning the stock recovery.
This must happen so when the new OTA verifies the system it will meet all of the checks.
I will update the OP to say I verified the boot slot switched.
Before you start, your phone will be on Boot slot B or slot A.
Google improved the OTA system; there are two boot slots. When the OTA is installed, it installs first on the non-booting slot. Once it's complete, your phone switches the boot slot until the next OTA it will switch again. So, it will go A to B, or B to A, depending on the current slot. This makes the transition to new OTA easier and faster.
The Snoke kernel is a custom kernel. R1 is the build for 8.1
If you do not want a custom kernel, yes you will skip it.
Alternatively, you will have to use Magisk patched boot method with the Stock boot image.
Look here if that's what you want to do: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Steps and process are the same for patching the stock boot.
:good:
Click to expand...
Click to collapse
I am on december version, what if i download january factory image and flash this with flash-all (without -W) on my pixel 2? I am rooted , no twrp and using flash kernel.
Is this important to flash december factory image again before flashing updating to newer one ?
I want to keep my data and settings.
Billion THX for your great help, i am really learning a lot here.

Daandofreak said:
I am on december version, what if i download january factory image and flash this with flash-all (without -W) on my pixel 2? I am rooted , no twrp and using flash kernel.
Is this important to flash december factory image again before flashing updating to newer one ?
I want to keep my data and settings.
Billion THX for your great help, i am really learning a lot here.
Click to expand...
Click to collapse
I did not try to go straight to the JAN update. I needed to use flash-all to restore stock recovery because of TWRP.
Safest:
Either flash the DEC from flash-all (without -w) or fastboot flash boot & dtbo.
Then you should be successful updating from DEC to JAN.
Guinea pig:
Flash the JAN flash-all (without -w) and see what happens.
I have not tried this (because TWRP).
Removing the -w in the factory image keeps data and settings.
OTAs will keep data and settings.
OTAs are the best way to update.

If you're going to flash a factory image, you're better off just flashing the January factory image (sans -w) and getting it all done in one step. That's the method I used, and it worked just fine and kept my data intact. OTA's are flashed with ADB commands from the stock recovery, factory images are flashed through the bootloader, so TWRP doesn't interfere at all.
You'll of course still need to boot the TWRP and flash the TWRP zip afterwards, but the preceding steps are much easier.

Telperion said:
If you're going to flash a factory image, you're better off just flashing the January factory image (sans -w) and getting it all done in one step. That's the method I used, and it worked just fine and kept my data intact. OTA's are flashed with ADB commands from the stock recovery, factory images are flashed through the bootloader, so TWRP doesn't interfere at all.
You'll of course still need to boot TWRP and re-flash the zip afterwards, but the preceding steps are much easier.
Click to expand...
Click to collapse
So your saying: Flash Jan factory image (-w removed) on top of Dec will not require removal of TWRP and won't break anything?

Diesel_Jeremiah said:
So your saying: Flash Jan factory image (-w removed) on top of Dec will not require removal of TWRP and won't break anything?
Click to expand...
Click to collapse
Correct.
The recovery is part of the boot image, so the only time you'd need to remove TWRP is if you're trying to flash something that requires the stock recovery. OTA's require the stock recovery; factory system images don't, they flash a stock boot and dtbo as part of the flashing process.
The one caveat is that for Verizon users, there may be a possibility that flashing a factory image complete with updated bootloader may re-lock the bootloader on them. But for everyone else, it's fine. Even the Verizon users could just extract the factory image and flash the components in the script, minus the bootloader:
Code:
[STRIKE]fastboot flash bootloader bootloader-walleye-mw8998-002.0066.00.img[/STRIKE]
[STRIKE]fastboot reboot bootloader[/STRIKE]
fastboot flash radio radio-walleye-g8998-00164-1710262031.img
fastboot reboot bootloader
fastboot update image-walleye-opm1.171019.013.zip

Can someone explain in more detail how to remove the "w" from the factory image? TIA

Foolproof way for OTA-update with Magisk installed

Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?

Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.

Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me

Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?

Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?

I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..

_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?

Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.

Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.

https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?

Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....

Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern

This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk​
Restore Images​
Start OTA update
Downlowd​
Step1​
Step2​
Go Back to Magisk
Install to 2nd slot​
Reboot​
It was working ... very easy!

I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.

I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong

quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse

freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.

[Solved] Can´t update from version 5.1.2 to version 5.1.4 OnePlus5

So i tried to install the update for my OnePlus5 but TWRP gives ERROR 7 i also tried to wipe my data (including system),
i also tried to install the update with the stock recovery (without root) and the update just fails
oxygen updater won´t work aswell
thanks in advance
i´ve trieded newer versions of oxygen os too
sry for my bad english i am german

Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.

Alexandre-P said:
Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.
Click to expand...
Click to collapse
i used the OTA before but i will try the OTA you suggested
thanks in advanced:good:
Edit: can i theoretically use a newer version than 5.1.4?

Fredwuz said:
Edit: can i theoretically use a newer version than 5.1.4?
Click to expand...
Click to collapse
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.

Alexandre-P said:
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.
Click to expand...
Click to collapse
so i flashed version 5.1.3 and it did work but when i tried to flash to version 5.1.4 TWRP was stuck in "Patching system image unconditionally..." did i do something wrong?
After i flashed to 5.1.3 the devices worked normal as always

Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.

Alexandre-P said:
Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.
Click to expand...
Click to collapse
now the updater says my system is up-to-date but i only have 5.1.3 installed

Fredwuz said:
now the updater says my system is up-to-date but i only have 5.1.3 installed
Click to expand...
Click to collapse
Reboot, wait some time.

What is sometime are about 5 hours enough?
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
What is sometime are about 5 hours enough?
Click to expand...
Click to collapse
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.

strongst said:
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.
Click to expand...
Click to collapse
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Edit: I have to use version 5.1.4 or?
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Click to expand...
Click to collapse
Yes you can, that's what I suggested already

My experience with the 5.1.4 update - ERROR 7 & Treble error fix
Hi, I have 3 OnePlus 5's in my household and I have gotten them all to update to 5.1.4, then 5.1.5, then 5.1.6+ with this method.
(5.1.4 and then 5.1.5 is needed before flashing 5.1.6 or greater).
In my experience, no matter what caches I cleared or what recoveries I had used, 5.1.4 was not flashable on all three devices with the bootloader unlocked. If you have the patience and time, this method should 99.99% work for you if done correctly (leaving a 0.01% chance of failure just in case it does fail lol but that shouldn't happen.)
1.) Firstly, back up your device. I suggest doing this by making a full titanium backup, and copying all the files on the internal storage to a folder on your computer.
This may take a while to copy. In my experience, the fastest way to copy all the data off to the computer is to boot the device into TWRP recovery, plug a good USB C cable in to the device and to the PC's USB port, unlock the device in TWRP (put in the password/pattern to decrypt and mount the data partition [Ignorable if you dont set a password on the device]), and use the adb pull command to pull the files off the device. I found that ADB pull works much faster than an mtp file transfer in windows explorer.
Steps for ADB pull:
Ensure adb is installed on the computer with adb drivers. For Windows, open command prompt or powershell as admin. Type in adb devices and hit enter. If your OnePlus device comes up, then all is good. Use the command (without the square brackets):
[ adb pull /sdcard "XXX/." ]
Replace XXX with a directory on your computer (for example, you can do [ adb pull /sdcard "C:\Users\YOURUSERNAME\Desktop\OnePlus/." ]
If anyone notices any issues with this command please let me know so I can update the post. I am writing this off memory, so there may be minor mistakes.
2.) After your device backs up and you're happy with the backup (i.e. everything you need backed-up is saved off of the phone onto the computer), It's time to relock the bootloader and restore the firmware on the phone.
I haven't tried a simple fastboot OEM relock command, so I cannot say whether that is sufficient enough.
What I did was follow this thread:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Download the Driver and the Oxygen version.
Once downloaded, extract the driver Driver_OnePlus5.zip file to its own folder. Extract the firmware to its own folder (cheeseburger_23_O.13_170803).
3.) Using the firmware restoring tool to relock the bootloader and restore the device to factory firmware condition.
Now:
Turn off your OnePlus 5 device.
Hold volume up key.
Plug USB cable in to the PC and the Type-C side to the device. Make sure only volume up is held whilst you do this.
Open device manager and check for missing drivers/driver issues. If the driver isn't detected, use device manager to browse for the extracted Driver_OnePlus5 folder you made earlier.
The LED light on the OnePlus 5 should be yellow if I can remember correctly.
Open msm download tool as an adminstrator (right click, run as administrator)
Click the start button on the top left of the msm download tool. (If nothing happens, make sure drivers are installed properly and that the device is in download mode [Repeat the above steps])
If successful, one of the "Device Type" should show your device connected {com device} and the download process and time row will update. Wait for the download progress to finish. The device will reboot on its own when completed. The status should turn green and say done/finished (If I remember correctly).
When your device reboots, do a quick setup. Don't bother putting your google account in or restoring anything if you plan on unlocking the bootloader later for TWRP or other reasons.
Unlocking the bootloader will wipe the phone. For now, just focus on the updates.
Connect the device to Wi-Fi. I found one of the devices I used this method on wouldn't connect to Wi-Fi (modem issue or something). Luckily, I had the 5.1.4 update already downloaded on the computer so I copied the update to the root folder on the device and used the local upgrade option in the OTA update options (in the phone system update settings). Updating the firmware fixed my Wi-Fi issue.
Basically, just do the OTA updates as you would normally. Start with 5.1.4, then you can do the 5.1.5. Do not jump to 5.1.7 because OnePlus only just added treble support in 5.14/5.15 releases so it is important do do those in order first. If you can, do 5.1.4, 5.1.5, 5.1.6 and then 5.1.7 in order. Just follow the updates that the OTA screen allows you to take.
Notes for the Pie update:
I haven't had issues installing Pie with the bootloader unlocked, so if you wish to stay on oreo for now and update later with an unlocked bootloader, that should be fine.
If your bootloader is locked, and you're on at least OOS 5.1.5, you should be able to flash the Pie OTA with the stock recovery without issues.
If you encounter issues installing Pie, and your bootloader is unlocked follow this:​
Unlocked bootloader - Pie Update - Removing compatibility.zip from firmware archive:​
Method 1: Pre-Removed compatibility.zip modified firmwares:
For STABLE:​Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Download " OxygenOS 9.0.0 Full Zip (modified, without compatibility.zip) ".
For BETA:​Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Download " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
Copy the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) " to the device.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
Wipe dalvik-cache and cache.
Enjoy Pie.
Method 2: Manual Method to remove compatibility.zip for unlocked bootloaders:
Download the FULL firmware OTA (from device settings, or from the OnePlus website).
Copy the firmware to the computer (If downloaded on the device, it will be in the ".ota" folder. Else, it is available on the OnePlus firmware downloads page.
Open the firmware archive with 7-Zip.
Delete Compatibility.zip from the archive.
Copy the now-modified firmware back to the device.
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash your manually-modified OTA/firmware archive in TWRP.
Wipe dalvik-cache and cache.
Enjoy Pie.
DO NOT use winrar or any other non-recommended programs to remove compatibility.zip. I found that winrar causes treble errors or error 7.
4.) Re-unlocking the bootloader & Restoring your data.
Once you've installed 5.1.5 or greater, you can now safely go into developer settings and enable oem unlocking, and then reboot to the bootloader to unlock the bootloader (which will wipe/erase the phone data but keep the version to whatever you updated it to). You may then proceed to install TWRP, magisk if you plan on restoring with titaniumbackup, and restore all your sd card contents (or the sd card contents that you need) back from the computer backup the the device (I usually use ADB Push whilst booted in TWRP recovery because it copies quicker than MTP).
Updates should work from now on ( I was able to install android PIE Beta with the bootloader unlocked [See the Pie notes above]. Only had issues with the 5.14 / 5.15 updates with the bootloader unlocked ).
Hope this helps. If anyone has any more information, or questions about this method, do share. Like I said earlier, if done correctly, this method should definitely work for you guys.

Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Glad you got it working! Happy new year to you as well

November 2019 Security Patch is now available!

88.4 MB
No major changes.

For my 6/128 the Nov 2019 update is 93.9MB which installed successfully. I did not have any bootloop issues caused by previous updates either.

My 4gb_64gb model (india) shows update size of 93.9mb

again and again.
adaptive brightness bug is still there.
cannot go lower than 19% when it is on.
I heard the rumor that android Q for mia2 will be released in the end of November or early December.
Is this true?
I hope they fix the brightness bug in Q.

Yes ,when Android 10 will be available for the mi a2 ?, android one device from Xiaomi seems quite slow to get it...

jrcbm13 said:
again and again.
adaptive brightness bug is still there.
cannot go lower than 19% when it is on.
I heard the rumor that android Q for mia2 will be released in the end of November or early December.
Is this true?
I hope they fix the brightness bug in Q.
Click to expand...
Click to collapse
Where did you heard the rumor

...deleted as being incomplete ...

Stock and patched (Magisk 20.1) /boot partition images for v10.0.17.0 PDIMIXM zipped and attached (got OTA 10.0.15.0 -> 10.0.17.0)
Note that IMHO most safe procedure for those with Magisk-rooted phone is:
0. Become "developer" and disable automatic updates (IMHO THIS IS IMPORTANT, even if you have not rooted phone).
.....
Check for an OTA available, and if yes, immediately pause it (going to Options -> System -> Advanced -> System Updates [not sure for terms because previous is backward-translation from localized menu]).
1. MagiskManager -> UNINSTALL -> RESTORE IMAGES
2. Reboot (to have "clean stock" state) (IMHO THIS IS IMPORTANT, reboot before OTA even if you have not rooted phone);
3. Start OTA download and then installation (going to Options -> System -> Advanced -> System Updates);
reboot;
4. Download from here (or somewhere else or pull yourself via ADB/TWRP to PC) stock /boot partition image, and copy it to /Downloads;
5. Prepare for rooting and receiving next OTAs (IMHO THIS IS IMPORTANT):
<MagiskManager -> Install Magisk -> Select and Patch a File> (i.e. boot image), -
(copy of stock boot image is archived by MagiskManager in /data partition root for step (1) with next OTA)
6. Copy patched boot image from /Downloads back to PC (or download it from here or somewhere)
(MagiskManager makes file "magisk_patched.img", I usually rename it "patched_boot..img")
7. "fastboot boot patched_boot.img" - this is done to check that everything has succeeded in previous steps
(IMHO THIS IS much SAFER than "fastboot flash patched_boot.img")
8. If booting succeeded and phone works with temporary root OK, restore permanent root: MagiskManager -> Install Magisk -> Direct Install

Front flash is OK at last.

alperdemir32 said:
Front flash is OK at last.
Click to expand...
Click to collapse
Good find, thank you.
In my case it was also necessary to clear data and cache of the camera app for it to work correctly.

Aerobatic said:
Stock and patched (Magisk 20.1) /boot partition images for v10.0.17.0 PDIMIXM zipped and attached (got OTA 10.0.15.0 -> 10.0.17.0)
Click to expand...
Click to collapse
Hi Aerobatic, I recently reverted back to *13* fresh install. Is *17* one that you recommend? If so how to migrate from *13* to *17* (unlocked bootloader, not rooted)? Currently my Mi A2 is showing an OTA Security update available for September 2019 @ 69.5 mb.

nadia p. said:
Hi Aerobatic, I recently reverted back to *13* fresh install. Is *17* one that you recommend? If so how to migrate from *13* to *17* (unlocked bootloader, not rooted)? Currently my Mi A2 is showing an OTA Security update available for September 2019 @ 69.5 mb.
Click to expand...
Click to collapse
First update to September update, after that you receive October/November update.
Sent from my Mi A2 using Tapatalk

tomgv said:
First update to September update, after that you receive October/November update.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Hi tomgv, Aerobatic advised not to install both October 2019 updates, I assume due to stability issues. Do you know if one update is dependent on another (e.g. 13->14, 14->15, 15->16, etc.? or are the updates accumulative (e.g. 13->17? One would assume if accumulative, one would need to download and install it manually vs. OTA.

Updated without any glitches. No bootloops.

nadia p. said:
Hi tomgv, Aerobatic advised not to install both October 2019 updates, I assume due to stability issues. Do you know if one update is dependent on another (e.g. 13->14, 14->15, 15->16, etc.? or are the updates accumulative (e.g. 13->17? One would assume if accumulative, one would need to download and install it manually vs. OTA.
Click to expand...
Click to collapse
The problematic October update is removed from server, you will install fixed version via ota.
Sent from my Mi A2 using Tapatalk

Thanks guys! I proceeded to install the September 2019 update then it directly went to the November 2019 update an bypassed October all together. So far everything seems OK, nothing to report at this time.

official fastboot November
10.0.17
http://bigota.d.miui.com/V10.0.17.0.PDIMIXM/jasmine_global_images_V10.0.17.0.PDIMIXM_20191108.0000.00_9.0_94629a1855.tgz

I had the version 10.0.0.15 (yes it had bootloop) just now received the ota and installed it. It works now no bootloops anymore its on 10.0.0.17!
Just did a test restarted and works! Yess phone back to normal (i hope)

****oonn said:
official fastboot November
10.0.17
http://bigota.d.miui.com/V10.0.17.0.PDIMIXM/jasmine_global_images_V10.0.17.0.PDIMIXM_20191108.0000.00_9.0_94629a1855.tgz
Click to expand...
Click to collapse
updated successfully from 10.0.13
installed Magisk & disabled encryption & dm-verity
first boot after flashing is slower than normal.

HRSE said:
...disabled encryption...
Click to expand...
Click to collapse
Why did you disable encryption?