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!
I´m trying to install a custom ROM to get android 9 on my g6 h872. When trying to flash recovery.img to install TWRP, i get the error:
writing 'recovery'...
FAILED (remote: unknown command)
I tried with the "fastboot boot recovery.img" command but it won´t work either. Help would be much appreciated.
Are using adb command?
If yes it's not working
You can do it easy by
1- get temp root using su98.apk
2- use flashify to flash orange fox or other recovery img
3- reboot to recovery by using adb command "adb reboot recovery"
Dev4up said:
Are using adb command?
If yes it's not working
You can do it easy by
1- get temp root using su98.apk
2- use flashify to flash orange fox or other recovery img
3- reboot to recovery by using adb command "adb reboot recovery"
Click to expand...
Click to collapse
You can also do this :
4- install latest magisk
5- install any app for reboot to recovery from play store.
6- enjoy
This method work just in Oreo or nougat rom .
Use this tutorial https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518 tmo h872 fastboot flashing isn't working on this device
OK, This is embarrasing.
The phone is not MI 3, but MI A3.....
MiFlash solved the problem
Hi,
I accidentally tried to flash TWRP to the active partition (a) as "fastboot set_partition b" didn't work.
Now my phone is stuck in fastboot.
I tried flasing using the latest miflash and the ROM from here, but I get missmatch error.
I tried to flash using fastboot: system (returned OK), boot (returnedOK), recovery (returned No such partition) and cache (returned No such partition) but it didn't work.
I also tried booting to TWRP by "fastboot flash recovery twrp.img" and "fastboot reboot" but it reboots to fastboot.
I tried "fastboot boot twrp.img" and get "FAILED (remote: unknown command)"
it says:
downloading 'boot.img'...
OKAY [ 0.897s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.900s
Click to expand...
Click to collapse
I want to revive the phone if that is possible and if not at least recover my data.
Can anyone please help???
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
refresh5 said:
Hey folks,
has anyone already successfully rooted Android 13? If yes, is there an instruction available?
Thanks!
Click to expand...
Click to collapse
Just patch boot.img and flash it
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Adnan008 said:
Can we update firmware after root? If not where can we download full firmware? This is my first Sony phone so I don't know where to download full firmware and how to flash it
Click to expand...
Click to collapse
Xperiafirm on xda to download full fw and newflasher to flash it
King081 said:
Xperiafirm on xda to download full fw and newflasher to flash it
Click to expand...
Click to collapse
do we lose data when flashing firmware?
Adnan008 said:
do we lose data when flashing firmware?
Click to expand...
Click to collapse
You can choose using newflasher
King081 said:
Just patch boot.img and flash it
Click to expand...
Click to collapse
Can you tell me how?
zaxdamian said:
Can you tell me how?
Click to expand...
Click to collapse
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
King081 said:
Use unsin to get boot.img from stock file, then install magisk apk, use magisk to patch boot.img then flash in fastboot
Click to expand...
Click to collapse
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
zaxdamian said:
I have stock file but dont know which file unsin. When I try to instal twrp, "Download is not allowed on locked devices". How to unlock bootloader? Command from cmd dosen't work
Click to expand...
Click to collapse
I don't know what twrp you have, because we don't have one here and clearly your phones bootloader locked, this is about root and not twrp
Ok. I cant unlock bootloader, so how to get boot.img from stock file?
Unlock bootloader:
https://developer.sony.com/open-source/aosp-on-xperia-open-devices/get-started/unlock-bootloader
I tried it. Either I'm doing something wrong or it's not working
Everything works, I unlocked it myself, I just don't remember which command:
fastboot oem unlock
or
fastboot flash unlock
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
On comand fastboot flash unlock i have "fastboot: error: ANDROID_PRODUCT_OUT not set"
zaxdamian said:
fastboot devices ok
fastboot oem unlock 0xunlockcode "FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed"
fastboot oem unlock unlockcode the same
fastboot flash unlock "unknown partition 'unlock' fastboot: error: cannot determine image filename for 'unlock'"
I think the problem is with entering fastboot mode. When "phone is turned off and press and hold the Fastboot key Volume up* when you connect your phone to the computer" i have blue diode but in SDk no devices
Click to expand...
Click to collapse
Did you do that in fastboot or fastbootD
Fastboot D
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.