I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
wschamps42 said:
I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
Click to expand...
Click to collapse
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
I'm getting the error device already locked even though my bootloader clearly states that the bootloader is in unlocked. I just flashed the factory image for the phone and still same error. Any ideas?
Rox598 said:
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
Click to expand...
Click to collapse
hello i was able to get it to show up in fastboot devices but i am unable to relock...when i try to get it to relock it goes and says waiting for device even though its in fast boot mode.
Related
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Osaab said:
my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Click to expand...
Click to collapse
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
mywindow said:
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
Click to expand...
Click to collapse
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I doubt it, since you don't need to unlock it a little more.
You should check your USB cable, or try to switch to another port. But if the error still persists, you need to send it to repair.
I am sorry mate, but u might have to send it in for real
Maybe your nand memory is corrupted. Since ur phone just crashed for "no reason" and then got stuck in fastboot, it may be an indicator for that.
Best regards!
Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I BELIEVE once you tick it and unlock, it does not turn back off (allow OEM unlock)
But as said above, this option only allows the bootloader to accept the unlock command...
Best case is the internal storage got scrambled and your partitions/ partition table is corrupt/missing/gone, worse case and maybe more likely is hardware failure?
Not sure if you can send terminal commands, but next step is either just RMA or searching the internet for a way to manually rebuild partition table from bootloader?
I guess?
Sounds like it messed it self up pretty good somehow, sorry man.
I had unlocked bootoader for more than 1 year and didn't have any problem with it. But now for some reason I can't flash anything.
When I try to flash using TWRP i get ERROR 1. From recovery log:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
and when i try adb (not only flash but other commands like fastboot oem device-info aswell)
Code:
FAILED <Remote: command not allowed>
Any idea how to fix this?
woooz said:
I had unlocked bootoader for more than 1 year and didn't have any problem with it. But now for some reason I can't flash anything.
When I try to flash using TWRP i get ERROR 1. From recovery log:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
and when i try adb (not only flash but other commands like fastboot oem device-info aswell)
Code:
FAILED <Remote: command not allowed>
Any idea how to fix this?
Click to expand...
Click to collapse
Try to unlock again!
Bootloader say locked in green or unlocked in red?
.
persona78 said:
Try to unlock again!
Bootloader say locked in green or unlocked in red?
.
Click to expand...
Click to collapse
Unlocked red.
woooz said:
Unlocked red.
Click to expand...
Click to collapse
try to unlock again, and check what it say will you try to unlock.
.
Note: The only file system that works with fastboot is the file system that you extract from update.app, only!
But doesn´t work if you flash with twrp, for twrp is the file system that you pull from the phone.
.
persona78 said:
try to unlock again, and check what it say will you try to unlock.
Click to expand...
Click to collapse
FAILED (remote: already fastboot unlocked)
persona78 said:
Note: The only file system that works with fastboot is the file system that you extract from update.app, only!
But doesn´t work if you flash with twrp, for twrp is the file system that you pull from the phone.
Click to expand...
Click to collapse
I know. Tried to flash stock boot img with fastboot and zip with magisk in twrp.
EDIT: I was able to flash boot.img after this, I guess it worked. Thanks!
I have the same problem again... But now unlocking bootloader again doesn't help.
Also reflashed twrp.
Anyone?
woooz said:
Anyone?
Click to expand...
Click to collapse
If you only want to flash boot.img you can do that in TWRP.
keikari said:
If you only want to flash boot.img you can do that in TWRP.
Click to expand...
Click to collapse
Not only and I can't.
When I try flash anything in twrp i get this error:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
woooz said:
Not only and I can't.
When I try flash anything in twrp i get this error:
Click to expand...
Click to collapse
You still didn't fixed since then?
D1stRU3T0R said:
You still didn't fixed since then?
Click to expand...
Click to collapse
When I created this topic all I had to do to fix this problem was unlocking bootloader again.
But few days ago this problem occured again and unlocking bootloader doesn't help.
It's a bug. REINSTALL default firmware it 3 buttons, let it turn on. Unlock boot again and flash twrp. If that does not work either your phone is damaged or you did something wrong in the middle.
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
xdafanboii said:
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
Click to expand...
Click to collapse
there is a firmware for the phone
unpack it
u will find there file Checksum.ini
and unlock‐secro.img(or diferent name point is unlock)
rename checksum.ini on checksum.oem
then turn off all checks in flashtool leave marked only SECRO line
u must choose unlock‐secrom.img for SECRO line
once u'll flash SECRO u will have to flash twrp, to do that u must turn off all checks except RECOVERY, for RECOVERY u must open recovery 1.72.img then flash it, after u can just flash supersu.zip via twrp
i've done it all on my 1.76 device it will also work on 1.79
twrp u can find here(u need to register on that forum)
https://4pda.ru/forum/index.php?showtopic=756527&view=findpost&p=53228248
Hi.
I have searched for a solution but I couldn't find anything.
I was trying to install GCam and download the file here and when I selected Magisk Module in Magisk app my phone rebooted and didn't boot it was stuck in the screen after Android One logo.
I manually rebooted my phone and it showed me this message.
I can't take a pic of my phone because I don't have a camera or another phone right now but the error is the same in the I uploaded.
Has anyone had the same problem?
I can't flash the stock rom using the MiFlash 'cause it returns an erro: error: "Flash bluetooth_a error"
I solved the problem by unlocking the bootloader again.
gsilva92 said:
I solved the problem by unlocking the bootloader again.
Click to expand...
Click to collapse
I am sorry of course. But how did you unlock the bootlaoder? I just have a mistake
"remote: 'Flashing Unlock is not allowed"
Damir51 said:
I am sorry of course. But how did you unlock the bootlaoder? I just have a mistake
"remote: 'Flashing Unlock is not allowed"
Click to expand...
Click to collapse
Sorry for taking too long to answer.
You can unlock your bootloader by following this guide.
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484