Database Users

Mi A1 not recognized in Fastboot(?!)

I *just bought Mi A1, and I want the Night Light feature. And the blue accents (I love it).
I enabled OEM unlocking, enabled USB debugging. adb recognized my phone, and I rebooted it to bootloader (fastboot).
HOWEVER, fastboot devices brought up no devices - the phone is not being recognized.
I used the AIO tool here, and I'm getting the same results. Interestingly, when I reboot to the bootloader, the phone switches off after 30 seconds or so, and instead starts charging (cuz it's connected to my laptop) but it stays in fastboot if I use Vol - and power button.
I could be missing USB drivers, I supposed. I had installed drivers from the AIO tool, am I missing something?
Help appreciated, thanks!

If phone switches off/reboots in fastboot mode, it usually means that drivers are installed incorrectly. Find phone in device manager and install drivers manually from there.

_mysiak_ said:
If phone switches off/reboots in fastboot mode, it usually means that drivers are installed incorrectly. Find phone in device manager and install drivers manually from there.
Click to expand...
Click to collapse
Thanks! Where can I download the drivers? Through Windows update itself or from any other source?

kvn95ss said:
Thanks! Where can I download the drivers? Through Windows update itself or from any other source?
Click to expand...
Click to collapse
For example here and just follow the video guide in the post for both ADB and Fastboot drivers installation.

With your phone in fastboot mode, look in device manager, there is probably a device that does not have drivers. If you have already installed them, you can try having Windows search for them. Then you would validate by doing a fastboot devices command from command prompt.

I have managed to get it working, I've flashed TWRP, however it goes into a bootloop with linux penguin, then a white background with Google colors and an open lock at the bottom, reading "Unlocked".
Strangely, if I flash TWRP with the AIO tool, the phone boots into system rather than loading into TWRP ?
Any reason for the peculiarity!?
Also, I can't reboot the phone.
And for some reason, my phone is encrypted!

Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk..
Why do you want to keep phone decrypted? There is zero performance hit with encryption and it's, well, more secure

_mysiak_ said:
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk.
Click to expand...
Click to collapse
Oohh.. okay. Right now I'm downloading the Dec. update. I'll flash that with MiFlash tool (saving the user data) and then install Magisk with TWRP.
Before that, should I try flashing stock recovery?
Why do you want to keep phone decrypted? There is zero performance hit with encryption and it's, well, more secure
Click to expand...
Click to collapse
Well... I thought that the encryption is preventing my phone from booting. Strangely, flashing TWRP 3.2 using the AIO boots my phone to system, so at least I can use my phone.

_mysiak_ said:
Don't flash TWRP, just boot into it when you need it. From what I read you can't have TWRP + Magisk installed at the same time, so IMHO it's not worth the effort. Personally I use TWRP only to install Magisk.
Click to expand...
Click to collapse
ALSO, do I have to install magisk on both the slots?

I suppose that you want to root your system in the easiest possible way, I'd suggest:
1. flash December fastboot ROM (MiFlash or via fastboot directly, keep user data). This will flash full December ROM to BOTH slots and set slot A as active. At this point you have fully stock device.
2. unlock bootloader
3. fastboot into TWRP
4. flash Magisk
That's it. Magisk will be installed only into the active slot A. There is probably no reason to install it also in slot B. If you want to return to stock, it is enough to restore boot.img, either from Magisk app directly, or via fastboot.

_mysiak_ said:
I suppose that you want to root your system in the easiest possible way, I'd suggest:
1. flash December fastboot ROM (MiFlash or via fastboot directly, keep user data). This will flash full December ROM to BOTH slots and set slot A as active. At this point you have fully stock device.
2. unlock bootloader
3. fastboot into TWRP
4. flash Magisk
That's it. Magisk will be installed only into the active slot A. There is probably no reason to install it also in slot B. If you want to return to stock, it is enough to restore boot.img, either from Magisk app directly, or via fastboot.
Click to expand...
Click to collapse
So, I flashed the December fastboot ROM, unlocked my bootloader, booted to TWRP and installed Magisk v14 (latest). It installed without issues, but when I try to boot, it goes into a boot loop.
Also, when I boot using TWRP (no modifications) my hotspot doesn't seem to work, I have to restart my phone to fix it.
Well, I guess I'll try it once more...

Damn, it worked! Magisk installed and phone boots well. The phone gives a warning before booting, that it can't be checked for corruption (probably because of the unlocking I guess).
Now, onto installing the Magisk module which gives me to use GCAM (HAL3) and nightlight.

Just a note, Magisk v14 doesn't work well with dual partitions, this might explain strange behavior. Use official Magisk beta v 14.4 or 14.5.

* * * [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

[Guide][Root] Magisk without TWRP on Android P

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! ?

One Plus 8 Pro features (Wifi / Camera) stopped working after root

I rooted my OP8-Pro. I followed the instructions in this video:
https://www.youtube.com/watch?v=UVABAEGRgew.
To summarize, his steps were as follows:
1. Unlock the bootloader
2. Extract boot.img file from payload bin file (on Windows)
3. Install Magisk Canary 2020 app on the phone
4. Install the boot.img file through Magisk
5. Download Fastboot.zip in Windows and extract files
6. Download and place magisk.patched file in Fastboot folder
7. Connect the phone to Windows, use cmd to boot into bootloader
8. Flash the magisk.patched file on the device and reboot
This is a new method to me. In the past rooting always involved TWRP. Root checker shows that the phone is rooted but other features have stopped working.
WiFi no longer works. Even if I turn it on, it turns itself off. Camera keeps crashing and I can't even change the camera mode once I launch the app. My phone also rebooted itself a couple of times while I was testing it after root.
I also rooted my One Plus 6 in 2019 but had to use a custom TWRP (Bluspark) for it to be stable.
I rather start over with a factory reset than try to repair the device in it's current state (but will try to repair it if it's easier). I prefer to stick with the factory ROM and only need root for one app.

Try latest stable magisk instead of canary. Mine works perfectly with regular magisk

I used the all in one tool by mauronafrio here. Worked flawlessly.
shagexpert said:
I rooted my OP8-Pro. I followed the instructions in this video:
https://www.youtube.com/watch?v=UVABAEGRgew.
To summarize, his steps were as follows:
1. Unlock the bootloader
2. Extract boot.img file from payload bin file (on Windows)
3. Install Magisk Canary 2020 app on the phone
4. Install the boot.img file through Magisk
5. Download Fastboot.zip in Windows and extract files
6. Download and place magisk.patched file in Fastboot folder
7. Connect the phone to Windows, use cmd to boot into bootloader
8. Flash the magisk.patched file on the device and reboot
This is a new method to me. In the past rooting always involved TWRP. Root checker shows that the phone is rooted but other features have stopped working.
WiFi no longer works. Even if I turn it on, it turns itself off. Camera keeps crashing and I can't even change the camera mode once I launch the app. My phone also rebooted itself a couple of times while I was testing it after root.
I also rooted my One Plus 6 in 2019 but had to use a custom TWRP (Bluspark) for it to be stable.
I rather start over with a factory reset than try to repair the device in it's current state (but will try to repair it if it's easier). I prefer to stick with the factory ROM and only need root for one app.
Click to expand...
Click to collapse

I used the all in one tool by mauronafrio here. Worked flawlessly.
Click to expand...
Click to collapse
So I tried that tool. I tried to flash factory image downloaded directly from One Plus website and kept getting the following error message:
"Error: flash-all.exe or flash-all.bat or flash_all.bat or flashall.bat not found!!!"
I think this has to do with the fact that I am using a secondary hard drive on my computer to store all the downloaded files and the bat file is supposed to be in the same folder as the zip file.
I also reset it to factory settings from the recovery mode but that didn't fix the WiFi issue.
Then I ran TWRP from the All in one Tool and installed the factory firmware from phone's internal memory. This soft bricked my phone.
After getting soft-bricked I installed Magisk through the tool but that didn't fix the issue.
Now it is stuck in a boot loop and keeps going into recovery mode. I can also boot into Fastboot mode and install zips through there but I would like to unbrick it first. Is there an alternative ROM that can unbrick it?

I think I am going to try and use the unbrick tool first and if that doesn't work I will try the Fastboot ROM, that already comes with the bat file.
I am a little confused as to which version goes on my phone though. They have Indian, Global and European versions but I live in the U.S. Global seems to be the most appropriate for my phone but I don't want to install the wrong ROM on it.

I remember reading that you can run into WiFi issues if you flashed the wrong version (from a different region) for your phone
I've rooted for many years and this is the first time I didn't go through TWRP as well.

If you use the unbrick tool you'll probably get issues with the fingerprint reader. But that's fixable, after you've rooted.
The easiest way to get root is to just unlock the bootloader, fastboot boot twrp (not flash), and then flash magisk 20.4 stable.
Before TWRP you had to patch the boot.img and fastboot flash it, but with twrp there is no need for it.

If you use the unbrick tool you'll probably get issues with the fingerprint reader. But that's fixable, after you've rooted.
The easiest way to get root is to just unlock the bootloader, fastboot boot twrp (not flash), and then flash magisk 20.4 stable.
Before TWRP you had to patch the boot.img and fastboot flash it, but with twrp there is no need for it.]
Click to expand...
Click to collapse
Thanks for letting me know. I attempted to use the unbrick tool but it had problems connecting to the phone. And I also didn't want to run into finger print issues.
I downloaded the patched Rom (with flash-all.bat file included) and installed it via All in one tool. That unbricked the phone and I reset the system to start from scratch. I used the global / international version for my North American phone.
After setting up the phone, I rebooted into Fastboot and loaded TWRP via All in one tool and installed Magisk 20.4 and got the phone rooted.
Root checker shows the phone is now rooted. WiFi and camera also work. I am ready to transfer data from the old phone.
This would have gone smoother if I had just used the correct version of Magisk from the start.

About to give up on flashing recovery to OOS 11.1.1.1

I tried "fastboot boot" almost all of KizuYuna's .imgs, tried fastboot boot the lineagerecovery.img. All I get is the fastboot logo and the phone just restarts into OOS... TWRP is same.
About to MSM downgrade to OOS 10 to get recovery working like I did before. Thought it would be better to flash a rom from OOS 11 to get better firmware compatibility but just wont work.

Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.

bpambrose said:
Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.
Click to expand...
Click to collapse
So you are saying MSM to 10 and then flash official 11.1.1.1 or fastboot flash boot magisk_patched-23000_11.1.1.1 (this is a full 11.1.11.1 OS flash? No need to use twrp from 10?)
Thanks

So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.

Fenopy said:
So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.
Click to expand...
Click to collapse
So you had to go through all the trouble because you had a bootloop issue when OTA updating to 11? I already got to 11 but am trying to fastboot boot a recovery because I want to flash a custom ROM... When I fastboot boot TWRP.img or LOS Recovery .img it just shows fastboot logo and restarts the phone with no recovery shown..