[Q] Internal SD Card corrupted - Captivate Q&A, Help & Troubleshooting

My wife seems to have corrupted her internal SD card, absolutely no idea how. She was bone stock, not even rooted. I could not get stock to even boot past the boot animation, so I tried one of the GB 1 Clicks and boogs KJ3 kernel to get CWM, now I can boot to the launcher, but it bootloops from there. I don't want to format the internal SD until I can get her pictures from it if possible, so my question is: is there a way to get the pictures off, if they even still exist? I have tried mounting in CWM and all i get is a lost directory, now I can't even mount USB storage.

Boot into recovery, then use adb to pull from /mnt/sdcard
Don't need to mount with adb.

Just tried this, I get an empty directory. Tried using adb shell and still showing an empty directory. Any other thoughts, or am I going to have to reformat?

Ouch....I think a format is in order.
sorry man

Well I got it to boot with the kk4 1 click and it runs, but the gallery is empty, so I assume I'm hosed. Any thoughts on cause, she says that earlier she got a message in the notification area about removing her sd card (she has no external, just an internal)?

Try this
Set your screen timeout to the max. Reboot y your phone. Keep touching the screen, don't let it go to sleep. Keep doing that as you pull everything from the phone.
About adb
If you don't set a destination folder in your command, it won't pull. If she's on 2.1, you don't use the mnt part. Place a folder directly on your c drive, so that it's address path is c:\your folder name
This makes your adb command
adb pull \sdcard\ c:\your folder name
Do all of this without letting the phone go to sleep. Maybe it will work for you.

Adb pull /sdcard c:\your folder
Forward slash on phone, backslash on pc.

studacris said:
Adb pull /sdcard c:\your folder
Forward slash on phone, backslash on pc.
Click to expand...
Click to collapse
Yeah, your right.

Appreciate both of your input, but now adb won't even recognize that the phone is attached in the stock kk4 1 click, even in recovery. Like I said the gallery is totally empty and my USB storage on the about phone shows that all of the storage is available, so I'm gonna guess it's all gone. I'll try flashing one of the custom kernels for kk4 just to give it one last try, but I'm not holding out much hope here.

How are you trying to connect to your computer with adb? All you have to do is turn usb debugging on and plug in. open a command prompt terminal. Any of that sound familiar?

There should be a "my files" app you can explore the sdcard that way.
Pictures are in DCIM/camera folder.

the stock 1 click did not have a usb debugging option. Got it to work connecting with samurai 1.4.3, but the directories are showing empty or nonexistent.

Studacris,
You must have been posting while I replied. I've used the my files app and it shows dcim as empty. Now, my wife has decided she's gonna give up on the phone since this was her warranty replacement after her first 1 completely bricked after our daughter played with it. Never could get that one to even boot, although, I've found that this one won't boot to download with a jig, have to use the battery pull, vol +/vol -, insert usb cable method.
Thanks again for the attempts, but I think it's a lost cause, so I'm giving up.

Flash it back to stock and get it replaced again.

Related

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

[Q] Internal SD card retrieval?

Hi, new here and I have a question:
I broke the screen on my Cappy and just got a replacement. The thing is, I hadn't moved all my pictures and movies (and various other things) to the external SD card. I've been searching for a way to retrieve them and it doesn't seem to look good.
I've tried on 2 other phones to get into CWM and mount the USB storage from there (Since hard keys are my only option) and it didn't work there (same model and mod) or when I tried on the bricked phone (6 menu options down, 2 up to mount sd card).
The question is this:
How can I through some way get all this data downloaded to my PC? Boot loader, download mode, recovery... I know just enough to do what I need to do to mod my phone, but not enough to know how to do this.
Any help would be appreciated! You guys have helped me so much by your informative posts I would be humbled for you to help me specifically.
Install adb
If you had usb debugging enabled you cab just boot up, if not recovery will communicate with adb regardless.
Adb pull /mnt/sdcard (where ever you want it to go on your PC)
studacris said:
Install adb
If you had usb debugging enabled you cab just boot up, if not recovery will communicate with adb regardless.
Adb pull /mnt/sdcard (where ever you want it to go on your PC)
Click to expand...
Click to collapse
The following happens when I try:
C:\> adb pull /mnt/sdcard c:/sd/
pull: building file list...
pull: /mnt/sdcard/lost.dir/28 -> c:/sd/lost.dir/28
cannot create 'c:\sd\lost.dir/28': No such file or directory
Nevermind. It should have been:
C:\> adb pull /mnt/sdcard c:\sd\
In windows, file locations use back slashes. you're telling it to go to c:/sd/
Should be c:\sd and no final backslash.

Copy files from damaged device

My daughter got her m7 wet, now it wont stay running.
It will boot up but it immediately shuts off and shows the charging symbol.
It will run ok in recovery for a while.
Is there any way to copy her files off of the phone and onto the computer from recovery?
Random667 said:
My daughter got her m7 wet, now it wont stay running.
It will boot up but it immediately shuts off and shows the charging symbol.
It will run ok in recovery for a while.
Is there any way to copy her files off of the phone and onto the computer from recovery?
Click to expand...
Click to collapse
if you have adb and fastboot on your computer, you can boot into re3covery and use the adb pull command to pull the whole contents of the internal storage to your computer.
If I remember correctly, the command is just adb pull /sdcard/ and it will pull the entire contents of your internal storage to the adb/fastboot folder on your computer
Yes!
That is working, transferring files now.
I had to use: "adb pull /sdcard/0/" to get it to work.
Random667 said:
Yes!
That is working, transferring files now.
I had to use: "adb pull /sdcard/0/" to get it to work.
Click to expand...
Click to collapse
Thanks for clarifying, :good: its been a long time since I used that command and couldnt quite remember it, you can pull individual folders by adding the name of the folder to the end of that command too, such as adb pull /sdcard/0/Music.

[Q] Getting data from the phone

Hello,
the phones lcd was changed and something went wrong when we did the assembly. The phone "doesn't" turn on, it does but the screen is blank. I would like to know how can I get the files down.
If there is any way. Thanks for the support!
Daichisan said:
Hello,
the phones lcd was changed and something went wrong when we did the assembly. The phone "doesn't" turn on, it does but the screen is blank. I would like to know how can I get the files down.
If there is any way. Thanks for the support!
Click to expand...
Click to collapse
if you can somehow blind navigate your way to recovery then you can just pull the contents of the internal storage to your adb / fastboot folder on your computer.
adb pull /sdcard/0/ ------- (thats a zero)
or
adb pull /sdcard/0/Music to just pull your Music folder etc, change to Pictures or DCIM etc, the first command above will pull everything.
Seanie280672 said:
if you can somehow blind navigate your way to recovery then you can just pull the contents of the internal storage to your adb / fastboot folder on your computer.
adb pull /sdcard/0/ ------- (thats a zero)
or
adb pull /sdcard/0/Music to just pull your Music folder etc, change to Pictures or DCIM etc, the first command above will pull everything.
Click to expand...
Click to collapse
Was thinking about that, but it's hard to get to recovery. The guy who changed the screen somehow damaged the buttons but when I connect the phone to the laptop, I get an bip, that the phone is connected.
But the problem is that I get an uknown device notice and when I wan't to update drivers, I get an error. Is it maybe the problem USB 3.0? Should try with USB 2.0?
Hmm...will go mad .)
Any idea?

Sort of a bootloop after Android 11 update

Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...

Categories

Resources