Related
NO DEEP SH!T GUIDE TO UPGRADE BOOTLOADER​--Yes this is what it says!​
A short, Simple, No Questions ask guide to Upgrade bootloader without using fastboot or a PC and without losing your Internal Storage Data.
Steps:
Assuming that you are on OLD bootloader right now, already using OFFICIAL TWRP (compatible with old bootloader only).
Flash a rom which supports Block Based OTA or Stock ROM(oos 2.X.X). (I used PURITY ROM as i was having that only with me)
Explaination: Make sure that you are already running a rom which was using a block based OTA to install (those which have files compressed in a system.img/dat file, roms compiled by me (DU/Tesla/AICP/Broken) doesnt have it as i wanted all files to be easily extractable. Stock Oxygen OS zip scans for block size etc so its recommended you use a rom with block based ota installation)
Make sure you are having "OEM unlock" and "ADB/USB debugging" enabled in Developer options (if not, enable them first!)
Reboot to recovery > Go to MOUNT section and make sure all partitions are mounted) > Go to INSTALL and flash THIS STOCK ROM ZIP > when flashing is completed, Click on Back Button and Go to the main menu of TWRP and click on INSTALL > Click on Install/Flash image option and flash this NEW TWRP > Then click on REBOOT TO RECOVERY > Then click on REBOOT SYSTEM.
Let Stock rom boot first then enable "ADB/USB Debugging" and "oem unlock" in Developer Options
Reboot to Recovery and Flash This SuperSu Zip > Then Reboot System.
And You are done!
Now you are free to flash Any ROM or Kernel (which supports New Bootloader).
Side note:
If you are already in Trouble - unable to boot recovery/fastboot etc. then follow this Mega Unbrick Guide to Unbrick your device, (this guide will restore your device back to old LP Bootloader then follow the above guide to upgrade to New Bootloader.
I could boot into the stock os but couldn't get twrp to install...
After installing twrp and rebooting to recovery, I got a glimpse of the twrp interface, the screen flashed and then rebooted, I am back to stock recovery
So yeah went back and did the blu_spark install from PC
three0s said:
I could boot into the stock os but couldn't get twrp to install...
After installing twrp and rebooting to recovery, I got a glimpse of the twrp interface, the screen flashed and then rebooted, I am back to stock recovery
So yeah went back and did the blu_spark install from PC
Click to expand...
Click to collapse
Follow the steps properly and it will work as expected
These steps are tried and tested by many peeps and works.
Back to old!
Well this works good enough,
But can u provide a zip for going back to old bootloder, i know that flashing the whole oos 2.x.x rom does the trick but flashing a small file would be better and would save some memory and some seconds while flashing.
I'm on step 4, trying to flash the latest stock rom (OOS 3.1.4 which download from Oneplus site) and constantly gives me an error 7 during the installation. I tried to full wipe all sections, re-flash but the same error. I tried to change the "updater-script" erasing the commands, re-flash but the same error. I tried the mega unbrick guide and next your steps but again the same error. I can't understand what is going on. Everytime I manage to return to OOS 2.2.1 or a ROM with 6.0.1 version but I can't update the bootloader succesfully.
Any suggestion?
Good afternoon,
@CheckYourScreen You wrote "enable ADB/USB debugging". Why should I enable adb/usb if I have no contact with the PC? If I'm wrong so correct me please.
@three0s Maybee my Note helps you. Your OPX is oem unlockt, adb / usb driver installed so reboot in fastboot. With "fastboot devices" is your OPX hopefully detected from your PC. Now write "fastboot oem unlock". "fastboot erase recovery" will erase the Stock-Recovery. With "fastboot flash recovery your-twrp.img" the new one is installed. When you write now "fastboot reboot" so is the new Recovery installed and your System started but when you write "fastboot boot your-twrp.img" you make a reboot directly in the twrp-Recovery and you can install supersu and so on. Good Luck and, yes, my english is poor. Sorry.
mahalo
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.
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! ?
Running on a stock Pie with latest security update, I want to root my phone in order to utilize some Magisk modules, but I'm really concerned about all the "System has been destroyed" TWRP issues, it messed up my phone twice in the past.
I was wondering, could I flash Magisk just by temporarily fastbooting TWRP from the computer? Will that provide me a root access and prevent any future soft-bricking caused by the A/B partition issues?
Thanks in advance.
You can install magisk manager and patch boot image (kernel) as file from that. Than you fastboot that kernel and get temporary magisk root. After that, install permanent root from magisk manager and reboot. You dont need twrp for that.
Thank you for a suggestion, but that doesn't answer my question.
If the root is what you want, this is the best way to install magisk imho.
Hello,yes,you can temporary boot TWRP.
1.Make sure to have your bootloader unlocked
2.Make sure to have platform-tools on your PC
3.Download the latest .img file from TWRP Official Site and copy it in the platform-tools folder
4.Put your phone in Fastboot Mode(Volume Down+Power)
5.On your PC,in the platform-tools folder,hold Left Shift and press Right Click;it should appear an option namedpen a Powershell window here
6.Click on that
7.Write "fastboot devices" or ".\fastboot devices"
8. If your device appears there,you can write:fastboot boot "name of the file".img
9.It should boot in TWRP;if it asks you to swipe to allow modifications,don't do it,instead,press on Keep Read Only
From this point,you can install whatever you want.
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.