Database Develop

[Q] Is my phone permanently bricked?

Yesterday, some bad things happened when I went to switch ROMs. Eventually, I ended up erasing my internal storage and re-locking the bootloader. I am aware that mistakes were made and I take full responsibility for my foolish actions.
So right now the problem is that I can't unlock the bootloader with the fastboot command because the "Allow OEM unlocking" box is not checked. The main problem here is that I can't simply boot into the OS and check this. I have no OS because I wiped my internal storage, including all my backups (Yes, I am an idiot.).
The phone is currently stuck on the bootloader screen. Rebooting into recovery just makes the Google splash screen flicker and it goes back to the bootloader immediately. I've seen similar threads but I haven't seen anything that mirrors my issue.
Is the phone bricked until we find a way to bypass the "Allow OEM unlocking" checkbox?
Thanks,
-PurpScurp

PurpScurp said:
Yesterday, some bad things happened when I went to switch ROMs. Eventually, I ended up erasing my internal storage and re-locking the bootloader. I am aware that mistakes were made and I take full responsibility for my foolish actions.
So right now the problem is that I can't unlock the bootloader with the fastboot command because the "Allow OEM unlocking" box is not checked. The main problem here is that I can't simply boot into the OS and check this. I have no OS because I wiped my internal storage, including all my backups (Yes, I am an idiot.).
The phone is currently stuck on the bootloader screen. Rebooting into recovery just makes the Google splash screen flicker and it goes back to the bootloader immediately. I've seen similar threads but I haven't seen anything that mirrors my issue.
Is the phone bricked until we find a way to bypass the "Allow OEM unlocking" checkbox?
Thanks,
-PurpScurp
Click to expand...
Click to collapse
Yes you are bricked.
http://forum.xda-developers.com/nexus-6/help/lock-bricked-nexus-6-t3056401

What recovery is on it?
Have you tried booting a recovery image if you don't have stock recovery?
fastboot boot recovery.img
I'd try to boot twrp may not work with the lock
fastboot erase cache got me out of trouble but I didn't relock my boot loader.
Wish I had a nexus stuck in this situation to fiddle with.

R4INS said:
What recovery is on it?
Have you tried booting a recovery image if you don't have stock recovery?
fastboot boot recovery.img
I'd try to boot twrp may not work with the lock
fastboot erase cache got me out of trouble but I didn't relock my boot loader.
Wish I had a nexus stuck in this situation to fiddle with.
Click to expand...
Click to collapse
I don't believe that command works with a locked bootloader. It had TWRP. Rebooting into recovery doesn't work at all. It just flickers the Google screen then goes back to bootloader menu.
The only thing that the phone does now is show the bootloader screen.
Simply powering on the phone brings it to the bootloader menu. I don't even have to hold power + vol up/down.

Yep it does that if you wipe the OS. There's nothing you can do at the moment.

PurpScurp said:
I don't believe that command works with a locked bootloader. It had TWRP. Rebooting into recovery doesn't work at all. It just flickers the Google screen then goes back to bootloader menu.
The only thing that the phone does now is show the bootloader screen.
Simply powering on the phone brings it to the bootloader menu. I don't even have to hold power + vol up/down.
Click to expand...
Click to collapse
Does a PC recognize it when connected? Can you get fastboot to see the device?

Evolution_Freak said:
Does a PC recognize it when connected? Can you get fastboot to see the device?
Click to expand...
Click to collapse
Yes he can. His bootloaders is locked though so he cannot unlock it.

rootSU said:
Yes he can. His bootloaders is locked though so he cannot unlock it.
Click to expand...
Click to collapse
Oh, ouch. I must have missed that part. So it's basically the same issue so many others have run into.

Evolution_Freak said:
Oh, ouch. I must have missed that part. So it's basically the same issue so many others have run into.
Click to expand...
Click to collapse
Unfortunately so.

LOCK Oneplus 5 Bootloader (GUIDE)

Hi guys, if you are like me trying to lock the bootloader to get Android Pay, or Netflix back up and running without much fuss, I found a way to lock the bootloader.
WARNING: This will do a factory reset to your device, so do backups...
Requires:
- Official OOS flashed (Download here the full zip file for the latest OOS, you can flash through TWRP or stock Recovery)
- Latest Fastboot drivers and SDK file
- Basic knowledge of Fastboot commands
Guide:
- Boot the device into Bootloader mode (power the device with Volume up + Power Button)
- Connect to the PC
- Run the command "fastboot flashing lock"
- On the device, using the volume keys select "Yes" to lock the bootoader
And that's it, the 1st boot will take longer, but just wait.
Hope this helps =)

@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.

Titokhan said:
@hugoprh
It should be
Code:
fastboot oem lock
instead of
Code:
fastboot flashing lock
as OnePlus still uses the older LK. Only Nexus 6P & Pixel/Pixel XL have updated LK that includes these changes.
You should also mention that this procedures factory resets the device i.e. the internal memory is wiped.
Click to expand...
Click to collapse
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.

hugoprh said:
Hi, thanks for your feedback, but I did try "fastboot oem lock", as other XDA Oneplus 5 users have tried as well, without success, so I tried the Nexus 6p way "fastboot flashing lock" and it worked and this is the reason I decided to make this guide and I did write a "WARNING" about this procedure doing a factory reset, it's written in bold and underlined, please read carefully.
Click to expand...
Click to collapse
Let me explore the firmware - it would a curious case of hybridization then.
Regarding the warning: Yah, my bad... missed it somehow.

Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?

rgreene1971 said:
Trying to relock my bootloader, everytime I get to the fastboot screen I scroll through to "START" and select it using the power button the phone shuts off and reboots. Having a hard time getting into fastboot. any suggestions?
Click to expand...
Click to collapse
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?

rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
+1

rgreene1971 said:
I was able to figure out my fastboot issues and able to flash twrp and revert back to a stock image, however when I try to lock the boot loader i get the error "FAILED (remote: flashing lock is not allowed).
Any ideas on the direction I need to go?
Click to expand...
Click to collapse
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!

Why lock? Why not just use Magisk? That works fine with Android Pay.

You don't need to lock your bootloader to use Netflix

nagorimayank said:
You need to turn on OEM Unlocking in Developer Settings. If for any reason OEM Unlocking is freezed, flash Magisk and then turn on OEM Unlocking. Flash the stock recovery and the lock bootloader command. It should work flawless!
Don't forget the backup!
Click to expand...
Click to collapse
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?

mullafabz said:
I am getting the same error saying that Flashing Lock is not allowed.I did what you said to do but the i can't turn on the OEM Unlocking in Developer Settings since it is greyed out.
What should i do?
Click to expand...
Click to collapse
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.

beache said:
What I did was install custom ROM, the option isn't greyed out. Then try again. But make sure you install stock ROM and recovery before bootloader lock.
Click to expand...
Click to collapse
I managed to lock back the bootloader but now am stuck in an bootloop.

mullafabz said:
I managed to lock back the bootloader but now am stuck in an bootloop.
Click to expand...
Click to collapse
You have to format data in recovery

New Xiaomi A2 global bricked???

I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.

foxdanger said:
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
Click to expand...
Click to collapse
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.

Njaiker said:
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Click to expand...
Click to collapse
What I did was with the phone working I entered on configuration, developer, and turned of the oem lock option.
Than I reboot in fastboot and did fastboot oem lock.
This made the cellphone unbootable. Bootloop saying that I'm trying to start a different operational system.
And I can't make fastboot unlock because I turned off the option in the system, so I can't send fastboot commands like oem edl, unlock, unlock-critical and etc...
I can't do nothing :/

I don't know how the option was working, but was... I know it should be locked, but this time wasn't. Was after I factory reset the cellphone

Your fault that you locked bootloader on a modified system. Do a research next time

Question No FastbootD mode ?

Dear all,
I searched a lot but couldnt find the answer.
I got OP10Pro stucked at fastboot screen.
Fastboot enhance doesnt make device boot on fastbootD. neither with commands too.
Any solutions or offers ?

Hi,
How did you get to this point in the first place?

tap77 said:
Hi,
How did you get to this point in the first place?
Click to expand...
Click to collapse
it was half brick phone. Someone flashed developer preview firmware and stucked at "setup lockscreen password". It always fails to setup password.
I flashed EU rom but didnt realize that there were no fastbootD mode. Due to this after fastboot flash it stucked on fastboot/bootloader screen.

Hi,
I see. According to instructions online, reboot to fastbootd should be an option in the recovery, under advanced in the recovery menu.
However, when I entered recovery, I couldn't see the advanced option. It could be because my bootloader is not unlocked.
To enter recovery: Turn phone off. Then hold power button + vol down simultaneously until you see the oneplus logo.

benzersizadam said:
it was half brick phone. Someone flashed developer preview firmware and stucked at "setup lockscreen password". It always fails to setup password.
I flashed EU rom but didnt realize that there were no fastbootD mode. Due to this after fastboot flash it stucked on fastboot/bootloader screen.
Click to expand...
Click to collapse
It just struck me that If you you're stuck at the bootloader screen with regular fastboot available, you could try use fastboot enhance which can reboot your phone to fastbootd mode and from there you could flash stock payload.

Fastboot black screen only? Need help asap

Hi guys so my device is on global miui 12.0.6.0 stable and whenever i check for updates it says its the latest but I know there is an android 11 already, my device is still on android 10.
So next step is to unlock adb and fastboot right so I can update my device.
I did all the steps necessary.
OEM Unlock is on
MI account is connected on (mi unlock status)
usb debugging is on
install via usb is on
usb debugging security settings is on
No password (lockscreen)
Other things I've done:
I installed the Miui 12 on the check update screen twice
I factory reset on settings
I cleared all data on recovery settings (stock recovery only of miui)
andd still no LUCK! I badly need some of you high IQ guys here to help me resolve this please My mind hurts its like the factory of fastboot of this phone has somehow got corrupted....
I can hear a sound when connecting via usb when on black screen fastboot mode
I can even access adb commands like " adb reboot bootloader & adb reboot fastboot " and they all leads to the BLACK SCREEN FASTBOOT (NO LOGO) MODE T.T

Does >fastboot devices respond with your phone?

HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is

HaveSomeCyanide said:
Does >fastboot devices respond with your phone?
Click to expand...
Click to collapse
after tweaking and tweaking it does. Fortunately MI Unlock also works even if its just a black screen fastboot mode. so weird but it is what it is

I believe that this shouldn't modify fastboot, try to reflash the latest and original MIUI rom using flash_all.bat (don't use flash_all_lock.bat)
It should fix any corrupted partitions. Or it may not do anything.