Database Develop

My g1 no longer supports adb and fastboot via pc

NOTE: my problem is not like the other two threads where usb mass storage dosent work...
I can successfully mount my sd card on my pc via the notification ITS just the problem of developing/debuging connections made between G1 and PC
Somebody please help me I have adp1 when I bought all was fine but recently, don't know why bubuging dosent work means all adb and fastboot commands don't work on my g1 I have tried re installing the drivers but they fail to install so it hangs at adb devices or saying waiting for device. Also I have tried installing ubuntu to do that but here too it says the same stuff waiting for devices
Even the usb debug mode is enabled....
I have also tried flashing rc29 then other jf versions but can't flash system images via fastboot even flashed HSPL again n now I am trying to flash system image via update.zip
Is it
"format SYSTEM"
"Write_raw_image system.img PACKAGE:SYSTEM" SOMETHING LIKE THIS found in JF update script what I have to include in update script ???
Please help...[/B]

I have the same problem, I can mount the sd card but now the G1 won't let me use adb or fastboot on two computers where it previously did : /

go into control panel and go to Device Manager and try uninstalling the usb mass storage device that corresponds with your device, then unplug and replug the usb to your phone and let it reinstall the drivers and see if that fixes it...
-BMFC

you can't write_raw_image:SYSTEM through and update, I've tried it before and it fails (I'm trying to determine why). I'd recommend flashing another rom (you can still use recovery, right?) and then trying. Try JF 1.51 since it's known good.
What did you do to the phone before loosing adb and fastboot.
Also, have you tried "adb root" and then "adb remount"?

sangeet.003 said:
NOTE: my problem is not like the other two threads where usb mass storage dosent work...
I can successfully mount my sd card on my pc via the notification ITS just the problem of developing/debuging connections made between G1 and PC
Somebody please help me I have adp1 when I bought all was fine but recently, don't know why bubuging dosent work means all adb and fastboot commands don't work on my g1 I have tried re installing the drivers but they fail to install so it hangs at adb devices or saying waiting for device. Also I have tried installing ubuntu to do that but here too it says the same stuff waiting for devices
Even the usb debug mode is enabled....
I have also tried flashing rc29 then other jf versions but can't flash system images via fastboot even flashed HSPL again n now I am trying to flash system image via update.zip
Is it
"format SYSTEM"
"Write_raw_image system.img PACKAGE:SYSTEM" SOMETHING LIKE THIS found in JF update script what I have to include in update script ???
Please help...[/B]
Click to expand...
Click to collapse
I had a problem with adb awhile back it was doing the same thing what I did was read the hell out of threads and I used this tool called USBDeview. I opened up the program and anything that had android or htc I uninstalled all the drivers, then I rebooted my cpu and plugged my phone into usb cord and it worked. Here's the link to the app http://www.softpedia.com/get/System/System-Info/USBDeview.shtml try it out its worth a shot

lol. Funny how you guys try and help him 6 months later.
Im sure he figured it out by now since he had no follow up for such a long time.

some ppl just dont read thats sad...u rght now they want 2 help..maybe they need help themselves

Some help is better then no help

try this
you should uninstall it and the reinstall it but this time pick chose from Pacific location or something like that and chose the htc adb interface device with the green icon i believe it is like the second one or something on it this is on xp computers i forgot what it looked like on my vista computer

I have two phones. ADB works on one but not the other. I device manager, HTC Android Phone USB device shows up for both but ADB interface only appears for one phone but not the other.
What gives?

maybe u should try the steps again------->>> http://forum.xda-developers.com/showthread.php?t=532719

Need Help please [solved] !!!

I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do

Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !

I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!

priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk

priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that

OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..

priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...

[Q] Recovering files from broken phone

First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:

tuotanin said:
First of all, i have tried to solve this problem for hours and so far i don't have found anything that could help me.
So my screen is broken, completetely black, and i would like to save some files from my galaxy S(files are NOT on external SD card). Connecting phone to computer doesnt help because i should turn mass media mode on, and thats kind of hard when the touch screen is not working. Kies recognizes my phone(tries to connect), but can't connect because i should turn some other mode on? I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK http://developer.android.com/sdk/index.html
USB Driver http://developer.android.com/sdk/win-usb.html
1. Download and install this tool: http://de.codeplex.com/releases/view/107423
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card

cixty said:
Hi,
I have a solution for you
No need to turn on mass storage.
What you need:
USB cable
Working pc
Android SDK
USB Driver
1. Download and install this tool:
2. Boot your phone into recovery (worked for me) ( volume up+home+power)
3. Connect your usb cable
4. Start Droid Explorer and search for your sd card
Click to expand...
Click to collapse
Thank you for your answer. I think i can't get my phone into recevory mode. At least Droid explorer doesn't find it. When i try to boot it into recovery, my computer makes that "connected sound" several times, so i think the phone really is broken... Also, when the phone is connected to computer with usb cable, and i put the battery into the phone, i can hear that connected sound immediately, so i guess the phone automatically boots on? Well i keep trying but i think it is not possible to boot this phone into recovery mode

tuotanin said:
I have read that it could be possible to save files with ADB and i even tried but i didnt find any suitable instructions. So could anybody tell me how to save my holiday pictures :crying:
Click to expand...
Click to collapse
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!

2 Be said:
What you need therefore is a (rooted) phone and USB debugging must be enabled - at least I never tried withouit thos options turned on. Since you don't need to do sthg with su I think technically you can go without root as well, but did never run it without so not sure on that. Hope you had USB debugging active before your screen broke...
Install the adb tools on your pc if you haven't already. (google is your friend )
What you want to do now is connect your phone to the PC, open up a terminal session (within windows e.g. execute -> cmd ) and then fire up those commands:
Code:
adb
lot of stuff, ignore - if it doesn't work: google installing drivers and the adb tools
Code:
adb devices
here your phone should be listed if it is in debugging mode.
then just
Code:
adb pull [pathToYourHolidaypics] [pathToSaveOnHarddisk]
so for example:
Code:
adb pull /sdcard/DCIM Holidaypics
and you photos should be rescued. Good luck!
Click to expand...
Click to collapse
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.

tuotanin said:
Thank you for your answer. Unfortunately, this method doesn't find my phone either.. I think that USB debugging mode was on but can't say for sure. Maybe my Samsung is just completely broken. I guess we are out of ways to recover files . Thank you for your help and of course feel free to post anything if anybody have any idea.
Click to expand...
Click to collapse
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium

compacity said:
if usb debugging off, mtp still working so pc must detect ur fone unless its already not working.if pc recognised ur fone when plugged in, use any partition backup app in pc to backup da entire partition
n i m sorry if its doesnt help u
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It should be in USB storage mode. I dont know what mode is on atm. Even Kies doenst recognize phone

[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.

Solved [Q] How to copy files to my phone

Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud

When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste

L0rdNels0n said:
When you connect the phone to the PC - the phone will show its connected on the top (notification bar) pull that down and select /USB connected then choose
HTC Sync Manager
Now connect the phone to the pc and it will be seen as a media devise open it and in root copy the rom and anything else you need
leave the phone with that setting then when you need to move photo, music, docs or whatever its is just a matter of finding the correct file and copy/paste
Click to expand...
Click to collapse
Thanks, but your explanation is for normal usage, as said, I had a read-only system, this did not work for me.
I understand that the command adb remount did the trick, after that at least adb was able to do its task.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Ruud Westerhout said:
Hi all,
the question seems simple, but I am unable to solve it, would be very grateful for somebody helping me out.
I have an unlocked HTC One
Bootloader is working, OS is upgraded to 2.24.401.1
Recovery is installed and working TWRP 2.6.1.0
When starting the phone, the system asks to connect to WiFi but does not find a network in the air, hence I am not able to continue that route.
When connecting it to a Windows PC, it is recognized, the usual "drives"are mounted as the drivers are installed.
I see the HTC One but it is read-only and a file cannot be copied to it.
I tried to use the adb push xxxx /storage command but this also says the system is read-only.
I just lack the knowledge on how to continue, I cannot flash a rom as it is not copied to the device.
Please be so kind to guide me in the right direction.
Ruud
Click to expand...
Click to collapse
Do you have USB debugging mode activated when you connect to a PC?
Also you can adb sideload a rom when you are in recovery.

Thanks farang4u,
As I said, Matt helped me out and the last Wipe Data which I did this morning was also the trick, so now all seem fine with my phone again.
Thanks all.