[Guide][Root] Magisk without TWRP on Android P - Google Pixel 2 XL Guides, News, & Discussion

[Guide][Root] Magisk without TWRP on Android P - Google Pixel 2 XL Guides, News, & Discussion

Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode
REQUIREMENTS -
1 - Setup adb and fastboot on your PC.
2- Stock boot image (boot.img) of your device (extract file from factory image android P)
3 - Last Magisk Manager (v 5.8.3)
4 - Active Internet connection
5 - Active mind and patience.
6 - Devices must is unlock bl.
This Boot-Image is for boot android P PPR1.180610.009:
https://drive.google.com/open?id=166pE9aMk-jqns3JM74enFhsaDY6-c3yJ
Magisk Manager
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
==================================================
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta
7- Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk
CREDITS
@topjohnwu (Magisk)

Sadly goes into a bootloop for me - no idea why though

This worked for me. I had magisk installed and took the pie update. No more root. D/l the factory image and extracted the boot image to the files folder...pissmeoff they changed the name of the icon... and magisk patched the image and saved it in its folder. Found the file, moved it to the laptop then flashed it.

reawo said:
Sadly goes into a bootloop for me - no idea why though
Click to expand...
Click to collapse
I think you made a mistake.

I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide

reawo said:
I always did that method pre Pie and it always worked but now I end up in a bootloop and I did everything according to guide
Click to expand...
Click to collapse
I think you use my file(boot.img) for patch_boot.img from magisk manager.
I think you must check your build number devices.
You must use file boot.img from your factory image for root.
9.0.0 (PPR1.180610.009, Aug 2018) >This is version for my devices
9.0.0 (PPR1.180610.011, Aug 2018, Telstra) >?

hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?

reawo said:
hey mate thanks for the input, I got a normal non testra (whatever that is) taimen - tried your boot.img and before that I tried the one from the factory image, both result in a boot loop.
I went through all stages of the Android p beta and in the end, to try solve this, I also non wipe flashed the factory image all to get the same result
could you sent me a drive Link to the patched version of yours or something?
Click to expand...
Click to collapse
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin

newyesor said:
This is file patch_boot.img from my devices.
https://drive.google.com/open?id=1nVEpoGam-VY1YT3GBbG6HNfhnT2NqRin
Click to expand...
Click to collapse
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?

I receive also a bootloop and I didnt make any mistake. I also used this method pre Pie, I read that alot of users have problems with rooting Pie atm, even with TWRP

reawo said:
Also doesnt work, i thought so - didnt do anything different than when it worked - no idea why it doesn't though
Is there a way to see or read out any protocols regarding this?
Click to expand...
Click to collapse
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.

newyesor said:
You use adb last version for flash patch_boot.img ?
I think you should flash factory image new again and factory reset your devices.
You are use stock kernel or other kernel on your devices.
Click to expand...
Click to collapse
I downloaded all the latest adb and fastboot. Never touched kernel or did custom recovery, always used the magisk method since i am on a pixel device. i also got the issue that my pc doesnt recognize my pixel from time to time, you think i should do a complete wipe?

I don't sure.
You are use platfrom-tool from sdk lastversion?(for flash via fastboot mode)

@reawo
I think you should flash factory image new again and factory reset your devices.
Step 1: Patching the stock boot.img
1- Copy the stock boot.img of your device to your phone's internal storage.
2- Install the latest Magisk Manager
3- Launch Magisk Manager app
4- If prompted to install Magisk, select NO THANKS
5- If you're planning to flash the patched boot image,For normal users leave it as the default .img
6-Press Setting>Update Channel>Beta ,and close this app.****
7- Open app again and Press Install > Install > Patch Boot Image File, and select your stock boot image file
Navigate to the location of the stock boot.img you copied earlier on, then Select it
8- Magisk Manager should begin downloading the magisk zip file used for patching (This process is not failed)***
9- Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img
Step 2: Flashing the patched boot.img
1- Copy the patched_boot.img from your phone's internal storage to folder adb or platform-tools on PC (directory>SDcard/MagiskManager/patched_boot.img)
2- You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
1- Setup adb and fastboot on your PC.
2- Unlock the phone's Bootloader (if its not unlocked)
3-Re-enable USB debugging on the phone
4- Connect the phone to the PC via USB cord
5- Boot into fastboot mode.
code
-adb reboot bootloader
6- Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Quote:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
-Verify root using Root Checker
Try at your own Risk

Will work on the verizon variant (bootloader locked)?

sabi95190 said:
Will work on the verizon variant (bootloader locked)?
Click to expand...
Click to collapse
Nope. If it were that easy for bootloader locked Verizon phones, it would have been done months ago.

What happens if you lock the bootloader after all of this?

DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
You'll wipe the phone, lose root, and be stock.

DarkSilentSC said:
What happens if you lock the bootloader after all of this?
Click to expand...
Click to collapse
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.

TonikJDK said:
When still rooted and modified? You might very well brick it. Relocking while modified is borderline insanity.
Click to expand...
Click to collapse
"Borderline"???? More like certifiably insane! ?

Related

[Guide] Flash 6.0, root, and no-forceencrypt from stock (easy method)

Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.

Didnt work for me.

Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img

typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you

Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk

You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344

- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt

Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:

i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.

dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.

Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.

That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.

Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.

Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?

Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.

Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help

Nice guide.

I install Busybox from Play, I assume that's needed? Everyone else doing this?

- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.

All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?

* * * [Pixel 2 XL] - UPDATE Monthly Factory Image / UPGRADE To New OS * * *

WHO IS THIS GUIDE FOR:
Anyone updating factory images within the same OS version (10 to 10)
Anyone upgrading from one OS to another (9x to Android 10)
Below is a QUICK REFERENCE guide for those who have done this before, and a DETAILED STEP BY STEP guide for the first or second timer who needs each and every step outlined. Links to all required files are also provided (make sure you are selecting the latest version)
UPDATE TO THE LATEST FACTORY IMAGE . . . UPGRADE TO THE NEXT OS. . .
PREP WORK:
* Unlocked bootloader. (*performing critical_unlock only required with bootloader versions PRIOR to TMZ20a) read it here.
* Latest SDK Platform Tools found here.
* USB 2.0 & 3.0 cables available (trust me)
* Remove screen lock security before starting
* Remove all substratum overlays
*Download and extract the latest Taimen factory image (place the second extracted folder in Platform Tools folder)
CLEAN FLASH (wipe everything) or DIRTY FLASH (keep data)
Decide now whether you want a fresh OS that will restore your device to factory setup OR if you want to flash the latest factory image but keep your data.
For a clean flash: leave the FLASH-ALL file intact, change nothing.
To retain your data: EDIT the FLASH-ALL file and REMOVE the -w near the end of the script. Save the file and reopen it to ensure the -w has been removed,
When UPGRADING from one OS to another I reco a CLEAN FLASH (leave the -w intact)
Place these files on your sdcard (either before dirty flash or from PC after clean install):
* Latest TWRP.ZIP
* Your preferred customer kernel zip, I use ElementalX kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing :good:
QUICK REFERENCE GUIDE for updating/upgrading Pixel 2 XL:
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash custom kernel, I use flar2's ElementalX Kernel. SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
DETAILED STEP BY STEP GUIDE for updating monthly factory images, or upgrading to the next OS (ie: 9x to 10x)
I reco a CLEAN FLASH (leave the -w intact) when jumping from one OS to a new one (not necessary when doing monthly factory updates within the same OS version)
Requirements:
*Unlocked bootloader and Critical_unlock* completed. (*critical_unlock required with bootloader versions PRIOR to TMZ20a) read it here.
*Latest SDK PlatformTools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* Latest TWRP.ZIP
* Your preferred Custom Kernel, I use Elemental X Kernel
* Magisk uninstall instructions In the event you need to manually uninstall and reinstall MM
* Latest Magisk.zip
* Latest Magisk Manager APK
These files in your Platform Tools Folder:
* Latest factory image (MAKE SURE YOU DL THE CORRECT DEVICE IMAGE :good: )
* Latest TWRP.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Connect device to PC, verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot latest factory image (To KEEP internal storage intact, edit and remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
Type: FLASH-ALL (hit enter) Allow the OS to reboot and settle for a minute *REMEMBER LEAVING THE -W INTACT WILL WIPE YOUR DEVICE*
6. Reboot into BOOTLOADER, in CMD screen Type: fastboot boot <twrpxxx.img name> to boot into Latest TWRP.IMG
7. Once in TWRP, install Latest TWRP.ZIP from sdcard
8. Reboot back into Recovery
9. Install compatible custom kernel, I use flar2's ElementalX Kernel.
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Boot into Recovery
13. Install Latest Magisk.zip
14. Reboot into System
15. Profit
Troubleshooting Tips & Other Information
Click here for * * * BASIC FASTBOOT/ADB TROUBLE SHOOTING FOR THE 2XL * * *
If you get stuck at the G screen, or bootloop into TWRP, try these steps:
-Perform a hard reboot (long press the power button) or
-Get back to TWRP (whether by booting into it from fastboot, or rebooting into bootloader -long press power & vol down- then boot into recovery) and reinstall the Magisk Uninstaller in TWRP a few times.
- If you are bootlooping into TWRP with Magisk installed, READ THIS!
- Safety Net message in Magisk "The Response Is Invalid" is a known issue[/URL] ... Be patient
View attachment 4572738
Make sure you have all the correct and/or latest versions of SDK Tools, factory image, TWRP.img and TWRP.zip, and Magisk
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Again, HUGE thanks to @Badger50 for his invaluable input

Az Biker said:
A lot of users have had success upgrading from Oreo to Pie and there are several tutorial / guide posts located in different threads, so I figured I'd centralize instructions in a Quick Reference Thread, that includes all needed file links and an easy to follow step by step.
Please feel free to make any suggestions to simplify or make this more accurate.
Requirements:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
These files on your sdcard:
* TWRP 3.2.2-0.ZIP
*Flash kernel 3.0
* magisk uninstaller
*magisk zip 1674
* MM 5.8.3 APK
These files in your Platform Tools Folder:
* 9.0 factory image
*TWRP 3.2.2-0.IMG
1. Make backup, move to PC (because you never know)
2. Disable all security; patterns, pins, etc.
3. In Developer Options, make sure USB DEBUGGING is on
4. Verify fastboot is working type; fastboot devices (should see your device's serial number)
5. Fastboot 9.0 factory image(To KEEP internal storage intact, remove -w in "flash-all.bat" file and SAVE, to wipe entire device, leave flash-all unedited)
6. Type: fastboot boot <twrpxxx.img name> to boot into TWRP 3.2.2-0.IMG
7. Once in TWRP, install TWRP.ZIP on sdcard
8. Reboot back into Recovery, and install the magisk uninstaller in twrp,
9. Reboot back into Recovery and install Flash kernel 3.0
10. Reboot back into Recovery
11. Reboot into System, allow OS to settle for a few minutes
12. Install MM 5.8.3 APK
13. Reboot into Recovery
14. Install magisk zip 1674,
15. Reboot back into Recovery
16. Reboot into System
17. Profit
Note: as a matter of superstition, I reboot back into recovery each time after installing TWRP, cust kernel, and magisk, prior to booting into system. It is NOT required, but it works
Thanks to @Badger50 for figuring out the right steps in this process!
Click to expand...
Click to collapse
Well done my brother!! :good::good:

Badger50 said:
Well done my brother!! :good::good:
Click to expand...
Click to collapse
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).

newyesor said:
I use unlock bootloader normal.
I was done follow your step but it's boot stuck google logo after flash magisk(16.74).
Click to expand...
Click to collapse
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??

Badger50 said:
Sometimes it takes 5 minutes or so on first boot. If it doesn't work, do a hard restart a few times. If that doesn't work, flash magisk again in twrp.
You use unlock bootloader normal??
Click to expand...
Click to collapse
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.

newyesor said:
I use normal unlock bootloader.
I wait devices boot around 5 minutes and it 's reboot in to twrp recovery.
Click to expand...
Click to collapse
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.

Badger50 said:
So your bootloader _critical partition isn't unlocked?? Which can't be right either since you've been able to boot fastboot the update to P. Guess I just don't know what your trying to say.
Click to expand...
Click to collapse
I use this command for flash unlock bootloader.
fastboot flashing unlock

newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?

Badger50 said:
Have you ever ran fastboot flashing unlock_critical..?
Have you actually booted into the 9.0.OS yet?
Click to expand...
Click to collapse
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.

newyesor said:
I use this command for flash unlock bootloader.
fastboot flashing unlock
Click to expand...
Click to collapse
If you flashed the factory image with no issues, then you must have completed critical_unlock as well, otherwise the new bootloader shouldn't have taken (as far as I understand).
I'd start from scratch again, and make sure you follow the process exactly. Many users have used this with no issue, so maybe you missed something? The first time I flashed the factory image to my 6P (my backup) I totally skipped flashing the boot.img, and wondered why it wouldn't boot

Kudos, just what I needed to update!

newyesor said:
I have never ran fastboot flashing unlock_critical.
Yes,My devices is base on android P and I was booted into the 9.0.OS.
Click to expand...
Click to collapse
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?

Badger50 said:
Have you flashed the magisk uninstaller as well? Why are you showing magisk 16.0?
Click to expand...
Click to collapse
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.

Is flashing the kernel mandatory?

newyesor said:
Yes,i was flashed the magisk uninstaller as well.
I try to root with magisk on my devices.
I try to flash patch boot for root without twrp but it's not work.
I try to flash magisk follow you but it's not work.
Click to expand...
Click to collapse
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.

aznriceballman said:
Is flashing the kernel mandatory?
Click to expand...
Click to collapse
Not mandatory, but it keeps TWRP touch screen working among other things...

Just wanted to say thanks for this!
I didn't have time to update from DP5 yesterday, but I guess that was a good thing because now there's this guide, and it worked perfectly. Upgraded from DP5/flash 2.44 and who knows what Magisk version to all the latest and greatest in no time at all.
Thanks!

Badger50 said:
Something just seems fishy to me. I've never heard of anyone not unlocking _critical, and being able to fastboot the factory image. However, it seems that you have somehow. All I can suggest is to fastboot the 9.0 again to both slots, and let it boot up each time.
Then fastboot into twrp, flash the installer zip, and let it boot up. Then go back to twrp, flash magisk uninstaller zip, then flash custom kernel, and let it boot up. Then go back to twrp, and flash magisk 1674 again.
If none of that works, I'd unlock _critical, which will wipe your phone, and then start over.
Click to expand...
Click to collapse
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?

shooterlgk said:
im having an issue, i followed all instructions and got booted up an everything but when i flash twrp img it stays stuck on the twrp logo, flashed the one mentioned in o.p and the newest as well to remove any doubts, but no go. Any suggestions?
Click to expand...
Click to collapse
Do you have screen lock disabled?

Badger50 said:
Do you have screen lock disabled?
Click to expand...
Click to collapse
Yes sir

delete guide

delete guide

--reserved--

Hoe can i tell what image matches for my phone stil on 8.1 november 1st security patch n a unlocked boot

rob420p said:
Hoe can i tell what image matches for my phone stil on 8.1 november 1st security patch n a unlocked boot
Click to expand...
Click to collapse
Check your build and download the right file.
Matteo

While uninstalling Magisk(from rooted stock), do we need to find the current active slot and flash the stock image to it? In the guide flashing to both partitions is mentioned.

mujtahid1494. said:
While uninstalling Magisk(from rooted stock), do we need to find the current active slot and flash the stock image to it? In the guide flashing to both partitions is mentioned.
Click to expand...
Click to collapse
Flash a both slot just to be sure to pass OTA if needed.
Matteo

Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Twrp latest file.img check Dowloads Section
- A brain
Procedure:
Sideload method. (It's for people who want to install Magisk on their phone during Custom Rom installation process without any permanent Twrp (usefull for people who want to root their phone when they have MTP issue during Custom Rom installation)
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your adb folder.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open adb (fastboot) command prompt on your pc, type
Code:
adb sideload magisk.zip
Reboot and done, you have Magisk on your device.
Normal temp Twrp method. (It's for people who want to install Magisk on their phone when they are already running a Custom Rom without permanent Twrp.
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your phone sdcard.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Click Install, choose magisk.zip
- Swipe to confirm, wait for the process...
Reboot and done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip
Click to expand...
Click to collapse
Hello, the stock boot v10.0.1.0.img, does not have mirrors, please could upload it again, I need it urgently, thank you very much

ofuen said:
Hello, the stock boot v10.0.1.0.img, does not have mirrors, please could upload it again, I need it urgently, thank you very much
Click to expand...
Click to collapse
No. If you have issue with androidfilehost it's not my problem.
Matteo

Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Twrp latest file.img check Dowloads Section
- A brain
Procedure:
Sideload method. (It's for people who want to install Magisk on their phone during Custom Rom installation process without any permanent Twrp (usefull for people who want to root their phone when they have MTP issue during Custom Rom installation)
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your adb folder.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open adb (fastboot) command prompt on your pc, type
Code:
adb sideload magisk.zip
Reboot and done, you have Magisk on your device.
Normal temp Twrp method. (It's for people who want to install Magisk on their phone when they are already running a Custom Rom without permanent Twrp.
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your phone sdcard.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Click Install, choose magisk.zip
- Swipe to confirm, wait for the process...
Reboot and done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip
Click to expand...
Click to collapse
Thank you very much. It works for my stock rom. already clicked the thanks icon

dipankar.roy said:
Thank you very much. It works for my stock rom. already clicked the thanks icon
Click to expand...
Click to collapse
Thank you man, but plz next time don't quote the entire guide
Have a nice day
Matteo

No links available for stock boot 9.6.17.0
Edit: Oh I see, not his problem, dang.

dipankar.roy said:
After installing the patched boot image to my device (MI A2), android version 9. build number V10.0.2.0.PDIMIFJ,
the Magisk working properly. But when I turned off my phone and insert the power cable for charging, the phone start booting and stuck at "AndroidOne" logo.
Waiting for your advice...
Thanks..
Click to expand...
Click to collapse
That's a normal stock rom issue with magisk, you can't fix it. but if you want, we don't have this issue on custom roms
( next time plz don't quote the entire thread )
Matteo

Hey Matteo,
I've got a problem while booting with the patched boot image. Whenever I start the 'fastboot boot image' stuff, it ends with following message:
downloading 'boot.img'...
FAILED (command write failed (no error))
finished. Total time 0.002s
Phone screen goes black and says 'press any key to continue' or something like that. I tried several different USB ports and also different boot images, I cant even boot with the stock image.
When I unlocked the bootloader I had a problem that while booting the phone said I should perform a factroy reset because of a corrupt file system...after doing that, the phone itself works fine. But I really want the root access.
Have you ever encountered that message?
Thanks in advance
Update: Did the same procedure with my notebook and ironically it worked without a flaw. USB driver conflicts maybe?

On Pie V10.0.2.0, applied the patched_boot.img, Magisk was not installed at the beginning.
Installed Magisk manually but the phone was not rooted.
Applied the patched_boot.img again and I got root.
Now, every time I reboot the phone, root is gone and I have to apply the patched_boot.img again.

Thread closed on OP request

Unlocking bootloader

With the huawei support down, could anyone please help me to unlock huawei nova 2i RNE-L22 bootloader and to root it?

DC. UNLOCKER?
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code

bootloader unlock codes forbidden
Chisetdel31260 said:
DC. UNLOCKER?
It says
> If your phone runs Android 8 or later with latest security patch - then this service won't work!
I have the latest security patch(March 1, 2019), I've been searching for the past 3 days for a working method to root my mate 10 lite, found nothing.
Huawei stopped providing oem unlock codes, All the services that provided unlock codes for money are now obsolete too.
I'm trying to find a way to root this phone on my own, but I'm not sure where to go from here.
I've read this book today "XDA Developers' Android Hacker's Toolkit", but it teaches how to use rooting methods that are already out there and not how to create your own way to root a device.
Can you provide guidance on where to go from here to learn how to find vulnerabilities in android?
Click to expand...
Click to collapse

"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite .

it works
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
(4€/4$).
Service ROMs you can find here :
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.

m10_lite said:
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
Click to expand...
Click to collapse
Best Custom ROM is Stock ROM & root .

bozka1 said:
Best Custom ROM is Stock ROM & root .
Click to expand...
Click to collapse
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?

davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
He did already
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
(4€/4$).
Service ROMs you can find here :
https://androidhost.ru/search.html
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse

ante0 said:
He did already
Click to expand...
Click to collapse
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone

davideakc said:
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
Click to expand...
Click to collapse
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.

ante0 said:
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
Click to expand...
Click to collapse
Don't worry, thanks for the fast reply!

davideakc said:
Don't worry, thanks for the fast reply!
Click to expand...
Click to collapse
I can't find any TWRP with decryption. This one might work, it's from the MorfuZ thread: https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
So it may or may not have working decryption. But if you have an external SD it doesn't really matter as you'd only transfer magisk to that.
Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download latest stable.
Flash twrp using fastboot.
Reboot to recovery.
Transfer magisk zip to external SD.
Flash Magisk zip using the Install button
You will probably have to browse to /external_sd manually as it will default to /sdcard in the install browser.
If it fails to install using TWRP:
Open terminal in TWRP from the Advanced button then enter this command:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
This will dump your stock ramdisk to external sd, which you then can patch in Magisk Manager and flash the output file to 'ramdisk' using fastboot. You will have to install Magisk Manager apk first though, it can be found in the Magisk thread.

davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*

bozka1 said:
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!ot8TGIIa!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
Click to expand...
Click to collapse
If I do this, I lost all apps and data or not?

davideakc said:
If I do this, I lost all apps and data or not?
Click to expand...
Click to collapse
No you won't, but you should always backup your data.

AztekSoul said:
No you won't, but you should always backup your data.
Click to expand...
Click to collapse
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?

davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Yes you can, although you have to download updates through firmware finder and update with HuRUpdater in twrp.

davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.

bozka1 said:
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
Click to expand...
Click to collapse
After that, how can I restore factory eRecovery?

davideakc said:
After that, how can I restore factory eRecovery?
Click to expand...
Click to collapse
Okay, one can install Magisk without TWRP. There are plenty of guides on how to do these things in the Mate 10 forums. Of course, TWRP makes things easier ....

Message of dm-verity on TWRP Recovery website

I'm using android Pie(stock rom) on mi a1. I want to flash Lineageos for microG. On TWRP Recovery website, it says this device(mi a1-tissot) uses dm-verity and in order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in fastboot.
I'm completely new in the realm of flashing custom roms. And no website and youtube video talks about dm-verity in a clear manner:crying:. So what steps exactly should I follow to install Lineageos for microG?
Also, my phone(data) is encrypted. And I can't find a way to decrypt it. Will it affect flashing TWRP Recovery or Lineageos?

wHY did not anybody answer guys?

Here are the steps to install TWRP and maybe a custom ROM:
1.Make sure to have USB Debugging activated
2.Put the Mi A1 in Fastboot Mode(Volume Down+Power)
3.Connect your phone to your PC
4.Make sure to have downloaded platform-tools
5.Download the .img TWRP file and copy it in the platform-tools folder
6.Hold Shift and right Click in the platform-tools folder,and click onpen a PowerShell window here
7.Type fastboot devices or .\fastboot devices(for me the second worked)
8.Now write fastboot boot twrp.xx.xx.xx.img(here Goes the name of your .img TWRP file)
9.After 15 seconds,you will probably see a warning that asks You to swipe to allow modifications.Don't swipe.Press on:Keep read only.
10.From this point,You can install every custom ROM,You can install Magisk.
Hope this helped You out!

TheAlmigthyOne said:
Here are the steps to install TWRP and maybe a custom ROM:
1.Make sure to have USB Debugging activated
2.Put the Mi A1 in Fastboot Mode(Volume Down+Power)
3.Connect your phone to your PC
4.Make sure to have downloaded platform-tools
5.Download the .img TWRP file and copy it in the platform-tools folder
6.Hold Shift and right Click in the platform-tools folder,and click onpen a PowerShell window here
7.Type fastboot devices or .\fastboot devices(for me the second worked)
8.Now write fastboot boot twrp.xx.xx.xx.img(here Goes the name of your .img TWRP file)
9.After 15 seconds,you will probably see a warning that asks You to swipe to allow modifications.Don't swipe.Press on:Keep read only.
10.From this point,You can install every custom ROM,You can install Magisk.
Hope this helped You out!
Click to expand...
Click to collapse
I found this thread by doing something wrong that you mentioned. I didn't swipe to allow modifications and now the TWRP can't flash anything. Tried every remedy I can find but nothing. It can wipe system though, but not restore it so now I'm stuck in bootloops. Damn, idk what to do.

Dear Zentom,for me,that method worked.But,I can help you get out of that situation
1.Make sure to have your bootloader unlocked
2.Download the stock ROM for Mi A1
3.Boot into Fastboot Mode
4.Extract the stock ROM archive
5.Copy all the extracted files into the platform-tools folder
6.Find a .bat file names "flash-all"
7.Open it
8.After 15 minutes or so,your phone will boot.
Hope I helped you!

TheAlmigthyOne said:
Dear Zentom,for me,that method worked.But,I can help you get out of that situation
1.Make sure to have your bootloader unlocked
2.Download the stock ROM for Mi A1
3.Boot into Fastboot Mode
4.Extract the stock ROM archive
5.Copy all the extracted files into the platform-tools folder
6.Find a .bat file names "flash-all"
7.Open it
8.After 15 minutes or so,your phone will boot.
Hope I helped you!
Click to expand...
Click to collapse
Thanks, but I flashed the stock rom from twrp anyway. Though I had to flash the October 2019 ROM. Do you know anywhere where one can get an updated one?

If You want the latest stock ROM,this is:https://drive.google.com/file/d/1yVWv4hiTSk-3zai-4u2c2OcLpRdFL_J6/view

Database Users

welcome