Related
AFTER ROOTING & OTA UPDATES
DOWNLOAD [ROOT CHECKER]
To make sure you have root access
Most of the time rooting your phone simply adds a couple files without changing any others, and an OTA will flash over just fine.
OTA updates first check to see that the partitions are holding the boot image and the recovery image are unmodified,
if you haven't frozen, replaced or removed a file inside the system that its looking for, then you should be able to accept the update.
DOWNLOAD [OTA RootKeeper]
To save superuser access
Any time you run a system update, you run the risk of loosing root. But you can save your superuser access with OTA Rootkeeper.
One's we get a custom Rom up and running for this device, I recommend using it (no custom ROM's for the Spectrum 2 as of yet).
With a custom Rom, you will get more updates and development then you would with the stock OTA update.
HOW TO USE LG UPDATE TOOL:
1. Backup your phone >How To Guide
2. Download and install the LG Update Tool
3. Launch the Update Tools application
4. Install USB Drivers
5. Make sure that the "PC Software" mode" enabled (Settings/Memory Management/USB storage)
6. Charge your phone battery to full
7. Plug in your phone via usb cable
8. Press "Launch software update", the update process might take as much as 30 minutes.
9. Reboot and enjoy.
COPY THE LINK BELOW TO YOUR BROWSER FOR MORE INFORMATION TO THE SPECTRUM 2
rootzwiki.com/topic/36242-spectrum-2-forum/page__st__20#entry1083538
Hi, anybody help me?
Can I flash this update with twrp(3.0.2r2) and root(SuperSu 2.71) or should I restore stock boot, recovery, system?
I don't see any "verify" in updater-script.
I found the answer - NO.
https://drive.google.com/file/d/0B9k8W8e2YrFfNmliUldCWjhqSXM/view?usp=drivesdk
dzidexx said:
Hi, anybody help me?
Can I flash this update with twrp(3.0.2r2) and root(SuperSu 2.71) or should I restore stock boot, recovery, system?
I don't see any "verify" in updater-script.
I found the answer - NO.
https://drive.google.com/file/d/0B9k8W8e2YrFfNmliUldCWjhqSXM/view?usp=drivesdk
Click to expand...
Click to collapse
hoping to have an answer to this too since I just got my tablet and don't want to brick it. I hope there will be a hero here.
And whwrw is the file? With TRWP and Root I have a permanent notification to downloand ans install that obviusly doesn't work. Shield downloads OTA file, restarts on TWRP and nothing happens because this doesn't know where is OTA file. Only if I download OTA zip file I could intall install it, but I don't find it looking on Google and another lookers.
I guess, the easiest way is to flash recovery and system of ota 1.4 (download from developer.nvidia.com and fastboot flash) and then flash the new ota update.
njhuiz said:
I guess, the easiest way is to flash recovery and system of ota 1.4 (download from developer.nvidia.com and fastboot flash) and then flash the new ota update.
Click to expand...
Click to collapse
There is another way and its the way i have done it.
Go back to stock 1.4 (So that everything is not modded)
Unlock Bootloader
Boot TWRP Recovery (Don't Flash it)
Make Sure in TWRP that you pick Read-Only for the System when asked
Flash SuperSU
Boot Tablet
Sign into Google and Download FlashFire
Ensure OTA is setup for Full
Then each time a OTA downloads use FlashFire to flash it.
My K1 had 1.4 with Root setup in the above manner and When OTA 1.5 Downloaded i used Flashfire and it flashed the Device and then i was on OTA 1.5 with Root intact.
If you use exposed on the other hand then this method will not work unless its the systemless version. But you will need to deactivate all Xposed Modules before flashing.
You could always wait till GtrCraft releases his optimized stock rom once Nvidia releases the factory images. All that's required is to wipe the system partition, flash the rom and then flash SuperSU. No full wipes needed. He hasn't released the 1.5 OTA update yet but I have found this is the easiest way to update. Shouldn't be too much longer.
KentuckyGuy447 said:
You could always wait till GtrCraft releases his optimized stock rom once Nvidia releases the factory images. All that's required is to wipe the system partition, flash the rom and then flash SuperSU. No full wipes needed. He hasn't released the 1.5 OTA update yet but I have found this is the easiest way to update. Shouldn't be too much longer.
Click to expand...
Click to collapse
I'm on rooted 1.4 stock rom, if I'm gonna flash GtrCraft rom, my data will not be deleted since there's no need to full wipe, right?
Thanks
coowkeee said:
I'm on rooted 1.4 stock rom, if I'm gonna flash GtrCraft rom, my data will not be deleted since there's no need to full wipe, right?
Thanks
Click to expand...
Click to collapse
Correct, you will be required to wipe the system partition but app and personal data is not stored on that partition. App data is stored in the Data partition and personal data such as pictures is stored in your internel storage. When in TWRP on the wipe tab you can select which partitions you wanna wipe under the Advanced tab, make sure NOT to select any partition other than system. System is where your ROM info and OS info is stored.
Just a note if you do not know what or how to do what I'm talking about please do a little research first. After you flash the optimized stock image, flash SuperSU for root.
Also note he hasn't released the 1.5 OTA update yet and make sure to flash the K1 OTA update when he releases it and NOT the original shield tablet OTA update. There is a difference.
KentuckyGuy447 said:
Correct, you will be required to wipe the system partition but app and personal data is not stored on that partition. App data is stored in the Data partition and personal data such as pictures is stored in your internel storage. When in TWRP on the wipe tab you can select which partitions you wanna wipe under the Advanced tab, make sure NOT to select any partition other than system. System is where your ROM info and OS info is stored.
Just a note if you do not know what or how to do what I'm talking about please do a little research first. After you flash the optimized stock image, flash SuperSU for root.
Also note he hasn't released the 1.5 OTA update yet and make sure to flash the K1 OTA update when he releases it and NOT the original shield tablet OTA update. There is a difference.
Click to expand...
Click to collapse
Done. Quite easy to do, thought it will be hard. But I don't feel Optimized yet, it feels like the same, but I'll give it more time lol.
Thanks
Prerequisites:
1. K1 is rooted.
2. K1 has TWRP custom recovery installed.
3. File manager (e.g. Total Commander).
4. supersubeta.zip on your K1.
Update procedure:
1. Go to “System upgrade” meniu screen (Settings->About tablet->System upgrade)
2. Enable full update image download. In the “System upgrade” meniu window press dots on the far upper right corner and select “Advanced”. In the new meniu screen check the option “Check full upgrade”. Go back to previous screen.
3. Let the “System upgrade” window download the latest ROM image (1.2 was about 668 MB). When the file is downloaded, DOT NOT PRESS REBOOT/INSTALL.
4. OTA downloaded update files are stored deep in the system. You need to know where the downloaded OTA update file has landed. Open your file manager and navigate to “/data/data/com.nvidia.ota/app_download”. There you will find the downloaded OTA update zip file. Check for the size (it should around 668 MB in case of 1.2 update).
5. Copy/move this file to a more manageable location, e.g. your downloads folder “/storage/emulated/0/download”.
6. Reboot K1 into TWRP recovery. Press the power button on your K1, select “Reboot”. As soon as the screen goes dark, press Volume Down button on your K1. When the K1 has booted into black screen with small letters, navigate with Volume Down button to the meniu item “Recovery” and select it by pressing Power button on K1.
7. K1 reboots to the TWRP recovery.
8. Select “Install”. Navigate to the OTA downloaded zip file, which you copied/moved to the directory “/storage/emulated/0/download”.
9. Select that file. The tablet will seem to freeze, but it’s not. But if you will not touch the screen, the K1 will lock the screen. So, while the K1 is thinking, keep touching the screen in various places until you see a new menu with a slider to install the zip file.
10. When you see a menu with slider, slide it to the right to install the new ROM.
11. After the install is complete, select “Clear caches” on the left.
12. After that, do not reboot the tablet yet. Navigate back to the install screen.
13. Select your “supersubeta.zip” file and install SuperSu binaries.
14. After that, reboot the tablet.
15. If all went well, first boot should show it’s optimising Apps. It means, you successfully update your tablet. After the boot, check if SuperSu is present. If not, repeat the procedure into going to Recovery mode and installing the supersu.zip file again.
its much easier with flashfire by chainfire, all you do is download the full update then load flashfire and click flash then it does it all for you, and you keep twrp and root. the only thing you lose is xposed if you use it so you have to flash that again using twrp
robgee789 said:
its much easier with flashfire by chainfire, all you do is download the full update then load flashfire and click flash then it does it all for you, and you keep twrp and root. the only thing you lose is xposed if you use it so you have to flash that again using twrp
Click to expand...
Click to collapse
You could always add the flashable Xposed zip to the queue in Flashire and have it install after the rom. Same with kernels etc....
Thanks for the tips here. Flashfire worked for me. Immediatly used it on my rooted phone too.
I had to re enable adaway afterwards, but thats not a problem.
lmulli said:
You could always add the flashable Xposed zip to the queue in Flashire and have it install after the rom. Same with kernels etc....
Click to expand...
Click to collapse
ahh cheers mate it just gets better
m0nt3s said:
Prerequisites:
1. K1 is rooted.
2. K1 has TWRP custom recovery installed.
3. File manager (e.g. Total Commander).
4. supersubeta.zip on your K1.
Update procedure:
1. Go to “System upgrade” meniu screen (Settings->About tablet->System upgrade)
2. Enable full update image download. In the “System upgrade” meniu window press dots on the far upper right corner and select “Advanced”. In the new meniu screen check the option “Check full upgrade”. Go back to previous screen.
3. Let the “System upgrade” window download the latest ROM image (1.2 was about 668 MB). When the file is downloaded, DOT NOT PRESS REBOOT/INSTALL.
4. OTA downloaded update files are stored deep in the system. You need to know where the downloaded OTA update file has landed. Open your file manager and navigate to “/data/data/com.nvidia.ota/app_download”. There you will find the downloaded OTA update zip file. Check for the size (it should around 668 MB in case of 1.2 update).
5. Copy/move this file to a more manageable location, e.g. your downloads folder “/storage/emulated/0/download”.
6. Reboot K1 into TWRP recovery. Press the power button on your K1, select “Reboot”. As soon as the screen goes dark, press Volume Down button on your K1. When the K1 has booted into black screen with small letters, navigate with Volume Down button to the meniu item “Recovery” and select it by pressing Power button on K1.
7. K1 reboots to the TWRP recovery.
8. Select “Install”. Navigate to the OTA downloaded zip file, which you copied/moved to the directory “/storage/emulated/0/download”.
9. Select that file. The tablet will seem to freeze, but it’s not. But if you will not touch the screen, the K1 will lock the screen. So, while the K1 is thinking, keep touching the screen in various places until you see a new menu with a slider to install the zip file.
10. When you see a menu with slider, slide it to the right to install the new ROM.
11. After the install is complete, select “Clear caches” on the left.
12. After that, do not reboot the tablet yet. Navigate back to the install screen.
13. Select your “supersubeta.zip” file and install SuperSu binaries.
14. After that, reboot the tablet.
15. If all went well, first boot should show it’s optimising Apps. It means, you successfully update your tablet. After the boot, check if SuperSu is present. If not, repeat the procedure into going to Recovery mode and installing the supersu.zip file again.
Click to expand...
Click to collapse
Thank you very much for your detailed instructions. I followed it exact, and my K1 rooted with 1.4 is now rooted with 1.5
Sent from my Nexus 7 using XDA Free mobile app
robgee789 said:
its much easier with flashfire by chainfire, all you do is download the full update then load flashfire and click flash then it does it all for you, and you keep twrp and root. the only thing you lose is xposed if you use it so you have to flash that again using twrp
Click to expand...
Click to collapse
What if i have LP and want to do the MM update, i should TWRP, MM ROM and then SU. What should be the steps...
m0nt3s said:
Prerequisites:
1. K1 is rooted.
2. K1 has TWRP custom recovery installed.
3. File manager (e.g. Total Commander).
4. supersubeta.zip on your K1.
Update procedure:
1. Go to “System upgrade” meniu screen (Settings->About tablet->System upgrade)
2. Enable full update image download. In the “System upgrade” meniu window press dots on the far upper right corner and select “Advanced”. In the new meniu screen check the option “Check full upgrade”. Go back to previous screen.
3. Let the “System upgrade” window download the latest ROM image (1.2 was about 668 MB). When the file is downloaded, DOT NOT PRESS REBOOT/INSTALL.
4. OTA downloaded update files are stored deep in the system. You need to know where the downloaded OTA update file has landed. Open your file manager and navigate to “/data/data/com.nvidia.ota/app_download”. There you will find the downloaded OTA update zip file. Check for the size (it should around 668 MB in case of 1.2 update).
5. Copy/move this file to a more manageable location, e.g. your downloads folder “/storage/emulated/0/download”.
6. Reboot K1 into TWRP recovery. Press the power button on your K1, select “Reboot”. As soon as the screen goes dark, press Volume Down button on your K1. When the K1 has booted into black screen with small letters, navigate with Volume Down button to the meniu item “Recovery” and select it by pressing Power button on K1.
7. K1 reboots to the TWRP recovery.
8. Select “Install”. Navigate to the OTA downloaded zip file, which you copied/moved to the directory “/storage/emulated/0/download”.
9. Select that file. The tablet will seem to freeze, but it’s not. But if you will not touch the screen, the K1 will lock the screen. So, while the K1 is thinking, keep touching the screen in various places until you see a new menu with a slider to install the zip file.
10. When you see a menu with slider, slide it to the right to install the new ROM.
11. After the install is complete, select “Clear caches” on the left.
12. After that, do not reboot the tablet yet. Navigate back to the install screen.
13. Select your “supersubeta.zip” file and install SuperSu binaries.
14. After that, reboot the tablet.
15. If all went well, first boot should show it’s optimising Apps. It means, you successfully update your tablet. After the boot, check if SuperSu is present. If not, repeat the procedure into going to Recovery mode and installing the supersu.zip file again.
Click to expand...
Click to collapse
This is causing me bootloops
w0rtez said:
What if i have LP and want to do the MM update, i should TWRP, MM ROM and then SU. What should be the steps...
Click to expand...
Click to collapse
you should be fine mate, fkashfire will tell you if there is a problem and ask if you want to try anyway. so if it says there is something wrong then do it long way
robgee789 said:
you should be fine mate, fkashfire will tell you if there is a problem and ask if you want to try anyway. so if it says there is something wrong then do it long way
Click to expand...
Click to collapse
stuck on logo screen but i can still access TWRP..
w0rtez said:
stuck on logo screen but i can still access TWRP..
Click to expand...
Click to collapse
weird mate, just do it the long way around then mate
I flashed 5.1.11 fastboot image but get Qualcomm crashdump.
So had to go back to 9.0 for now but want to use OOS 5.1.11.
How do I go back to 5.1.11?
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
dom_mnml said:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2
Click to expand...
Click to collapse
Downloaded the file but doesnt install.
Tried on system local upgrade first and then via twrp and it failed with this error.
Any idea?
III. Instructions of roll back from PIE - DP version to OREO version – Local Rollback
Rollback process:
Please note: This upgrade will clear all contents of the phone, please make sure to back up.
1. Settings –> System –> About phone –> Advance –> scroll to the bottom and tap Build number 5 times.
2. Settings –> System –> Developer options –> Open "OEM unlocking".
3. Download the ROM rollback package [HERE].
4. Copy ROM rollback package to mobile phone storage root directory.
5. Settings -> system updates -> top right corner icon -> local upgrade -> click on the installation package -> immediately upgrade -> system upgrade to 100%.
6. Select Reboot system now.
7. Update successfully.
this is from oneplus forum.
https://forums.oneplus.com/threads/android-p-beta-developer-preview-3-for-oneplus-6.872904/
The 5.1.11 package is the same as downgrade package .....
So Just Download OOS5.1.11 then put it in root directory using local-updating ....
It's not the same as 5.1.11. tried this last night and trying to gain root with a patched boot image yielded a bootloop, so there's a version mismatch. It took me 2 hours to get it back in working order, though I had to use the msm tool to revert back to original retail ROM.
I might try again this weekend, and see if I can't figure out which version is in that zip and do increments from there. Something tells me it's 5.1.6 or similar.
XNine said:
It's not the same as 5.1.11. tried this last night and trying to gain root with a patched boot image yielded a bootloop, so there's a version mismatch. It took me 2 hours to get it back in working order, though I had to use the msm tool to revert back to original retail ROM.
I might try again this weekend, and see if I can't figure out which version is in that zip and do increments from there. Something tells me it's 5.1.6 or similar.
Click to expand...
Click to collapse
U just believe or NOT ...... up to you....
It is THE SAME
U can download the 2 fiiles form HERE : https://downloads.oneplus.com/devices/oneplus-6/
rollback file : http://oxygenos.oneplus.net.s3.amaz...all_1808102118_downgrade_68586451f7334c4d.zip <= acroding https://forums.oneplus.com/threads/oxygenos-9-0-for-the-oneplus-6.909533/
and compare .
It's not. You cannot take the 5.1.11 FULL OTA Zip file and roll back. System update will not let you. The Rollback Zip is different, as System Update will let you roll back with it. I have both installed in Root of my phone right now and they are completely different. They're even different sizes (Rollback is 1.44GB, OTA is 1.42GB). They are not one and the same thing.
Oh, and, I JUST flashed the Rollback image. Yeah, It's 5.1.6, just like I ****ing said.
Frist You Must Unlock BootLoader
Second You Must Have Pc With Android platform tools (They Exist Also For MacOS And Linux)
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options".
2. Go back to the previous page, where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).
3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen.
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section
Download This https://mega.nz/#!3aZ3AICJ!YAHEVP5dQ2bgnV0_oDd3O4MBzdVt1qT_9HfqGWvVzCE
open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
Fastboot boot boot_rooted.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
HOW TO APPLY OTA UPDATES
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
I'm 12 Years Old Don't Worry I Test It On My Mi A2 Lite Thanks
I Take Some Things From https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
NourHazem I said:
Frist You Must Unlock BootLoader
Second You Must Have Pc With Android platform tools (They Exist Also For MacOS And Linux)
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options".
2. Go back to the previous page, where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).
3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen.
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section
Download This https://mega.nz/#!3aZ3AICJ!YAHEVP5dQ2bgnV0_oDd3O4MBzdVt1qT_9HfqGWvVzCE
open an administrative command prompt, move to the Android platform tools directory and then write the following command:
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
HOW TO APPLY OTA UPDATES
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
I'm 12 Years Old Don't Worry I Test It On My Mi A2 Lite Thanks
I Take Some Things From https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Click to expand...
Click to collapse
May i use this method on my a2 lite running android pie
ashikalone said:
May i use this method on my a2 lite running android pie
Click to expand...
Click to collapse
Instead of doing a full quote, you should have read it.
Also if you are only 12, you didn't take "some things" from bubuxp's thread, but almost the whole story. I would prefer if mod could close this thread.
harvey said:
Also if you are only 12, you didn't take "some things" from bubuxp's thread, but almost the whole story. I would prefer if mod could close this thread.
Click to expand...
Click to collapse
Starting to think there is no mod in this forum... At least for this device:silly:
Any one try this
Why do we need a separated Pie root guide, when the only difference for Pie is a newer patched boot image which you can make yourself with Magisk and the fitting OTA/Fastboot files?
We really need a mod for our A2 Lite forum, there are too many "useless" posts and threads inside. Feels like MIUI forum and not XDA.
OTA
NourHazem I said:
Frist You Must Unlock BootLoader
Second You Must Have Pc With Android platform tools (They Exist Also For MacOS And Linux)
BOOTLOADER UNLOCK
First thing to do: unlock the bootloader (if you didn't already do this, obviously). Smartphones with Android One are much easier to unlock compared to other Xiaomi phones with MIUI (where you have to ask for authorization and wait for weeks).
CAUTION: when you unlock the bootloader, the phone will reset, erasing all your saved data. Backup your data before unlocking.
1. Go to Settings > System > About phone > and tap many times on "Build number" until you unlock "Developer options".
2. Go back to the previous page, where you can find now "Developer options". Go there and enable the "OEM unlocking" option (and it's better to never disable this).
3. Now you can shutdown your phone, then turn it on while holding the "Volume down" button pressed. Release it when you see the Fastboot screen.
4. Now connect the phone with your PC via USB cable, open an administrative command prompt, move to the directory where the Android platform tools are placed and unlock the bootloader with the following command:
Code:
Code:
fastboot oem unlock
The phone will reboot, erasing all the data.
Now you unlocked your phone's bootloader and can continue to the next section
Download This https://mega.nz/#!3aZ3AICJ!YAHEVP5dQ2bgnV0_oDd3O4MBzdVt1qT_9HfqGWvVzCE
open an administrative command prompt, move to the Android platform tools directory and then write the following command:
Code:
Fastboot boot boot_rooted.img
If everything works the phone should boot normally. Open Magisk Manager and it should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
HOW TO APPLY OTA UPDATES
IMPORTANT: OTA updates will work only if all the partitions on the smartphone are untouched. Magisk Manager can restore the original boot.img following this section of the guide, but if you tampered directly with the system partition (e.g. manually editing build.prop) or other partitions, OTA will refuse to install.
You can try to fix OTA updates without the need to flash the whole original fastboot ROM, by flashing only the tampered partitions (usually only "system") with the corresponding img file found inside the fastboot ROM zip. Check the "Troubleshooting" section of this guide for details.
12. When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images" but very important: absolutely don't reboot the phone now!
Important note: Magisk Manager will restore the boot.img that was found on the phone while installing Magisk. If the boot.img was already non-vanilla (for example you flashed the boot.img with TWRP before installing Magisk), Magisk Manager will backup that modified version of boot.img, and when restored the OTA will not work, as that's not a vanilla boot.img.
13. Close Magisk Manager and go to "Settings" > "System" > "System update" and install the OTA update. After the update is downloaded, a two-stages update will begin.
14. When both stages of the update process completed, it will ask to restart: DON'T DO IT!. Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot (After OTA)" and after that you can tap on "Reboot".
After the reboot you will have the updated Android version with Magisk already working.
I'm 12 Years Old Don't Worry I Test It On My Mi A2 Lite Thanks
I Take Some Things From https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Click to expand...
Click to collapse
Waiting I do not understand if I'm running my phone and installing a magician please update will not work?
---------- Post added at 06:37 PM ---------- Previous post was at 05:54 PM ----------
alenaki123 said:
Waiting I do not understand if I'm running my phone and installing a magician please update will not work?
Click to expand...
Click to collapse
f i unlock bootloader, root and install magisk ota update i will not work ???
Read the guide
Updates will work if you install it if you got ota go to magisk manager
Click uninstall>restore images>go install ota do not reboot>go magisk manager and click install select>inactive slot (after ota)
Bootloop! Not working
V10.0.2 Working https://www.the***********.com/root-xiaomi-mi-a2-a2-lite-android-pie-magisk/
OP should be ashamed of copying the entire guide and pasting It with a new link and poor formating.
I don't see Magisk Manager after doing boot patched_boot.img. It actually run successfully, the phone restarted after the command.
My Build number is PKQ1.180917.001.V10.0.2.0.PDLMIFJ, I tried both of these patched, V10.0.2.0.PDLMIFJ Patched Boot Image: Link
V10.0.1.0.PDLMIFJ Patched Boot Image: Link
luckyvictor said:
I don't see Magisk Manager after doing boot patched_boot.img. It actually run successfully, the phone restarted after the command.
My Build number is PKQ1.180917.001.V10.0.2.0.PDLMIFJ, I tried both of these patched, V10.0.2.0.PDLMIFJ Patched Boot Image: Link
V10.0.1.0.PDLMIFJ Patched Boot Image: Link
Click to expand...
Click to collapse
You need install manually magisk manager ,you can download apk from official website, after from magisk manager you can install magisk 18.0 ...this is my experience
thanks man, following your guide I was able to root this bad boy. Much more complicated than anything I've ever rooted as I've usually got TWRP installed but for whatever reason it's unable to decrypt my system and even after a fresh wipe I still can't install so this method worked great for me, we'll see how OTA updates go...
EDIT: Seems to be after a reboot I am no longer rooted, do I need to fastboot flash that patched boot image everytime I reboot?
@discomilk
Boot from patched boot.img
Open Magisk Manager -> install -> install direct
Reboot and profit!
Yup, seems I forgot to install Magisk after that patched boot. Everything working now.
Hi all,
I rooted a Nord of a friend of mine. Since then he installed several updates and reapplied Magisk before reboot, as usual. Now his Nord is running the lastest Android 10 release, Magisk v21.4 and Magisk Manager v22.
Today the upgrade to Android 11 is offered on his Nord. He asked me whether he can peform the update as usual, with applying Magisk - then v22 - to the OTA slot.
I cannot answer it, because I own a 7t, and never performed an OS upgrade.
Does he has to follow the standard process, or is something special to be performed to leave the Nord rooted?
Thx in advance
Hi!
This process is pretty simple.
DONT REBOOT THE PHONE DURING STEPS!!
Step by step:
-download the last Oxygen update with oxygen updater on play store (dont install this update now!).
-go on magisk manager main page and uninstall magisk image.
-install your downloaded update (go to phone setting and apply a local update)
-go on magisk manager main page again and install magisk on the inactive slot
-reboot phone
-enjoy ;p
Thank you.
What I don't understand: You say
-download the last Oxygen update with oxygen updater on play store (dont install this update now!).
-...
-install your downloaded update (go to phone setting and apply a local update)
Why do I need to download the update package the Oygen Updater when I should use the update package in the phone settings? For what do I need the first one?
The major difference to the standard process is that one need to uninstall Magisk on the active slot before applying the update. Have I understood that correctly?
1- Download official oxygen os update with "Oxygen Updater" app.
Now the update package is stocked on your internal memory.
2- Install this update package (previously downloaded with "Oxygen Updater" app) with the official updater on phone setting.
(Local update use file stocked on your phone)
Download just one update package, not two.
Sorry for the mistake..
My friend did what proposed.
For "go on magisk manager main page and uninstall magisk image" he uninstalled Magisk using the manager, and the phone rebooted immediately. So he lost root :-(
What went wrong?
Your friend have uninstall totally magisk..
Is not the same that "uninstall magisk image".
Please follow the image patch method again to gain the root.
[GUIDE] How to root OnePlus Nord
Devices that started to be received today have Oxygen OS 10.5 out of the box. No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted. You then need to update to a newer build first. You...
forum.xda-developers.com
He took the option "Uninstall Magisk" written in red on the main page of the Magisk Manager.
According to https://forum.xda-developers.com/t/guide-how-to-root-oneplus-nord.4139411/post-84244381 the standard keep-root-process should work while upgrading from an already rooted Nord from Android 10 to 11:
Apply upgrade, prior to boot install Magisk to the inactive slot, then reboot.
So why does one need to uninstall Magisk?
Last time I rooted his phone using a fastbooted TWRP and think this should work with Android 11 as well, or?
Yes, press "uninstall magisk", pop-up is appeared, press "restore image" (uninstall magisk image..).
Your friend press "uninstall magisk" >> "uninstall all"
If not the same :/
Restore image before OTA update to prevent bootloop, brick, .. This step is essential for me for a majority of phone.
I don't know if the TWRP method work for this.. sorry.
Therand said:
Yes, press "uninstall magisk", pop-up is appeared, press "restore image" (uninstall magisk image..).
Your friend press "uninstall magisk" >> "uninstall all"
If not the same :/
Click to expand...
Click to collapse
Thank you. I never used the option, so I couldn't guide him