Database Develop

[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

[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

[Q] Possible Hard Brick. How can I fix it?

Dear XDA-Developers Forum,
I require your help fixing my HTC One M7.
When I tried to use an RUU to set it back to stock firmware the RUU.exe returned error 155. Maybe I did something wrong. I have some experience flashing different phones but I'm not a pro like most people here..
Anyway, the phone hung at the black screen with the HTC logo. At some point I managed to reconnect to the bootloader and Fastboot commands were still available. I tried using Fastboot to verify I had the correct RUU which to all appearance was the case. After trying to reboot to system the phone is stuck in a loop. It displays the CM logo from the ROM it had previously installed.
From here, I'm stuck. Power button does not work, combinations to go into bootloader don't work. The only thing that does work is holding power and vol+ and vol- at the same time. This makes the phone reboot (showing white HTC screen with green logo). After a few seconds I am however stuck with the CM logo.
Is there a way to fix this?
Some additional info on my device:
HBoot 1.55
Bootloader unlocked
S-ON (although that's strange cause I had it turned off before)
CM 10.2 installed
TWRP 2.8.5.0
I hope someone has a solution. Of course all drivers and software are up to date and I have backup of my relevent data. I fear that I will need to get a replacement since extensive Google-Search would not yield a solution so far. It could be I'm just not educated enough to understand.
Best regards
Nick

Little Update
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?

DNK83 said:
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU
You don't need to keep waiting for the battery to die, hold down the volume down button and the power button together, keep them held down, the captive lights on the bottom will flash about 15 times, when the phone goes off, let go of the power button only, the phone should now boot to the bootloader.
post your fastboot getvar all without imei and serial number please, anyone here needs more info about your phone before we can help and this will tell us all everything we need to know.

Hello,
thanks for your reply.
I have tried holding the power button and vol- together. Even after more than 30 seconds the phone does not react and keeps on showing the CM logo.
Sorry, for not providing more information. I would've posted the getvar info before but was not able to connect through fastboot.
Will do once the battery is charged enough for the next try.

After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s

DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
take the brackets off the all () the command is fastboot getvar all

DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.

C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

alray said:
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
Click to expand...
Click to collapse
The brackets are added because I'm tired and kinda angry.

DNK83 said:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
first of all I recommend you flash twrp 2.8.6.0 from here, it will make life easier for you: https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp, and create a very simple backup, just something like boot or cache.
now plug your phone into the computer, it should open on your computer as this version of twrp supports MTP, navigate to the TWRP backup folder on your phone and delete the backup file from the folder (just the backup file itself, none of the folders) it will be in TWRP/BACKUP/PHONE SERIAL NUMBER/DATE AND OTHER DIGITS/ delete the file in here and replace with the files in this zip (make sure you extract the zip first): https://www.androidfilehost.com/?fid=95897840722646676
now unplug your phone and restore the backup.

The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.

DNK83 said:
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
Click to expand...
Click to collapse
in that case, select wipe, and then format data button, type yes to confirm, when done, select reboot to recovery for change to take effect, it will say no OS installed, just ignore it, it will also ask you if you would like to install super SU, select do not install, when the phone boots back to recovery, try backup again.

Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.

DNK83 said:
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
Click to expand...
Click to collapse
make sure you are on the recovery main screen when you plug the phone into your computer, no sub menu's.
If it still doesn't appear on your computer, double check your device manager to make sure its showing in there correctly.

A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.

DNK83 said:
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
Click to expand...
Click to collapse
Strange, it should look like this pict below, I'm using a HTC One M8, with the latest TWRP, but its the same thing as yours, as I previously had the M7.
try uninstall, that driver and then manually install the correct driver.
check Question 2 here on how to manually force the driver: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.

DNK83 said:
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
Click to expand...
Click to collapse
yes, just right click that other driver and uninstall it, then reboot.
I just download HTC sync manager and install that for my drivers, then just uninstall HTC sync, you will see the driver package which comes with sync manager just above it, leave that one alone, never had a problem with it.

The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?

DNK83 said:
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
Click to expand...
Click to collapse
strange, ive never seen it appear like that.
ive attached my adb and fastboot files below if you want to use those, maybe yours came with the google nexus driver.

"Active cmdline overflow!"

Hi there, I must have flashed the wrong sense ROM. I am extremely noobish, so bare with me.
I tried following this amazing guide: http://forum.xda-developers.com/showthread.php?t=2739126 but have had no luck when it comes to flashing the recovery indicated.
"C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
error: cannot load 'twrp-recovery-2.7-m7-nobcb.img'"
It looks like I entered it right...
My phone will power on and function OK with data and text, but cannot make calls. Sometimes it'll reboot into hboot when I plug it into USB/AC. I have access to fastboot, but not adb, nor recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: `
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35...
(bootloader) imei: 3559...
(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: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time, XDA!

Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk

cyrusct82 said:
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes and it shows under "fastboot devices"

It's now managed to have gotten worse and will only boot into the spash screen, then Fastboot (not Hboot).
If I remove the sim card, it will boot up normally (unless it's plugged into USB/AC). If I insert the sim, or plug in the microUSB, it will shortly thereafter crash into fastboot.

1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted

nkk71 said:
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
Click to expand...
Click to collapse
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!

Enigmatic Fart said:
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Click to expand...
Click to collapse
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy

nkk71 said:
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
Click to expand...
Click to collapse
Cool man, I'll run through and try to flash it again in the meantime and edit this post with results.
Thanks again for your help! Peace!
EDIT: OK, I see what the issue was, but a new one popped up. So I was attempting to flash the recovery I placed in my phone's storage. I now have "TWRP.img" (latest TWRP) and "TWRPnbcb.img" (the no bcb one from that guide) in my adb folder (where fastboot is) on my PC and have attempted to flash both recoveries for S&Gs.
Here are the results:
"C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
HT35xxxxxx... fastboot
C:\adb>fastboot flash recovery TWRPnbcb.img
sending 'recovery' (11278 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
C:\adb>fastboot flash recovery TWRP.img
sending 'recovery' (12534 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s"

Last ditch bump! I don't want my phone retire in a junk drawer!

Enigmatic Fart said:
Last ditch bump! I don't want my phone retire in a junk drawer!
Click to expand...
Click to collapse
please post a "fastboot oem last_dmesg", after trying to flash something
@alray, might be able to decipher that
(sorry for the ping)

Help please. Phone started boot looping

Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James

The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.

jamesdf5 said:
Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James
Click to expand...
Click to collapse
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.
Click to expand...
Click to collapse
Hi,
Thanks for the reply
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know

donkeykong1 said:
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs
Click to expand...
Click to collapse
Thanks for replying. Yes i can get into bootloader

jamesdf5 said:
Thanks for replying. Yes i can get into bootloader
Click to expand...
Click to collapse
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions.
Click to expand...
Click to collapse
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
Click to expand...
Click to collapse
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
jamesdf5 said:
Hi,
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know
Click to expand...
Click to collapse
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.

alray said:
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.
Click to expand...
Click to collapse
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again

donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs
Click to expand...
Click to collapse
It does now i've unlocked it. yes

jamesdf5 said:
It does now i've unlocked it. yes
Click to expand...
Click to collapse
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs

donkeykong1 said:
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs
Click to expand...
Click to collapse
Okie dokie thanks
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

jamesdf5 said:
Okie dokie thanks
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs

donkeykong1 said:
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs
Click to expand...
Click to collapse
ok thank you :good:

jamesdf5 said:
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again
Click to expand...
Click to collapse
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
jamesdf5 said:
Okie dokie thanks
(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.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Click to expand...
Click to collapse
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
alray said:
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James

jamesdf5 said:
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James
Click to expand...
Click to collapse
PS definitely not recognised on my Windows 10. Won't see it at all.

jamesdf5 said:
PS definitely not recognised on my Windows 10. Won't see it at all.
Click to expand...
Click to collapse
Strange, keep using your w7 pc for now. Maybe a driver problem, or maybe you are using an usb 3.0 port instead of a 2.0?

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James

jamesdf5 said:
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James
Click to expand...
Click to collapse
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.

alray said:
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.
Click to expand...
Click to collapse
Oh dear. I have to confess i accidentally restarted the phone after i flashed it without erasing cache. :crying::crying: I then went back and flashed again and erased as you said in the instructions.
I have have tried the older version on twrp. No luck. I'm guessing i ballsed it up first time! Sorry