ok, ultra is toast.....ive looked around and it seems I can pull files off through adb using "adb pull". I don't know though where to direct adb to pull from though. this would work right? or am I being too optimistic....phone does connect through adb/ fastboot.
thanks!
**
nevermind, i changed out the busted screen with a screen from a different phone. recovered what i needed that way.
Related
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
bump. i also need this. btw have you tried using a script to do it?
danboard said:
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=698059
and especially did you install this driver?
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I do have read the thread and I have installed that driver. While in recovery mode using GOT's or OpenRecovery I notice that under device manager it says my phone is listed as "Android Phone" and if my phone is on and I connect it to my computer with USB debugging it lists it as "ADB interface". I can't get the phone to appear under adb devices while in recovery mode.
USB-Debugging active? (Settings-->Development)
It is when the phone is on, but what I am trying to do is push a file to the phone while its "off" in recovery mode so the usb debugging is irrelevant or so i believe.
Yes, sorry, you are right.
As I can remember, I have had a similar problem a year ago...
Try to copy adb into another directory and use it from there. Sounds stupid, but helped me in the past.
Sent from my Milestone using XDA App
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
danboard said:
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
Click to expand...
Click to collapse
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
micdim said:
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
Click to expand...
Click to collapse
Seems OK now. I just reinstalled official SDK.
dl.google.com/android/installer_r08-windows.exe
Getting the SDK installed didn't come without a couple issues, but I managed finally to get it working. Now, how do I transfer files to and from my g2x? I tried "adb push c:\users\eric\downloads\Pink Floyd /sdcard/music" and nothing happens. It doesn't give me some error in the command prompt or anything it just sits there indefinitely. I saw some videos that showed a success message after the files were transferred.
Should I be in "c:\sdk\" or "c:\sdk\platform-tools" to execute the push/pull commands? Does it even matter? I tried doing it from both and I got the same results from both. I'm thinking it's just something small that I'm missing, but unfortunately I can't seem to find what that may be. HELP PLEASE!
e4e5nf3nc6 said:
Getting the SDK installed didn't come without a couple issues, but I managed finally to get it working. Now, how do I transfer files to and from my g2x? I tried "adb push c:\users\eric\downloads\Pink Floyd /sdcard/music" and nothing happens. It doesn't give me some error in the command prompt or anything it just sits there indefinitely. I saw some videos that showed a success message after the files were transferred.
Should I be in "c:\sdk\" or "c:\sdk\platform-tools" to execute the push/pull commands? Does it even matter? I tried doing it from both and I got the same results from both. I'm thinking it's just something small that I'm missing, but unfortunately I can't seem to find what that may be. HELP PLEASE!
Click to expand...
Click to collapse
For ADB Push/Pull, I place my files in the "platform-tools" folder.
It should be something like this. -
cd \AndroidSDK\platform-tools
adb devices
adb remount
adb push Whatever.apk /system/app
adb remount
adb reboot
I was using the wrong slashes like a moron. Too much Sunday beer I guess.
Sent from my LG-P999 using xda premium
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
Does anyone know if its possible to pull pictures of a one x that wont boot it gets to the HTC one screen and freezes can it be done through fastboot ...phone is totally stock ......my wife is freaking out has pics on there she cant replace ..appreciate any help
You could try to boot into recovery and adb pull /sdcard/dcim c:\"location to photo folder"
Sent from my One X using Tapatalk 2
ok im a bit of a newb could you post more detailed instructions have used abd a little before but i have searched without finding any guides...it does seem to regocnise the device in adb just not sure of the exact commands
c:\android\bootloader>adb pull /sdcard/dcim c:\pictures
remote object '/sdcard/dcim' does not exist
is what i get if i try it
and like i said phone is stock no custom recovery so phone isnt recognised by adb when in recovery
It's kind of round about but you could unlock the bootloader. Install twrp. Then mount USB storage from twrp to access the ad card.
Sent from my HTC One XL using xda app-developers app
i need to keep it stock ...phone has locked up and they are replacing it need to get the pics off before i send it back to warranty ....so unlocked bootloader isnt an option
i think you'll find the adb shell (a linux shell essentially) is case sensitive, so try capitalising DCIM like this, you may have more success.
adb pull /sdcard/DCIM c:\pictures\
I hope that works for you mate.
edit: I just had a play around with this on my computer (windows XP) and it didn't seem to matter about the case, it might be worth trying it anyway, as there is no guarantee that other Operating Systems act the same. Good Luck getting your photos.
Hmm not getting very far with this but i had a thought ...is there a way to put phone in disk drive mode with adb ..if so i can use a cellbrite machine to get my pics ??? is this even possible ..ps i guess im learng some good adb stuff here so thanx anyway
so anyone have any ideas or if getting into disk drive mode is even possible using adb or fastboot ?????
No its not possible. The ways we said are the only ways you are going to recover your photos sorry.
Sent from my HTC One XL using xda app-developers app
Yeah, adb will only work if you have already turned on usb debugging in the developer options on the phone.
EDIT: Make sure you set up some sort of instant upload when she gets her new phone via dropbox or google+ or something.
if you can get into TWRP you may be able to mount the sdcard to be read from your PC, but I haven't really played around with this.
I posted this question over on Phandroids but this forum seems perhaps more appropriate. My Lenovo laptop running XP sees my phone just fine (Samsung Gravity Smart SGH-T589) and I'm able to transfer files to/from the phone. However, adb doesn't seem to be able to see it. A search about this problem turns up solution suggestions that mostly involve drivers, but my Samsung driver is up to date and clearly working (or else the phone wouldn't show up to Windows and I wouldn't be able to transfer files). My phone is rooted, which also makes it obvious that my laptop can talk to it just fine -- I used OneClick to root it last week using the same computer.
I'm using the DOS prompt (cmd) to run adb, and adb works fine. It simply doesn't see any devices. Here's an actual text transcript:
===============================
C:\Android\adt\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Android\adt\sdk\platform-tools>adb shell
error: device not found
C:\Android\adt\sdk\platform-tools>
===============================
Any ideas? I'm pretty new to this, so perhaps I'm missing something really simple. I hope so anyway!
--
Craig
Sunnyvale, California
Make sure that USB debuggin is enabled on your device. (This option should be changed only while device is disconnected from USB).
Also, try to restart adb server by killing it from the device manager.
Thanks for the suggestions. I had indeed already done both of those things. USB debug must be enabled to do file transfers, so I already knew it was definitely on. I still cycled it off/on anyway to make sure. And I did both kill-server and start-server commands as part of my checkout to assure myself that adb was in fact working correctly. I had Windows task manager up as well so I could watch adb disappear and reappear with those commands.
--
Craig
Sunnyvale, California
Hmmm... Try to reboot both your computer and device.
Have you tried to connect other devices to ADB? May be there is a problem with ADB installation?
Phone and laptop have both been rebooted many times. I also tried it with the phone in charge-only mode because that's what One Click Root required, but nothing changed. I also tried using all of the different USB ports on my laptop and tried two different USB cables, although that was silly because the phone is obviously talking to the laptop via USB. It shows up in file explorer, and I am able to transfer files using Windows drag and drop.
I'm afraid I have only one device, my recently rooted Samsung Gravity Smart phone, so I can't try it out on anything else.
I'm not sure how the adb installation could be at fault since the commands work as long as they don't involve the USB port. And I know that it MUST be possible to shell to the phone with what's already on this computer because One Click did it. I tried running the adb commands from the One Click Root > ADB directory just in case something about that particular install of adb was different, but I got exactly the same result.
It seems to me that I must be failing to do some setup step that an experienced Android developer might know about. I've never done anything like this before, so I wouldn't have even known about downloading the Android sdk if it weren't for forums like this! I sure appreciate the community of knowledgeable people here, who are clearly willing to help newbies like me.
If there are any software tools that anyone can suggest using to help me figure out what's going on, please let me know.
EDIT: Is there something that I need to load on my phone before adb will work? It occurs to me that OneClick might push something to the phone when it does the root, then delete it when the task is complete. I tried using QTadb, which is an adb GUI, and got the same result: no devices seen on the port even though Windows sees my phone and can talk to it via USB.
--
Craig
Sunnyvale, California