Database Develop

Official bootloader unlock procedure from LG AND the one that works for everyone ;)

I just checked my emails and saw a reply from LG, containing the official unlocking procedure
alright, so here you go:
Requirements
- Linux: no drivers, only adb and fastboot (Linux is preferable, because drivers can't mess something up I've used Xubuntu 12.10 BTW)
- Windows: all drivers (including fastboot drivers) installed and functioning
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware which is flashed several hours before trying to unlock the bootloader (and also being connected to the network)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The Steps
1) charge your phone to 100% (not mentioned by LG, but it helped for me)
2) connect your phone in LG software mode (every mode with an activated adb should work, too)
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
{
"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"
}
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
in Linux or
Code:
cd C:\...
on windows (if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
4) now you should see this on your phone:
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
Some people still think that
Code:
adb reboot bootloader
fastboot oem unlock
is the right command, but guess what: it isn't so please don't use it
Please follow below directions to unlock bootloader.
1. Turn on the phone with SIM card, and wait for connection to the real network.
2. Wait for couple of hours.
3. Connect your handset to local PC with USB cable.
4. Enter "adb reboot oem-unlock" in DOS command window.
5. Reboot handset and you can see the bootloader unlock guide on your phone.
6-1. If you press volume up key, handset is bootloader unlock status.
You can download custom image using fastboot command.
6-2 If you press power on key, user doesnot accept unlock bootlaoder and handset normally power on.
Click to expand...
Click to collapse
so this was the official way now we're gonna take a look into the way, that can unlock every bootloader (at least we've heard nothing opposite )
download this attatched BL_unlock file and extract it
execute the BL-unlock.bat
your bootloader is now unlocked
so what it does:
it copys the calue of the fuse "odm_reserved" to a temporary folder in /data/local
changes the value to an "unlocked" one
and it pushes the changed value back to the fuse
Be aware, that whatever you do, you do it on your own responsibility. I am not responsible for any damage that might occur.
Also keep in mind, that there is no way to relock it. So think before doing anything.

No matter which version?

I asked for the official unlock method, and lg said that only euro-open would be unlockable. But i guess it will work on some other firmwares too.
Sent from my LG-P880 using xda premium

Ask about uk too? Since you got a response and I didn't. Or make a modded kdz that always flashes to eur-xxx since you have mad skills lol
Sent from my rooted P880

@non4 said:
Ask about uk too? Since you got a response and I didn't. Or make a modded kdz that always flashes to eur-xxx since you have mad skills lol
Sent from my rooted P880
Click to expand...
Click to collapse
It is not kdz that should be moded it is the kdz flash program...

There must be something which controls the device ID or IMEI, because it is no longer possible to unlock. Allways stack on [LGE_SECURITY] Unlock permission denied. I did tried already all possibility including drivers, differen adb versions, downgrading, updating e.g.

It is done on Optimus G...maybe someone could contact developer of that app.
https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=hr
Also XDA dev.
http://forum.xda-developers.com/showthread.php?t=2094696

Doesn't work on 234. Security error.

On 232.14 - Unlock Permission Denied.
So with a branding you cannot unlock your boot loader. Maybe someone can find a workaround.
i have tried it on kubuntu with ADB.

nedooo said:
It is not kdz that should be moded it is the kdz flash program...
Click to expand...
Click to collapse
Yeah I'm thinking that, maybe we can spoof the region to lg flashtool or something, if its just flags in the kdz that are read by the flashtool it shouldn't be too hard to patch. Hopefully someone can :thumbup:
Sent from my rooted P880

@non4 said:
Yeah I'm thinking that, maybe we can spoof the region to lg flashtool or something, if its just flags in the kdz that are read by the flashtool it shouldn't be too hard to patch. Hopefully someone can :thumbup:
Sent from my rooted P880
Click to expand...
Click to collapse
German, Euro Open and Czech fw have same size and I don't think so, that they released difeffrent versions for several countries. But what I think is somewhere some specific RIL's region list what BL check before unlocking process.

In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob

mastershefis said:
German, Euro Open and Czech fw have same size and I don't think so, that they released difeffrent versions for several countries. But what I think is somewhere some specific RIL's region list what BL check before unlocking process.
Click to expand...
Click to collapse
that's what i'm thinking too. i guess there's the same BL on every firmware version. when trying to unlock the phone, the bootloader checks a file and "decides" then if it's unlockable or not...
Emin3ms said:
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
Click to expand...
Click to collapse
you need to execute the command in a folder, where your adb is

Emin3ms said:
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
Click to expand...
Click to collapse
Sounds like you havent installed it to CMD. Instead you can type cd C:/(name of adb directory) and hit enter, now adb commands should work. If you don't know what adb is do some research before messing with it
Sent from my rooted P880

I think that I need a little help with this process. I've entered the "Bootloader unlock mode" where I can see the warranty disclaimer etc, pressed "Vol Up" key to accept the terms and to continue with the process...after that, a red text appeared - "Download mode !!!". What should I do now, enter some commands in adb or...?

teddyxfire said:
I think that I need a little help with this process. I've entered the "Bootloader unlock mode" where I can see the warranty disclaimer etc, pressed "Vol Up" key to accept the terms and to continue with the process...after that, a red text appeared - "Download mode !!!". What should I do now, enter some commands in adb or...?
Click to expand...
Click to collapse
just do nothing the phone is making a factory reset and will reboot when it's done.
if it doesn't reboot itself, but says that it's done, just pull the battery and boot it manually

Ok I got 'unlock permission denied' si I cannot unlock or what i'm supposed to do?

laufersteppenwolf said:
just do nothing the phone is making a factory reset and will reboot when it's done.
if it doesn't reboot itself, but says that it's done, just pull the battery and boot it manually
Click to expand...
Click to collapse
Is it normal that this process takes a long time to complete? I think that it's been running for about 15 minutes now...

teddyxfire said:
Is it normal that this process takes a long time to complete? I think that it's been running for about 15 minutes now...
Click to expand...
Click to collapse
it was done in about 15 sec for me... try pulling the battery and boot it up. if it's unlocked, be happy, if not, try it again

Hello strange i have unlock denied message but i am on the Eur-xxx software non branded , ( polish software ) is there an option to open it ?:

motorola nexus 6 cant unlock boot loader please help

hello guys
i have moto nexus 6 xt1100 int i think its 6.0
i cant unlock boot loader i tried with SkipSoft ToolKit and with nexus root toolkit and with fastboot but not work
any help
thanx
:silly:

Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?

dahawthorne said:
Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?
Click to expand...
Click to collapse
hello sir
thanx to replay
i do
fastboot oem unlock
C:\Users\pc\Desktop\platform-tools>fastboot flashing unlock
...
FAILED (remote: Unknown command)
finished. total time: 0.002s
C:\Users\pc\Desktop\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\pc\Desktop\platform-tools>

The answer is in the output. You must go into Settings > Developer Options and select "Enable OEM Unlock" before you can unlock the bootloader.

i cant go to setting to open oem lock becuase pbone after upgrade ota 60 now cant open still hung google nexus screen plz hlp plz

any one help me plz

Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.

TMG1961 said:
Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.
Click to expand...
Click to collapse
im sorry to late phone is locked plz be fix and not open just google screen not work even after wip frm recvry

Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.

Didgeridoohan said:
Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.
Click to expand...
Click to collapse
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.

Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
True... Didn't think of that. That's a good workaround until N is released.

Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
hello sir
again so sorry to late and thanx to replay
i think no bady undrstand my prob my brop is after update ota 60 phone was like photo under long time all day just like this photo oky i do wip data factory reset from recovery not work
and i tried to flash other fimrware from all toolkit nexus but need unlock boot but cant unlock
please can u help me
im here wating every bady
{
"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"
}

please brothers help me

------------------------------------------------------------------------------------
Follow the Instructions on the devices screen to Unlock your BootLoader.
Enable the developer options screen by going to the settings, about screen and
clicking on build number at the bottom 7 times. Then go to developer options and
tick USB debugging so the procedure to continue.
If you get stuck on 'Waiting for USB debugging to be enabled' and have already
enabled USB debugging then just unplug/replug the usb cable and it should proceed.
IF NOTHING HAPPENS TRY PULLING DOWN THE NOTIFICATION SCREEN AT THE TOP LEFT WITH
THE DEVICE CONNECTED, THEN CLICK ON 'CONNECTED AS' AND CHANGE TO PTP MODE.
On Android 4.2 or later when you replug the usb cable after enabling usb debugging
for the first time you will get a popup asking you to authenticate your pc.
Tick 'Always allow' then click 'ok' and everything should carry on as normal.
LASTLY BEFORE STARTING, LOOK IN DEVELOPER OPTIONS IF YOU NEED TO CHECK THE
'ENABLE/ALLOW OEM UNLOCKING' OPTION TO ALLOW THE DEVICE TO BE BOOTLOADER UNLOCKED.
------------------------------------------------------------------------------------
Are you ready to start? Type y[yes] or n[no]:y
Device detected in FASTBOOT MODE
Device Serial Number is: ZX1G4244LL
When prompted, Press the 'Volume up' button to highlight Yes on the screen, then
press the 'Power' button to select it and Unlock your Bootloader. If you are
already unlocked then this will just be skipped and your device will not be wiped.
ERROR: The device cannot be bootloader unlocked in its present state
You need to enable OEM Unlock in developer options in Developer options..
Once the device has rebooted to Android do this and the Unlock routine should work

any help

Ok... You need to stop trying to unlock your bootloader. You can't.
You have a couple of options:
1 - If you have TWRP recovery installed, flash a custom rom and you'll be good to go.
2 - If you do not have a custom recovery, try flashing the N OTA from here: http://developer.android.com/preview/download-ota.html. After that, go here https://www.google.com/android/beta and enroll and then unenroll your device. Soon after (up to a day, probably) you'll get an OTA for Marshmallow.
You might want to unlock your bootloader while you're in the N preview, so you won't have to go through this again...
Edit: Reading your post again I realised you probably don't have TWRP installed, since you wouldn't have gotten that far with an OTA in that case.

C:\android>adb sideload <ota-package>
The syntax of the command is incorrect.
C:\android>

thanx to replay
but not work with me cannot read update zip:crying:

I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".

Strephon Alkhalikoi said:
I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".
Click to expand...
Click to collapse
apply update from ADB
not work

Can not flash TWRP, Status Code: 2

I am currently trying to install LineageOS on my Nexus 6 but can not replace the original bootloader. I enabled USB debuging and OEM Unlock, but when I reboot into recovery I am greeted with the message "Device is LOCKED. Status Code: 2". All attemts at replacing the bootloader fail.
I bought my phone used, from ebay. The previous owner might have meddled with it.
I tried:
-Turning the developer options on/off (didn't change a thing)
-I signed in using my Google account
-adb devices (works)
-fastboot devices (doesn't work)
Am I missing something?

reogaro said:
I am currently trying to install LineageOS on my Nexus 6 but can not replace the original bootloader. I enabled USB debuging and OEM Unlock, but when I reboot into recovery I am greeted with the message "Device is LOCKED. Status Code: 2". All attemts at replacing the bootloader fail.
I bought my phone used, from ebay. The previous owner might have meddled with it.
I tried:
-Turning the developer options on/off (didn't change a thing)
-I signed in using my Google account
-adb devices (works)
-fastboot devices (doesn't work)
Am I missing something?
Click to expand...
Click to collapse
You keep saying "replace bootloader" I hope you mean unlock.
With a working fastboot on your PC AND the phone in fastboot (bootloader) mode, you need to use the command "fastboot oem unlock". This will wipe internal storage and factory reset the device.
To boot into the fastboot mode, start from a powered off state then press and hold Volume Down, Volume UP and Power buttons simultaneously. Let go of the buttons when the Fastboot menu appears.
You sound as though you're new to the device. I suggest you read the first post, and the final 10-15 pages of the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. It's important to read through those final pages because there are changes to the process since the thread was originally written.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
You keep saying "replace bootloader" I hope you mean unlock.
With a working fastboot on your PC AND the phone in fastboot (bootloader) mode, you need to use the command "fastboot oem unlock". This will wipe internal storage and factory reset the device.
To boot into the fastboot mode, start from a powered off state then press and hold Volume Down, Volume UP and Power buttons simultaneously. Let go of the buttons when the Fastboot menu appears.
You sound as though you're new to the device. I suggest you read the first post, and the final 10-15 pages of the [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. It's important to read through those final pages because there are changes to the process since the thread was originally written.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thanks for the quick reply! I meant replace the recovery and unlock the bootloader. Poor choice of words by me there, I am indeed new to the device (and Android in general. It's my first Android phone). I was following the Beginners guide and kept trying "fastboot OEM unlock", which was outdated. "fastboot flashing unlock" worked.
After doing my homework and reading through the thread I was able to instal TWRP and Magisk. Took me some time because I was too nervous about breaking something. Thanks for the hint. I am right now reading on how to install a custom ROM (Paranoid Android? Any recommendations for privacy oriented ROMs/finding ROMs in general?).
This question might not be fully on-topic, but is there a page like "All you need to know about Android rooting" that explains the inner workings of Android, but more in-depth? And in general, if I have a bunch of these newbie-questions, where could I ask them? I am thinking about expanding my Java knowledge to Android development.

reogaro said:
Thanks for the quick reply! I meant replace the recovery and unlock the bootloader. Poor choice of words by me there, I am indeed new to the device (and Android in general. It's my first Android phone). I was following the Beginners guide and kept trying "fastboot OEM unlock", which was outdated. "fastboot flashing unlock" worked.
After doing my homework and reading through the thread I was able to instal TWRP and Magisk. Took me some time because I was too nervous about breaking something. Thanks for the hint. I am right now reading on how to install a custom ROM (Paranoid Android? Any recommendations for privacy oriented ROMs/finding ROMs in general?).
This question might not be fully on-topic, but is there a page like "All you need to know about Android rooting" that explains the inner workings of Android, but more in-depth? And in general, if I have a bunch of these newbie-questions, where could I ask them? I am thinking about expanding my Java knowledge to Android development.
Click to expand...
Click to collapse
If "fastboot flashing unlock" worked, you don't have a Nexus 6 which is what this forum is for.
Maybe you have a 6P?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
If "fastboot flashing unlock" worked, you don't have a Nexus 6 which is what this forum is for.
Maybe you have a 6P?
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
I definitely have a Nexus 6 (s. Photo). Maybe it was something else I did but this morning I went into recovery, ran both "fastboot oem unlock" and "fastboot flashing unlock" and it worked. All previous attempts (only using "fastboot oem unlock") failed, which is why I assumed that "fastboot flashing unlock" was the missing step to unlock my Bootloader.
{
"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"
}

hi. i know that this is a very old thread, but i will try. i have the very same problem as you had, expcept that non of the commands above work for me. i also tried the auto root program that chainfire made, but that doesn't work neither. do anyone has any idea what else can i try to unlock the bootloader?

@D_vid97
You'll need to tell us more about how far you get.
Do you have fastboot working? (To test, type fastboot devices and check that a device is shown).
Some people recommend using an old version of fastboot, from when this phone was supported. However, I haven't tried that myself.

runekock said:
@D_vid97
You'll need to tell us more about how far you get.
Do you have fastboot working? (To test, type fastboot devices and check that a device is shown).
Some people recommend using an old version of fastboot, from when this phone was supported. However, I haven't tried that myself.
Click to expand...
Click to collapse
I have fastboot working, device shows up at active, or something similar.
When I type the in the oem unlock code, tried fastboot oem unlock, and fastboot flash unlock too, but both of them ended up showing the same result. Fastboot says waiting for device, but the phone sitting still like nothing happened
Drivers are installed.
In developer options both usb debugging and oem unlocking are turned on, but I tried in every combination possible

I will try using an older version of fastboot, from around 2015, but I don't know why would they stop supporting older devices

D_vid97 said:
I have fastboot working, device shows up at active, or something similar.
When I type the in the oem unlock code, tried fastboot oem unlock, and fastboot flash unlock too, but both of them ended up showing the same result. Fastboot says waiting for device, but the phone sitting still like nothing happened
Drivers are installed.
In developer options both usb debugging and oem unlocking are turned on, but I tried in every combination possible
Click to expand...
Click to collapse
Well, it sounds like you do the right thing, but I'm going to ask stupid questions just in case:
1) "type the in the oem unlock code". What code? I don't remember that the Nexus 6 has a code.
2) fastboot oem unlock is correct. Phone must be in bootloader state when you do it.
3) USB cables/port can be unreliable.

runekock said:
Well, it sounds like you do the right thing, but I'm going to ask stupid questions just in case:
1) "type the in the oem unlock code". What code? I don't remember that the Nexus 6 has a code.
2) fastboot oem unlock is correct. Phone must be in bootloader state when you do it.
3) USB cables/port can be unreliable.
Click to expand...
Click to collapse
Answers for your questions.
1. Earlier on this thread two oem unlock codes were mentioned, "fastboot oem unlock", and "fastboot flash unlock", no special ones for this device as far as I know
2. Phone is in bootloader
3. I can reboot the phone to bootloader from fastboot, typing in "adb reboot bootloader", so usb cables and ports are reliable in my opinion.

D_vid97 said:
Answers for your questions.
1. Earlier on this thread two oem unlock codes were mentioned, "fastboot oem unlock", and "fastboot flash unlock", no special ones for this device as far as I know
2. Phone is in bootloader
3. I can reboot the phone to bootloader from fastboot, typing in "adb reboot bootloader", so usb cables and ports are reliable in my opinion.
Click to expand...
Click to collapse
Fastboot flashing unlock. The command you typed isn't a valid command.

'fastboot devices' command not working

Hi guys, I specially made an account due to this frustrating event of not being able to use the fastboot devices command after unlocking my Max Pro M1's bootloader, so as to install a Custom ROM.
Tried everything possible but to no avail. The adb devices command works fine and my phone shows up on the computer. But on fastboot, when i execute the command 'fastboot devices' i get a response with "????????" and my phone screen turns black with a message on the top left corner stating press any key to shut down. PLEAAASE HELP!

D0CT0RFATE said:
Hi guys, I specially made an account due to this frustrating event of not being able to use the fastboot devices command after unlocking my Max Pro M1's bootloader, so as to install a Custom ROM.
Tried everything possible but to no avail. The adb devices command works fine and my phone shows up on the computer. But on fastboot, when i execute the command 'fastboot devices' i get a response with "????????" and my phone screen turns black with a message on the top left corner stating press any key to shut down. PLEAAASE HELP!
Click to expand...
Click to collapse
Enable oem unlock in developer options
and does your phone show when you do " adb devices "

flairepathos.info said:
Enable oem unlock in developer options
and does your phone show when you do " adb devices "
Click to expand...
Click to collapse
Hey, I'm unable to locate the "oem unlock" option under developer options. However, i tried unlocking the bootloader yesterday with help of USB debugging. That didn't initially work, so i did the bootloader unlocking through the Asus app that i downloaded externally, which was successful (without PC).
That aside, adb seems to be working fine as the command "adb devices" results in showing my phone as connected. But 'fastboot devices' command simply does not work, so now I'm just left with a Bootloader unlocked phone.

Attaching a picture for more clarity.
These are the commands I typed after my phone entered fastboot mode.
After the last result, my phone screen turns black with a message on the top left corner saying press any key to shut down.
There seems to be a problem only with fastboot.
It would be great if anyone could provide a solution or help in any way possible!
{
"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"
}

D0CT0RFATE said:
Attaching a picture for more clarity.
These are the commands I typed after my phone entered fastboot mode.
After the last result, my phone screen turns black with a message on the top left corner saying press any key to shut down.
There seems to be a problem only with fastboot.
It would be great if anyone could provide a solution or help in any way possible!
View attachment 5400501
Click to expand...
Click to collapse
It's probably something in the boot partition or tee partition, this is first time i see this but i did some research and found that it's not a hard locked device and releases with the developers proprietary engeneering drivers and user drivers
so the commands must be done in succession when enter fast boot using a bat script : here is the guide
[GUIDE][UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
DATA WILL BE WIPED SO MAKE A BACKUP (instructions are there in rar too) Unlocking 1. Download this rar and you'll get 2 folders namely unlock and ASUS_Android_USB_drivers_for_Windows 2. Install the drivers according to your OS and go the unlock...
forum.xda-developers.com

Thanks man, will try it sometime and give an update. As of now, this is my sole phone, so i'll work around with all this once i get a replacement. Until then, stock ROM it is

Quick update! 'Fastboot devices' command worked fine on my old PC with Windows 7 on it. Didn't require any extra steps nor did I go through any hassle like on the newer Windows 10. And ofc I was also able to install the custom recovery as well.
This clearly looks to be a Windows 10 issue.

Question Stuck in FastBoot Mode loop , recovery and rescue mode give boot failure, bricked?

Hi!
I got this new Pixel 7 2 weeks ago, yesterday the battery went completly discharged and now the phone starts into Fastboot mode, with the Enter Reason being boot failure. Recovery mode and rescue mode both fail to load, and just send me back to the Fastboot Mode. I alredy tried a bunch of stuff to fix it, but the phone its still OEM lock so flashing via the Google flash tool its imposible, does anyone has any idea of what can i do to save it?

Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection

t-ryder said:
Did you try this too?
https://pixelrepair.withgoogle.com/carrier_selection
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"
}
yes, Rescue Mode fails to load, so it gives me Unable to connect the Phone

There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
No, i am going to give it a go and update on results

t-ryder said:
There's fastboot mode and fastbootD I guess. You can enter fastbootD from fastboot. Maybe I confuse stuff tho, since lately I got a lot of chaos in my head. DYOR.
Have you tried Pixel Flasher?
https://github.com/badabing2005/PixelFlasher/releases
Click to expand...
Click to collapse
It failed, it gives me "Bootloader is locked, can't flash." and trying to unluck the bootloader with the fastboot commands gives me FAILED (remote: 'flashing unlock is not allowed')

And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?

t-ryder said:
And get into fastbootd and sideload a full OTA somehow?
https://developers.google.com/android/ota?hl=en
Or is adb disabled?
Click to expand...
Click to collapse
adb its disabled and entering recovery mode also fails, the phone its pretty much new, so i didn't have time do much with it.

I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...

Lughnasadh said:
I've seen this before where people's phones have "died" when letting the battery run out. I haven't seen any successful methods to recover (not to say there isn't).
Since you're bootloader is locked and you don't have OEM Unlocking enabled you won't be able to flash anything via fastboot. If OEM Unlocking were enabled you would be able to use Android Flash Tool as that will unlock your bootloader during the process as long as you have OEM Unlocking enabled.
Maybe try to see if Pixel Flasher can get you into recovery mode to see if you can sideload an OTA, although given the circumstances I'm doubtful it will. By the way, you don't need USB Debugging enabled to sideload an OTA. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip.
Good luck...
Click to expand...
Click to collapse
Even trying to get into recovery mode with Pixel Flasher fails.. looks like my only option its asking for warranty and i wanted to avoid that.

Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.

41rw4lk said:
Have you tried issuing the command fastboot getvar all to see what slot you're on and what the status of your slots are? Maybe switching slots could get you a boot.
Click to expand...
Click to collapse
Unfortunately their bootloader is locked so they won't be able to switch slots via fastboot commands. Even if they were able to switch slots they would then have to flash the OS to that slot before being able to boot into that slot since you can only boot into the slot where the OS was last flashed in this circumstance.

I can't get over the fact that you can't just flash an official image on a locked bootloader. I used to be a Moto fan and that was always the good thing about them, as long as it was officially signed, locked or not you could flash the same or updated firmware. Plus if it was qualcomm, when you bricked it would go into edl mode and you could blankflash your way back.
Yet a Google device, who also develops android, you're up a creek unless you unlock your bootloader.