Related
Hi everyone ! Tryied so hard to root, but every time i use the command "fastboot oem unlock " the device says "unknown command". Thanks ^^
-LF75JVUO99999999 fastboot
C:\Users\Eldertree\Downloads\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.004s
zenfone go zb452kg
hello my phone is: zenfone go zb452kg
I'm having the same problem I can not unlock the bootloader. I enabled the developer options and tried to find the option "activate unlock oem" but it is not there ... well I tried until I entered the search bar of the developer options and I researched .... the strange thing is that it appears when I search ... but it is blocked or something like that .... and if I try to reboot the phone in bootloader mode .... "power and volume button down or up" if it is with the down button it goes into mode Recovery and if it is with the one above it does not start .... it only stays at the asus boot (as if it were bricked) well this is my problem .... if someone can help me ..... I will be very grateful. ...thank you
Roash said:
Hi everyone ! Tryied so hard to root, but every time i use the command "fastboot oem unlock " the device says "unknown command". Thanks ^^ -LF75JVUO99999999 fastboot
C:\Users\Eldertree\Downloads\adb>fastboot oem unlock
... FAILED (remote: unknown command)
finished. total time: 0.004s
Click to expand...
Click to collapse
Doctor_Titi said:
hello.
What's your model phone? (like ZB552KL for example, because Asus did other models of "Zenfone Go")
Click to expand...
Click to collapse
Cyber_bot51 said:
hello my phone is: zenfone go zb452kg
I'm having the same problem I can not unlock the bootloader. I enabled the developer options and tried to find the option "activate unlock oem" but it is not there ... well I tried until I entered the search bar of the developer options and I researched .... the strange thing is that it appears when I search ... but it is blocked or something like that .... and if I try to reboot the phone in bootloader mode .... "power and volume button down or up" if it is with the down button it goes into mode Recovery and if it is with the one above it does not start .... it only stays at the asus boot (as if it were bricked) well this is my problem .... if someone can help me ..... I will be very grateful. ...thank you
Click to expand...
Click to collapse
All i did was Google the key words "Unlock Bootloader Zenfone GO" (without quotes) which is based on the Metadata system that Google and even the XDA Forum uses.
These are the key results found on the first page of the Google search and remember that the titles may look like it's for something different but, always check them out for responses and comments that just might be what you're looking for.
[GUIDE][UNOFFICIAL METHOD] Unlock Bootloader Without Asus Unlock App [*ROOT*] by sziraqui
[Experience Sharing] [GUIDE][ZE550KL]How To Root And Unlock BootLoader...
[New Question] Zenfone Go bootloop, Lock oem, no recovery
[New Question] BOOTLOADER UNLOCK TOOL/METHOD
[ROOT/TWRP] Asus Zenfone Go ZC500TG/Z00VD by keityrobins
Similarity with zenfone Go (ZB500KL) by Noobzone01
How To Root & Unlock the ASUS ZenFone Go ZC500TG via TWRP
How To Root & Unlock the ASUS ZenFone GO (ZC500TG)
I hope these, at least, points you in the right direction.
Good Luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
hey..
my device is ZB552KL zenfone go and anybootloader unlock command is not working and there is no option on developer options "enable oem lock"..
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot devices
GAAXGV682849CDW fastboot
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.000s
and recovery is not writable,
C:\Users\Desktop\Go Root>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (14628 KB)...
OKAY [ 0.475s]
writing 'recovery'...
FAILED (remote: not supported command in product image.)
finished. total time: 0.489s
t-mobile_mda said:
hey..
my device is ZB552KL zenfone go and anybootloader unlock command is not working and there is no option on developer options "enable oem lock"..
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot devices
GAAXGV682849CDW fastboot
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Users\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.000s
and recovery is not writable,
C:\Users\Desktop\Go Root>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (14628 KB)...
OKAY [ 0.475s]
writing 'recovery'...
FAILED (remote: not supported command in product image.)
finished. total time: 0.489s
Click to expand...
Click to collapse
Try this
Get ahold of adbd insecure...
Patch it on the system.
Then try..
Open that program and click both options.
Next go online in the Google.
Search XDA Kingroot
Get that and make sure your online while it tries to root.
But I came across the same issues with other phones.
Insecure the adbd and make sure USB debugging is on.
Google has this option that automatically scans your phone... Says that kingroot or purify is harmful "would you like to remove it"
With buttons..
Along with checking if I am rooted or not.
Google tells you your not safe being rooted.
My question is who told them to automatically download sh$t on my phone when all options to do that are disabled.
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
solarsoap said:
Try this
Get ahold of adbd insecure...
Patch it on the system.
Then try..
Open that program and click both options.
Next go online in the Google.
Search XDA Kingroot
Get that and make sure your online while it tries to root.
But I came across the same issues with other phones.
Insecure the adbd and make sure USB debugging is on.
Google has this option that automatically scans your phone... Says that kingroot or purify is harmful "would you like to remove it"
With buttons..
Along with checking if I am rooted or not.
Google tells you your not safe being rooted.
My question is who told them to automatically download sh$t on my phone when all options to do that are disabled.
Click to expand...
Click to collapse
Regarding flashing...
It's saying the options in adbd and or the boot.img has no such function..
So your getting blocking.
You seem to be going great ,but you need to insecure it.
---------- Post added at 08:44 AM ---------- Previous post was at 08:42 AM ----------
solarsoap said:
Try this
Get ahold of adbd insecure...
Patch it on the system.
Then try..
Open that program and click both options.
Next go online in the Google.
Search XDA Kingroot
Get that and make sure your online while it tries to root.
But I came across the same issues with other phones.
Insecure the adbd and make sure USB debugging is on.
Google has this option that automatically scans your phone... Says that kingroot or purify is harmful "would you like to remove it"
With buttons..
Along with checking if I am rooted or not.
Google tells you your not safe being rooted.
My question is who told them to automatically download sh$t on my phone when all options to do that are disabled.
---------- Post added at 08:42 AM ---------- Previous post was at 08:40 AM ----------
Regarding flashing...
It's saying the options in adbd and or the boot.img has no such function..
So your getting blocking.
You seem to be going great ,but you need to insecure it.
Click to expand...
Click to collapse
I almost forgot...
In the settings of android there is a developer option to unlock boot loader. Anything above kitkatt from lollipop up
Hope that info helps u.
Same I have a Zenfone Go G550KL and its bootloader is locked, I contacted ASUS customer service and asked them if they can release a tool or an update that unlocks the bootloader and they straight up said no, no way we are doing that, and I don't understand why Google does it all the time with the Nexus/Pixel, and since they're keeping a 1-year-old device stuck at Lollipop, at least they can unlock the bootloader so we can install custom ROMs like Lineage OS and enjoy the latest and greatest and have a nice Stock Android experience but no, honestly I wouldn't buy any phone from ASUS after this
Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks
You're screwed.
In situations where there is a locked bootloader and a soft brick like this, sideloading a Google OTA image using the stock recovery would have been able to restore the device to operating condition. Unfortunately you have no recovery, and thus no way to restore this device.
If you are stuck in boot loop and have no recovery, there is a way to fix your problem. If fastboot commands work then download Wugs Nexus Root Toolkit and use that to return to stock. There might be a way to unlock the bootloader first and then go from there. Have you tried to get the bootloader unlocked through fastboot commands then flash TWRP. Dude thinks this through. There is always a way to fix a soft brick. I hard bricked not long ago and was able to fix my device on low level systems code. Just don't give up
Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.
Strephon Alkhalikoi said:
Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.
Click to expand...
Click to collapse
I flashed a faulty bootloader image via fireflash app instantly bricked. I went through low level fastboot recovery options. I fixed my device. This is a mid level soft brick it can be fixed just needs some patience and perseverance. If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible. When I bricked it was a black screen, qhusb Qualcomm level I needed to restore my bootloader, I did it. This guy can fix his situation, I could do it for him if I had the device in hand.
Rondeau79 said:
If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible.
Click to expand...
Click to collapse
Look, we can go back and forth on this until blue in the face. The facts of the matter are as follows.
1. The bootloader is locked.
2. There is no OS in the system partition.
3. There is no stock recovery.
4. An OS in the system partition is required to be able to unlock the bootloader.
5. A stock recovery is required to sideload OTA images.
6. The original post does not mention whether the OP tried unlocking the bootloader.
You mentioned Fastboot. Everything you described in the quoted portion of your post works, but only if the bootloader can be unlocked. I'm assuming however the OP tried that already, failed, and went straight into flashing system images. If he didn't try it, he should, although I believe the attempt will fail.
Any help here. I have the exact same situation. Should I take my phone to Motorola/Google for repair? Anything else i can try?
@sumit.nathany: If you are in the same situation (locked bootloader, no OS, no recovery) you'll need to contact Motorola. But it won't hurt to try unlocking the bootloader before you do.
The only other option requires hardware hacking, and both the tools and methods can't be discussed here (against XDA rules).
Not that I know much about this, but what about the fastboot boot recovery.img command? If used with a Google recovery image, it might get around the bootloader lock?
Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.
Strephon Alkhalikoi said:
Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.
Click to expand...
Click to collapse
Making it work, but only with an original recovery from Google, would not open any opportunities.
BTW, do you, or anyone else have any theories why this happens? Hardware error?
It probably could be made to work, but then you'd run into an issue of people spoofing the stock recovery, which would still open up the whole can of worms. Better to simply block the ability completely unless the bootloader is unlocked.
As to how this happened I will not speculate. Reason being that any speculation would be useless without seeing the devices firsthand and examining them. Not to mention the people that would be throwing hissy fits thinking I accused them of something. All that really matters here is that a device in this state is not something that can be fixed without a trip to the repair center.
fix it
truwrxtacy said:
Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks
Click to expand...
Click to collapse
I found a solution for this problem i know is late in the game but better late than never jijiji
Did you try unlocking the device with?
Code:
fastboot oem unlock
Zombie
Rezz577 said:
fix it
I found a solution for this problem i know is late in the game but better late than never jijiji
Click to expand...
Click to collapse
Hi sir.
Can you tell me the solution, please?
I am in yhe same situation, no recovery and bootloader locked, and bootloop
i wait for your answer
Hi, I'm about hours to jump from my window.
I wanted to flash EMUI 9 official C432 firmware, but I did it with HuRU so the compilation number was bad. I tried again with the official EMUI 9 beta update "The TOOL", but at some point TWRP lost conection with my PC, so as a dumb guy, I reseted the Developer Options, and the "Unlock OEM" option was greyed out and couldn't enable it.
So I rebooted to TWRP and made a Factory wipe, but I kept having problems with my pc detecting my phone. (I tried changing usb cable and port, reinstalling drivers, erasing all USB devices, etc). So I dont know why I did a Wipe Data partition, but it took so long that I turned off my phone.
So now, here is my problem/s:
>Bootloader unlocked/FRP Locked
>Constant Bootloop, nor OS or recovery works
>As I wiped Data partition, OS and TWRP or any recovery is not available (maybe?)
>As I have FRP Locked, I can't install any recovery nor .img (when I try to flash anything it says: "FAILED (remote: Command not allowed)"
>Also I installed Magisk, so when I run command to LOCK bootloader, it says that there is root: "FAILED (remote: root type is risk)"
fastboot data, maybe could help:
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot flash ramdisk recovery_ramdis.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (32768 KB)...
OKAY [ 0.887s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.897s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 13.464s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 13.476s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot oem get-build-number
...
(bootloader) :CLT-LGRP2-OVS 9.0.0.163
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.003s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.022s
PS C:\Users\Kev\Desktop\Nueva carpeta> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CLT-L29 8.1.0.156(C432)
OKAY [ 0.008s]
finished. total time: 0.009s
Any hopes for me or I should jump from my window?
Thanks
Only thing is to change motherboard..
You should go to huawei service.
If i were you i would try to find a way to downgrade to oreo using usb-otg method before going to hw service.
Many people report "activate oem unlock" being greyed out. I've noticed that too when i was on 9.0.163 and wiped my phone (it was active before factory reset) . It looks like this setting is simply inactive in pie. Downgrade to oreo is the only solution.
it is impossible to install anything - any firmware..
1. Have you ever tried installation with sd card (usb otg)?
2. Another thing is trying to contact funky huawei. People with similar problems got their devices fixed without having to switch mainboard.
forever_lol said:
1. Have you ever tried installation with sd card (usb otg)?
2. Another thing is trying to contact funky huawei. People with similar problems got their devices fixed without having to switch mainboard.
Click to expand...
Click to collapse
No, I havn't. Do I need to use a flash drive and connect it with an otg cable?
Yes I could contact FH but I don't have access even to recovery nor erecovery.
Also, If I choose to fix it with Huawei Service I can't because in my country there is not service for P20 PRO. So i'm dead.
polaco95 said:
No, I havn't. Do I need to use a flash drive and connect it with an otg cable?
Yes I could contact FH but I don't have access even to recovery nor erecovery.
Also, If I choose to fix it with Huawei Service I can't because in my country there is not service for P20 PRO. So i'm dead.
Click to expand...
Click to collapse
1) yes indeed. I use micro sd card and usb adapter for that purpose.
2) it's worth to ask anyway.
forever_lol said:
1) yes indeed. I use micro sd card and usb adapter for that purpose.
2) it's worth to ask anyway.
Click to expand...
Click to collapse
So I'll buy and OTG-USB cable so I can use this.
I recently requested for an FRP Unlock Code with this program: Huawe FRP Tool, and used it, but now phone keeps rebooting trying to get into recovery and doesn't even get into fastboot mode. I think this is the end.
polaco95 said:
So I'll buy and OTG-USB cable so I can use this.
I recently requested for an FRP Unlock Code with this program: Huawe FRP Tool, and used it, but now phone keeps rebooting trying to get into recovery and doesn't even get into fastboot mode. I think this is the end.
Click to expand...
Click to collapse
Sorry too hear that man. I hope you'll find a way to fix it.
forever_lol said:
Sorry too hear that man. I hope you'll find a way to fix it.
Click to expand...
Click to collapse
Trying to do everything fast I f*ked up. Anyway, I think I learned the lesson not to go that far and settle a little bit. Anyway, don't use FRP Unlock tool, at least if you are bricked.
I think the last solution is to switch mainboard, but anyway I can't get it in my country, so Idk
i also have this problem, have send it to service centre here in The Netherlands.
They could repair it, with replacing the motherboard for 450 euro.
I let them send it back unrepaired.
coolhead said:
i also have this problem, have send it to service centre here in The Netherlands.
They could repair it, with replacing the motherboard for 450 euro.
I let them send it back unrepaired.
Click to expand...
Click to collapse
Hello.
Registered to report a successful repair after a manual firmware upgrade to EMUI 9.
After the update, I made a reset and got a brick.
Bootloader and FRP after updating blocked. He reset the phone, got a brick.
In funkyhuawei [x] club, he paid $ 18.00 USD to restore the brick using the eRecovery method. This method did not work. I made a request for a refund, they did NOT return the money. I do not recommend to contact this organization.
The problem was solved by the official corporate service center of Huawei in Moscow. They restored the firmware in my device. Service cost $ 12USD.
took 1 hour of time.
There is no need to change the motherboard.
Thanks to all.
Hi, I'm trying to get TWRP flashed onto my device (model number G8441), but when I try to flash it with fastboot it spits out an error:
> fastboot flash recovery twrp.img
Sending 'recovery' (33688 KB) OKAY [ 0.885s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
I'm using https://twrp.me/sony/sonyxperiaxz1compact.html (if it helps, I wanted to flash https://forum.xda-developers.com/t/rom-havoc-os-4-6-official-r.4225905/ and I use Arch Linux (I don't have a Windows device available))
I have enabled USB Debugging and OEM Unlocking. I have the US model.
I'll try to be able to send more information if needed.
Sorry about the terrible formatting, its my first time using XDA forums.
Sneexy said:
Hi, I'm trying to get TWRP flashed onto my device (model number G8441), but when I try to flash it with fastboot it spits out an error:
> fastboot flash recovery twrp.img
Sending 'recovery' (33688 KB) OKAY [ 0.885s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
I'm using https://twrp.me/sony/sonyxperiaxz1compact.html (if it helps, I wanted to flash https://forum.xda-developers.com/t/rom-havoc-os-4-6-official-r.4225905/ and I use Arch Linux (I don't have a Windows device available))
I have enabled USB Debugging and OEM Unlocking. I have the US model.
I'll try to be able to send more information if needed.
Sorry about the terrible formatting, its my first time using XDA forums.
Click to expand...
Click to collapse
You enabled OEM unlocking but did you actually unlock the device? Toggling the switch in the Dev options is one thing but to properly unlock the bootloader, you must have an unlock key from Sony.
More info here:
How To Unlock Bootloader on Xperia XZ1 and XZ1 Compact
Good News for all Sony Xperia XZ1 and XZ1 Compact users. Now you can Unlock Bootloader on Xperia XZ1 and XZ1 Compact, Read all the instruction carefully.
www.getdroidtips.com
AlexKarimov said:
You enabled OEM unlocking but did you actually unlock the device? Toggling the switch in the Dev options is one thing but to properly unlock the bootloader, you must have an unlock key from Sony.
More info here:
How To Unlock Bootloader on Xperia XZ1 and XZ1 Compact
Good News for all Sony Xperia XZ1 and XZ1 Compact users. Now you can Unlock Bootloader on Xperia XZ1 and XZ1 Compact, Read all the instruction carefully.
www.getdroidtips.com
Click to expand...
Click to collapse
I actually didn't, I thought it was already unlocked, silly me. Going to try that now.
Got the code and such, but when I run the command to unlock the bootloader, fastboot complains fastboot: invalid option -- 'i'
Is there another/newer command or tutorial I'm supposed to check?
EDIT: Checked Sony's site and it had the updated command, Thanks for your help!
Sneexy said:
Got the code and such, but when I run the command to unlock the bootloader, fastboot complains fastboot: invalid option -- 'i'
Is there another/newer command or tutorial I'm supposed to check?
EDIT: Checked Sony's site and it had the updated command, Thanks for your help!
Click to expand...
Click to collapse
You're welcome
Does that mean you unlocked the bootloader on PIE? When I did it, the only known way was to downgrade to OREO, temp root, back up TA partition, unlock bootloader, restore TA and then upgrade back to PIE.
AlexKarimov said:
You're welcome
Does that mean you unlocked the bootloader on PIE? When I did it, the only known way was to downgrade to OREO, temp root, back up TA partition, unlock bootloader, restore TA and then upgrade back to PIE.
Click to expand...
Click to collapse
Yep, I unlocked it on Pie.
I'm having, a similar (sort of) problem. I've unlocked the bootloader following Sony's steps. Fastboot sends recovery "okay", writes it "okay" as well. But it doesn't boot into recovery. Instead, the phone briefly shows an opened lock image with the text "Your device software can't be checked for corruption. Please lock the bootloader", and it proceeds to booting up into the OS.
suquet.paul said:
I'm having, a similar (sort of) problem. I've unlocked the bootloader following Sony's steps. Fastboot sends recovery "okay", writes it "okay" as well. But it doesn't boot into recovery. Instead, the phone briefly shows an opened lock image with the text "Your device software can't be checked for corruption. Please lock the bootloader", and it proceeds to booting up into the OS.
Click to expand...
Click to collapse
I'll try and help but I need a little info:
First: Do you have USB debugging enabled?
How did you flash recovery? Could you give your steps?
How are you booting into recovery?
AlexKarimov said:
I'll try and help but I need a little info:
First: Do you have USB debugging enabled?
How did you flash recovery? Could you give your steps?
How are you booting into recovery?
Click to expand...
Click to collapse
Hey Alex! After a few hours I managed to figure out what was wrong.
I had to force reboot (after flashing the OS, via fastboot reboot) and press Sony's recovery hardware combination buttons which Sony themselves had misrepresented as being VOL DOWN + Power. Turns out, it's VOL UP + PWR.
So, I'm all good! I was able to boot into twrp and give it all the accesses and permissions it needed.
Facing the same issue here with my Vivo Y21,when I run fastboot flash recovery of the img file it says
Sending 'recovery' (32700 KB) OKAY [ 0.781s]
Writing 'recovery' FAILED (remote: 'Verify state locked')
fastboot: error: Command failed
can anyone help please
Hello. Is there a way to unlock the Bootloader without having to do it from the same phone settings??
I am not able to enter the phone because of the security it has and I am unable to flash it again because it has the Bootloader blocked =(
I have the same issue with VIVO Y16
Sending 'boot' (32768 KB)
FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
did anyone face the same issue? please help
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) ***************************************
(bootloader) WARNING: This command erases user data!
(bootloader) Please re-run this command to confirm.
(bootloader) ***************************************
OKAY [ 0.022s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Bootloader is now locked
OKAY [ 0.045s]
finished. total time: 0.046s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.012s]
finished. total time: 0.014s
C:\ProgramData\LMSA\Download\RomFiles\LAKE_QPWS30.61_21_18_7_subsidy_DEFAULT_regulatory_XT1965_2_SUTEL_DS_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23537 KB)...
OKAY [ 0.618s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.678s
Click to expand...
Click to collapse
Does anyone know how to fix this?
Did you ever get this sorted ? I have the same problem on my G7 Plus. I unlocked, then loaded Lineagos, but then decided to go back to stock, I used LMSA to rescue the phone, but still got the warning and boot time "Your phone has loaded a different OS" and I can't use GPay. I tried the fastboot OEM lock (worked) and fastboot flashing lock, but I still get the warning and I can't use GPay.
I think in my case the LMSA rescue didn't work because I was originally on Android 9 and the rescue took me straing to Android 10
Elrom said:
Hello guys.
So, I recently bought a new phone and thought "let's try rooting my old one" and tried it on my G7+. I ended up not liking out it turned out (Netflix DRM, Vanced didn't work properly, etc).
So I reflashed the stock ROM and put the comand fastboot oem lock.
The thing is, after I boot the device again, all the messages still appear, like Your device has loaded a different operating system" and below that "ID: " (blank) and I also get "Verity mode is set to disable".
The thing is, every tutorial I come across to relock the bootloader(regular G7, G7 Power, G6, etc), says that when you enter the command "fastboot oem lock" two times, the message that you should only flash signed images, does not appear. I instantly get the state flashing_locked, and I can't continue flashing the stock firmware like every other tutorial shows.
In short, once you enter the command "fastboot oem lock", it's locked for good, and you can't do anything unless you unlock it again, starting the whole process again.
The problem is, even with the bootloader locked again, my device still shows as "insecure", Netflix is nowhere to be found on the app store, and the state of my device is not certified.
I wouldn't have unlocked If I knew it was going to be this difficult to get it back. Selling it now would be next to impossible.
Here are some examples of the errors I'm getting:
Does anyone know how to fix this?
Click to expand...
Click to collapse
You can try downloading each versions from your region (RETUS, RETEU, etc) and retry the relock process until you find the correction version.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com