Database Develop

[Q] stuck on boot no usb connection to computer

** update **
just got usb working i think.
meaning when looking in the device list on my computer i got a "android phone - android bootloader interface"
but i dont see it in the explorer as a drive or something, so i am not quite sure if it's reachable by now or not.
** extra info
only got the original hboot so i can't choose a zip from the sd card to re-flash
hi
during a system update i had a power break down. no i got the problem my phone wont boot.
The phone is also not connectable thru usb (computer won't recognize the phone)
is there any way to solve this problem?
when i connect the phone to the usb port it starts searching for it but i get the error (unknown device and the driver won't be installed)
when i turn on the phone with volume down + power i get into the hboot screen with the next info.
vivo pvt ship s-off rl
hboot-6.13. 1002
radio- 3822. 10.08.28_m
emmc-boot
the factory reset doesn't work
going to hboot usb also does nothing.
any tips/help and advice is apriciated

theflyingdutchman said:
** update **
just got usb working i think.
meaning when looking in the device list on my computer i got a "android phone - android bootloader interface"
but i dont see it in the explorer as a drive or something, so i am not quite sure if it's reachable by now or not.
** extra info
only got the original hboot so i can't choose a zip from the sd card to re-flash
hi
during a system update i had a power break down. no i got the problem my phone wont boot.
The phone is also not connectable thru usb (computer won't recognize the phone)
is there any way to solve this problem?
when i connect the phone to the usb port it starts searching for it but i get the error (unknown device and the driver won't be installed)
when i turn on the phone with volume down + power i get into the hboot screen with the next info.
vivo pvt ship s-off rl
hboot-6.13. 1002
radio- 3822. 10.08.28_m
emmc-boot
the factory reset doesn't work
going to hboot usb also does nothing.
any tips/help and advice is apriciated
Click to expand...
Click to collapse
i did find a way to connect the phone to the computer (it is visable as a HTC in device manager list)
but still not reachable thru explorer
At this point it does only connect to the computer when booting in HBOOT (hboot usb)
are there any options to use it as a drive or something while booting in HBOOT since the phone won't be seen by the computer when i power up normally

theflyingdutchman said:
** update **
just got usb working i think.
meaning when looking in the device list on my computer i got a "android phone - android bootloader interface"
but i dont see it in the explorer as a drive or something, so i am not quite sure if it's reachable by now or not.
** extra info
only got the original hboot so i can't choose a zip from the sd card to re-flash
hi
during a system update i had a power break down. no i got the problem my phone wont boot.
The phone is also not connectable thru usb (computer won't recognize the phone)
is there any way to solve this problem?
when i connect the phone to the usb port it starts searching for it but i get the error (unknown device and the driver won't be installed)
when i turn on the phone with volume down + power i get into the hboot screen with the next info.
vivo pvt ship s-off rl
hboot-6.13. 1002
radio- 3822. 10.08.28_m
emmc-boot
the factory reset doesn't work
going to hboot usb also does nothing.
any tips/help and advice is apriciated
Click to expand...
Click to collapse
Can you enter recovery?
Doing any kind of system update is generally unadvisable on an s-off device. You may have mentioned this at some point but I missed it: By not booting, do you mean bootloop? What Rom did you have installed?

Nonverbose said:
Can you enter recovery?
Doing any kind of system update is generally unadvisable on an s-off device. You may have mentioned this at some point but I missed it: By not booting, do you mean bootloop? What Rom did you have installed?
Click to expand...
Click to collapse
i used to have a cynogen mod rom with an bootloader being able to flash zip files from the sd card (dont know wich one anymore)
after wanting back the stock rom i did a downgrade from cynogen to the stock rom with the original hboot ( so basicly factory settings)
When turn on the phone and go into HBOOT i can do a recovery or a factory reset and go into usb boot mode.
both the recovery and the restore option don't work, after a while the phone does reset and get stuck at a white screen with green HTCC letters THATS IT.
going into HBOOT usb mode the phone is found as a HTC device in the device manager but not shown in the explorer so still not reachable

I think you're still far away from having enough knowledge to even explain what problem you have, cause you obviously don't know the meaning and difference between bootloader and recovery.
You need to find some good noob tutorial and learn how it all works and how all should be done.

theflyingdutchman said:
i used to have a cynogen mod rom with an bootloader being able to flash zip files from the sd card (dont know wich one anymore)
after wanting back the stock rom i did a downgrade from cynogen to the stock rom with the original hboot ( so basicly factory settings)
When turn on the phone and go into HBOOT i can do a recovery or a factory reset and go into usb boot mode.
both the recovery and the restore option don't work, after a while the phone does reset and get stuck at a white screen with green HTCC letters THATS IT.
going into HBOOT usb mode the phone is found as a HTC device in the device manager but not shown in the explorer so still not reachable
Click to expand...
Click to collapse
Does the pc recognize the phone in fastboot mode?

Nonverbose said:
Does the pc recognize the phone in fastboot mode?
Click to expand...
Click to collapse
it is in the recognized as a "android phone - HTC "recognized in the device mannager BUT not shown in the explorer
ps after a re-install this weekend the phone won't be recognized and have to get that fixed again.

theflyingdutchman said:
it is in the recognized as a "android phone - HTC "recognized in the device mannager BUT not shown in the explorer
ps after a re-install this weekend the phone won't be recognized and have to get that fixed again.
Click to expand...
Click to collapse
When you get set up, post the output of the command
Code:
fastboot getvar all
remove info like imei and serial number before posting.

Just connect your phone in fastboot mode, check if you have HTC Sync and if drivers are installed. If drivers are not installed (and you have exclamation mark over it in Device Manager) choose to update driver and lead it to folder HTC in Program Files, there you have 2 different folders with drivers try both of them.
After that command prompt should see your phone in fastboot mode with
fastboot devices
Command.
Then simply flash recovery from fastboot
fastboot flash recovery c:\'path to your recovery'
Recovery can be obtained on RomManager site. After that just restore some of your backups or flash a clean new rom.
If that doesn't work, and shoud work, you can always run newest stocks ICS.
And one more question, how do you think to get your phone connected in storage mode (so you can see it in explorer) when you can't boot it up or boot to recovery???

nlooooo said:
I think you're still far away from having enough knowledge to even explain what problem you have, cause you obviously don't know the meaning and difference between bootloader and recovery.
You need to find some good noob tutorial and learn how it all works and how all should be done.
Click to expand...
Click to collapse
i sure do know

theflyingdutchman said:
i sure do know the difference between those 2 its prob more a lack of my english
btw what makes you think i don't know the difference between those 2?
Click to expand...
Click to collapse
Try to read my second post and don't be a dush.

Nonverbose said:
When you get set up, post the output of the command
Code:
fastboot getvar all
remove info like imei and serial number before posting.
Click to expand...
Click to collapse
ok this might sound stupid.
do you mean in a dos box within windows?
if i open a dos box ( cmd ) and type this commando i get an error like this is not recognized as an internal or external command
since the phone is only in the device mannager list i still have no option to get connected with it (thru explorer or something like that)

theflyingdutchman said:
ok this might sound stupid.
do you mean in a dos box within windows?
if i open a dos box ( cmd ) and type this commando i get an error like this is not recognized as an internal or external command
since the phone is only in the device mannager list i still have no option to get connected with it (thru explorer or something like that)
Click to expand...
Click to collapse
First, you don't wanna read and you want help, so why are we typing.
Second, for fastboot commands you nead ADB installed or at least fastboot.exe, and you have to lead command prompt to location of ADB tools.
And, at the end, to get phone recognized as a storage (or how you say a drive) YOUR PHONE HAS TO BE BOOTED AND CONNECTED TO PC AS A STORAGE DEVICE OR BOOTED TO A WORKING RECOVERY AND MOUNTED AS STORAGE DEVICE.
I still think that you need to read some tutorial about Android functioning, ADB, phone working mods and partitions and how to handle them. Also, for difference, try to read what we are typing...

1. Ensure you have installed the drivers for your phone model.
2. Search the forums on 'fastboot' (it is obvious you are not setting/using it correctly if you get that error - I know I did )
3. SDCard will only be seen by PC once Android system is booted up or HBOOT is loaded correctly then it can be accessed through HBOOT using fastboot - it will NOT show up as an external drive on the PC in it's current state.
4. Small steps, if you know roughly which rom you had installed I would use that to recover your phone from, starting with HBOOT then RECOVERY one at a time, to know what and how takes reading up in the forums for your phone and rom.
Sent from my Acer E320-orange using xda app-developers app

theflyingdutchman said:
ok this might sound stupid.
do you mean in a dos box within windows?
if i open a dos box ( cmd ) and type this commando i get an error like this is not recognized as an internal or external command
since the phone is only in the device mannager list i still have no option to get connected with it (thru explorer or something like that)
Click to expand...
Click to collapse
Yes I did mean a cmd window. As stated previously, you need fastboot and adb installed. If you use my downgrade script (link in Sig) and unzip it, it contains the correct files. You need your drivers installed though (install and uninstall HTCsync) and you need to cd to the files directory.

Nonverbose said:
When you get set up, post the output of the command
Code:
fastboot getvar all
remove info like imei and serial number before posting.
Click to expand...
Click to collapse
below are the results of the getvar all command.
<bootloader> version 2.5
<bootloader> version-bootloader: 6.13.1022
<bootloader> version-baseband: 3822.12.03.28_m
<bootloader> version-cpl: none
<bootloader> version-nicrop: none
<bootloader> version-nain: none
<bootloader> serialno
<bootloader> imei
<bootloader> product: vivo
<bootloader> platform: HBOOT-7630
<bootloader> modelid: FG3213200
<bootloader> cidnun: HTC_E11
<bootloader> battery-status: good
<bootloader> battery-voltage: 4179mV
<bootloader> partition-layout: Generic
<bootloader> security: off
<bootloader> build-mode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> conmitno-bootloader: dirty-8a731c5e
<bootloader> hbootpreupdate: 12
<bootloader> gencheckpt: 0

did follow these steps clockword mod recovery http://www.androidauthority.com/one-x-clockworkmod-touch-recovery-76853/
but i get the error con't load imagename.img

nlooooo said:
Just connect your phone in fastboot mode, check if you have HTC Sync and if drivers are installed. If drivers are not installed (and you have exclamation mark over it in Device Manager) choose to update driver and lead it to folder HTC in Program Files, there you have 2 different folders with drivers try both of them.
After that command prompt should see your phone in fastboot mode with
fastboot devices
Command.
Then simply flash recovery from fastboot
fastboot flash recovery c:\'path to your recovery'
Recovery can be obtained on RomManager site. After that just restore some of your backups or flash a clean new rom.
If that doesn't work, and shoud work, you can always run newest stocks ICS.
And one more question, how do you think to get your phone connected in storage mode (so you can see it in explorer) when you can't boot it up or boot to recovery???
Click to expand...
Click to collapse
drives might still be the problem.
there are no exclamation marks in the device manager. in the device manages i got a "Android usb device - My HTC" but adb wont show up any connected device.
checked thru "adb devices" there are no connected devices shown

Reboot to fastboot and type
fastboot devices
Not adb devices, abd commands can be used from recovery or a booted device. Try to google something about fastboot commands, you will find a lot of it.

If it's like my phone there may not be any output for 'devices' after executing the devices command with fastboot you get a blank return and your command prompt back in the command window.
Other commands can be sent regardless of an actual 'devices' returned name, at least that is what I get, with your phones problem atm the same may apply.
Sent from my Acer E320-orange using xda app-developers app

[GUIDE][FIX] Solve Bootloops and no OS on phone!

Hello XDA-Community!
Because of the high amount of people having this particular problem, I decided to make this guide. Here it goes:
< < < ! ! ! WARNING ! ! ! > > >
THIS THREAD DOESN'T TEACH YOU HOW TO USE YOUR RICE COOKER, USE IT ON YOUR OWN RISK​
This guide is for you if you are in the following situation:​​
S-ON or S-OFF
UNLOCKEDor (RE)LOCKED Bootloader
NO ROM installed or a nasty BOOTLOOPor you just need METAPHYSICAL SUPPORT
You can get to fastboot!
Maybe you don't even know that you are able to enter fastboot, check FAQ in the 2nd post for that
​​
​
No matching and working ROM.zip? No Problem​​
Now there are several ways to do that. If you are S ON or S OFF download one of these ROM's and read the rest of the guide while the ROM is downloading in the background.
HTC Sense ROM KitKat:
http://www.androidrevolution.nl/downloader/download.php?file=One_4.19.401.8_odexed.zip
(Thanks to @mike1986.)
HTC Sense ROM JellyBean 4.3:
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
(Thanks to guru reset)
Google Play Edition KitKat(S OFF needed):
http://forum.xda-developers.com/showthread.php?t=2341395 (Go there and hit the thanke button if you use this)
https://mega.co.nz/#!3BtCBD6T!ViZfS1MwhR4ttcPEkB3XrDVv9Asardy4e01UJO-5ZB0
(Thanks to @bigxie)
Omni ROM:
http://forum.xda-developers.com/showthread.php?t=2488216 (Go there to and punch the thanks button if you use this)
http://dl.omnirom.org/m7ul/ (Official nightlies (download the ZIP file!!))
Or just download the homebrew ... I personally prefere this one(It's in the thread linked above)
CyanogenMod:
http://download.cyanogenmod.org/?device=m7ul
​
No drivers working? No Problem​​
This here works for Windows Vista/7/8 and Mac as far as I know !
Try using a different USB Port
Uninstall all the drivers related to android devices!
Download the HTCSync manager here (HTC Sync Manager)
Install the HTCSync Manager with ALL compomnents
Restart the computer
Uninstall the HTCSync Manager BUT do NOT uninstall the drivers!
Reboot your computer
Now the phone should be recognized properly.
Otherwise try using a different USB cable and a USB port directly on the motherboard of the PC
For those of you (windows users) that just want to install the drivers without the HTCSync procedure, you can download the drivers directly from this post here:
[Drivers] HTC Drivers for Windows - Several Versions
(Thanks @nkk71 for this hind and thanks @mdmower for providing HTC Drivers!)
If you have this particular issue here(Thanks @nkk71 check out his guide [GUIDE] nkk71's SuperGUIDE to returning 100% back to stock and punch the thanksbutton as often as you can!)
{
"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"
}
Then follow this procedure:
THIS SECTION IS FULLY COPY&PASTED FROM @nkk71 FROM THIS POST [GUIDE] nkk71's SuperGUIDE to returning 100% back to stock
If this works (and even if it doesn't) please go to his thread and punch the thanks button to death !
I did some small changes to it, so if there's a fault, it might just be LibertyMarine who made a mistake
​
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
Follow the steps below to fix it:
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
for those who like a visual guide:
As you can see, the drivers didn't install properly:
To solve this issue, open the Device Manager with Administrator permissions
Look, there's the culprit -.-
Right click One and select Update Driver Software
Next, select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer in the following menu
Choose Android USB Devices
Select My HTC ... (if you have more than one version, choose the latest)
There's a warning, select Yes and ignore it
Let's hope for a successful installation
Now it looks better
We can now confirm that you have a stable ADB connection from your PC to your phones recovery
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
This works in 99% of all cases. Otherwise these guides may help you further:
[FIX] Working Fastboot Drivers for Windows 8.1 x64
[FIX] Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)
Easily Set Up FASTBOOT and ADB on a MAC for Android Smartphones Youtube Turorial
Other guides will come soon!
​
RELOCKED or even LOCKED and even S ON? No Problem!​
For some unknow reason, you are relocked or even locked... yeah... and your bootloader is locked... you have no operating system installed and you think you are hard bricked.
To solve this problem, you just have to Unlock the bootloader again using HTCdev. I though this is pretty logic but there are still people that think they can't unlock it again. No that's wrong. So basically -> Just head over to: HTC Dev
And for those that want some pictures:
1) Chose All other supported models:
2) Chose the option: Begin Unlock Bootloader:
3) Press OK, then this screen appears, you have to accept both and continue:
4) Now.. Boot your phone into the bootloader holding power and vol down button at the same time while booting after having shutdown your phone
5) Since you must have fastboot installed because you followed the above descripted procedure... issue this command:
6) You'll get such an ouput(credit to htc because of privacy issues):
7) Enter the string on the bottom of the page(you need an account):
http://www.htcdev.com/bootloader/unlock-instructions/page-2
8) Follow the instructions given by mail from HTC...
And now for the case if you are S OFF and Locked or Relocked:
You can either use this toolkit: http://www.htc1guru.com/guides/guru-bootloader-reset/
Or follow this thread: [how to] lock/unlock your bootloader without htcdev(s-off required)
Both needs a recovery.. and how to flash a recovery with locked bootloader and s off, just look a few lines below ​
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
You want to have stock software again? No Problem​
This section here doesn't tell you how to go 100% stock. Here you find instructions for how to run a RUU or a FUU. If you want to go back to to a factory fresh device use this guide here instead:
[GUIDE] nkk71's SuperGUIDE to returning 100% back to stock
by @nkk71​
RUU - ROM Update Utility:​
A RUU will reset your phone back to stock software and you'll be able to get OTAs. But a RUU won't set you LOCKED and S ON!
PAY ATTENTION IF YOU ARE ON WINDOWS 8.1 AND READ FAQ FIRST IN SECOND POST!
First, find a matching RUU. There are several sources for RUUs, here are the most popular ones:
AndroidRUU | The #1 source for Android RUU files
Collection of HTC One RUU Zip File Downloads. Reset device to Stock (By HTC1Guru, if anyone know what his XDA account name is, tell it, I wanna mention him)
Now, here the step by step GUIDE goes:
THIS WILL DELETA ALL USERDATA​
Make a backup using TWRP or CWM
Copy the backup to your PC and copy your whole SDCard content to the PC too
Boot your phone to the bootloader and enter fastboot
Reboot to the RUU mode using this command:
Code:
fastboot oem rebootRUU
Check the connection:
Code:
fastboot devices
The output should look like this:
Code:
C:\Users\Obama\> fastboot devices
List of devices attached
<serial number> fastboot
Then flush your RUU.zip using this command(Windows users, pay attention to ruu.zip.zip):
Code:
fastboot flash zip "C:\<path>\<ruu_name.zip">
This should be the output, check that the red marked text is 100% exactly like this and ensure that you don't get any error during hboot flash, a failed hboot flash will UNEVITABLY lead into a hardbricked device if you reboot. For that check the FAQ section in my second post !
Code:
C:\User\Cheese\>fastboot flash zip "C:\<path>\<ruu_name.zip>"
sending 'zip' (100322311 KB)...
OKAY [ 30.124s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [COLOR="red"][RUU]WP,hboot,0[/COLOR]
(bootloader) [COLOR="red"][RUU]WP,hboot,99[/COLOR]
(bootloader) [COLOR="red"][RUU]WP,hboot,100[/COLOR]
(bootloader) [COLOR="Red"]...... Successful[/COLOR]
[COLOR="Red"]FAILED [/COLOR](remote: 90 hboot pre-update! [COLOR="Blue"]please flush image again immediately[/COLOR])
finished. total time: 35.231s
Reflash zip file again after the phone has automatically rebooted itself back to the RUU mode:
Code:
fastboot flash zip "C:\<path>\<ruu_name.zip">
Here, we won't flash any too cricital software parts, so check that the output looks approximately like this, it's ok that several partitions are bypassed.. just make sure it isn't the system or other partitions you'd like to reset back to stock. Ok, output looks like this:
Code:
C:\User\Cheese\>fastboot flash zip "C:\<path>\<ruu_name.zip>"
sending 'zip' (100322311 KB)...
OKAY [ 31.293s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,11
[...lot's of flashing...]
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... [COLOR="Blue"]Bypassed[/COLOR]
[...that's ok...]
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 230.443s]
finished. total time: 230.444s
Then reboot your phone to the bootloader:
Code:
fastboot reboot-bootloader
Check, that hboot is 1.44 and reboot your phone normally and enjoy stock software !
​
FUU - Firmware Update Utility:​
Was once WIP - Work in Progress !
But now, this section is shut down too.
​
I hope this guide helped you. Ask everything(except said differently) in the comments!​
Disclaimer:
I AM NOT RESPONSIBLE FOR ANY LOSS OF DATA BECAUSE YOU FOLLOWED THIS GUIDE
I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES, TOASERS, RICE COOKERS!
I AM NOT RESPONSIBLE FOR ANY KIND OF NUCLEAR WAR DECLARED BY YOUR DOG/CAT​​

! Once this section was constantly growing !
​
Basic issues and troubleshooting? Here it goes​
Q: I can't start up my device, not even the soft buttons are lighting up!
A: I know, it sound strange, but you have to do the following thing:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!​
Q: I still can't boot up my device!
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again​
Q: I tried flashing the RUU and I got an error while flashing hboot, what can I do?
A: JUST DON'T REBOOT try reflashing, try a different hboot... use a different computer/usb cable, just don't reboot, rebooting will lead into a hard-bricked device!
The following Errors are save to reboot(Thanks @Sneakyghost, http://forum.xda-developers.com/showthread.php?t=2316726):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 seems to indicate different things, always relating to your phone not being eligible for a certain update. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match - there is no conclusive evidence yet, only hints. I can for now not see the commands being run by a RUU and determine which check exactly fails, so i am left guessing for now.​
Q: What do I have to pay attention to using Windows 8.1 ?
A: Actually, there are no more driver issues with Windows 8 or Windows 8.1. But if your HTC One is on hboot 1.44 or even below hboot 1.44 you can't get a fastboot connection to your HTC One. This means if you're using one of the older RUU's that downgrade to hboot 1.44 you'll be stuck after the first hboot preupdate:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
And you won't be able to reflash the RUU to complete the RUU process.. This means that you have to find a Windows 7 Computer to complete the RUU process. What does this exactly mean?
Never flash a 1.44 firmeware or RUU package to your device using Windows 8+ or you'll be stuck!
​
Q: What do I have to check when choosing an RUU?
A: That's pretty easy. But the best thing is to explane it with an example.. Ok, I downloaded this file here from HTC1Guru and it's called like this:
RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.zip
Click to expand...
Click to collapse
Now, the red marked text has to be the same as your device was on stock.
x.xx.401.x stands for your location. It's also written before... like above "Europe"
And the blue text is also important ​
Q: What issues might come with newer hboots?
A: Ok, new hboots give you more performance and better stability. But the downside of one of these hboots is the newly introduced Tamper detected on hboot 1.55. This basically means that when going back to stock with a RUU Locking and Untampering and taking all OTAs up to hboot 1.55+ and then going back S ON(Highly NOT recommanded) will lead into a tamper dectected and you'll see this tampered flag again. What means, a lot of work: Unlocking, S offing, RUUing and Locking going S ON the right time again.. The particular right time is:
After hboot 1.44 but before hboot 1.55... this means the best hboot to use is 1.54.. you did an OTA and this means that the bootloader is more than stock and so most likely safe to go back s on and you are on a version before hboot 1.55 what means you won't get a tamper detected!
Also: Going back S ON with a altered bootloader is inevitably going to lead into a hard bricked device !
Summary:
NEVER GO S-ON WITH A MODIFIED HBOOT AND A HBOOT VERSION HIGHER THAN 1.54​

Reserved 2 is not needed anymore and won't be needed in the near future. So give him a snickers that this post is happy again !

Saying Thanks, Why not?​​
Ok, here I list the people that helped me building this thread, people that helped me gaining knowledge in such a short time, people that gave me advice, people that I used as a source in this thread.
Why do I do that? People say too seldon thanks, and I'll most likely leave the HTC One section because of problems I don't wanna mention.
I think I have to thank him first because:
@nkk71 He helped me dozens of times and and I used him as a source for this thread, as you can see, so Thanks very much
I also wanna really say thanks to:
@Sneakyghost Because I used him as a source on this thread and he gave me valuable advice to improve the threads content
And also a very big thanks to:
@kamilmirza for giving me advice and stealing my thread into his signature
But the bigges thanks goes to my:
@rice_cooker because it supports me through my every day life and provides the best rice!
​Sources and Very important links​​
For going back to a factory fresh HTC One for sending in for warranty claims:
[SOURCE]
[GUIDE] nkk71's SuperGUIDE to returning 100% back to stock
Custom hboots without red warning after S OFF, Firmware Update Utilities:
[SOURCE]
[GUIDE] [MOD] GSM Firmware Flashing & Hboots red warning gone
RUU Source, not only HTC One:
AndroidRUU | The #1 source for Android RUU files
CWM Backup, RUU, ROM.zip Source, basically everything for going back to stock:
HTC1Guru - HTC One Downloads
Installing ADB and FASTBOOT automatically:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1
​

nice
keep up the good work :good:

Nice work mate, i'm sure that'll help some noobies like us ourselves haha.
commenting on this: pushing ROM to path /data/media/0 resulted in permission and SU errors for me in the past, partly due to an imperfect SU which needed to be adjusted for Android 4.3 and then again for Android 4.4
What helped me there was trying different pathes, since we got at least 3 ways to access the SDCard:
/data/media/0
/storage/emulated/0
/sdcard
there might still be more. /sdcard should be the default way to address this so i recommend changing your adb command to /sdcard/rom.zip instead but provide the other two pathes as alternatives for people who experience issues with file and directory permissions after the flash or while flashing the ROM.
Regards,
Sneaky

Sneakyghost said:
Nice work mate, i'm sure that'll help some noobies like us ourselves haha.
commenting on this: pushing ROM to path /data/media/0 resulted in permission and SU errors for me in the past, partly due to an imperfect SU which needed to be adjusted for Android 4.3 and then again for Android 4.4
What helped me there was trying different pathes, since we got at least 3 ways to access the SDCard:
/data/media/0
/storage/emulated/0
/sdcard
there might still be more. /sdcard should be the default way to address this so i recommend changing your adb command to /sdcard/rom.zip instead but provide the other two pathes as alternatives for people who experience issues with file and directory permissions after the flash or while flashing the ROM.
Regards,
Sneaky
Click to expand...
Click to collapse
Thanks Sneakyghost !
Yeah, I made this guide because quite a lot of people are complaining about having no OS and so on
I added this hint about the different paths to the guide I personally haven't had this issue but it's the best to provide solutions for as many cases as possible .. (sorry for my bad english)
Have a great evening,
LibertyMarine

Hi @LibertyMarine
nice work :good::good: (i did press the thanks before, bot only now actually got to reading it all)
If you don't mind, a few notes (just trying to help)
Let them check MD5 on anything they download, a lot of times, just turns out to be a bad download.
No matching and working ROM.zip? No Problem
"HTC Sense ROM KitKat(S OFF needed)" by @mike1986. doesn't actually need S-OFF,
but "Google Play Edition KitKat" by @bigxie needs S-OFF,
if I'm not mistaken.
No drivers working? No Problem
HTC Drivers for Windows (without HTCSync), can be found here: http://forum.xda-developers.com/showthread.php?t=2089508
also, if the phone is just recognized as:
check my (updated ) Guide, Post #1, FAQ #2 on how to fix that.... feel free to incorporate it (or relevant parts) into your guide.
No Recovery? No Problem
"For some stupid reason you are s off (that's a MUST) and Relocked" the firmware package you posted works only for CID: 11111111 , T-MOB010 CWS__001 , BS_US001 and maybe GOOGL001; it wont work for HTC__001 and HTC__002 due to missing line break
so
1- let them first change CID to SuperCID then flash it
2- (in my humble opinion) once in custom recovery, let them unlock bootloader using @scotty1223 adb commands ( http://forum.xda-developers.com/showthread.php?t=2475914 ), or whatever method you find appropriate
keep up the good work :highfive:

thanks for your post.. nice post

nkk71 said:
Hi @LibertyMarine
nice work :good::good: (i did press the thanks before, bot only now actually got to reading it all)
If you don't mind, a few notes (just trying to help)
Let them check MD5 on anything they download, a lot of times, just turns out to be a bad download.
No matching and working ROM.zip? No Problem
"HTC Sense ROM KitKat(S OFF needed)" by @mike1986. doesn't actually need S-OFF,
but "Google Play Edition KitKat" by @bigxie needs S-OFF,
if I'm not mistaken.
No drivers working? No Problem
HTC Drivers for Windows (without HTCSync), can be found here: http://forum.xda-developers.com/showthread.php?t=2089508
also, if the phone is just recognized as:
check my (updated ) Guide, Post #1, FAQ #2 on how to fix that.... feel free to incorporate it (or relevant parts) into your guide.
No Recovery? No Problem
"For some stupid reason you are s off (that's a MUST) and Relocked" the firmware package you posted works only for CID: 11111111 , T-MOB010 CWS__001 , BS_US001 and maybe GOOGL001; it wont work for HTC__001 and HTC__002 due to missing line break
so
1- let them first change CID to SuperCID then flash it
2- (in my humble opinion) once in custom recovery, let them unlock bootloader using @scotty1223 adb commands ( http://forum.xda-developers.com/showthread.php?t=2475914 ), or whatever method you find appropriate
keep up the good work :highfive:
Click to expand...
Click to collapse
ok, thanks thousand times !!
I'll add these hints to my guide ... just need some time
What you said about @scotty1223's guide... I tried it once in the custom recovery... but it didn't work for me... but I'll add it... and I'll try to get it working for me.. so I can give them my experience... or whatever
Anyways, THANKS !!
Have a great evening,
LibertyMarine

LibertyMarine said:
ok, thanks thousand times !!
I'll add these hints to my guide ... just need some time
What you said about @scotty1223's guide... I tried it once in the custom recovery... but it didn't work for me... but I'll add it... and I'll try to get it working for me.. so I can give them my experience... or whatever
Anyways, THANKS !!
Have a great evening,
LibertyMarine
Click to expand...
Click to collapse
how come it didnt work
worked for me, there are more than one way to unlock bootloader with S-Off (maybe "safest" and easiest to use is http://www.htc1guru.com/guides/guru-bootloader-reset/ )
but there are other ways too (GPE 4.2.2 RUU -> fastboot oem unlock ) as long as s-off

WIP, I am making all the screenshots and I'll upload them as fast as I can, because just using the screenshots from nkk71 would be some kind of stealing, so I wanna quickly do it on my own
Click to expand...
Click to collapse
@LibertyMarine no problem, you can use the pictures (since you're already mentioned where it came from :laugh: ). Let me know if you want the text too, i can PM you the whole section (including the IMG pictures links)

nkk71 said:
@LibertyMarine no problem, you can use the pictures (since you're already mentioned where it came from :laugh: ). Let me know if you want the text too, i can PM you the whole section (including the IMG pictures links)
Click to expand...
Click to collapse
ok, thanks ! this saves a lot of work !! :good::victory:
oh, you don't need to send me the section with PM, I think I can copy paste it when I try to quote your post Thanks anyways for this offer !
If you know another way I can mention you, just tell it, I'll do it !

LibertyMarine said:
Thanks Sneakyghost !
Yeah, I made this guide because quite a lot of people are complaining about having no OS and so on
I added this hint about the different paths to the guide I personally haven't had this issue but it's the best to provide solutions for as many cases as possible .. (sorry for my bad english)
Have a great evening,
LibertyMarine
Click to expand...
Click to collapse
I think there's another path you can use but I haven't tested it, just seen it being there: /mnt/sdcard
mobile Viper bite

I ****ed up my phone. I think I need to just get a rom onto my phone but its basically stuck in recovery. Can someone explain how to get a rom onto my phone? Is it adb sideload? And if it is I can't figure out how to work that.

lilfil3 said:
I ****ed up my phone. I think I need to just get a rom onto my phone but its basically stuck in recovery. Can someone explain how to get a rom onto my phone? Is it adb sideload? And if it is I can't figure out how to work that.
Click to expand...
Click to collapse
As I understood, you can get to the recovery.
If you already have a ROM downloaded to your computer, just go to this section of the first post in this thread called:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
Lots of instructions​
But if you don't have any OS downloaded, go to this section and download one
No matching and working ROM.zip? No Problem​​
Lots of roms​
If this doesn't work, just call me again with a mention or a post.. whatever

lilfil3 said:
I ****ed up my phone. I think I need to just get a rom onto my phone but its basically stuck in recovery. Can someone explain how to get a rom onto my phone? Is it adb sideload? And if it is I can't figure out how to work that.
Click to expand...
Click to collapse
Is this what's supposed to happen? And thanks for all the help by the way!
(Attachment below)

lilfil3 said:
Is this what's supposed to happen? And thanks for all the help by the way!
(Attachment below)
Click to expand...
Click to collapse
you forgot the space .. you wrote
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip/sdcard[/COLOR]/One_blabla.zip
instead of
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip /sdcard[/COLOR]/One_blabla.zip
in the second one there's a space between .zip /sdcard

LibertyMarine said:
you forgot the space .. you wrote
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip/sdcard[/COLOR]/One_blabla.zip
instead of
Code:
adb push C:\Users\filic_000\One_blabla.[COLOR="Red"]zip /sdcard[/COLOR]/One_blabla.zip
in the second one there's a space between .zip /sdcard
Click to expand...
Click to collapse
Ok now it said error: device not found

lilfil3 said:
Ok now it said error: device not found
Click to expand...
Click to collapse
are you in recovery? if yes... try this section in the first post:
No drivers working? No Problem​​Lot's of instructions​

[Q] HTC One, tampered, unlocked, S-ON, no OS, device not foun on laptop. Cluster****.

Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!

PrimalMK said:
Hi xda!
I recently got a HTC One from a friend, as my old phone was worn out. It turned out he had rooted it, tampered with it, the whole nine yards. I was not told he had rooted it, so I accepted a prompt asking me to update the phone to what I believe was 4.4.2, KitKat. I now realize that should not have been done. When the phone restarted it went to the HTC startup logo, into a kind of blue screen (not the BSOD), the Google logo flashed on the screen for 0.5 seconds, and then it got stuck on this weird blue/turqoise screen. Nothing happened.
I called my friend, he told me he rooted it etc., and that I should try a factory reset, and if that didn't work, complete reset (including the system folder wipe). That obviously didn't work, but I didn't know any better as I have never touched a rooted phone in my life, and I'm thus a complete noob when it comes to terminology, what steps to take and so on.
Now I have a phone with no OS, stuck at the HTC logo when I start it normally, and all I can do is boot up into bootloader. I can also access TWRP. I have installed HTC Sync on my laptop, but the phone is not detected properly (meaning, the "device connected" sound is played, and I can find "Android device" in device manager, but the HTC Sync can't find the phone) when connected through a USB. It is not the USB that came with the phone. I also installed Squabbi's HTC One toolkit, which basically is the one-click interface of pushing revone etc. to the phone. Problem is, "error, device not detected".
I've browsed around for a good six hours without any luck, other than that I've started to understand how this is all connected.
Phone is
*TAMPERED*
*UNLOCKED*
M7_UL
S-ON
HBOOT 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
I pray to the mighty tech gods of xda to help me out. I looked for similar threads, couldn't find any that were simple and similar enough for me to understand. I must admit I'm very keen to learn this, so if someone know of any place where basic terminology is explained, I'd really appreciate that. Other than that, a step by step instruction on how to proceed from this cluster**** would also be highly appreciated (what I need installed on my laptop, where I can find ROM's, what flashing means etc.).
Thank you in advance!
Click to expand...
Click to collapse
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs

clsA said:
well a lot of the work seems to already be done
your unlocked / rooted which means you should have a custom recovery installed.
boot the phone by holding the power + volume down
this will bring up the bootloader. use the volume key to choose recovery aand hit the power button. when you boot into recovery come back and report the name and version of recovery. I.E. Teamwin recovery 2.5.0.0 or clockworkmod 6.0.3.1 ...I'll be here the next couple hrs
Click to expand...
Click to collapse
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version of TWRP does not work. I have no preferences when it comes to OS's. A stock OS (is OS and ROM the same thing?) would be fine.

Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.

PrimalMK said:
Version of TWRP is 2.5.0.0. Currently trying to re-install an OS. Need one that the current version of TWRP can flash to the phone, as flashing a new version does not work. I have no preferences. A stock OS (is OS and ROM the same thing?) would be fine.
Click to expand...
Click to collapse
Well your going to need adb / fastboot on your PC
use mine here >> https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
and install the HTC Drivers here >> http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
unzip that to c:\ so you have c:\fastboot in windows explorer
now inside the folder you shift + right click / command prompt here
now you have a command prompt window type
fastboot getvar all
and post the result here / minus your serial number and IMEI
then i can find you the correct recovery and rom for your phone
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
PrimalMK said:
Also, found out that doing stuff on a Windows 7 laptop was easier than on my own Windows 8. The phone is at least detected on the Windows 7, which means I will be able to flash stuff to it through cmd, something I wasn't able to do from the Windows 8.
Click to expand...
Click to collapse
yes window 8 will be a problem till you get another hboot above 1.44/1.54
hboot 1.55 has no problem on windows 8 ( I use windows 8.1)

clsA said:
instructions
Click to expand...
Click to collapse
Downloaded fastboot, unzipped in c:
Drivers from that link are classed as malware. Trying to find earlier drivers/other mirror.

Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.

PrimalMK said:
Find attachment.
Still looking for drivers. Apparently "every" browser blocks exe-files from being downloaded. Changed settings, managed to download it, run as admin. No response.
Click to expand...
Click to collapse
this will work fine
just put TWRP and the Rom in the fastboot folder
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse

clsA said:
this will work fine
just put TWRP and the Rom in the fastboot folder
Click to expand...
Click to collapse
error: cannot open 'openrecovery.......img'
What to do?

PrimalMK said:
error: cannot open 'openrecovery.......img'
What to do?
Click to expand...
Click to collapse
is it in the fastboot folder ?

clsA said:
is it in the fastboot folder ?
Click to expand...
Click to collapse
Yes, see screenshot.

PrimalMK said:
Yes, see screenshot.
Click to expand...
Click to collapse
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?

clsA said:
is the command window in c:\fastboot ?
did you copy paste the command or try and type it ?
Click to expand...
Click to collapse
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?

PrimalMK said:
My bad. Managed to run it, but then it crashes straight away. Can that have anything to do with the driver not installed?
Click to expand...
Click to collapse
fastboot crashes ?
no if fastboot getvar worked it will all work
it's only 4 commands and your phone will be working
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
adb sideload rom.zip
sideload takes about 8 min

calculation icatkg
clsA said:
fastboot crashes ?
no if fastboot getvar worked it will all work
Click to expand...
Click to collapse
Restarted a couple of times etc. It worked. Will do the ROM thing now.

PrimalMK said:
Restarted a couple of times etc. It worked. Will do the ROM thing now.
Click to expand...
Click to collapse
great your about done ...your phone will be android 4.3 when it finishes
don't take any updates to the OS

cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:

PrimalMK said:
cmd said it sent the ROM to the phone. I was in the TWRP adb sideload on my phone when it was transferred. Then that was it. 100% on cmd. Phone shut down. Suddenly discovered I had to install on the phone. WAT. I do so, then wait until completion. I anxiously restart the phone. It's alive again!
Really, thanks so much clsA! You made me a very happy person! :victory:
Click to expand...
Click to collapse
no problem, hit the thanks button

Help finding M7 on Windows 10 to use ADB

Hi guys, I have been lurking for a while, but can't seem to find anything on my current issue. I am brand new to development and was able to sim unlock my old CM11 M7, reinstall CM11, and even rescue it from a bootloop through adb. That was all through windows 8.1.
I just bought a phone from ebay that is caught in a bootloop. No idea if USB debugging is enabled (does that matter for adb?), what ROMs were installed, etc. It looks like it's not rooted, but the Hboot says unlocked/tampered. I can access recovery (TWRP), fastboot/Hboot, but I cannot get my computer to recognize the phone in device manager (no misc. devices even appear when it's plugged in). I have tried installing various drivers, running/updating htc sync, and at one point, it even recognized the phone as a misc. device, but I wasn't able to do anything practical, nor replicate those conditions. I have windows 10 and have just wiped all of the htc programs.
Ideally, I plan to access adb, push a stock rom, check the imei (don't even know if it's stolen or not at this point), then find a custom rom that'll work with it (that still has ir blaster working).
My understanding is very limited, but I learn quick and would be very grateful for any help and insight into my situation!
Thank you very much for reading and for your time!

Install the drivers here. Then yes, you need to enable USB debugging for adb to work

Thanks to the mods who moved me here. I will post these questions in the Q&A from now on!
dd98 said:
Install the drivers here.
Click to expand...
Click to collapse
Thank you for the reply!
I think the cord was faulty, but device manager now sees my phone as an unknown device titled: "m7wls"
With everything HTC removed, I installed the driver you had recommended, but device manager still shows the caution symbol/"!" . I tried manually browsing for the driver and automatically searching, to no avail. I think I have found the unpacked version of the driver online as well, if it would help to put that somewhere and have device manager find that? I'm a little lost.
Then yes, you need to enable USB debugging for adb to work
Click to expand...
Click to collapse
This is disconcerting because I do not have access to a rom. Is there a way to enable USB debugging through TWRP? Here's hoping the last owner had it enabled :fingers-crossed:

Enigmatic Fart said:
Thanks to the mods who moved me here. I will post these questions in the Q&A from now on!
Thank you for the reply!
I think the cord was faulty, but device manager now sees my phone as an unknown device titled: "m7wls"
With everything HTC removed, I installed the driver you had recommended, but device manager still shows the caution symbol/"!" . I tried manually browsing for the driver and automatically searching, to no avail. I think I have found the unpacked version of the driver online as well, if it would help to put that somewhere and have device manager find that? I'm a little lost.
This is disconcerting because I do not have access to a rom. Is there a way to enable USB debugging through TWRP? Here's hoping the last owner had it enabled :fingers-crossed:
Click to expand...
Click to collapse
Ok well USB debugging is enabled by default in recovery and there is no way to toggle it anyway

dd98 said:
Ok well USB debugging is enabled by default in recovery and there is no way to toggle it anyway
Click to expand...
Click to collapse
Shameless bump!
Alright guys, I have the weekend to work on this project and I'm doing my research now.
In ADB, the phone does not appear in device manager, nor will it appear in command prompt; adb under devices. In fastboot, IT APPEARS (as "My HTC")!!! It also connects via command prompt; fastboot!
In recovery, it shows as m7wls.
I think I need to access adb to push a rom and cannot via fastboot, right? If so, is there anything else I can try?

Enigmatic Fart said:
Shameless bump!
Alright guys, I have the weekend to work on this project and I'm doing my research now.
In ADB, the phone does not appear in device manager, nor will it appear in command prompt; adb under devices. In fastboot, IT APPEARS (as "My HTC")!!! It also connects via command prompt; fastboot!
In recovery, it shows as m7wls.
I think I need to access adb to push a rom and cannot via fastboot, right? If so, is there anything else I can try?
Click to expand...
Click to collapse
If your using any TWRP version 2.8.3.0 and up, you can just drag and drop the file like normal. Just open Computer and you should see something like "One" or "MTP Device"

dd98 said:
If your using any TWRP version 2.8.3.0 and up, you can just drag and drop the file like normal. Just open Computer and you should see something like "One" or "MTP Device"
Click to expand...
Click to collapse
EDIT: disregard the following, TWRP is at 2.6.3.0
Ha, no way, that'd be way too easy! Uhh, but how? The phone appears in the device manager, but not as a storage device under my computer.
While in recovery, Windows device manager shows my phone as an exclamation point without a driver (after installing the latest one linked above) as "m7wls". I took it upon myself to do a manual installation (device manager>m7wls>update driver software>browse>let me pick from driver software on the computer>My HTC) and now it appears as "My HTC". This has not rectified the absence from my computer.
So back to the adb push idea: the phone appears in device manager as My HTC in fastboot and recovery, but does not appear at while in Hboot, for adb.

Enigmatic Fart said:
EDIT: disregard the following, TWRP is at 2.6.3.0
Ha, no way, that'd be way too easy! Uhh, but how? The phone appears in the device manager, but not as a storage device under my computer.
While in recovery, Windows device manager shows my phone as an exclamation point without a driver (after installing the latest one linked above) as "m7wls". I took it upon myself to do a manual installation (device manager>m7wls>update driver software>browse>let me pick from driver software on the computer>My HTC) and now it appears as "My HTC". This has not rectified the absence from my computer.
Click to expand...
Click to collapse
Download the latest TWRP image here(its 2.8.7.0) and flash it in fastboot and then you should have access to your internal storage using windows explorer

dd98 said:
See above post: can't post links on new account
Click to expand...
Click to collapse
I can do that...
Except, the only hangup is that I cannot push TWRP onto my phone without adb, right? fastboot will flash, but not push, I thought I had understood. I'm new though.
This is all a very strange and interesting process, so I really appreciate your patience and attention here, man (or ma'am)! It's some fun problem solving!
If I can push a file onto my phone, everything would be solved. The lack of rom, and lack of drivers seem to be the main issues.

You don't need to push anything on your phone if you're using fastboot. Just putt your TWRP.img in your adb folder on your PC and flash using flastboot flash recovery "recovery name".img. After that you just drag and drop ROM.zip using MTP in your recovery

donkeykong1 said:
You don't need to push anything on your phone if you're using fastboot. Just putt your TWRP.img in your adb folder on your PC and flash using flastboot flash recovery "recovery name".img. After that you just drag and drop ROM.zip using MTP in your recovery
Click to expand...
Click to collapse
Dude, I completely forgot you could do that. AAAAAGGGGGHHHHHH!!!!!!!! Lol, Ok, let me see what I can do and post back some results.
Thank you sooooo much again, you guys!

Alright, so for all intents and purposes, I'm up and running. I can swap the ROMs I need and do well enough with TWRP and Fastboot. Unfortunately, I still do not have access to my device in ADB. It still doesn't show in device manager.
I had thought that installing a sense ROM and plugging it into the computer would automatically rectify this, then I even plugged in a SIM card for a software update, but I guess they won't update a tampered device.
Where can I go from here? I assume that it's just Windows 10 compatibility issues?
EDIT: phone's rooted and unlocked bootloader.

Enigmatic Fart said:
Alright, so for all intents and purposes, I'm up and running. I can swap the ROMs I need and do well enough with TWRP and Fastboot. Unfortunately, I still do not have access to my device in ADB. It still doesn't show in device manager.
I had thought that installing a sense ROM and plugging it into the computer would automatically rectify this, then I even plugged in a SIM card for a software update, but I guess they won't update a tampered device.
Where can I go from here? I assume that it's just Windows 10 compatibility issues?
EDIT: phone's rooted and unlocked bootloader.
Click to expand...
Click to collapse
Now go to settings/about/software info and click on build number untill it says "you are a developer now". Then settings/developer optinions and enable USB debugging

donkeykong1 said:
Now go to settings/about/software info and click on build number untill it says "you are a developer now". Then settings/developer optinions and enable USB debugging
Click to expand...
Click to collapse
Yessir, no effect.
EDIT:Wait, for S&Gs, I tried "adb devices" while in the system of a sense rom and it shows, but as unauthorized. I'm going to play some more.
EDIT 2: Wiping everything and starting from scratch.

Bump again,
Back to ground zero:
I uninstalled all HTC programs and drivers
I reinstalled SDK and all the components
I have adb files placed in root of C:/
I installed the latest drivers
Device manager still only recognizes my android in fastboot, recovery, and system, but not ADB. (everything lists as android USB Devices>MY HTC
Phone is rooted, unlocked, and USB debugging is enabled.
What am I missing?
(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: 7.18.531.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
Maybe there are some other basics I am missing? I installed jdk previously before.

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

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

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

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

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

Delete please, forgot to quote/ reply.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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