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!
So I was trying to unlock my bootloader with LG Laf Recovery MultiTool v1.2 (You can find it on android fourms) I choose Automatic unlock, and it went through fine. Until it got to the fastboot location. When it tried to use a command it returned: FAILED (remote: unknown command). Now its stuck booting into fastboot, but it won't accept any commands. They all return with the above error. Is there anyway that i can fix this?
What is your phone model? Can you enter download mode? If yes, then you can flash stock kdz ROM with LG Flash tool, see tutorial about returning to stock. Good luck.
I was successfully able to install TWRP and LineageOS on my OnePlus3T. However, due to the bugs in LineageOS, I downloaded the latest (non-Beta) OxygenOS from the OnePlus website and flashed that back onto my phone. I didn't realize that this would remove TWRP and give me an error screen about dm-verity error (in red) during the boot process. I have tried many things to get rid of the dm-verity error and to put TWRP back on the device so that I can eventually move back to a custom ROM. However, I am unable to get rid of the dm-verity error and everytime I try to install TWRP, it gets stuck on the TWRP splash screen. Then, I have to hold down the power button to power off, power back on, re-encounter the red dm-verity error and I am back into OxygenOS.
How can I get rid of the dm-verity error and get TWRP back on my phone?
Try sideloading any OOS version 4.0.2 or below, then use the following commands in fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
This will reset dm-verity, remember to root or flash the no-verity zip after flashing TWRP or it will trip dm-verity again.
This will not work in OOS 4.0.3 or the latest open beta as OP has patched out those commands.
Anova's Origin said:
Try sideloading any OOS version 4.0.2 or below, then use the following commands in fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
This will reset dm-verity, remember to root or flash the no-verity zip after flashing TWRP or it will trip dm-verity again.
This will not work in OOS 4.0.3 or the latest open beta as OP has patched out those commands.
Click to expand...
Click to collapse
I can do that. However the latest version of the fastboot command does not allow for fastboot oem disable_dm_verity (assuming that this command runs from the PC and is executed against the phone via USB). For example, in command prompt, if I type fastboot help, there are no options for oem disable or oem enable.
oem disable_dm_verity doesn't show up in my fastboot prompt either when I enter "fastboot", but it was able to lock and unlock dm-verity when I used it a few weeks ago. I'm not entirely sure what version of fastboot I have, though are you sure the command was removed and not just hidden?
Anova's Origin said:
oem disable_dm_verity doesn't show up in my fastboot prompt either when I enter "fastboot", but it was able to lock and unlock dm-verity when I used it a few weeks ago. I'm not entirely sure what version of fastboot I have, though are you sure the command was removed and not just hidden?
Click to expand...
Click to collapse
I used it earlier today and it said that it is an unknown command. However, I attempted it against OOS 4.0.3. I don't think this should matter.
You could try using older versions of minimal adb and fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790
Thanks. I will try an older version this evening and let's see what happens. I should be able to get OOS 4.03 correct? Is there a reason you are recommending OOS 4.02 and lower?
Oneplus patched out the fastboot oem lock/unlock commands in the OOS 4.0.3 update. The phone will refuse the commands outright, technically it was a vulnerability. I suspect that the reason your fastboot was unable to run the command was because the phone's firmware didn't recognize it, not because the commands were removed from fastboot.
Those commands will only work on OOS with firmwares from 4.0.2 or below.
You could flash only the 4.0.2 firmware without replacing the entire 4.0.3 ROM by using this guide, though I'm not sure if you can do it without TWRP.
After resetting dm-verity on an older version, you can dirty flash OOS 4.0.3 (or just the firmware if you followed the guide).
weaponG said:
IHowever, everytime I try to install TWRP, it gets stuck on the TWRP splash screen. Then, I have to hold down the power button to power off, power back on, re-encounter the red dm-verity error and I am back into OxygenOS.
How can I get rid of the dm-verity error and get TWRP back on my phone?
Click to expand...
Click to collapse
TWRP Is already flashed on your phone
You just have to wait a while as oxygen os uses f2fs system and it takes time to boot into twrp
For the dm verity error you can follow the guide which is mentioned above
But as the error does not affect any functionality of Rom it should not be bothered with
Thank you all for your help. I did wait out the TWRP splash screen for about 20 minutes and it didn't seem to make any difference. The resolution was to download and install OOS 4.02 via adb sideload and then perform the following commands: fastboot oem disable_dm_verity, fastboot oem enable_dm_verity. The sideload of OOS 4.02, itself, did remove the dm-verity error. However, I wanted to be sure and performed the fastboot oem commands. (As speculated earlier in this post, fastboot oem enable_dm_verity and fastboot oem disable_dm_verity are known and working commands against OOS 4.02, but NOT against OOS 4.03.) I was then able to install TWRP and am now running a version of CM which has been modded by Sultan. This is a very stable ROM and is exactly what I was looking for. The issues which I had with LineageOS do not occur in Sultan's ROM.
I have my Bootloader Unlocked, OEM Unlock is selected in Developer options, USB Debugging enabled, latest drivers and version of the SDK installed. I am able to get into fastboot mode, but once I proceed to fastboot flash recovery twrp.img
it starts to work but then says FAILED (remote: unknown command)
I've tried every version of TWRP. I've tried rebooting PC, Phone, etc. All to no avail. Very frustrated after spending 3 hours trying to get this to work. Any suggestions would be appreciated in getting this to work properly. Thank you.
Once you are in fastboot, instead of flashing, do 'fastboot boot twrp(name of file).img' to load twrp on the phone. The phone will load twrp and boot into it. Prior to the previous step, you should download flashable twrp.zip and place on your sd card that now you can flash once you boot in recovery.
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that and if I unlock the bootloader will I be able to flash custom recovery like on a normal phone?
Treeager said:
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that
Click to expand...
Click to collapse
adb reboot bootloader
mvikrant97 said:
adb reboot bootloader
Click to expand...
Click to collapse
This only reboots the phone
Treeager said:
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that and if I unlock the bootloader will I be able to flash custom recovery like on a normal phone?
Click to expand...
Click to collapse
The fastest way to unlock your phone's bootloader is using mtk client.
You will find plenty of tutorials on youtube as well as XDA on how to use mtk client.
Please comment down here if you need any help.
UPDATE: So I unlocked the bootloader with mtk, and with this weird fastboot I can flash recoveries. But if I do "adb reboot fastboot", I can execute fastboot commands, but the recovery becomes the stock recovery wich is a little strange to me... Anyway, how to decrypt the storage in twrp? And also I am trying to install Pixel OS from here. I installed the pixel recovery too.