My HTC ONE doesn't work :(

wpECy.png
 
You typed fastboot devicec instead of devices. You have to be careful when typing commands.

X out of the command box and reopen it. Type fastboot devices.

Jennifer Stough
Forums Moderator
Droid DNA
 
If that doesn't work, type

fastboot -w (this will wipe the device) and hit enter

Then type

fastboot update romname.zip



Jennifer Stough
Forums Moderator
Droid DNA
 
Hmm, I've never seen that error in adb before. Perhaps you should try a different USB port, if your using the ones on the case and not the motherboard they can give you problems.

If that doesn't work, try a new cable. In fact, are you using the stock cable? If your using a different cable other than stock, make sure it can transfer data as well, as most 3rd party cables are charge only.

Sent from my paranoid s3...
 
Alright, this is getting silly with the errors. Let's try to bypass this method entirely and just get your device functioning again, ok? Let's get the device into the bootloader by typing "adb reboot bootloader" without the quotes. Every command I'm giving you here will be quoted, but don't type the quotes in. After you're back to bootloader let's lock it back up with the command "adb oem relock". Now we can restore via a valid ruu file. These ruu files are handy as they require little to no effort to use. The following is a website that is hosting the ruu files:
AndroidFiles RUU

Go there and find the right ruu for your device. If you're having a problem figuring that out please reply with your carrier or whether or not you bought it unlocked international whatever and I'll let you know. In the event you just try one because you think it's the right one you'll be ok. If the ruu is wrong for your device it will do a check and fail before it does anything detrimental. Upon finding the correct ruu, I recommend STRONGLY that you keep it stored somewhere physical and in the cloud via Google Drive or Dropbox just in case you need it again.
After you have the correct RUU file, use adb to reboot into the bootloader and select fastboot with the phone attached to your computer (obviously). After you're in fastboot just execute the ruu file and let the computer and your phone do the work. The phone will recover itself to the stock state.
After you're stock and have the ruu, feel free to go back to modding if you feel comfortable doing so. Make sure you always backup your stuff in nand and you always wipe your data, cache and dalvik before flashing anything please. Let us know how it works out.
 
Alright, this is getting silly with the errors. Let's try to bypass this method entirely and just get your device functioning again, ok? Let's get the device into the bootloader by typing "adb reboot bootloader" without the quotes. Every command I'm giving you here will be quoted, but don't type the quotes in. After you're back to bootloader let's lock it back up with the command "adb oem relock". Now we can restore via a valid ruu file. These ruu files are handy as they require little to no effort to use. The following is a website that is hosting the ruu files:
AndroidFiles RUU

Go there and find the right ruu for your device. If you're having a problem figuring that out please reply with your carrier or whether or not you bought it unlocked international whatever and I'll let you know. In the event you just try one because you think it's the right one you'll be ok. If the ruu is wrong for your device it will do a check and fail before it does anything detrimental. Upon finding the correct ruu, I recommend STRONGLY that you keep it stored somewhere physical and in the cloud via Google Drive or Dropbox just in case you need it again.
After you have the correct RUU file, use adb to reboot into the bootloader and select fastboot with the phone attached to your computer (obviously). After you're in fastboot just execute the ruu file and let the computer and your phone do the work. The phone will recover itself to the stock state.
After you're stock and have the ruu, feel free to go back to modding if you feel comfortable doing so. Make sure you always backup your stuff in nand and you always wipe your data, cache and dalvik before flashing anything please. Let us know how it works out.

I would have suggest that earlier, but I didn't think using the adb command to relock the bootloader would work as adb wasn't properly detecting the device, only in sideload. I thought an error like "device not found" would be given.

It is definitely worth a try, though!

Jennifer Stough
Forums Moderator
Droid DNA
 
I would have suggest that earlier, but I didn't think using the adb command to relock the bootloader would work as adb wasn't properly detecting the device, only in sideload. I thought an error like "device not found" would be given.

It is definitely worth a try, though!

Jennifer Stough
Forums Moderator
Droid DNA

Yeah, I misread that fastboot was detected and not adb. Try it anyway and see what happens. If that doesn't work try to uninstall and reinstall the drivers. Also try launching command prompt as administrator in compatibility mode. I had to do that with Windows 8 to get adb to recognize my Note 2.

Sent from my HTC One using Mobile Nations mobile app
 
This is one reason I switched to Twrp. It has a swipe to confirm feature so you don't accidentally do something you don't want to do.

I'm trying to see what I can figure out, if anything comes up I'll let you know.

I'm also working on a simple to follow guide for the HTC one. I'll let you know when its finished.

Be glad you have people looking out for you like Jennifer. Hopefully we can get this figured out for you.

HTC One - ARHD GE 2.0 / ARHD 12.1 Bulletproof kernel
Nexus 7 - Cyanogenmod
Tab 2 7 - Cyanogenmod
 
Hmm, I've never seen that error in adb before. Perhaps you should try a different USB port, if your using the ones on the case and not the motherboard they can give you problems.

If that doesn't work, try a new cable. In fact, are you using the stock cable? If your using a different cable other than stock, make sure it can transfer data as well, as most 3rd party cables are charge only.

Sent from my paranoid s3...

yes i used stock cable , mmmm i think because i have mac and i used windows by parallels ...!?
 
Alright, this is getting silly with the errors. Let's try to bypass this method entirely and just get your device functioning again, ok? Let's get the device into the bootloader by typing "adb reboot bootloader" without the quotes. Every command I'm giving you here will be quoted, but don't type the quotes in. After you're back to bootloader let's lock it back up with the command "adb oem relock". Now we can restore via a valid ruu file. These ruu files are handy as they require little to no effort to use. The following is a website that is hosting the ruu files:
AndroidFiles RUU

Go there and find the right ruu for your device. If you're having a problem figuring that out please reply with your carrier or whether or not you bought it unlocked international whatever and I'll let you know. In the event you just try one because you think it's the right one you'll be ok. If the ruu is wrong for your device it will do a check and fail before it does anything detrimental. Upon finding the correct ruu, I recommend STRONGLY that you keep it stored somewhere physical and in the cloud via Google Drive or Dropbox just in case you need it again.
After you have the correct RUU file, use adb to reboot into the bootloader and select fastboot with the phone attached to your computer (obviously). After you're in fastboot just execute the ruu file and let the computer and your phone do the work. The phone will recover itself to the stock state.
After you're stock and have the ruu, feel free to go back to modding if you feel comfortable doing so. Make sure you always backup your stuff in nand and you always wipe your data, cache and dalvik before flashing anything please. Let us know how it works out.
i don't know which RUU file for my phone :(
my phone from T-mobile USA and i unlocked sim card via them , then i opend bootloader and installed recovery via this application
How to use Hasoon2000's All-In-One Toolkit - YouTube
 
I don't know how computer savvy you are, but you may want to try to download the ubuntu live cd and do this with Linux. I do not have much experience with Mac and adb error messages.
If you get the live cd and boot into it you can access the SDK on your Macs hard drive.

Sent from my HTC One using Mobile Nations mobile app
 

Trending Posts

Forum statistics

Threads
957,322
Messages
6,972,412
Members
3,163,761
Latest member
tao17