I have a problem. I have been passed a HTC Wildfire that has a big chunk missing, namely the touchy part of the screen On this phone is, apparently a photograph that I need to rescue or the world is going to end. The phone is configured to charge only when connected to a computer so I need to access the internal storage, whilst in recovery/fastboot and save the photo.
I have HTC Sync installed, the SDK too, but when I use ADB to list devices I see nothing.
Can anyone please point me in the right direction?
philskents said:
I have a problem. I have been passed a HTC Wildfire that has a big chunk missing, namely the touchy part of the screen On this phone is, apparently a photograph that I need to rescue or the world is going to end. The phone is configured to charge only when connected to a computer so I need to access the internal storage, whilst in recovery/fastboot and save the photo.
I have HTC Sync installed, the SDK too, but when I use ADB to list devices I see nothing.
Can anyone please point me in the right direction?
Click to expand...
Click to collapse
How did you save a photo on the internal storage?
More on topic:
If you know where it is you can use adb to pull it out.
Command to do this is:
"adb pull [location of file here]"
If you don't and you know the name, you can use the shell to "search for it"
command:
adb shell
now that your in the shell, use ls to list what's in the folder and cd [folder] to change the directory.
Thanks for your speedy reply!
It's not my phone, so I have no clue how a photo got on to the internal storage. Your response was very helpful, but at the moment I cannot get the device to list in "adb devices". Can you shed any light on that?
Try to turn it on and see if the trackball still works.
If it does, navigate to settings->applications->debugging and turn on USB debugging.
My apologies, I have just noticed I have posted this in the wrong forum. It is a Wildfire S not a Wildfire (no trackball). I will repost in the correct forum.
I did find another way...
but it requires you to install Ubuntu.
http://forum.xda-developers.com/showthread.php?t=981774
Related
Sorry, i know you must get this all the time guys, but i'm really struggling with rooting and such.
I'm on 1.72 and have no idea how to downgrade. I know you might say "read the guide" blah blah, but i don't understand it "Moron" i hear you saying. Anyway, Is there a complete noob guide for it anywhere? Like literally one that talks you through every step?
Also, my screen cracked, so i opened it up and replaced the screen myself, didn't have insurance or the £170 to have them fix it. Before the screen cracked it was doing this thing where it looked all psychedelic, Whites have blue coming off them, blacks have reds coming off them, that kind of thing. and its doing it again. This made me think it was a software issue, it happen to anybody else? I was thinking if i put a different rom on it, it'd stop, but i dunno. Anyway, thanks for any help anyone gives.
Does the screen replacement involve the flat ribbon cable between the screen part of the phone and the keyboard? I'm thinking it doesn't, but I'm certainly no expert. A damaged ribbon cable can cause colors to display improperly.
Nah, its attached to the screen so it was a new one.
The screen only comes with a small ribbon cable that connects to the pcb in the front half of the phone.
There is a larger ribbon cable that connects the two halves of the phone together, you can see it if you hold the phone halfway between open and closed. If this cable gets damaged, which happens easier than you may think then it can causes all sorts of things to mess up, including the colours on your display.
Unfortunately this cable is attached to the screen pcb so needs to be replaced as one unit.
So i'd need to replace my main pcb? Damn. Thanks for the help though! Could anyone help me with rooting?!
Sent from my HTC Vision using XDA App
at which point are you getting lost? sussed downgrading yet?
emdaftrave;14529179.Could anyone help me with rooting?! :D
.
Sent from my HTC Vision using XDA App[/QUOTE said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
Just have a search and there are numerous step by step guides, I was a total amateur and managed to do it, I think the hardest part to try learn would be using ABD (command prompt) and how to navigate to directories and push files but there are numerous guides on this forum so just pick your simplest and go for it!
elliott2705 said:
at which point are you getting lost? sussed downgrading yet?
Click to expand...
Click to collapse
Pretty much trying to install the sdk, i think im gonna reinstall it because its being a bit dodgy for me. But thanks for all the help guys!
Sent from my HTC Vision using XDA App
silverwind said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
can you use the SD card already in there as a gold card, or do you need a separate one?
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
emdaftrave said:
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
Click to expand...
Click to collapse
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
pmcqueen said:
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
Click to expand...
Click to collapse
ok, i've done it, thank you very much! now to just downgrade and root!
Ok so i'm using the XDA wiki guide on rooting, and i've got to the part where you move all the files onto the phone. Specifically, the files that aren't moving are:
$ adb push flash_image /data/local/tmp/
$ adb push su /sdcard/,
I'm getting a "Permission denied" error in command prompt. I also don't have an /sdcard directory on my phone, maybe thats why i'm getting an error?
EDIT: Never mind, i had the phone in Disk Drive mode when it wasn't supposed to be. Sorry for the double post.
So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.
If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.
Can someone guide me in the direction I need so I can do this adb reboot?
chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.
I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.
I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.
I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.
If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk
So I somehow managed to completely delete all the data on my sdcard through TWRP recovery when U was getting ready to flash PA 1.7. I have been flashing roms for many years and am now beating myself over the head considering I have never managed to do this before. So other than the fact that I have just lost an immense amount of important photos and data, I need some advice/help.
So to answer a few questions that I know will come up.
- I have not backed up my internal storage lately (I know *Rookie Mistake*)
Since this is the first phone I have ever had that doesnt have an SD Card is there a way to connect it to a PC and then run a data recovery program..All i really care about is the 1600 photos that I had on my phone of my kids.
My other problem is during this process i had factory reset which means there is no current ROM flashed to the phone so I cant usb mass storage through the rom itself. I have even tried to USB mass storage through the TWRP recovery but it is not working. So from what I can tell is I am screwed at this moment.Please I hope someone can shed some light on this situation.
Thanks
m4tt.03 said:
Since this is the first phone I have ever had that doesnt have an SD Card is there a way to connect it to a PC and then run a data recovery program..All i really care about is the 1600 photos that I had on my phone of my kids.
Click to expand...
Click to collapse
No, the internal storage can't be mounted so you can't run any recovery software on it. From this point forward I'd turn on Dropbox instant upload or Google+ instant upload to upload pictures. You can even set it to only do it on WiFi to save your data cap. It'll just back them up every night at home.
My other problem is during this process i had factory reset which means there is no current ROM flashed to the phone so I cant usb mass storage through the rom itself. I have even tried to USB mass storage through the TWRP recovery but it is not working. So from what I can tell is I am screwed at this moment.Please I hope someone can shed some light on this situation.
Click to expand...
Click to collapse
Just use ADB to send the ROM and GAPPS and other files to the phone.
Assuming you have ADB and drivers set up.... Connect to your PC. In the command line, type:
Code:
adb push FILE.zip /sdcard/
and let it go. You won't get a confirmation or anything until its complete. ADB is very slow. It'll take a couple minutes for a large (~200mb) ROM.
martonikaj said:
No, the internal storage can't be mounted so you can't run any recovery software on it. From this point forward I'd turn on Dropbox instant upload or Google+ instant upload to upload pictures. You can even set it to only do it on WiFi to save your data cap. It'll just back them up every night at home.
Just use ADB to send the ROM and GAPPS and other files to the phone.
Assuming you have ADB and drivers set up.... Connect to your PC. In the command line, type:
Code:
adb push FILE.zip /sdcard/
and let it go. You won't get a confirmation or anything until its complete. ADB is very slow. It'll take a couple minutes for a large (~200mb) ROM.
Click to expand...
Click to collapse
Well to be honest I assumed I had adb set up correctly. But for some reason when I plug in the phone, and open cmd prompt. I go to my platform-tools folder and type adb devices i get nothing listed under connected devices? It doesn't seem like my computer recognizes the phone anymore. OMG...so frustrating.. *im that guy now!!!*
m4tt.03 said:
Well to be honest I assumed I had adb set up correctly. But for some reason when I plug in the phone, and open cmd prompt. I go to my platform-tools folder and type adb devices i get nothing listed under connected devices? It doesn't seem like my computer recognizes the phone anymore. OMG...so frustrating.. *im that guy now!!!*
Click to expand...
Click to collapse
Well is ADB updated and installed properly? Do you get anything if you just type "adb" and hit enter?
Its probably a driver issue.
Ok so after a little messing around I was able to get ADB working and am currently pushin ROM files to the phone now. Appreciate the help!! Super bummed about the pictures but like a few of you have said this unfortunately my fault and nothing that can be done. Nowdoes anybody have any advice on how to tell my wife I lost over 1600 photos? She already gives me a hard enough time for always messing with my phone, this is only going to ammo to her already large arsenal. LOL
m4tt.03 said:
Ok so after a little messing around I was able to get ADB working and am currently pushin ROM files to the phone now. Appreciate the help!! Super bummed about the pictures but like a few of you have said this unfortunately my fault and nothing that can be done. Nowdoes anybody have any advice on how to tell my wife I lost over 1600 photos? She already gives me a hard enough time for always messing with my phone, this is only going to ammo to her already large arsenal. LOL
Click to expand...
Click to collapse
Glad it worked.
No idea on the wife front. GL with that.
Hi, great site you have here. I dropped my GS3 and broke the digitizer. The phone turns on, but has a blank screen. Of course I didnt back anything up to google or save my contacts to my sim. I tried using kies with my laptop and connected my phone, but it says my phone is locked. I enabled a swipe pattern on the phone before i broke it, but I cannot unlock it since the digitizer is not working. Is there anything I can do to disable it? Also, Samsung is quoting me about $175 ($65 for the digitizer, $100 for labor/shipping) to fix the phone, however they wipe then entire thing and of course all my contacts, pictures, music, apps and everything will be gone. If I cant get kies to work because the phone is locked, can you recommend a good place to purchase the digitizer? Is it difficult to install yourself? Thanks for all the help
You can use the "adb pull" command to pull any files/folders off your sd-card even with the screen lock (I've tested this). Install the android SDK and adb can be found in the platform-tools folder. Simply use the windows command prompt to pull the needed folders out. Sorry for your misfortune hope that helps.
illmatic24 said:
You can use the "adb pull" command to pull any files/folders off your sd-card even with the screen lock (I've tested this). Install the android SDK and adb can be found in the platform-tools folder. Simply use the windows command prompt to pull the needed folders out. Sorry for your misfortune hope that helps.
Click to expand...
Click to collapse
Thank you for the help. I will try and you tube how to do what you told me, as I know next to nothing about using computers in this way lol
xxH3llsp4wNxx said:
Thank you for the help. I will try and you tube how to do what you told me, as I know next to nothing about using computers in this way lol
Click to expand...
Click to collapse
No problem! Good luck, there are tons of videos/tutorials on how to set up the SDK. Just make sure to install the right drivers or else your device won't show up in ADB.
Just to simplify it a bit, I figured it might save you some time.
1. SDK installer file:
http://developer.android.com/sdk/index.html
2. Once you've got the SDK installed and configured open up "Command Prompt" (if on windows) (have your device on and at the lock-screen).
3. In command prompt, navigate to "sdk/platform-tools/" (or wherever you chose to install the SDK, just make sure to navigate to the platform-tools directory as that's where adb is located) (use cd command)
4. Next, type "adb devices" into command prompt to make sure your device shows up (it might be named something weird, don't worry)
5. Now, type "adb pull /sdcard/*FOLDERTOCOPY* (if you don't remember the names of the folders you can dump the entire sdcard)
This will dump your sd-card files to the "sdk/platform-tools/" directory.
Cheers.
wow, thanks for the time to write that out for me, it is greatly appreciated. I will try this out when i get home from work.
Wont identify my phone
Hello! It seems that I have the same problem. I have followed your directions. However, when I type "adb devices" the next line is blank. I do not think that it see's my phone. I have a Galaxy S3 on Verizon. I am running Windows 8. I have attached the phone through it's USB and the computer sees the phone.
Am I missing something?
Thank you
Hi. Most probably it is due to adb drivers not being installed. Download the galaxy s3 toolkit, and install the android drivers from within.
Toolkit:
http://forum.xda-developers.com/showthread.php?t=1746665
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have just posted this thread to another topic of whom the user may encounter a similar contacts lost situation.
Hope that would help him
I recently had to pull files from a gnote2 with a broken screen. With the lock enabled you won't have access to the files via adb unless you have a custom recovery installed. What I did was enter download mode and then Odin an insecure boot loader. After that I was able to use adb to pull the files.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
illmatic24 said:
No problem! Good luck, there are tons of videos/tutorials on how to set up the SDK. Just make sure to install the right drivers or else your device won't show up in ADB.
Just to simplify it a bit, I figured it might save you some time.
1. SDK installer file:
http://developer.android.com/sdk/index.html
2. Once you've got the SDK installed and configured open up "Command Prompt" (if on windows) (have your device on and at the lock-screen).
3. In command prompt, navigate to "sdk/platform-tools/" (or wherever you chose to install the SDK, just make sure to navigate to the platform-tools directory as that's where adb is located) (use cd command)
4. Next, type "adb devices" into command prompt to make sure your device shows up (it might be named something weird, don't worry)
5. Now, type "adb pull /sdcard/*FOLDERTOCOPY* (if you don't remember the names of the folders you can dump the entire sdcard)
This will dump your sd-card files to the "sdk/platform-tools/" directory.
Cheers.
Click to expand...
Click to collapse
Thanks for this, I've just recovered data from a Galaxy S2 using this. I was able to activate USB debugging using blind touches, based on a video, and recovered the sdcard using
Code:
adb pull /sdcard/ MYFOLDER
Yea what people seam to forget is that adb only works if it was enabled on the device before hand....
Sent from my ATT Samsung Galaxy SIII using TapaTalk
broken screen with screen lock on, trying to use Kies as a tempory remote terminal
Hi all,
I have the Galaxy S3 SGH-I747, and this morning I managed to break the LCD. The digitizer isn't cracked, but seems to be unresponsive.. I'm not with any of the major carriers, I have GCI in Alaska. I'm on the road, away from home, working. I should be able to get a new case when I get home. Which will be in only 4 days, luckily.
I was also hoping I could use Kies essentially as a remote terminal to send SMS or make calls just until I can get home and replace the case. (Which in my mind is actually an easier quicker repair than the screen digitizer replacement, just not always quite as cheap.)
I have ADB, I'm just not an expert with it. Is there a way to use it to disable to lock screen, even temporarily, so I can use the GUI in Kies? Is there any was to turn on the Bluetooth perhaps? I already have the partnership established with my Laptop, and is set up to connect without confirmation. I might be able to figure out a way to get some sort of functionality out of it until I can get it repaired.
Yea what people seam to forget is that adb only works if it was enabled on the device before hand..
Click to expand...
Click to collapse
I don't think I have connected this phone with the ADB yet. I also didn't have the USB debugging mode enabled. Am I SOL getting it connected with the ADB, then?
Hi illmatic24. I need a help - I have a Samsung E7 - broken lcd, forgot the password and usb debugging mode is off. Is there anyway through which I can recover my phone's content? I want access to my internal storage memory. Any help will be much appreciated. Thanks, Ritz
Hi all,
Yesterday I got a Desire from my friend. The screen is broken, so it is full black, but the phone is working. He would like to backup the data from the phone. Unfortunately the phone isn't rooted, so the QtADB don't working.
I tried any command in fastboot with usb connection from my windows 7 x64 machine, and it seems the computer can see the phone.
If I write in a command prompt "fastboot devices" then I see HT03SPL0184.
But after a normal start the computer doesn't see the phone. A tried with "adb devices" but the list is blank.
If I checked the windows Device Manager, then I see only a new item, under "Portable devices", a new drive "J:", nothing others. The phone is working, because if I try to call the Desire, the phone is ringing.
Hereby I'd like to tell, that I manage my Sensation since two years success, It means I see my Sensation with adb shell too. Of course my Sensation is rooted, and under Device Manager I see by the "Portable devices" also a new drive, but I see another item too: "Android USB Devices -> My HTC".
Why cannot I see by Desire the My HTC item? Perhaps because of it isn't rooted?
Can you help me? Have you got any idea, how can I backup a whole system partition (or at least the /data) by a non-rooted Desire?
Thx!
blackdog7 said:
Hi all,
Yesterday I got a Desire from my friend. The screen is broken, so it is full black, but the phone is working. He would like to backup the data from the phone. Unfortunately the phone isn't rooted, so the QtADB don't working.
I tried any command in fastboot with usb connection from my windows 7 x64 machine, and it seems the computer can see the phone.
If I write in a command prompt "fastboot devices" then I see HT03SPL0184.
But after a normal start the computer doesn't see the phone. A tried with "adb devices" but the list is blank.
If I checked the windows Device Manager, then I see only a new item, under "Portable devices", a new drive "J:", nothing others. The phone is working, because if I try to call the Desire, the phone is ringing.
Hereby I'd like to tell, that I manage my Sensation since two years success, It means I see my Sensation with adb shell too. Of course my Sensation is rooted, and under Device Manager I see by the "Portable devices" also a new drive, but I see another item too: "Android USB Devices -> My HTC".
Why cannot I see by Desire the My HTC item? Perhaps because of it isn't rooted?
Can you help me? Have you got any idea, how can I backup a whole system partition (or at least the /data) by a non-rooted Desire?
Thx!
Click to expand...
Click to collapse
Most pobably the Desire doesn't have USB Debugging enabled.
abaaaabbbb63 said:
Most pobably the Desire doesn't have USB Debugging enabled.
Click to expand...
Click to collapse
Oops, and have you got any idea how to turn it on by the blank screen?
blackdog7 said:
Oops, and have you got any idea how to turn it on by the blank screen?
Click to expand...
Click to collapse
Well, it isn't easy at all, and you'll have to blindly activate it. Take your Sensation, and put the earliest Sense version you can. Then, take the Desire and put them both one by another. Now, you enable USB debugging on the sensation, and in the same time you do the exact same movements and touches on the Desire. Hopefully, it will somehow work...
abaaaabbbb63 said:
Well, it isn't easy at all, and you'll have to blindly activate it. Take your Sensation, and put the earliest Sense version you can. Then, take the Desire and put them both one by another. Now, you enable USB debugging on the sensation, and in the same time you do the exact same movements and touches on the Desire. Hopefully, it will somehow work...
Click to expand...
Click to collapse
hehe good thinking batman :cyclops:
@op if that dont work then tell ur friend to take phone to a phone repair shop and im sure they can pull all the data off it for a few euro.
Adb doesn't work in fastboot, however it should work fine in recovery mode. Boot into hboot, wait for a bit, then press volume down once to highlight recovery, and finally press the power button to select it. Try adb devices from there.
chromium96 said:
Adb doesn't work in fastboot, however it should work fine in recovery mode. Boot into hboot, wait for a bit, then press volume down once to highlight recovery, and finally press the power button to select it. Try adb devices from there.
Click to expand...
Click to collapse
Yes, I know, you must right, but not now... I tried it of course, but the results is the same I have only a blank list after command "adb devices". If I have a CWM, then in recovery mode should be working all fine. But I haven't got CWM.
I tried installing a CWM. But it is failed too. For installing a CWM is beginning that I must to set up the debugging mode... What I cannot.