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/

ZUK Z1 Entered an endless restart loop

Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.

Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too too.

Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"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"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?

yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.

Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg

yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257

Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.

yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo

Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?

i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.

Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]

[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed ​
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_edl-v2.zip from Here.
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"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"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3. ​
Proof:
Thanks to @emuzychenko for the Idea!

This is AWESOME!! Just tested and worked amazingly.
Thank you!
Edit: the included command prompt didn't work for me though, launched standard and traversed to this folder

It would've been better if the source of this guide is also mentioned, just my thoughts
Sent from my Redmi Note 3 using XDA-Developers mobile app

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned
Click to expand...
Click to collapse
Especially since most of text had been copied "as is".

Please add this to op
=> https://youtu.be/-6uErg52nKs

kaushal64 said:
Please add this to op
=> https://youtu.be/-6uErg52nKs
Click to expand...
Click to collapse
I have updated the fastboot.exe and the method also. Update your video with this and I will add it to OP.

I had replaced link for modified fastboot file please add it to op.

Harish_Kumar said:
It would've been better if the source of this guide is also mentioned, just my thoughts
Click to expand...
Click to collapse
emuzychenko said:
Especially since most of text had been copied "as is".
Click to expand...
Click to collapse
Thumbs up!

This is great
My problem solved
Many thanks

not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.

BRoy_98 said:
Send me your current emmc_appsboot.mbn and I will check what is happening wrong there.
Click to expand...
Click to collapse
Where to find it?

Zarko007 said:
Where to find it?
Click to expand...
Click to collapse
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.

BRoy_98 said:
You can find it in the fastboot rom. Or if you have recovery rom, then go to the firmware-update folder in the zip there you will find it.
Click to expand...
Click to collapse
Maybe stupid question, but wouldn't phone go to edl mode (with red led flashing) before flashing rom and what then mbn file has to do? According to your manual it is the last step?
thanks

Zarko007 said:
not working for me...redmi note 3 pro sd, rom 7.2.7.0.0. it says something like "your phone enter edl mode successfully", but it simply restarts and enter Android OS...
Click to expand...
Click to collapse
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk

sator02 said:
Is your device bricked or you want to flash an official miui rom? Since your rom looks like a distributor rom not an official rom.
Sent from my kenzo using Tapatalk
Click to expand...
Click to collapse
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
Don't use this tool if your device is not bricked, your rom is a distributor rom that's why you cannot unlock your device, you have to flash miui rom prior to unlocking, you can do it thru edl mode using adb, search on miui forums and you'll find it.
Edit: check this out: http://en.miui.com/thread-235865-1-1.html
Sent from my kenzo using Tapatalk

Zarko007 said:
No, my device is not bricked, it has locked bootloader. I received code from xiaomi to unlocked bootloader but it constantly stops at 50%, and I found out that it can't be unlocked without china dev rom, but no rom can be installed with locked bootloader I only want to flash an official miui rom to be able to receive updates...Xiaomi really made this too complicated....
Click to expand...
Click to collapse
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.

BRoy_98 said:
If your device is not bricked, then you can reboot to EDL mode from adb. Do this to reboot to edl from adb:
1. Connect your device to PC.
2. Open adb and type: adb devices and press enter to see your device if it is connected properly.
3. When you can see your device ID, type: adb reboot edl and press enter. It will reboot your device to EDL mode.
4. Now flash your rom with Mi Flash.
Click to expand...
Click to collapse
I have tried it already many Times but no success...

Zarko007 said:
I have tried it already many Times but no success...
Click to expand...
Click to collapse
This must be driver problem. Install MI PC suite and it will install all necessary drivers. Then try it again.

Help please

Hello , I had my mini rooted and with recovery TWRP but is is disappeared , I can not get it open not by phisical keys nor through ADB commands , I tried to install it again with ADB but no succes , I have also tried to do a factory reset but it also does not work , it reboots as always , no changes at all , I have tried tuliptool but it doesnt work also , any idea please ???

TWRP recovery disappeared? That's new.
What about fastboot boot twrp.img
Replace twrp.img with the location of the twrp image on your PC. You need debugging mode on and unlocked bootloader for that to work.
Also have you tried flashing it again?

XDHx86 said:
TWRP recovery disappeared? That's new.
What about fastboot boot twrp.img
Replace twrp.img with the location of the twrp image on your PC. You need debugging mode on and unlocked bootloader for that to work.
Also have you tried flashing it again?
Click to expand...
Click to collapse
Hello , I can not start TWRP , instead system reboots with physical keys or ADB commands , I can not flash , through ADB ,"ADB Devices" list the phone but with any other command I only get "waiting for device "

Rafaru said:
Hello , I can not start TWRP , instead system reboots with physical keys or ADB commands , I can not flash , through ADB ,"ADB Devices" list the phone but with any other command I only get "waiting for device "
Click to expand...
Click to collapse
That's a driver problem, you can your device driver from here.
Device driver may be different from driver installed upon connecting the device, or the driver installed from the internet through windows device manager.

XDHx86 said:
That's a driver problem, you can your device driver from here.
Device driver may be different from driver installed upon connecting the device, or the driver installed from the internet through windows device manager.
Click to expand...
Click to collapse
Thanks , I will try and see

Hello XDHx86 , I have installed drivers , adb devices recognizes the phone but "fastboot boot recovery.img" states "waiting for device" , trying "adb reboot bootloader" phone system is restarted normally , seems no TWRP at all , just like using physical keys , but it was installed as i have used it many times
Edit: I have just checked device manager and on Android Device folder appear "Android ADB Interface" - "Android Bootloader Interface" and "Android Composite ADB Interface" , on all of them in properties appears "Device can not be started Code 10 "
{
"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 have also tried a factory reset from settings but device just reboots with no changes

Rafaru said:
Hello XDHx86 , I have installed drivers , adb devices recognizes the phone but "fastboot boot recovery.img" states "waiting for device" , trying "adb reboot bootloader" phone system is restarted normally , seems no TWRP at all , just like using physical keys , but it was installed as i have used it many times
Edit: I have just checked device manager and on Android Device folder appear "Android ADB Interface" - "Android Bootloader Interface" and "Android Composite ADB Interface" , on all of them in properties appears "Device can not be started Code 10 "
View attachment 5252773​
Click to expand...
Click to collapse
That command only works in fastboot mode, you need to use adb reboot bootloader first.
On a side note the command for checking devices in fastboot is fastboot devices
Rafaru said:
I have also tried a factory reset from settings but device just reboots with no changes
Click to expand...
Click to collapse
I don't know why you thought factory reset would restore recovery, you just wiped the device and lost root access if you had it.

XDHx86 said:
That command only works in fastboot mode, you need to use adb reboot bootloader first.
On a side note the command for checking devices in fastboot is fastboot devices
I don't know why you thought factory reset would restore recovery, you just wiped the device and lost root access if you had it.
Click to expand...
Click to collapse
Hi , yes I know but with adb reboot bootloader phone just boots to system does not get fastboot mode , I tried factory reset just to start all over , root , recovery and so on . but it does not work , nothing is wiped it just reboots with all data , apps....nothing is erased

Rafaru said:
Hi , yes I know but with adb reboot bootloader phone just boots to system does not get fastboot mode , I tried factory reset just to start all over , root , recovery and so on . but it does not work , nothing is wiped it just reboots with all data , apps....nothing is erased
Click to expand...
Click to collapse
Have you checked if your bootloader is unlocked?

XDHx86 said:
Have you checked if your bootloader is unlocked?
Click to expand...
Click to collapse
As far as I know it was unlocked when I bought it , at least I was told so , I have never checked myself , do not know how to

Rafaru said:
As far as I know it was unlocked when I bought it , at least I was told so , I have never checked myself , do not know how to
Click to expand...
Click to collapse
I don't think you have unlocked bootloader, but first check the driver and USB cable.
If everything seems fine then follow this thread to check bootloader status and unlock it then flashing TWRP. Or directly flashing it if your bootloader is already unlocked.

XDHx86 said:
I don't think you have unlocked bootloader, but first check the driver and USB cable.
If everything seems fine then follow this thread to check bootloader status and unlock it then flashing TWRP. Or directly flashing it if your bootloader is already unlocked.
Click to expand...
Click to collapse
I have already tried but zadig does not recognize the device , I guess it is/was open as I had TWRP and I have changed in the past the ROM , now I have Lineage 16 , I also had Lineage 14 , AOSP , I reinstalled drivers as you told me and cable is the original from ZTE and I have used it in the past to flash from this same PC , never had problems before , I guess I did something wrong and phone seems "blocked" as does not respond to ADB nor Factory reset , pc does bot recognize it , will keep trying , thansk anyway for your help

Rafaru said:
I have already tried but zadig does not recognize the device , I guess it is/was open as I had TWRP and I have changed in the past the ROM , now I have Lineage 16 , I also had Lineage 14 , AOSP , I reinstalled drivers as you told me and cable is the original from ZTE and I have used it in the past to flash from this same PC , never had problems before , I guess I did something wrong and phone seems "blocked" as does not respond to ADB nor Factory reset , pc does bot recognize it , will keep trying , thansk anyway for your help
Click to expand...
Click to collapse
How can't the tool recognize the device?
Check for the following:
Are you sure the device is in EDL mode? It should display nothing, but only a black screen and no vibrations or any indicators. Try manually rebooting to EDL mode (Volume Up + Volume Down + Power), or adb reboot edl and you should see QHSUSB_BULK unknown device or something similar in windows device manager.
Are you sure you installed the correct driver? EDL mode requires different driver than the device driver. You can get that from here. You may want to boot into test mode to install the driver properly.
Original cable can also get faulty it's in essence still a cable. Try a different cable, or get an EDL cable they're cheap.

XDHx86 said:
How can't the tool recognize the device?
Check for the following:
Are you sure the device is in EDL mode? It should display nothing, but only a black screen and no vibrations or any indicators. Try manually rebooting to EDL mode (Volume Up + Volume Down + Power), or adb reboot edl and you should see QHSUSB_BULK unknown device or something similar in windows device manager.
Are you sure you installed the correct driver? EDL mode requires different driver than the device driver. You can get that from here. You may want to boot into test mode to install the driver properly.
Original cable can also get faulty it's in essence still a cable. Try a different cable, or get an EDL cable they're cheap.
Click to expand...
Click to collapse
I have tried again , I wrote adb reboot edl , device did as you said , black screen and no sound , vibrations , I can see QHSUSB_BULK in device manager , now I ran zadig that says 0 devices found , as per tuliptool thread it should detect it and install WINUSB driver but that is not happenning , on CMD I write command as tuliptool read boot but system says tuliptool is not recognized as internal or external command .......sorry I guess is me doing something wrong
EDIT: I have managed to do at last , it says Device Unlocked : yes Device tampered : no

Rafaru said:
I have tried again , I wrote adb reboot edl , device did as you said , black screen and no sound , vibrations , I can see QHSUSB_BULK in device manager , now I ran zadig that says 0 devices found , as per tuliptool thread it should detect it and install WINUSB driver but that is not happenning , on CMD I write command as tuliptool read boot but system says tuliptool is not recognized as internal or external command .......sorry I guess is me doing something wrong
Click to expand...
Click to collapse
Manually installing the driver should do the trick. I already provided the link, and as I said: "You may have to boot the PC into test mode to install the driver properly"

XDHx86 said:
Manually installing the driver should do the trick. I already provided the link, and as I said: "You may have to boot the PC into test mode to install the driver properly"
Click to expand...
Click to collapse
it is working now , I have already confirmed that bootloader is unlocked , could you let me please know how to write TWRP please ?? tuliptool-win64.exe write recovery "filename" ?? I have tried this but says "Sending programmer...Failed to send programmer: Unknown error"
EDIT: At last I did it , TWRP installed and working , phone fully erased to start installing apps and so on , many thanks for your help

XDHx86 said:
That's a driver problem, you can your device driver from here.
Device driver may be different from driver installed upon connecting the device, or the driver installed from the internet through windows device manager.
Click to expand...
Click to collapse
Hey I'm having a similar issue. Fastboot wont work. You mentioned a driver problem. Im on linux and installed adb and fastboot. Im pretty sure i did it correctly. adb works fine, fastboot not. In the stock recovery was no option for fastboot neither in twrp. Is it possible that fastboot is disabled or not available on my device (Axon 7 mini B2017G)

Wave1982 said:
Hey I'm having a similar issue. Fastboot wont work. You mentioned a driver problem. Im on linux and installed adb and fastboot. Im pretty sure i did it correctly. adb works fine, fastboot not. In the stock recovery was no option for fastboot neither in twrp. Is it possible that fastboot is disabled or not available on my device (Axon 7 mini B2017G)
Click to expand...
Click to collapse
No, your device fastboot isn't disabled, unless stated so by your carrier. Like Verizon almost all of their devices are perma-locked.
Did you check the device driver itself? You can get your device driver from this link. You can install it automatically or if it doesn't work try installing it manually. Don't forget to restart your PC.
If it still doesn't work then it may be cable connection issues, try a different cable.
If it still however doesn't work, then I don't know what may be the cause of the issue. Although you can always count on XDA forums for such issues, here's an article on how to unlock your specific device's bootloader.

MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL

FOR ALL XIAOMI
BOOTLOADER MUST BE UNLOCKED
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
-----------------------------------------------------------------------------------------------------------
All your data will be erased
IMPORTANT
*****Please note that the clean all and lock box is checked by default*****
*****The path must be C:/MIFLASH/rom folder*****
Download the latest version of MI FLASH here :
https://xiaomiflashtool.com/
Extract the files from Miflash zip and place them in a folder named Miflash at the root of your hard drive.
Download a Fastboot Rom here https://xiaomifirmwareupdater.com/archive/miui/lmi/
Or
https://xiaomirom.com/en/series/ more firmwares.
Others devices
(Some devices have several versions hence the importance of knowing the code name)
https://xiaomifirmwareupdater.com/
https://xiaomirom.com/en/series/
EUXM=EEA Europe
MIXM=Global
TRXM=Turkey
RUXM=Russia
INXM=India
JPXM=Japan
IDXM=Indonesia
TWXM=Taiwan
CNXM=China
DEV=Public Beta
____________________________________________________________________________
TIPS:UNROOT BEFORE AND REMOVE LOCKSCREEN SECURITY
Battery charged at least 65%.
_______________________________________________________________________________________
-----------------Chinese device does not relock the bootloader--------
with a non-chinese rom,it will brick your device.
__________________________________________________________________________________________________________________________________
{
"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"
}
_____________________________________________________________________________
Open the TGZ file with 7-zip(or others)
_________________________________________________________________________
______________________________________________________________________
Move the folder to Miflash
​
_______________________________________________________________________________________________
Rename it​************************************ No long name, space, special characters.*********************************
_____________________________________________________________________________________________________
Launch MIFLASH and install drivers
_____________________________________________________________________________________________________
Select Rom folder
_________________________________________________________________________________________
Start the phone in fastboot mode(press and hold the power button and volume down button at the same time) and plug in to the pc.
REFRESH
Check the box at the bottom right CLEAN ALL.
Flash the rom.
At the end of the flash, miflash indicates an error (normal, no problem).
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
the phone restarts unplug in.
​

Or easier one click method (which i prefer) if miflash gives some errors in flashing or installing.
Just connect phone in fastboot to pc, open fastboot rom and click on bat files to flash.

If I want to lock the bootloader (EU version) and return the phone to its stock state, then I have to select 'clean all and lock' or is there a specific reason on why selecting 'clean all'?

jovanv said:
If I want to lock the bootloader (EU version) and return the phone to its stock state, then I have to select 'clean all and lock' or is there a specific reason on why selecting 'clean all'?
Click to expand...
Click to collapse
select 'clean all and lock'
(unlock or lock erase data)

I did this when I first got the phone and flashed stock EU rom, Will do it again if no one else responds with any other methods, and I really need to use phone and hassle each time to set everything up after reflashing
Thanks

Can i re-lock the bootloader after root/Magisk ?

conmaxanhle said:
Can i re-lock the bootloader after root/Magisk ?
Click to expand...
Click to collapse
Better to unroot before

NOSS8 said:
Better to unroot before
Click to expand...
Click to collapse
Ok i will complete uninstall magisk and follow your guide

Hi, I'm trying to flash stock MIUI so i can do a clean flash of another custom ROM. But I'm stuck with an error that's MiFlash Tool is giving me.. The error says: Length cannot be less than zero. Parameter name: length. Does anyone know a fix for this? When i try to double click the flash_all bat my cmd just closes instantly when it opens. Pretty new to this so I'm worried i might brick something. Thanks

janjambon said:
Hi, I'm trying to flash stock MIUI so i can do a clean flash of another custom ROM. But I'm stuck with an error that's MiFlash Tool is giving me.. The error says: Length cannot be less than zero. Parameter name: length. Does anyone know a fix for this? When i try to double click the flash_all bat my cmd just closes instantly when it opens. Pretty new to this so I'm worried i might brick something. Thanks
Click to expand...
Click to collapse
Did you use the last Miflash?
Did you rename the rom folder?
did you use usb 2 port?
is the phone in fastboot mode?

Yes, latest MiFlash and called the folder 1204. I've tried both usb 2 and 3 with no luck. My phone is in fastboot mode but I must say i tried flashing the stock rom with XiaomiTool v2 since it did recognize my phone but it gave an error while flashing the super.img. So I'm pretty scared if ill reboot it will be stuck.

Also installed all drivers neccesary with my device called android phone -> android bootloader interface in Device Manager

janjambon said:
Yes, latest MiFlash and called the folder 1204. I've tried both usb 2 and 3 with no luck. My phone is in fastboot mode but I must say i tried flashing the stock rom with XiaomiTool v2 since it did recognize my phone but it gave an error while flashing the super.img. So I'm pretty scared if ill reboot it will be stuck.
Click to expand...
Click to collapse
This is surely the first attempt with XiaomiTool v2 that blocks, try to restart and then reflash with Miflash.
Anyway you will not be able to reset it without restarting
Make sure the ROM file has been extracted completely with no corrupted files.
Extract the ROM file in the root directory such as drive C:\ or D:\.
Make sure no single space in the folder name path.
Ensure the Mi Flash tool is run as Administrator (Right-click > Run as administrator).

NOSS8 said:
This is surely the first attempt with XiaomiTool v2 that blocks, try to restart and then reflash with Miflash.
Anyway you will not be able to reset it without restarting
Make sure the ROM file has been extracted completely with no corrupted files.
Extract the ROM file in the root directory such as drive C:\ or D:\.
Make sure no single space in the folder name path.
Ensure the Mi Flash tool is run as Administrator (Right-click > Run as administrator).
Click to expand...
Click to collapse
MiFlash is in this path along with the clean stock rom 12.5.4 global: C:\Program Files\Xiaomi\MiFlash
Should i plug out my phone, restart it, enter fastboot and try again?

janjambon said:
MiFlash is in this path along with the clean stock rom 12.5.4 global: C:\Program Files\Xiaomi\MiFlash
Should i plug out my phone, restart it, enter fastboot and try again?
Click to expand...
Click to collapse
1/move the miflash folder and the rom directly to C:/
retry flashing
It doesn't work unplug the phone and reboot in Fastboot mode and try again

NOSS8 said:
1/move the miflash folder and the rom directly to C:/
retry flashing
It doesn't work unplug the phone and reboot in Fastboot mode and try again
Click to expand...
Click to collapse
Flashing wont work because everytime i press refresh my phone doesn't show up and it gives me the error length can not be less than zero. Tried putting it directly in C:/ too. Thanks for taking your time btw I'm really grateful. I'm also a bit hesitant of restarting my phone because of fear for bootloops. Is that the only option you know?

My end goal is to flash the new hentai OS with android 12 and i was wondering (since i know how to do adb sideload) if i could sideload it now when it's in fastboot. Or should i try to firstly fix going back to stock MIUI?

janjambon said:
Flashing wont work because everytime i press refresh my phone doesn't show up and it gives me the error length can not be less than zero. Tried putting it directly in C:/ too. Thanks for taking your time btw I'm really grateful. I'm also a bit hesitant of restarting my phone because of fear for bootloops. Is that the only option you know?
Click to expand...
Click to collapse
Restart the phone and try again

NOSS8 said:
Restart the phone and try again
Click to expand...
Click to collapse
Plugged it out, restarted it back in fastboot and plugged it back in. Still the same error message.

janjambon said:
My end goal is to flash the new hentai OS with android 12 and i was wondering (since i know how to do adb sideload) if i could sideload it now when it's in fastboot. Or should i try to firstly fix going back to stock MIUI?
Click to expand...
Click to collapse
janjambon said:
Plugged it out, restarted it back in fastboot and plugged it back in. Still the same error message.View attachment 5431607
Click to expand...
Click to collapse
Did you extract the rom folder from the TGZ file?