Database Develop

[Q] Device not found on ADB | TWRP Sideload and CWM mount problems

My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?

Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again

NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.

You're welcome. glad it's all all OK for you

Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.

Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.

If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.

woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC

Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated

my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.

Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium

makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.

I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:

EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:

timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!

Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks

Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)

NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.

flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!

This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.

[Q] HELP! Wiped out all data, how to install a new ROM if:

Hey guys,
First of all I'd like to apoligize for my english skills and a thread if I've posted in a wrong one category.
However, I have REALLY serious problem right now and I'll try to explain. Today I decided to reset my phone (settings - back up & reset). This didin't help me as I was expected therefore I wiped out all the data by using TWRP(yes, I'm a noob). Thought that it will erase everything but the ROM. I tried to do a reboot and the phone did the htc quietly brilliant logo but got caught at the beats audio logo screen and never advanced.
Went into recovery and tried to do a factory reset, and a whole bunch of other things (tried to reboot system, but is says that no os installed). The phone still gets stuck at the same screen. Also, I am unable to get it to be accessible on my computer again. it says that installing new device but nothing happens, so I have no way how to get into sdcard and mount a new ROM or something. Is there any way how to fix it?? How to install a new ROM when USB not working and there's no way to take off SD card.....?

Nelayme said:
How to install a new ROM when USB not working and there's no way to take off SD card.....?
Click to expand...
Click to collapse
TWRP has an option to enable adb sideload. Then you can adb push rom.zip

BenPope said:
TWRP has an option to enable adb sideload. Then you can adb push rom.zip
Click to expand...
Click to collapse
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..

Nelayme said:
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..
Click to expand...
Click to collapse
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.

AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S

joselv456 said:
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
Another option is to just use an OTG cable and flash a ROM from a flash drive.

AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?

Nelayme said:
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?
Click to expand...
Click to collapse
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516

See this post, might help
http://forum.xda-developers.com/showpost.php?p=44730345&postcount=13

AllAboutTheCore said:
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516
Click to expand...
Click to collapse
Hey mate,
I just got OTG cable, moved a new Rom into USB stick and tried to mount on TWRP. All I got was "E: Unable to mount '/usb-otg'. Maybe I've missed couple of steps before?
FIXED: All I had to do is to format an USB stick in FAT32. Everything went well and now I can use my phone once again. Thanks a lot for your help, hope it will help to others as well.
Cheers!

[Q] Wiped all internal storage data and ROM HELP!?

I'm using twrp and i accidentally deleted everything from my phone, now my pc doesn't recognise it on usb.
Tried adb push and it says device not found.
Any way I can get a ROM on it or set it backj to factory settings?

Kaichu said:
I'm using twrp and i accidentally deleted everything from my phone, now my pc doesn't recognise it on usb.
Tried adb push and it says device not found.
Any way I can get a ROM on it or set it backj to factory settings?
Click to expand...
Click to collapse
Just because you wiped it, shouldnt have anything to do with the PC not recognizing it. Reboot PC, just in case and try again. (Was adb/fastboot working before? otherwise you may need to update your drivers).
Another way would be to use an OTG cable to flash the ROM directly from a USB stick.

Kaichu said:
I'm using twrp and i accidentally deleted everything from my phone, now my pc doesn't recognise it on usb.
Tried adb push and it says device not found.
Any way I can get a ROM on it or set it backj to factory settings?
Click to expand...
Click to collapse
What OS are you using? Have you attempted ADB while in twrp, just twrp, not sideload?

Kaichu said:
I'm using twrp and i accidentally deleted everything from my phone, now my pc doesn't recognise it on usb.
Tried adb push and it says device not found.
Any way I can get a ROM on it or set it backj to factory settings?
Click to expand...
Click to collapse
Unplug your phone
Reboot the phone and the PC.
Make sure your phone is in recovery mode.
Make sure the adb files and drivers are up to date.
Plug in the phone.
Open a command prompt in the folder that has your adb file.
Type:
adb devices
Click to expand...
Click to collapse
What is the return?
Sent from my HTC One using XDA Premium 4 mobile app

[Q] Updating TWRP

Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery

jaykspokane said:
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
Click to expand...
Click to collapse
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good

BD619 said:
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Updated the drives. In Fastboot now. on my cmd prompt c:\user\user wont tried typing and ADB Devices and nothiing

In fastbootusb type fastboot devices

BD619 said:
In fastbootusb type fastboot devices
Click to expand...
Click to collapse
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.

jaykspokane said:
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
Click to expand...
Click to collapse
PM me tomorrow and I'll help you out

BD619 said:
PM me tomorrow and I'll help you out
Click to expand...
Click to collapse
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?

jaykspokane said:
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
Click to expand...
Click to collapse
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb

BD619 said:
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
Click to expand...
Click to collapse
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.

jaykspokane said:
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?

BD619 said:
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
Click to expand...
Click to collapse
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache

jaykspokane said:
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
Click to expand...
Click to collapse
What does this mean?

BD619 said:
What does this mean?
Click to expand...
Click to collapse
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?

jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
Navigate to the platform tools folder
Press shift and right click inside the folder and choose open cmd here

jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.

jaykspokane said:
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
Click to expand...
Click to collapse
back to square one. LOL.
and no opening cmd from there did not work either

Check PM

I had a similar issue where I needed the updated twrp. I ended up using the original AIO toolkit that I used to root the phone/unlock the phone to begin with.
I found the latest version of the AIO (made by Hasoon: http://www.hasoon2000.info/getdownl...obile,ATT,Sprint)/One_All-In-One_Kit_v3.1.rar) and the latest image of TWRP from here: http://teamw.in/twrp_view_all_devices.
After installing hasoon, stick the downloaded image in the data/recoveries folder w/in the folders from the AIO. Next use the "Your Own Recovery" option under the flash a recovery option and choose that image instead. Worked great for me several times. Hopefully it does for you. Let me know if you have question.
BD619 said:
Check PM
Click to expand...
Click to collapse

[Q] Wiped everything > no OS

Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!

adb sideload

b0gd4n said:
Hey there.
Was playing around with recovery and managed to wipe EVERYTHING (yeah...I know... )
I now have no OS and, obviously, when I reboot I get stuck in a bootloop.
My question is how do I flash a rom onto it, as there is no sdcard slot?
Thanks in advance!
Click to expand...
Click to collapse
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot

1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).

rpmccormick said:
1) Go back into recovery (power on while holding vol-, then select recovery). Plug in to PC and use "adb push <rom>.zip \sdcard\(rom).zip. Flash.
2) ADB Sideload (don't know how to use personally).
3) Go back into recovery and plug in a USB flash stick (either an OTG flash that will plug right in, or a microUSB-to-FemaleUSB cable and any USB flash stick or hdd).
I don't understand why people are so in love with microSD, when hardly anyone spends the cash on a 64gb card so the built in 32gb is just fine. If you need removable media, you have it in a $1.99 otg cable and any flash stick (or even a 3tb usb-hdd).
Click to expand...
Click to collapse
clsA said:
you use adb from your adb / fastboot folder
TWRP / Advanced / Sideload
From PC adb /fastboot folder
you use
adb sideload name_of_rom.zip
or
just have TWRP loaded on the first screen and
adb push name_of_rom.zip /sdcard/
both ways the name_of_rom.zip needs to be in the same folder as adb / fastboot
Click to expand...
Click to collapse
BenPope said:
adb sideload
Click to expand...
Click to collapse
thank you all!!!

ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...

b0gd4n said:
ok, tried using and OTG cable...but it just broke when unplugged a driver from it...oh well.
Then tried booting into recovery, plugged in the the to my pc, started cmd as admin. now I can't find the phone.
adb devices returns an empty list.
Also tried starting adb sideload, but it just gets stuck at Starting ADB sideload feature. left it for up to 30 mins and nothing...
EDIT: also tried updating TWRP recovery. now I have 2.7.0.0 and I still have the same problems...
Click to expand...
Click to collapse
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.

BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...

b0gd4n said:
yeah, I tried that. every time I try to enable it, it gets stuck at "Starting adb sideload". Left if for 30 mins and still nothing...
Click to expand...
Click to collapse
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.

windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?

b0gd4n said:
aaah, so I don't have to wait for it to "start". OK then, I'll try this.
When I plug in the phone, Windows makes the "New device" sound, so I guess it does recognise it.
so it's adb sideload ....zip ?
Click to expand...
Click to collapse
yup.

BlockABoots said:
Yeah adb will not list any devices as USB Debugging needs to be enabled and as you dont have a OS installed you won't be able to enable it. Luckily you have the latest version if twrp install so you can use adb sideload from twrp, I think it's in the advanced tab. Start up adb sideload and make sure your Rom.zip file is in the adb folder on your PC and then type, adb sideload <name of Rom>.zip, and the sideload will copy zip file over abd install for you.
Click to expand...
Click to collapse
windieboss said:
a bit misleading it is, it wont come up with a msg started or something (in other words your waiting for nothing, its already running after the starting msg). Plug your phone in and start the adb sideload in cmd. Of course your system must recognize your phone else your will error out with no device found.
Click to expand...
Click to collapse
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...

b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
Same Problem here. No Solution?

b0gd4n said:
ok, booted to recovery > Advanced > ADB Sideload > now it ways "Starting ADB sideload feature..."
Plugged in the device, started cmd from adb folder. Doing adb devices here returns no devices...
Tried all USB ports, still none...
Click to expand...
Click to collapse
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command

BlockABoots said:
After you have started the sideloader server in twrp, just type adb sideload <name of rom>.zip and it will start sending the file. Dont bother trying to search for the device (adb device) as sideloader only understand the above command
Click to expand...
Click to collapse
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found

b0gd4n said:
doing just that:
start in recovery> start adb sideload (saying "starting adb sideload feature...") > plugged in (windows new device sound) > cmd with admin > navigate to sdk/platform-tools/ > and now I do the following command:
Code:
adb sideload filename.zip
and I get:
error: device not found
Click to expand...
Click to collapse
Hmmm, maybe try uninstalling all HTC drivers on the PC and then reinstalling.....
HTCDriver_4.2.0.001.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi (or x86 version if on win 32)
SyncManager_2.0.61.0.exe
found here, http://forum.xda-developers.com/showthread.php?t=2217396
http://www.mediafire.com/?o10b16j5b3r3o

try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)

I deleted os
Hello brother pls help me . I am sorry but i deleted is of htc one. Now can't anything . Here is the details
Twrp - yes
Hboot- unlocked tampered.
S-off
T-mobile htc one 4.4.2
Please help me . Here I saw many many expert so brother pls help me how to solve it & I can use my htc one .
Pls brother........
If someone can mail me in [email protected]
The details what to do. As I am really new & don't know what to do.
So again brother pls help.

windieboss said:
try the above. If that still fails then give this a go
http://koush.com/post/universal-adb-driver
(after again uninstalling htc drivers)
Click to expand...
Click to collapse
Whooo this worked!! Finally!!!
So I uninstalled all HTC stuff I had installed (drivers, sync manager, everything), then installed the stuff in the link.
Plugged in the HTC One in sideload mode and did
Code:
adb sideload filename.zip
and it worked!! Thanks again mate!