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
Related
Hello, everyone.
So, about an week ago, I posted a thread to ask for your help regarding my broken N6. Since then, nothing has changed(but got worse, I guess...?). Here is what is happening with my N6 right now.
1) It powers up(thank god) but goes straight to the boot-loader screen(I believe this means that my device doesn't have system image file within the device)
2) On boot-loader menu(Start, Restart bootloader, Recovery mode, Power off, Factory, Barcodes, BP Tools, QCOM, Bootlaoder logs), only few are working(Restart bootlodaer, Power off, Barcodes). When I try to perform other than these, it just goes back to main boot-loader screen.
3) I tried to use both Nexus Root Tool kit and manual installation of each image but doesn't work for both of them(From this, I believe that my phone is just BROKEN)
With this happening, conclusion that I can think of is
1) There is no 'Recovery' available in my device(that's why I can't do anything to recover my device)
2) ADB is not functioning.
Only solution that I can think of from this point is that contact Motorola and replace my device(which is what I am currently doing but Motorola has huge problem with their customer service that I am waiting for their answer for about 2 weeks now)
If possible, would there other options that I can repair this device by myself?
I appreciate your attention.
Sincerely.
Adb has no impact on bootloader. What do you mean doesn't work when you fastboot the factory image?
Sent from my Nexus 6 using XDA Free mobile app
your problem is the use of toolkits. stay away from them, unless you know what you are doing!
your phone doesnt have any rom on it. you can.. 1. flash the factory img via fastboot, like you are supposed to do(not via a toolkit), or 2. unlock the bootloader, flash a custom recovery then while in the custom recovery adb push a rom, gapps, and supersu and flash them that way. what you did does not give you the right for a trade in.
The two previous posters are correct. You just need to fastboot flash the factory rom and factory recovery. It is fairly simple, if you take the time to read how to do it. There are posts all over XDA for beginners on how to do this. And I cannot stress how correct @simms22 is. Toolkits may seem to make things easy, but when there is a problem, you need to know how to manually fix it. I just personally stay away from toolkits. And I was in your shoes. I didn't know jack about flashing roms and such. Just reading XDA got me to where I am. (and i am still learning!)
Like the others have pointed out, you are fine. You have access to your bootloader screen, this is a Nexus. Take a deep breath. Take some time and read this site about flashing a factory image. Please do it the best way - manually with fastboot commands. If you get stuck come back here and someone will help. It really is easy. Please repeat after me "I will avoid all toolkits from now one".
Start with this and read lots.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Flashing the factory image should still work from boot loader with fast boot.
Follow the second link for manual flashing after downloading the zip from the first link.
https://developers.google.com/android/nexus/images
If you run into the missing system.img problem here is the link to fix it:
http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/
This way you can start from the beginning.
Problem with flashing factory image manually.
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
chg911225 said:
First, thanks everyone for helping me by providing useful information but there is a problem when I flash factory image manually.
Whenever I try to flash image(for example, 'boot.img', or other images, I always get the same error 'FAILED <remote failure>' and not installed on my device. From here, I have no idea what to do.
Click to expand...
Click to collapse
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
simms22 said:
first off, does fastboot see your device?? you can check by typing.. fastboot devices
if it doesnt see your device, do you have the driver instslled?
Click to expand...
Click to collapse
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
chg911225 said:
fastboot detects my device. but when I tried to TWRP recovery, it shows following error.
sending 'recovery' <11668 KB>...
OKAY [ 0.375s]
writing 'recovery'...
<bootloader> Failed to erase partition
<bootloader> Failed to flash partition recovery
FAILED <remote failure>
finished. total. time: 6.133s
Click to expand...
Click to collapse
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
simms22 said:
look for the command to erase the recovery partition. youll have to google it as i dont know(or remember) it. i dont even own a computer :angel:
then youll have to reflash the recovery.
Click to expand...
Click to collapse
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
chg911225 said:
found the command "fastboot erase recovery" but not working with following error message.
fastboot erase recovery
erasing 'recovery'
<bootloader> Erase allowed in unlocked state
<bootloader> Failed to erase partition
FAILED <remote failure>
finished. total time: 5.763s
*my phone is unlocked for sure(I checked 'fastboot oem unlock' and it said
fastboot oem unlock
...
<bootloader> Device already unlocked!
FAILED<remote failure>
finished. total time: 0.003s
Click to expand...
Click to collapse
i have no idea, but this is a good thread to read and post questions about fastboot in http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
RIP. What did you do to your N6?
OP how did you install your fastboot. I would assume you did it from within a toolkit. That is probably your problem. If that is the case, please do this. Go here and install the .exe: http://developer.android.com/sdk/index.html#Other
It's big I know it but just do it please.
Make sure everything (SDK) gets installed in a folder path like c:\android or something you will easily remember. This is very important because it is within this folder you will place the extracted factory image files (.img). Place all full unzipped .img files in this folder.
Please follow method #2 in this excellent guide:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
zetsumeikuro said:
RIP. What did you do to your N6?
Click to expand...
Click to collapse
One day it just shut down by itself and since then it's like this. I just contact Motorola and they are going to ship me new device with different color(idk y they are still having problem with their stocking their devices in because what I had was Cloud White 32Gb but only model that were present when I contact them was Midnight blue with 32Gb, other options are all out of stock. really wished they had a white color...)
This phone is a damn Nexus, it can't die. It's user error.
Sent from my Nexus 6
Hi all - I'm not entirely stupid, but I'm probably doing something basically wrong here.
I'm trying to convert my Chinese CRR-UL00 to something a bit more western, but still with dual SIMs, so converting it to Middle East/Africa model seems like a good idea. I'm not interested in root or even a custom recovery in the long term. I just want to change regions.
I have been trying to follow the instructions both here and elsewhere but am getting stuck early in the process. I've tried a bunch of different things so my phone may be in an odd state.
I have, I believe, unlocked the bootloader via DC-Unlocker. When I reboot into the bootloader (using adb reboot bootloader) I get a white screen with a header that says "Fastboot&Rescue mode", an Android icon, and "Phone Unlocked" in red underneath.
Attempting to flash a TWRP recovery.img using fastboot doesn't seem to have any effect, even though fastboot reports it has successfully transferred the image. Trying to boot into recovery - either using adb/fastboot or vol+/power keys results in the phone hanging at the Huawei logo at bootup. I've also tried to flash back a "stock" recovery.img. At no time have I been able to get the fastboot menu on the phone - it's either the white screen with no options, or the phone hanging at the Huawei logo.
Despite all this the phone will still operate normally! When operating normally the phone now reports its running CRR-UL00C00B172.
Any ideas what I'm doing wrong? What recovery.img should I use?
Thanks for any help!
WD
I'm not home right now but from memory the one I've used was named somthing like TWRP-2.8.7.0-Carrera.img
Thank you for the quick reply. I've had some time to have another go at this. Still can't seem to get TWRP recovery onto the phone...
It seems to flash...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24454 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.242s]
finished. total time: 0.787s
but then rebooting and holding down various keys to get into Recovery, I either get a hang at the Huawei logo, or I eventually end up back at the stock recovery. (I think if it boots to the full OS it overwrites any TWRP recovery)
What is the actual key combo to get into recovery? Various web pages report different combos:
- vol+ and vol- and power
- vol+ and power
- ?? something else
Many thanks,
wd
wonky donkey said:
Thank you for the quick reply. I've had some time to have another go at this. Still can't seem to get TWRP recovery onto the phone...
It seems to flash...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp3.img
target reported max download size of 471859200 bytes
sending 'recovery' (24454 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.242s]
finished. total time: 0.787s
but then rebooting and holding down various keys to get into Recovery, I either get a hang at the Huawei logo, or I eventually end up back at the stock recovery. (I think if it boots to the full OS it overwrites any TWRP recovery)
What is the actual key combo to get into recovery? Various web pages report different combos:
- vol+ and vol- and power
- vol+ and power
- ?? something else
Many thanks,
wd
Click to expand...
Click to collapse
- flash stock recovery
- boot device normaly
- go into developersettings and look for OEM-Unlock
- if available, enable it. if not go to fastboot mode and use "OEM-Unlock" command with code again. (sometimes the bootloader isn´t unlocked fully on first try)
- then try to flash TWRP 2.8.7.0
- fastboot reboot
anyway whats your current build?
i can only access recovery via. "adb reboot recovery" command
Thanks for the help. Clearly I'm doing something wrong.
On rebooting normally after flashing recovery I don't see an OEM-unlock option in Developer Options. Attempting to fastboot oem unlock again gives me failed, already unlocked.
I've tried four different downloads of TWRP recovery from different places, I've even tried different adb/fastboot binaries to make sure that's not the issue. The TWRP recovery images I have are:
25,040,896 bytes (three different downloads, and I've seen one or two sites that claim this is only for the L09 version)
25,378,816 bytes (from a random Chinese web site that says its for the CRR-UL00 B131)
I'm on CRR-UL00C00B172. I wonder if I need to flash everything back to something earlier? (e.g. I have a full download of UL00C00B153).
wd
OK, success!
At some point I ended up in stock recovery and it suggested to download and install UL00C00B131. (why B131? Maybe because at some point I had been using the Chinese download with B131 on it?). Did so.
adb reboot bootloader
relock and unlock to confirm unlock is definitely working in fastboot
fastboot reboot
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot reboot
adb reboot recovery
...now I'm into TWRP!
Thanks all for your help.
wd
...and now I've got it localised to MEAFNAF (C433) - so still dual SIM but with Google Play by default etc. Running CRR00-UL00C433B146 which is available from Huawei.
I followed these instructions. (based on the original Russian post but much better than Google Translate
At the end, the install of update.app hung at 90%. Using vol+/power to get into recovery dropped me into a Chinese recovery (probably from the recovery.img I flashed back to remove TWRP). Factory resetting from recovery resulted in booting to the full OS, but I didn't get the option to enter a Google ID in setup and the full OS was dog slow with a black home screen.
Doing another factory reset, I was then asked for a Google ID during setup, and this time resulted in a fully functioning Googley OS.
I understand I won't get OTA updates as I've changed my localization, so I'll keep an eye out for the final Marshmallow release from Huawei's web site.
I hope this thread is useful to others.
wd
I recently purchased a Moto X XT1056 through eBay to use as a guinea pig for flashing custom ROMs without risking my primary phone. When I first booted the phone, the last owners account was still present and alot of apps were crashing. I didn't care because I was going to wipe it anyway. I do eventually, and frustratingly, make it to the Settings Menu that allows me to factory reset the phone. It restarts, does its thing and reboots, but it didnt get wiped. I thought, 'No worries, I'm going to unlock it and that will wipe it.'
I started following the instructions on the CM website.
First thing I did was use the Moto web site to get an unlock code and unlock the bootloader. I'm assuming that succeeded because I get the Bootloader unlocked boot screen and the bootloader screen says 'Device is UNLOCKED. Status Code: 3'.
Then I tried to flash twrp-2.8.7.0-ghost.img per the instructions and get this result:
Code:
[[email protected] phone]# mfastboot flash recovery Recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (8498 KB)...
OKAY [ 0.834s]
writing 'recovery'...
OKAY [ 0.949s]
finished. total time: 1.783s
[[email protected] phone]#
I assume everything is fine and reboot into Recovery using the bootloader screen, but all I get is the dead android and red triangle. Pressing VOL+ and Power get me to the stock recovery where I can reboot the machine. It boots into Android and I notice that the unlock didn't wipe the device. I turn it off and using the button combo boot into the bootloader then select Recovery and use the stock recovery to factory reset the device. I reboot the phone and see that the previous owners account is still there and there are a bunch of popups stating that apps are crashing. I have tried a number of things from a few threads I have read, but nothing seems to work. Trying to flash anything to any partition just seems to succeed without an error, but nothing changes. The only time I get anything different is when i try to erase or format a partition, then I get 'Permission Denied'.
I haven't been able to find any help using search on these forums or using Google.
Please Help.
I do know that it has 4.4.4 on it and Bootloader 30.B7.
I use Linux only and do not have access to a Windows machine.
Android SDK is installed so I have 'adb' and 'fastboot' and I also installed 'mfastboot.'
And, yes, I issued all the commands with root privileges.
its dead already! problem is inside emmc chip! its fried ;(..
I have a review phone of the P9 (the 09 version). I'm trying to put a nougat beta on it. Bootloader came unlocked- see attached photo. When i go into bootloader fastboot devices sees it no worries. I ran the bat file to check and yes the bootloader is unlocked according to it.
Problem is that when I try to flash TWRP i get:
Code:
fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery" (22368 KB)...OKAY [ 0.655s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.667s
I am not a noob to hacking android etc that is for sure but this is doing my head in. Is there an issue with the bootloader unlock? I've sent an email to Huawei support people as well. I had issues getting a bootloader unlock code anyway as being in Australia it doesn't allow be to do anything in Huawei ID, so i cannot get the code. I also tried using the beta app but even when using a VPN it was geoblocked.
ideas on what is going wrong?
thanks
Make sure OEM unlock is enabled in developer settings. If you have an app called "Phone Finder" or any other phone tracker app, disable it. If that doesn't work, you can try restoring phone to factory settings and enable OEM unlock again then try again.
I tried the above stuff mate- unfortunately it did not work. only phone finder is android device manager and it is turned off (phone is basically stock). OEM unlock is enabled correctly etc. even factory reset and did it all over again. oh well. i give up for now. i would love root on this too...
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