Database Users

[How To] "lock" bootloader and revert to stock for warranty exchange

I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
EDIT_____-----____-
before doing anything, i did open up the .bat file named MAIN in the unzipped, "automatic unlock" folder. i tested out all the relevant options such as "restore to stock" and "repair boot error". I never actually used the software, but maybe just installing and initializing it was what it took to break through

steevquinn said:
I did this to my own Motorola Atrix 4g running rom: HB 2.3.4 oc 1.3ghz ext4 with the newest cwm installed
***i take no responsibility if this messes up your phone. I just did it to mine tonight before the replacement arives and wanted to help anyone else worried about being charged $399 for unlocking our bootloader
1) you need to download
//www35.megaupload.com/files/70b7d352e9514672c426f9dda58d3f6e/AUTOMATIC_UNLOCK_V4.2.zip
just incase something goes wrong you can unbrick it
2) RSD lite 5.3.1
//crackflashers.com/b16/Atrix/RSDLite5.3.1.msi
3) Newest moto update 2.3.4
//gitbrew.org/~dasmoover/android/atrix/1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
boot into rsd mode and flash the official update using rsd lite, it will stop at 100% but never finish. once you see the at&t logo you can unplug if it takes forever and just wait for it to load.
after you will no longer have cwm or the "unlocked" text at boot, but all your data will still be on the phone so dont forget to wipe after.
***link #1 is only if you have problems booting after using rsd lite (i didnt need it)
Click to expand...
Click to collapse
And this didn't brick ur phone.
Sent from my MB860 using XDA App

anupash said:
And this didn't brick ur phone.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
amazingly, no

AFAIK the bootloader is still unlocked, it just doesn't show the "UNLOCKED" in the bootscreen anymore and reflashes/ overwrites CWM with the original ANDROID RECOVERY.

There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.

But if I have already hard bricked my phone? what to do? it shows nothing ... the battery is charged

CaelanT said:
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
Click to expand...
Click to collapse
^ This!
10char

I want to do a best buy warranty exchange (screen got lil bit scratch)....and would this method hide the "UNLOCKED" from the booting screen....is there any other method that you can hide the unlocked from the boot screen...reason being if they decide to just replace the screen and give it back the same phone...i dont wanna go through all the work....thank you...

CaelanT said:
There are already several threads about this. You cannot relock the bootloader, only hide "unlocked" the boot logo screen.
Click to expand...
Click to collapse
so...can u install custom roms: no. does it say unlocked at boot: no. so therefor it is unlocked for our purposes. The only way to unlock again is to rerun pudding. dont worry about what you've read elsewhere, im telling you this works.what other reason do u need to lock it for other than return. its people like you that cause misinformation. I did it, it works, now getting a new phone for free
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
rockbio said:
I want to do a best buy warranty exchange (screen got lil bit scratch)....and would this method hide the "UNLOCKED" from the booting screen....is there any other method that you can hide the unlocked from the boot screen...reason being if they decide to just replace the screen and give it back the same phone...i dont wanna go through all the work....thank you...
Click to expand...
Click to collapse
dude, it takes 7 minutes...a lot of work? lol just get it done and be safe. you can always go back to before, or fix a bricked device if needed
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
TinyRK said:
AFAIK the bootloader is still unlocked, it just doesn't show the "UNLOCKED" in the bootscreen anymore and reflashes/ overwrites CWM with the original ANDROID RECOVERY.
Click to expand...
Click to collapse
its not unlocked. you have none of the features of an unlocked phone after this process. there is no such thing as a software fuse - theres always a way to go back. remember when they said it would be impossible to have a full bootloader unlock??? a couple weeks later, what do you know, "pudding" shows up. dont post on stuff you have never tried. like they say i'll believe it when i see it.

lol.
hey OP do this.
$ sudo ./moto-fastboot oem lock
... INFOOEM lock is not implemented
or fastboot oem lock
lol.
oh ya btw. http://forum.xda-developers.com/showthread.php?t=1211198
http://forum.xda-developers.com/showthread.php?t=1260127
http://forum.xda-developers.com/showthread.php?t=1254029
http://forum.xda-developers.com/showthread.php?t=1168255

steevquinn said:
so...can u install custom roms: no. does it say unlocked at boot: no. so therefor it is unlocked for our purposes. The only way to unlock again is to rerun pudding. dont worry about what you've read elsewhere, im telling you this works.what other reason do u need to lock it for other than return. its people like you that cause misinformation. I did it, it works, now getting a new phone for free
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
dude, it takes 7 minutes...a lot of work? lol just get it done and be safe. you can always go back to before, or fix a bricked device if needed
---------- Post added at 11:35 AM ---------- Previous post was at 11:29 AM ----------
its not unlocked. you have none of the features of an unlocked phone after this process. there is no such thing as a software fuse - theres always a way to go back. remember when they said it would be impossible to have a full bootloader unlock??? a couple weeks later, what do you know, "pudding" shows up. dont post on stuff you have never tried. like they say i'll believe it when i see it.
Click to expand...
Click to collapse
Unlocking the bootloader burns a software fuse in the bootloader. Same with the 4.9.51 update. That is what caused a lot of hard bricks. You cannot reflash the bootloader unless through nvflash with the SBK and a engineering cable, That would be the only way to patch the software fuses. This might remove the unlocked text at bootup and inhibit you from flashing roms, but the bootloader fuse is still blown, leaving proof of an unlocked bootloader.
Sent from my PG86100 using xda premium

And there's no way they can tell the phone has been unlocked when you return it? I'm thinking of exchanging my phone today. Currently unlocked and rooted.

archer75 said:
And there's no way they can tell the phone has been unlocked when you return it? I'm thinking of exchanging my phone today. Currently unlocked and rooted.
Click to expand...
Click to collapse
you can hide the "unlocked" but if they fastboot oem your phone lol then you're OOL.
I highly doubt they do though :T tbh..

darkamikaze said:
lol.
hey OP do this.
$ sudo ./moto-fastboot oem lock
... INFOOEM lock is not implemented
or fastboot oem lock
lol.
oh ya btw. http://forum.xda-developers.com/showthread.php?t=1211198
http://forum.xda-developers.com/showthread.php?t=1260127
http://forum.xda-developers.com/showthread.php?t=1254029
http://forum.xda-developers.com/showthread.php?t=1168255
Click to expand...
Click to collapse
why would i do that? i already sent my phone back, and there is absolutely no reason to relock a device for personal use. as soon as at&t recieves it, I imagine they turn it on, make sure it boots and no damage has been done. then they notify u that they recieved the phone and u are no longer the owner of it. Im sure as soon as the phone boots to the welcome screen without any weird things to indicate you have modified the phone, to at&t your phone is locked and unmodified. long before they test the phone for referbishing purposes, your account hold has been released and no one will ever know at one point their new, refurbished device was one a modded android with an unlocked bootloader, (Mod edit: Cease the abusive behavior)

armonwilson888 said:
Unlocking the bootloader burns a software fuse in the bootloader. Same with the 4.9.51 update. That is what caused a lot of hard bricks. You cannot reflash the bootloader unless through nvflash with the SBK and a engineering cable, That would be the only way to patch the software fuses. This might remove the unlocked text at bootup and inhibit you from flashing roms, but the bootloader fuse is still blown, leaving proof of an unlocked bootloader.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
No such thing as a software fuse, and if there were you could reverse it because it is software.
From IBM who developed eFuse technology:
" The patented technology, called "eFUSE," combines unique software algorithms and microscopic electrical fuses to produce chips that can regulate and adapt their own actions in response to changing conditions and system demands."
Nuff said!

steevquinn said:
why would i do that? i already sent my phone back, and there is absolutely no reason to relock a device for personal use. as soon as at&t recieves it, I imagine they turn it on, make sure it boots and no damage has been done. then they notify u that they recieved the phone and u are no longer the owner of it. afterwards, they flash all the memory and send it to be tested "thoroughly"(lol) for any internal damage before having the glass replaced and a new shell put on
Click to expand...
Click to collapse
that command will show you that your phone is still unlocked. that's why
anyway. believe us or not. but you cannot relock an unlocked device.

darkamikaze said:
that command will show you that your phone is still unlocked. that's why
anyway. believe us or not. but you cannot relock an unlocked device.
Click to expand...
Click to collapse
When you say 'device' are you only referring to Atrix?
Cus ya know.. you can relock the Xoom... just saying....
http://forum.xda-developers.com/showthread.php?t=967065
http://www.droid-life.com/2011/03/11/how-to-re-lock-the-motorola-xoom-bootloader-to-receive-updates/

CaelanT said:
No such thing as a software fuse, and if there were you could reverse it because it is software.
From IBM who developed eFuse technology:
" The patented technology, called "eFUSE," combines unique software algorithms and microscopic electrical fuses to produce chips that can regulate and adapt their own actions in response to changing conditions and system demands."
Nuff said!
Click to expand...
Click to collapse
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------
TinyRK said:
WOW!
Real mature.
We just said, that the BL isn't locked. No reason to act like a kiddo and be offensive.
Grow up!
So letting others believe, that you're right is not correct, since the BL is not "re-locked."
I once did exactly what OP mentioned in the 1st post.
The UNLOCK disappeared, but the BOOTLOADER was still unlocked.
Click to expand...
Click to collapse
I said for our purposes (returning a defective unit) that the bootloader is effectivly locked. when in the process of returns does the step of running moto fast boot come into play? if that were so then the at&t techs would need to know the equivalent fastboot software for every single android phone.....HA! I doubt $9/hr at&T techs have any clue about this stuff unless they are into it on their own time

steevquinn said:
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------
I said for our purposes (returning a defective unit) that the bootloader is effectivly locked. when in the process of returns does the step of running moto fast boot come into play? if that were so then the at&t techs would need to know the equivalent fastboot software for every single android phone.....HA! I doubt $9/hr at&T techs have any clue about this stuff unless they are into it on their own time
Click to expand...
Click to collapse
read
https://motorola-global-portal.cust...378/~/atrix---bootloader-mode-(efuse)-rooted*
Also, All Motorola would need to do is image the boot partition and hash that file and compare it to a hash of stock bootloader.. Two different hashes would be a dead give away that something was done to the bootloader.
Do they do that for every single return that comes in the door?? Most likely not. The probably reflash all their stuff back to it and leave it at that.
That being said.. you are arguing a failing point. The bootloader is still locked. Change the title of the thread to how to fool ATT if you have an unlocked bootloader and perhaps people will stop giving you **** about it.

steevquinn said:
so...your saying youve seen somewhere that says the atrix has IBMs "efuse" technology, or that it just exists to prove me wrong?
Click to expand...
Click to collapse
Motorola uses Efuse technology. Now I'm done with all these bootloader threads. Appears some of you will never listen, but offer no constructive arguments yourselves. I've done lots of homework myself. I'm not shooting from the hip. Believe what you wish!
Cya!
Assimilated via WinBorg 4G

Panic - plz help! applied the wrong ota file from adb by mistake, now bootloop

I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?

sumit29 said:
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
Click to expand...
Click to collapse
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)

gasparzim said:
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
Click to expand...
Click to collapse
No, as per the instructions in my guide you can only install a newer build. I wasn't aware that full OTA zips were even available for the Developer Previews.

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Have already tried doing this...this also gets interrupted mid-way, with the command terminal showing - "connection reset by peer". these are the same OTA files available on the google developers website.

and for some reason, it worked this time around!!!

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.

Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
Same problem have you been able to sort it out yet?

Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.

Heisenberg said:
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Click to expand...
Click to collapse
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
no.:crying::crying:

Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.

Heisenberg said:
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Click to expand...
Click to collapse
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.

Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
Mine is also still messed up I'm calling the store where I bought it to see if they can do anything highly doubt they will though

Ame123 said:
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Click to expand...
Click to collapse
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.

Heisenberg said:
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Click to expand...
Click to collapse
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled

AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
An accredited repair centre should have access to software tools that can do it.

AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
did not understood what you said. can you explain a little bit more?

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Ame123 said:
did not understood what you said. can you explain a little bit more?
Click to expand...
Click to collapse
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've tried sideloading multiple times and they succeeded however my phone is still not booting :/

Bootloop - Locked Bootloader - Is the phone considered bricked?

Hi,
I have a nexus 6P and one day after a lovel OTA my phone had died on me. Sad enough I decided that I had to put her to bed and go get a dr. pepper from the fridge. Months later, as my feelings withered, I wished to resurrect my nexus.
SO here is what I know. I cannot flahs the stock rom with the bootloader locked. Guess what guys, my bootloader is locked. No flashing, its all locked up, but I kjnow no company is dumb enough to not have a plan B for when you don't wear protection.
Question 1: I heard I have to use TWRP to flah a custom rom to then unlock the bootloader but this seems silly as stock firmware should be far more flashable. ANy explanation?
Question 2> What is the difference between the K and D firmwares?

williamschromebook said:
Hi,
I have a nexus 6P and one day after a lovel OTA my phone had died on me. Sad enough I decided that I had to put her to bed and go get a dr. pepper from the fridge. Months later, as my feelings withered, I wished to resurrect my nexus.
SO here is what I know. I cannot flahs the stock rom with the bootloader locked. Guess what guys, my bootloader is locked. No flashing, its all locked up, but I kjnow no company is dumb enough to not have a plan B for when you don't wear protection.
Question 1: I heard I have to use TWRP to flah a custom rom to then unlock the bootloader but this seems silly as stock firmware should be far more flashable. ANy explanation?
Question 2> What is the difference between the K and D firmwares?
Click to expand...
Click to collapse
To flash twrp you need an unlocked bootloader. If you enabled USB debugging in developer options before the issue then you should be able to do fastboot oem unlock. However if not try going into your stock recovery and adb sideload a stock OTA for the nexus 6p and it should write all the partitions and boot up fine. I'm not sure what K and d firmwares are.
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Also, when you plug your device into your pc what does it say in device manager? Does it say something like EDL?

Boot loader locked....
I don't think I can glad twrp

williamschromebook said:
Boot loader locked....
I don't think I can glad twrp
Click to expand...
Click to collapse
That doesn't answer my question.

I won't know until my friend brings a device over again later

Some people are just better off not unlocking their bootloader.

DEVILOPS 007 said:
To flash twrp you need an unlocked bootloader. If you enabled USB debugging in developer options before the issue then you should be able to do fastboot oem unlock. However if not try going into your stock recovery and adb sideload a stock OTA for the nexus 6p and it should write all the partitions and boot up fine. I'm not sure what K and d firmwares are.
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
Also, when you plug your device into your pc what does it say in device manager? Does it say something like EDL?
Click to expand...
Click to collapse
I believe the new unlock code is "fastboot flashing unlock" - oem was for older phones. Also, he'd need have checked Allow OEM Unlock or OEM Unlocking or whatever it says in development settings to unlock bootloader, USB debugging for your next step, which could hopefully work.
williamschromebook said:
Boot loader locked....
I don't think I can glad twrp
Click to expand...
Click to collapse
Correct, you need an unlocked bootloader to flash TWRP. I'd try 007s advice above if you had USB Debugging enabled. Try to sideload a newer OTA via stock recovery and maybe a factory reset for good measure. See if it can at least get you booted.
lucky_strike33 said:
Some people are just better off not unlocking their bootloader.
Click to expand...
Click to collapse
Rude. OP said his phone had a locked bootloader (so, stock) and it died during an OTA. He came here asking for help..

Verizon Pixel Bootloader unlocked?

Me and this guy was talking about unlocking the bootloader by modifiying the .bin in an ota file and to my surprise he apparently was able to unlock the Pixel 2. Maybe this will work for those in on a Verizon Pixel 1 so give this a shot!
From all I can tell your just unlocking the critical partition with the command "Fastboot flashing lock_critical" then it allows for you to unlock. Refer to this thread and good luck!
https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294

Couldn't be this easy, so many devs have looked into this.
Sent from my Pixel XL using Tapatalk

FUZER384 said:
Couldn't be this easy, so many devs have looked into this.
Click to expand...
Click to collapse
I too think this is too easy but if it works it works.

I don't see how you can modify an OTA and still pass the the cert signing check and update checker.

TonikJDK said:
I don't see how you can modify an OTA and still pass the the cert signing check and update checker.
Click to expand...
Click to collapse
That is what is interesting me but it seems another person has done the same and it worked.

I don't even have Verizon or the Verizon pixel, but I'm curious if this works too lmao.

Didn't for me on my pixel. Says cannot be unlocked

abranson said:
Didn't for me on my pixel. Says cannot be unlocked
Click to expand...
Click to collapse
I see is this on the Pixel XL or just the Pixel ?

5 inch. I wouldn't think it would matter

abranson said:
5 inch. I wouldn't think it would matter
Click to expand...
Click to collapse
It just seems that all the success stories of the Pixel 2 are of the smaller verison and not the Pixel 2 XL so I didn't know if one or the other would work better. Also what error did it give you?
Edit: the critical part is an XL command only so try
Fastboot lock
Or
Fastboot flashing lock

The flashing lock-critical said it wasnt a valid command, so tried the lock_critical. Already locked and did nothing else. Also if changed to unlock_critical, fails and says unlocking is not allowed ,

abranson said:
The flashing lock-critical said it wasnt a valid command, so tried the lock_critical. Already locked and did nothing else. Also if changed to unlock_critical, fails and says unlocking is not allowed ,
Click to expand...
Click to collapse
How about fastboot flashing lock or flashing unlock

Did those too. The oem unlocking not allowed came up. Can't toggle oem unlocking switch, so idk

abranson said:
Did those too. The oem unlocking not allowed came up. Can't toggle oem unlocking switch, so idk
Click to expand...
Click to collapse
I don't understand this comment maybe a typo?

Oem unlocking toggle under developer options is greyed out. When you input those commands, it says failed, and says unlocking is not allowed. I'm not at a PCat the moment, but I can do again tomorrow, and take a pic
---------- Post added at 02:22 AM ---------- Previous post was at 02:15 AM ----------
And I was under the impression the critical command was only for pixel 2 and 2xl, so Idk. I have latest adb and fastboot

abranson said:
Oem unlocking toggle under developer options is greyed out. When you input those commands, it says failed, and says unlocking is not allowed. I'm not at a PCat the moment, but I can do again tomorrow, and take a pic
---------- Post added at 02:22 AM ---------- Previous post was at 02:15 AM ----------
And I was under the impression the critical command was only for pixel 2 and 2xl, so Idk. I have latest adb and fastboot
Click to expand...
Click to collapse
I thought the critical command was just a Android Oreo thing not specific to the Pixel 2's

EstiR86 said:
I thought the critical command was just a Android Oreo thing not specific to the Pixel 2's
Click to expand...
Click to collapse
For Pixel 2: To flash the bootloader, Pixel 2's boot loader must be updated to at least Oreo MR1's version first. This may be done by applying an over-the-air (OTA) update, or sideloading a full OTA with the instructions on that page.
For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical

Looks like this exploit does not work for the original Pixel. Bummer waste or a thread, good luck to those still trying to unlock.

try this, take Sim out and scratch out gold plating square closest to cut in one corner. reinsert Sim, reboot phone and adb/fastboot first then try activate oem unlock.sean

petiolarissean said:
try this, take Sim out and scratch out gold plating square closest to cut in one corner. reinsert Sim, reboot phone and adb/fastboot first then try activate oem unlock.sean
Click to expand...
Click to collapse
I'm confused what this would do, would you like to elaborate more.

Boot.img patched with magisk

Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.

RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
---------- Post added at 11:19 PM ---------- Previous post was at 11:12 PM ----------
Ash180287 said:
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
Click to expand...
Click to collapse
Am sure your aware but if you don't know how to get to the developers menu, open settings, click system at the bottom, go to about phone, and then click your build number 7 times to unlock the developers options.

Ash180287 said:
Have you tried unlocking the bootloader threw the developers settings thee option to unlock the bootloader is the 3rd or 4th option down, personally not tried it tho?
---------- Post added at 11:19 PM ---------- Previous post was at 11:12 PM ----------
Am sure your aware but if you don't know how to get to the developers menu, open settings, click system at the bottom, go to about phone, and then click your build number 7 times to unlock the developers options.
Click to expand...
Click to collapse
I didnt try anything until there is a guide of how to do it tested previously to avoid a possible brick.

RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Thanks for this, i would try this if i could unlock the bootloader, but i neither know how to do it.

RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
unlocking the bootloader is simple, it works exactly with the black shark helo, you enable the unlock in the developer section and then I have it in fastboot mode and you send the command "fastboot oem unlock" the smartphone will restart and make a factory reset and you will have the bootloader unlocked

Sime90ita said:
unlocking the bootloader is simple, it works exactly with the black shark helo, you enable the unlock in the developer section and then I have it in fastboot mode and you send the command "fastboot oem unlock" the smartphone will restart and make a factory reset and you will have the bootloader unlocked
Click to expand...
Click to collapse
I tried today doing everything you say, but fastboot say command doesnt exist, maybe you have chinese version(I am using global version)

RlxDev said:
Hello!, i managed to get the boot.img and i patched the boot.img with magisk but i cant test it becuase my phone have bootloader locked and i dont know how to unlock it.
I cant post links until i have 10 posts thats why i put a point at the beginning of the link
.drive.google.com/drive/folders/1m1ajF_GNtthYYV6SbeG0tQWSbxJGdCyD
if someone can tell me how to unlock the bootloader i will try by myself.
If it works please tell me in this post.
Click to expand...
Click to collapse
Enable developer function and enable OEM unlock function

pichitpongx said:
Enable developer function and enable OEM unlock function
Click to expand...
Click to collapse
Did it worked for you?
I tried that and didn't work. I have global version

Anyone managed to unlock the boot loader on this phone? I would like to get one but need root.

adkilla said:
Anyone managed to unlock the boot loader on this phone? I would like to get one but need root.
Click to expand...
Click to collapse
Ditto. Waiting on confirmation of root.

r3flux said:
Ditto. Waiting on confirmation of root.
Click to expand...
Click to collapse
I'm also waiting for root confirmation, i have BS 2 Global and unlocking boot loader tutorial was posted by a skilled member, here is the link
https://forum.xda-developers.com/bl...ck-bootloader-problem-easy-t3895992?nocache=1
---------- Post added at 11:18 PM ---------- Previous post was at 11:04 PM ----------
Also here is a full guide to unlock Black Shark 2 and seems to be effective
Steps To Unlock Bootloader On Xiaomi Black Shark 2
1.) First Of We Need To Enable Developer Options
For That Go To Settings >> About Phone >> Now Tap On MIUI Version 6-7 Times
2.) Now Go Back >> Go To Advanced Settings >> Developer Options >> Enable OEM Unlocking & Tap On Mi Unlock Status
These Things You Have To Do It On Your PC/ Laptop
3.) Go To This Link >> Then You Will See MIUI Page Tap On Unlock Now >> Now Fill The Form To Get The Permission From Xiaomi
4.) Once You Applied you will get an OTP sent to your phone, Enter that OTP on your PC >> Then Hit Next. So, this way your application gets submitted
Now You Have To Wait Until You Get A Message On Your Phone Saying “You Are Eligible To Unlock The Bootloader”
Now Follow The Unlocking Procedure
6.) Once You Got The Message >> Next You Need To Download Mi Unlock Tool & Extract It
7.) After That Just Power Off The Device,>> Now Press & Hold Volume Down + Power Button At The Same Time To Boot Into Fastboot Mode
8.) Once Your Are In Fastboot Mode >> Connect Your Phone To PC/Laptop
9.) Now Open (Mi Unlock Tool) From Your PC/Laptop
10.) Next Click On Agree & Next Enter Your Mi-Account Username, Password And Sign In
Use Same Mi Account Details Which You Already Login Into Your Phone To Unlock Bootloader
11.) Hit Next >> After That Tap On Unlock
12.) Once The Process Is Done Tap On Reboot
13.) That’s It ? You Have Successfully Unlock Bootloader Of Xiaomi Black Shark 2
For tutorial link, you can PM me, i can't post it publicly to avoid any moderator ban

Update : **
No any solution above has worked with me, seems there is no active solution for unlocking boot loader of BS2. even developer around all sites doesn't offer effective solution.
The only 2 messages that you will get when you use adb are :
adb>fastboot flashing unlock
Error : Unlock is not allowed on device has sales on market!
adb>fastboot oem unlock
Error, Unknown command
Even MI tool couldn't unlock the bootloader, If Kanded can give a solution as he is a skilled member so it will be great help

Any update? Still waiting for the XBS2 unlocking bootloader and rooting it.

I have found this about patching MM:
https://www.htcmania.com/showthread.php?t=1466079
I Hope enjoy, I have the same problem, BS2 global to root,

Anyone who tried unlocking bootloader and rooting bs2 using the bs helo? CN variant

has anybody got solution? I think this device has a potential to fullfill

So sad. Until now there's no TWRP and way to unlock bootloader of this device.

iampatricktan said:
So sad. Until now there's no TWRP and way to unlock bootloader of this device.
Click to expand...
Click to collapse
Agree. I'm planning to switch to Red Magic 3 because there really is no sign of development on this device.

batuken said:
Agree. I'm planning to switch to Red Magic 3 because there really is no sign of development on this device.
Click to expand...
Click to collapse
Yeah. I don't how can we encourage dev to look into this device, their are many users of this phone that wants to have twrp and root. Also this device is very powerful.

iampatricktan said:
Yeah. I don't how can we encourage dev to look into this device, their are many users of this phone that wants to have twrp and root. Also this device is very powerful.
Click to expand...
Click to collapse
Black Shark is independent of Xiaomi when it comes to the software development. Their team just have to release the kernel source then that's when the real thing starts. Sadly though, the Black Shark team is very lousy and their support is very poor so let's just expect that this device will get stuck to Android Pie, like what happened to Black Shark 1 which development is "dead".