[Q] Recovering data from a broken Wildfire - Wildfire Q&A, Help & Troubleshooting

Hey guys. My Wildfire's screen doesn't respond to touch. Also the phone doesn't respond when I use the buttons at the bottom so I can't do anything. I want to try this
http://forum.xda-developers.com/showthread.php?t=1275680
but firstly I would like to recover the data on the phone. Obviously, I need to put the stuff on my computer using USB. But whenever I connect it to the computer, it goes into charge mode and doesn't mount as a disk drive. Is there anyway to get around this, given that the screen isn't responding? I'd mostly like to get the contact details, if possible. Many thanks.

deadman1206 said:
Hey guys. My Wildfire's screen doesn't respond to touch. Also the phone doesn't respond when I use the buttons at the bottom so I can't do anything. I want to try this
http://forum.xda-developers.com/showthread.php?t=1275680
but firstly I would like to recover the data on the phone. Obviously, I need to put the stuff on my computer using USB. But whenever I connect it to the computer, it goes into charge mode and doesn't mount as a disk drive. Is there anyway to get around this, given that the screen isn't responding? I'd mostly like to get the contact details, if possible. Many thanks.
Click to expand...
Click to collapse
are you s-on or s-off? if you have no touch input you are really gonna struggle. especially without root. does the trackball still work and do you have usb debugging on?

heavy_metal_man said:
are you s-on or s-off? if you have no touch input you are really gonna struggle. especially without root. does the trackball still work and do you have usb debugging on?
Click to expand...
Click to collapse
I haven't done any rooting or anything like that (I don't know much about it) so it must be s-on. The phone doesn't seem to respond to the trackball or the volume buttons either. I don't know if I have USB debugging on. I think I do. When I connect it to the computer the phone says "USB debugging connected" but I can't remember if I had it turned on or off in the settings. The computer recognizes it as "Android Phone" but, as I said, the phone is in charge mode and I can't access any of the files.

deadman1206 said:
I haven't done any rooting or anything like that (I don't know much about it) so it must be s-on. The phone doesn't seem to respond to the trackball or the volume buttons either. I don't know if I have USB debugging on. I think I do. When I connect it to the computer the phone says "USB debugging connected" but I can't remember if I had it turned on or off in the settings. The computer recognizes it as "Android Phone" but, as I said, the phone is in charge mode and I can't access any of the files.
Click to expand...
Click to collapse
Hmmm. OK, can you power off the Phone for me and then reboot with volume down held in and power at the same time.
This will take you to a white screen with info like s-off, s-on and hboot and a version number beside it. Can you share with me that Info please.
Then use the volume buttons to navigate the phone to reboot and use power to select. Then once it has rebooted connect it to the PC with the screen unlocked/awake and see if it pops up on the screen with USB debugging connected.
If we can security unlock your phone with revolutionary we will be able to add a custom recovery to your phone and make a full back up of your mobile. If USB debugging is not enabled you are stuck, and cannot retrieve anything from the phone before you ruu unless you are s-off already, (but that is very unlikely).
Your SD card can be removed from the back of your phone and with it all your pictures/music videos ect will be safe but your contacts are on the phone.
If you had the phone linked to your Google account it may be worthwhile logging in on the website and going to the Google dashboard. Find your phone on the list and your contacts "may" be backed up there if you enabled it during your initial phone set up.
Sent from my HTC Sensation using Tapatalk

Related

I think I bricked my phone :(

I tried to downgrade to a earlier firmware in hboot and it did everything it was supposed to and asked if I want to reboot. I said yes, and then it turned off and vibrated like it is turning on but nothing turns on the screen. My computer will beep like I added a device (when plugged into USB). I did the battery pull a dozen times and it still does the same thing. IOW, I cant even access recovery/hboot/etc because nothing at all shows up on the screen.
Any ideas?
SLCD or AMOLED?
I believe there were certain versions of HBOOT that won't install the correct display drivers for the SLCD version of the INC, so you're phone would be on and running but your screen won't show you anything.
Sorry I'm not more help
if it boots its not bricked
like toosurreal01 said you'll just have to install a hboot that is compatible with your screen. you'll just have to look at a few videos online to memorize the keypresses to install it blindly (should be pretty easy).
just have to push the hboot files to your phone through ADB after booting your phone normally since you can't mount USB. (unless you have it set to auto-mount).
Let us know how that goes and if you need more help!
You will have to use a computer to adb push the fix for this, If your phone was rooted and you have the adb drivers installed on a pc then just do this, turn phone off, volume down/power button like normal to access hboot ( even though you cant see it) plug into the pc, see if your pc lists it in the device manager. If so then all you need is a proper hboot to adb push from the pc to phone.
That sucks to brick your phone. Good to have s-off if you brick!
Sent from my Incredible using XDA App

Need urgent help accessing data on my rooted t989 with broken screen

My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk
CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.
slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium
try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.
To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.
THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.
Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.

HELP! Cracked screen, can't unlock to recover photos, etc.

Hello smart people. Hoping someone there has an idea for me...
This morning I dropped my GN and killed the screen. The display kinda-sorta works, but the touch sensor is non-op. OK, no problem, I've got in contact with Samsung and they'll fix it for the same price I can buy a replacement lcd/digitizer assembly anywhere I've found. Only problem: They'll be wiping the phone.
90% of what I need on the phone is synced to the cloud in one way or another, so I'm not too worried, but I WOULD very much like to recover some recent video and pictures that haven't been archived yet (daughter's dance recital). Phone is still working, except that it's pin-locked now (company policy) and I can't see the file tree to pull the stuff out.
Then I thought I'd play with the GN Toolkit. Only problem there is I guess I need USB debugging turned on, or something else I need enabled is disabled and I can't twiddle the menus to enable it.
Let's start with the obvious easy question: Any way to sync to the file system without unlocking via the touchscreen?
Failing that, is there any way to unlock/enable whatever I need to use the toolkit to pull the images out of the media directory?
I have a little time before I need to send the phone to Samsung for repair, so I'm willing to mess with this a bit and learn whatever I need to learn, but I'm not sure if what I need to do is even possible.
Thanks.
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
ÜBER™ said:
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Herbie555 said:
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Click to expand...
Click to collapse
Sorry wasnt aware of that. If you cant get it unlocked.. and USB debugging isnt enabled... then your outta luck.
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Is there another way for enable debugging on Nexus?
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Stadsport said:
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
There's a plug in for the SDK called screencast which let's you use your computer screen a duplicate screen to your Android device. You can select things with your mouse. We used to use it in the early gingerbread days of my old vibrant when recovery was hidden behind the double rainbow
Sent from my Sprint Galaxy Nexus CDMA using xda premium
mnoguti said:
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Click to expand...
Click to collapse
Debugging has to be enabled for ADB to be able to interact with the phone.
Glad I ran across this thread. I have a colleague in the same situation.
Stadsport said:
You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
Ahh, this might be a path to victory. Didn't realize I'd be able to do a factory reset and have stuff stay intact. Might be my best approach...
ÜBER™ said:
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Herbie555 said:
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Click to expand...
Click to collapse
Yes. And the only way to get anything to work is to have USB debugging enabled. Screen cast only works with adb enabled.
Looks like I might be boned on this one. Thanks much for everyone who had suggestions. Sounds like leaving USB debugging enabled might be a best practice from now on, eh? (Or at least making sure EVERYTHING syncs to the cloud automatically...)
Looking at the google policy manager, I can remotely: Lock the device (duh), Reset the Pin, make it ring, or "Wipe", which I'm guessing is a factory reset. Might try that as a last resort, but I'll remain hopefull.
I'm sure you've tried this - but if you''re on stock you may be able to boot into recovery using voldown + power (or is it volup+voldown + power? Not sure, can't remember). THEN plug it into your machine and see if it shows up in the toolbox as a connected device...
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
ipfreelytech said:
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
Click to expand...
Click to collapse
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Herbie555 said:
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Click to expand...
Click to collapse
Plug it in via USB and see if the Toolkit picks it up...
thepatman said:
Plug it in via USB and see if the Toolkit picks it up...
Click to expand...
Click to collapse
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Herbie555 said:
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Click to expand...
Click to collapse
Can't do adb in Fastboot mode. While in flastboot mode. Hit the volume up twice and hit the power button. This will boot into recovery. Then try using the
Code:
adb devices
command. If you get a gibberish code next do device ID. Then your good. Go ahead and
Code:
adb pull /sdcard/
Sent from my sprint galaxy nexus

[Q] s3 pictures with busted screen

S3 screen is totally dead including touch. We cannot enter the PIN to unlock the device due to dead screen. We need to get the pictures from the internal SDcard/built-in storage.
We tried booting into recovery mode (we used another S3 to test the timing since we can't see the screen). Once in recovery mode we used the Samsung Galaxy S3 Toolkit, it recognizes the device/serial number but trying to pull data it says "waiting for USB debugging" - how can we get past this?? I even tried with a working S3 and even in recovery mode it still says waiting for USB debugging.
How can we get to the files?
Thank you,
androidnoob10 said:
S3 screen is totally dead including touch. We cannot enter the PIN to unlock the device due to dead screen. We need to get the pictures from the internal SDcard/built-in storage.
We tried booting into recovery mode (we used another S3 to test the timing since we can't see the screen). Once in recovery mode we used the Samsung Galaxy S3 Toolkit, it recognizes the device/serial number but trying to pull data it says "waiting for USB debugging" - how can we get past this?? I even tried with a working S3 and even in recovery mode it still says waiting for USB debugging.
How can we get to the files?
Thank you,
Click to expand...
Click to collapse
Without usb debugging turned on, you won't be able that way (or any ADB based way).
You can try to get in recovery and mounting your sd card. (will have to use you other S3 to know how many times you need to go down).
One thing though, even with the PIN to unlock, when the phone is on and plugged to the pc, shouldn't you be able to see the storage?
damn PIN
BWolf56 said:
Without usb debugging turned on, you won't be able that way (or any ADB based way).
You can try to get in recovery and mounting your sd card. (will have to use you other S3 to know how many times you need to go down).
One thing though, even with the PIN to unlock, when the phone is on and plugged to the pc, shouldn't you be able to see the storage?
Click to expand...
Click to collapse
A computer can see the device but when you go into it no drives/shares appear until you enter the PIN in the phone, as soon as you enter the PIN the storage appears with all pics and such.
androidnoob10 said:
A computer can see the device but when you go into it no drives/shares appear until you enter the PIN in the phone, as soon as you enter the PIN the storage appears with all pics and such.
Click to expand...
Click to collapse
Ah ok. Well flashing a ROM will remove the PIN lock so that's another option (stock included).
Never tried, but just a thought: what if you connect USB keyboard through micro USB port, then enable Debugging.
Sent from my SGH-I747 using xda app-developers app

Options for Recovering Files & Phone Repair???

Today hasn't been one of the better ones this week. Putting aside my pride for a moment, here's what happened. In my frustration, I threw my phone into a cardboard box. Aiming for the side of the box...it ricocheted of the floor then the side. Yeah, not the best available option to vent!
So...screen spiderwebed and the screen will no longer turn on. Phone vibrates when the power button is used, yet screen is blank.
I'd like to ask for help for the following:
Retrieve several important files that weren't back yesterday: Pictures & program files not synced for privacy reasons, plus TWRP backup from a couple of days ago to internal memory b/c SD full.
Screen damage or more involved? To determine if I spend time fixing or buying a replacement phone.
Phone is the Canadian Koodo T989D running CM11 8/04 with TWRP 2.7.1
Phone Symptoms:
After removing and replacing battery
Pushing power button - Normal 'turning on' short vibrate, screen doesn't turn on (no light/pixels light up)
Recovery Mode - Normal Vibrate, release pwr button and again screen blank with exception of top Left corner showing multiple pixels, unrecognizable
Download Mode - Plugging in the USB cord causes the phone to vibrate every 2 or three seconds and the cycle repeats. vibrate...vibrate...vibrate...continuous
Any thoughts on troubleshooting to determine if retrieving files on the phone is still an option?
Would appreciate ya'll sharing your common knowledge that uncommon while I'm this frustrated. After switching to an AWS service provider (WIND) 2 weeks ago my backup phone isn't compatible - Galaxy Ace GT-S5830D. Thought it was until I tried, then realized it isn't. I'm kind of flustered that I acted so impulsively and doubly because I thought I had a backup phone, ughh!
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
MASTERBLASTER69 said:
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
Click to expand...
Click to collapse
Thanks for the educated guess and ADB suggestion to recover files.
Yes the computer shows 3 drives when attached in Recovery Mode. And darn it I can't remember if debugging on or off. The computer doesn't recognize the phone by default while in recovery mode. If this is the case, would ADB likely allow access to the phone? Not a tool familar with yet.
Unlikely that the battery is damaged if the phone turns on. Still stays cool while on or charging. Which is good news.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
the computer shows 3 drives when attached in Recovery Mode.
Click to expand...
Click to collapse
I don't understand why you see 3 drives... I'm sure Windows will ask you to insert removable storage if you try to access the drives, right? If that is the case, and you have no screen/touchscreen, only ADB will allow you full access to everything in the phone.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
Click to expand...
Click to collapse
Yes. Here's the tricky part though, in order to make adb work, your computer needs the right drivers for your phone.
I think you should try to follow the HOWTOS (How to Install Android ADB Interface Drivers) on installing the drivers for ADB.
If all goes well, you can check if it worked by typing 'adb devices' from the windows commandline. Then it would be possible to use adb to get your files back.
If the phone boots into the system...if, since you can't see it....you should be able to open the sd folder on your pc and simply copy/move what you want to the pc.
Just checking if you've tried this.

Categories

Resources