Database Info

i9023 - HELP! "No Boot or Recovery IMG & can't connect via USB

Hi guys,
I just have received a i9023 from a friend to repair. I put fastboot on and the device is unlocked, then I copied over Matr1x kernel via USB to the SD card and flashed CMW to recovery.
From here things went bad.
When trying to update the kernel to Matr1x, it showed that the file wasn't on the SD card anymore, so I tried to mount the SD card to copy it back, but it my computer wouldn't see it. Since then I tried many things to get the USB working - updating drivers etc... after awhile I decided to format SD card, which didn't help, so I formatted all the partitions on the phone.
Now, every time the phone comes on, it boots straight to fastboot, but also the PC will still not recognise the phone via USB.
I've tried getting into Download mode and using ODIN to flash a new kernel & ROM, but this wont work without USB working.
Can anyone help?
PS. I have read many other guides and posts, but nothing has helped.
Many thanks.

*Bump*

Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?

I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.

bedalus said:
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
Click to expand...
Click to collapse
Yes, I tried to mount as USB Storage in the Recovery Menu - didn't work, but now, I've only got fastboot - Booting up the phone normally jumps straight to fastboot, trying to boot into recovery doesn't work (just the fallen over Android pic with the red "!" on his chest).
I'm using Windows 7 and computer will not recognise the phone at all (it was working before this & the MicroUSB port is not damaged).
My GT-i9100 works perfectly via USB.
Piemo said:
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
Click to expand...
Click to collapse
If I can get it to connect to my PC so I can throw a stock ROM on there via ODIN I should be right (Pretty sure SAMFIRMWARE has some).

I've found often that the sdcard only gets mounted when you "choose zip from sdcard" in recovery. I panicked once with a galaxy s when I had forgot to put any rom on the sdcard and couldn't mount it subsequently. Ended up using heimdall with success. Also make sure you have latest version of fastboot, from platform tools 4.0.3.

Yeah, try Odin

If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!

twadda218 said:
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
Click to expand...
Click to collapse
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.

Can you try Ubuntu? Any luck with Odin?

KLoNe1 said:
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Click to expand...
Click to collapse
Does it say unknown device in device manager?
Sent from my ice cream powered Nexus S

I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file

KLoNe1 said:
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
Click to expand...
Click to collapse
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S

DarkhShadow said:
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes, I did - it said that this inf (driver) doesn't contain information about the device in question.

I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.

Many thanks for all your help everyone; unfortunately I still have yet to figure out how to get this working. Please keep throwing out your ideas
bedalus said:
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Click to expand...
Click to collapse
I gave this a go as it sounded like a great idea, but unfortunately it still isn't working.
I ended up deleting the drivers it was installing which wouldn't work & now it will only show up as 2x Unknown device under 'Portable Devices' heading.

I think you should try installing ubuntu, and the android sdk so you have access to fastboot again.

Getting ADB access in Android 4.2.2

This incorporates the ideas of http://forum.xda-developers.com/showthread.php?t=2144709, so if you want to see how this was resolved for the Nexus 4, check out that thread.
Okay. So you've flashed a spanking new 4.2.2 ROM and ADB no longer talks to your Sensation. What happened?
Well, the fact is that 4.2.2 is significantly more secure, in the good sense. It enforces RSA authentication via ADB. However, RSA authentication is supported only in recent versions of ADB.
What to do?
First, make sure you have the latest version of ADB on your PC.
On Windows you can quickly find out if you your version of ADB is up to date. Check your ".android" folder and see if it holds a file called "adbkey".
On any platform type "adb version" to verify that you have the latest version of ADB. Versions 1.0.31+ support RSA authentication.
-- So now, if you have ADB 1.0.31 or higher. You can skip directly to step 2, then.
-- If you do not have ADB 1.0.31 or higher, and you have the full Android SDK installed, open the SDK manager and update it. If you only have ADB and fastboot installed in a folder on your PC, overwrite files in the folder with those in the corresponding zip file attached (windows or linux -- sorry! I don't have Mac versions at this time). These come from version 16.01 of the android platform-tools package, if you are curious.
-- if you have never installed the SDK or ADB or fastboot, now is the time to do that. I recommend going to http://developer.android.com/sdk/index.html to get started.
[*]Enable USB debugging on your phone
USB debugging is now enabled by selecting Android Debugging in System Settings > Developer Options.
"I don't have the Developer Options items in System Settings!!"
In Android 4.2.x, you need to go to System Settings > About Phone and tap the Build Number item about 6 or 8 times, and Developer Options will reappear.
[*]Plug in the USB cable. Securely.
Dismiss the USB mass storage window.
"I connected the cable, but nothing happened!!"
Okay, chill. You won't get a response until ADB tries to connect to your Sensation. So go ahead and start ADB on your PC. Suggested command:
Code:
adb devices
"Now ADB started, but nothing's happening on my computer!!!"
Uh, didn't I just advise you to chill ? Take a look at your phone...
"What's this pop-up that just popped up??"
(See image below)
Congratulations, that is Android asking your permission to store an RSA key on your Sensation for ADB interaction with your PC.
Fearlessly accept it.
Hint: check the "Always allow from this computer" box to save time later on.
The RSA authentication key you just accepted will be stored on your phone in the file /data/misc/adb/adb_keys.
You are now good to go. Just 3 easy steps with a minimum of panic.
Questions? Problems? Ask away!
Many thanks to XDA member skipjacks for the idea for this post

Hi,
Nice! :good:
People should also not use USB 3.0 slots or USB hubs.
Try several slots if the front ones do not work.
Windows 7 & 8 drivers are HERE in case anyone needs them...

malybru said:
People should also not use USB 3.0 slots or USB hubs.
Click to expand...
Click to collapse
I understand about the hubs, but why not USB 3.0?

Skipjacks said:
I understand about the hubs, but why not USB 3.0?
Click to expand...
Click to collapse
Hi,
I have read a lot of instances of "Device not recognized" when using 3.0 slots.
I am not saying it will never work.
But ,if you use one,and it does not work,then,try it on a 2.0 slot.

Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.

onemanshow85 said:
Thanks for the post
few problems:
- I tried updating ADB with SDK manager. It kept saying something was accesing the installation folder. even after I closed explorer, virusscanner etc. I replaced the files with the zip attachement, but still a weird issue.
- another thing. Before I updated adb reported error: device offline. After update the issue persists. not using any hubs or USB 3.0. I think it's because I'm not using the stock cable that came with the phone.
Click to expand...
Click to collapse
Hi,
I think there is one solution that will address both issues. Before I mention it, let me ask: are you sure you enabled USB debugging on your Sensation? This is confirmed if, when you plug in the cable to your PC, you immediately get a USB debugging icon in the Notification Bar.
Glad we got that out of the way!
Unplug your device from the PC.
Anyhow, since you already have the SDK installed, the recommended way to update is to use the SDK Manager.
--in Windows, I think this is an executable in the tools sub-folder of your main android SDK folder. Double clock on it.
--in Linux, start up a terminal and type
Code:
android
if that doesn't do it, CD to the /tools directory in android-sdk-linux, or wherever you put the SDK, first. Then type "android".
The window that opens when you start SDK Manager should show that you need an update to (at least) platform-tools. Go ahead and do the update. You will have to accept some license(s) - accept it or them.
Once the install is complete, close SDK Manager.
Now plug your USB cable back in, and try out the "adb devices" command. It should work.
Suppose you still get "device not found", though. Try the following: again unplug.
Type the command:
Code:
adb kill-server
Now plug the phone back in, verify that you have USB debugging, and try "adb devices".
If no go, let me know what platform you are running, etc. I've heard it could be the cable, but I think that you just need to make sure it is plugged in securely.
BTW, the reason you probably won't have to do the adb kill-server step is that the SDK Manager kills running adb processes during the install.
Let me know how it goes!
Yrs,
dkephart
Sent from my HTC Sensation using xda premium

tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot

onemanshow85 said:
tnx. I was somewhat ehead of the steps you mentioned. problem was that SDK manager can't install anything cause it can't seem to kill any other adb proces. But I used a workaround for that so no problem there.
ADB does find my device, only it is stated as offline. I will have to try it again with the stock cable that came with the phone. Then I'll know if this is a software issue. Currently I'm using a complete random micro-USB cable wich I found on work laying around.
I'll let you know if stock cable is any difference. If so, it might be usefull info for ppl to know to always use stock cable while using ADB/Fastboot
Click to expand...
Click to collapse
Yeah... my random selection doesn't have this problem. But I once seemed to have it with the official cable. You might want to try rebooting both the phone and the PC.
Sent from my HTC Sensation using xda premium

The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.

onemanshow85 said:
The stock cable did the trick. everything works fine with the stock cable.
So if ppl find any trouble using ADB with a cable other then stock, this might cause the problem.
Click to expand...
Click to collapse
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium

dkephart said:
Great find...and extra points to anyone who determines why this might be the case...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Some really cheap cables only have 2 wires in them and can only be used for charging. You need the other wires for data transfer.
But some companies only put the charging wires in to save money on the copper.
It must be a REALLY low quality cable though. I mean I get all my cables on Monoprice for like $1-$2 and they all work great for data.
Or, the cable does have all the internal wires and one is just broken inside.
Sent from my HTC Sensation using xda app-developers app

I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.

nemovich said:
I've done everything in the thread, I can see my htc when I run the adb command but I don't get the pop-up on my phone. I tried the stock cable and different one but nothing. I'm on latest albinoman ROM. what should I do ?
P.S : I tried rebooting both the phone and pc but still the same problem.
Click to expand...
Click to collapse
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium

dkephart said:
You get your serial number and "device offline" from the adb devices command?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
no just the serial number

nemovich said:
no just the serial number
Click to expand...
Click to collapse
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium

dkephart said:
I'm puzzled, then. What happens when you do "adb shell"?
And if that comes back with the shell prompt (a $), then what happens if you type "su"?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
with adb shell I get $ and with su I get #.

nemovich said:
with adb shell I get $ and with su I get #.
Click to expand...
Click to collapse
Cool! Then you have adb working. To confirm, in the shell, "ls" should come back with a listing of the files on your device. If you do "cd sdcard" and "ls" you get the files on the SD card.
You're good to go.
Sent from my HTC Sensation using xda premium

Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Sent from my HTC Sensation using xda premium

nemovich said:
Yes it's working with shell commands but still not detected by Android Commander for example. It worked when I reverted to stock ROM.
I still don't know why I didn't get the security pop-up though
Click to expand...
Click to collapse
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium

dkephart said:
There is still a possibility adb did not update, or that you have more than one copy of adb on your system. Here's another way. cd to the android-sdk- windows folder (you are running windows, right?) and type
Code:
android update sdk --no-ui
...now the SDK manager will run. It takes a while. When done, reboot your PC and plug in your Sensation. Go to the platform-tools subfolder of your SDK folder and run adb from there. You could type "./adb" to make sure. Check your device - the homescreen has to be unlocked - and you should see the pop-up.
I don't really know about Android Commander, so there is always a possibility that that app doesn't handler things right, but I think this will work.
Let me know how it goes...
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
when I cd to the sdk folder ( C:\Users\Documents\adt-bundle-windows-x86-20130219), it gives me command not recognized. I can run sdk manager from the folder and everything is up to date.
I run adb from platform-tools and it gives me the same thing as before.
one thing though, I don't see the "adbkey" file in platform-tools but it is there in ".android" folder. so I run it from the later folder too but the still the same thing, no pop-up.
it's not just android commander, a lot of other apps give the same thing.

HTC Sensation Offline

Hi,
I am using htc sensation with vipers 3.1.2 rom with sabestian fm kernel. while playing with my phone, i've found out that my phone is offline. even though the usb debugging is enabled, my computer is not reading my device. i've installed the htc driver many times but it doesnt work. since my computer doesnt recognize my device, the adb is showing the device as offline. Plz help

huzefaonline said:
Hi,
I am using htc sensation with vipers 3.1.2 rom with sabestian fm kernel. while playing with my phone, i've found out that my phone is offline. even though the usb debugging is enabled, my computer is not reading my device. i've installed the htc driver many times but it doesnt work. since my computer doesnt recognize my device, the adb is showing the device as offline. Plz help
Click to expand...
Click to collapse
You need to get newer adb files. Since android 4.1 you need newer ADB files. Just download the sdk and extract the updated files. Also possible (if you have the SDK) is to open the SDK manager and download updated platform-tools.

astar26 said:
You need to get newer adb files. Since android 4.1 you need newer ADB files. Just download the sdk and extract the updated files. Also possible (if you have the SDK) is to open the SDK manager and download updated platform-tools.
Click to expand...
Click to collapse
ok. i am done with that. whats next? plz guide. need to get computer detect my phone as well. unable to install drivers.

huzefaonline said:
ok. i am done with that. whats next? plz guide. need to get computer detect my phone as well. unable to install drivers.
Click to expand...
Click to collapse
connect the device to pc
open a command prompt and do
adb devices
see if it detects it now
also install htc sync.it might help

rzr86 said:
connect the device to pc
open a command prompt and do
adb devices
see if it detects it now
also install htc sync.it might help
Click to expand...
Click to collapse
Yaay its working now thank you so much

huzefaonline said:
Yaay its working now thank you so much
Click to expand...
Click to collapse
so it was all about htc sync?

rzr86 said:
so it was all about htc sync?
Click to expand...
Click to collapse
Nops. i am downloading htc sync at the moment. i had the old file of the adb. updated that using the sdk manager, copied them to my android folder and then used cmd to link adb to phone. now the usb debugging is working fine

rzr86 said:
connect the device to pc
open a command prompt and do
adb devices
see if it detects it now
also install htc sync.it might help
Click to expand...
Click to collapse
i am having the same problem again even have the updated abd and installed the correct driver but my computer is not detecting my phone neither is adb detecting. help plz

huzefaonline said:
i am having the same problem again even have the updated abd and installed the correct driver but my computer is not detecting my phone neither is adb detecting. help plz
Click to expand...
Click to collapse
ok lets take things from the beginning again
check usb debugging mode
htc drivers
install/uninstall htc sync in any case
use usb 2.0 ports not 3.0
use also different usb ports
also try this app
https://play.google.com/store/apps/details?id=com.ramdroid.adbtoggle&hl=el

rzr86 said:
ok lets take things from the beginning again
check usb debugging mode
htc drivers
install/uninstall htc sync in any case
use usb 2.0 ports not 3.0
use also different usb ports
also try this app
https://play.google.com/store/apps/details?id=com.ramdroid.adbtoggle&hl=el
Click to expand...
Click to collapse
OK.
usb debugging is enabled but no enable sign on the rom and my computer doesnt show any sign on the computer.
htc drivers installed
htc sync uninstalled
using usb 2.0 port
have tried all the ports in system. none of them work.
Adb toggle app is also not working

huzefaonline said:
OK.
usb debugging is enabled but no enable sign on the rom and my computer doesnt show any sign on the computer.
htc drivers installed
htc sync uninstalled
using usb 2.0 port
have tried all the ports in system. none of them work.
Adb toggle app is also not working
Click to expand...
Click to collapse
install htc sync again
if fails then maybe something is wrong with usb
have you tried a ruu.exe?

rzr86 said:
install htc sync again
if fails then maybe something is wrong with usb
have you tried a ruu.exe?
Click to expand...
Click to collapse
ok. let me search xda for ruu.exe. btw whats it for?

huzefaonline said:
ok. let me search xda for ruu.exe. btw whats it for?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1672425
ruu.exe returns the device into completely stock situation as you bought it
but don't worry if you are on S-OFF you won't lose it
then see if you have better results with adb usb

[Q] HTC One X AT&T/Computer doesn't recognize phone

I have question.
I transferred everything to my sd card, there was a function to choose from my phone settings. Afterwards I connected my phone to my computer- which was always detected by my computer without a problem-to clean out some cache files from game folders, using total commander. While I was deleting the cache files I believe I accidentally deleted the sd card folder on my computer (which was associated with my phone.) I know this sounds kind of strange, but I do not have root access or any rights to deleting system files from my phone since my phone is locked because I have a contract with at&t. Now after resetting my phone 3 times, my computer fails to recognize my phone when I plug it in. When I plug my phone in, it charges but it is not recognized on my or any other computer for that matter. My computer states that there is an unknown device but not recognizing it as my htc. I located the unknown device on the device manager and installed all the drivers requested of me from the htc device sync manager folder and that still did not work. I have contacted htc directly and I have contacted at&t. They were not able to offer anything beyond doing another factory reset, which I have already done 3 times.
So my question, is there anything I can do? My phone works and charges it is just not recognized by my computer anymore and I cannot add music or anything. Since my warranty is up should I just unlock my phone and install the new android version? Any help or tips would be appreciated.

Have you tried uninstalling the drivers and then plugging the phone in
Sent from my VENOMized HoxL

area51avenger said:
Have you tried uninstalling the drivers and then plugging the phone in
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Yes. But nothing helped.

djrnz said:
Yes. But nothing helped.
Click to expand...
Click to collapse
A Ubuntu or any other LINUX OS may recognize SD CARD... Give it a try!
btw when you connect it and i assume you have Windows does it even show a semi transparent icon of Removable Storage?

1.What OS are you using on the computer?
2. Do you receive any sort of error messages from the cpu?
I have heard of corrupted or missing usb INF files on computers causing this exact same issue.
Sent from my HTC One XL using XDA Premium 4 mobile app

Sonone said:
A Ubuntu or any other LINUX OS may recognize SD CARD... Give it a try!
btw when you connect it and i assume you have Windows does it even show a semi transparent icon of Removable Storage?
Click to expand...
Click to collapse
it only says unknown device

Black!Jack said:
1.What OS are you using on the computer?
2. Do you receive any sort of error messages from the cpu?
I have heard of corrupted or missing usb INF files on computers causing this exact same issue.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
1. Windows 7
2. No report errors about that. Computer says: "unknown device" and that is all. I located the unknown device on the device manager and installed all the drivers requested of me from the htc device sync manager folder and that still did not work.

djrnz said:
1. Windows 7
2. No report errors about that. Computer says: "unknown device" and that is all. I located the unknown device on the device manager and installed all the drivers requested of me from the htc device sync manager folder and that still did not work.
Click to expand...
Click to collapse
Have you tried this
http://forum.xda-developers.com/showthread.php?t=1942519
Sent from my HTC One XL using XDA Premium 4 mobile app

Black!Jack said:
Have you tried this
http://forum.xda-developers.com/showthread.php?t=1942519
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I do not have root access. Phone is locked.

djrnz said:
I do not have root access. Phone is locked.
Click to expand...
Click to collapse
Since you don't have root access I'm assuming you do t have supercid or s-off. You could run the RUU. It will completely wipe and restore your phone to an original state. See the following thread:
http://forum.xda-developers.com/showthread.php?t=1671237
Scroll down and you will find a link for HTC OTAs and RUUs.
Or , as you mentioned at the end of your OP, you could just root your phone and install a custom Rom.
I hope I've helped in some way.
Sent from my HTC One XL using XDA Premium 4 mobile app

Trying to S-Off but keep running into walls.

Wow the threads make it look so easy but here are my steps so far and I'm a couple hours into S-Off but had to go through all this stuff (The basics I guess but this is my first time on android 4.4 so I was pretty lost.
1) First I found the XDA Developer link here which has a QR code to scan to download the file.
2) Realized I did not have a QR Scanner installed so I installed google goggles.
3) Scanned the code and realized it did not work and simply takes me to the xda developers forum
4) Searched for another link and found this one http://dottech.org/156395/how-to-roo...verizon-guide/ (This QR code works)
5) downloaded and installed the weaksauce exploit.
6) Decided I will backup my data on the phone before continuing .
7) Installed titanium backup
8) Was told to enable USB debugging
9) Found this can only be enabled if your phone has development mode enabled.
10) Searched for how to do that on this newest version of android and found this link. http://www.pcadvisor.co.uk/how-to/go...formance-mode/ which I was able to figure out the exact steps for the M* on my own.
11) In the newly unlocked developer options from the enabled USB debugging.
12) Titanium backup reminded me I do not have the paid version (but I do own a licesnse!) Need to copy the license file to the SD card.
13) Realized I don't have an external SD card installed.
14) Searched the house for a paperclip to pop out the SD card slot, no dice... Found a needle and trimmed the head off it with wire cutters, and popped out the door.
15) Installed the SD card!
16) Titanium backup says it cannot write to the external SD card (Well this is where I like to keep my backups not on the internal Card....)
So Starting from 18 how do I:
1) Use titanium backup to backup to my external SD card (No write permission). I have tried the SDFix application and that did not work. How do i get write permission to backup with titanium backup?
2) Where do I download the HTC M8 Drivers?

Ok so I guess I cannot backup the phone, lets say I will just skip the backup.
I'm trying to S-Off using the weaksauce method. I go to the folder where I downloaded firewater and type adb reboot and I get a message that my device is unauthorized..
What now?

Did you look here ? http://forum.xda-developers.com/showthread.php?t=2708628
Works great.

You can just use internal storage for your backup, once you get the phone s offed . Then do a backup to the external sd card. You need root access and a kernel without write protection. Take your time, it'll work.
Sent from my Nexus 7 using XDA Premium 4 mobile app

I would recommend watching some of these videos, they are very helpful.
http://forum.xda-developers.com/showthread.php?t=2697957

+1 on the videos well worth watching!
Sent from my Nexus 7 using XDA Premium 4 mobile app

Did you get it figured out? If you didn't and still need some help, send me a PM and I'll walk you through step by step and help you get it done. I've walked three people through the S-OFF method now (using Teamviewer and chat) and am getting pretty efficient at it. Shoot me a PM if your still stuck.

Watch this...
https://www.youtube.com/watch?v=sLtmwN1UyUU

I'm having the exact same problem. I rooted the phone thinking that's all I'd need to do. But with TiBu I can't backup to my SD card. So now I'm trying to do the S-Off so I can solve that problem. But I can't get the adb to work either.
I installed the HTC Sync Manager "package" from HTC, which allegedly comes with the driver. But, when I plug the phone into the computer it doesn't even see an adb device for my phone. I'm familiar with adb devices because I used it on my Droid Bionic.
Then I downloaded what has been nicknamed the "HTC One Toolkit M8" and installed the "Universal Adb Driver" from that. Still, no adb device is detected. Frankly, I'm laughing and disgusted with this phone. I'm laughing because someone with my prior skills with android should have no problem with this. But disgusted because this phone has been the most counter-intuitive phone I've ever owned. Just trying to disable the lock screen took almost 30 minutes.
Anyone know what I'm doing wrong? When I plug the phone in right now it shows up under "Portable Devices" and that's it. My Bionic would pop up 3 devices(CD-ROM, media device or something of that sort and the adb device).
I've literally spent the last hour searching with Google trying to figure out what I'm doing wrong. I thought it was a driver problem, but now that I'm not seeing any "unknown" devices nor am I seeing the adb device I'm convinced I've screwed this up somehow.
Yay me. I can't find my old account info, so 1 post for me.
Edit: Also, after installing the "Minimal ADB and Fastboot" as well as the Android SDK, the command "adb devices" has never found my phone. LOL

Just an FYI...the tool to open the SD card slot comes with the phone. It's the metal piece with the HTC logo in the packaging that the manuals come in. You'll have to pull that part of the box apart to get it out.

It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Pauls57 said:
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Also, if you have any other type of phone software such as pdanet installed on your computer, either uninstall it or close it before trying to run the exploit.

Pauls57 said:
It was suggested to first install htc sync manager with the drivers, then uninstall sync manager, but leave the drivers installed. Try that.
Click to expand...
Click to collapse
Yeah, I did that already. I'm convinced this isn't a driver issue since I never actually see the adb device(or an unknown device) in my device manager.
robocuff said:
Also, if you have any other type of phone software such as pdanet installed on your computer, either uninstall it or close it before trying to run the exploit.
Click to expand...
Click to collapse
I don't. I haven't gotten that far since I haven't gotten s-off done.

Are you using a USB 2.0 port on your computer. USB 3.0 will cause problems with ADB. What operating system does your computer have on it? Windows 8 doesn't seem to get along well with ADB either. Seems to work for some, and not for others.

Joshy8 said:
Yeah, I did that already. I'm convinced this isn't a driver issue since I never actually see the adb device(or an unknown device) in my device manager.
I don't. I haven't gotten that far since I haven't gotten s-off done.
Click to expand...
Click to collapse
That just seems to me that it IS more likely a driver issue. You should see your device name or at least unknown device. Open up your device manager, then unplug your phone and replug it in. See what it shows when it refreshes. It will be under portable devices or Android USB devices or both. Mine shows both. If you still need help shoot me a PM and I can walk you through.
robocuff said:
Are you using a USB 2.0 port on your computer. USB 3.0 will cause problems with ADB. What operating system does your computer have on it? Windows 8 doesn't seem to get along well with ADB either. Seems to work for some, and not for others.
Click to expand...
Click to collapse
Windows 8 doesn't have any problems with adb. I've used it flawlessly on several computers. USB 3.0 neither. USB 3.0 can however cause problems with Firewater running correctly.

nicholi2789 said:
That just seems to me that it IS more likely a driver issue. You should see your device name or at least unknown device. Open up your device manager, then unplug your phone and replug it in. See what it shows when it refreshes. It will be under portable devices or Android USB devices or both. Mine shows both. If you still need help shoot me a PM and I can walk you through.
Click to expand...
Click to collapse
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.

Joshy8 said:
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Click to expand...
Click to collapse
I don't know, I have had lots of driver issues on lots of devices and had to sort it out many times. Most notably was my Nexus 7 that thing was the hardest device to get drivers installed for, it took me hours. I've gotten pretty dang efficient at installing drivers nowadays though. I need more specific information about your set-up before I can really offer good advice though. The HTC Media Cd rom that you see pop up when you plug in is the CDROM.iso. It's just stupid HTC bloatware crap, you can disable it or delete it once you have root. When you plug it in you should see the CDROM popup on your desktop then it should mount as MTP too. You should be able to browse your internal and external storage.
One thing I would suggest though and you may think i'm crazy for it.. Swap the USB cable your using for a different one and try that on a different usb port. I've messed around trying to get drivers installed for hours, only to switch the USB cord and have it work just fine. I've even had this problem with brand new USB cords.
If you do still need help tomorrow don't hesitate to shoot me a PM, I would be glad to help.

Joshy8 said:
Right, you just argued why I don't think it's a driver issue. I've played with ADB before. I plug my Droid Bionic in and ADB comes right up on my desktop. On my HTPC that doesn't have the driver installed I get an unknown device.
But, with my HTC One M8, I never get any ADB device or an unknown device.. I get the HTC media device or whatever it is(mounts the storage on the desktop0, but I have *never* seen an ADB device or an unknown device from my HTC One M8... ever.
Thanks for the offer of the PM. I'm going to bed since I'm only 3 hours past my bedtime. But I'll PM you tomorrow and hopefully we can figure this out.
Click to expand...
Click to collapse
I don't know if this will help but I see you typing in adb device, it must be adb devices you must have the s.
Don't ask me how I know.

hager03 said:
I don't know if this will help but I see you typing in adb device, it must be adb devices you must have the s.
Don't ask me how I know.
Click to expand...
Click to collapse
Haha. I wont' ask. Thanks for the tip, but I am doing adb devices. It comes back and says something like "List of devices found" or something and then is blank. Of course, it works just fine on my Bionic.. haha. It's always listed.

This is going to be a silly question, but did you turn on USB Debugging in the developer options? Does the phone say USB debugging connected on the phone's notification tray?
You should either have unknown device or you should see it listed properly in device manager.
I would go through device manager and uninstall any devices related to the phone. When prompted I would also remove the drivers. Then follow the below guide.
http://forum.xda-developers.com/showthread.php?t=2742295