Database Users

[Solved] OnePlus Two stuck on boot after install OxygenOS 3.0

If you have installed OxygenOS 3.0 and when you try to boot recovery mode, or other case, your phone stuck on boot, here's the solution. It's easy, you only have to enter this link: http://forum.xda-developers.com/devdb/project/dl/?id=16684 and download the content. After unzip, connect your phone in fastboot mode (on/off button + volume up button) and execute the script that is in the folder unziped (firstaid.bat in windows or fistaid.sh in linux). Now it's possible that system don't boot, but now you have TWRP recovery and you can install the ROM that you want. If you don't want that your phone becomes to stuck on boot, please, read the instructions in this link: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108 before install again OxygenOS 3.0.
Summary:
Before all this you have to install the adb/fastboot and your phone drivers.
1- Download the firstaid tool from http://forum.xda-developers.com/devdb/project/dl/?id=16684
2- Put the phone in fastboot mode (on/off button + volume up button) and connect to pc
3- Execute the script (firstaid.bat in windows or fistaid.sh in linux)
Now you have recovery again.
4- If you want to install OxygenOS 3.0, follow the instructions of https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108

I've been a lot of hours searching a solution for the problem and it's very annoying. It's a pleasure to help you for don't lose your time like me.

luisito68 said:
If you have installed OxygenOS 3.0 and when you try to boot recovery mode, or other case, your phone stuck on boot, here's the solution. It's easy, you only have to enter this link: http://forum.xda-developers.com/devdb/project/dl/?id=16684 and download the content. After unzip, connect your phone in fastboot mode (on/off button + volume up button) and execute the script that is in the folder unziped (firstaid.bat in windows or fistaid.sh in linux). Now it's possible that system don't boot, but now you have TWRP recovery and you can install the ROM that you want. If you don't want that your phone becomes to stuck on boot, please, read the instructions in this link: https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108 before install again OxygenOS 3.0.
Summary:
Before all this you have to install the adb/fastboot and your phone drivers.
1- Download the firstaid tool from http://forum.xda-developers.com/devdb/project/dl/?id=16684
2- Put the phone in fastboot mode (on/off button + volume up button) and connect to pc
3- Execute the script (firstaid.bat in windows or fistaid.sh in linux)
Now you have recovery again.
4- If you want to install OxygenOS 3.0, follow the instructions of https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108
Click to expand...
Click to collapse
thank you for the post but unfortunately it didn't work in my opt

ronyjarod said:
thank you for the post but unfortunately it didn't work in my opt
Click to expand...
Click to collapse
Sorry, if you have the problem yet you can try to connect your phone in fastboot mode (having all drivers ok) and write "fastboot devices", if your device appears download the twrp modified of the link of the instructions to install OOS 3 (https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108), open cmd in the download folder (shift + right mouse -> open cmd here) and write "fastboot flash recoery recovery.img". This did not work for me, but I tried it with an toher recovery. I wish you solve the problem soon!

luisito68 said:
Sorry, if you have the problem yet you can try to connect your phone in fastboot mode (having all drivers ok) and write "fastboot devices", if your device appears download the twrp modified of the link of the instructions to install OOS 3 (https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108), open cmd in the download folder (shift + right mouse -> open cmd here) and write "fastboot flash recoery recovery.img". This did not work for me, but I tried it with an toher recovery. I wish you solve the problem soon!
Click to expand...
Click to collapse
solved accidentally. what i did was typed fastboot boot OP2_recovery .img (not in the fastboot mode but at the stuck boot logo mode). i don't know how the img went in but that was the way saved my opt from bricked. anyhow, thank you for the reply

i just wanna downgrade pissed off of oos3.0
i wanna flash cm13 or oos 2.2.1 plz help

ronyjarod said:
solved accidentally. what i did was typed fastboot boot OP2_recovery .img (not in the fastboot mode but at the stuck boot logo mode). i don't know how the img went in but that was the way saved my opt from bricked. anyhow, thank you for the reply
Click to expand...
Click to collapse
Oh cool ! It is rare to have recovered at this way , but I'm glad to know it!

Veer1080 said:
i just wanna downgrade pissed off of oos3.0
i wanna flash cm13 or oos 2.2.1 plz help
Click to expand...
Click to collapse
If you follow the three first steps you will have recovery and you will can flash any rom. If this way not work (it worked for me) you can try the way of ronyjarod.

luisito68 said:
If you follow the three first steps you will have recovery and you will can flash any rom. If this way not work (it worked for me) you can try the way of ronyjarod.
Click to expand...
Click to collapse
lol. my way is inappropriate. i was just lucky
---------- Post added at 05:59 AM ---------- Previous post was at 05:53 AM ----------
Veer1080 said:
i just wanna downgrade pissed off of oos3.0
i wanna flash cm13 or oos 2.2.1 plz help
Click to expand...
Click to collapse
my oos 3 seems to be much better than v2.2.1

ronyjarod said:
lol. my way is inappropriate. i was just lucky
---------- Post added at 05:59 AM ---------- Previous post was at 05:53 AM ----------
my oos 3 seems to be much better than v2.2.1
Click to expand...
Click to collapse
3 is laggy after 4 days

Veer1080 said:
3 is laggy after 4 days
Click to expand...
Click to collapse
mine didn't lag after many days

OP2 stuck in bootloop on upgrading 3.0.2 .. even after trying tons of things

First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out

Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk

Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again

Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.

Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!

Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!

Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.

OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...

ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??

No i forgot to enable...

No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?

ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.

ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.

ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?

Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).

When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings

Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android

ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help

ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Android 7.1.1 Doogee X5PRO

I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?

I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.

Do the camera and fingerprint work?

Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.

Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?

****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!

The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.

I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.

installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?

xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )

Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug​#b. Enable OEM unlock​
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:​type: adb reboot-bootloader ___ (Wait 1-3 second)​type: fastboot devices ___ (verify device is detected)​#b. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: yes​= unlocked: no​#c. unlock bootloader​type: fastboot oem unlock ___ and you get​-> start unlock flow​---> on screen appear:​vol UP=Yes; void warranty, clear ALL data​vol DWN=no; no unlock​Press Vol UP​#d. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: no​= unlocked: yes​#e. May be phone restart​
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt​as per normal way (You know this , after some trying...)​
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)​
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons​#b. choose recovery with Vol Up and confirm with Vol Down​
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.

Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo

xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.

when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file

I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file

xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?

The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.

I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...

As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?

What to do when you're stuck in EDL-Mode (black screen = no fastboot - no recovery)

Probably you have the Anti-Rollback activated and tried to flash another ROM. After a successful installation your phone just went dead.
Here's how you could fix it (or how I fixed it):
1. Windows PC with MiFlash Beta (!) tool
2. Download a Xiaomi Fastboot Rom (ends with *.tgz)
http://bigota.d.miui.com/8.8.30/nitrogen_images_8.8.30_20180830.0000.00_8.1_cn_66dfc4bb58.tgz
--> Beta (MIUI 10 8.8.30) (ANTI ROLL-BACK ACTIVATED!!!)
3. extract Rom to your PC
4. start MiFlash Beta tool and point to the extracted folder
5. press Vol+ & Vol- & Power on your MiMax3 for 10 seconds and connect it to your PC while holding the buttons another second after plugging it in
6. press refresh button on MiFlash tool
7. if your drivers are installed correct, your phone should be visible on COM-Port XXX
8. press flash and hopefully it will be flashed
9. if not: try several times
10. wait until it boots to the welcome screen (around 5 mins)
now your phone should be useable again.
If you want Treble-Rom to be installed, then go on:
11. turn phone off --> go into fastboot mode (Vol- & Power) --> install TWRP --> boot into TWRP
12. wipe date = yes --> reboot TWRP
13. make yourself a MiRom at https://mi-globe.com/rom-builder-features/?codename=nitrogen&img=mimax3.png&realname=Mi+Max+3
--> I used 8.8.30 version, and choose "advanced settings"--> set Magisk for root and build your zip
14. flash it through TWRP
15. reboot --> you will end up in a bootloop, but thats okay
16. go back to TWRP: swipe factory reset
17. install treble.img + gapps + Magisk and reboot and you're all good

thanks a lot! but i m in a different situation now!
i have baught the device from local store with so called fake rom. and as per some instruction found at different forums i have successfully flashed china developper rom, and than flashed again eu rom. the version was miui 10 8.8.30. some how, i was trying to install a gcam mod mistakenly wich was originally for mi a1, and the mobile suddenly stuck on "the system has been destroyed!" mode. i can eventually come to fastboot mode from this screen, but cannot flash rom, as it says now, it is locked. dont have the right to erase. so, i tried miflash unlock with my mi account, but it says current account is not bound to this device. even, i can't go to edl, so what is happening now, i m totally nobis here.
can some one help me. please? how can i achive unlock in this situation or how could i get rid of this and reboot to system?

So there is a way to recover the phone if you brick if from installing a firmware after having anti-rollback?

yes, but the anti-rollback will be still activated. You can flash the China Roms or a treble ROM as described. If you try to flash the EU Rom you will boot into the EDL mode without any warnings.

I need help.
The post in #1 doesnt work for me.
I have also tried a many of miflash beta; all not work.
I become always the info "can not open port ..."

didi_m said:
I need help.
The post in #1 doesnt work for me.
I have also tried a many of miflash beta; all not work.
I become always the info "can not open port ..."
Click to expand...
Click to collapse
The method does work!
You need to re-activate the EDL mode in a split second of accuracy and timing by luck!
Keep trying! Your finger has got to very very fast to hit the "Flash" in MiFlash tool in relation to the process of entering he EDL mode!
I was on China Beta 8.8.30 (ARB) and I tried miflashtool to China Stable 9.6.11.0 (Non-ARB) and my phone bricked with blank screen. Could not power on at all, and not even into the Fastboot mode.
You have to miflashtool to ARB version of China Stable 9.6.12.0 to be able to success.

Hi,
I see the com port.
It begin to flash, put then the Error: Only nop and sig tag can be recevied before authentication.

didi_m said:
Hi,
I see the com port.
It begin to flash, put then the Error: Only nop and sig tag can be recevied before authentication.
Click to expand...
Click to collapse
I see. No problem.
In that case. Don't use 9.6.11.0 to miflash.
Please use the 9.6.7.0 and retry to miflash again.
9.6.7.0 should work.

I think 9.6.12 is the wright rom.
Why now 9.6.7.0.
Have you i link for me for this rom.
Is 9.6.7.0 without ARB.
Sorry for my bad english.

didi_m said:
I think 9.6.12 is the wright rom.
Why now 9.6.7.0.
Have you i link for me for this rom.
Is 9.6.7.0 without ARB.
Sorry for my bad english.
Click to expand...
Click to collapse
This is because you would probably get the same error massages as with 9.6.11.0 if you miflash to 9.6.12.0 ARB directly and even though some users might be able to miflash to 9.6.12.0 directly without the error massages
Therefore, Miflash using 9.6.7.0 Non-ARB first, and if you wanna update to 9.6.12.0 ARB. You can just do it via the Updater! This is the best and safest way to do it!
Grab the 9.6.7.0 now ...... I mean NOW!!!!!!!! before it is unlisted by Xiaomi for users to download as it is a damn old freaking rom!!!!!!!!!
UNLESS.... 9.6.7.0 failed as well! Then, you have to miflash to 9.6.12.0 directly as a last option and pray it works!
http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz

I only found the zip Version.
I need for myflash the tgz Version.
Have you a link to this Version ?
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
thanks, you ar quicklier.

didi_m said:
I only found the zip Version.
I need for myflash the tgz Version.
Have you a link to this Version ?
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
thanks, you ar quicklier.
Click to expand...
Click to collapse
UNLESS....miflashing to 9.6.7.0 failed as well! Then, you have no choice but to miflash to 9.6.12.0 directly and pray that it works with your version of miflash tool and pc.
Good Luck!

by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks

didi_m said:
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
Click to expand...
Click to collapse
Your Mi account has been locked by Xiaomi! OMG!
If so, then. No one can help you except you taking a flight to China and take a Q number at China Xiaomi service centre..
No one is dare enough to share his Mi account with you because arb is hardware "coded" so to speak. . It can cause his Mi account to be locked by Xiaomi too using it on your Mi Max 3 . '(
For my similar case, my Mi account has not been locked by Xiaomi.

I had the same issue
silentext said:
thanks a lot! but i m in a different situation now!
i have baught the device from local store with so called fake rom. and as per some instruction found at different forums i have successfully flashed china developper rom, and than flashed again eu rom. the version was miui 10 8.8.30. some how, i was trying to install a gcam mod mistakenly wich was originally for mi a1, and the mobile suddenly stuck on "the system has been destroyed!" mode. i can eventually come to fastboot mode from this screen, but cannot flash rom, as it says now, it is locked. dont have the right to erase. so, i tried miflash unlock with my mi account, but it says current account is not bound to this device. even, i can't go to edl, so what is happening now, i m totally nobis here.
can some one help me. please? how can i achive unlock in this situation or how could i get rid of this and reboot to system?
Click to expand...
Click to collapse
I had the same issue and i opened the phone and did the test point to enter to edl mode and flashed the chinese miui 10 stable rom , and now i have to wait 720 hours to unlock the bootloader to flash twrp and a global rom

So I just helped someone boot successfully to 10.0.1.0 global stable fastboot whose phone got bricked trying to flash 8.8.9 eu (maybe he had ARB but didn't know it). It was the black screen of death basically as noted here. TEST-POINT METHOD WAS NOT NEEDED.
Follow these steps:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi...icial-recovery-fastboot-roms-mi-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
4) It should boot. If it doesn't and you get stuck on the Mi Recovery screen. Select Wipe Data. It should boot you back into the recovery again where you'll see Reboot, Wipe Data or Connect Using Mi Assistant. From here, get back to fastboot mode by holding Power and Volume Down together until you see the bunny fastboot screen.
5) Open or refresh MiFlashTool again and select 10.0.1.0 fastboot rom (it should remember from previous selection). At the bottom select 'Clean All Only' (do NOT select clean all and lock). Hit REFRESH button at the top and this time it will show your device number like normal instead of COM. Click Flash.
6) Phone will reboot on its own to Miui 10 Global login screen. Setup your phone from there.

mi max 3 hard brick
opasha said:
So I just helped someone boot successfully to 10.0.1.0 global stable fastboot whose phone got bricked trying to flash 8.8.9 eu (maybe he had ARB but didn't know it). It was the black screen of death basically as noted here. TEST-POINT METHOD WAS NOT NEEDED.
Follow these steps:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi...icial-recovery-fastboot-roms-mi-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
4) It should boot. If it doesn't and you get stuck on the Mi Recovery screen. Select Wipe Data. It should boot you back into the recovery again where you'll see Reboot, Wipe Data or Connect Using Mi Assistant. From here, get back to fastboot mode by holding Power and Volume Down together until you see the bunny fastboot screen.
5) Open or refresh MiFlashTool again and select 10.0.1.0 fastboot rom (it should remember from previous selection). At the bottom select 'Clean All Only' (do NOT select clean all and lock). Hit REFRESH button at the top and this time it will show your device number like normal instead of COM. Click Flash.
6) Phone will reboot on its own to Miui 10 Global login screen. Setup your phone from there.
Click to expand...
Click to collapse
WIl l be able to go back to xiaomi eu room after that ?
thanks
---------- Post added at 01:39 PM ---------- Previous post was at 12:53 PM ----------
didi_m said:
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
Click to expand...
Click to collapse
hi..you get the error message ("cannot read...") because there must be space in you directory path somewhere ....remove all spaces in any directory path... it works like a charm.. i used the global stable rom mentioned below V10.0.1.0.OEDMIFH/nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105.tgz
---------- Post added at 01:46 PM ---------- Previous post was at 01:39 PM ----------
didi_m said:
by flash 9.6.7.0 it comes every one "can not read from com port"
9.6.12 dosnt go to.
Here he want a authorizierd mi account.
whoats now ?
Does anyone share his authorized account with me?
thanks
Click to expand...
Click to collapse
hi..you get the error message ("cannot read...") because there must be space in you directory path somewhere ....remove all spaces in any directory path... it works like a charm.. i used the global stable rom mentioned below nitrogen_global_images_V10.0.1.0.OEDMIFH_20181012.0000.00_8.1_global_159a03b105.tgz

vikram237 said:
WIl l be able to go back to xiaomi eu room after that ?
thanks
Click to expand...
Click to collapse
There is no ARB on xiaomi.eu roms (except maybe 8.8.30 as omer919 stated).

The real brick solution by ARB, it works for mi max 3 too.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
and this is the ARB in Mi MAX 3.
https://forum.xda-developers.com/mi-max-3/how-to/rom-official-recovery-fastboot-roms-mi-t3827503

I had that one. Please charge up your Mobile for at least %100, lt will reboot.

{root} Boot-loader unlock, TWRP flash and Magisk install after updating to Pie

* I'm 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 the products you find here 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.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Needed tools : Backup your phone before following any steps
1. Minimal adb and fastboot
2. official TWRP 3.3 for jasmine_sprout Download img file from twrp website
3. latest magisk manager 19.2 zip file from magisk manager website
First step : Boot loader unlock
1) Tap on build number more than 7 times and unlock developer option in about phone.
2) turn on OEM Unlocking and USB debugging
Now open command windows in adb shell folder and connect your device to computer.
type : 1) adb devies (this should show your device after giving permission in your phone : conformation that your device is
connected)
2) adb reboot bootloader
3) fastboot devices ( conformation that your phone is coonected in fastboot mode)
4) fastboot oem unlock
( after that you need to follow according steps in your phone and grant to unlock phone)
keep in mind this will reset your phone. Afteer reboot again turn on developer options and usb debugging
5) fastboot flashing unlock_critical
( the warning and steps you need to follow again in your phone like in step 4)
this will again reset your phone.Afteer reboot again turn on developer options and usb debugging
Congratulations your bootloader is Unlocked now.
STEP 2. Flashing TWRP and Magisk Install
before that keep in mind As Mi A2 follows A/B boot partition system so DONT DIRECT FLASH TWRP FROM
FASTBOOT.
" Dont forget to turn on developer options and usb debugging "
open command window in adb shell folder and boot your phone in bootloader mode as told earlier and connect to computer.
Copy twrp-3.3.0-0-jasmine_sprout.img to minimal adb and fastboot folder. you can rename it to your convenient name
type : 1) fastboot boot twrp-3.3.0-0-jasmine_sprout.img
or if you renamed it
fastboot boot YourRenameName.img
this will temporarily boot twrp in your Device. As twrp is booted you will be able to see your phone connected in computer
(file transfer mode)
Copy and paste both magiskmanager.zip (current latest stable is 19.2 ) into phone
Flash your downloaded version of Magiskmanager.zip
Reboot your Phone.
Congratulations If nothing goes sideways Your phone is Magisk Rooted.
If you want to flash something using TWRP now is the time Otherwise as Mi A2 has A/B slot form and no Recovery Partition You Cannot flash TWRP permanently.
But You can always boot TWRP from adb and use it.

ROM flashing help
Can't flash ROM after using this method

Torque422 said:
Can't flash ROM after using this method
Click to expand...
Click to collapse
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

Failed
No such a directory problem, please help

Please elaborate more about the problem ? @shahidrok
shahidrok said:
No such a directory problem, please help
Click to expand...
Click to collapse
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
TYPHOON9055 said:
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks ?, i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now?
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055

Hve done everything but when i try to reboot to twrp it gets stuck on twrp logo,dont know what im doing wrong.

Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks

I get error 1 during flashing

Amnvlad said:
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
Click to expand...
Click to collapse
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Alucard said:
I get error 1 during flashing
Click to expand...
Click to collapse
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic ?

Torque422 said:
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic
Click to expand...
Click to collapse
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
Available custom roms are for Oreo versions if you have updated ur device to pie , it won't work.

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
I was on stock pie + may update (10.0.9)
Follow this way , unlock the bootloader via fastboot oem unlock, fastboot flashing unlock it will reboot here, goto developer settings Enable usb debugging
Then do this fastboot flashing unlock_critical It will again reboot
Now, install the magisk app And download the patched boot image from internet Whatever your build no is, mine was 10.0.9 so i downloaded version 10.0.9_boot.img
Open the magisk app, click on install , select and patch a file, Then choose this downloaded patched image, it will flash it successfully, if it don't Then you have mistaken something..
After this there will be a patched.img in download folder Which is just created by magisk, copy this img to pc, Through fastboot Flash it "fastboot boot patched.img"
Now, flash TwrpImage3.3.img through fastboot
When you boot in , Copy and paste your rom, gapps
Now flash twrpVersion3.2.img via fastboot
Clear system,data,caches, Flash the rom in slot B
Now flash the twrp3.2.zip through installed twrp, click on recovery And it will boot to twrp
Now Flash the gapps in slot a (i used nano)
Now flash magisk.zip through twrp
Reboot , That's it!
(Twrp 3.2 is stable for flashing rom and gapps , Just for first time When we coming from stock
Twrp 3.3 latest Gives us MTP transfer, The difference is this in using both of these)
Installation of magisk is the last process, it is part of rom, First installed ur desired rom and then magisk
You said, You installed twrp, as i mentioned above You forgot to do some steps as about patched boot + installation of magisk through patched file etc..
Though you can try to search on google for your next step
patched supported magisk Version x.x.x for mi a2
If you got the file, You are lucky.. otherwise flash the stock rom with mi flash tool
And Start from unlocking bootloader

Magisk Module available.
Torque422 said:
Please elaborate more about the problem ? @shahidrok
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
Thanks , i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Click to expand...
Click to collapse
There is a magisk module available for installing kali nethunter in this device. i never tried installing it but it should work fine. Read proper descriptions before installing it though.

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
the adb recognized my phone but fastboot do not, help me out please

Andrew.kathy said:
the adb recognized my phone but fastboot do not, help me out please
Click to expand...
Click to collapse
Probably a problem with drivers, check and reinstall drivers

Can i use this method to flash magisk on Mi 9T pro?

I can't boot into twrp
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs

Topper8118 said:
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Click to expand...
Click to collapse
Checklist:
- there is file of <compatible TWRP recovery> in ADB/Fastboot directory with the name you are typing in fastboot command
- ADB drivers installed correctly (both "adb devices -l" and "fastboot devices" return valid results in corresponding phone states)
- only one phone (namely MiA2) is connected to PC
- phone fully unlocked (OEM debugging enabled and PC was previously approved for ADB in phone)
- USB port on MB of PC is USB-2.x or USB-3.x-compatible-with-Mi-A2<which is not true in general>

Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you

HTCDevil said:
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical