Database Develop

SanDisk16GB Micro SDHC won't read on mac os or android phone. Help!?

This memory card has been used in my Nexus One Android running Froyo. I was using the phone last night (specifically FourSquare) and it froze up, I'm not sure if it was writing something to the micro sd but I removed the battery to restart the phone. When it restarted it said "checking memory card for errors", but after waiting for ten minutes nothing was recognized and I restarted it again, this time removing the sd card. Fast forward a few hours. I tried repeatedly different methods to get the phone to recognize it and finally gave up. I put an older memory card in the phone which worked just fine.
I have a usb micro sd reader and plugged it in to the mac. Usually iPhoto pops up but nothing happened. I ran disk utility to see if the memory card could be recognized and still nothing. I tried many free software programs but they all require the memory card to at least be recognized, which mine is not. Any Ideas? I've ran out of them. I just want a few pictures and a video but if thats not possible at least a way to reformat sd card for future use.
Cliffnotes: Card corrupted by android phone, no longer recognized by phone or mac os, tried several sd recovery programs to no avail, I just want the pics!

Sounds like it's not corrupted, it just died. Sorry dude. Time for a new card.

Had my 8 gig die the other night. Mine is recognized when I put it in my laptop but when ok try to copy any file, it can't access. It does see all of then though. I've been trying some recovery software but haven't had any luck so far.
-------------------------------------
Sent via the XDA Tapatalk App

j.bruha said:
Sounds like it's not corrupted, it just died. Sorry dude. Time for a new card.
Click to expand...
Click to collapse
Thanks. You're probably right. I guess this is where the iPhone has an advantage over us Android users. Permanent on board storage.

r3vmixman said:
Thanks. You're probably right. I guess this is where the iPhone has an advantage over us Android users. Permanent on board storage.
Click to expand...
Click to collapse
So if that storage goes out, you replace the whole phone. Sounds like quite the advantage...
Versus cheap expandable memory. Hmm.....

Ok I found a half satisfying solution. The sd card reader has a lock switch. When I click lock I am able to read everything, thus letting me copy it to my computer. I guess putting it in lock mode makes everything read only. The card is still dead, imo. No way to reformat it in this mode and removing the lock switch only reverts to my prior problem.

r3vmixman said:
Ok I found a half satisfying solution. The sd card reader has a lock switch. When I click lock I am able to read everything, thus letting me copy it to my computer. I guess putting it in lock mode makes everything read only. The card is still dead, imo. No way to reformat it in this mode and removing the lock switch only reverts to my prior problem.
Click to expand...
Click to collapse
That means your card is dead. When a flash card dies, it cannot be written anymore, but it can still be read from because the data is still there, it's flash memory so its nonvolatile. By forcing it to read only mode, you should be able to recover your data, like you just did.

Awesome suggestion on setting to read only. It worked for me too. I'm happy to at least get the stuff off it, even if it's dead.

FINAL ADB SOLUTION: For those who couldn't get ADB with Recovery

1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. Start and loop (you can start this before now if you wish, just has to be before entering recovery)
9. After the phone scans the sdcard choose "Recovery" and press the Power button.
*10. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
11. Now go get Rooted using the steps on the first page of this post.

dymanese said:
1. Install HTC Sync 2.0.25 onto your PC (it came with your phone) (maybe the custom driver works but I haven't tried it yet)
2. Power off your device
3. Remove the battery
4. Plug in your USB cable
5. Insert your SDcard (any kind, it doesn't matter the type, i have 6 different cards and class associations in my possesion and have rooted all of my co-workers DI's today using all 6 cards for proof of concept, 9 phone total [Everyone wanted Wireless Tether)
6. Insert your battery
7. Hold Vol. Down button + Power button
8. After the phone boots up and scans the sdcard choose "Recovery" and press the Power button.
*9. SOLUTION: As soon as the white screen appears just casually (don't be a speed demon) click IN & OUT your sdcard and continue to do so (keep clicking it) when the black screen with triangle appears. You will be listening for the last windows chime that identifies the USB has registered. But, you want to stop with your last sdcard click IN just before the last windows chime is sounded through your PC speakers. You might need to do this a couple times just to get familiar with the timing of the windows sounds on your computer system. Those phones that don't have to do this and was rooted first have a much earlier timing of when the Exploit is active.
10. Now go get Rooted using the steps on the first page of this post.
Click to expand...
Click to collapse
is this while running loop.bat? it didn't say

vzw said:
is this while running loop.bat? it didn't say
Click to expand...
Click to collapse
yes run the loop.
I tried this for about an hour with no result btw.

Worked for me

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it SHOULD NOT involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.

Seriously , this is the EXACT same steps that has been posted numerous times before. When you speak of a Solution as something Final it should involve trial and error steps that require timing or just *luck*.
What a waste of a post and thanks for im sure getting peoples hopes up.
Click to expand...
Click to collapse
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App

Ouch.... Burned by last post
dymanese said:
Yes you run the loop but not necessary to run in a loop. Yes it is about timing and similar posts have been made but I think I've written it with more detail.
These precise steps worked with the exact timing on 8 DIFFERENT phones yesterday. If its not working for you then perhaps you don't know how to follow directions well.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)

Just keep clicking that card in your own intervals after the white screen and you will get it. With my own proof I can contest that there is a BIG misconception that this is only achieved during the White screen. NOT TRUE!!!
Those steps are what I experimented with trying to root my own DI and it worked. I was not convinced I'd get it to work on other phones since It's been days and countless hours trying to get mine to connect to ADB in Recovery. So, one of my co-workers let me try it on his phone with his different card type, and one co-worker after the other, success! The root I did on MY phone was with an sdcard I bought that came with some of the phones (SanDisk 2gb). I didn't get a free card from VZW. I had FASTER success with this card of all 6 cards I've rooted with. It took longer with the other cards, class 4 PNY, and off-brand class 6 cards. With the 2gb SandDisk class 2 it works on the first try for every phone I've tried.
Did you have HTC Sync installed as your active driver, I really can't say if the customer driver works as I haven't tried it myself? My laptop is the latest Sony VAIO F-series with Core i7 with Windows Ultimate x64. In Device Manager, while in HBOOT my phone only showed up as Android 1.0 and as HTC Bootloader.

dreamersipaq said:
You know, just because it worked for you doesn't mean it will for others....
I CAN follow directions well, and I can't get it reproduced. (though it may be because I'm already rooted?)
Click to expand...
Click to collapse
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.

I installed root by using an old laptop with XP... I had one point installed the HTC drivers. In this case, I had unistalled the HTC drivers and the HTC sync driver. Now I only used the SDK usb.inf drivers with the modified line for HTC incredible.

rynosaur said:
No, and if you want to be in tune with the FINAL SOLUTION, your chakras must be aligned with Lady DI and her mysterious ways. I recommend balancing her on your head while you sleep for a fortnight, and then comes the sacrificial goat!
Seriously OP, I followed the last CARD CLICK prophet's advice and now my card mushes into lock--the DI just ain't built for the kind of abuse frenzied insert/ejection creates. I respect that you're good at what you do, but as others have found, teaching timing with http very difficult, at best.
Click to expand...
Click to collapse
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!

dreamersipaq said:
Oh CHAKRAS! Formula 51 reference FTW!!!! B.E.S.T. M.O.V.I.E E.V.A.R.R.R.R.!.!.!.!
Click to expand...
Click to collapse
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .

From what I've seen
rynosaur said:
Believe it or not, I haven't seen it yet--just added it to my Netflix queue tho.
OP, can you get us a dmesg of you hitting the timing with your method? I want to see how it reacts to mounting/checking the sdcard devices more than once in recovery boot. I think good dmesg logs would help us all figure out what's going on here . . . .
Click to expand...
Click to collapse
It depends on how quick you insert/remove. It takes anywhere form a 1/2 second to 1 second between the initial "Slot changed from 0 -> 1" to where the card is actually mounted. If you click too fast, you never that that "mount" so you'll never get root, since it seems like the "mount" is actually causing the error we need. If you slow down your insert/remove to a slower pace, you'll get numerous mounts of the sd card. This might increase your chances of getting root because you're mounting multple times, but it makes the mounts more random then precise timing, and unfortunately, to get our error that we need, the read needs to happen at a percise time. You've seen the dmesg that was posted by 'mite.

THANK YOU OP! Worked for me :-D
My other 2 incredibles had worked consistently, but this one took your process to get.

dreamersipaq said:
You've seen the dmesg that was posted by 'mite.
Click to expand...
Click to collapse
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.

rynosaur said:
Yeah, and I'm still wondering why he was so 'elliptical' about explaining what was going on there. I still can't figure out if it's the mount process or the mounted card that triggers the adbd event, or if a delayed sdcard process simply pushes adbd start into the recovery window, when commands such as 'adb shell' can be received by daemon for a split/few seconds. Would be nice to hear his explanation of what system events are occurring outside of what is logged in dmesg. The OP says mount event can complete in recovery/black screen, you say sdcard mount must complete before black screen, that's a big diff.
I wonder if it's possible to create a host-side script that reads dmesg, watches for card mount and triggers 'adb shell' at a much faster rate than a simple win shell 'loop'. That would be killer, and would eliminate all need for card insertion timing, IMO.
Click to expand...
Click to collapse
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.

dreamersipaq said:
I don't think so. Don't have the devices in front of me right now, but I believe that the phone is disconnected from the PC (that first do - do) before our window of opportunity, which means the pc is not communicating with the phone at all. So if (big if) I am correct, nothing local to the PC can be done to initiate anything AT THE TIME that we need it to.
Click to expand...
Click to collapse
Dat's kinda what I thought

I'll try to get you guys a dmesg as soon as possible. I'm at work right now and I'm responsible for alot of servers at a law firm in DC. (never get any free time it seems) I'm been trying to check in with you guys as often as I can. It's brutal today because we have Maintenance tonight throughout the morning.

This is what I found by myself to work for me after trying for 3 days originally.

Say what you will about the OP, but the timing is key and his post did help me out. I've tried tons of cards, every method out there and had no luck, until now. So for what's it's worth, this post was much appreciated.

[Q] USB Port Kaput , Internal SD card recognized as USB Storage, can't root.

Good day folks,
I am in a bucket of hot soup at the moment with my Galaxy S.
Firstly, my Micro USB port has decided to call it a day (I have tried the alcohol cleaning trick and all other "fixes" at this stage I am contemplating getting a new MicroUSB port and installing it) . At the moment the only thing it can do is charge the phone and so perhaps I should be grateful for small mercies.
However, No USB means download mode is now unavailable to me.
This also impacts rooting with a PC. A lack of root means I cannot update my gps.conf, I cannot install a custom recovery and I cannot install custom roms. I also cant back-up or re-install my apps using titanium. I also cant use googletalk 1.3+ wth voice and video calling.
Secondly, my Internal SD card is mounted by the system and recognised as "USB storage". I can still use most apps even though its mounted with the wrong name however certain apps looking for Internal SDcard cannot find my storage. So I need to somehow change that. How do I do that?
For an individual used to running custom roms and tweaking my device any which-way I please, I find my galaxy s very unattractive right now.
I got into this situation when I was coming from Jetpack and I was moving to Simplicity. Simplicity just would not boot. At this point my phone was stuck with no ROM and after sitting and fiddling for about 5 hours with a several micro usb cables and plugging and unplugging my phone odin recognised it for one last flash and i was able to get stock JVT on it. I lost Clockword Mod 3 and so now stuck with stock recovery and thats as good as having no recovery
I really dont want to buy a new phone till I can make a decision between Nexus Prime and Galaxy S3. Im a firm believer in as close as possible to a 2 year phone cycle and my galaxy s has just turned 1 year 3 months.
So if i can root this thing I have now and survive another 6-9 months I'll be a happy man.
Help? Suggestions?
Cheers guys

You say you got stock on it... Any particular reason that you cant give it in for repair? SGS is 2 year warranty as remember...
Also crazy idea, if it is possible, turn cf-root into a update.zip and get it signed LOL. Or check to see if you can use cyanogenmod, and work your way around from there?
Lastly which you should probably do first, another computer?? (or did i miss that?) Oh and check drivers, reinstall them.. (I dont know what fixes you have tried...i just know you've tried)

Talon26 said:
You say you got stock on it... Any particular reason that you cant give it in for repair? SGS is 2 year warranty as remember...
Click to expand...
Click to collapse
Really didnt know that about the warranty. Not practical for me as the country I bought it in is different to the country in which I reside. And Samsung Here wont support/honour the warranties from There yeah what a pain . When I bought the phone I semi-bricked it and had to ship it back and forth to the other country. At the time it was worth it because the shipping values were less than 25% the value of the phone. However now shipping would be almost 100% of the current value of the phone.
Talon26 said:
Also crazy idea, if it is possible, turn cf-root into a update.zip and get it signed LOL.
Click to expand...
Click to collapse
Talon26 said:
Or check to see if you can use cyanogenmod, and work your way around from there?
Click to expand...
Click to collapse
Im looking right now.... will let you know how it goes.
Talon26 said:
Lastly which you should probably do first, another computer?? (or did i miss that?) Oh and check drivers, reinstall them.. (I dont know what fixes you have tried...i just know you've tried)
Click to expand...
Click to collapse
List of "fixes" include amongst others,
1) Different makes of micro-usb cables.
2) Different computers, 3 to be exact.
3) Cleaning the USB port , alcohol trick , scratching with a wire trick , tissue paper trick.
4) Driver un/re-install on all three machines.
5) Rebooting phone interspersed with varying combinations of cable, computer, cleaning steps all to no avail.
All in all, the ownership of this galaxy has been a bit of a pain because I got it within a week of its release and it turns out it was part of that notorious batch that had no 3BR hence the intial semi-bricking.

wmanyati said:
Talon26 said:
Or check to see if you can use cyanogenmod, and work your way around from there?
Click to expand...
Click to collapse
Im looking right now.... will let you know how it goes.
Click to expand...
Click to collapse
Nope, no can do, need root and need CWM. Has anyone ever wanted to root so badly in their life ?

Hey, did you find any solutions? I have the same problem and I can't find any answer to it... Please help

Try this method this worked for me once:
1. Remove battery, plug usb cable with other end connected to pc, insert battery and switch on. I expect you've selected the usb debugging
Sent from my GT-I9000 using Tapatalk

Monu123 said:
Try this method this worked for me once:
1. Remove battery, plug usb cable with other end connected to pc, insert battery and switch on. I expect you've selected the usb debugging
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Tried that and it didnt work thanks.

Yeah i did some research its probably a moisture problem. Idk why and how it got it. It seems that i can charge but driver failed to install/tried reinstall still fail. Any solutions?
Sent from my LG-P500 using XDA App

hellodzulz said:
Yeah i did some research its probably a moisture problem.
Click to expand...
Click to collapse
It is definitely a moisture problem. I managed to change the USB port and that didnt make a different but I also noticed that my board is starting to corode.
So i tried to cleaning the coroded bits gently with a piece of cloth soaked in alcohol and I had one last flash and so I finally managed to root and get clockwork mod.
hellodzulz said:
Idk why and how it got it.
Click to expand...
Click to collapse
After doing a lot of research I discovered that this galaxy s is very prone to moisture issues.
1) Its not well put together so moisture does tend to get into it.
2) Moisture from your hands
3) The daily heating and cooling effects of sun. Especially if you live in a humid environment. The moisture condenses internally in the device. I live 100m from the beach.
4) I also use my phone to monitor my regular cycling activies. I ride in the rain etc and although I have what I thought was a splashproof case for the phone, it still has been quite moistened.
hellodzulz said:
Any solutions?
Click to expand...
Click to collapse
Well given that you cant stop the corroding its only a matter of time before the phone eventually fails so I would recommend the following;
1) Stop storing any data on your internal card I now bought a 32GB sd card and I will just use that so if the phone fails I simply bin it and put the card in a new device.
2) Regularly back-up your device
3) Start saving for a new device
4) Get a new motherboard for the device
5) A scum-bag thing to do is hard reset it and sell it to someone who isnt aware of its data storage properties.

Thanks dude i tought it was the driver fault. Quite sad for my dad
Sent from my LG-P500 using XDA App

me too!
wmanyati said:
Secondly, my Internal SD card is mounted by the system and recognised as "USB storage". I can still use most apps even though its mounted with the wrong name however certain apps looking for Internal SDcard cannot find my storage. So I need to somehow change that. How do I do that?
Click to expand...
Click to collapse
did you resolve this issue?

[Q] Completely dead screen on an SGH-I896 - Any way to retrieve data?

A friend of my brother's had a Captivate and it's screen is completely dead. Cracked and broken physically, and won't display anything. I know the phone still kinda works since there is a row of pixels at the top that kinda lights up when the power button is pushed. The lights seem to correspond to a normal boot up and screen on/off functionality.
I am not versed in this particular phone, is there any way for me to get the data off of it? The guy who used it can't remember the google account info (...yes I know...) so he's come to me, the resident techie, to try and get the data off of it.
Is it possible? It's unrooted, stock, basically untouched from what I know. So we're dealing with something that has zero root access.
Do you guys think it's still possible to get it into fastboot mode and get something off of it? Maybe using ODIN?

Well, I am guessing that it is impossible to activate USB mass storage given the condition of the screen. The best way would be to odin a kernel that has CWM, and blindly navigate through the menus in order to mount USB storage. I have seen this done before; it's easy if you know how many times to press the buttons. I suppose I could help with that if you can't find another reference.
Or you could use ADB but that relies on USB debugging being enabled, which isn't likely if the person was an average user.
BTW, I'm jealous of your current devices...

korockinout13 said:
Well, I am guessing that it is impossible to activate USB mass storage given the condition of the screen. The best way would be to odin a kernel that has CWM, and blindly navigate through the menus in order to mount USB storage. I have seen this done before; it's easy if you know how many times to press the buttons. I suppose I could help with that if you can't find another reference.
Or you could use ADB but that relies on USB debugging being enabled, which isn't likely if the person was an average user.
BTW, I'm jealous of your current devices...
Click to expand...
Click to collapse
You can ODIN a kernel with CWM on an unrooted device? I did not know that! Could you kindly point me in the direction of some sort of ODIN how-to? I'm not versed in the Samsung proprietary stuff. I should also add that it's not just the "USB Storage" that needs to be retrieved, things like contacts and stuff too if possible. I tried explaining that the Google account would have the stuff synced, but that's where the "I dunno the login" comes in. -sigh-
USB Debugging is not enabled as far as I know this is purely a stock device. Nothing changed other than basic usage settings.
I'm a bit of a Nexus junkie...my husband gets my older stuff...so he's kind of up to date (only out by a year or so), and I get the fancy really new stuff lol.

FlareHeart said:
You can ODIN a kernel with CWM on an unrooted device? I did not know that! Could you kindly point me in the direction of some sort of ODIN how-to? I'm not versed in the Samsung proprietary stuff. I should also add that it's not just the "USB Storage" that needs to be retrieved, things like contacts and stuff too if possible. I tried explaining that the Google account would have the stuff synced, but that's where the "I dunno the login" comes in. -sigh-
USB Debugging is not enabled as far as I know this is purely a stock device. Nothing changed other than basic usage settings.
I'm a bit of a Nexus junkie...my husband gets my older stuff...so he's kind of up to date (only out by a year or so), and I get the fancy really new stuff lol.
Click to expand...
Click to collapse
Yep, rooting only affects things at the OS level, while download mode has access to everything right out of the box. Do you happen to know which stock version the phone was running? That will affect which kernel I suggest.
As far as the contacts go... I suppose we can do a nandroid backup of the device from recovery, and to get the other stuff out, I figure you'd have to restore it to a different device and deal with it from there.

korockinout13 said:
Yep, rooting only affects things at the OS level, while download mode has access to everything right out of the box. Do you happen to know which stock version the phone was running? That will affect which kernel I suggest.
As far as the contacts go... I suppose we can do a nandroid backup of the device from recovery, and to get the other stuff out, I figure you'd have to restore it to a different device and deal with it from there.
Click to expand...
Click to collapse
No idea what version it was running prior to crash, and I don't have another Captivate to restore a nandroid to, so I'm not sure how well this is going to work...
I'm kinda leaning towards the..."nope you borked it" answer.

FlareHeart said:
No idea what version it was running prior to crash, and I don't have another Captivate to restore a nandroid to, so I'm not sure how well this is going to work...
I'm kinda leaning towards the..."nope you borked it" answer.
Click to expand...
Click to collapse
Okay, well in that case you should probably just try a froyo kernel because we don't know if you have gingerbread bootloaders or not.
And I'm pretty sure you can extract that kind of stuff from a nandroid using titanium backup.
Sent from a jelly bean

korockinout13 said:
Okay, well in that case you should probably just try a froyo kernel because we don't know if you have gingerbread bootloaders or not.
And I'm pretty sure you can extract that kind of stuff from a nandroid using titanium backup.
Sent from a jelly bean
Click to expand...
Click to collapse
I plugged the phone into my PC to charge, and it's not making the chime...I know it won't pop up as a storage location, but shouldn't the PC still chime to indicate that it sees the device? Also, something appears to have caused it to cease powering up like before. The lights on the buttons don't come on anymore, and the power button no longer seems to elicit the normal pixel line at the top showing power...I think it just finished dying.
I don't think it's going to work for us.
Thanks anyway though!

remote screen: if you can figure how to install myphoneexplorer client on your cappy and then install the myphoneexplorer on you pc, it has a driver to remote the cappy screen via usb into a window on the pc. you can use the mouse to do anything you would do with your finger on the cappy screen.
search 'my phone explorer' via google play. the developer of the app may have a way for you to get it on the cappy via usb.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app

XT1096 Screen Broke. Options for recovery?

Hi all.
Looking for some insight and help. I've had an unfortunate situation with my Moto X. I went to the store to buy my son a toy, and for whatever reason the price was not coming up correctly. I ended up taking a picture of the price and when I showed the older lady working the register, she grabbed my phone from my hand and proceeded to drop it, shattering the screen. She was old, and more upset about it that I was. I told her not to worry about it and went on my way. The screen and digitizer still worked at this point, but I didn't bother trying to recover my files. After a day, everything just stopped working. Doh!
Now I can get the phone into fastboot mode, and adb sideload even though I can't see the screen. I believe USB debugging is off. I really would like the pictures off the phone, of the first 6-7 months of my sons life. So here are my question:
Does the Moto X display the screen via hdmi without any interaction with the screen? Can it simultaneously use a mouse as well with the right dongle?
Does Mofo require usb debugging, and if not, can I load a rom via fastboot/mofo that would allow access to the sdcard?
Those are the only 2 options I can think of that may work, but not exactly sure.
Thanks for any help!

Are they auto backed up to Google+ Photos?

cal196 said:
Those are the only 2 options I can think of that may work, but not exactly sure.
Click to expand...
Click to collapse
When you turn the phone on and connect it to your computer does your computer recognize the phone? Do you have Motorola Device Manager installed on your computer?

chrisrozon said:
Are they auto backed up to Google+ Photos?
Click to expand...
Click to collapse
They are not unfortunately.

JulesJam said:
When you turn the phone on and connect it to your computer does your computer recognize the phone? Do you have Motorola Device Manager installed on your computer?
Click to expand...
Click to collapse
Yes and Yes. I have everything set up on the computer and can get a response from fastboot devices. I can get the phone into recovery as well and put it into sideload mode in adb. I already have a 2nd Moto X that I am using to show me the exact volume down up button pushes I need to get me where I'm going.

cal196 said:
Yes and Yes. I have everything set up on the computer and can get a response from fastboot devices. I can get the phone into recovery as well and put it into sideload mode in adb. I already have a 2nd Moto X that I am using to show me the exact volume down up button pushes I need to get me where I'm going.
Click to expand...
Click to collapse
Why don't you just turn the phone on regularly and plug the phone into your computer - you should see the internal storage. The pictures you took with your camera are in the DCIM/camera folder.
Can you see the pictures that way? If so, try to copy the pictures to your computer.

JulesJam said:
Why don't you just turn the phone on regularly and plug the phone into your computer - you should see the internal storage. The pictures you took with your camera are in the DCIM/camera folder.
Can you see the pictures that way? If so, try to copy the pictures to your computer.
Click to expand...
Click to collapse
I checked with my working Moto X, and it requires that you unlock it at least once before it shows up as internal storage. I have a pattern passlock on the broken phone.

cal196 said:
I checked with my working Moto X, and it requires that you unlock it at least once before it shows up as internal storage. I have a pattern passlock on the broken phone.
Click to expand...
Click to collapse
If you can get into recovery, then you may be able to do an adb pull of the /sdcard/DCIM/Camera folder.
adb pull /sdcard/DCIM/Camera
If it works, that would leave all of the photos in the directory where you have navigated to in the command prompt.
But I am not sure if you can pull if you have pattern passlock on the broken phone. If you could, that would make the pattern passlock worthless. All you can do is try.
If you can't access the phone, then take it to a repair shop and pay to have them extract the photos if the photos are that important to you. I am sure they can either fix the screen to enable you to enter your pattern or they may have a way to bypass those passlocks to pull the files.
If there were some easy way to bypass the pattern passlocks, then they would be worthless so I doubt you will be able to get anything off of that phone without either paying to fix the screen or paying a repair shop to use equipment to bypass the passlock.

JulesJam said:
If you can get into recovery, then you may be able to do an adb pull of the /sdcard/DCIM/Camera folder.
adb pull /sdcard/DCIM/Camera
If it works, that would leave all of the photos in the directory where you have navigated to in the command prompt.
But I am not sure if you can pull if you have pattern passlock on the broken phone. If you could, that would make the pattern passlock worthless. All you can do is try.
If you can't access the phone, then take it to a repair shop and pay to have them extract the photos if the photos are that important to you. I am sure they can either fix the screen to enable you to enter your pattern or they may have a way to bypass those passlocks to pull the files.
If there were some easy way to bypass the pattern passlocks, then they would be worthless so I doubt you will be able to get anything off of that phone without either paying to fix the screen or paying a repair shop to use equipment to bypass the passlock.
Click to expand...
Click to collapse
Thanks for your suggestions. I was just able to solve my own problem. I ordered an OTG cable and plugged in a wireless mouse. I practiced a few times with my other phone, and then tried with the broken phone and was able to get the passlock on the 2nd try, unlocking the phone, and allowing the media drive to show up after plugging into my computer. I pulled my photos and all is good.
Thanks again

cal196 said:
Thanks for your suggestions. I was just able to solve my own problem. I ordered an OTG cable and plugged in a wireless mouse. I practiced a few times with my other phone, and then tried with the broken phone and was able to get the passlock on the 2nd try, unlocking the phone, and allowing the media drive to show up after plugging into my computer. I pulled my photos and all is good.
Thanks again
Click to expand...
Click to collapse
Ok so then after you unlocked it, you were able to just copy using the copy function of your PC or did you have to use adb?

JulesJam said:
Ok so then after you unlocked it, you were able to just copy using the copy function of your PC or did you have to use adb?
Click to expand...
Click to collapse
Yes, after unlocking the drive shows up on my PC. :good: