Database Develop

[Q] Bricked after flashing Insertcoin 4.4 ROM (ADB can't find device)

I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.

Caboose127 said:
I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.
Click to expand...
Click to collapse
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.

LibertyMarine said:
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.
Click to expand...
Click to collapse
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.

Caboose127 said:
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.
Click to expand...
Click to collapse
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
fastboot getvar all
Click to expand...
Click to collapse
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?

LibertyMarine said:
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?
Click to expand...
Click to collapse
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.

Caboose127 said:
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.
Click to expand...
Click to collapse
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe

have you tried re flashing a new recovery via fastboot?

LibertyMarine said:
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
Click to expand...
Click to collapse
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
I would flash a new recovery, but my computer doesn't seem to be recognizing my device. It does for a second during boot into recovery, but once the recovery crashes and the phone resets, the phone disappears from device manager. It doesn't show backup when I'm in FASTBOOT USB.
I'm going to try it on a coworkers computer.

Caboose127 said:
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
this is weird... try another computer. Try different drivers from here:
http://forum.xda-developers.com/showthread.php?t=2191279
TRY EVERYTHING GO GET THE COMPUTER RECOGNIZING YOUR HTC ONE
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
...lol this would be funny.. maybe his recovery partition is corrupt.. hmmm then we'd have to use different error handling strategies...

Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: *****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.

If you are still trying for your computer to recognize the adb device and still hasn't then just buy an USB OTG then put an USB to flash a rom from there.
http://www.androidapps4u.com/temp/screenshot_3-usb-otg-cable.jpg

Define crashed? TWRP 2.6.3.0 ? or CWM ? What happens in recovery mode?

Caboose127 said:
Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.
Click to expand...
Click to collapse
adb commands won't work while in fastboot mode/bootloader. fastboot needs to be used while in fastboot mode. While your in fastboot, try
fastboot erase cache
Then fastboot flash your recovery again (fastboot flash recovery nameofrecovery.img), and try to access recovery

Thanks for all of your help guys. I finally got it working.

For everyone else reference, mark your thread [SOLVED] and post a brief description how you fixed it..

Thanks guys for helping me out!

[Q] Boot looping

Please treat me as a total noob, my problem is this i installed the stock RUU Vodafone rom on my HTC One and everything went fine until i had a couple of phone updates ota first 2 installed and phone rebooted no problem on the 3rd system update the phone rebooted but this time on a boot loop where it would get as far as the HTC splash screen the continually reboot itself.
I have gone into recovery – hold power and Vol Down to go into recovery but when i do press the power button to go into recovery it just goes back to the boot loop i did have Clockworkmod installed on the phone but this seems to have stopped working.
I have tried to use fastboot and ADB but because my phone is looping it will not say on long enough to connect to the PC and run a command to wipe the cache.
My question mainly is there anything i can do to save my phone or should i just bin it.
Thanks

Dogsrus said:
Please treat me as a total noob, my problem is this i installed the stock RUU Vodafone rom on my HTC One and everything went fine until i had a couple of phone updates ota first 2 installed and phone rebooted no problem on the 3rd system update the phone rebooted but this time on a boot loop where it would get as far as the HTC splash screen the continually reboot itself.
I have gone into recovery – hold power and Vol Down to go into recovery but when i do press the power button to go into recovery it just goes back to the boot loop i did have Clockworkmod installed on the phone but this seems to have stopped working.
I have tried to use fastboot and ADB but because my phone is looping it will not say on long enough to connect to the PC and run a command to wipe the cache.
My question mainly is there anything i can do to save my phone or should i just bin it.
Thanks
Click to expand...
Click to collapse
You MUST use stock recovery for ota updates. Flash your stock recovery back, fastboot erase cache and try to update again.

alray said:
You MUST use stock recovery for ota updates. Flash your stock recovery back, fastboot erase cache and try to update again.
Click to expand...
Click to collapse
RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 which i believe was stock?
i can not work out how to flash back as i have no access to fastboot cmd as my phone wont connect to my pc no more

Dogsrus said:
RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4 which i believe was stock?
i can not work out how to flash back as i have no access to fastboot cmd as my phone wont connect to my pc no more
Click to expand...
Click to collapse
If you flashed clockworkmod recovery after the ruu, then you don't have stock recovery.
reboot the phone in bootloader mode, you should be able to do fastboot commands from there.
If you go in windows devices manager, is your phone listed?
and never use the 1.20.401.1 ruu, its a pre-release version. always use the 1.28.401 or the newer 4.19.401.9 ruu

alray said:
If you flashed clockworkmod recovery after the ruu, then you don't have stock recovery.
reboot the phone in bootloader mode, you should be able to do fastboot commands from there.
If you go in windows devices manager, is your phone listed?
and never use the 1.20.401.1 ruu, its a pre-release version. always use the 1.28.401 or the newer 4.19.401.9 ruu
Click to expand...
Click to collapse
no phone not listed as the pc is trying to install the drivers but the phone wont stay on long enough to install them

Dogsrus said:
no phone not listed as the pc is trying to install the drivers but the phone wont stay on long enough to install them
Click to expand...
Click to collapse
so you are saying that your phone is bootlooping even if its in bootloader mode?

alray said:
so you are saying that your phone is bootlooping even if its in bootloader mode?
Click to expand...
Click to collapse
in bootloader mode the pc shows it as Other Devices Android 1.0 (No drivers are installed for this device)

Dogsrus said:
in bootloader mode the pc shows it as Other Devices Android 1.0 (No drivers are installed for this device)
Click to expand...
Click to collapse
follow this guide:
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways​
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse

alray said:
follow this guide:
Click to expand...
Click to collapse
Thank you so far for the help i now have My HTC showing in device manager, can some please give me very simple instructions on what to do next, i have tried so many things over the last 3 days my brain has gone soft

Dogsrus said:
Thank you so far for the help i now have My HTC showing in device manager, can some please give me very simple instructions on what to do next, i have tried so many things over the last 3 days my brain has gone soft
Click to expand...
Click to collapse
please reboot your phone in bootloader mode and type:
Code:
fasboot getvar all
and post result here except IMEI and SERIALNO

alray said:
please reboot your phone in bootloader mode and type:
Code:
fasboot getvar all
and post result here except IMEI and SERIALNO
Click to expand...
Click to collapse
This is where i start getting lost, i have downloaded so many programs the last few days i dont even know which one to use to get the code

Dogsrus said:
This is where i start getting lost, i have downloaded so many programs the last few days i dont even know which one to use to get the code
Click to expand...
Click to collapse
open a command prompt from your fasboot/adb folder (shift + right click in blank space of that folder and select ''start a command prompt here'')
then the command prompt will open
type:
Code:
fastboot getvar all
should output something similar to this:

alray said:
open a command prompt from your fasboot/adb folder (shift + right click in blank space of that folder and select ''start a command prompt here'')
then the command prompt will open
type:
Code:
fastboot getvar all
should output something similar to this:
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
C:\adb>

Dogsrus said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
C:\adb>
Click to expand...
Click to collapse
ok so you said in post #1 you have flashed vodafone ruu but afaik, there is no ruu for that phone. And the ruu you are referring to in post #3 is not for vodafone but for international (unbranded) phone and will not work on your phone with S-ON.
try to ''fastboot erase cache'' and reboot the phone. If its still bootloop, the easiest solution is to flash twrp 2.6.3.3 recovery and flash a custom rom i.e arhd 53.

alray said:
ok so you said in post #1 you have flashed vodafone ruu but afaik, there is no ruu for that phone. And the ruu you are referring to in post #3 is not for vodafone but for international (unbranded) phone and will not work on your phone with S-ON.
try to ''fastboot erase cache'' and reboot the phone. If its still bootloop, the easiest solution is to flash twrp 2.6.3.3 recovery and flash a custom rom i.e arhd 53.
Click to expand...
Click to collapse
the 'fastboot erase cache` never worked so am i downloading twrp and arhd 53 now.
can someone explain how i load these onto my phone using the fastboot and ADB, i dont want to mess this up again, many thanks for all the help so far
i can load arhd 53 on to my usb stick and connect to phone via micro cable i really need to know how to get twrp on to the phone

Dogsrus said:
the 'fastboot erase cache` never worked so am i downloading twrp and arhd 53 now.
can someone explain how i load these onto my phone using the fastboot and ADB, i dont want to mess this up again, many thanks for all the help so far
Click to expand...
Click to collapse
Code:
fastboot flash recovery name_of_recovery_file.img
then boot twrp recovery and push the rom to your sdcard
Code:
adb push name_of_rom.zip /sdcard/
Wait a while for the rom to transfer
then select ''install'' and choose the rom. Swipe to flash.

alray said:
Code:
fastboot flash recovery name_of_recovery_file.img
then boot twrp recovery and push the rom to your sdcard
Code:
adb push name_of_rom.zip /sdcard/
Wait a while for the rom to transfer
then select ''install'' and choose the rom. Swipe to flash.
Click to expand...
Click to collapse
sort of getting there lol may be the zip file is corrupt but at least now i have recovery working , see image

Dogsrus said:
sort of getting there lol may be the zip file is corrupt but at least now i have recovery working , see image
Click to expand...
Click to collapse
MD5 check sum the rom and make sure it match. If you downloaded arhd 53 it should be
Code:
[B]DF9854F79C6E6928BEFD6EC43EC9F4A5[/B]

alray said:
MD5 check sum the rom and make sure it match. If you downloaded arhd 53 it should be
Code:
[B]DF9854F79C6E6928BEFD6EC43EC9F4A5[/B]
Click to expand...
Click to collapse
Codes do not match guess its another download but really appreciate your help alray

Found a download where MD5 check sum match will report back

[Q] HTC One Bootloop - Cannot unlock bootloader

Hi All,
My phone suddenly started doing a Bootloop, please notice that I haven't messed up with any custom ROMs, flashing, etc... the only thing that I may guess that happened here is that my phone got a little wet a couple of days ago. The screen won't came up so I dry it using a hairdryer and started working normally. Two days later I got an error that Foursquare app was failing and then I got into the Bootloop that I cannot get rid of....
I'm totally new with flashing phones, rooting, unlocking, etc... but I'm a developer, so, I can learn much easily.
I was reading some forums and solutions but I could not get it work.
Here are the details:
1- The phone is a HTC One M7
2- I'm able to enter to "Recovery mode" screen
3- If i scroll down to "Recovery" or "Factory Reset" the phone try to enter to those modes but after a few seconds of black screen I got an image with a phone with a red warning icon inside. So, I cannot enter to recovery nor do a factory reset
4- If I try to use "adb" commands looks like the bootloop is avoiding me to recognize the device. I tried "adb devices" several times while the phone is rebooting and I see the phone appearing in the list in the middle of the reboot but the status is "offline", then, it changed to "unauthorized" and then it disappears. I also tried "adb wait-for-device" but does not worked and sometimes it said that there is more than one device connected (if i tried adb devices again, appear my device a lot of times but always offline).
I also tried a .bat file to wait for the device and do a shell stop to be able to "freeze" where the phone is accessible, but did not worked neither.
I guess that I don't have debugging enable on my device and that is why i cannot use the adb commands of see the phone connected. I saw that adb will work even with debugging disabled in recovery, but like i mentioned before, i cannot enter to recovery.
5- I was able to enter to "fastboot mode" and my phone connected to USB. If i use fastboot devices, my device appears and looks fine.
6- I tried to unlock the bootloader using the htcdev.com. I followed the steps and looks simple, I don't think i messed something there. I was able to get the phone token, submit, get the Unlock_code.bin, flash the code using fastboot, I got the screen to select yes/no to unlock the bootloader, and at this point everything looks great. I selected Yes, and my phone reboot and still on bootloop (as expected), but If i enter again to recovery mode, the phone is still "*** LOCKED ***". I tried the process (get toke, submit, flash bin, etc) lot of times, but with no result, phone is still appears as Locked.
7- My idea on #6 was to flash the recovery img and try to make the recovery to work, but to be able to flash the recovery i need my bootloader to be unlocked. I tried anyways to flash the recovery but as expected if failed :
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.201s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.172s
8- I saw that there is another method to unlock the bootloader but is using adb, which on #4 i explained i cannot use.
Any idea? thoughts?
Thanks in advance,
Juan.

first USB debugging is only for when you are booted into a rom, it doesn't apply to recovery or bootloader.
Red triangle with exclamation mark is normal, that's the stock recovery.
next, you wont beable to adb devices whilst its bootlooping, that's why that's not working, adb is for in a rom or in recovery, fastboot commands are for when your in the bootloader
So reboot your phone to bootloader mode, this is where you saw the list with options to factory reset and reboot and recovery etc, this is the only thing you need to use for now, and only fastboot commands will work there, once plugged into your computer it should say on the screen "fastboot USB"
post your "fastboot getvar all" without quote marks

Seanie280672 said:
first USB debugging is only for when you are booted into a rom, it doesn't apply to recovery or bootloader.
Red triangle with exclamation mark is normal, that's the stock recovery.
next, you wont beable to adb devices whilst its bootlooping, that's why that's not working, adb is for in a rom or in recovery, fastboot commands are for when your in the bootloader
So reboot your phone to bootloader mode, this is where you saw the list with options to factory reset and reboot and recovery etc, this is the only thing you need to use for now, and only fastboot commands will work there, once plugged into your computer it should say on the screen "fastboot USB"
post your "fastboot getvar all" without quote marks
Click to expand...
Click to collapse
Hi Seanie, thanks for the quick response.
Here is the result of fastboot getvar all command:
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3451mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
J.

first thing is first, remove your serial number and imei from your output, its dangerous to post them.
also get your battery charged up to 50% or more,

Seanie280672 said:
first thing is first, remove your serial number and imei from your output, its dangerous to post them.
also get your battery charged up to 50% or more,
Click to expand...
Click to collapse
Ohh, just removed.
About battery, I cannot turn off my phone (even if trying from fastboot "power off" option), that is why i keep it with low battery so it power off when it's empty.
Do you thing battery level will change my results? If yes, after charging my batter, what i should do?
Thanks,
J.

htc butterfly a 9060 bootloop
I also have something that type of problem what u said ....
By missing i delete some some files from system/bin. And after that my phone boot loop ....nothing is working..... my bootloader is working but is locked .asb not working ..fastboot working ......i have recovery and boot.img.....can can one help ....plzz ..i m crying.....its really big mistake...:crying:

Htc butterfly s 9060 bootloop
garyplaton said:
Hi All,
My phone suddenly started doing a Bootloop, please notice that I haven't messed up with any custom ROMs, flashing, etc... the only thing that I may guess that happened here is that my phone got a little wet a couple of days ago. The screen won't came up so I dry it using a hairdryer and started working normally. Two days later I got an error that Foursquare app was failing and then I got into the Bootloop that I cannot get rid of....
I'm totally new with flashing phones, rooting, unlocking, etc... but I'm a developer, so, I can learn much easily.
I was reading some forums and solutions but I could not get it work.
Here are the details:
1- The phone is a HTC One M7
2- I'm able to enter to "Recovery mode" screen
3- If i scroll down to "Recovery" or "Factory Reset" the phone try to enter to those modes but after a few seconds of black screen I got an image with a phone with a red warning icon inside. So, I cannot enter to recovery nor do a factory reset
4- If I try to use "adb" commands looks like the bootloop is avoiding me to recognize the device. I tried "adb devices" several times while the phone is rebooting and I see the phone appearing in the list in the middle of the reboot but the status is "offline", then, it changed to "unauthorized" and then it disappears. I also tried "adb wait-for-device" but does not worked and sometimes it said that there is more than one device connected (if i tried adb devices again, appear my device a lot of times but always offline).
I also tried a .bat file to wait for the device and do a shell stop to be able to "freeze" where the phone is accessible, but did not worked neither.
I guess that I don't have debugging enable on my device and that is why i cannot use the adb commands of see the phone connected. I saw that adb will work even with debugging disabled in recovery, but like i mentioned before, i cannot enter to recovery.
5- I was able to enter to "fastboot mode" and my phone connected to USB. If i use fastboot devices, my device appears and looks fine.
6- I tried to unlock the bootloader using the htcdev.com. I followed the steps and looks simple, I don't think i messed something there. I was able to get the phone token, submit, get the Unlock_code.bin, flash the code using fastboot, I got the screen to select yes/no to unlock the bootloader, and at this point everything looks great. I selected Yes, and my phone reboot and still on bootloop (as expected), but If i enter again to recovery mode, the phone is still "*** LOCKED ***". I tried the process (get toke, submit, flash bin, etc) lot of times, but with no result, phone is still appears as Locked.
7- My idea on #6 was to flash the recovery img and try to make the recovery to work, but to be able to flash the recovery i need my bootloader to be unlocked. I tried anyways to flash the recovery but as expected if failed :
C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.201s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.172s
8- I saw that there is another method to unlock the bootloader but is using adb, which on #4 i explained i cannot use.
Any idea? thoughts?
Thanks in advance,
Juan.
Click to expand...
Click to collapse
i also have all these problem what u have with your phone..can u please tell is your problem solved or not if yes so please share with i m crying right now with this..please help

abby1996 said:
i also have all these problem what u have with your phone..can u please tell is your problem solved or not if yes so please share with i m crying right now with this..please help
Click to expand...
Click to collapse
Hi, after trying everything that I found in the forums, google, etc, without been able to work around it, I took my phone to two places where they fix cell phones but both of them told me "it can't be fixed". So, I lost my hope and currently i'm still keeping the broken phone but already got another one

Hello,
My htc butterfly s 9060 bootlooping with locked bootloader was solved.... I unlocked my bootloader by htcdev method... Its working... U also try this again and again bcoz its only method toh unlock the bootloader..... U also search all correct steps for this method....by searching on htc butterfly s unlocked bootloader threats.. And follow all steps... Bcoz i direct use htcdev site to unlock is not working... After that i used these steps for unlock bootloader...
May be help you
Abby
Sent from my HTC 9060 using XDA Free mobile app

I don't buy the 'can't be done' anymore after my issue for the past 24 hours. Your only way forward is to unlock the phone though. When I get back to the pc (using my now working phone!!) I'll put my notes up for you to work through.

I'm going to write this on the assumption that you followed the correct process to get your unlock token from HTC and you now have that.
BEFORE you do any of this, charge your phone. If you're having trouble powering it off, I found that having it connected via usb to my pc and then just holding the power off button or even the power off and volume down button (while it was on) did the trick. The LED should be lit red even if you don't have a visible indicator of what level the battery is at.
In the meantime:
#1 Go to your desktop on your pc. Set up a new folder and call it HTC.
#2 Into this folder extract everything within the attached zip. Don't put it into a further sub directory, just fill the HTC folder with the zip's contents. These are the ADB dll's and HTC's Fastboot programme. On top, I've included version 2.8.6.2 of TWRP.
#3 Put your Unlock_code.bin from the HTC email you received into this same folder.
-The contents of your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#3 When your phone has charged for at least an hour (make it two to be safe) get it onto the bootloader screen and onto the fastboot menu. You should still have the phone connected to the pc and the line should now say 'fastboot usb'
#4 Open up a cmd terminal. Assuming that you know how this is done, make sure that it is reading c:\<path>\HTC (where path is whatever it is where htc is. On mine it was c:\users\username\desktop\HTC
#5 type the following in: fastboot flash unlocktoken Unlock_code.bin (then wait to see what it says.. if successful then proceed to #6)
#6 type the following in: fastboot reboot -bootloader
Tell us how you get on.

abby1996 said:
Hello,
My htc butterfly s 9060 bootlooping with locked bootloader was solved.... I unlocked my bootloader by htcdev method... Its working... U also try this again and again bcoz its only method toh unlock the bootloader..... U also search all correct steps for this method....by searching on htc butterfly s unlocked bootloader threats.. And follow all steps... Bcoz i direct use htcdev site to unlock is not working... After that i used these steps for unlock bootloader...
May be help you
Abby
Click to expand...
Click to collapse
Make sure you don't flash files from this forum (M7), dowload files only from your device forum
Butterfly S forum here: http://forum.xda-developers.com/htc-butterfly-s

[SOLVED] Is there NO solution for my bootloader stuck HTC One with s-on?

So I think I've pretty much bricked my phone here. Where do I start?
I can only go into Bootloader. I have S-On and its relocked.
I can't S-off because I'm stuck in boot loader ....
I can't Unlock because I'm stuck in boot loader....
I can't even flash an RUU because its S-ON
The ONLY thing I can do is fastboot commands....Is there any way I can fastboot command to s-off? Any solutions? I was trying to make this stock to give the phone to my mom but I think I'm screwed

fifaman said:
So I think I've pretty much bricked my phone here. Where do I start?
I can only go into Bootloader. I have S-On and its relocked.
I can't S-off because I'm stuck in boot loader ....
I can't Unlock because I'm stuck in boot loader....
I can't even flash an RUU because its S-ON
The ONLY thing I can do is fastboot commands....Is there any way I can fastboot command to s-off? Any solutions? I was trying to make this stock to give the phone to my mom but I think I'm screwed
Click to expand...
Click to collapse
You can run a RUU with S-ON! The big question is there a RUU for your phone? Post a fastboot getvar all except for imei and serialno!

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main 4.19.401.11
(bootloader) version-misc: PUT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097
majmoz said:
You can run a RUU with S-ON! The big question is there a RUU for your phone? Post a fastboot getvar all except for imei and serialno!
Click to expand...
Click to collapse

fifaman said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main 4.19.401.11
(bootloader) version-misc: PUT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.097
Click to expand...
Click to collapse
Here is a RUU 4.11.401.11.zip that you can flash in fastboot. If you have an issue running the RUU then flash this firmware 4.11.401.11 first. These are the commands to flash both the RUU & firmware after booting into bootloader/FASTBOOT USB:
Code:
fastboot oem rebootRUU
Should see silver HTC logo
Code:
fastboot flash zip <name of file.zip>
The first time you issue this command merely sets up phone to receive the RUU or firmware, it will fail you have to issue the exact command again.
Code:
fastboot flash zip <name of file.zip>
The green status bar may not go all the way to 100%, if it is complete in the cmd window wait a few seconds then proceed.
Code:
fastboot reboot

majmoz said:
first. These are the commands to flash both the RUU & firmware after booting into bootloader/FASTBOOT USB:
Code:
fastboot oem rebootRUU
Should see silver HTC logo
Code:
fastboot flash zip <name of file.zip>
The first time you issue this command merely sets up phone to receive the RUU or firmware, it will fail you have to issue the exact command again.
Code:
fastboot flash zip <name of file.zip>
The green status bar may not go all the way to 100%, if it is complete in the cmd window wait a few seconds then proceed.
Code:
fastboot reboot
Click to expand...
Click to collapse
So I tried what you said (including the stock wipe firmware) but every time it says:
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 85.644s
I don't know why but I seem to keep getting this 12 signature verify fail....

fifaman said:
So I tried what you said (including the stock wipe firmware) but every time it says:
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 85.644s
I don't know why but I seem to keep getting this 12 signature verify fail....
Click to expand...
Click to collapse
Let try this version RUU 5.11.401.10.zip and firmware.

majmoz said:
Let try this version
Click to expand...
Click to collapse
This may be a dumb question but just to confirm, you want me to flash the firmware first, THEN the RUU right?

@majmoz
Hey so I tried the firmware, and it worked! Flashed it BUT when I tried your RUU file, it said the same 12 signature verify fail

fifaman said:
This may be a dumb question but just to confirm, you want me to flash the firmware first, THEN the RUU right?
Click to expand...
Click to collapse
They may not run since you are S-ON and I don't know if they are signed. I am trying to find a RUU.exe for you. Failing that, do you have a linux machine or MAC? If not, you can run linux off a USB FAQ Q5. Linux doesn't do all of the check that Win performs.

@majmoz
I have a Mac which would be much easier and I don't have Linux.... but I can create a USB Linux based on what I see from that link...
Which one should I use?

fifaman said:
@majmoz
I have a Mac which would be much easier and I don't have Linux.... but I can create a USB Linux based on what I see from that link...
Which one should I use?
Click to expand...
Click to collapse
Since you have a Mac use it. Just use the information from Q#3 in the guide to get the correct syntax.

@majmoz
hey so I tried it on my mac, did it all correctly.
But it comes down to this again:
(boot loader) signature checking...
FAILED (remote: 12 Signature verify fail)

fifaman said:
@majmoz
hey so I tried it on my mac, did it all correctly.
But it comes down to this again:
(boot loader) signature checking...
FAILED (remote: 12 Signature verify fail)
Click to expand...
Click to collapse
Since the firmware worked did you try to reboot the phone?
I'm not clear on what caused your issue? What rom was the phone on before you decided to go back to stock? Did you perform the unlock procedure the first time? If so, do you still have the Unlock_code.bin? If not, according to the procedure you need mostly fastboot to unlock your phone.

@majmoz
Yes I did reboot the phone using the command when I used the first firmware.
I was on Cyanogenmod 11 before. I did perform the unlock procedure the first time and YES I do still have the unlock_code.bin
Right now its on Relocked...
Is there any way I can use this unlock_code.bin to Unlock it? I tried on my mac and it said <error: cannot load 'token'> when I tried to <./fastboot flash unlock token Unlock_code.bin>
Sorry for giving you so much trouble...

@majmoz
So maybe I could be doing this wrong or perhaps the RUU file is the wrong one?
Because I'm able to flash the firmware fine and when I enter the reboot command....it reboots but doesn't go into boot loader, its just a black screen. Then I hold down the power and volume down and it goes into boot loader mode....And I repeat the process for the RUU you gave me and it says the same 12 signature verify fail.
What exactly is supposed to show when I flash the initial firmware? because my phone seems to turn off....and I have to hold down power and volume down for 15 seconds (the home and back button flashes a few times, then it goes into boot loader)

fifaman said:
@majmoz
Yes I did reboot the phone using the command when I used the first firmware.
I was on Cyanogenmod 11 before. I did perform the unlock procedure the first time and YES I do still have the unlock_code.bin
Right now its on Relocked...
Is there any way I can use this unlock_code.bin to Unlock it? I tried on my mac and it said <error: cannot load 'token'> when I tried to <./fastboot flash unlock token Unlock_code.bin>
Sorry for giving you so much trouble...
Click to expand...
Click to collapse
You might have to go through the procedure again since you changed your firmware.
So, I guess the phone is working but you want to go back to stock? If you can get it unlocked again, then you could install TWRP and flash this Guru Reset 5.11.401.10. This will get you back to stock, at the end it will ask if you want to root or not choose do not root and it will install the stock recovery. Then you could relock the bootloader and you are done!

@majmoz
OH MY GOD! I Unlocked it!! It worked holy hell you're amazing!
Now I've downloaded TWRP...How do I install this?
majmoz said:
You might have to go through the procedure again since you changed your firmware.
So, I guess the phone is working but you want to go back to stock? If you can get it unlocked again, then you could install TWRP and flash this Guru Reset 5.11.401.10. This will get you back to stock, at the end it will ask if you want to root or not choose do not root and it will install the stock recovery. Then you could relock the bootloader and you are done!
Click to expand...
Click to collapse

fifaman said:
@majmoz
So maybe I could be doing this wrong or perhaps the RUU file is the wrong one?
Because I'm able to flash the firmware fine and when I enter the reboot command....it reboots but doesn't go into boot loader, its just a black screen. Then I hold down the power and volume down and it goes into boot loader mode....And I repeat the process for the RUU you gave me and it says the same 12 signature verify fail.
What exactly is supposed to show when I flash the initial firmware? because my phone seems to turn off....and I have to hold down power and volume down for 15 seconds (the home and back button flashes a few times, then it goes into boot loader)
Click to expand...
Click to collapse
When you run the firmware and you use the fastboot reboot command the phone should reboot into the OS. If you use the fastboot reboot-bootloader command the phone should reboot into the bootloader.
Did the black screen have a red triangle in it?
Cyanogenmod 11 does a job on the phone and unfortunately it sometimes takes a RUU to correct it.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
fifaman said:
@majmoz
OH MY GOD! I Unlocked it!! It worked holy hell you're amazing!
Now I've downloaded TWRP...How do I install this?
Click to expand...
Click to collapse
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery <name of recovery.img>
fastboot erase cache
fastboot reboot-bootloader

@majmoz
Okay so you're amazing. I installed TWRP and it works, which gives me some relief. Now the only problem is, how do I get the Guru Reset on my phone? I can't seem to drop it in using android file transfer. Any solutions?

fifaman said:
@majmoz
Okay so you're amazing. I installed TWRP and it works, which gives me some relief. Now the only problem is, how do I get the Guru Reset on my phone? I can't seem to drop it in using android file transfer. Any solutions?
Click to expand...
Click to collapse
Here is the entire procedure you have already got most of it complete.
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

HTC M7 - Tried to root (Installed TWRP) but now phone won't boot

I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more

Syrup4 said:
I tried to use this guide to on htconeroot
Got to installing the zip for SuperSU v1.30
The phone rebooted but it said SuperSU failed
Tried to install Update Super SU v2.46
Phone no longer reboots. It shows the white HTC One loading screen but then just goes very dark grey forever.
I can still access the white menu that comes up when you hold volume down and power
Can also access the TWRP screen, however I tried factory reset there and it didn't change, it still won't boot.
Can't take out sd or battery as metal case
Anyway not sure if this is meant to be in the HTC M7 category, a TWRP category, Rooting one.
I'm not sure if it is because the guide was for 4.3 and on 5.02 or what.
I also held the power off button when it was doing some things which may have also caused it
I don't really care about it being rooted so much as having my phone back. The only reason I wanted it rooted was to install the camera change that is supposed to get rid of the green tint.
Anyway thank you for your time. And I appreciate any assistance that can be given. I have spent hours trying to figure it out, but I am still confused and figure I am likely to screw it up even more
Click to expand...
Click to collapse
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.

mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.

Syrup4 said:
Thank you very much for responding.
I am not sure what a nandroid backup is. I was following a guide.
I copied every file on phone to my computer via the file manager. And I used the command prompt and typed in "adb backup -apk -all -f backup.ab". I am not sure if that is the right kind.
I don't know how to post that output you asked for. I googled it, but it sounded like I needed to use my computer, and my computer no longer recognizes my phone due to it not booting. Or is that done in TWRP? Thank you again.
PS: htconeroot .com /htc-one-root/how-to-root-htc-one-windowsmaclinux/ is the guide I was following. Got up to install SU before it went bad. In case it helps. I can't properly link as I haven't made enough posts.
Click to expand...
Click to collapse
A nandroid backup is actually made with in twrp, read up on for future.
You obviously have adb installed since you used it for backup.
Put the phone in bootloader mode, restart holding down power and volume down. (have you not gone into twrp?) Then plug in usb and you should see "fastboot usb"
then from the adb folder type "fastboot getvar all"
Do some google searching there are dozens of articles regarding flashing htc one and using adb and fastboot commands phone bootloader and recovery .

Delete please, forgot to quote/ reply.

mb_guy said:
Since you have twrp installed, did you make a nandroid before installing the zip, if so restore it.
If you don't have a nandroid, please post output of fastboot getvar all.
Click to expand...
Click to collapse
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Removed
(bootloader) imei: Removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

Syrup4 said:
Hello, thanks again. is this what you were referring to posting?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.661.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4165mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 7.17.661.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.661.35 to 7.17.661.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.661.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1

alray said:
When posting a "fastboot getvar all" edit out your imei and serialno, don't post these 2 numbers on the forum (edit your above post and remove them).
You should be able to restore your phone by flashing the 7.17.631.7 RUU. You'll first need to edit your MISC partition to change your version-main from 7.17.631.35 to 6.17.631.7 then relock your bootloader and flash the RUU. Once done, you'll have to install 2 ota updates so your phone is back to the 7.17.631.35 version. When back on this version, re-unlock your bootloader, re-flash twrp and flash supersu version 2.46 (any version lower than that will not work on lollipop)
Instructions how to change your version-main at the end of post #2 of this thread (see "how to downgrade with s-on")
The RUU and instructions how to flash it in the same thread at post #1
Click to expand...
Click to collapse
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.

Syrup4 said:
Thank you very much. Both for the help fixing it, and letting me know to remove that info. I read the instructions however given that it won't boot. My computer won't recognize it to transfer the tool (Misc_Tool_1.00.zip) over, so I can install it in TWRP. I tried pushing it using a command with adb. But it said Device not found. Given it has no removable SD card I do not know how to move it. The manual one also required adb shell, which says device not found. I shall continue looking things up in the mean time.
Edit: Strangely HTC Sync manager pops up when it does fail to boot if I restart the phone. Given it is set to do so when the phone is plugged in. However it always says "no phone connected". As if it recognizes it for a second then stops.
Click to expand...
Click to collapse
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).

alray said:
First thing you want when using adb or fastboot commands is to make sure HTC Sync is not installed or your computer because it can interfere with adb/fastboot connectivity. So go ahead and uninstall it (not closing it, uninstall for real) don't uninstall the drivers btw.
Make sure you have the latest htc drivers installed, that you are using a good usb cable (preferably the original cable or any other cable already known to work with data transfer as opposed to usb cables that can only provide power). Make sure you are using a usb 2.0 port on your computer at the back of your tower (not using front ports neither an external usb hub). Finally, adb commands will only work when booted in twrp recovery, they will not work when in bootloader mode as opposed to fastboot commands which only works in bootloader.
If using the commands to change your version-main, better to post it here before so I can confirm its the correct one. A simple typo in this command could make the situation worse (i.e: corrupting your misc partition).
Click to expand...
Click to collapse
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Syrup4 said:
Hello, thank you again.
I uninstalled sync. I am using the original cable, and have now plugged it in to a USB 2.0 port on the back.
I also tried to use the commands while the phone is on the TWRP screen. The one with a grey background and big touch buttons with blue on them that say "Install" "Wipe" "Backup" etc.
But it still won't recognize my device. I can type in ADB to get a list of commands.
But when I try to push anything, it says "error: device not found"
I tried the command "adb get-serialno" to see if other commands worked but it said "unknown".
Edit: Got it to show up as a device when in Fastboot USB. However it won't show up as a drive in mycomputer. ADB won't recognize it in either that mode or on TWRP. And once I access TWRP, it changes to android phone" as shown in the second pic.
Click to expand...
Click to collapse
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.

mb_guy said:
It looks to me this is working from your second picture.
Click to expand...
Click to collapse
same. Maybe re-installing the latest drivers version wouldn't hurt...

alray said:
same. Maybe re-installing the latest drivers version wouldn't hurt...
Click to expand...
Click to collapse
mb_guy said:
When you're in TWRP are you sure you don't see the device as a disk drive, the newer versions of twrp support mtp which allows this. You should be able just to copy paste from you PC to the device. It looks to me this is working from your second picture.
Click to expand...
Click to collapse
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0

Syrup4 said:
Thanks once again both of you. But even though it seems like it should be listed. It is not. And if I right click on the device that appears, it is greyed out.
Which drivers? HTC ones? Android ones? or the Universal ADB (Android Debug Bridge) Driver for Windows.? I think I am getting confused between uninstalling and installing so many drivers, as to which overwrite.
Thanks again
Edit: It is TWRP v2.6.3.0
Click to expand...
Click to collapse
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck

alray said:
The HTC drivers, not the universal ones.
2.6.3.0 is to old and will cause problem. Once your drivers problem is fixed, update your twrp recovery before going any further (at least 2.6.3.3 or much newer if you want MTP support)
Ill be back in a few hours good luck
Click to expand...
Click to collapse
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day

Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.

Syrup4 said:
Thank you again.
I'm not sure how to update twrp.
However I tried to use a driver remover, then download and install new htc drivers, and nothing seems to have changed.
I will try and go over that video guide I was following before and see if there was something wrong in it compared to others once I get up (7:00am here and I haven't slept yet), but I thought I would update the situation before then.
Have a good day
Click to expand...
Click to collapse
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/

mb_guy said:
I have good luck with these adb tools. Also did you reboot pc after removing old drivers, sometime things just magically work after.
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP is updated from fastboot (fastboot flash recovery nameofrecovery.img)
https://dl.twrp.me/m7/
Click to expand...
Click to collapse
alray said:
Is fastboot connectivity working? (boot in bootloader mode and use "fastboot device" command to see if your phone is detected) Or is it only adb not working when in twrp?
You can update twrp using fastboot commands when in bootloader mode:
fastboot flash recovery file_name.img
fastboot erase cache
fastboot reboot-bootloader
(replace "file_name.img" by the file name of the recovery you want to flash.
Click to expand...
Click to collapse
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:

Syrup4 said:
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Click to expand...
Click to collapse
The tool Ive made will indeed hang if used with recent twrp version, sorry i forgot to mention that. So yes flash the 2.6.3.3 version and you should be able to use it without any problem. MTP isn't supported in 2.6.3.3 but you should be able to use "adb push" commands to transfer files, anyway I don't think you'll need any other file for now. Just change your version-main then relock your bootloader and flash the ruu.

Syrup4 said:
THANK YOU.
There has been progress.
So I installed the new TWRP posted, version 2.8.7.0-m7.
At first it said signature checking failed, so I booted the token thing from HTCDev again.
It then allowed me to install the new TWRP.
When the new TWRP was installed it came up with a screen with errors in red. "Can't write to Cache" or something.
I was going to write them down but it restarted itself then got stuck.
However once I turned the phone off and on again then went into recovery the new version allowed "MTP Device" to be recognized as a drive on my computer and I was able to copy over Misc_Tool_1.00.zip.
It still won't boot though. Anyway then I was re-reading the steps to use the Misc Tool and it said I should be using twrp 2.6.3.3 as newer versions hang.
So would the next step to be to reflash an older TWRP like I did the new one?
Then install Misc_Tool.zip and follow the other instructions that went along with it in that guide posted on the last page?
Are there any other things I should copy onto the phone first in case the older TWRP stops the drive from showing up on my computer again?
I just thought I would double check before proceeding so that I do not make a bigger mess of it.
Thank you both again for your time:good:
Click to expand...
Click to collapse
First I would download the ruu suggested by Alray to your computer (if you haven't already) have it in the adb folder
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
7.17.661.7 ruu
Then
Just flash the older twrp like you did the installed version
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot-bootloader
then run the misc tool and change cid
Then
then flash the ruu (it will replace twrp and rom with stock versions)
use the "how to flash" instructions on the first page of ruu download page.
Note: you MUST use htc_fastboot. Download it and place in the adb folder.
phone will reboot and then continue when flashing the ruu, don't rush, will take 10-15 min