When I try flashing anything at all it says FAILED (remote: not supported in locked device). I unlocked it via "fastboot oem unlock" but I noticed it keeps getting back to the locked state when the phone reboots to bootloader.
In this thread people say to flash cache.img and see what happens. So I entered the command "fastboot flash cache cache.img" and I got FAILURE (remote: flash write failure).
I just want to mention that I've tried several guides and haven't had any luck. Also I'd like to say I haven't installed any custom ROMs nor rooted my phone before this happened.
Heres's an androidExchange topic if anyone wants to read it. http://android.stackexchange.com/qu...re-while-trying-to-fix-a-bootloop/98809#98809
Is there anything else I can do to confirm that my phone is dead, meaning it's some kind of a hardware problem?
Sorry, but your emmc is fried. Not being able to lock/unlock is a sure sign. You'll have to rma the device.
Sent from my Nexus 9 using XDA Free mobile app
Hello!
I have a small problem. A week ago died my phone when i unlocked the lockscreen one evening. Thought that the battery was empty, i put it on the charger and started up the phone a few hours later and the only thing that happens is that Google logo is displayed, then it starts over again. I can go into recovery and fastboot, but it does not matter what i do there. Managed to get it to be connected as a USB drive so I got out the pictures from it. But if you make a complete factory reset including data and restarts there everything left! Tried to run "fastboot format cashe" but it only return "FAILED (remote: flash write failure) "
The phone is rooted and bootloader is unlocked, i had a custom rom installed, and it had worked since beginning of summer.
Have you already tried to reflash stock rom with fastboot? Maybe that will help to get your partitions working properly...
i followed a guide on androidrootz dot com, "how-to-unroot-nexus-5-complete-stock" but directly when i try to flash bootloader i get a error message.
Does the bootloader remain unlocked? What error are you getting when flashing stock?
audit13 said:
Does the bootloader remain unlocked? What error are you getting when flashing stock?
Click to expand...
Click to collapse
Yes! It remains unlocked! Heres the "print screen"
C:\UnrootNexus5>fastboot flash bootloader-hammerhead-HHZ11d.img
unknown partition 'bootloader-hammerhead-HHZ11d.img'
error: cannot determine image filename for 'bootloader-hammerhead-HHZ11d.img'
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
g90814 said:
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
Click to expand...
Click to collapse
I Have tried that also, here is the print from that:
Connectivity Status: Fastboot Device Connected
Flashing bootloader-hammerhead-HHZ11d.img to BOOTLOADER partition...
fastboot flash bootloader "C:\UnrootNexus5\bootloader-hammerhead-HHZ11d.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
But when it boots up again its still unlocked...
fastboot flash bootloader bootloader.img
Oh! I missed one word. Will try it tonight!
Nope.... Doesnt work either....
C:\UnrootNexus5>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.256s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.457s
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
audit13 said:
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
Click to expand...
Click to collapse
Damn! thats what im afraid of....
ChocholateMaster said:
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
Click to expand...
Click to collapse
The telephone is unlocked, the lock is open when i reboot the phone.
C:\UnrootNexus5>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
I don't know how it got damaged. One day, ti started bootlooping and the bootloader had re-locked on its own even though I unlocked it straight out of the box. I booted into fastboot, unlocked the bootloader, and it only too a few seconds to erase everything. I immediately rebooted in fastboot and the bootloader was locked again. This unlock/relock happened over and over.
I booted into recovery and tried a factory reset but recovery could not mount cache or data to perform the erase.
My phone just kept getting stuck at the Google logo or bootlooping.
ChocholateMaster said:
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
Click to expand...
Click to collapse
I have tried that also, when im just type "FASTBOOT OEM LOCK" it lookes like this:
C:\UnrootNexus5>fastboot oem lock
...
OKAY [ 0.054s]
finished. total time: 0.054s
PERFECT!?!? But when i reboot its still unlocked.... if i do first lock, then unlock without rebooting, i get a new meny on the phone where i have to chose if i want to unlock my device. and if i chose yes it will reboot and its the same again....
How do i download that file??? I just got an EXE file, and i dont want to run that!
If it's not sticking on a reboot, that means the memory is most likely gone bad. I guess you could try using the diagnostic tool, which would confirm if the memory is bad.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
ChocholateMaster said:
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
Click to expand...
Click to collapse
after flashing it can take up to 15 mins to turn on because of first boot
@kardanmannen any news?
I'm getting more and more sure that the memorymodule is faulty in the phone. If you reboot in Recovery and select filemanager, for example you remove a directory with files, if you restart the phone, the directory is there again! And when you start it up in recovery and connect it to the computer, theres a few directorys you can write/delete/. Similarly, if you run "fastboot oem lock" and reboot it, its locked the first time it is started up and then the second time it is unlocked again.
Lost hope a little there and went off and ordered a Nexus 6P, hoping it will arrive on Wednesday.
Hello Guys, I am new to the forum. I read a lot of threads, but no one i found had the solution or the exact same problem i have.
I bought a new Xiaomi Redmi 4X and wanted to install the los 14.1 Version I found here in XDA (https://forum.xda-developers.com/android/development/rom-2017-08-07lineage-14-1-t3653016). (I have installed custom roms a few times before and also faced some problems)
I flashed twrp via the fastboot mode using my linux laptop. I installed the los zip file and booted into it, but it was stuck in a boot loop. I wanted to go back into twrp, but it did not work, so i tried it with the fastboot again. Then I saw that oem is locked.
As root user i tried to unlock it with
Code:
# fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
but it doesnt work.
So I am stuck now without any ROM and Recovery, I can only access to the bootloader.
I am happy for any help.
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying:
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
wiliestseven51 said:
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
Click to expand...
Click to collapse
Edit: Downgrading is not an easy task. My understanding is you will first need to downgrade your firmware, then flash a compatible RUU. I believe this requires you to be s-off.
As far as the backup you mentioned, well that's what TWRP is for. First you'll need to unlock your bootloader which you can do by following the instructions from the htcdev website (understand this will factory reset your phone). Then find the TWRP thread which will have instructions on how to temporarily boot TWRP or permanently install TWRP to your phone's boot partition. Within TWRP you can perform the backup you desire. There is a learning curve to all of this. Good luck.
RUU download here --> https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
About backup,if you are rooted, use twrp recovery o titanium backup app,otherwise google drive backup
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Maybe this could help though
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103
wiliestseven51 said:
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Click to expand...
Click to collapse
I use HTC windows driver version 4.10 and the fastboot binaries from step 4 of the unlock bootloader process. I've never had to make the choice you are describing.
Sounds like you are basically on the last step of the procedure, no?
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
wiliestseven51 said:
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
Click to expand...
Click to collapse
You have got oem unlock & adb debugging set in developers option sliders on? Try "adb reboot" command, see if your adb has been authorised on yr PC. I had a dodgy lead, using usb3 port, using shell instead of cmd cause similar problems