Develop Bugs

Can't manage to unlock my nexus bootloader succesfully

Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks

How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...

gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.

since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin

THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM

First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)

There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img

I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S

use the galaxy nexus toolkit to unlock bootloader, root

Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.

Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S

Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.

Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it

AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250

OP, OMAP flash?

Cannot boot into bootloader/fastboot

Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6

remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode

auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?

Seriously nobody? I thought this phone has good community and support...

I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:

charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock

ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.

I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.

you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU

samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.

SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device

ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk

SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too

ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk

I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.

Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.

Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.

i can't boot my phone and i need your help!

i really need your help, please help....
i rooted my phone...
(i rooted it with magisk) buy a while after i wanted to revert the phone, and to use the stock operation system without root
i used TWRP to wipe anything (besides internal storage, where the oxygen os was), and OEM unlocked my device (using command prompt)... after that, i wanted to install the software using the OnePlus recovery, but than i noticed that i have forgotten to enable USB debugging and OEM Unlocking (this was the mistake, because now i dont think i can do anything with the computer... when i want to install the operation system using the command prompt (fastboot flash system) i cant...
(erasing 'system'... FAILED (remote: Erase is not allowed in Lock State)) ans when i want to unlock the OEM the same thing happens, an error shows up ()
i attempted to enter the recovey... but there is another error: your device is corrupt. it can't be trusted and will not boot
visit this link on another device: g.co/Abh)
i have no clue what to do, i dont have a cellphone right now and i have no hope... it is a new one, but it 20 days ago and im so upset...please help!!a

Is your phones bootloader is unlocked or what??

locked
it is locked (i mean i can do nothing becuse USB Debugging and OEM unlocked are not ticked in the settings)

Don't worry too much, the newer snapdragon devices such as the op5t are ubrickable. Try to search something like "unbrick a hard bricked phone with snapdragon soc"

TNX... i managed to solve it, it was bricked
Dixi99 said:
Don't worry too much, the newer snapdragon devices such as the op5t are ubrickable. Try to search something like "unbrick a hard bricked phone with snapdragon soc"
Click to expand...
Click to collapse
thank you!!! i found a youtube video about it and i unbricked it...!! i didnt even know what it is called...

it wasnt loced
rakesh595160 said:
Is your phones bootloader is unlocked or what??
Click to expand...
Click to collapse
nope, it wasn't, but i could do nothing with it because USB Debugging and OEM unlocking were not ticked in the settings

I unbrick my OP5T two times with this tool 100% working

Question Locked phone stuck in Fastboot mode

Hey everyone!
I was updating to the latest Android beta to try to get the Move to iOS app to work. The update seemingly went fine and I was using my phone (on reddit lol) and suddenly it powered off.
Now when it starts I get a black screen that asyas "Fastboot Mode". My phone isn't unlocked so I haven't done anything funky with the firmware.
I'm afraid I've lost everything on the phone
Here's a picture of what the phone shows:
https://imgur.com/oBpGFGX

Well, the fact you can boot into fastboot is good news
Before we talk about possible actions:
- what ROM exactly were you coming from ? Was that rooted or with a custom kernel ? Was the device unlocked ?
- what ROM exactly have you been flashing ? By using which method ? Any additional steps you did while/after flashing this ?

s3axel said:
Was the device unlocked ?
Click to expand...
Click to collapse
Besides @adamkparker's statement below, the screenshot shows the bootloader is locked, unfortunately.
adamkparker said:
My phone isn't unlocked so I haven't done anything funky with the firmware.
Click to expand...
Click to collapse
You should never install Betas without having the bootloader unlocked. Is OEM unlocking at least enabled in Developer Options (I know you can't get in there right now, but was it enabled before the phone stopped being able to boot to Android)? If OEM unlocking is enabled, even with the bootloader locked now, you can try Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
If OEM unlocking isn't enabled, there's probably nothing you can do to fix the phone - you'll have to RMA it.

Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader

fil3s said:
Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader
Click to expand...
Click to collapse
You can sideload OTA updateds without USB debugging enabled. It's really the only way forward for op.

Question can't get get unlock_code or fastboot oem unlock on LE2127 T-MOBILE

Hello everyone, I have a LE2127 in C.20 software and I have been seeing some things that I don't particularly like the camera, first I see that it only uses the second lens, the others are never used, I already did the typical test of switching between the options and Go covering to see which lens it uses, enter the camera config that it brings which is -> LCM 8.4 and I went to the additional cameras section, I enabled them and one of the ones below works when trying to change the app crashes and does not return to open.
The truth is that I already installed a gcam port and it continues to use only one lens, I feel that I am not taking advantage of the phone as it should be due to its cameras and I want to remove that rom that it has from t-mobile.
but as I describe in the title I follow the steps and when doing fastboot get_unlock_code it only stays in <waiting for any device> and nothing happens in my idea of achieving it I tried a fastboot oem unlock and nothing happens either, I clarify that I always place the device in fastboot with bootlader reboot and leave it at the fastboot START screen.
I would appreciate anyone who can guide me on what I am doing wrong and if what I am saying is normal, that I always only use the camera with the second lens, it seems absurd to me.

Are you sure you have the right fastboot driver installed? Which version did you install?
If you're planning to flash roms anyway, you could skip the need for unlock.bin (takes a week to get) by flashing the Tmo->Eu MSM in EDL mode. Then take global/eu OTA roms from oxygen updater. Or use One+_TooL to ungray the oem unlock toggle and unlock the bootloader to root and flash custom roms. No unlock_token is needed. Sim unlock is not needed either.
But you should fix the fastboot driver either way. Lettuce know which one you installed

Use platforms-tools r31.0.3 on windows and official oneplus drivers
You know what I noticed strange regarding the tutorials that in which I saw everything is with the fastboot command, it does not work for me like that, I must use an example adb devices

Lu7h0r said:
Use platforms-tools r31.0.3 on windows and official oneplus drivers
You know what I noticed strange regarding the tutorials that in which I saw everything is with the fastboot command, it does not work for me like that, I must use an example adb devices
Click to expand...
Click to collapse
Solved: Can not access fastboot device driver not found and I can not locate any either
So I have the drivers usb_driver_r13-windows: from google they do not work and as far as I can see they are the latest They are from 7/23/2020 but they are the latest Google provides. I have installed OP9P_Default_Drivers, do not help at all...
forum.xda-developers.com
Install the sdk adb/fastboot and usb drivers, may need to disable driver signing as mentioned in this thread too
Edit: be sur3 to use original cable also

Lu7h0r said:
Hello everyone, I have a LE2127 in C.20 software and I have been seeing some things that I don't particularly like the camera, first I see that it only uses the second lens, the others are never used, I already did the typical test of switching between the options and Go covering to see which lens it uses, enter the camera config that it brings which is -> LCM 8.4 and I went to the additional cameras section, I enabled them and one of the ones below works when trying to change the app crashes and does not return to open.
The truth is that I already installed a gcam port and it continues to use only one lens, I feel that I am not taking advantage of the phone as it should be due to its cameras and I want to remove that rom that it has from t-mobile.
but as I describe in the title I follow the steps and when doing fastboot get_unlock_code it only stays in <waiting for any device> and nothing happens in my idea of achieving it I tried a fastboot oem unlock and nothing happens either, I clarify that I always place the device in fastboot with bootlader reboot and leave it at the fastboot START screen.
I would appreciate anyone who can guide me on what I am doing wrong and if what I am saying is normal, that I always only use the camera with the second lens, it seems absurd to me.
Click to expand...
Click to collapse
If your interested in converting your T-mobile variant to Global then you won't need a unlock code and you can unlock the bootloader without it plus the new Android 13 fixes the no sim detection issue that was happening on Android 12 with the T-Mobile model. I'm on it now and works great.
OnePlus 9 Pro TMO Le2127 Converted to Global Le2125 OOS 13 OB2
First convert to EU using the TMO to EU MSM Tool then install global firmware from the OnePlus website. Update it all the way to C.65 then install the OOS 13 OB2 firmware, go into settings and factory reset and your done VOILA ! Everything works...
forum.xda-developers.com

Try this one

djensen777 said:
Try this one
Click to expand...
Click to collapse
Why would you post that? A unlock bin is device specific. It won't work. It will cause a verify error.

TheSayaMan said:
Why would you post that? A unlock bin is device specific. It won't work. It will cause a verify error.
Click to expand...
Click to collapse
Yep, unlock.bin is based on bootloader unlock code!