Database Develop

[Q] HTC One bricked HELP

hi,
yesterday i was trying to install a rom, when some errors occured leading to the recovery being wiped and me being left with just a bootloader.
since, i have tried to install a recovery with fastboot, but the phone just loads and then restarts straight away. i have tried to do an RUU, but i cant find the right one. I dont know what to do, i cannot boot my phone into recovery. These are the details that fastboot is giving me:
HBOOT- 1.55.0000
RADIO:- 4a.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1.
The phone is from the UK and is on O2. i have tried the HTC1guru RUU which is UK O2 but it gives me error 131(the wrong RUU).
Please can i have some help?????
cheers

yeah i know
robbiewhone said:
hi,
yesterday i was trying to install a rom, when some errors occured leading to the recovery being wiped and me being left with just a bootloader.
since, i have tried to install a recovery with fastboot, but the phone just loads and then restarts straight away. i have tried to do an RUU, but i cant find the right one. I dont know what to do, i cannot boot my phone into recovery. These are the details that fastboot is giving me:
HBOOT- 1.55.0000
RADIO:- 4a.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1.
The phone is from the UK and is on O2. i have tried the HTC1guru RUU which is UK O2 but it gives me error 131(the wrong RUU).
Please can i have some help?????
cheers
Click to expand...
Click to collapse
I have kind of the same problem. When i try to put it in recovery it reboots into recovery an then really fast it reboots fast into boot logo. I have tried every option on htc one tool kit, tried to do a RUU, tried to do flash a new rom manually even changing from cwm to twrp didn't work. any help?
Phone is:
Unlocked
Tampered
S-on
Hboot-1.44.0000
Radio-4A.14.3250.13
Open DSP-v26.120.274.0202

robbiewhone said:
hi,
yesterday i was trying to install a rom, when some errors occured leading to the recovery being wiped and me being left with just a bootloader.
since, i have tried to install a recovery with fastboot, but the phone just loads and then restarts straight away. i have tried to do an RUU, but i cant find the right one. I dont know what to do, i cannot boot my phone into recovery. These are the details that fastboot is giving me:
HBOOT- 1.55.0000
RADIO:- 4a.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1.
The phone is from the UK and is on O2. i have tried the HTC1guru RUU which is UK O2 but it gives me error 131(the wrong RUU).
Please can i have some help?????
cheers
Click to expand...
Click to collapse
Can you post a fastboot getvar all ( delete IMEI and S/N)

Zenosx said:
I have kind of the same problem. When i try to put it in recovery it reboots into recovery an then really fast it reboots fast into boot logo. I have tried every option on htc one tool kit, tried to do a RUU, tried to do flash a new rom manually even changing from cwm to twrp didn't work. any help?
Phone is:
Unlocked
Tampered
S-on
Hboot-1.44.0000
Radio-4A.14.3250.13
Open DSP-v26.120.274.0202
Click to expand...
Click to collapse
not sure you have the same problem as the OP, your problem should be solved by a "fastboot erase cache"
(assuming the recovery you flashed isn't a bad download, did you check MD5?)
robbiewhone said:
hi,
yesterday i was trying to install a rom, when some errors occured leading to the recovery being wiped and me being left with just a bootloader.
since, i have tried to install a recovery with fastboot, but the phone just loads and then restarts straight away. i have tried to do an RUU, but i cant find the right one. I dont know what to do, i cannot boot my phone into recovery. These are the details that fastboot is giving me:
HBOOT- 1.55.0000
RADIO:- 4a.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1.
The phone is from the UK and is on O2. i have tried the HTC1guru RUU which is UK O2 but it gives me error 131(the wrong RUU).
Please can i have some help?????
cheers
Click to expand...
Click to collapse
there is no RUU for O2... what exactly were you flashing, what errors? please more details (with links), and as mentioned above, a "fastboot getvar all" (excluding IMEI and s/n)

733 evloopr
well is there an RUU i can use? i really dont know what to do, i have now got access to a recovery but i cant seem to install any roms through adb sideloading. i think it might be because there isnt a file system in place to install it to?

(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.401.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: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4328mV
(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!

robbiewhone said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
all: Done!
Click to expand...
Click to collapse
well you don't have an O2 branded phone, you may be with O2, but your phone is international unbranded.
you may want to consider S-Off before upgrading to 4.xx
but in either case: get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then you'll have custom recovery, and can install any ROM you like

Do not try to S-Off
considering that the device is currently "bricked" S-Off is the LAST thing you want to do, as it prevents you from ACTUALLY bricking your phone to the point of no return. However, as long as the OP can get into fastboot, since aparently only the bootloader is available, you should be able to flash a custom recovery, like TWRP or CWM. I very nearly bricked my One from a similar situation. Also, is your bootloader unlocked? I assume it is since you were trying to flash a non-stock ROM

Can now get into recovery, and am trying to install roms through adb. Ive tried many different roms, but they all come up with errors saying that it cannot mount ... Different partions (data, etc). I cannot adb push any roms into the sdcard either due to more errors. Cheers

robbiewhone said:
Can now get into recovery, and am trying to install roms through adb. Ive tried many different roms, but they all come up with errors saying that it cannot mount ... Different partions (data, etc). I cannot adb push any roms into the sdcard either due to more errors. Cheers
Click to expand...
Click to collapse
Now am getting erro "E:error in /tmp/update.zip
Imstallation abortedt"

Bump.. Anyone??

robbiewhone said:
Can now get into recovery, and am trying to install roms through adb. Ive tried many different roms, but they all come up with errors saying that it cannot mount ... Different partions (data, etc). I cannot adb push any roms into the sdcard either due to more errors. Cheers
Click to expand...
Click to collapse
robbiewhone said:
Now am getting erro "E:error in /tmp/update.zip
Imstallation abortedt"
Click to expand...
Click to collapse
can you be more specific which partition TWRP is unable to mount? because "unable to mount /cache...." is perfectly normal.
on the other hand "unable to mount /data" is not so good (could be a corrupt partition or a hardware problem), you'll have to select "Format data" in TWRP's wipe section.
not knowing what you flashed, it's hard to guess what's wrong.
you could try running "e2fsck -n -f -v /dev/block/mmcblk0p37" in an adb shell to see if you have a corrupt data partition. Here's an example of what a corrupt data partition could look like: http://forum.xda-developers.com/showthread.php?t=2512105

nkk71 said:
can you be more specific which partition TWRP is unable to mount? because "unable to mount /cache...." is perfectly normal.
on the other hand "unable to mount /data" is not so good (could be a corrupt partition or a hardware problem), you'll have to select "Format data" in TWRP's wipe section.
not knowing what you flashed, it's hard to guess what's wrong.
you could try running "e2fsck -n -f -v /dev/block/mmcblk0p37" in an adb shell to see if you have a corrupt data partition. Here's an example of what a corrupt data partition could look like: http://forum.xda-developers.com/showthread.php?t=2512105
Click to expand...
Click to collapse
{
"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"
}
this is the error i got after trying to adb install the guru reset M7 3.62.401.1.zip in particular, however this same error occurs with some other roms also.

robbiewhone said:
View attachment 2660575 this is the error i got after trying to adb install the guru reset M7 3.62.401.1.zip in particular, however this same error occurs with some other roms also.
Click to expand...
Click to collapse
1- you're recovery is seriously outdated
2- try adb push instead:
adb push <name of rom>.zip /sdcard/ <- this will take about 5 to 6 minutes not showing any progress, until it finishes
3- are you sure the download isn't corrupt? have you checked MD5

Ok im starting agin.
Updated recovery, downloading a new rom (insertcoin) and making sure the md5s match.
Does adb sideload have a size limit??

robbiewhone said:
Ok im starting agin.
Updated recovery, downloading a new rom (insertcoin) and making sure the md5s match.
Does adb sideload have a size limit??
Click to expand...
Click to collapse
i guess everything has a limit, but all the ROMs are being sideloaded just fine. I personally prefer adb push in these situations, as i can check md5 after it's on the phone, for example
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s)
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM

YEEEEEEESSSS
fixed it

robbiewhone said:
YEEEEEEESSSS
after 72 hours of trying, my phone is now fixed! What a relief thanks everyone!!
Ended up reinstalling windows 7 on my pc and first time with insert coin adb sideload and it works!!
Woo
Click to expand...
Click to collapse
Congrats mate, please edit main thread title to include [SOLVED]
and btw, it's always polite to press the thanks button when a post is useful

[Q] Potential Bricked Device?

Hi, I have an issue as well. It appears my M7 is bricked.
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause. However, I cannot make it S-OFF as adb is not functioning correctly, I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Attempted to factory reset in CWM. Wiped all caches. Attempted to re-flash ROM. Attempted to fastboot oem lock, but still no change.
Please assist if at all possible. Can contact me on Skype as well. Fastboot details are below...
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36AW910839
(bootloader) imei: 3544xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4061mV
(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
Many thanks!

timex321321 said:
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause.
Click to expand...
Click to collapse
You must be S-OFF to flash ARHD GPE edition otherwise it will bootloop like its doing now.
However, I cannot make it S-OFF as adb is not functioning correctly
Click to expand...
Click to collapse
ADB is only working from a booted rom or from a custom recovery
I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Click to expand...
Click to collapse
Of course, ADB debugging is set to off by default so if you ahve flashed a rom, it will be off unless you turn it on from the dev option menu. Anyway USB debug is only to use ADB when booted in the OS. You can still use ADB from custom recovery even if USB debug is turned off.
Attempted to factory reset in CWM. Wiped all caches. Attempted to re-flash ROM.
Click to expand...
Click to collapse
Will not work unless you s-off the phone first
Attempted to fastboot oem lock, but still no change.
Click to expand...
Click to collapse
Why have you re-locked the bootloader on a bootlooping phone? unlock it again...
Please assist if at all possible. Can contact me on Skype as well. Fastboot details are below...
Click to expand...
Click to collapse
You'll need to flash a rom that doesn't require S-OFF (basically all roms except GPE). Then if you still want to use a GPE rom, achieve S-OFF on a Sense rom (ARHD 81 for example) and flash your GPE rom after.
If you are gonna flash a Sense rom (ARHD 81), get rid of CWM and flash TWRP 2.6.3.3.

timex321321 said:
Hi, I have an issue as well. It appears my M7 is bricked.
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause. However, I cannot make it S-OFF as adb is not functioning correctly, I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Many thanks!
Click to expand...
Click to collapse
According to the OP:
Android Revolution HD 6.1 Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
You need TRWP 2.6.3.3 custom recovery!​
Flash TWRP 2.6.3.3
Install AHRD 81.0
If you want to flash GPe ROM, then obtain S-OFF!
ADB only needs USB Debugging when in the OS; it works just fine in Recovery Mode without USB Debugging. You can use alray's method to push the ROM to your phone:
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

I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?

timex321321 said:
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
Click to expand...
Click to collapse
See my post #3 above yours!

timex321321 said:
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
Click to expand...
Click to collapse
read the first post. Particularly what said about ADB or at least take the time to read the instructions Majmoz just posted...

Flash twrp 2.6.3.3, boot into it and then use adb push or adb sideload commands to push or install a ROM.

Thanks for the information. I re-unlocked, and flashed TWRP. When trying to push firewater for S-OFF it just hangs. The good news is that the device is now being recognized when doing adb devices. Any ideas?

timex321321 said:
Thanks for the information. I re-unlocked, and flashed TWRP. When trying to push firewater for S-OFF it just hangs. The good news is that the device is now being recognized when doing adb devices. Any ideas?
Click to expand...
Click to collapse
You need a working ROM on your phone for firewater to work. Push ARHD 81.0 first and boot into it. After you know it is working then try firewater!

majmoz said:
You need a working ROM on your phone for firewater to work. Push ARHD 81.0 first and boot into it. After you know it is working then try firewater!
Click to expand...
Click to collapse
Doesn't that ROM require S-OFF? Hence why I am trying to install Firewater.

timex321321 said:
Doesn't that ROM require S-OFF? Hence why I am trying to install Firewater.
Click to expand...
Click to collapse
ARHD 81.0 requires S-ON and an unlocked bootloader. You really need to read the OP:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock

majmoz said:
ARHD 81.0 requires S-ON and an unlocked bootloader. You really need to read the OP:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
Click to expand...
Click to collapse
Even on base 4.4.2 still go to ARHD 81.0? Or will I have to upgrade my base?

timex321321 said:
Even on base 4.4.2 still go to ARHD 81.0? Or will I have to upgrade my base?
Click to expand...
Click to collapse
You will be alright with your current base.

Big thanks to all the posters here. Issue has been solved successfully with your help! :good::good::good:

[Q] ADB can't find phone

So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44) as that is needed to update the firmware however it cannot connect to my phone either (same adb problem)
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables. I've tried uninstalling and reinstalled different HTC drivers, I also tried installing the google usb drivers.
I need helps

Cofffey said:
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in
Click to expand...
Click to collapse
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
To achieve s-off on hboot 1.44 use Revone
as that is needed to update the firmware
Click to expand...
Click to collapse
S-OFF is only needed if you flash a custom firmware.
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables.
Click to expand...
Click to collapse
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps[/QUOTE]

alray said:
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
To achieve s-off on hboot 1.44 use Revone
S-OFF is only needed if you flash a custom firmware.
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps
Click to expand...
Click to collapse
[/QUOTE]
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(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: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(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.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive

Cofffey said:
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(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: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(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.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Click to expand...
Click to collapse
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.

alray said:
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
Click to expand...
Click to collapse
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?

Cofffey said:
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Click to expand...
Click to collapse
you are s-off now?

alray said:
you are s-off now?
Click to expand...
Click to collapse
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)

Cofffey said:
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Click to expand...
Click to collapse
Change your CID to GOOGL001:
boot in bootlaoder / fastboot usb mode
using fastboot enter these commands:
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
Then confirm your cid is now GOOGL001:
Code:
fastboot oem readcid
output must be "GOOGL001"
reboot in ruu mode:
Code:
fastboot oem rebootRUU
flash this firmware, not the one you have linked above:
Code:
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot reboot-bootloader
then reflash twrp:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery, push the GPE rom to your phone and flash it. Reboot and your phone should boot in the 5.1 rom (first boot can take up to 10-15 mins, will be stuck at htc splash screen)
Dont forget to backup your important files before, the firmware flash will wipe your phone.

alray said:
Wait, I'll make some modification to the firmware so it can be flashed on your phone and I'll send it to you in a few minutes.
Click to expand...
Click to collapse
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?

Cofffey said:
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Click to expand...
Click to collapse
see edited post above. (#8)

alray said:
see edited post above. (#8)
Click to expand...
Click to collapse
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?

Cofffey said:
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Click to expand...
Click to collapse
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)

alray said:
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
Click to expand...
Click to collapse
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?

Cofffey said:
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Click to expand...
Click to collapse
If you need some of elementalX features then yes flash it, you can always revert back to the previous kernel that comes with the rom by extracting it from the rom.zip and flashing it using fastboot:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
ElementalX kernel must be flashed in recovery.

[Q] hboot 1.44.00 and can't move forward nor backwards

Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...

From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.

dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat

OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:

Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery

Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk

Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!

Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk

Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^

Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk

HELP !! HTC ONE M7 Bricked, with Recovery

hello guys, i got htc one m7, today, i rooted the phone and installed the twrp recovery, then rebooted to system and was working fine until i installed the modified rom "NuSenSeven", it successfully installed the rom but when i restarted the phone it stuck on boot animation and then rebooted and entered the recovery, i tried to wipe cache, data, factory reset, reboot, it still didn't worked, i installed the rom again with the different settings, and it still isn't working and unfortunately when i connect phone to computer, it cannot be detected. i have 2 laptops and it was working on both of them before it got stuck. Can anyone help me to fix it?
Thanks in advance.

TAT1SHA said:
hello guys, i got htc one m7, today, i rooted the phone and installed the twrp recovery, then rebooted to system and was working fine until i installed the modified rom "NuSenSeven", it successfully installed the rom but when i restarted the phone it stuck on boot animation and then rebooted and entered the recovery, i tried to wipe cache, data, factory reset, reboot, it still didn't worked, i installed the rom again with the different settings, and it still isn't working and unfortunately when i connect phone to computer, it cannot be detected. i have 2 laptops and it was working on both of them before it got stuck. Can anyone help me to fix it?
Thanks in advance.
Click to expand...
Click to collapse
What recovery version do you have?

donkeykong1 said:
What recovery version do you have?
Click to expand...
Click to collapse
I used the one from all in-one toolkit, i have no idea what version it is. also i tried to connect otb but it doesnt lets me use the otg neither. I wish it had a sd-card slot, it would escalate it easily.

TAT1SHA said:
I used the one from all in-one toolkit, i have no idea what version it is. also i tried to connect otb but it doesnt lets me use the otg neither. I wish it had a sd-card slot, it would escalate it easily.
Click to expand...
Click to collapse
Go into recovery and at the top of the screen is version number

donkeykong1 said:
Go into recovery and at the top of the screen is version number
Click to expand...
Click to collapse
TWRP v2.7.1.0a

TAT1SHA said:
TWRP v2.7.1.0a
Click to expand...
Click to collapse
I think your recovery is old. Find a newer version for your phone and flash it via recovery. You are on T-mobile, right?

Almost like something happens.
With HTC PN07200 (searching the model is a HTC ONE M7). I wanted to put a different rom.
The equipe was with the Bootloader "Locked", "S-Off" and "1111 user" (by what I read is superuser).
With the tools unlock "One_All-In-One_Kit_v3.1" or other downloadable for this model ...
Since fastboot command console and unlockcode .... I got to the "Unlocked" STEP 1 OK !!!
As recovery was already the "TWRP 2.5.0.0" try putting seven different ROMs without success.
Android_Revolution_HD-One_84.0.zip
Android_Revolution_HD-One_92.0_4a9d05.zip
Guru_Reset_M7_3.22.1540.1.zip
HTC_One_-_MaximusHD_53.0.0.zip
NuSenSeveN-LP-m7-gsm_v4.02_050715.zip
One_M7_7.15.401.1_stock_system_dump.zip
Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
The installation within TWRP is done without problems, you do not give error messages. But when asked reboot was presented with all of the 3 problem I describe them ...
or catch, white screen with HTC logo with a small and short vibration, black screen 3 seconds and again the white screen with HTC logo with a small and short vibration (bootloop)
or white screen with HTC logo with a small and short vibration and screen goes black.
or log in directly and fast recovery.
I tried without success to achieve other recovery programs from loading them into recovery Fastboot (fastboot flash recovery /// xxx.img fastboot erase cache)
TWRP 2.5.0.0.img
TWRP 2.7.0.0.img
TWRP 2.8.7.0.img
OpenRecovery-TWRP-2.5.0.0-m7wls.img
OpenRecovery-TWRP-2.7.0.0-m7.img
This team does not have external SD card, so did everything from internal memory, and also tried to OTG cable pendrive, without success.

donkeykong1 said:
I think your recovery is old. Find a newer version for your phone and flash it via recovery. You are on T-mobile, right?
Click to expand...
Click to collapse
I cant connect the phone to pc, its undetectable on all 3 laptops i got, i downloaded and installed about 3 different HTC drivers but it still isn't detected, i have bootloader unlocked and cid 1111, and S-off just in case if you might need to know that too

slash22toly said:
Almost like something happens.
With HTC PN07200 (searching the model is a HTC ONE M7)
Click to expand...
Click to collapse
PN0720000 is a Sprint CDMA HTC One.
I wanted to put a different rom.
Click to expand...
Click to collapse
So you need to use roms that are compatible with the Sprint HTC One (CDMA)
The equipe was with the Bootloader "Locked", "S-Off" and "1111 user" (by what I read is superuser).
Click to expand...
Click to collapse
11111111 is SuperCID not SuperUser, these are 2 different things. SuperCID allows the phone to bypass the CID check when flashing a RUU that was not made for your phone. Pretty useless for the Sprint M7 imo since you can only flash Sprint RUU because others ruu are not compatible with Sprint HTC one but anyway its ok to have superCID, you can keep it like that.
With the tools unlock "One_All-In-One_Kit_v3.1" or other downloadable for this model ...
Since fastboot command console and unlockcode .... I got to the "Unlocked" STEP 1 OK !!!
Click to expand...
Click to collapse
You might to use adb and fastboot directly from a command window using the latest android sdk tools. These toolkits are not up-to-date and not ideal when having issues. The other major issue with this toolkit is that its for the GSM M7 not for the Sprint variant.
As recovery was already the "TWRP 2.5.0.0" try putting seven different ROMs without success.
Android_Revolution_HD-One_84.0.zip ---> Its a rom for GSM htc one M7 (M7_UL or M7_U). You have a sprint M7 (M7WLS)
Android_Revolution_HD-One_92.0_4a9d05.zip ---> Its a rom for GSM htc one M7 (M7_UL or M7_U). You have a sprint M7 (M7WLS)
Guru_Reset_M7_3.22.1540.1.zip ---> Its a rom for GSM htc one M7 Developer edition PN0712000 not PN0720000
HTC_One_-_MaximusHD_53.0.0.zip ---> For GSM
NuSenSeveN-LP-m7-gsm_v4.02_050715.zip ---> For GSM
One_M7_7.15.401.1_stock_system_dump.zip ---> For GSM
Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip ---> Its an RUU for Sprint HTC one. RUU are not flashed using custom recovery, its flashed using fastboot.
Click to expand...
Click to collapse
The installation within TWRP is done without problems, you do not give error messages. But when asked reboot was presented with all of the 3 problem I describe them ...
or catch, white screen with HTC logo with a small and short vibration, black screen 3 seconds and again the white screen with HTC logo with a small and short vibration (bootloop)
or white screen with HTC logo with a small and short vibration and screen goes black.
or log in directly and fast recovery.
Click to expand...
Click to collapse
All these errors are caused by flashing a GSM rom on a CDMA phone.
I tried without success to achieve other recovery programs from loading them into recovery Fastboot (fastboot flash recovery /// xxx.img fastboot erase cache)
TWRP 2.5.0.0.img
TWRP 2.7.0.0.img
TWRP 2.8.7.0.img
OpenRecovery-TWRP-2.5.0.0-m7wls.img
OpenRecovery-TWRP-2.7.0.0-m7.img
Click to expand...
Click to collapse
You can only flash recoveries that are compatible with Sprint HTC One M7, in that above list, only that one ending with "m7wls.img" should work. To flash a recovery you have to use:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Better to post the output of "fastboot getvar all" so we can know everything about your phone, stop the confusion and direct you to a rom/recovery and instructions that will work with your phone. When posting the output of "fastboot getvar all", censor your IMEI, MEID and SERIALNO, you don't want to post these values on the forums. Other values will help determining what you can flash and how.

alray said:
PN0720000 is a Sprint CDMA HTC One.
So you need to use roms that are compatible with the Sprint HTC One (CDMA)
Click to expand...
Click to collapse
This little detail much explains my problem. Thanks
alray said:
Better to post the output of "fastboot getvar all" so we can know everything about your phone, stop the confusion and direct you to a rom/recovery and instructions that will work with your phone. When posting the output of "fastboot getvar all", censor your IMEI, MEID and SERIALNO, you don't want to post these values on the forums. Other values will help determining what you can flash and how.
Click to expand...
Click to collapse
Here is the data...
Code:
E:\ROMs\HTC One m7\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4056mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
alray said:
You might to use adb and fastboot directly from a command window using the latest android sdk tools. These toolkits are not up-to-date and not ideal when having issues. The other major issue with this toolkit is that its for the GSM M7 not for the Sprint variant.
Click to expand...
Click to collapse
In the directory, I use a command console, and write fastboot... etc.
Code:
Directorio de E:\ROMs\HTC One m7\One_All-In-One_Kit_v3.1\HTC\Data
09/10/2015 10:13 <DIR> .
09/10/2015 10:13 <DIR> ..
19/08/2012 01:00 846.848 aapt.exe
19/08/2012 01:00 191.488 adb.exe
19/08/2012 01:00 96.256 AdbWinApi.dll
19/08/2012 01:00 60.928 AdbWinUsbApi.dll
20/05/2013 04:03 1.151.546 APKBIT.exe
20/11/2010 22:23 345.088 cmd.exe
05/10/2015 17:19 1.345 Data - Acceso directo.lnk
19/08/2012 01:00 140.800 fastboot.exe
01/04/2012 00:53 186 mainver_fix.bat
19/02/2012 01:24 656.708 misctool
19/02/2012 08:41 4.526 misctool.c
07/10/2015 14:50 1.288.121.395 One.zip
28/07/2013 13:43 <DIR> Recoveries
07/10/2015 14:40 1.204.676.279 Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip
28/07/2013 13:42 <DIR> SU
06/10/2015 10:48 1.360.737 Superuser.zip
14 archivos 2.497.654.130 bytes
4 dirs 60.303.917.056 bytes libres
alray said:
You can only flash recoveries that are compatible with Sprint HTC One M7, in that above list, only that one ending with "m7wls.img" should work. To flash a recovery you have to use:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Ok. i will use that
alray said:
Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip ---> Its an RUU for Sprint HTC one. RUU are not flashed using custom recovery, its flashed using fastboot.
Click to expand...
Click to collapse
So, I don´t need to use a twpr to flash the phone?. but from fastboot, how can i flash a .ZIP file? I thought i needed a .IMG
------------------------------------------------------------------------------------
I just installed ok the OpenRecovery-TWRP-2.5.0.0-m7wls.img. it´s running ok
I unzipped file Sprint_HTC_One_m7wls_3_04_651_2_RUU.zip ....
Code:
adb.exe
AdbWinApi.dll
android-info.txt
ARUGlobal.dll
ARUWizard.exe
ARUWizard.ini
ARUWizard_ARA.lng
ARUWizard_BrPt.lng
ARUWizard_Cze.lng
ARUWizard_Dan.lng
ARUWizard_Dut.lng
ARUWizard_Eng.lng
ARUWizard_EuPt.lng
ARUWizard_EuSpa.lng
ARUWizard_FIN.lng
ARUWizard_Fra.lng
ARUWizard_Ger.lng
ARUWizard_Grk.lng
ARUWizard_Ita.lng
ARUWizard_Jap.lng
ARUWizard_Nor.lng
ARUWizard_Pol.lng
ARUWizard_Rus.lng
ARUWizard_SC.lng
ARUWizard_Svk.lng
ARUWizard_TC.lng
ARUWizard_Thai.lng
ARUWizard_TRK.lng
default.pal
DIFxData.ini
DMData00.DAT
DMData01.DAT
DMData02.DAT
DMData03.DAT
DMData04.DAT
DMData05.DAT
DMData06.DAT
DMData07.DAT
DMData08.DAT
DMData09.DAT
DOL_RECOVERY02_01.bmp
FontData.ini
htc_fastboot.exe
isrt.dll
MonitorConsole.exe
PHONE.bmp
ReadMe_ARA.doc
ReadMe_BrPt.doc
ReadMe_Cze.doc
ReadMe_Dan.doc
ReadMe_Dut.doc
ReadMe_Eng.doc
ReadMe_EuPt.doc
ReadMe_EuSpa.doc
ReadMe_FIN.doc
ReadMe_Fra.doc
ReadMe_Ger.doc
ReadMe_Grk.doc
ReadMe_Ita.doc
ReadMe_Jap.doc
ReadMe_Nor.doc
ReadMe_Pol.doc
ReadMe_Rus.doc
ReadMe_SC.doc
ReadMe_Svk.doc
ReadMe_TC.doc
ReadMe_Thai.doc
ReadMe_TRK.doc
rom.zip
setup.inx
StringTable_0x0409.ips
UPD_RECOVERY00_01.bmp
UPD_RECOVERY01_01.bmp
UPD_RECOVERY02_01.bmp
UPD_RECOVERY03_01.bmp
UPD_RECOVERY04_01.bmp
_isres_0x0409.dll
I ran the file "ARUWizard.exe" and ...
HTC Android Phone ROM Update Utility 2.0.5.2013, some steps ok,
Verify that you want to apdate the ROM version from 4.06.651.9 to 3.04.651.2, ok
Some steps before, the ERROR [155]: UNKNOWN ERROR (the rom update cannot update. Please get the correct ROM update utility).

slash22toly said:
Code:
E:\ROMs\HTC One m7\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4056mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
So, I don´t need to use a twpr to flash the phone?. but from fastboot, how can i flash a .ZIP file? I thought i needed a .IMG
Click to expand...
Click to collapse
If you flash a rom, you must flash it using twrp and make sure your twrp is for M7WLS variant and that the rom is also for that variant. If flashing a RUU, you must flash it using fastboot. Yes the ruu are zip files, all the required .img files are packed inside of it, you just need to flash the entire zip file. You can only flash ruu for sprint so*the ones that match with the sprint CID MID and version number x.xx.651.x <----- important since your phone is s-off. Make sure you are flashing the right files because with s-off, you can brick your phone easily if flashing a file that is not for your variant. Better to ask if you are unsure.
Code:
fastboot oem rebootRUU
fastboot flash zip your_ruu_name.zip
fastboot flash zip your_ruu_name.zip
fastboot reboot
That ruu is a downgrade btw but it should flash fine since your phone is s-off.

Im not shure the ruu files. I think it will be better, if i flash a custom ROM whith twpr. I only need to find a ROM for sprint m7wls.
What ROM do you recomend?

slash22toly said:
Im not shure the ruu files. I think it will be better, if i flash a custom ROM whith twpr. I only need to find a ROM for sprint m7wls.
What ROM do you recomend?
Click to expand...
Click to collapse
you can find Sprint HTC One M7 rom there: http://forum.xda-developers.com/sprint-htc-one/development
Make sure your phone have all the requirements before flashing a rom. Some roms like the Lollipop ones, requires to be on the latest firmware to be used, so if its the case you won't be able to flash those one, you'll probably be limited to kitkat roms.

alray said:
you can find Sprint HTC One M7 rom there: http://forum.xda-developers.com/sprint-htc-one/development
Click to expand...
Click to collapse
Well, my solution...
I Install in my PC the HTC One M7 driver MTP
By Fastboot, I install a TWPJ (twrp-2.8.7.0-m7.img)
Wipe ALL and format.
Install the last Cyanogenmod (CM11) custom ROM (https://download.cyanogenmod.org/get/jenkins/90464/cm-11-20141112-SNAPSHOT-M12-m7spr.zip)
Install a Gapps for 4.4 (ARM-4.4-Pico) (OpenGapp)
Install the Argentina Radio (Link)
It Run OK!!!!!!!!
---------- Post added at 03:20 PM ---------- Previous post was at 02:48 PM ----------
Well, my solution...
I Install in my PC the HTC One M7 driver MTP
By Fastboot, I install a TWPJ 2.8.7
Wipe ALL and format.
Install the last Cyanogenmod (CM11) custom ROM (download.cyanogenmod.org/get/jenkins/90464/cm-11-20141112-SNAPSHOT-M12-m7spr.zip)
Install a Gapps for 4.4 (ARM-4.4-Pico) (opengapps.org)
Install the Argentina Radio (androidfilehost.com/?fid=23159073880933335)
It Run OK!!!!!!!!