Database Users

Help with bootloop

Hi,
I did search, but I didn't find any solution to the issue. I got the Nexus 6P 64 GB.
I unlocked my bootloader using the 6p Multitool. Thereafter I used my normal method of fastboot (Minimal ADB) to flash the boot.img from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
After that I flashed TWRP. Basically I followed the instructions here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
But my phone is not booting up.
It gives me this error:
Your device software cannot be checked for corruption. Please lock the bootloader."
But I tried that and it doesn't work. I tried from fastboot restoring to factory, but get the same message.
Please help me!

Did you check the enable oem unlocking in developer settings?
Sent from my Nexus 6P using Tapatalk

Yes. As I said, I achieved the unlock. Now I just can't get back into my phone or recovery or anything other than fastboot (where it says unlock)

isn't "Your device software cannot be checked for corruption. Please lock the bootloader." the new msg on boot when you are unlocked, and you have to wait ~10 secs before it startup ?

After that, I'm stuck on the Google screen. It just goes on and on. Left it for over 20 minutes at one point and it didn't get past it.
Edit: The multicolored animated google screen. The animation just keeps going and going.

Del.

Your issue might be due to the encryption of the phone. Take a look at this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
From this thread:
NOTE: Decrypting data is not supported yet. The Nexus 6P will normally attempt to encrypt the device automatically on first boot. To use TWRP as you normally would, you will have to format data and install a slightly modified boot image with forceencrypt disabled. My Nexus 6P should arrive tomorrow and I will start working on decrypt once I get my hands on it.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

Read through that thread. Part of the issue is that I don't know which variant (MDA89D & MDB08K) I have, or how to find that out seeing as I can't boot into the phone.
If I have the variant I may be able to fix this through the unified toolkit (though I'm not sure of that)

Did you ever fix this?

Try flashing the factory image and starting from scratch. You must have messed up somewhere. Re-download the boot.img from Chainfire's thread, maybe that was corrupt or something.

1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.

kibmikey1 said:
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
Click to expand...
Click to collapse
Thank you for your reply, but I can't get into TWRP either!! Any way for me to restore to factory or do the repairs from in flashboot without the restore?

I ran into the same issue last night trying to install TWRP. I'm still not sure how to get around it but I did get my phone back. you should be able to get to the bootloader (hold the power button until phone turns off, then hold vol up+vol down+power) once there use ADB fastboot to go back to stock.
this link will walk you through what you need. follow step 7.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
here it is as well:
How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-01.31.img
radio-angler-angler-01.29.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-01.31.img
cache.img
radio-angler-angler-01.29.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash userdata C:\angler\images\userdata.img
fastboot flash vendor C:\angler\images\vendor.img

Thank you. I was eventually able to do tysonwald's suggestion. First I didn't know what my version was, so I couldn't.
At some point I was able to get into the phone with constant gapp errors, check it.
Now my phone is unlocked and rooted. But when I go to settings to security (and when I tried to set up my fingerprint) settings crashes. Any ideas?
There was still some issue. I wiped the phone with the above method again, did NOT set up twrp/root, and everything works. It was something about the custom boot image I guess. Any advice if I want to try to set it up again?

Problem solved. Needed to update to newer image before doing everything. Issue resolve from Heisenberg's thread. Thank you all!

I had the same damn issue last night. Thise bootleg instructions had me flashing build k boot.img on build D. Maybe i wasnt paying attention lol!

I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?

TeriusPR said:
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
Click to expand...
Click to collapse
Read thru this guide and follow the instructions to the T. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

I had a similar issue just now where my phone got stuck at the TWRP logo. Selecting the reboot option in download mode refused to remove it. I had to follow step 10 to get my phone back to stock. I'm afraid to try this again now

Is there anyway to know which version do i need to download? i bought the phone already bricked and i am trying to bring it back to life

How to flash back to stock kernel after using custom kernel ?

Well, Last night i tried franco kernel over my stock rom and now i want to go back to stock kernel itself. So to flash Franco kernel, i had to unlock the bootloader and installed TWRP Recovery and also rooted the phone with normal super su from chainfire website. I dunno what is systemless root cause i'm new here and never had any issues before with my old nexus device.. i'm little in knowledge regarding the Nexus 6P. So please guide me with a proper link to follow.. I googled and coudnt find the real sources.

Flash boot.img from bootloader using fastboot flash boot boot.img

sam razzy said:
Well, Last night i tried franco kernel over my stock rom and now i want to go back to stock kernel itself. So to flash Franco kernel, i had to unlock the bootloader and installed TWRP Recovery and also rooted the phone with normal super su from chainfire website. I dunno what is systemless root cause i'm new here and never had any issues before with my old nexus device.. i'm little in knowledge regarding the Nexus 6P. So please guide me with a proper link to follow.. I googled and coudnt find the real sources.
Click to expand...
Click to collapse
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I solved it by installing wugs toolkit on my PC.. Thank you..
Sent from my Nexus 6P using Tapatalk

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Should I lose TWRP by doing this command. I seem to always loose my recovery doing android updates, or now when I went back to stock kernel using your instructions, on NEXUS 6P. I just flash the recovery back, but it's still weird.

GogoAkira said:
Should I lose TWRP by doing this command. I seem to always loose my recovery doing android updates, or now when I went back to stock kernel using your instructions, on NEXUS 6P. I just flash the recovery back, but it's still weird.
Click to expand...
Click to collapse
No TWRP is in the recovery partition. This command flashes the boot partition. On losing TWRP, try flashing SU immediately following TWRP before booting to the System for the first time. Then TWRP will stick.

I did per Heisenberg's instructions, it sticks, but still I lost it after this command that's why it's weird

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
To keep root and the custom recovery (TWRP) you need to do additional steps
Code:
fastboot reboot-bootloader
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
start recovery from bootloader
install SuperSU from TWRP

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
What's in the boot.img? Will it not reset or do something on the rom? Because I just wanted to restore the kernel .

Pawnzer said:
What's in the boot.img? Will it not reset or do something on the rom? Because I just wanted to restore the kernel .
Click to expand...
Click to collapse
It is the kernel.

Heisenberg said:
Get the factory images for the correct build of your stock ROM, extract the boot.img from the archive, and flash it with fastboot:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Can it be executed via recovery, install>select image file (boot.img)>choose boot partition>swipe
Or must via fastboot mode?

EASIEST way:
(No need to connect to PC & use fastboot)
— Extract your stock rom .zip,
— Copy 'boot.img' somewhere else on internal or external SD,
— In TWRP select 'flash .img',
— Flash 'boot.img', (DO NOT REBOOT!)
— Now flash your 'recovery.img' again in recovery.
DONE.
Now if you 'reboot to recovery' you still have TWRP, when you 'reboot' you are using the stock boot.img (kernel) too, no need for PC/Fastboot.
KEEP IN MIND!.... After flashing stock boot.img you will need to flash root again AND (depending on device) may trigger 'DM-verity' and/or 'Forced Encryption' (Oxygen OS and others) if you reboot straight away, so make sure if you do NOT want this to flash/re-flash 'DM-verity & force encryption disabler' .zip (search google/the forums here - zackptg5)
Hope this helps anyone in the future.

ErbDroid said:
EASIEST way:
(No need to connect to PC & use fastboot)
— Extract your stock rom .zip,
— Copy 'boot.img' somewhere else on internal or external SD,
— In TWRP select 'flash .img',
— Flash 'boot.img', (DO NOT REBOOT!)
— Now flash your 'recovery.img' again in recovery.
DONE.
Now if you 'reboot to recovery' you still have TWRP, when you 'reboot' you are using the stock boot.img (kernel) too, no need for PC/Fastboot.
KEEP IN MIND!.... After flashing stock boot.img you will need to flash root again AND (depending on device) may trigger 'DM-verity' and/or 'Forced Encryption' (Oxygen OS and others) if you reboot straight away, so make sure if you do NOT want this to flash/re-flash 'DM-verity & force encryption disabler' .zip (search google/the forums here - zackptg5)
Hope this helps anyone in the future.
Click to expand...
Click to collapse
Thank you so much for your instruction, Doing it step by step and karnel restored to stock!

[Root] Zenfone 2 Official Android 6.0 Root + Xposed and Downgrade

**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca. If you like his work, please make him a small donation for encouragement.
2. This is a systemless root. Yet you need to unlook Lollipop before upgrading to Marshmallow.
3. Flashing the attached SuperSU file modifies stock boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** to unroot before upgrading to official Android 6.0.
Root:
1. Unlock your device in Lollipop, then upgrade to Android 6.0
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. This TWRP is recommended.
HTML:
adb reboot-bootloader
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp. /OR install the SuperSU in twrp if you saved it in device storage.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Unroot:
Just flash back stock boot.img
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: Download Xposed Installer here
Downgrade to Lollipop:
In case you need to downgrade to Lollipop, follow the instructions with care. Do it at your risk.
Refer to Asus Zentalk Forum and grab the required files from there.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot reboot-bootloader
Now you are back in Lollipop. You can flash back stock recovery(.184 recommended), wipe the device(cache/userdata/system) and then sideload back stock LP or MM as you wish. OR, you can flash custom recovery/boot/system.img start from here.
Good luck!

It worked!Thank you master!I bow now....

I just need root on 6.0.1. Is this going to achieve that?

MikeyLee said:
I just need root on 6.0.1. Is this going to achieve that?
Click to expand...
Click to collapse
According to op it will
Sent from my ASUS_Z00AD using Tapatalk

It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.

pokey006 said:
It does work, but YMMV, my phone is one of the few that works completely with the beta software. But before running fastboot cmd in adb. Use adb reboot recovery, then fastboot cmd. Phone will reboot twice after sideload of SU.
Click to expand...
Click to collapse
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?

samcjtsai said:
1. All credits go to @shakalaca and I just try to recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum but, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Works like a charm !! Thanks !!

kamyk70 said:
Hi Brother would you like be so patient and provide us with detailed toturial for less advanced users?
Click to expand...
Click to collapse
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users

when update to 6.0. bootloader unlocked again ! how can i flash twrp ?

pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.

Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
No it does not

Vouga said:
To that to work does WE need to have bootloader UNLOCKED ? just really confused atm.
Click to expand...
Click to collapse
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
He's using whats called "tethered TWRP". It's basically running twrp on your phone from your computer instead of actually installing it (which would require unlocking).
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thank You for explaining that to me, appreciated!

To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.

euthic said:
To downgrade to Lollipop, is it possible to just use AsusFlashToolInstaller and flash raw firmware? Any harms by doing that?
Thank you in advance.
Click to expand...
Click to collapse
You need to adb sideload all LP .184 images first then use Asus FlashTool to flash RAW Firmware.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

root works perfect along with systemless xposed, but i still cant pass safenet check..(super su disabled, and also xposed) so no AP.. is that normal ?

pokey006 said:
Assuming that everyone knows how to use adb and its commands
1: Well first make sure adb and drivers are on your pc.
2: Plug phone in make sure USB debugging is on
3: In adb cmd window type "adb devices" to make sure phone is recognized, if so proceed
4: type "adb reboot recovery" phone should boot into recovery with android robot on screen
5: Then type "fastboot boot <twrp.img>" twrp.img is whatever your file is named
6: phone will boot into recovery, go to adb sideload in recovery
7: type "adb sideload <SU.zip>" or whatever you have it named
8: After it's done loading reboot from recovery, it will reboot twice and the screen will say as per OP
9: After phone optimizes...enjoy root.
This is for advanced users
Click to expand...
Click to collapse
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well

ponhei9502 said:
Maybe I'm doing something wrong but my phone isn't recognised when trying to flash twrp from the dead bot before recovery? Just says waiting for device. Already checked device manager as well
Click to expand...
Click to collapse
Guess your ZF2 is not unlocked in LP first, so that you can't see twrp booting. Since you are in Android 6.0 now, try to downgrade to LP, Unlock it, upgrade to 6.0 and then root.

samcjtsai said:
**WARNING** You need to have background knowledge of adb, fastboot, twrp, sideload.. before you can go on with this thread.
1. All credits go to @shakalaca and I just recap his threads posted in Taiwan Asus Zentalk forum. Although this is reported working in the forum, as usual, do it at your risk and I won't be able to answer your questions.
2. Android 6.0 is still not unlocked. Device will be locked once you upgrade to 6.0
3. You can downgrade to Lollipop and unlock again.
4. The following SuperSU file contains a modified boot.img. In case you receive an OTA file later, do
**REMEMBER to FLASH BACK TO STOCK Android 6.0 BOOT.IMG** before upgrading to official Android 6.0.
Root:
1. Make sure your zenfone 2 is unlocked before upgrading to Android 6.0 from Lollipop.
2. Once you are in Android 6.0, fire the following command to boot twrp. <twrp.img> is the twrp recovery file. Version 2.8.7.7 is recommended.
HTML:
fastboot boot <twrp.img>
3. adb sideload the attached SuperSu file in twrp.
4. reboot system. You will see a warning screen saying "Your device has failed Verification". Ignored it and wait for the reboot.
5. Done
Xposed:
1.Flash the attached Xposed file from twrp.
2.use Material Design Xposed Installer: link
Downgrade to Lollipop:
Refer to this and get the files from the links. Note the first commnad line is the revised one by @shakalaca and it should work.
HTML:
fastboot flash token bom-token.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
Click to expand...
Click to collapse
Where are these files again? They aren't in the zip

thanks, works great, was able to downgrade to lollipop with no problem what so ever. Install twrp, gain root again, and rockin custom roms...

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.

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"
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"[/HIDE][/SIZE]
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
[/SIZE]
Click to expand...
Click to collapse
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..

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

[GUIDE] Flashing ROMs with TWRP black screen

Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings

Flash999 said:
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Click to expand...
Click to collapse
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional

Wormboymx said:
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Click to expand...
Click to collapse
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).

Flash999 said:
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Click to expand...
Click to collapse
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!

Wormboymx said:
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Click to expand...
Click to collapse
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.

mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
P.D. the encryption is when finishi whole process in the installed custom rom the hard drive doesn't work e.g... Open the camera and system say "Don't have sd card to save the files"

where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4

asad0181 said:
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
Click to expand...
Click to collapse
On this Youtube channel https://www.youtube.com/channel/UCuEtuySiR1DDYCRerutqvnA/videos
You can get some files...

Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?

chrisdlc119 said:
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
Click to expand...
Click to collapse
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.

Flash999 said:
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Click to expand...
Click to collapse
I think my display is tianman (ss atached). Is that right? Do you know if any display is affected with burning effect? It's just that I had a RN5 and I changed from MIUI to a custom ROM and one day the display just got the burning effect
Thanks for your reply.

Wormboymx said:
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
Click to expand...
Click to collapse
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?

mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Thanks! Now I could install Havoc and have access to my files!
Op you should include ,,fastboot -w" in your guide.

Finally i can boot PitchBlack recovery without Blackscreen in JDI panels::
Boot this recovery file: https://sourceforge.net/projects/pitchblack-twrp/files/jasmine_sprout/
Only one difference between the guide of this Thread....
I can´t change the partitions in PitchBlack recovery... i used the command in the op to change the partitions.... NOW i can flashed the Resurection remix rom in my phone

hlg1 said:
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
Click to expand...
Click to collapse
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?

hlg1 said:
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I made it work by doing the first 2 steps from the OP and then after booting into system the first time I booted into bootloader and then used fastboot -w. I did this with Havoc OS though so it might not work for everyone.
When I wanted root and didn't know how to get a patched boot image for my ROM, I just followed the steps to access TWRP through ADB again and then wiped cache and dalvik, afterwards I used the sideload command to flash Magisk on my phone.

hlg1 said:
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I eventually figured out that all my problems occurred because I was using old versions of ADB and fastboot. After updating to latest platform-tools (currently r28.0.2) I was able to run fastboot -w without problems. And once that worked I was able to set up a fully working system following the steps of this guide.
Thanks for a very useful guide, it saved my day!

i got failed command write failed. any suggestion?

I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me

Sarath_sh said:
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Click to expand...
Click to collapse
I'm not entirely sure I understand your question, but please note that by following the OP instructions you never flash TWRP, you just boot right into it from RAM. So should be no problem to do that while keeping stock ROM.