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 system without ROM on card. How to USB mount in TWRP?

I just loaded a new version of CM 10.1 on my sdcard ready to flash. I rebooted in TWRP, did the necessary wipes, then went to install my new ROM. Surprise, using Safari on Mac, it automatically opened the downloaded .zip file to a folder I didn't realize this as I was transferring, so now I have the extracted folder for my ROM, but the system can apparently only read .zips. So I am now without an OS. And no, I don't have a backup on the card. I just transferred it to my Hard Drive a few days ago to save on storage. But now I am VERY clear why it should stay on the card. Stupid.
I noticed that TWRP has a USB mount feature so I could copy over the proper .zip. But it won't mount on my computer (Mac or PC). In the console I see "E:Unable to locate volume information for USB storage mode." I tried getting into it via ADB, which worked before, but now it does not even list my device. Tried ADB side load, and it just never starts up on the Kindle.
I could never get fastboot to detect the device in the first place, so I haven't even bothered with any of that.
What can I do? All I want is to get my .zip back on the kindle. Or is there a way to .zip the extracted folder back into a .zip on the kindle itself with command line? Is there a way to install folders instead of .zips?
I've scoured several similar posts but nothing seemed to be resolved, or their fixes depending on ADB working.
Please help!

There isn't a way to re-zip a directory within Android in such a way that it can be flashed in recovery. You'll need to sort out your driver issue in Windows, or use the Mac (better choice anyway) to 'adb push' a new ROM to your sdcard.
Did you happen to wipe your internal storage before this happened?

soupmagnet said:
There isn't a way to re-zip a directory within Android in such a way that it can be flashed in recovery. You'll need to sort out your driver issue in Windows, or use the Mac (better choice anyway) to 'adb push' a new ROM to your sdcard.
Did you happen to wipe your internal storage before this happened?
Click to expand...
Click to collapse
When I did my wipe, I just followed the same instructions as when I did my original flash. Wiped system first, and then did the Factory Reset which includes data, cache and dalvik.
I tried plugging in the Kindle to my Mac while TWRP had the USB mounted, but nothing. I was just using the Android File Transfer for Mac that Amazon originally recommended when I first got it. That does not recognize anything now. Is there another way to access a Kindle on a Mac? Can you get Android SDK and run from a Mac Console command line? I thought all the commands were only for Windows. Does the Mac work better?
For my PC, I had the ADB drivers working fine before this. When I plug in now, I hear the windows SFX and it shows up in device manager as "Other Device" but listed as a Kindle. But the driver doesn't work, and it can't find drivers when I search. The Kindle used to show up as its own device with Android ADB under it. That never shows up anymore, probably why I can't do ADB commands.
But I think the computer is fine, because when I try to reinstall those drivers, it says they are already there. I'm guessing the Kindle itself is not allowing it to be recognized because there is no way to "enable ADB" in its settings since the OS is gone. I was hoping TWRP would have this built in.
I'm not sure why ADB Sideload doesn't work. It just sits there forever trying to start. I wish I could just push a new .zip that way. It's driving me nuts trying to figure out why nothing ADB works after the wipe.
Thanks

I downloaded the SDK for Mac and ran the ADB commands through Mac Terminal — it recognized the device! I never would have thought to try the Mac. Not sure why it worked differently, but it did. I was able to push a new ROM .zip through ADB and all is well.
Still not sure why I couldn't get the TWRP USB mount to work, but I learned my lesson, always keep a backup ON-CARD.
Thank you!

jhonny0099 said:
I downloaded the SDK for Mac and ran the ADB commands through Mac Terminal — it recognized the device! I never would have thought to try the Mac. Not sure why it worked differently, but it did. I was able to push a new ROM .zip through ADB and all is well.
Still not sure why I couldn't get the TWRP USB mount to work, but I learned my lesson, always keep a backup ON-CARD.
Thank you!
Click to expand...
Click to collapse
I assumed you already tried it on the Mac. But yeah....Mac is waaaaaay better at detecting the Kindle Fire than Windows.

[Q] URGENT No OS Installed

I rooted my KFHD and installed hashcode's 2nd bootloader and TWRP recovery. After I backked up my files in recovery I tried to reboot but it kept going back into recovery so i did a wipe and now when I try to reboot it says no OS installed and freezes at the blue Kindle Fire logo. The only thing I can do is go back into recovery. What do I do?

TWRP isn't the ROM file. You need to go and push the files to your Kindle. I did something similar (copied the unzipped files instead of just the zip). Unfortunately I am on mobile and not at home, or I would put in the link. Read through the recovery and help threads in the development thread and there are instructions on how to get the ROM zip on there. Then you should be fine.
Sent from my SCH-I545 using xda app-developers app

Here's the link: http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Thank you for the replies! But I figured it out on my own this morning . If anyone else is having this problem, here's how I fixed it:
I put my kindle into recovery and adb sideload then plugged it in to the computer. After the computer recognized it I went to the device manager and found it under unknown devices. I went into its properties dialog box and clicked update driver. I clicked browse my computer and then let me choose... Then I went into the Kindle Fire submenu and installed the ADB composite interface drivers and voila sideload started working for me!

k1llsh0t16 said:
Thank you for the replies! But I figured it out on my own this morning . If anyone else is having this problem, here's how I fixed it:
I put my kindle into recovery and adb sideload then plugged it in to the computer. After the computer recognized it I went to the device manager and found it under unknown devices. I went into its properties dialog box and clicked update driver. I clicked browse my computer and then let me choose... Then I went into the Kindle Fire submenu and installed the ADB composite interface drivers and voila sideload started working for me!
Click to expand...
Click to collapse
Glad you got it straitened out. Always keep a nandroid on your recovery. i imagine your "swiped" and cleared everything out. You can wipe Dalvik and CACHE anytime and be fine but swiping in TWRP is a factory reset.

[Q] KF7HD is stuck on twrp mode no os! any help?

So my kindle fire is stuck on twrp mode everytime i boot it. it first go to kindle with the "orange logo" then the "blue logo" i can hold the volume down to go to twrp recovery options and i can go to fastboot by going to "reboot" and "bootloader". How did this happen your wondering? Well i accidentally deleted my backup and the rom after i was done installing a rom, when i mount it i dont see it on my desktop, I click on the script while its mounting and it says "E:Unable to locate volume information for usb storage mode". it wont show the device on my windows 7 on "my computer" i downloaded the adb driver it detects the kindle and w/e but it wont show on my desktop so that i can transfer a rom into it and install it. If your curious of knowing what usb im using , its a galaxy s3 usb charger. It fits on the rear side of the kindle fire 7 hd and chargers...could it be that thats stoping my kindle fire hd from mounting? if it is then what other usb am i suppose to use to mount it or where can i find or buy one online or store? :crying:

Marckiscool said:
So my kindle fire is stuck on twrp mode everytime i boot it. it first go to kindle with the orange logo then the blue logo (twrp) i can hold the volume down to go to twrp recovery options but i accidentally deleted my backup and the rom when i mount it i dont see it, i click on the script while its mounting and i see "E:Unable to locate volume information for usb storage mode". it wont show the device on my windows 7 on "my computer" i downloaded the adb driver it detects the kindle and w/e but it wont show on my desktop so i can transfer a rom in it and install it. Of your curious of knowing what usb im using its a galaxy s3 it fits on the rear side of the kindle fire 7 hd and chargers could it be that? if it is then what other usb am i suppose to use to mount it or where can i find or buy one online or store? :crying:
Click to expand...
Click to collapse
Here is the tutorial to push onto TWRP. http://forum.xda-developers.com/showthread.php?t=2459498 Follow it and you will be back up in a short time.

Hey Thanks for the reply tho but The cmd doesnt seem to find the rom and its not working i tried to download his adb but my kindle wont install it

Marckiscool said:
Hey Thanks for the reply tho but The cmd doesnt seem to find the rom and its not working i tried to download his adb but my kindle wont install it
Click to expand...
Click to collapse
To CD into the directory you go into the folder where you put your extracted adb zip folder and ROM hold shift and right click on the mouse. Now left click on "open a command window here." Or you can CD from the directory directly. Use adb sideload rather than adb push. You want to copy the ROM into the same folder as the extracted adb folder because adb.exe is already in there and that's what you need for this procedure to work.
Here is a video that I think will help you a bit too. Short but very well done and very informative https://www.youtube.com/watch?v=CivvxcM1PCY He refers to the SDK tool folder. When he refers to that, you will refer to the extracted ABD folder. It takes a few seconds but soon you will see the flashing process in the form of a percentage.
Edit: When he refers to the USB drivers, thats what you use to get your device recognized. In command type adb devices. If you get waiting for device, you need to square that around first.

same thing wid nexus s
same thing happened to my nexus s. but when i type sideload or push it, it shows device not found. And when i type adb devices command it shows no devices please help, no os is there. i think there is any virus or any thing there which is stops it to connect. Kindly tel me if there is any file tht i can delete frm system and i can connect. Please guyx help me

Help with (I think) bricked Mi Mix

HI everyone, i have unlocked Mi Mix with EU Global ROM (rooted) and TWRP installed.
After the phone was playing up, I idiotically removed root and deleted Xposed, and it was OK, but tonight I tried to re-install originial ROM, and now can't do anything with the phone.
I can boot into TWRP, but when i try fastboot, the fastboor screen comes up for 20 seconds, then the phone boots to Mi logo, and nothing happens.
I can't get computer to recognize the phone so can't add new ROM - so unsure how to do anything now
Any help appreciated, thanks!
Jamie

Hello !! i think i can help you , well same thin happened to me and what i did was ----∑ Boot into recovery , plug your phone to computer , download Universal ADB Driver and when it detects Adb Composite click install . Then you will be able to unlock and use fastboot. Hope it helps if not im sorry , this is all i know. Good Luck !!!

If you are able to boot in to twrp why just install the original Chinese rom and start from scratch.

YazumiWuHung said:
Hello !! i think i can help you , well same thin happened to me and what i did was ----∑ Boot into recovery , plug your phone to computer , download Universal ADB Driver and when it detects Adb Composite click install . Then you will be able to unlock and use fastboot. Hope it helps if not im sorry , this is all i know. Good Luck !!!
Click to expand...
Click to collapse
Thanks, will try

jaime4272 said:
If you are able to boot in to twrp why just install the original Chinese rom and start from scratch.
Click to expand...
Click to collapse
Hey, thanks for the reply - in TWRP though I can't see any ROM files, or anything to install?

Download a ROM (from desktop)... boot to TWRP (device)... Mount storage... Copy Rom to device... Flash ROM...

lesscro said:
Download a ROM (from desktop)... boot to TWRP (device)... Mount storage... Copy Rom to device... Flash ROM...
Click to expand...
Click to collapse
Hi, thanks for the reply. the problem is, the computer doesn't recognize phone no matter what I do, and I tried the mount storage option but it only shows the phone internal storage!
Sorry, i'm new to this all, thanks,
Jamie

There is sdcard on Mix, then if you see internal storage you can copy rom on it then when u try to flash, navigate to this zip file...
Other u can flash using MiFlashTool using adb feature....

lesscro said:
There is sdcard on Mix, then if you see internal storage you can copy rom on it then when u try to flash, navigate to this zip file...
Other u can flash using MiFlashTool using adb feature....
Click to expand...
Click to collapse
Thanks! Yeah, I noticed it said SD card - but it's not removable, no? So i don't know how to put ROM onto it, when my computer doesn't recognise it!
Thanks
Jamie

When you boot into TWRP, try "adb devices" on your PC. If it's read there, you can use the "adb push filename.zip /sdcard/" command to push the ROM to your phone and then install it.

admirdante said:
When you boot into TWRP, try "adb devices" on your PC. If it's read there, you can use the "adb push filename.zip /sdcard/" command to push the ROM to your phone and then install it.
Click to expand...
Click to collapse
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie

Check if u have an issue with your driver when device is connected... device manager on windows 10...
If yes, check to install driver from computer (not from web or cd's or something like that), select universal USB/adb feature... and ur device will appear...

Weirdali said:
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Click to expand...
Click to collapse
Well, I use minimal ADB and fastboot too. Just run it, and try "adb devices". If it's read, you can try the "adb push". If not, please check your Device Manager to see if it is read there.

admirdante said:
Well, I use minimal ADB and fastboot too. Just run it, and try "adb devices". If it's read, you can try the "adb push". If not, please check your Device Manager to see if it is read there.
Click to expand...
Click to collapse
It doesn't appear in Device Manager, and it always has done before. I installed new drivers (made sure they were correct), rebooted PC, and still doesn;'t show in device manager, so not sure what top do!
Thanks,
Jamie

Weirdali said:
It doesn't appear in Device Manager, and it always has done before. I installed new drivers (made sure they were correct), rebooted PC, and still doesn;'t show in device manager, so not sure what top do!
Thanks,
Jamie
Click to expand...
Click to collapse
Damn. Not sure what to do either. Maybe download a fastboot ROM from their site and flash it trough Miflash? Maybe that'll work? If not, then I'm out of ideas.

lesscro said:
Check if u have an issue with your driver when device is connected... device manager on windows 10...
If yes, check to install driver from computer (not from web or cd's or something like that), select universal USB/adb feature... and ur device will appear...
Click to expand...
Click to collapse
I've 100% installed the right drivers, but the device doesn't show in device manager, or anywhere on my PC! It does charge though, which is weird

Weirdali said:
I've 100% installed the right drivers, but the device doesn't show in device manager, or anywhere on my PC! It does charge though, which is weird
Click to expand...
Click to collapse
if you have a usb OTG adapter you can put a rom on an usb stick mount it in twrp and flash from there

Did you do a total wipe? And left your device totally clean?

Weirdali said:
Thanks, is adb devices the same as mimal ADB and fastboot? As in, the program? I have that installed, although it can't find phone
And sorry for knowing so little, i don't have much Android experince.
Thanks,
Jamie
Click to expand...
Click to collapse
Put your ROM in the same folder as your adb drivers folder. Hold shift while right clicking in this folder and choose "open command window here". Boot into TWRP and goto "advanced", then "adb sideload". Now write in the command prompt "adb devices". It should now show your device id and "sideload" after it. Write "adb sideload name of your rom.zip"

At least your phone isn't totally dead like mine. I powered mine off with a full charge and we to power it back on a little while later and it's totally dead now. Even Xiaomi Flash Tool won't let me flash anything. Sees the phone but won't let me flash anything. I get an error code. Xiaomi, via email says they can't service my phone because I'm in the USA. This will be my last Xiaomi phone. So pissed off