SOLVED
(No success for me personally, but I'd still like to explain how I realised there's no hope left - description is at the bottom of this post)
Hi, not a regular poster in the S3 mini section, but a friend of mine has had his entire screen smashed. Somehow though, the phone is still breathing and can be turned on/off.
The problem is: My friend has asked me to extract his photos and similar media from the device's memory.
The device isn't rooted and I'm not sure if there's a default recovery mode or something like that built in the device.
I've tried connecting the device to my PC and it gets recognized and the drivers install themselves, but the device is empty. Moreover, I've downloaded KIES which also recognized the device, but says that there's a lockscreen and he can't go any further.
Any advices? Most of the other xda answers are for rooted phones so they haven't been very helpful, unfortunately.
There's a picture of the device in the attachments below, and KIES interface aswell.
<<EDIT>>
I'm using this http://forum.xda-developers.com/showthread.php?t=2339530 Recovery operation but it keeps saying "adb.exe" not found. I've installed ADB via the 15sec install ( http://forum.xda-developers.com/showthread.php?t=2588979 ) and entered the path correctly, but it still can't detect it. Any tips? perhaps i'm using the wrong ADB - I don't have c:\android\platform-tools folder - it's simply c:\adb\adb.exe.
SOLVED PROBLEM:
After messing with this for 2-3 days, I've decided to go with the simplest method - find a way to list all directories on the device and then see if there's anything in "sdcard" or a similar folder. To do this, after ADB recognizes your device, type : adb shell ls -R
adb shell ls -R will list a zillion directories so you may want to save the data into a .txt file. to do this, type adb shell ls -R > output.txt (or any other name).
After that, open the output.txt file and then use ctrl-f to find the sdcard folders and check if there's any data left in them.
IMPORTANT:
I've read that, without root permission, one cannot access the data or sdcard directories. The device I was working on had USB debugging OFF so there was no way I could root the phone in order to access the data directories.
Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?
aumedina said:
Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?
Click to expand...
Click to collapse
Yup, but it still can't find it. That's why I think the ADB-15sec install might be flawed.
There's a screencap of the Recovery + TotalCMD in the background in the attachments.
<EDIT>
Alright so I've followed an ADB tutorial (http://forum.xda-developers.com/showthread.php?t=2266638), installed all the SDK packages just to be sure.
ADB now recognizes the device after I've booted it into recovery mode. I've tried doing adb pull /data and it says 0 files pulled, 0 files skipped. Does this mean the device's internal memory is blank? No it doesn't, only the folder "data" is blank, other system data is present.
<EDIT 2> Can anyone please tell me the path to the internal camera storage folder? I may have fixed the problem if only I knew the correct path. SOLVED: The correct path is one of 4 combinations, usually these: /mnt/sdcard0/ /mnt/sdcard/ /storage/sdcard0/ /storage/sdcard/
Related
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.
Trying to be charitable and cautious, I'm trying to back up my EFS folder before I go messing around and it is consistently failing. I'm using:
SGS Tools Vz 0.5.7
Busy Box Vz1.17.2
On my previous captivate this works just fine. Now I get
"could not create backup folder /sdcard/SGSToolbox/backup (date string)" and then the bluebox saying creating backup. This never goes away and to clear I have to reboot.
Any helpful hints?
I tried to download the latest and greatest SGS Tools but Google knows I have it installed and won't let me get the newest one. Haven't figure out how to get around that unless I just have to un-install my current one.
Rooted 2.2, KB2, running existz KB1 kernel.
Knowing there are no successful backups... just successful restores.
If you're willing to use your computer and can get the Android SDK and ADB going, just get into a command prompt in the ADB directory and type "adb pull /efs". That will back it up to your computer.
Or you could open a file explorer and copy the directory from there to your sd card
You could use an app called nitrality
Sent from my SGH-I897 using XDA App
Try to update your su binary, the simpliest way is use Root Explorer to backup whatever u want
Well just to be daring, I tried to install the ADB tools. Had to install the Java development software first. After I installed what I thought was the ADB suite, I can't seem to find the place to type in commands, dumb as that sounds. I may not have gotten the right package. Going to tinker with it though.
My SU is up to date.
I can see the folder with Super Manager so I guess I'll just copy with that. Interesting though I can't see anything in the /efs directory. Probably just something else I don't understand.
Still curious though as to why SGS Tools is failing... part of my nature.
Thanks to all that replied.
Make a note of where adb is installed (e.g. c:\users\person\Android-sdk-windows\platform-tools). Then hit the windows key and R, and type cmd. Once in the prompt, type CD (directory from before, no parentheses) and hit enter. From there, type your adb commands.
Ahhhh.... I get it. Was expecting something a bit more elegant. Gotta love DOS commands.
Well..there are a couple more elegant ways to do it.
Open up a new note in NotePad, just type:
Cmd
Exit
And save, but instead of a .txt file extension save it as a .bat, now drop that into your adb directoty, then just double click on that to open a prompt in that directory, so you don't have to do the cd command every time.
Or..the most elegant way is to add adb to your environmental variables so you can enter adb commands from anywhere
That's a good solution. I've got a set of files put into my C:\Users\(my username) folder called "adb", "adbr" (adb reboot), "adbrd" (adb reboot download), and "adbrr" (adb reboot recovery).
Each of these is a .bat file with a version of this text in it:
@ echo off
cd "C:\Users\(me)\Other\tools\android-sdk-windows\platform-tools"
adb reboot
That way, all I have to do is hit Win-R and type one of those file names and it does that command for me. Or, I can type cmd, then adb, and automatically be where adb is installed without cd'ing through a long file list.
My suggestion is Root Explorer. I was able to backup the EFS directory without problems also create a .tar file.
I used root explorer to do my backups, another option is the explorer inside the rom tollbox aplication its also very good
Now I have another adb question...
First off, now I'm just trying to learn and get better. I've built my bat files and I can get adb working. Thanks to those that helped with that. When I tried to pull the /efs folder it said there was no device recognized. I was in "mass storage" mode at the time.
Whenever I've seen people talk about using adb, I don't recall anything being said about if it should be in Download, debug or what. One of those assumed knowledge things.
So what do I have to do to the phone to let adb recognize it?
gnawing on the bone....
I'm also thinking of pulling a logcat or something when SGS tools fails... just to see. That's my next step.
Enable usb debugging in settings> applications> development
SGS Toolbox doesn't work with efs backups. Are there easier ways to do the backup?
Adb or root explorer.
I did both... just to say I did it and finally got adb working.
Hello,
I've had my phone rooted for a long time and things were working out quite fine (yes, I have a recent xRecovery backup ) but a couple of days ago I wanted to try out something new, and wanted to prepare my system for the installation of a custom kernel.
Long story short: I used the busybox installer from the market, but it couldn't verify the installation process because of some previously installed busybox version (guess it came with my ROM...) So I used the uninstall option within the app and this is were things started to go down the drain:
Now when I reboot the phone, it's no longer possible to enter xRecovery as it was possible before (pressing back button repeatedly, during SonyEricson Logo) instead the it just reboots straight into Android. And in Android all that works is the log screen - all other applications / services crash. (I really can't do anything, as soon as I try to unlock the screen I'm bombarded with Error Messages, and sometimes the phone reboots because so many services fail)
I still can get into the reboot options menu when I press the power button > 1sec, but selecting "reboot into xRecovery" or "reboot into CWM" doesn't work -> it will just reboot normally again.
It also seems impossible to get the phone into flash mode. (Turn Phone off, Unplug USB, hold Back Button, Turn Phone on, Connect USB - and every possible variation I could find just leads to the phone booting into Android)
What I tried to do:
I still have root access when I connect to the phone with adb, so I reinstalled the busybox binary from the "SuperOneClick" package into the /system/xbin/ folder manually -> no change
I checked the debug log (from adb logcat) for errors indicate a problem, but there's no obvious message
I checked the dmesg output for errors / problems, but here everything seems to be fine
I reinstalled xRecovery manually (files from SuperOneClick) via adb by putting the files (xrecovery.tar+chargemon), into /system/bin -> no change
I tried to get into recovery / bootloader mode by using "adb reboot bootloader" and "adb reboot recovery" -> normal reboot
I checked the permissions of the binary files (su, busybox, chargemon) and they're all set to 06755
I checked if all symlinks of system programs that require busybox / su are pointing to existing binaries, and they all seem to be correct
Before I proceed and start trying some things that are not so easily reversible I've got a couple of questions:
What happens if I delete all files in the "/system/" folder? (the xRecovery files are in that folder and I guess xRecovery itself needs a couple of files to work properly)
Do you have any tips / ideas what I could try? I really don't mind resetting the phone as I have backups, it's just that I can't get into the mode where I can reset the phone
Thank you very much!
In your case, i suggest you never ever, ever fiddle up with busybox again... leave that up to chefs.
Also, i think you should try removing the battery for a couple minutes, then put it back and press back, then (while holding it) insert usb cable. That's a surefire way to get into flash mode (At least for me, sometimes it happens to boot normally even if i press back if i don't remove the battery). Also, just to be sure, before connecting your phone in flash mode, press Windows + R [In your keyboard, obviously] and type "devmgmt.msc" [Without the quotes] and see if you get a new device under USB devices. If it has a yellow triangle, right click it and choose update drivers, then point it to the flashtool folder for drivers, it should be able to find them. Good luck.
Use PCC
PCC Brought my phone to its original state when I had soft bricked my phone. It worked as a charm , and it was back to the state like nothing ever happened. Also my phone got unrooted. Everything stock like I had bought it from the store.
Use PCC , thereafter get your phone rooted again , as you had initially done.
Dude are you kidding me???You are doing it wrong man...
to get into flashmood
1. turn your phone off
2.press and hold the back button
3.without leaving the back button insert ur phones cable ..
you don't. need to turn on your phone after doing this....
use pcc or seus to repair it it's a soft brick......
@all that replied: Thank you for your help, I managed to fix the problem, will explain it in next post in case somebody runs into a similar problem
@Drknzz
about the fiddeling: that's how you learn stuff - in the last 36 hours I was forced to dig deep into android, and it was fun - and now I've got a pretty good picture of the system
Your your tip about removing the battery for a cpl of minutes didn't work for me.
I also tried XperiaRebootOptions, but this app also fails putting the phone into FASTBOOT mode - so I'll have to keep searching for an explanation
@Mayank77
I can't use PCC, because I'm running Linux as my O/S of choice and try to keep my VirtualBox locked (when I was very desperate this morning I tried it in a VirtualMachine, but PCC wouldn't connect properly to my phone)
@noobismyname
thanks, but doesn't work in my case
a little description of how you can solve problems (using Linux) with incompatible versions of su and busybox that can occur when Market Apps like BusyBoxInstaller are used in combination with ROMs that require specific Versions of the above tools.
In special cases this might lead to the problem, that you can no longer enter xRecovery or put your phone into fastboot mode (depending on your ROM) but you still have debug access to your phone.
Requirements
Nandroid / xRecovery Backup on your local machine
Android SDK -> adb
Image extraction tool unyaffs
root access to phone
Steps
Extract the backup image
The backup files created by xRecovery use an uncommon format because of the filesystem used in android. Use the tool unyaffs (code dot google dot com/p/unyaffs) to extract the image to a directory of your choice.
log into you phone with adb
open up a terminal, and use $adb shell to connect to your phone. Change to root user $su root
If required: make the partition writeable
$mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
compare files
open a second terminal window and navigate to the folder where you extracted the backup image. Start comparing the content of the directories with each other. Important files are: /system/build.prop, /system/bin/su ->symlink to system/xbin/su, /system/xbin/busybox, ...... (depending on what you messed up)
the command $busybox ls -l /system/targetdir | grep sought_file [/] comes in handy, because it will output the files alphabetically sorted and not in arbitrary order like the default adb ls proproamm
[*]use adb to push files to your device
if you find a missing / missmatching file use $adb push /file/on/your/pc /data/local/tmp to copy the backup file to your mobile
[*]copy files to target directory
use (as root) $ cp /data/local/tmp/file /system/..... to copy your backup into the correct place
[*]check permissions
check the permission of every file you copied and in case you're unsure: they should belong to root, group root, access permission 755 (or 06755 in case of busybox and su)
$ls -l /target/dir | grep filename to check
$chown root /target/file
$chgrp root /target/file
$chmod 755 /target/file
[*]make sure changes are written to disk
flush all pending filesystem changes $sync
[*]reboot
exit the adb session with ctrl+c
and use adb reboot to restart & enjoy your phone
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
kmacho714 said:
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
Click to expand...
Click to collapse
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
twrp sideload
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
kmacho714 said:
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
Click to expand...
Click to collapse
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
adb
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
do i need android sdk? and htc sync? i have the drivers i think? on my device managers it doesnt say adb . just device and on the info it says htc device
thank you
tdhite said:
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
Click to expand...
Click to collapse
thanks a lot! those commands work ! just needed to install the drivers . thanks! again
Hello,
I googled and searched the forum but none o the threads apply to my problem as far as I can see. :/
So my old phone finally dies more or less... and I am trying to get the picture from the internal storage.
My setup: I9000, running CM11 (not sure which nightly exactly), rooted, BUT usb-debugging could be off I dont know for sure.
I can go to recovery mode but as the screen is broken I am limited with my actions. So using
Code:
adb devices
I can see my device
Code:
<long number here> recovery
Here is what I tried:
Code:
adb pull / H:/backup
This does not work because after a short while it aborts with an error message: "... no such file or directory"
Using
Code:
adb shell
followed by cd sdcard gives me a "cant cd to sdcard"
If I try to cd into other directories they are empty when trying to list them with ls.
su is also not found but adb root shows that it is already running as root.
Afterwards I tried Android Commander but that also did not work for me because Android Commander did not show my device and it also crashed after a while.
To make a long story short I am desperate...
What else can I try to get my data?
push
no one?
SaphirX said:
push
no one?
Click to expand...
Click to collapse
I don't think you can just PULL the whole "/" partition. The long number you listed there is likely to be your IMEI number (Just a guess).
EDIT: You might want to check this out: http://stackoverflow.com/questions/19225467/backing-up-android-device-using-adb