Develop Bugs

Can't unlock bootloader on N5X

Hello guys I try 10 times unlock my N5X bootloader and nothing happened after everything. I am using NRT method. I have developer options enabled and oem unlock turned on. Phone is going to bootloader mode I tap on screen when I choose if I want to unlock and after all procedure device has wiped data because I have to set my language etc. etc. but when I want to root it in bootloader mode system show BOOTLOADER: locked. I posted screen. What am I doing wrong. Thx for helping!
{
"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"
}

Blacknighter said:
Hello guys I try 10 times unlock my N5X bootloader and nothing happened after everything. I am using NRT method. I have developer options enabled and oem unlock turned on. Phone is going to bootloader mode I tap on screen when I choose if I want to unlock and after all procedure device has wiped data because I have to set my language etc. etc. but when I want to root it in bootloader mode system show BOOTLOADER: locked. I posted screen. What am I doing wrong. Thx for helping!
Click to expand...
Click to collapse
Did you flash twrp?
I reccomend you start from scratch using this guide:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Doing it all manually gives you a way better understanding of what you are doing than using a toolkit.

Bro I can't unlock bootloader, so how can I install TWRP? What is this secure boot: enabled , what does NO RPMB mean?

Blacknighter said:
Bro I can't unlock bootloader, so how can I install TWRP? What is this secure boot: enabled , what does NO RPMB mean?
Click to expand...
Click to collapse
Just trying to help. Chill a bit please. The second part of your story isn't all that clear.
Let's take a few steps back. Do you have fastboot access working?

Yes, when I connect phone to PC in fastboot pc see my phone.

Blacknighter said:
Yes, when I connect phone to PC in fastboot pc see my phone.
Click to expand...
Click to collapse
And you tried the manual steps in Heisenbergs guide?
Mainly:
Fastbbot devices (check serial)
Fastboot OEM unlock
Fastboot reboot
If that doesn't work there's probably something wrong in your initial setup.

When I wrote command fastboot devices I don't saw serial ... so problem is here. What to do?

Blacknighter said:
When I wrote command fastboot devices I don't saw serial ... so problem is here. What to do?
Click to expand...
Click to collapse
My guess is not all required software is installed correctly.
As I said start from scratch using the guide I mentioned.

On third PC I get the sam result - when I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.

Blacknighter said:
On third PC I get the sam result - when I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.
Click to expand...
Click to collapse
What if you flash TWRP before executing "fastboot reboot-bootloader". Does it work?

C:\SDK\platform-tools>fastboot devices
0140998a5ec096e4 fastboot
C:\SDK\platform-tools>fastboot oem unlock
...
OKAY [ 3.972s]
finished. total time: 3.972s
C:\SDK\platform-tools>fastboot flash recovery twrp_bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16325 KB)...
OKAY [ 0.590s]
writing 'recovery'...
OKAY [ 0.100s]
finished. total time: 0.700s
C:\SDK\platform-tools>
After rebooting, information appeared that file may be corruption, but when I go to recovery it still showing state LOCKED. Now after rebooting system Logo Google appeared and nothing happened (Bootloop?) Now I can't do anything

Why after rebooting everything goes back and device state is LOCKED? I have motherboard replaced by warranty service. What to do?

USB drivers are (re-)installed?
You never relocked bootloader at any point in the proces?

OK I flash *.img files manually one by one and I installed system. But main problem isn't solved.
After fastboot command oem unlock in bootloader mode it showing bootloader unlocked but after rebooting STATE is showing LOCK.
Any ideas? What **** is restore back system unlock to lock?

ok I found a simillar thread
http://forum.xda-developers.com/google-nexus-5/help/fastboot-oem-unlock-goes-to-lock-reboot-t2903581
So it can't be repaired... great warranty service replace my damaged motherboard for another not good working motherboard where I can't unlock bootloader to even flash nexus factory images hehehehehe OMG...

It's not fastboot oem unlock anymore.. The command is fastboot flashing unlock
Sent from my Nexus 5X using Tapatalk

graffixnyc said:
It's not fastboot oem unlock anymore.. The command is fastboot flashing unlock
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Since when is this implemented?

Even I wrote command fastboot flashing unlock, after reboot bootloader I get the same result - state: locked :/ and I have to again set everything from the beginning because command wipes my device... Thx for trying to helping me but I think that nothing can solve this problem.

Blacknighter said:
Even I wrote command fastboot flashing unlock, after reboot bootloader I get the same result - state: locked :/ and I have to again set everything from the beginning because command wipes my device... Thx for trying to helping me but I think that nothing can solve this problem.
Click to expand...
Click to collapse
Which version of the SDK and Platform Tools do you have installed?
Sent from my Nexus 5X using Tapatalk

I have installed latest sdk tools version. What does this have to do with it? I have all drivers installed. Any fastboot commands work ok, even flashing manually img files also work. System after rebooting bootloader do not save the unlock state settings :/

The system has been destroyed

I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?

ghtcp said:
I was using the Mitool tool, and suddenly the machine shut down and the message "the system has been destroyed" appears and it does not start anymore, the only option I have access and the fastboot, would anyone have the solution?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Did the PC shut down or the phone?
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
If unlocked you can fastboot the firmware as you normally would

Dobsgw said:
If your bootloader is locked you will need to open the back of the phone and flash a new firmware with PC and pressing the test point on the inside of the phone.
Click to expand...
Click to collapse
You can flash images with Mi Flash on locked bootloader no problem.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
They can try but if recovery isn't accessible then fastboot is the only option and without unlocked bootloader you cannot use it.
Test point is then the only way.
Obviously its best to try flashing without opening the phone first.

marinespl said:
You can flash images with Mi Flash on locked bootloader no problem.
Click to expand...
Click to collapse
Wtf! You can't use mi flash tool unless your bootloader is unlocked

The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END

ghtcp said:
The problem was tense, but it's already been resolved. I find it hard to understand more I will try to explain.
-------------------------------------------------- ------------------------------------- 1º It was with the Global Beta rom and the bootloader unlocked and installing the TWRP for the mitool, however for lack of attention I selected the option to block the bootloader.
After confirming the bootloader block by mitool, the cell phone appeared the message "the system has been destroyed", and it was restarting on this same screen, the only option I had access was to the fastboot.
Since I had access to the fastboot, I tried to install the rom by the miflash only that it gave the message "remote: Erase is not allowed in loke state".
4º After despairing and thought to open the cell to do the testpoints method.
5º Since probably the bootloader had been blocked by the mitool, I decided to enter the site and ask Xiaomi to release the code to unlock the bootloader again.
6th I put the chip in another device and thanks to the holy protector of the cell phones Xiaomi quickly released the code, I did process to unlock the bootloader and the cell phone ran again.
-------------------------------------------------- -------------------------------------END
Click to expand...
Click to collapse
The bootloader gods have smiled upon you this time

Hello! I have locked bootloader with "fastboot oem lock". I was in panic, but randomly I press "Volume -" + "power-on" and my Mi A1 have loading in Fastboot mode, where I was able to unlock bootloader again.
Hope, this can help you.

HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone

same issue in redmi note 4
indersethi said:
HI there I also stuck in the same condition and it seems your phone's bootloader is locked now, this happens because you root the phone or installed custom libs or twrp in it and locked the bootloader. So unlocking the bootloader will fix this problem. You can unlock it by going into Fastboot mode (pressing power button + volume down (-) button) and then with platform tools you can unlock it again by typing "fastboot oem unlock" and then "reboot".
I hope this will help someone
Click to expand...
Click to collapse
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....

Basilp275 said:
After i flashed lots of roms in redmi note 4 there is no problem i have seen but, right now my device suddenly rebooted because of rooted and flashed imgs and it shows ''system has been detroyed''.I tried the commands using adb fastboot oem unlock then its shows ''token verification failed;i can only acess to fastboot. what i have to do now ??.....
Click to expand...
Click to collapse
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.

ccelik97 said:
Reflash your rom with fastboot and hope you haven't messed up anything related to your data so you can still use and have access to it.
Click to expand...
Click to collapse
Yes,it's worked

Basilp275 said:
Yes,it's worked
Click to expand...
Click to collapse
Cool then ?

I had the same problem today. my phone was distroed when I tried to install Gcam.
my phone was not unlocked so that the flash of the new stock of the ROM was not possible. The solution is to connect the phone to a PC in fastboot mode and from the platform tools in cmd to type fastboot oem unlock. After that, I did not have to have a flash phone. Everything worked as if I only had to backup the data.
now I have a new phone.
People, with Mi A1, cling to two things - slot A or slot B and lock or unlock. The easiest way to do this is a cardinal error.
Greetings.

Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?

jesus4android said:
Same thing happened to me. Had global rom with bootloader unlocked, then I installed TWRP and reinstall MIUI 10, as well as no-verity and Magisk. When installed the phone showed some issues with the proximity sensors so I decided to reinstall, after installing and booting MIUI showed a message, "the device is locked", I couldn't connect to the internet to unlock it, so I decided to do a fresh installation through miflash, after a couple attempts all of a sudden TWRP was not there anymore. Now the bootloader shows unlocked on '''fastboot oem device-info'''. Now the real problem: miflash doesn't work because bootloader is locked, I didn't unlocked it in the first place so I cannot do a fresh installation through miflash, when booting TWRP it shows the message, The system has been destroyed....
I tried miflash, fastboot oem unlock, fastboot recovery flash for TWRP, fastboot -w then fastboot flash recovery ....zip. Absolutely nothing is working.
How did you make it work exactly?
Click to expand...
Click to collapse
With locked bootloader I got no chance to flash anything. Neither fastboot nor MiFlash - any solutions? Also would be helpful to enabke USB Debugging via fastboot. Anyone knows?

If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!

I want to sell my Google Play app developer license.
Please email me or call me if you are interested.
phone - +917007797787
Email- [email protected]

I got a bricked Mi 6 from a friend. He was trying to flash firmware, and somehow messed up. Trying to boot normally or into recovery showed "The system has been destroyed". `fastboot continue` did not work. Bootloader was locked ( = no possibility to do fastboot oem unlock). On top of that, the phone only accepted fastboot commands right after the usb cable was connected ( => I had to run a fastboot command, like `fastboot getvar all`, fastboot would output `< waiting for any device >`, then I connected cable, and it would work). Running fastboot commands later resulted only in fastboot hanging / getting stuck, with no output, can not be terminated with ctrl+c unless cable was disconnected.
I got myself a windows computer (I use linux), tried to do bootloader unlock. Failed on "add your mi account in Settings -> Developer -> blablabla" - no way to do that with a bricked phone. Then I found out about EDL (Emergency download) mode. This is what worked.
The only way to get into the EDL mode in this state was the hardware way (shortcutting the pins / "PCB test points"). Search online for "mi 6 edl mode testpoints". Basically, you have to:
1. remove the rear cover
2. remove the screws on the plastic part above the battery, remove the plastic piece
3. disconnect the battery (shorter connector on the left side)
4. shortcut the pins using a tweezer (the pins are just above the battery connector)
5. while the pins are connected, connect the USB cable
6. check in device manager that you have "HS-USB QDloader 9008" in the COM devices
7. use mi flash tool to flash the fastboot firmware
The pins (from https://www.mobilerdx.com/2019/02/xiaomi-mi-6-test-points-xiaomi-mi-6-edl-mode-pinout.html):
{
"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"
}
And after you succeed, maybe unlock your bootloader, so that you don't have to do this again

MI 9 SE Brick After Locking the Bootloader (Global rom installed on Chinese phone)

Hi everyone!
I bought a MI 9 SE for my dad, it was a Chinese version with an unlocked bootloader and global rom installed.
After trying to use Google Pay, I figured it needs a locked bootloader. So I locked it using "fastboot oem lock".
After that, the phone is bricked
I didn't have an account bound to it, so can't use the official unlock.
Can access fastboot and recovery.
Tried flashing using recovery, sideloading.
It refuses to install a chinese rom, only a global one can be installed.
Obviously, I get the "This MIUI version can't be installed on this device".
I know there's the EDL path, but that requires an authorized account
Is there any other way around this?
Is there a way to force install a chinese rom over the global rom?
I would really appreciate any help or advice. I've spent a few days reading the forums, tried a lot of utilities but with zero luck.

Did you try the original chinese ROM, the first release? The same with global?

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
I have tried the last few MIUI versions, but didn't try the original release versions. That's a good point! Will try today, and get back with the results :good:

If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from https://drive.google.com/open?id=1-Np8xHPfVlJwUJLURntIklmkCyVqU5jH and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.

Flounderist said:
If you locked the bootloader on a non-official ROM, you could have messed the AVB (Android Verified Boot) partition.
Disabling vbmeta could be helpful.
Download vbmeta.img from and place it in the same folder of your fastboot tools.
Open a cmd window (don't use Windows Power Shell) and type command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
If you get the command executed properly, then type
fastboot reboot
and pray if device will restart on old ROM, set a MiAccount and unlock bootloader again using MiFlash, then flash any Official ROM and relock bootloader, if needed.
You can also get GPay working on unlocked bootloader, using Magisk, in case.
Click to expand...
Click to collapse
{
"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"
}
It didn't work, says 'Flashing is not allowed in Lock State'

elpaablo said:
Did you try the original chinese ROM, the first release? The same with global?
Click to expand...
Click to collapse
The same error both times, seems it refuses to install older versions of MIUI

savandriy said:
The same error both times, seems it refuses to install older versions of MIUI
Click to expand...
Click to collapse
Oh, you don't use miflash tools?

savandriy said:
It didn't work, says 'Flashing is not allowed in Lock State'
Click to expand...
Click to collapse
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily

Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box

Flounderist said:
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
What the hell, I have a family? What's this about?

Grus said:
What the hell, I have a family? What's this about?
Click to expand...
Click to collapse
Hahaha sorry mate. It's the link of a telegram group and it matched with your nickname.
Grus is the device name for Mi 9 SE :laugh:

That's so incredibly strange. Guess I'll have to check that phone out.

Flounderist said:
Try with
fastboot format userdata
and
fastboot reboot
If you use telegram, join the conversation here @GrusFamily
Click to expand...
Click to collapse
Sadly, it just hangs forever on the "Sending 'userdata' (4400 KB)" part ...

pikouchou said:
Reboot in fastboot ans use Flashtool
Flash any ron in fastboot format from here https://mirom.ezbox.idv.tw/en/phone/grus/
With flashtool, all partition will be format and phone is like out of the box
Click to expand...
Click to collapse
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?

savandriy said:
Can you please link to the Flashtool or a tutorial? Do you mean XiaomiADB?
Click to expand...
Click to collapse
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.

https://mirom.ezbox.idv.tw/en/phone/grus/roms-cn-stable/
Try the first chinese version (10.2.3).

Flounderist said:
Here is the link:
https://www.xiaomiflash.com/download/
You need to download a fastboot ROM and to unzip it TWICE to get the flashable files.
Then launch flashtool while device is connected in fastboot mode.
Locate files using flashtool interface and try to flash it.
If you won't succeed, EDL flash is your last resort.
Click to expand...
Click to collapse
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then

Try global too. I would try all Chinese and global versions, just to be sure. Because, you know, edl isn't free.

savandriy said:
It says there's a device mismatch, but this is the Chinese MIUI 10.2.3 for MI 9 SE
I guess EDL it is then
Click to expand...
Click to collapse
If you get device mismatch error you should:
- check if your device is actually a Mi9 SE
- check if you downloaded a fastboot ROM for Mi 9SE
- check if you are using the latest MIUI driver and MiFlash.
Probably your device had a fake-MIUI ROM installed with some messed device fingerprint, hence MiFlash does not recognize it as Grus.
If you are 100% sure your device is a Mi 9SE, and you downloaded the correct ROM (I would recommend latest China Stable), you can try editing the flash-all.bat file.
Here is a tutorial (you probably will need to translate it): https://www.miui.it/forum/index.php...lazione-delle-rom-fastboot-con-miflash.15301/
Good luck!

You can flash him only with testpoint and auth account

No succes trying to unlock my Swift 2x

Hi, I spent several hours trying to unlock my phone. Tried following steps:
* I made a full backup
* I did full reset to original settings: Androïd 8.1.0
* I got myself developers rights
* in settings turned on 'usb debugging' , 'OEM unlock' and 'advanced restart'
After turning off device and restart ('power/vol up' buttons), device started in recovery mode
* downloaded 'ADB + Fastboot-package' on Win10-PC and tried in every conceivable way to install but phone would not not connect; recovery boot indicated device was locked; PC did not recognize phone
and impossible to flash TWRP-recovery
* I installed Magisk-manager on phone with succes to avoid having to use a PC; but then flashing TWRP did not succeed
What did I wrong, what do I wrong? Suggestions VERY welcome. after all this I had rather not return to original OS. Thanks for your help.

With the phone in fastboot mode issue "fastboot devices" make sure you get a response.
Then "fastboot oem unlock - go"

Thank. you very much for your answer. Problem is that after rebooting with <power + volup> I get a menu with ao START (in green), Power off (i n white), Recovery mode (in red) and Restart Bootloader (in red). Further on I read FASTBOOT MODE (in red), product name etc., SECURE BOOT -enabled (in white). and DVEICE. STATE - locked (in red). How do I get my phone in 'fastboot mode'?
Thanks for help.

hepkeb said:
How do I get my phone in 'fastboot mode'?
Thanks for help.
Click to expand...
Click to collapse
First you select Fastboot
Spoiler: Fastboot
{
"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"
}
Then you get in Fastboot Mode, then connect your cable to your Pc
Spoiler: Fastboot Mode
THIS IS FASTBOOT !

Thank you for trying to help. Of course I know how to get in fastboot mode. My problem is that in 'every' mode my telephone is locked, and I do not succeed in unlocking it. I cannot connect to another device, Magisk installation not complete etc. Again: I have developers right, I unlocked OEM, I did allow USB-debugging but no unlocked device!? What is going wrong, or has Wileyfox blocked the normal unlocking-procedure?

hepkeb said:
Thank. you very much for your answer. Problem is that after rebooting with <power + volup> I get a menu with ao START (in green), Power off (i n white), Recovery mode (in red) and Restart Bootloader (in red). Further on I read FASTBOOT MODE (in red), product name etc., SECURE BOOT -enabled (in white). and DVEICE. STATE - locked (in red). How do I get my phone in 'fastboot mode'?
Thanks for help.
Click to expand...
Click to collapse
That is fast boot mode

robin0800 said:
That is fast boot mode
Click to expand...
Click to collapse
I have exactly the same problem. I do not have access to the phone and a hard reset leads me to having to enter a googe account synced with the device which I do not have the details of. I can enter the mode that you describe above and the FASTBOOT MODE is in red below. Now when I'm here and plug into my laptop wth USB and fire up fastboot.exe and issue 'fastboot device' it just says '< waiting for device >'.
Did you manage to make any progress on this issue at all, I'm really stuck!

download adb and fastboot from here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
unzip the file and then install adb and fastboot, no drivers needed on win ten.
enable debugging and debugging notifier on phone.
open a command prompt and do "adb Devices"
the first time you do this you should get a notification on your phone accept it.
do "adb Devices" again and the phone should be seen.
do adb reboot bootloader
you should be in fastboot now
do fastboot devices and then fastboot oem unlock - go.

robi0800 said:
download adb and fastboot from here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
unzip the file and then install adb and fastboot, no drivers needed on win ten.
enable debugging and debugging notifier on phone.
open a command prompt and do "adb Devices"
the first time you do this you should get a notification on your phone accept it.
do "adb Devices" again and the phone should be seen.
do adb reboot bootloader
you should be in fastboot now
do fastboot devices and then fastboot oem unlock - go.
Click to expand...
Click to collapse
Thanks robi0800 but I don't have access to the phone so I can't enable USB debugging which means I can't use adb. I am trying to use fastboot but when I issue the command 'fastboot device' it can't connect to the phone and just displays '< waiting for device >'. Any other advice on how to make my Win10 laptop recognise the device when I plug it in so I can use fastoot successfully?

Sounds like you are missing a driver you could try the driver from the package in post #8 above?

Thanks robin0800, I've tried that package with the original Wileyfox red USB cable, no luck unfortunately. My Win10 laptop can see the device in Device Manager but adb Devices will not list anything, neither will fastboot. I don't have access to the phone to enable usb debugging.

Bermudan said:
Thanks robin0800, I've tried that package with the original Wileyfox red USB cable, no luck unfortunately. My Win10 laptop can see the device in Device Manager but adb Devices will not list anything, neither will fastboot. I don't have access to the phone to enable usb debugging.
Click to expand...
Click to collapse
Adb will not see it if debugging is not enabled but fastboot does not need this but the phone must be in recovery mode

robin0800 said:
Adb will not see it if debugging is not enabled but fastboot does not need this but the phone must be in recovery mode
Click to expand...
Click to collapse
Thanks - and to put it in recovery mode is this just Powebutton + Vol Up for several seconds or Vol Down, I can't recall...

Question Bricked OP9pro

Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?

craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?

U not able to flash boot the stock boot.img?

i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed

You need to be in fastbootd,
Code:
fastboot reboot fastboot

craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"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"
}

danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)

@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.

MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com

New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off

danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse

djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign

danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support

djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help

craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?

djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on

craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked