Hi Guys, Just to let everyone know the command for unlocking the bootloader is now "fastboot flashing unlock" oem unlock will return an error and no longer functions.
Isn't the command just "fastboot oem unlock"?
overlord727 said:
Isn't the command just "fastboot oem unlock"?
Click to expand...
Click to collapse
Not anymore it would seem.... fastboot oem unlock returns an error
according to the android developer FAQ, "flashing" is the correct command, but I can't figure out why.
https://source.android.com/devices/tech/security/verifiedboot/verified-boot.html
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
it made me start to wonder if OEM would somehow trigger the fuse, whereas FLASHING is specifically designed not to. anyone know why there's a "unlock bootloader" switch in the developer options within Android?
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Kitch16 said:
God, I thought I was going crazy. Unknown command error returning had me confused as ****. Good to know I'm not the only one.
Click to expand...
Click to collapse
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Kitch16 said:
Is it confirmed that 'fastboot flashing unlock' is the new command now then?
Click to expand...
Click to collapse
Yes, Confirmed on my 6P.
Cheers bud, saved me spending more than the 30 mins I have already done pulling my hair out.
---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------
Tung_meister said:
I know, I spent ages trying to get it to work on my Laptop and Desktop before I discovered about the new command. It was really getting annoying as I was desperate to setup the device but didn't want to do it before the bootloader unlocking wipe.
Yes, Confirmed on my 6P.
Click to expand...
Click to collapse
Did it trip your eFuse?
Kitch16 said:
Did it trip your eFuse?
Click to expand...
Click to collapse
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Born<ICs said:
What happens if you flash TWRP AFTER unlocking bootloader?
I came across a cautionary note that you may bootloop.
fron 5X forum
"So I fastboot unlocked my bootloader and flashed TWRP straight after. Now stuck in bootloop between "your device software cant be checked for corruption" orange screen and TWRP first install Failing."
.
Before I try anything trying to sort out how Marshmallow alters unlock, root, flash game.
.
Click to expand...
Click to collapse
TWRP isn't available for the Nexus 6P yet!
But when it is available, we'll have to cross that bridge when we come to it.
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Born<ICs said:
Also if I'm not mistaken buttons to get to Fastboot are now Vol Up+Vol Dn+Pwr vs old Pwr+Vol Dn
Click to expand...
Click to collapse
I got in to Fastboot by holding volume down and powering on the phone as normal.
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
So what causes the Qfuse to blow?
Being a Nexus device shouldn't command be fastboot oem unlock. Curious
On the official Google Developers Factory Images page it’s still “fastboot oem unlock”.
http://forum.xda-developers.com/nexus-6p/general/fastboot-unlocking-command-t3233722/page2
To add to this also make sure your Android SDK is fully up to date
JustinTrouble said:
I've just unlocked my bootloader, and the Qfuse is still enabled, so it's all good. :good:
Click to expand...
Click to collapse
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
indianajonze said:
how are you checking qfuse status? i thought the process of unlocking the bootloader trips it?
Click to expand...
Click to collapse
Does qfuse trip if you relock bootloader?
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
GCbard said:
Does qfuse trip if you relocation bootloader?
Click to expand...
Click to collapse
Does qfuse trip if one flashes a rom?
Related
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock" and also flash back to STOCK images (if changed) or else it wont boot
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
duarian said:
Any idea if this sends anything to the google servers? I know when unlocking the T700 it sends the serial to ASUS to void the warranty. Not sure if this was the case with any nexus device or not (also I realize this isnt out yet). Just figured i'd ask if you had any past experience with the N7 or prior nexus device
Click to expand...
Click to collapse
No, it doesn't send anything to Google, that's why they give you the option to relock the bootloader .
can this be done on linux using fastboot included in sdk?
jrod091 said:
can this be done on linux using fastboot included in sdk?
Click to expand...
Click to collapse
of course man fastboot is fastboot
matt95 said:
of course man fastboot is fastboot
Click to expand...
Click to collapse
You will probably need to run fastboot as root, though.
gnustomp said:
You will probably need to run fastboot as root, though.
Click to expand...
Click to collapse
It isn't needed, if the sdk folder is in the PATH it will work normally
udimars30 said:
First Of all Thanks to AndroidCentral for this!!!
I am not responsible for any bricked device
Try at your own risk!!
Now Lets go and unlock the nexus 10!! :laugh:
Requirements"
Fastboot
Android SDK
Downloads:
fastboot (windows): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-windows.zip
fastboot (mac): http://cdn.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
Now lets unlock!!!! :highfive:
1.Power off your Nexus 10, and reboot it into fastboot mode by holding the volume up button, volume down button and power button.
2.Plug your tablet into a full speed primary USB port on your computer. If you're using Windows, you'll see the pop-up about drivers being installed and initialized.
3.Open the terminal or command prompt on your computer, and navigate to the folder you have placed the fastboot program in. if you have already done this before you might not get any prob in doing all this stuff!!
4.At the command line, type in (without any quotes) "fastboot devices". You should get a device ID returned, which lets you know that fastboot can see your Nexus 10
5.it is really important to get the ID of the device or else you cannot go further
6.After you have got the ID just type(without qoutes) "fastboot oem unlock" in your command window.
7.Look to your tablet, where you'll have to verify the process. Remember that there's no way to undo the data loss that will happen the instant you say "Yes".
8.When the tablet reboots, you're done. You're free to install custom software, modified boot images, custom recovery.
Enjoy your unlocked nexus 10 !!!
IF you want to RE-lock your bootloader
1.All the steps are same
2.on the 6th step just change the code from "fastboot oem unlock" to "fastboot oem lock"
3.This will relock your bootloader so that only authentic, signed images from Google can be flashed to the phone.
Enjoy!!!
Video coming soon, after i get my hands on it!
Click to expand...
Click to collapse
Thanks！I will try it!
Re-lock
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
matt95 said:
It isn't needed, if the sdk folder is in the PATH it will work normally
Click to expand...
Click to collapse
I just put it in /usr/bin with adb, I've only had my SGSII as far as android devices, Si want sure, thanks though!
Sent from my SGH-I777 using xda app-developers app
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Lumsdoni said:
Thank you, its been so long since I rooted my last device I've forgotten most of it - do I need a new SDK and if so where do I get it?
I'm running Mac OS X 10.7.5
Apoloiges for asking but it has completely left me.
Click to expand...
Click to collapse
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Sdk has been updated
Sent from my SGH-I777 using xda app-developers app
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
yeah thanks for reminding dude
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
---------- Post added at 02:31 PM ---------- Previous post was at 02:15 PM ----------
matt95 said:
no you don't need a newer SDK, if you have the platform-tools and tools folder you are good to go...
Click to expand...
Click to collapse
Lumsdoni said:
Apologies but is there an online guide? Iv'e got no idea what I did before when I was on my Nexus One, I reckon I might as well delete the SDK and reinstall both SDK and Eclipse sO I can root with a clean system.
Click to expand...
Click to collapse
It would appear it is a lot simpler now as you can download a sdk / eclipse bundle from here
alias_neo said:
You should also mention in the OP that in order to re-lock you should flash back to STOCK images (if you have changed anything) otherwise the device will no longer boot.
Click to expand...
Click to collapse
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
I unlocked the bootloader but now the tab will not start? I starts to the X of JB and then nothing happens... Help
---------- Post added at 10:56 PM ---------- Previous post was at 10:18 PM ----------
I have the Solution :good:
If you have the same problem - Go into Stock-Recovery and make a "Factory Reset" then reboot the system.
EniGmA1987 said:
Why do you say that? I have my Galaxy Nexus locked again with a custom ROM and kernel and it works fine. Ive never seen mention of this non-booting thing if the bootloader is locked when running something custom
Click to expand...
Click to collapse
It's may be wrong, I'm basing it on my XOOM days where it wouldn't boot it you relocked with anything other than stock. If that's different now, feel free to ignore me
Sent from my GT-I9300 using Tapatalk 2
I know that when an update comes out I have to relock the bootloader, but if I unlock it after the update does it wipe the device again
Sent from my Galaxy Nexus
I have 3 questions
1. Unlocking nexus 10 means rooting it ?
2. Is unlocking or rooting tablets legal in US?
3. I ordered nexus 10 but read n
ot so good things about the limited applications are supported for 10 inch screen .. Is there any workaround to have apps look as good as iPad I mean using the entire screen ...any custom ROMs available yet
Sent from my SGH-I897
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
Hello all I have a Unlocked Huawei Y6 Elite (LYO-L02) and it seems to me im unable to flash twrp at this time cause everytime I flash into fastboot then type the usual command to flash the recover it immediately fails with this message "FAILED (remote: failed to get download permission because status is locked!)" does anyone know what would be causing it and how to fix it? I really wanna get on with rooting my phone ive already tried several one click root methods none have seemed to work so im wanting to get root via custom rom or superuser
Veritux said:
Hello all I have a Unlocked Huawei Y6 Elite (LYO-L02) and it seems to me im unable to flash twrp at this time cause everytime I flash into fastboot then type the usual command to flash the recover it immediately fails with this message "FAILED (remote: failed to get download permission because status is locked!)" does anyone know what would be causing it and how to fix it? I really wanna get on with rooting my phone ive already tried several one click root methods none have seemed to work so im wanting to get root via custom rom or superuser
Click to expand...
Click to collapse
Send a photo
Amaan007 said:
Send a photo
Click to expand...
Click to collapse
attached the screen capture of what happened
Veritux said:
attached the screen capture of what happened
Click to expand...
Click to collapse
fastboot oem device-info
Show output of this
Amaan007 said:
Send a photo
Click to expand...
Click to collapse
Amaan007 said:
fastboot oem device-info
Show output of this
Click to expand...
Click to collapse
Failed...
Veritux said:
Failed...
Click to expand...
Click to collapse
Try minimal and adb fastboot
Amaan007 said:
Try minimal and adb fastboot
Click to expand...
Click to collapse
both failed
Veritux said:
both failed
Click to expand...
Click to collapse
is usb debugging on or frp unlock
Amaan007 said:
is usb debugging on or frp unlock
Click to expand...
Click to collapse
USB debugging was on an frp unlock is shown in the bootloader
Veritux said:
USB debugging was on an frp unlock is shown in the bootloader
Click to expand...
Click to collapse
Re unlock it
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
Veritux said:
USB debugging was on an frp unlock is shown in the bootloader
Click to expand...
Click to collapse
Btw what twrp ur flashing
Amaan007 said:
Re unlock it
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
Btw what twrp ur flashing
Click to expand...
Click to collapse
problem is I dont have the unlock code and I dunno how to recover it and TWRP 3.0.2
Veritux said:
problem is I dont have the unlock code and I dunno how to recover it and TWRP 3.0.2
Click to expand...
Click to collapse
So u are not unlocked
---------- Post added at 07:52 AM ---------- Previous post was at 07:52 AM ----------
Amaan007 said:
So u are not unlocked
Click to expand...
Click to collapse
Ur blog loader needs to be unlocked
Amaan007 said:
So u are not unlocked
---------- Post added at 07:52 AM ---------- Previous post was at 07:52 AM ----------
Ur blog loader needs to be unlocked
Click to expand...
Click to collapse
well the phone came unlocked and im able to use it on multiple networks as in the seller sold it to me unlocked but didnt give me the unlock code but the phone should already be unlocked and I tested it and it seems to work on all networks
Veritux said:
well the phone came unlocked and im able to use it on multiple networks as in the seller sold it to me unlocked but didnt give me the unlock code but the phone should already be unlocked and I tested it and it seems to work on all networks
Click to expand...
Click to collapse
Boot loader is not unlocked
Amaan007 said:
Boot loader is not unlocked
Click to expand...
Click to collapse
its does say unlocked on the bootloader menu when I have allow oem from the developer menu on when its off its only then does say my bootloader is locked
Veritux said:
its does say unlocked on the bootloader menu when I have allow oem from the developer menu on when its off its only then does say my bootloader is locked
Click to expand...
Click to collapse
That's on the menu plz understand
Amaan007 said:
That's on the menu plz understand
Click to expand...
Click to collapse
its when I load into fastboot that it says its unlocked I know my phone is unlocked im unsure on what that issue is
Veritux said:
its when I load into fastboot that it says its unlocked I know my phone is unlocked im unsure on what that issue is
Click to expand...
Click to collapse
That is network unlock and ur bootloader is locked try to understand.
Veritux said:
its when I load into fastboot that it says its unlocked I know my phone is unlocked im unsure on what that issue is
Click to expand...
Click to collapse
There is a BUG. Your phone is locked but it says it's unlocked. A lot of people already reported this. You have to re-unlock it.
Amaan007 said:
That is network unlock and ur bootloader is locked try to understand.
Click to expand...
Click to collapse
The only language permitted here is english, "ur" is not english...
Veritux said:
Hello all I have a Unlocked Huawei Y6 Elite (LYO-L02) and it seems to me im unable to flash twrp at this time cause everytime I flash into fastboot then type the usual command to flash the recover it immediately fails with this message "FAILED (remote: failed to get download permission because status is locked!)" does anyone know what would be causing it and how to fix it? I really wanna get on with rooting my phone ive already tried several one click root methods none have seemed to work so im wanting to get root via custom rom or superuser
Click to expand...
Click to collapse
This error can occur when the bootloader is still locked... when you boot to the bootloader (power off the phone then hold volume down while powering on) it will display FRP unlock in red if you successfully unlock the bootloader otherwise I believe it displays something like FRP locked in yellow which will be the cause of this error...
to get to the point i used the ota updater for a lineage and it wiped twrp and replaced it with lineage recovery. then i decided to perform a factory reset in sed recovery. that led to boot loop that landed me back in recovery. so i started up lgup and went back to stock oreo and bootloader remained unlocked. now that i'm back on stock oem unlock is greyed out. when in fastboot it says to enable oem unlock. so what do you guys think i should do? unable to flash or fastboot boot twrp at all.
heres the pics
https://imgur.com/a/WiDIqfm
For anyone that happens to run into this issue. Run fastboot OEM lock and it'll fail on the command line but reboot your device and it'll relock the bootloader. Then follow the Frankenstein guide to unlock the bootloader again.
Was able to immediately toggle OEM unlock after this
What error do you get when you try to flash?
Sent from my LG-US998 using Tapatalk
kenbo111 said:
What error do you get when you try to flash?
Click to expand...
Click to collapse
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
R800x_user said:
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
Click to expand...
Click to collapse
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
ChazzMatt said:
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
Click to expand...
Click to collapse
I want aware of the wait time. Thanks for the info
R800x_user said:
I want aware of the wait time. Thanks for the info
Click to expand...
Click to collapse
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
ChazzMatt said:
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
Click to expand...
Click to collapse
How long would one have to wait? Still grayed out.
Just an update to this.
R800x_user said:
How long would one have to wait? Still grayed out.
Just an update to this.
Click to expand...
Click to collapse
I never measured, but less than a week I think.
ChazzMatt said:
I never measured, but less than a week I think.
Click to expand...
Click to collapse
[email protected] okay, I'll need to try to OEM lock. I'm unsure if it'll even work. At least I have a functional v30. I was thinking using LGup would've relocked the bootloader if I downgraded.