Database Users

[GUIDE] How to * Unlock * Flash TWRP * Root * OnePlus X [Including Oxygen 3.1.3]

Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________​
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps​
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X​
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.

Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess

I could try today evening... will update here.

@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..

Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.

I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly

Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.

CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/

Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.

Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.

CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...

Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.

mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted

Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!

Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here

mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit

CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD

Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0

ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.

@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/

(Working Method, Latest MIUI 8) - Unlock bootloader + twrp recovery + install SuperSu

How to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission on the Latest MIUI 8 - V8.0.6.0.LHOMIDG. (as of 22-11-16)
Here you have the step by step procedures to successfully unlock your Redmi Note 3 SnapDragon global variant with latest global stable rom MIUI 8. Please follow the steps carefully.
The rom used for this procedure is the latest global stable fastboot rom MIUI V8.0.6.0.LHOMIDG.
This is the working guide for the Xiaomi redmi note 3 (SD) on latest MIUI 8.0.6.0 as on 22-11-2016. I did lots of experiments, bricked my device several times to find this working guide for latest rom, however you are free to link to this page for reference.
You dont need to apply for official unlocking and wait for a month or more to get the sms confirmation from xiaomi to officially unlock the bootloader, the problem with the official method is many users have reported that they did not receive the confirmation sms from xiaomi, even if they receive the confirmation sms the unlocking process stucks at some percentage and fails to unlock the bootloader. So for everyone here is the easy way to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission.
First of all take a backup of all important files from your phone to your PC before starting. Because all data will be formatted while flashing the rom.
I have simplified most of the procedures and complicated works for this guide. A good part of the credit goes to some other developers because their works were helpful to me for experimenting to find this working full unlocking guide for the latest miui rom for redmi note 3 (SD) as of 22-11-2016.
REQUIREMENTS:
Xiaomi Redmi Note 3 (SD) Mobile
Micro USB data cable (or) compatible usb cable
Desktop or Laptop (Widows based)
Download all the tools, rom and other files from this androidfilehost folder link and keep all files in one folder for easy access:
https://www.androidfilehost.com/?w=files&flid=137618​Files List:
1. AnF.zip
2. fastboot_edl.zip
3. Fastboot Rom: "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz"
4. MiFLash_v2016.08.30.0.zip
5. minimal_adb_fastboot_v1.4_setup _working.exe
6. MiPcSuiteSetup_v3.2.1.3111_2717.exe
7. Root Checker Basic v5.9.7.apk
8. SR1-SuperSU-v2.78-SR1-20160915123031.zip
9. twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip
10. ADBdriversetup.zip (alternate use, in case device specific drivers are not properly installed)​
***Carefully remove your sim card & sd card from mobile (if inserted) before you begin and do not connect to internet until all steps are completed, because the phone would automatically sync with Xiaomi servers at first boot and may cause problems.
Make sure your phone is charged 60% and above.
The complete video go through of step by step procedures in this guide is available in this YouTube video,
https://www.youtube.com/watch?v=rj4gVMk3y0o​
FOLLOW THE STEPS CAREFULLY, IF YOU FACE ANY TROUBLE, START OVER AGAIN FROM STEP 1, IF YOU FACE ANY OTHER ERROR OR BOOTLOOP OR STUCK IN LOGO LOOK AT THE TROUBLE SHOOT SECTION AT THE BOTTOM.
Step 1:
Enable Usb Debugging, if not done before:
Open Settings in your device"Redmi note 3 (SD)", scroll to bottom in settings and click on "About phone" and now tap on MIUI version 7 times, it will show a message like "You are now a developer" and Developer options will be revealed.
Next go back to Settings main screen and then -> Additional settings -> Developer options -> Enable Developer options, Enable OEM Unlock, Usb Debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: After that when you connect your phone to the Pc to execute adb commands, a prompt may appear on your phone with computer's fingerprint key, you should confirm it when it appears. In case if you already done this for your computer with proper adb drivers installed, you don't need to bother about this.
Step 2:
DISABLE DRIVER SIGNATURE ENFORCEMENT IN YOUR PC:
You now have to disable driver signature enforcement in your PC, to do this you have to open the settings window by pressing the shortcuts"Windows button + i -> Update & Security -> Recovery -> Advanced startup -> Restart now. Now the system will logout and show Recovery options, from there select Troubleshoot -> Startup Settings in Advanced options -> Restart. Your system will now reboot and show the "Startup settings" screen, a list of options will be available, you have to choose option number 7 to disable driver signature enforcement. Then the system will boot into the OS with driver signature enforcement disabled. After that do not restart your pc until all the below steps are completed, in case if you restart your pc for any reason you need to redo this step again because system reboot might enable driver signature enforcement again. That's it. Refer this video if you need further guidance.
Step 3:
To install ADB, Fastboot and other drivers in your PC:
Install the " minimal_adb_fastboot_v1.4_setup _working " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiPcSuiteSetup_v3.2.1.3111_2717.exe " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiFLash_v2016.08.30.0.zip " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Step 4:
Extract AnF.zip file and execute the commands:
Now extract the "AnF.zip" file downloaded from the link I provided above. Connect your phone to Pc using the Usb cable. Open the extracted AnF folder and double click on the cmd.exe file, which will open a adb command window from there.
Execute the below command through adb command window to check and confirm the phone is connected via adb interface. If connected properly it should show device serial like "******** device"
adb devices​
Incase if your phone shows a prompt for computer's fingerprint key approval, allow it. Then execute the command again. You should see your phone serial number as shown in the image below, which means your phone is properly connected via adb. Incase if the device is not connect properly via adb, disable and enable USB debugging on your phone. If that also helping to install the phone's adb drivers, extract and run the"ADBdriversetup.zip" downloaded from the link I provided above to install the specific drivers for your phone.
Step 5:
Reboot the phone to EDL mode:
Now you have to reboot your phone to edl mode aka Emergency download mode. To do this execute the below command via adb window with phone still connected to Pc.
adb reboot edl​
Your phone will now reboot into blank screen or edl mode and new driver named "qshusb qloader 9008" will be installed in your Pc, now only red led notification light will be blinking on your phone. Once the driver is installed properly, the phone is now connected in edl mode. Now close the adb command window.
Step 6:
Setup MiFlash Tool & Flash the ROM:
Open the MiFlash tool (MiFLash_v2016.08.30.0.zip) application you installed earlier, click refresh button and your phone will be visible as port number (ex: COM10) in MiFlash tool. Exe file is in this path,"C:\Xiaomi\XiaoMiFlash"
Now extract the "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz" fastboot rom file downloaded from the link I provided above. In your MiFlash tool window, click the Browse button and locate the extracted fastboot rom folder. Then select "clean all" button at the bottom of MiFlash window. The flash tool is now configured. Now click the Flash button.
Wait for few minutes for the flashing process to complete, once the process is complete and MiFlash tool window will show task finished. But do not disconnect the phone.
Step 7:
Reboot to Fastboot mode & execute Fastboot commands:
Now while the phone is still connected to your pc, reboot your phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the boot screen and release, the phone will now enter into fastboot mode.
Now double click and open the cmd.exe file from AnF folder you extracted earlier to open the command window. Then execute the below command.
fastboot oem device-info​
This command will show you the current bootloader status. The bootloader status shows "Device Unlocked: False", execute the below command in command widow, it will Unlock the bootloader.
fastboot oem unlock-go​
Your device might restart now, if restarts press Volume down button and Power button simultaneously to reboot phone to fastboot mode again to check your bootloader status again by executing the below command. It should show "Device Unlocked: True" in the command window. Which means the device's bootloader is unlocked.
fastboot oem device-info​
Now to flash TWRP recovery and Supersu for root permissions, jump to step 8, or if your aim is to unlock the bootloader only, you may restart your phone and skip all below steps.
Step 8:
Flash TWRP:
Now restart phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the fastboot screen.
Extract the "twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip" file downloaded from the link I provided above to the AnF folder.
Then open the AnF folder, double click and open the cmd.exe file, paste the below command in the command window to flash twrp recovery.
fastboot flash recovery twrp-3.0.2-2-kenzo.img​
After flashing the recovery image reboot the phone to TWRP recovery by pressing Volume Up button and Power button simultaneously until you see the boot screen. It will boot the phone into TWRP recovery, on the front screen just swipe the slider to mount system as read only. That's it now to flash supersu proceed to step 9.
Step 9:
Flash SuperSu:
While the phone is in TWRP recovery connect the phone to Pc, it will be detected as mass storage device, just copy the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" file downloaded from the link I provided above to your phone's mass storage device.
On the twrp menu click on Install option and locate the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" to install via twrp, now swipe the slider to right to install supersu to have root access in your phone's OS and then wipe dalvik cache using the button below in twrp.
If twrp shows any read/write error while flashing supersu, on the twrp mainscreen choose mount option and click on system in the next menu, then go back to main screen and try again to install.
That's it, now supersu is installed, to check the root status follow to step 10.
Step 10:
Check root status:
After completing all the steps successfully, reboot the phone into the system normally and complete the initial setup without Sim card, the first boot may take a little more time to boot into OS, In case if the phone stuck in boot screen for very long(10+ mins), go to troubleshoot section at the bottom and start over the steps. Otherwise you are good to go.
Connect device to Pc after initial setup completes, now copy the "Root Checker.apk" file to your phone and install it, open the root checker app and click on verify root, you will be prompted by Supersu for root permission, allow it, your root access will be verified. Voila, you have successfully rooted, flashed twrp and installed supersu on your Redmi Note 3 with latest rom installed.
That's it. Now you are ready to rock.
KNOWN ISSUES:
No issues found so far, in case if you find any issues after successfully unlocking using the above method, kindly let me know.
After successfully unlocking your bootloader, incase if you update your rom via official updates, your will lose root access and twrp custom recovery and may end up with locked bootloader again, if you face this situation by some reason, you may start over and follow this guide from step 1 to revert back to unlocked bootloader. Do not update the rom and turn off automatic updates in settings as a precautionary measure.
Troubleshoot:
If your device gets bricked or Stuck in Boot logo, try this,
Reboot your phone into edl mode by following below step.
If you are stuck on bootscreen, you may not be able to enter into edl mode using the normal method above because of bootloop or Stuck in Boot logo, in that case try this method to enter into edl mode from fastboot, download "fastboot_edl.zip" file from the link I provided above, extract the zip file and open the extracted folder, connect the phone to your Pc in fastboot mode(vol down + power), double click and run this file "edl.cmd", the phone will automatically enter into edl mode if the phone's drivers and adb drivers are installed properly.​Now follow step 6 and follow on from this step.​
If QHUSB_BULK drivers are not properly installed while the phone in edl mode,
If QHUSB_BULK drivers are not installed while the phone in edl mode, your device may not be visible in MiFlash tool(ex:COM10) even after you click refresh button, in this case open the device manager in your Pc, the phone will be visible as QHUSB_BULK with some alert sign, right click on it and select Update driver software. Then click browse my computer and browse to the location of the driver files in path "C:\Program Files\Xiaomi\MiPhone\Qualcomm\Driver" and proceed and when prompted to Install this Driver Software anyway, allow it and complete the driver installation. Now open MiFash tool and click refresh button your device will be detected in MiFash tool, now you can flash the fastboot rom by following the steps above.​

Does this work for Kate version also? OP doesn't specify

Will I lose my warranty by using this method of bootloader unlock?

This method still works for Global Snapdragon phone. Finally got it last night after 2 days of torture (I didn't sleep).
The important part is firstly the image with the modified file you are going to flash to the phone. Here he is using v8.0.6.0 which is the newest (and now last) update for android 5.1 (which is needed, phone will not flash 6.0 without a proper Cache and data clear). I ended up using version 7.3.2.0 which is 1 patch before the version my phone came with (7.3.7.0). Then I replaced emmc_appsboot.mbn with the one from here then flashed the file in EDL mode.
After the flash is done is just as important I found. You place it in fastboot mode (power button + vol down) and run a script. I wasn't able to manually unlock the device via cmd line 'fastboot oem unlock-go'. Instead I found a script that worked from here called 'Root_Folder' (this site also has majority of the files needed). You use the script called 'Root' in the folder to finish the unlock. Notice there is a 'recovery.img' in the folder as well, I replaced it with ZCX TWRP.
Now run through the script after the flash in fastboot mode. Follow the instructions from script, sometimes you take cable out or force phone back into fastboot mode. The key goal here is to have the script boot into TWRP in the end. If this happens you can do all that's needed now.
Another thing I noticed was you have to give debug permission to computer your using and save permission. Debug mode/oem unlock - connect cable, on phone you should get a prompt to accept PC and save permission. If you don't get this prompt make sure you have ADB and Fastboot installed.
Important steps are:
1. Phone connect to computer via debug/oem mode.
2. Flash correct modified ROM with MiFlash in EDL mode.
3. Once flash is done hold power and volume down button for fastboot mode.
4. Run script to attempt to unlock bootloader and/or install TWRP.
MikeyLee said:
Does this work for Kate version also? OP doesn't specify
Click to expand...
Click to collapse
You would have to look it up for Kate specifically. If anything at all that changes it's the Image you use to flash the phone.
zeon321 said:
Will I lose my warranty by using this method of bootloader unlock?
Click to expand...
Click to collapse
Don't think so. You don't 'officially unlock it' and you can flash a stock image that relocks the phone automatically.

Thank you works 100% !!!! :laugh:

After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.

zeon321 said:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
Click to expand...
Click to collapse
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).

Narcle said:
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Click to expand...
Click to collapse
Thanks, I flashed old version of twrp and formatted the storage. Now phone is working fine.

Can i use this tuto on a Redmi note 4 MTK?

Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !!

Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !! @Sci Subi

Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html

W7nstroll said:
Can i use this tuto on a Redmi note 4 MTK?
Click to expand...
Click to collapse
This method is for Redmi Note 3 pro, (Kenzo) variant.

can i use it for global stable 8.2.3 ??

The heart of this - the unofficial bootloader unlock - are taken from: http://en.miui.com/thread-345728-1-1.html (It's generally polite to link your sources).
This _does_ work on `kate`. However, this is using a modified 'emmc_appsboot.mbn'. If you flash an original emmc_appsboot.mbn, you may well find your bootloader no longer unlocked and you needing to reflash your device back to stock.
Also, for those wanting to use it on kate (because Xiaomi seems singularly incompetent when it comes to supporting the official bootloader unlock for that devcie): your device will identify itself as a kenzo, so you may have trouble flashing things like the 'miuifirmware_x.zip' updates for kate. Also, those 'miuifirmware_x.zip' files often include the emmc_appsboot.mbn, so be careful.
On another note, if anyone has an actual infallible method to get an official bootloader unlock for the kate device, please let me know.

Can I use this method for 2GB / 16 GB version of Redmi Note 3 Pro (Snapdragon)?
Thanks

Works Thanks
Tested On 18/05/17
This method works But You are stuck on a older rom with no OTA/Later Updates. Method Does not work with MM Roms.(Maybe with different emmc_appsboot.mbn it would work.
Some Pointers
I was on MIUI8 before using this.
1. This downgrades your ROM from the latest ROM, therefore Points to follow.
2. Use This Method Instead Works with latest firmware as on date.

Works, Simply Nicely Perfectly Done, Just follow the steps things will never goes wrong. :highfive:

Sci Subi said:
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
Click to expand...
Click to collapse
hi my phone was on miui 8 marshmallow i used the above method nd flashed the rom ( rom is 5.1.1) which is given after that unlocked bootloader nd installed twrp also but now i downloaded a new rom nd i want to flash it i placed the rom in micro sd card nd wiped everything in phone nd flashed the rom with gapps now phone boots but its stuck at the boot logo of the rom i also tried many other roms of 7.1.1 but same is happening phone is not going ahead its stuck in the rom boot logo what should i do also when i flashed that given rom when i charge the phone the red light blinks which seems like edl light help me out of this !! thanks in advance !!

You have flashed a recovery rom and that's why you are in bootloop.
Try to flash in EDL mode a fastboot rom.
PS: Hope you haven't tried to downgrade already because you can loose IMEI and baseband.

[Help] Fastboot mode missing?

I have A2017G, came with MM. I unlocked the bootloader, flashed TWRP and rooted, then flashed Nougat B04 and the corresponding B04 boot.img (was that necessary?)...
IIRC, TWRP came up once, but was then replaced with the stock recovery. I went to flash TWRP again, but the bootloader seems screwy. I get this screen for a few seconds:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I touch the volume in time, this comes up:
But if I select fastboot, it just goes back to the first screen, then boots up after a few seconds. ADB shows no fastboot device on either of these screens. Hours of googling has gotten me nowhere...
The stock recovery will let me sideload a zip, but I gather it's no help with a img. OEM unlocking in developer options is greyed out; stuck on.

Select Fastboot and if the first screen comes again press the power button to continue and it wait it should boot itself to fastboot.
Or activate adb in the developers settings and type ADB reboot fastboot in ADB on Windows or Linux

I ended up with this too after trying to flash a custom rom, my just kept cycling around and around. I could not access any recovery.
I rescued mine from this point using the Miflash app and an edl package.
"DM verity enforcing" is what you need disable if you can get back to twrp. (Nfound has a twrp with all your needs covered)
Or try Voenix suggestion
I hope this helps
Edit: this is my rescue guide
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700

Kimmoth said:
I have A2017G, came with MM. I unlocked the bootloader, flashed TWRP and rooted, then flashed Nougat B04 and the corresponding B04 boot.img (was that necessary?)...
IIRC, TWRP came up once, but was then replaced with the stock recovery. I went to flash TWRP again, but the bootloader seems screwy. I get this screen for a few seconds:
If I touch the volume in time, this comes up:
But if I select fastboot, it just goes back to the first screen, then boots up after a few seconds. ADB shows no fastboot device on either of these screens. Hours of googling has gotten me nowhere...
The stock recovery will let me sideload a zip, but I gather it's no help with a img. OEM unlocking in developer options is greyed out; stuck on.
Click to expand...
Click to collapse
I'll make it quick: No fastboot, but you don't need it really. Just use EDL. You can install TWRP via EDL Tool or axon7tool.exe
axon7tool is finicky and hasn't got a GUI so you should try with edl tool first.
Download EDL Tool and TWRP, follow instructions on how to set up edl tool, put the twrp .img on Flash - Recovery (rename it to recovery.img just in case [BE SURE that show file name extensions is enabled]) then flash. Then reboot the phone, AND ENTER TWRP (otherwise it'll get replaced). simply reboot the phone after twrp is flashed and select "recovery" from the 5 seconds screen on boot.
Once you're in TWRP you simply have to flash Magisk to avoid losing it again, if you are on stock N firmware you should flash Magisk 16.7 (17.1 will bootloop). But I recommend that you format data (Wipe - Format data) and THEN flash magisk, so that you unencrypt the internal storage and don't lose it if you change your ROM or whatever

Choose an username... said:
Download EDL Tool and TWRP, follow instructions on how to set up edl tool, put the twrp .img on Flash - Recovery (rename it to recovery.img just in case [BE SURE that show file name extensions is enabled]) then flash. Then reboot the phone, AND ENTER TWRP (otherwise it'll get replaced). simply reboot the phone after twrp is flashed and select "recovery" from the 5 seconds screen on boot.
Click to expand...
Click to collapse
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Once you're in TWRP you simply have to flash Magisk to avoid losing it again, if you are on stock N firmware you should flash Magisk 16.7 (17.1 will bootloop). But I recommend that you format data (Wipe - Format data) and THEN flash magisk, so that you unencrypt the internal storage and don't lose it if you change your ROM or whatever
Click to expand...
Click to collapse
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?

You need to enter,
"DM verity enforcing" in twrp advanced settings.
To remove corruption message.
NFound has a twrp with a specific advanced setting for this.

Kimmoth said:
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
Click to expand...
Click to collapse
The password is because data is corrupted - the system tries to unencrypt it but it isn't encrypted. You just have to format data again (If you have the error, it might be hard - try unmounting and mounting data, or changing its filesystem, it might work. If it doesn't, you'll have to install Fastboot (if it is a G, you can use Raystef's zip from the bottom of this post) and go to it, then do "fastboot erase userdata", it usually works.
And that screen is the 5 seconds screen, you should leave it there, it's useful. Only way to enter Fastboot without commands, plus you can also enter recovery and stuff
also, flash magisk AFTER formatting. I think Magisk Manager is installed in /data so you are essentially removing it
https://www.google.com.ar/url?sa=t&...FjAAegQIBhAB&usg=AOvVaw0mLcRna7wHd0MBSXcBI3sr

So I installed Nfound's TWRP, allowed it to modify the system, disabled DM verity enforcing, and that damn message still comes up (it also shows up instead of fastboot, and choosing fastboot gets me no fastboot), and what's more, now I just get a little linux penguin instead of the boot animation, which just sits there forever, even after re-flashing the ROM...

Check the comments here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
I'm not sure which ROM you are installing, this one is Lineage Os 15.1.
Check this twrp
https://forum.xda-developers.com/axon-7/development/twrp-3-1-0-2-t3591075
You may have to "delete inscription" too
I hope this helps.

I've flashed this rom: A2017G-N-B04 (australian) from here: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Is it it necessary to flash the boot.img that's listed with it, or is that included in the rom zip, or can you run a different one?
I tried adb reboot "dm-verity enforcing" from the pc, and typing reboot "dm-verity enforcing" straight into the terminal on twrp, and the phone rebooted both times but the same 'your device software can't be checked for corruption' thing still comes up...
Is there some way I can wipe the slate clean and start fresh? Something seems a bit off. I'm trying to install Xposed (I have the right one, sdk25-arm64), but when I flash it the phone just hangs at the end of the boot animation.
I could really use a comprehensive primer on all this business... I kind of half get the hang of it, then it's a year or so until I need to do it again, and I've forgotten most of what I learned the last time, with some portion of it that's become obsolete anyway... I feel like I'm groping in the dark here.

Check this post
https://forum.xda-developers.com/axon-7/help/encryption-password-boot-t3667446
Here flashing the ROM and doing a factory reset.
I'm in Australia too (running A2017G) and if you use the wrong software it can cause grief.
Did you flash all 3 files recovery, boot and firmware
From Raysteffs post? If not, you should.
I soft bricked mine by accident and recovered it with a stock edl package.
Edl has all the IMG files needed
Recovery (stock) fast boot, splash, firmware (usually 3 IMG files) and all associated.
I'm currently running B15 Oreo Chinese global (switched modem files to work here in Oz)
I would go back to as stock as possible to restart then use the Axon7 tool kit
Toolkit is here
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
If you mix and match recovery, boot and ROMs this can lead you too bootloop or system hangs because its looking for associated files that aren't there.
Sometimes 1 file can make all the difference.
Good luck, I hope you get it sorted

Kimmoth said:
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
Click to expand...
Click to collapse
This just worked for me too!

LineageOS starts booting, but then phone goes to Qualcomm Crash Dump Mode

Hello,
I am new to phone rooting/modding, this is my first time trying to install a custom ROM (lineageOS) to my OnePlus 8 Pro.
First, I followed this guide for rooting, installing TWRP and then Magisk. The only different thing that I did was, when flashing TWRP, not usingfastboot flash recovery twrp-image-filename.img, but fastboot flash recovery_a/b twrp-image-filename.img, because I read that the former may lead to a boot loop.
Everything worked. Then I proceeded to Install LineageOS on instantnoodlep, where it said I needed to upgrade my stock OS to Oxygen 11/Android 11 first (it came with O10/A10). I did that successfully.
However, it turned out that O11/A11 had overwritten TWRP with the stock recovery. So I flashed TWRP again. This too was successful.
I decided not to install the LineageOS with the LineageOS recovery, as in the official guide, but through TWRP. I copied the LineageOS image to phone memory, booted to TWRP, selected Wipe and did a Factory Reset - Wipes Data, Cache and Dalvik (DID NOT choose Advanced Wipe, probably this was the problem?)
After the reset, I selected the LineageOS ZIP file and installed it.
After booting to system, LineageOS starts loading, but after 4-5 mins I see
QUALCOMM CrashDump Mode
--------------------------------------------------
Panic requested on external modem boot failure
mdm_force_reset
Any help for getting out of this?
It will be MUCH appreciated.

Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.

Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.

MaybeDontAsk said:
Anyways if you want to re unlock the bootloader you can always reboot into the bootloader and do fastboot oem unlock. Then to flash twrp you can always do fastboot flash recovery (drag and drop the recovery image here) then sideload magisk.zip! Any errors like always tell me.
Click to expand...
Click to collapse
The unlock command would be:
Code:
fastboot flashing unlock

Thanks for the suggestions, I will try them when I get to my home PC, I'm at work now.
In the meantime: can someone explain to me what is the exact procedure for installing LineageOS with the latest TWRP image? More specifically, which options in "Advanced Wipe" should be checked, because in all the tutorials I found they were using old versions of TWRP which did not include the "system" option. Mine had it, so I decided not to use Advanced Wipe at all and use the default wipe options (this is also what they did in one of the tutorials). Could this be the cause for the crash dump error?
Also, I am kind of reluctant to re-lock the bootloader and go back to stock OxygenOS. I still have access to the (LineageOS) recovery mode (it overwrote TWRP). Can I try doing something from there, like maybe overwriting it with TWRP again, then wiping everything (the right way) and installing LineageOS again?

Well when ever I get a Qualcomm crash dump error I always like to go back to stock and re do everything fresh just in case something else goes wrong but if you just don't wanna go back to stock you can do this:
If you wanna overwrite lineage os recovery you can reboot into the bootloader, and just do fastboot flash recovery (drag and drop twrp image here)
So it will be something like:
Code:
fastboot flash recovery C:\Users\YourUsername\Desktop\(recovery name).img
Or if you have the twrp image in the same place at platform-tools you can do:
Code:
fastboot flash recovery (recovery.img)
Or a one time twrp boot:
Code:
fastboot boot C:\Users\YourUsername\Desktop\(recovery name).img
Or:
Code:
fastboot boot (recovery name).img
But like I said it's probably better to re-lock the bootloader to start fresh then you can unlock it again and do anything else. Good Luck.
Anyways in TWRP Navigate To:
Wipe>Advanced Wipe> Dalvik/Cache>Data>swipe to wipe
Go back to TWRP home
Advanced>Adb Sideload
Now in PC cmd do:
Code:
adb sideload (drag and drop lineage os zip here)
Hit Enter And Wait Until It Finishes Flashing
Now For The Google Apps (GAPPS):
Download Nik GAPP From:
NikGApps - Custom Google Apps Package!
NikGapps Website
nikgapps.com
Select "Download"
Then look through all packages and read what each one contains, I would go with either core or basic. But you may need another apps so just read and choose.
Once you choose, click "download now"
Navigate To Folder
Releases>NikGAPPS R if lineage is 18.1(Android 11)>Latest Version>then choose from here and download.
Back to TWRP
If the download for gapps Finished:
Navigate to:
Advanced>adb sideload
Back On CMD:
Flash Gapps:
Code:
adb sideload (drag and drop NikGAPPS zip)
once it finishes:
On TWRP go back to home menu and navigate to:
Wipe>Format Data>Type "yes">Hit Enter>Go Back To TWRP Menu>Reboot>System if it says "no rom is installed" just swipe to confirm reboot, Lineage OS Is Actually Already Flashed. Good Luck!
I know this is long but it's really not lol.

@MaybeDontAsk
Thanks a lot! I will try again via TWRP first. I don't want to re-lock the bootloader just yet, because I fear something may go wrong in the process and I may end up with a bricked phone AND a locked bootloader, and that will really be the worst scenario, from what I've read in forums.
As for the GAPPS part - I don't plan to install them. Just a LineageOS image will be fine.

Alright well hope everything goes well and yeah I also feared I may end up bricking my device with the msm download tool but I've already done it multiple times.
It has fixed a lot of issues for me wether it is that the device is booting straight into recovery or fastboot or that it's not even booting up!

Just something about TWRP: when I tried just booting to it, the phone froze on the "Fastboot Mode" splash screen and stopped there. So I had to use the flash option.
Also, about flashing: I should use
Code:
fastboot flash recovery (recovery.img)
and not
Code:
fastboot flash recovery_a (recovery.img)
fastboot flash recovery_b (recovery.img)
right?
Just double checking to make sure.

Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?

freeride01 said:
Unfortunately, Wipe failed. In Advanced Wipe i chose
- Dalvik/ART Cache
- Data
and left Metadata, Internal Storage and USB OTG unchecked. (In my above post, I wrote I had "system", I meant I had Metadata instead of System in the options list).
Anyway, this is what I got:
View attachment 5543241
I forgot to mention I did a full backup before my first wipe. Should I try to restore from it now?
Click to expand...
Click to collapse
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.

MaybeDontAsk said:
I suggest to do msm download right now. It will fix every error, plus it doesn't even take long to re unlock bootloader you can just skip through the setup without wifi or Google account, no lock screen fingerprint or pin, then just enable oem unlock and reboot to bootloader unlock the bootloader then you don't need to to do setup again since you can just reboot to bootloader when its wiping by pressing volume up and down + power button then flash twrp and flash lineage or any other custom rom for the op8p.
Click to expand...
Click to collapse
Alright.
I gotta find a Windows PC though, I am on Linux/Fedora.
My OxygenOS before the wipe was 11.0.10.10.IN11BA, I guess from the list I should download "OOS 11.0.4.4", because its the latest.
I'll post again when there is some progress.

MaybeDontAsk said:
Hi, This Has Happened To Me Before On My Oneplus 8T, you basically have to download this program called msm download tool right HERE (the link is for the oneplus 8 pro) on the link select your filmware region so either: european, international or indian and download it. once you choose that choose either android 10 or 11 then follow this video (In the video the guy is using the oneplus 8t, but it will be the same for the oneplus 8 pro) This Proccess Will Revert Your Device To Stock And Bootloader Will Be Re-Locked, Good Luck! One more thing - you need to download the qualcomm drivers. if you need any more help regarding the msm download tool, booting your device to edl mode or having some issues with the qualcomm driver you can always ask me.
Click to expand...
Click to collapse
OK, I got my hands on a Windows 10 PC. I downloaded and extracted the MSM tool and watched the video you linked.
There is no Win7 version of the .exe file, so I guess I'll use the "normal" one anyway.

Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?

freeride01 said:
Yes, my phone is unbricked! Thank you VERY much!
Now, I still want to use LineageOS instead of OxygenOS. I will follow the same procedure and then your instructions for installing LineageOS via TWRP (with sideload instead of Install). I'll post about the result.
One thing that's still kind of unclear to me though. Is there any difference if I flash TWRP with the recovery or the recovery_a and recovery_b options?
Click to expand...
Click to collapse
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.

MaybeDontAsk said:
Hello, I am glad I was able to help you anyways I just recommend using recovery since I think if you do _a or _b you need to be on that partition so just do recovery so you can boot into twrp no matter on what partition you are in.
Click to expand...
Click to collapse
Hi again,
I did the whole process again and when I did adb sideload I got this:
Code:
[[email protected] phone root]$ adb sideload lineage-18.1-20220214-nightly-instantnoodlep-signed.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
Now what? There's a slide in TWRP that says "Swipe to start sideload", should I swipe it?
EDIT: Maybe Ishould use adb install as described here?

No, you need to reinstall the adb interface drivers, search up on how to do it on Linux.
Tht link you put is for installing apk directly from adb and not roms.

But adb seems to work, adb devices returns my phone ID.

It says something like "(Device ID) | Sideload?
If yes then reboot both the laptop/pc and phone.

Code:
[[email protected] phone_root]$ adb devices
List of devices attached
19356f32 recovery
(changed some digits in serial no. for privacy)

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 Ultra​Only for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?