[MOD/APP]{Xperia S/U/P}[GB] SDCARD Mounter as Mass Storage (MSC Mode) {Dt: 27/April} - Sony Xperia P, U, Sola, Go

[ info ]
so friends i know some of u are getting pissed because Sony didnt include MSC (mass storage mode) in the Xperia S/U/P GB firmware... the MTP mode is fine but some users (including me) prefer the MSC mode...
so here is a MOD/HACK which will enable that functionality!!!
[ credits ]
Napstar - for discussing this workaround which was ment for recovery but it works in OS very well
rogro82 - for creating and posting the GScript App here
finally me (DooMLoRD) - for implementing it for Xperia S/U/P and creating this easy to use package
[ requirements ]
stock GingerBread firmware
rooted device with busybox installed
[ downloads ]
APP for Xperia S
APP for Xperia U/P
if u want me to make a version of this app for ur Xperia P, Sola read this
OLD MANUAL WAY
test it out and let me know ur feedback!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ENJOY!!

Saw requirements and rooted, almost cried
But very good work u guys! Finally someone made this mod! I'll test out when bl is unlocked! xD
Sent from my LT26i using xda premium

Awesome! Working perfectly for me. Thanks! Was hoping for something like this

Thank you very much DooMLoRD Now copying is speeeedy...even 28MB/s

Sweet!!
Code:
[260388.740074] usb 1-4: new high speed USB device using ehci_hcd and address 60
[260388.878673] usb 1-4: New USB device found, idVendor=0fce, idProduct=b169
[260388.878680] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[260388.878683] usb 1-4: Product: SEMC HSUSB Device
[260388.878686] usb 1-4: Manufacturer: SEMC
[260388.878688] usb 1-4: SerialNumber: **********
[260388.878919] usb 1-4: configuration #1 chosen from 1 choice
[260388.880622] scsi12 : SCSI emulation for USB Mass Storage devices
[260388.880894] usb-storage: device found at 60
[260388.880897] usb-storage: waiting for device to settle before scanning
[260393.876839] usb-storage: device scan complete
[260393.877392] scsi 12:0:0:0: Direct-Access SEMC Mass storage 0100 PQ: 0 ANSI: 4
[260393.878421] sd 12:0:0:0: Attached scsi generic sg2 type 0
[260393.880092] sd 12:0:0:0: [sdb] 54128640 512-byte logical blocks: (27.7 GB/25.8 GiB)
[260393.880585] sd 12:0:0:0: [sdb] Write Protect is off
[260393.880591] sd 12:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[260393.880596] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[260393.882455] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[260393.882463] sdb:
[260393.891209] sd 12:0:0:0: [sdb] Assuming drive cache: write through
[260393.891218] sd 12:0:0:0: [sdb] Attached SCSI removable disk
[260394.093218] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Brilliant! and so simple too, 2 lines! Makes the recent donation all the more sweet, so yet again - thanks DooMLoRD & Napstar
It seriously screws this Notification Bar mod, but that can go in favour of this
EDIT: also works on SO-02D - 6.0.A.4.1 (personal project I'm working on..)

wow i didn't think you would release it this quickly donation coming your way, thanks a lot man!

Incredible!
Thanks you for all your work, donation is coming
I dunno why Sony has removed this function in the rom, MTP is horrible!

One more great job doom.
Thx you for developing for SXS.
Cant wait to put my hands on it.
Sent from my LT26i using XDA

some funny things I did (don't try this at home)
I've formatted the mounted internal SDCard as NTFS and guess what, it didn't mount properly (as expected) by the operating system - but using gscript, it did mount properly in windows.
After that, I used adb shell to gain access to the device to manually mount /dev/block/mmcblk0p15 and voila, it supports NTFS - though root explorer etc. It's not practical (as the OS reports the /sdcard/ is not mounted - even though it is), but still fun to investigate.
Code:
# df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 348.4M 64.0K 348.3M 0% /dev
tmpfs 348.4M 0 348.4M 0% /mnt/asec
tmpfs 348.4M 0 348.4M 0% /mnt/obb
/dev/block/mmcblk0p12
1007.9M 352.9M 654.9M 35% /system
/dev/block/mmcblk0p14
2.0G 484.3M 1.5G 24% /data
/dev/block/mmcblk0p13
246.1M 164.0M 82.0M 67% /cache
/dev/block/mmcblk0p10
7.9M 4.1M 3.7M 53% /data/idd
/dev/block/mmcblk0p13
246.1M 164.0M 82.0M 67% /data/dalvik-cache
/dev/block/mmcblk0p15
25.8G 86.5M 25.7G 0% /mnt/sdcard
# mount
mount
rootfs on / type rootfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p12 on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p14 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p13 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data/idd type ext4 (rw,nosuid,nodev,relatime,barrier=0,data=ordered)
/dev/block/mmcblk0p13 on /data/dalvik-cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p15 on /mnt/sdcard type ntfs (ro,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=iso8859-1,errors=continue,mft_zone_
multiplier=1)
---------- Post added at 05:11 PM ---------- Previous post was at 04:54 PM ----------
On the side note - which part denotes how the system boots up and mounts /sdcard/ ? I am not that good with android in terms of bootup sequences, so I thought I can look up /etc/fstab but there's nothing there

^ /etc/vold.fstab
possibly
the dir and symlinks are done in init
Sent from my LT26i using XDA

works perfectly
but i was just wondering (not complaining)
would it be possible to make this part of the os so you dont have to run the script
so for example, mod a system file?

Works here...Ubuntu 12.04 64bit...
Thx

It's even better than Xperia Arc. I've simultanously Mass Storage mode, MTP mode and access in phone.
..i just donated 10$ for good cofee or something you like Best regards

Seems great work. It is possible to install Gscript zip file manually by using root explorer and then follow rest of the guideline ?

Autmatic Mounting and Unmounting
Hello,
I hate MTP so much that I cried tears of joy after seeing this post, so thx Doomlord!
The only thing annoying was always having to manually Mount / Dismount.
So I went and made a Tasker Profile that complete automates this
You need the following for this to work:
Tasker
Autoshortcut
Locale Power Source Plug-In
Step 1:
Follow Doomlords awesome instructions on page 1
Step 2:
Install all of the above mentioned Programs
Step 3:
Download the attached ZIP File and extract to /sdcard/Tasker/profiles
Step 4:
Import the profiles by long pressing the "Profiles" Button in Tasker (top left) and then pressing import. And don't forget to engable the profile.
Step 5:
Now everytime you connect to USB the drive gets mounted, everytime you disconnect it gets dismounted.
It should work with Locale instead of Tasker, too but I don't own that programm so I haven't tried.
Enjoy

Just remembered we had http://forum.xda-developers.com/showthread.php?t=1389375 on the Desire/N1 before we fixed UMS properly. Works the same way, just need to change the LUN file path.
Sent from my LT26i using XDA

OLD INFO!
[ info ]
so friends i know some of u are getting pissed because Sony didnt include MSC (mass storage mode) in the Xperia S GB firmware... the MTP mode is fine but some users (including me) prefer the MSC mode...
so here is a MOD/HACK which will enable that functionality!!!
[ credits ]
Napstar - for discussing this workaround which was ment for recovery but it works in OS very well
rogro82 - for creating and posting the GScript App here
finally me (DooMLoRD) - for implementing it for Xperia S and creating this easy to use package
[ requirements ]
stock GingerBread firmware (.62/.63/.73)
rooted device
recovery
[ how to install? ]
download the zip file provided in download section below
put the zip on sdcard
reboot into recovery
flash the zip from sdcard
reboot into system
open app drawer, a new app GScript will be available
open GScript app and click MENU button
select "Add Script"
now select "sdcard-mount.sh"
now click on "Save"
do the above 4 steps again to add "sdcard-unmount.sh"
now go to homescreen and long press on blank space, you will get a menu to add things to homescreen
now select "Shortcuts" and browse to "GScript Lite"
now select "sdcard-mount"
a shortcut will now be placed on homescreen to autolaunch this script
do the above 3 steps to add "sdcard-unmount"
that it!! now everything is in place!
[ how to use? ]
mounting
now when ever u have the phone connected to PC just click on the shortcut "sdcard-mount" (you might get a SuperUser prompt, accept/allow it)
at first run it might take a while for the new drive to show up as drivers are getting installed in background but once thats done sdcard should now be mounted to PC
unmounting
now to unmount, safely remove the drive from ur PC and click on shortcut "sdcard-unmount"
done sdcard is now unmounted!!!
[ downloads ]
KINDLY DO NOT MIRROR MY FILES
SDCARD Mounter as MSC Mode (V01)
test it out and let me know ur feedback!!!
ENJOY!!

DooMLoRD said:
i hope u mean "I hate MTP so much...."
Click to expand...
Click to collapse
Haha, edited
What to you think of the script, any other way to automate it?

Mycorrhiza said:
Haha, edited
What to you think of the script, any other way to automate it?
Click to expand...
Click to collapse
i personally dont want to automate it as i keep connecting to PC often but dont want the sdcard mounted all the time...

Mycorrhiza said:
Haha, edited
What to you think of the script, any other way to automate it?
Click to expand...
Click to collapse
There's an app for that I posted just before you. I'll fix it to make it work on the XPS later today
Sent from my LT26i using XDA

Related

Acessing PocketPC via linux

Hi,
I've seen this before but I'm still not sure how to do it...
Ideally what I'd like is a linux program that will sync a pocketpc device..... but I havent seen one yet...
Say I have a file I want to transfer to my pocketpc... what would the process be to do it via linux?
when I sit my xda on the cradle and run dmesg from the console I get
Code:
hub.c: new USB device 00:10.1-1, assigned address 8
usbserial.c: PocketPC PDA converter detected
usbserial.c: PocketPC PDA converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
I've also got installed the media XP expansion (Abit Max2) which has 3 different card slots. (CF,SD,MS)
I dont have a clue how to mount that either
when I type mount by itself I only get:
Code:
/dev/hdk6 on / type ext3 (rw)
none on /proc type proc (rw)
none on /proc/bus/usb type usbdevfs (rw)
none on /dev type devfs (rw)
none on /dev/pts type devpts (rw,mode=0620)
/dev/hdk11 on /home type ext3 (rw)
none on /mnt/cdrom type supermount (ro,dev=/dev/hdc,fs=auto,--,iocharset=iso8859 -15,codepage=850,umask=0)
none on /mnt/cdrom2 type supermount (ro,dev=/dev/scd0,fs=auto,--,iocharset=iso88 59-15,codepage=850,umask=0)
none on /mnt/floppy type supermount (rw,sync,dev=/dev/fd0,fs=auto,--,iocharset=i so8859-15,codepage=850,umask=0)
/dev/hdi1 on /mnt/win_c type ntfs (ro,iocharset=iso8859-15,umask=0)
/dev/hdk1 on /mnt/win_c2 type ntfs (ro,iocharset=iso8859-15,umask=0)
/dev/hdi5 on /mnt/win_d type vfat (rw,iocharset=iso8859-15,codepage=850,umask=0)
/dev/hdk5 on /mnt/win_d2 type vfat (rw,iocharset=iso8859-15,codepage=850,umask=0 )
/dev/hdk2 on /mnt/win_e type ntfs (ro,iocharset=iso8859-15,umask=0)
/dev/hdk10 on /tmp type ext3 (rw)
/dev/hdk8 on /usr type ext3 (rw)
/dev/hdk9 on /var type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
any help for getting these connected would greatly be appreciated
cheers,
Ian.
SynCE
All you ever wanted to know about activesync for Linux.
http://synce.sourceforge.net/synce/
Re: SynCE
XDA developer W4XY said:
All you ever wanted to know about activesync for Linux.
Click to expand...
Click to collapse
cheers :twisted:
hehe
Debian
Just what the doctor ordered! I've just downloaded Debian Linux. 7 Disk install. Lets see how we get on!!!
damn, you've made me want to stop my GTA:VC carnage and go reboot into linux lol....
btw... you ever used wineX3 with the GUI plugin?
I can get the GUI working but it says winex3 isnt installed
<off to go give it a go>
hmmmm nope.... the main rpm installed fine but I'm missing dependencies for some of the other modules....
gonna need to work on it hehe
hehe worked like a charm... with a little fiddling in the options file ...
now just need to find a pretty kde program that will support it

[Q] ADB - Can't Find Internally Stored Pics

Yesterday, a customer brought me a phone that seems to be hanging on boot. The phone is a stock (non-rooted) US Cellular Galaxy S II SCH-R760. I'm not trying to fix the phone. He just wants his pics and contacts. There was no SD card in the phone and he claims there never has been.
This phone was a real pain to get into recovery. I'm pretty sure it suffers from the well known power button issues. ADB will let me connect in recovery mode. It never sees the phone when trying a normal boot.
I've found reference to internal storage being located at /storage/sdcard0. There is no storage folder off the root. I tried cd'ing to it anyway but it doesn't exist. There is nothing shown in /mnt or /dev. There are no files or folders in /sdcard.
I've read about using Kies. The program sees the phone and goes into "Connecting" while attempting a normal boot or in recovery mode but it never gets beyond that point. I'm using driver version 1.5.27.0.
I've tried using "adb pull / ./s2" in an attempt to copy the entire file system. The command just hangs and no files ever copy.
***EDIT - further attempts to pull the entire file system finally worked somewhat. After restarting recovery, I was able to get the command to run but it skipped most of the file system. It only copied over the mnt, sbin, sys, and system folders. The only jpg files in there are files you may see during a firmware upgrade.
Any other thoughts about how to get this guys data?
Here is the folder list:
mnt
persist
dbdata
efs
cache
system2
preload
sdcard
etc
system
sbin
ueventd.smdkc210.rc
sys
init.goldfish.rc
data
init
tmp
init_kernel_only.rc
vendor
init.rc
init.smdkc210.rc
proc
ueventd.rc
default.prop
recovery.rc
lib
fota.rc
lpm.rc
ueventd.goldfish.rc
res
dev
There is a chance, that /storage/sdcard0 is not mounted automatically when you boot into recovery. You could try to adb shell into the device when in recovery mode and try to mount sdcard0 manually.
Another chance to get the pics: do an image backup of the sdcard0 partition and loop mount that image on your PC. On my blog you can also find a tool which is doing that. Unfortunately it's not finished yet (even if the functionality you would need is working ) and there are only a few devices supported out of the box. For other devices you would need to create a device specific config file.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
There is a chance, that /storage/sdcard0 is not mounted automatically when you boot into recovery. You could try to adb shell into the device when in recovery mode and try to mount sdcard0 manually.
Another chance to get the pics: do an image backup of the sdcard0 partition and loop mount that image on your PC. On my blog you can also find a tool which is doing that. Unfortunately it's not finished yet (even if the functionality you would need is working ) and there are only a few devices supported out of the box. For other devices you would need to create a device specific config file.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I'll need some help on this one. I'm a Windows guy. I'm not afraid to try anything but Linux and Android are beyond me without help from Google and the awesome XDA community. I looked for your tool on your blog. I'm guessing you are referring to the Android Remote Toolkit. If that is the case, it has been over 10 years since I've compiled anything. That is beyond me.
From what I can gather, the internal storage is possibly located at /devices/platform/s3c-mshci.0/mmc_host/mmc0/mmc0. If that is correct, how exactly do I mount it? There is no /devices folder. The file system is read only (no root). I can't create a folder for the mount. I've tried using the empty /sdcard folder for a mount point. My best guess at the mount command was:
Code:
mount -r -t auto /devices/platform/s3c-mshci.0/mmc_host/mmc0/mmc0 /sdcard
This produced a result of
Code:
mount: Operation not permitted
Here is a little bit of data for you to help see what the current situation is. This is the output of the mount and fs commands:
Code:
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime,mode=755 0 0
/dev/block/mmcblk0p9 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=orde
red 0 0
$ df
df
Filesystem Size Used Free Blksize
/dev 417M 76K 417M 4096
/tmp 417M 56K 417M 4096
/system 503M 484M 19M 4096
/mnt/.lfs: Function not implemented
/cache 295M 5M 290M 4096
And here is the contents of vold.fstab. I'm guessing this will show where the internal storage is located but I'm not completely comfortable with reading it.
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# internal sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun0/file
asec = disable
discard = enable
}
dev_mount sdcard /mnt/sdcard 11 /devices/platform/s3c-mshci.0/mmc_host/mmc0/mmc0
# external sdcard
{
ums_path = /sys/devices/platform/usb_mass_storage/lun1/file
asec = enable
}
dev_mount sdcard1 /mnt/sdcard/external_sd auto /devices/virtual/block/cyasblkdevblk0
# otg sdcard
{
ums_path = /dev/zero
asec = disable
}
usb_mount sdcard2 /mnt/sdcard/usbStorage auto /devices/platform/s3c_otghcd/usb
#end line ## keep this line
You need to be root to mount a file system, to to call "su" before calling the mount command.
AndDiSa said:
You need to be root to mount a file system, to to call "su" before calling the mount command.
Click to expand...
Click to collapse
That is what I was afraid of. This is the US Cellular version of this phone. I think I can halfway get it rooted but I don't think the phone would ever function again or be able to be returned to stock for warranty. The only good info I can find for getting it rooted and being able to either return to stock or turn it into a functioning phone is found here:
http://forum.xda-developers.com/showpost.php?p=23276856&postcount=3
http://forum.xda-developers.com/showthread.php?t=1677463
The problem is that the USCCROOT-sfx.exe package is not available from the download link. Any downloads I've found by the same name do not include the files mentioned in the instructions.
I think it is time to hand this phone back to the guy and tell him he is out of luck. Keep your stuff backed up and synced.
Do you have a custom recovery installed on it? If yes, you will have root access on cmd line level.
Sent from my Nexus 7 using xda app-developers app

[Q] USB OTG Connectivity Issue - Unrecognized / Not Working

OK, so this is posted in the help section, cause I need help with an issue related to USB OTG
When I plug a known good OTG cable into my Micro USB on my device, then plug a USB drive or a USB keyboard or anything, it doesnt work
I'm rooted and I've used several USB OTG apps and all of them said nothing was detected.
My phone has an Internal Drive, and then it also has its own External built-in Drive, which is read on slot "sdcard0", then I have an internal microSD slot I added myself, which is read as "Sdcard1"
I suspect it has something to do with Android being limited to 2 slots.. is that right? or can I add more?
I havent tried taking out my SD card and seeing if it works yet
I also dont know if its because my USB isnt providing Phantom Power..and maybe I need a Y OTG cable plugged into a 5v AC adapter or USB cable
I've read that you shouldnt run them for very long or they may overheat your Motherboard, is that accurate?
I've also read there should be some drivers, but that they should come standard with Jellybean.. i'm running 4.2.2
here is my phone information. thanks for any help
my android system info is posted below..
thanks for anything you might of
Android version : 4.2.2
Release Codename : REL
API LEVEL : 17
CPU ABI : armeabi-v7a
Manufacturer : alps
Bootloader : unknown
CPU ABI2 : armeabi
Hardware : mt6572
Radio : unknown
Board : mbk72_wet_jb3
Brand : alps
Device : mbk72_wet_jb3
Display : A8_V1.0
Fingerprint : alps/mbk72_wet_jb3/mbk72_wet_jb3:4.2.2/JDQ39/1378194655:user/test-keys
Host : android
ID : JDQ39
Model : A 8
Product : mbk72_wet_jb3
Tags : test-keys
Type : user
User : root
and here is what it says about external storage:
External storage: mounted
External storage Max: 1.24GB/ Free: 0.90GB
External storage removable: false
External storage emulated: false
External SDCard Max: 29.32GB/ Free: 24.42GB
-
I've seen the function on many lesser devices work fine.. and the main thing I see when going through the other devices settings, is they actually have an item in their settings > Storage, and the section is titled "External Storage" and they read usb drives with no problem
my phone doesnt have that section, i have "Internal Storage" , and "Phone Storage", and "SD Card"..
is there any sort of drivers or kernel I could safely use to get this to work??
thanks for your help.
-
It is known that some devices such as the nexus 4 cannot support otg because of insufficient power. Those are hardware issues.
Others are software issues on your rom/kernel.
Chainfire's stickmount app does not work?
Did you try your otg cable on another phone known to have otg support? (to ensure your cable isn't the issue)
Sent from my GT-N7000 using Tapatalk 4
Markuzy said:
It is known that some devices such as the nexus 4 cannot support otg because of insufficient power. Those are hardware issues.
Click to expand...
Click to collapse
Thanks for your information..
I plugged the OTG into my device, with a USB drive, nothing happened, nothing listed in "Storage", then she pulled out the crappiest fake device I've ever seen, plugged it in to that, and it worked perfectly
I browsed the device she used and it said "External Storage" in Storage... but she didnt have any "SD card" section, like I have
can you or anyone else confirm the Sections you have in Settings > Storage?
I feel that devices with SDcard0 and SDcard1 both cannot use further External storage.. is that right? its just a hypothesis based on something I read about the Android system only being able to have 2 slots or something
I removed my internal SD card, (which requires a special screwdriver since its submersible) and then tried it again.. but that didnt work.. but i didnt "unmount" the sd card first in the Storage settings, I dont know if that would make a difference
I tried connecting via USB Hub connected to my PC, but that didnt work either
I tried using StickMount, USB OTG Helper, USB Device Info, USB Host Controller, USB Host Diagnostics, Slick USB 2 Serial Terminal
also tried Free USB Serial Terminal, FTDI AOA Hyper Terminal, & Paragon NTFS&HFS+, no idea what those do..
and all of them responded the same.. nothing found.
In my Device Info, under "Features" it says: "android.hardware.usb.host"
I dont really know what else to do..
Any other Ideas?
thanks for your help
Here is a list of some other information about my device, if it makes sense to anyone:
Environment
Root Directory: /system
Data Directory: /data
Download Cache Directory: /cache
External Storage State: mounted
External Storage Directory: /storage/sdcard0
Features
android.hardware.wifi
android.hardware.location.network
android.hardware.location
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.wifi.direct
android.hardware.usb.accessory
android.hardware.camera.any
android.hardware.touchscreen.multitouch.distinct
android.hardware.bluetooth
android.hardware.sensor.light
android.hardware.microphone
android.hardware.camera.autofocus
android.software.live_wallpaper
android.hardware.telephony
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.sensor.barometer
android.hardware.usb.host
android.hardware.touchscreen.multitouch
android.hardware.sensor.compass
android.hardware.faketouch
android.hardware.camera
android.hardware.sensor.proximity
android.hardware.location.gps
android.hardware.telephony.gsm
android.hardware.camera.front
android.hardware.touchscreen
android.hardware.sensor.accelerometer
glEsVers=2.0
Mount points
MountPoint, Name, Type, Options
- /
rootfs rootfs ro,relatime
- /dev
tmpfs tmpfs rw,nosuid,relatime,mode=755
- /dev/pts
devpts devpts rw,relatime,mode=600
- /proc
proc proc rw,relatime
- /sys
sysfs sysfs rw,relatime
- /acct
none cgroup rw,relatime,cpuacct
- /mnt/secure
tmpfs tmpfs rw,relatime,mode=700
- /mnt/asec
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /mnt/obb
tmpfs tmpfs rw,relatime,mode=755,gid=1000
- /dev/cpuctl
none cgroup rw,relatime,cpu
- /system
/[email protected] ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered
- /data
/[email protected] ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered
- /cache
/[email protected] ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered
- /protect_f
/[email protected]_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered
- /protect_s
/[email protected]_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered
- /mnt/cd-rom
/dev/block/loop0 iso9660 ro,relatime
- /storage/sdcard0
/dev/block/vold/179:7 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/secure/asec
/dev/block/vold/179:7 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /storage/sdcard0/.android_secure
tmpfs tmpfs ro,relatime,size=0k,mode=000
- /storage/sdcard1
/dev/block/vold/179:97 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
- /mnt/asec/net.dinglisch.android.appfactory-1
/dev/block/dm-0 ext4 ro,dirsync,nosuid,nodev,noatime
tricky stuff..
I'm hoping maybe its a kernel thing, and that someone knows of a kernel that works

[Q] Need to access files on broken phone

Hi there, first time I write here and I probably have a lot to learn
However, a few days ago I accidently dropped by Galaxu SIII from my balcony. As a result both the screen and the touch is broken, the rest seems to work. So, of course I can connect the phone to my computer and gain access to those folders that are always monuted. However I wan't to get access to all files, like I did on the phone after I rooted it. It looks like USB debugging is off even though I was sure it was on, ADB refuses to see the phone anyway. I have tried many ideas, including remote connection to the phone, but all soloutions require to either enable USB debugging or open an app and that is exactly what I cannot do! So what can I do besides getting a new screen, which I don't want since I've already brought a new phone. Mostly I want to save my contacts and I cannot to that with Samsung KIES since I have CM11 on the phone. I really can't find any solution and I really hope somebody out there can help me!
//Oscar
SuperLarre said:
Hi there, first time I write here and I probably have a lot to learn
However, a few days ago I accidently dropped by Galaxu SIII from my balcony. As a result both the screen and the touch is broken, the rest seems to work. So, of course I can connect the phone to my computer and gain access to those folders that are always monuted. However I wan't to get access to all files, like I did on the phone after I rooted it. It looks like USB debugging is off even though I was sure it was on, ADB refuses to see the phone anyway. I have tried many ideas, including remote connection to the phone, but all soloutions require to either enable USB debugging or open an app and that is exactly what I cannot do! So what can I do besides getting a new screen, which I don't want since I've already brought a new phone. Mostly I want to save my contacts and I cannot to that with Samsung KIES since I have CM11 on the phone. I really can't find any solution and I really hope somebody out there can help me!
//Oscar
Click to expand...
Click to collapse
I suppose your files are not on the SD-Card? If they are just remove the card, but I'm pretty sure you wouldn't ask this question if it was that easy!!
broonage said:
I suppose your files are not on the SD-Card? If they are just remove the card, but I'm pretty sure you wouldn't ask this question if it was that easy!!
Click to expand...
Click to collapse
You're right, it isn't that easy!
SuperLarre said:
You're right, it isn't that easy!
Click to expand...
Click to collapse
You could try nandroid backup from recovery, maybe using an otg for watching what your're doing on a separate screen.
When all data is nandroided, you can try going trough the backup (the data section specially).
If the backup has several parts (ie, a b c d… ) you can "merge" them into a single file that could be opened with 7zip or winrar. Just open a DOS command prompt and:
type data.ext4.tar.a data.ext4.tar.b >> data.ext4.tar
Thats the example for 2 parts a and b.Then, after unpacking the tar, you could look into the data to get stuff. For example…
Sms & mms:
data/data/com.android.providers.telephony/databases
Contacts:
data/data/com.android.providers.contacts/databases
And a lot of other stuff. Note that you need something to read-edit ".db" files, like an sqlite editor.
Alternatively, if you're using a similar phone, with same manufacturer, a close android version (for example not gb 2.3 vs kk 4.4, but yes jb 4.1 vs jb 4.3), etc, then you could copy such addresses and paste them inside your new phone (crossing fingers and any other crossable bodypart) and you might get all that stuff back.
Good luck.
Put a blank SD (formatted as FAT32 or exFat) on the phone. It must be sized as the phone's internal memory size (16 or 32GB)
Set the phone in download mode. Flash Phil'z recovery with Odin.
Start the phone in recovery mode. Connect usb to computer and after 10-15 seconds ADB will be enabled.
/data is mounted by default (internal SD is stored inside /data).
Now mount the external SD:
enter adb shell and put:
Code:
mount /dev/block/mmcblk1p1 /external_sd
If any error appear, stop.
If nothing appeared, check that it was sucessfully mounted. Ensure that mmcblk0p12 and mmcblk1p1 are mounted as this!
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type exfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro)
Now copy all the internal storage to the external SD:
Code:
mkdir /external_sd/intData; cd /data; tar cf - * | ( cd /external_sd/intData; tar xf -)
Take a breath and come 15 minutes later to see if it finished. It may take more if the device was nearly full.
After it comes back to shell (you see the # symbol again) it means it's over.
Now let's flush the filesystems and unmount the partitions :
Code:
cd /; sync; umount /external_sd; umount /data
Remove the battery and the sd card.
Put the SD on your computer...done!
- The internal SD is stored on /data/media.
- The app data is on /data/data.
- The apps are on /data/app
- Your contacts are stored on /data/data/databases/com.android.providers.contacts/contacts2.db.
Putting that DB file on the same place of other Android phone and rebooting after will restore your contacts. Or you can convert them to VCF:
http://askubuntu.com/questions/445997/how-to-convert-androids-contacts2-db-to-vcf
Good luck!
dabyd64 said:
Put a blank SD (formatted as FAT32 or exFat) on the phone. It must be sized as the phone's internal memory size (16 or 32GB)
Set the phone in download mode. Flash Phil'z recovery with Odin.
Start the phone in recovery mode. Connect usb to computer and after 10-15 seconds ADB will be enabled.
/data is mounted by default (internal SD is stored inside /data).
Now mount the external SD:
enter adb shell and put:
Code:
mount /dev/block/mmcblk1p1 /external_sd
If any error appear, stop.
If nothing appeared, check that it was sucessfully mounted. Ensure that mmcblk0p12 and mmcblk1p1 are mounted as this!
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type exfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro)
Now copy all the internal storage to the external SD:
Code:
mkdir /external_sd/intData; cd /data; tar cf - * | ( cd /external_sd/intData; tar xf -)
Take a breath and come 15 minutes later to see if it finished. It may take more if the device was nearly full.
After it comes back to shell (you see the # symbol again) it means it's over.
Now let's flush the filesystems and unmount the partitions :
Code:
cd /; sync; umount /external_sd; umount /data
Remove the battery and the sd card.
Put the SD on your computer...done!
- The internal SD is stored on /data/media.
- The app data is on /data/data.
- The apps are on /data/app
- Your contacts are stored on /data/data/databases/com.android.providers.contacts/contacts2.db.
Putting that DB file on the same place of other Android phone and rebooting after will restore your contacts. Or you can convert them to VCF:
http://askubuntu.com/questions/445997/how-to-convert-androids-contacts2-db-to-vcf
Good luck!
Click to expand...
Click to collapse
Amazing answer, however during the first steps, could he be blocked? Due to not seeing the screen? Maybe I'm over complicating things.

SDcard0 corrupt after cm-13.0-20160304-NIGHTLY-i9100

Hello,
I've been testing Android 6.0 on my Galaxy S2 about 1-1.5 month. Internal memory was repartitioned. I could take photos, videos, read, send them, all was fine.
SDcard0 was working until last update and now I can't find anything else but to format it. Don't want to loose my camera photos. Obviously I can't remove it from phone and try to recover files from laptop. Please, advise.
Using Cyanogenmod recovery (don't know version, something new with much less functionality that was in CWM recovery).
Flashing updates through ADB sideload with no problem.
Sorry, if this has been asked before.
Code:
C:\adb>adb shell
[email protected]:/ # ls
adb_keys file_contexts property_contexts sideload
boot.txt fstab.smdk4210 res storage
cache init sbin sys
charger init.rc sdcard system
data init.recovery.smdk4210.rc seapp_contexts tmp
default.prop mnt selinux_version ueventd.rc
dev oem sepolicy ueventd.smdk4210.rc
etc proc service_contexts
[email protected]:/ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 402468 24 402444 1% /dev
tmpfs 402468 12 402456 1% /tmp
tmpfs 402468 0 402468 0% /storage
127|[email protected]:/ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
/dev/block/mmcblk0p9 on /system type ext4 (ro,seclabel,noatime,user_xattr,barrier=1,data=ordered)
[email protected]:/ #
Code:
[email protected]:/sdcard # cat /etc/fstab
/dev/block/mmcblk0p9 /system ext4 defaults 0 0
/dev/block/mmcblk0p7 /cache f2fs inline_data,inline_xattr,discard 0 0
/dev/block/mmcblk0p7 /cache ext4 journal_async_commit,errors=panic 0 0
/dev/block/mmcblk0p1 /efs ext4 journal_async_commit,errors=panic 0 0
/dev/block/mmcblk0p10 /data f2fs inline_data,inline_xattr,discard 0 0
/dev/block/mmcblk0p10 /data ext4 noauto_da_alloc,journal_async_commit,errors=panic 0 0
/dev/block/mmcblk0p12 /preload ext4 journal_async_commit 0 0
2|[email protected]:/system # mount -a
mount: '/dev/block/mmcblk0p7'->'/cache': Invalid argument
mount: '/dev/block/mmcblk0p1'->'/efs': No such file or directory
mount: '/dev/block/mmcblk0p10'->'/data': Invalid argument
mount: '/dev/block/mmcblk0p12'->'/preload': No such file or directory
Code:
8|[email protected]:/ # umount /dev/block/mmcblk0p10
[email protected]:/ # e2fsck -fv /dev/block/mmcblk0p10
e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
17784 inodes used (4.52%, out of 393216)
1181 non-contiguous files (6.6%)
21 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 7/7/7
Extent depth histogram: 17602/128
635762 blocks used (40.42%, out of 1572864)
0 bad blocks
0 large files
15707 regular files
2022 directories
4 character device files
0 block device files
5 fifos
0 links
34 symbolic links (34 fast symbolic links)
3 sockets
------------
17775 files
Code:
[email protected]:/ # cat fstab.smdk4210
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache f2fs noatime,nosuid,nodev,inline_data,inline_xattr,discard wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data f2fs noatime,nosuid,nodev,inline_data,inline_xattr,discard wait,encryptable=footer,length=-16384
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=footer,length=-16384
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,noemulatedsd,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,encryptable=userdata
/devices/platform/s3c_otghcd/usb* auto auto defaults voldmanaged=usb:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
# zRAM
/dev/block/zram0 none swap defaults zramsize=268435456
This has to be sdcard0. What next? How to mount it manually?
dev_mount command not found in my phone's OS.
Code:
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0* auto auto defaults wait,voldmanaged=sdcard0:11,noemulatedsd,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc1* auto auto defaults wait,voldmanaged=sdcard1:auto,encryptable=userdata
ive got this problem also...have you managed to find a fix??
Installed Ubuntu (choose whatever you want) inside VMware workstation. All that runs in Windows host.
Then in Ubuntu terminal: sudo apt-get install android-tools-adb android-tools-fastboot
Make sure to allocate Ubuntu virtual hard disk at least 25GB. Don't ask how I know.
Enable debugging, enable adb, revoke and accept authorisation (whatever it's called).
Pulled out whole internal memory:
adb reboot recovery
adb devices (to see if phone is connected) - if not adb kill-server and adb start-server
then
adb pull /dev/block/mmcblk0 mmcblk0.img
Process lasted 4-5 hours.
Then copy 15-16GB file to NTFS partition where you can access it from Windows.
After that opened mmcblk0.img with FTK Imager (from Windows) and found DCIM folder and extracted all that.
That's it.
Update:
corrupt sdcard0 is back again. Was OK for 4 days after total wipe and reinstall with cm13.0-20160325 . Looks like I need to swap internal memory to external SD. From Storage & USB in Settings i get error while formatting it:
Code:
Command xx volume partition disk: 179_0 public
failed with 400 xx Command failed
where xx is number. This time 79, 80, ... 82 (while retrying to format and read whole error message).
I ended up reverting back to 4.1.2 stock Samsung. I will update this thread next month if it was software or hardware fault.
Testing Lollipop and Marshmallow was fun, but this is over my patience. See you next year.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources