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 ?:

I'm Stuck with Nexus 6 locked Bootloader

I encrypted my phone while it was rooted and somehow I lost everything. The device magically locked the boot loader. I can't seem to find a solution.

Define everything? Can you get into recovery?
Sent from my Nexus 6 using XDA-Developers mobile app

No, I can't even get into recovery. I tried pressing power and volume +, but no lock. There is the android logo with "no command". I can't even unlock the bootloader as it appears that there is no rom so I can't go into developer option. "Device is Locked. Status Code: 2"

No guarantees, and I haven't read this thoroughly myself, but you may be lucky:
http://forum.xda-developers.com/showpost.php?p=66475726&postcount=4

The OP apparently doesn't have a recovery either, which makes flashing the Android N OTA impossible. If that is the case, the device is bricked.

Strephon Alkhalikoi said:
The OP apparently doesn't have a recovery either, which makes flashing the Android N OTA impossible. If that is the case, the device is bricked.
Click to expand...
Click to collapse
Yeah I tried on my windows using minimal adb and fastboot it keeps telling me "check 'allow OEM Unlock' in Developer Options." Now is there a way I can completely erase the phone? I remember on my oneplusone I did it before. I wiped the cache and userdata but no luck.

Thanks, Strephon - I had missed that.
Still, the OP mentions: "the android logo with "no command"".
This post:
http://forum.xda-developers.com/showpost.php?p=66467329&postcount=12
has these comments:
"Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttons (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb"
Again, I haven't thought this one through (tiring day) but it's worth a shot...

If you have no system, then you've already erased the device. Give the advice by @dahawthorne a shot before calling it a day. You may actually have a recovery still, but it's just not easily accessed.

Oh No! Now it's just the android logo. Fastboot devices appears but no ADB in command prompt.
{
"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"
}

Maybe I'm misunderstanding this last post: " Fastboot devices appears"
ADB commands are for when the device is connected, switched on with USB debugging enabled. If you type "adb devices" in the CMD window you can expect to see "ZGST339FF6 device" or similar. From there you can type "adb reboot bootloader" and the phone will enter bootloader mode. [Edit: the Android image has just loaded on my screen now - that looks like stock recovery].
Once you're in bootloader mode you use fastboot commands. "adb devices" won't work. "fastboot devices" should show "ZGST339FF6 fastboot".
So are you saying that when you enter "fastboot devices" you get a response? Or nothing at all?
Have you done all the required background reading about installing drivers/ADB/fastboot and how to use them? Without actually sitting beside you watching what you're doing we're groping in the dark here...

dahawthorne said:
Maybe I'm misunderstanding this last post: " Fastboot devices appears"
ADB commands are for when the device is connected, switched on with USB debugging enabled. If you type "adb devices" in the CMD window you can expect to see "ZGST339FF6 device" or similar. From there you can type "adb reboot bootloader" and the phone will enter bootloader mode. [Edit: the Android image has just loaded on my screen now - that looks like stock recovery].
Once you're in bootloader mode you use fastboot commands. "adb devices" won't work. "fastboot devices" should show "ZGST339FF6 fastboot".
So are you saying that when you enter "fastboot devices" you get a response? Or nothing at all?
Have you done all the required background reading about installing drivers/ADB/fastboot and how to use them? Without actually sitting beside you watching what you're doing we're groping in the dark here...
Click to expand...
Click to collapse
I get a response when I enter "fastboot devices", and I see the device. However, I can't use the command fastboot oem unlock. It tells me that I have to select enable oem unlocking.

You're not reading the posts that I pointed you to. You need to download the Android N preview OTA and sideload it in that recovery screen via the CMD window. Once you've got Android N on the device you may be able to unlock the bootloader, though I've seen comments about it being greyed out. If you manage to load Android N then at least you have a working device, no? And if you do manage to unlock the bootloader then you can flash whatever ROM you like.

Problem occurs at Step. 4 "Select the option "Apply update through ADB"
I do not get the list of options.....even after Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.

dahawthorne said:
You're not reading the posts that I pointed you to. You need to download the Android N preview OTA and sideload it in that recovery screen via the CMD window. Once you've got Android N on the device you may be able to unlock the bootloader, though I've seen comments about it being greyed out. If you manage to load Android N then at least you have a working device, no? And if you do manage to unlock the bootloader then you can flash whatever ROM you like.
Click to expand...
Click to collapse
Android N Preview 2 grays out the "Enable OEM Unlock" option, while Preview 1 doesn't. The reason the Preview 1 OTA works so well to recover bricked devices is that it is a full system image, signed by Google, and flashable through the stock recovery. The Preview 2 OTA zips are most likely deltas, and thus only include the changes made to the system, rather than the complete system image.

Problem solved. Uninstall all android drivers. Reinstall new ones via google usb installer. Make sure in recovery mode you hit power, volume +, and volume - continuously until you see the options. Thank you all!

So do we understand that you have a working device?

yessiirr!

If your stuck in a locked state and want to downgrade. (Android N grays out OEM unlocking) Go to https://www.google.com/android/beta and opt in using the email your using on the phone. Then opt out. Go to settings and a OTA downgrade will be given.

Maybe hard bricked? Android won't start without PW after 3.1.3 update....never set pw

hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
update 1: hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....
update 2: I got adb to work...gonna play with that and see if I can do anything.
update 3: Here is a link to a video showing what I am talking about when I say the "oneplus logo" just flashes...
Video starts out with me just pushing the power button..then it looks like it is going to boot up..then hits that decryption unsuccessful screen..so, I tap reset, at this point, it will reboot and attempt to go into the recovery partition and wipe data...but, you can see that it just reboots and the one plus logo flashes, screen goes black and eventually the notification LED turns solid white.
so, next in the video..I power the device off and try to manually enter recovery mode (vol- + pwr) and same thing, oneplus logo flashes and blank screen. Anyway, here is the link to the video.
https://goo.gl/photos/EU2ZSkFw1JrdExeQ8
update 4: Level 2 OnePlus Support did NOT fix the issue. He didn't even give me a reason when I asked what the issue was, however, I did see that it failed out when he attempted to use the MSM tool. he escalated to the next level of support.

I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads

cms062407 said:
hello all....sooo..I have been attempting to bring my op3 to stock...so, I unrooted, applied the 3.1.3 update and UNCHECKED "OEM Unlocking" in dev options (i think that is where i screwed up) and went to the "all in one tool kit" and clicked on "lock bootloader"...it all went well, but when the phone rebooted, it is saying "To start android, enter password"..but I never even set a password..is there a default password or something I should be entering? also, I have tried to relock bootloader, format the phone..and obviously it is saying that "flashing not allowed" or "oem unlock is not allowed".......what in the world do I do to get this phone working again? Thanks a lot.
oh, also, I can't reboot back into TWRP, which seems obvious since the bootloader is now locked.
I can run fastboot commands of course, but nothing seems to stinking work here!
Device is not showing up when I run "adb devices"
I really appreciate any help! This is frustrating. I should have just kept the "oem unlocking" checked in dev options
Click to expand...
Click to collapse
Can you try and install the file via normal, recovery?

Edu616 said:
Can you try and install the file via normal, recovery?
Click to expand...
Click to collapse
hmm, well got an update....I just kept entering random passwords and it finally said "phone will be wiped after next failed attempt"..I was fine with that, so i typed something in...and the phone rebooted and it booted back up to a screen that says "decryption unsuccessful" the password you entered is correct, but unfortunatley your data is corrupt. To resume using your phone, you need to perform a factory reset...and it has a button at the bottom that says "reset"...so, i hit the "reset" button and the phone reboots and tried to go into recovery and the "one plus" boot logo flashes VERY quickly and then the phone just seems to shut down, screen goes black..I wait a bit and power the phone back on and it goes back to that same "decryption unsuccessful" screen...
I can NOT get into stock recovery (that was replaced with TWRP, anyway) or TWRP.....if i try to fastboot into recovery the phone will reboot and the "one plus logo" will flash very fast and then just go to a blank screen.....

Bradl79 said:
I wonder it it has the oneplus one bug to where if u relock ur bootloader u can't unlock it, also I don't think u need to relock if u r flash an OTA just unroot and refresh stock recovery (which no one has pulled yetyet, that has been tested), u may want to contact oneplus and see if they will give u that stock OS to fastboot files, also with the pw issues, all u had to do was boot into twrp and goto file manager and delete the pw key, it's somewhere in this forum that shows u how to do it, i think it's in one of the 3 trwp threads
Click to expand...
Click to collapse
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.

cms062407 said:
Unfortunately, I can not boot into TWRP to do anything
I am pretty sure the problem is it won't boot into TWRP because the bootloader is now locked, again and I do not have stock recovery of course, since I installed TWRP.
Is there no way that you know of to relock the bootloader without having to actually go into the dev options and select "OEM unlocking"? any sort of command I can run? I can't seem to find any
Thanks, sir.
Click to expand...
Click to collapse
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery

Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
going to try now! will update in a couple of minutes.

cms062407 said:
going to try now! will update in a couple of minutes.
Click to expand...
Click to collapse
best of luck, i hope it does work out for u

Bradl79 said:
ok since ur recovery partition if f'd, u can be our guinea pig, download this "stock recovery" (download the recovery.emmc.win and rename to recovery.img and flash via fastboot (fastboot flash recovery recovery.img), this was the only stock recovery pulled via twrp, he did it as a twrp backup, can't do any more damage than u have now and let us know if it works so we can have a real stock recovery
if it does work and u get stock recovery u should be able to sideload the Oxygen OS 3.1.3 zip file and install and have a clean install, u may be able to unlockbootloader via dev options and fastboot
MAKE SURE U DOWNLOAD THE 1st FILE, NOT THE SECOND, ITS AN MD5 file and that wont work, the file should be about 64mb for the stock recovery
Click to expand...
Click to collapse
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
{
"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"
}

cms062407 said:
well, didn't work...I feel as if something is up with the encryption of the phone here is a screenshot of what happens when I try to flash the recovery.img....it always says "partition flashing is not allowed" when i try to flash anything.
Click to expand...
Click to collapse
what is the error u get when u try to unlock the bootloader via fastboot?

Bradl79 said:
what is the error u get when u try to unlock the bootloader via fastboot?
Click to expand...
Click to collapse
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..

cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.

Bradl79 said:
yeah i think u r right, so u have no recovery or no OS installed, correct, i wonder if someone who is smarter than me on here can show u how to flash OOS manually yet, i can try to pull the partitions and send them to u and see if u can flash via fastboot, it may take me a bit, but i will upload them and have u download 3.1.3 partitions, i don't think u can flash recovery with out BL unlocked but u may be able to other partitions.
Click to expand...
Click to collapse
sure, it wouldn't hurt to try to manually flash...but I bet we get the same error

cms062407 said:
Here is the error...which, I think, is because I unchecked "OEM unlocking" in dev options..
Click to expand...
Click to collapse
OEM unlock essentially opens up the system partitions to be writeable, so since your system is still locked, it makes sense that you can't flash anything. There are a number of OnePlus/Qualcomm unbricking tutorials that you can lookup, but you'll need the right files and I don't think anyone has made a full unbricking set of partitions with flash instructions for the OnePlus 3. I could be wrong though. I think there could be hope for your phone, just not quite right away.

thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.

Bradl79 said:
thank u @tesherx that would make sense on why he can't, i'll still upload them anyway so if anyone needs them for whatever reason.
Click to expand...
Click to collapse
I think those partitions will be part of the final solution, but there has to be flash maps with them as well to correctly identify the sizes,locations, etc. Considering the OnePlus 3's level of developer support so far, I think a complete unbricking tutorial won't be far away.

@cms062407 - sorry that you're going through this, this is a little weird though, oneplus should have given priority to unlock bootloader even when the os doesnt work.. i mean what will people do if their phone soft bricks ? its a dead phone since you cant flash files, enter recovery or factory reset !! this is just stupid of oneplus.. but then again if this was the case anyone would steal a oneplus3 and use it as their own... damn this is messed up.

Thanks. But, there will be a fix, right?

Have you tried to just erase your userdata partition to remove encryption with the command
Code:
fastboot format userdata
Hope you'll get through.

cms062407 said:
Thanks. But, there will be a fix, right?
Click to expand...
Click to collapse
Even if bootloader is locked, there should be some recovery, OnePlus or twrp. Isn't it there?

how to flash NEXUS 6 XT1103 ROM, BOOTLOADER LOCKED, CAN'T GET INTO PHONE, PLEASE HELP

PROBLEM -
I can not get into phone settings or ANYTHING ELSE because it keep SHOWING this error and LOADS NO OS or any icon THING AFTER BOOT
{
"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"
}
I tried from adb and it didn't work :-
<<< C:\adb>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
- I have downloaded rom from google for my phone model
- I can not ENABLE OEM unlock because I can not get into phone.
- I have tried wiping CACHE AND FACTORY RESET from recovery but it does not LOAD anything after boot and shows error I posted in image above.

lol!
first off, you posted in the wrong nexus 6 forums, as you arent developing anything(besides a headache). secondly, adb and fastboot are different. fastboot is not an adb command! fastboot is a different tool, like adb but different, and you can only use fastboot while you are in the bootloader. secondly, go back for a little and do a little more reading please, then try again.
edit.. good, this thread got moved to the right place.

"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?

Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/

dahawthorne said:
"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?
Click to expand...
Click to collapse
no, its not dead though I was dead for couple days.

Administr4tor said:
Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/
Click to expand...
Click to collapse
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.

thatkindaguy said:
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.
Click to expand...
Click to collapse
Thank you for reply,
- I have adb and fastboot drivers installed from xda when I connect the phone it shows connected, Please check the screenshot.
- I just want to flash stock rom, even if its possible to do it without unlocking bootloader, please let me know.
_ i have already tried NEXUS TOOLKIT and tried to unlock bootloader but it failed to unlock it.
Regards

You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?

geokhentix said:
You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?
Click to expand...
Click to collapse
oh, I didn't do anything, I wokeup and charged it after it went dead, and it all happened,
also sometimes I get this error too if I am not getting those "unfortunate error"

Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.

vicks1008 said:
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.
Click to expand...
Click to collapse
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example

Vivjen said:
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example
Click to expand...
Click to collapse
My Nexus 6 is stuck at LMY48M & I tried pushing the latest Marshmallow OTA build MMB29X.

You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?

Why is your Nexus reported in Device Manager as a Samsung device? As someone who owns a Galaxy S4 as well as a Nexus, you cannot use the Samsung driver in place of the Nexus USB driver.
Change your driver to the Google-provided version and try again.

Vivjen said:
You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?
Click to expand...
Click to collapse
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.

Nexus root toolkit
this toolkit will do all the work for you. from wugfresh development

vicks1008 said:
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.
Click to expand...
Click to collapse
No. Just download OTA from PC and push it to N6 via adb sideload

joseppa87 said:
this toolkit will do all the work for you. from wugfresh development
Click to expand...
Click to collapse
Absolutely. It washed my dishes, took the dog for a walk, and helped me with my homework.

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
sIR, How did you push STOCK OTA and where did you get it from, Can you please tell me steps you followed in details?
Thank you for reading.

[GUIDE] Unlock Moto G5S Plus Bootloader [NOOB-FRIENDLY]

{
"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"
}
Warnings
Doing this will void your warranty.
Your phone will be wiped.
I am not responsible for anything that happens to your phone.
Prerequisites
Your phone
USB Cable
Minimal ADB and Fastboot (Download and install it from here)
A working human brain.
Steps To Unlock Bootloader
First, enable Developer Options. To do this, go to Settings>About Phone> Tap on Built Number multiple times until the toast You are a developer now appears.
Now go to Developer Options in Settings and find and enable OEM Unlock by sliding the button. A warning will appear, just confirm that.
Turn off Your smartphone.
Press Volume Down Button and Power button simultaneously and hold it for few seconds. This will boot your device into fastboot mode.
Double-Click the Minimal ADB and Fastboot icon on your desktop.
Connect your device via USB cable. ( Stock Motorola Cable recommended )
Now go to this website. Read the information given if you wish and click on next button to proceed.
The Page will ask you to sign in, complete the process by signing with your Motorola account or Google Account.
Now go the Command Prompt and type fastboot oem get_unlock_data.
Now a new serial code will appear in your command prompt screen you have to copy the entire code.
Now open this link and copy the code in the tool. Then select the entire code and paste that code in point 6 on Moto require Unlock Tool Website.
Now Click on the I Agree Button a Get Unlock Code will appear on the screen.
Click on the button.
An Unlock Code will appear or will be emailed to you.
Now again go to the Command Prompt screen and type fastboot oem unlock ************. (“************” will replace your unique key)
A warning screen will appear in command just retype the same command and hit enter.
Type fastboot reboot and your phone will reboot.
Done! Your bootloader has been unlocked.

I am getting bad id on bootup. No issues afaik but can someone point out the cause of this?

You forgot 'WINDOWS PC"... or can it be done from Ubuntu?

@edilebe: Certainly you can:
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
And then in a terminal:
To access adb :
Code:
adb devices
To access fastboot :
Code:
fastboot devices
Rest of the commands go on as usual.
Broadcasted from Zeta Reticuli

Can i relock the Bootloader without warning boot screen?

Get also Bad Key on Bootscreen but its working

Will doing this disable OTA updates?

I apparently did some step wrong, Id: Bad Key shows on Bootscreen and I can't seem to install TWRP recovery, I get the following error
Code:
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
Also when I run ""fastboot getvar unlocked" I get:
Code:
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
Maybe I put the wrong key, and now I can't try to unlock it again, what should I do?
I'll greatly appreciate some help

Tewisp said:
I apparently did some step wrong, Id: Bad Key shows on Bootscreen and I can't seem to install TWRP recovery, I get the following error
Code:
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
Also when I run ""fastboot getvar unlocked" I get:
Code:
(bootloader) unlocked: not found
getvar:unlocked FAILED (remote failure)
Maybe I put the wrong key, and now I can't try to unlock it again, what should I do?
I'll greatly appreciate some help
Click to expand...
Click to collapse
It says Your bootloader is locked
u may try from beginning to unlock the bootloader

I dud try to unlock it again, but it won't let me do it, i get a invalid state error
...
(bootloader) invalid boot state
I tried to lock it again just in case, installed factory rom but got the same message.
Is there a way to reset the boot state so i could try again to unlock it?
Thanks for answering by the way, I really appreciate it!

Schrotty35 said:
Get also Bad Key on Bootscreen but its working
Click to expand...
Click to collapse
same here as well. but seems to work fine.
need to proceed to root.

bradleyw801 said:
Will doing this disable OTA updates?
Click to expand...
Click to collapse
I would also like to know the answer. Today I will receive a brand new G5S Plus.
If I unlock the bootloader, install TWRP, decrypt data, and install Magisk, will I still receive OTA updates (including in a few months Oreo)?

gewe said:
I would also like to know the answer. Today I will receive a brand new G5S Plus.
If I unlock the bootloader, install TWRP, decrypt data, and install Magisk, will I still receive OTA updates (including in a few months Oreo)?
Click to expand...
Click to collapse
Installing TWRP will certainly prevent you from getting OTAs. Not sure whether simply unlocking the bootloader will disqualify you as well.

revengineer said:
Installing TWRP will certainly prevent you from getting OTAs. Not sure whether simply unlocking the bootloader will disqualify you as well.
Click to expand...
Click to collapse
I like to have my phone rooted (for things like backup, adblocker).
Since the data partition has to be decrypted for TWRP and Magisk, would the following order make OTA possible?
Create backup
Uninstall Magisk
Flash stock bootloader
Reboot
Let OTA install do its work
Reinstall TWRP
Decrypt data partition
Reinstall Magisk
Restore data partition

gewe said:
I like to have my phone rooted (for things like backup, adblocker).
Since the data partition has to be decrypted for TWRP and Magisk, would the following order make OTA possible?
Create backup
Uninstall Magisk
Flash stock bootloader
Reboot
Let OTA install do its work
Reinstall TWRP
Decrypt data partition
Reinstall Magisk
Restore data partition
Click to expand...
Click to collapse
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery. The firmware floating around here does not included signed images.

revengineer said:
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery. The firmware floating around here does not included signed images.
Click to expand...
Click to collapse
At the moment I am trying to create a backup of everything in the state directly after unlocking the bootloader.
I booted TWRP without flashing it, so I can create a backup. However, the backup freezes. I could create a backup of all partitions, except system. When I include system, the backup freezes. I tried three times. It froze at 13%, 21% and 1% (posted this here).

revengineer said:
You need original recovery for sure. Flashing bootloader alone is not sufficient. I believe you also need to lock the bootloader. What I do not know is whether you need signed images of bootloader and/or recovery.
Click to expand...
Click to collapse
You don't need signed images, and you don't need a locked bootloader to install OTA.
Signed images are only necessary for locking bootloader. Nothing else should be concerned.
Locked bootloader is only necessary for passing SafetyNet. Alternative is using Magisk, which pretends to the verifying routine the bootloader would have been locked. Then you should pass SafetyNet again, until the checks SafetyNet do are modified. Then it fails, until Magisk is updated to circumvent these checks also ... it is a cat-and-mouse game, and the author of Magisk (topjohnwu) is a fast one. But there probably always will be times where neither PokemonGo nor Android Pay are running fine. If you want root (my personal belief is, if you own a device, you should have the right to access and modify all data on it), you need to deal with it.
OTA update checks some things (system, recovery, boot, oem, maybe some more) are not modified. Mounting system r/w may suffice to mark the partition as changed and prevent installation of OTA. Failed OTA usually reverts to previous state and gives an error message, then you may read the logs to see what went wrong. Your device stays in a usable state in most cases, at least that's my experience.
Disclaimer: I don't own a G5S Plus, but I'm usually recommending it if I'm asked which mobile is currently a good one to buy. What I write here is to the best of my knowledge applying to many Android, at least most Moto devices. Some behaviours may change when Oreo arrives. Always do a complete backup before any action, and don't forget to treat /data/media in a special way if using Nandroid in twrp.

I can't even unlock the bootloader...:crying:, let alone flashing twrp and rooting my device..... I have no idea where i am going wrong, i followed every step you mentioned. i tried running this command:
c:\adb>fastboot oem get_unlock_data
but it did not work, it showed me an error
---
FAILED < command write failed <No error>>
finished. total time: 0.003s
c:\adb>
Can anyone tell why is this happening? I must have done something wrong otherwise it would not happen.

Unable to unlock Bootloader
Phone is unable to boot and ends up on fastboot screen.
Phone has a locked oem. It says software as modified in fastboot screen. Unable to load bootloader.
While trying to get unlock oem data throws data block read error. What can be done? Is there an alternate way to to get device ID so as to get oem unlock code from Motorola website?
This happened all of a sudden. It was running stock, nothing ever altered.