I have a new external micro sd card for my ICS device (worked fine at first). I tried using the Paragon NTSF android app and evidently screwed my card up nice and hard. Here is what i can and cant do (connecting usb via 2 steps microsd->sd then sd->usb):
1. Windows 7 Disk Management sees the device (but device says something along the lines of no medium)
2. linux Disk Utility sees the device although under "capacity" it says "no medium found"
(when i try to format the device i get the error: "Error creating partition table: helper exited with exit code 1: cannot open /dev/sdb: No medium found")
3. linux command: [email protected]:~$ sudo dd if=/dev/zero of=/dev/sdb bs=512 count=1
dd: opening `/dev/sdb': No medium found
4. linux command:
Jan 26 17:47:56 adam-NC20-NB20 kernel: [ 596.153946] scsi4 : usb-storage 1-3:1.0
Jan 26 17:47:57 adam-NC20-NB20 kernel: [ 597.152949] scsi 4:0:0:0: Direct-Access Generic Storage Device 0.00 PQ: 0 ANSI: 2
Jan 26 17:47:57 adam-NC20-NB20 kernel: [ 597.161322] sd 4:0:0:0: Attached scsi generic sg1 type 0
Jan 26 17:47:57 adam-NC20-NB20 kernel: [ 597.162392] sd 4:0:0:0: [sdb] Attached SCSI removable disk
sudo fdisk 597.162392
(So it sees the device)
any help? Im very nub at linux. Also a nub at IT in general but hopefully i can fix my device.
(There is no data on the drive so im willing to try anything at all)
Reading around i came up with a hypothesis that i deleted some type of software that is needed for the hardware to work???
Have you tired inserting the card into another phone to format it? Which Linux distro are you using?
May be your partition table is gone. try something like partition magic and use repair drive option. Its better if you can use a micro SD card reader for this.
@weatheredeyec57
using lubutu and also ubuntu for the linux distros. tried multiple phones as well
@suki300me
why is a direct microsd reader better than going through micro to regular?
Related
I have 2 questions. I did a search and found that usb devices should work with the gtab, so I'm trying to mount it.
Any idea how I can mount the devices?
I'm trying to mount
1. 500 GB drive
2. Canon Camera with 32 GB SD card
Second question: Can I mount them both at the same time? It looks like the gtab has 2 USB ports, 1 regular, 1 mini
I'm trying to offload the video clips so I can record some more.
Thanks in advance for the help.
Mini is for Slave
Normal is for Host
I think someone found a way to make the Mini a Host, not to sure.
Does this mean I can only use the regular port to connect to a storage device?
I have no need to swap them....just a need to use both to connect to external hard drives:-D
Can I use a usb hub to connect 2 USB devices? (camera and 500 GB drive)
Well, I can tell you this much as least:
If one wanted to connect 2 USB mass storage devices to their g Tab and were hard pressed to find an alternative, the docking station that fits the proprietary plug has an additional USB port as well as an HDMI port and an ethernet port.
Unfortunately I can't tell you anything else with certainty.
scyld said:
Well, I can tell you this much as least:
If one wanted to connect 2 USB mass storage devices to their g Tab and were hard pressed to find an alternative, the docking station that fits the proprietary plug has an additional USB port as well as an HDMI port and an ethernet port.
Unfortunately I can't tell you anything else with certainty.
Click to expand...
Click to collapse
Thanks
I guess I should still get a netbook for this purpose then.
By the way, for the host port (regular USB port). It seems to connect (I have power on the usb device), but the files are not showing up in the file manager (ES file manager) or ifilemanager. Is there anything else I have to do for it to recognize the drive?
TheFlyingPig said:
By the way, for the host port (regular USB port). It seems to connect (I have power on the usb device), but the files are not showing up in the file manager (ES file manager) or ifilemanager. Is there anything else I have to do for it to recognize the drive?
Click to expand...
Click to collapse
We'll have to take things step by step.
First, is the SD card on the camera a removable microSDHC card? If it is, you could just remove it and insert it into the gTablet's microSDHC slot instead of connecting the camera to a USB hub.
Second, have the 2 devices been detected correctly by the kernel? Both individually and then together on a USB-hub?
For example, if I connect my 1TB Maxtor USB HDD to the gTablet, the status bar message informs me that "SD card blank or has unsupported filesystem". This means that the drive was detected, but the NTFS filesystem on it was not recognized, and therefore the drive was not mounted (the vold program which does the mounting only likes ext4 or VFAT filesystems for automounting). I'm assuming that since you have a 500GB drive, it is formatted as NTFS?
If Android does not detect a drive insertion, check the kernel messages. In a Terminal, after I insert a USB drive, I do:
Code:
$ [B]dmesg | tail -n 20[/B]
[144874.547211] usb 1-1.1: New USB device found, idVendor=0d49, idProduct=7410
[144874.554415] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[144874.562368] usb 1-1.1: Product: Basics Desktop
[144874.567435] usb 1-1.1: Manufacturer: Maxtor
[144874.572010] usb 1-1.1: SerialNumber: 2HBEWHZR
[144874.580165] usb 1-1.1: configuration #1 chosen from 1 choice
[144874.589418] scsi0 : SCSI emulation for USB Mass Storage devices
[144874.601098] usb-storage: device found at 3
[144874.601123] usb-storage: waiting for device to settle before scanning
[144879.597766] scsi 0:0:0:0: Direct-Access Maxtor Basics Desktop 0125 PQ: 0 ANSI: 4
[144879.617283] sd 0:0:0:0: Attached scsi generic sg0 type 0
[144879.624170] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[144879.634583] sd 0:0:0:0: [sda] Write Protect is off
[144879.639482] sd 0:0:0:0: [sda] Mode Sense: 2d 08 00 00
[144879.639505] sd 0:0:0:0: [sda] Assuming drive cache: write through
[144879.647662] sd 0:0:0:0: [sda] Assuming drive cache: write through
[144879.653918] sda: sda1
[144879.688927] sd 0:0:0:0: [sda] Assuming drive cache: write through
[144879.695477] sd 0:0:0:0: [sda] Attached SCSI disk
[144879.813410] usb-storage: device scan complete
to check if the drive was detected. I can see by the messages that the Maxtor drive was detected by the kernel and that I can mount it manually by using the /dev/block/sda1 device. If you don't see similar messages, you're out of luck. If the camera is also detected, it may show up as /dev/block/sdbn.
If everything is detected properly, but, just not mounted, you can mount things manually.
For this, you have to know which kernel you're running. There are 2 kernels that are commonly used on the gTablet: clemsyn's and pershoot's. I use pershoot's kernel so my instructions will be for that. The pershoot kernel supports NTFS filesystems, but, this support is not built into the kernel. Support is instead provided using kernel modules which you'll have to download first from the author's website and then load manually.
Download the correct kernel modules file for the running kernel. Find the kernel version first:
Code:
$ [B]uname -a[/B]
Linux localhost 2.6.32.40-cyanogenmod #1 SMP PREEMPT Fri May 13 17:37:53 EDT 2011 armv7l GNU/Linux
The kernel version is 2.6.32.40. I go to http://droidbasement.com/db-blog/ and download the kernel modules file for that kernel version which would be this file for Gingerbased ROMs: lib-2632.40_gb.tar.gz, or, this file for Froyo based ROMS: lib-2632.40.tar.gz. Note the "_gb" suffix. Extract the file on your PC and then transfer these 2 file onto the gTablet: nls_utf8.ko and ntfs.ko. You should, ideally, put them in /system/lib/modules, but, it you can just leave it on the gTablet's SD card.
Load the kernel modules (I'm assuming now that they're on /mnt/sdcard), then mount the HDD:
Code:
$ [B]su[/B]
# [B]insmod /mnt/sdcard/nls_utf8.ko[/B]
# [B]insmod /mnt/sdcard/ntfs.ko[/B]
# [B]mount -t ntfs -o nls=utf8 /dev/block/sda1 /mnt/usbdisk[/B]
The HDD's contents will now be present in /mnt/usbdisk which is a directory that already exists for mounting USB devices. The /dev/block/sda1 device name we determined using the kernel messages. If you have partitions on the HDD, you can mount them individually using their device names which look like /dev/block/sdan, where n is a number. Look in /dev/block/ to see what partitions can be mounted.
To mount the camera, create a new directory somewhere else, let's say /mnt/sdcard/tmp, and then mount it in that directory. I'm assuming here that the camera's SD card was detected as /dev/block/sdb1 and that it has a VFAT (aka FAT32) filesystem on it.
Code:
$ [B]su[/B]
# [B]mount -t vfat /dev/block/sdb1 /mnt/sdcard/tmp[/B]
After you've finished, unmount both devices before you unplug:
Code:
$ [B]su[/B]
# [B]umount /mnt/usbdisk[/B]
# [B]umount /mnt/sdcard/tmp[/B]
TheFlyingPig said:
By the way, for the host port (regular USB port). It seems to connect (I have power on the usb device), but the files are not showing up in the file manager (ES file manager) or ifilemanager. Is there anything else I have to do for it to recognize the drive?
Click to expand...
Click to collapse
The files are in a folder called USBDISK - hunt around, you will find it.
Hello all,
I attached my SGS2 to my linux computer and was able to access the internal SD card, but was unable to access the external SD card. I was able to navigate with RootExplorer when my device wasn't plugged in to verify that it was mounted, and even did so using the adb shell.
After a bunch of reading, I found out that when you plug in the SGS2, it should show up as TWO devices. In fact it does on my work Win7 machine.
Curious to see what was going on, I looked inside the system logs to see if there were multiple partitions and KDE was only picking up the first one:
[157599.812858] usb 2-1.4.7.3: new high speed USB device using ehci_hcd and address 36
[157599.887980] usb 2-1.4.7.3: New USB device found, idVendor=04e8, idProduct=685e
[157599.887988] usb 2-1.4.7.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[157599.887994] usb 2-1.4.7.3: Product: SAMSUNG_Android
[157599.887998] usb 2-1.4.7.3: Manufacturer: SAMSUNG
[157599.888003] usb 2-1.4.7.3: SerialNumber: ------
[157599.889184] scsi18 : usb-storage 2-1.4.7.3:1.0
[157599.889874] cdc_acm 2-1.4.7.3:1.1: This device cannot do calls on its own. It is not a modem.
[157599.889978] cdc_acm 2-1.4.7.3:1.1: ttyACM1: USB ACM device
[157600.888206] scsi 18:0:0:0: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[157600.888625] sd 18:0:0:0: Attached scsi generic sg2 type 0
[157600.891070] sd 18:0:0:0: [sdc] Attached SCSI removable disk
[157615.570542] sd 18:0:0:0: [sdc] 24133632 512-byte logical blocks: (12.3 GB/11.5 GiB)
[157615.571050] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[157615.573554] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[157615.576323] sdc:
[157735.385098] VFS: busy inodes on changed media or resized disk sdc
[158087.331648] usb 2-1.4.7.3: USB disconnect, address 36
Click to expand...
Click to collapse
As you can see, it found exactly one disk: /dev/sdc.
Am I missing something? Thanks!!
edit:
I may have found a possible solution: http://androidforums.com/samsung-captivate/156875-help-linux-desktop-connect-via-usb.html#post1490358 (Enable "Probe all LUNs on each SCSI device" in the kernel). Will update with resolution.
Did you solve this problem?
How are you connecting? Through the network settings and with the usb mass storage option?
This is what I get this through dmesg:
[17413.586068] usb 1-1: new high speed USB device using ehci_hcd and address 3
[17413.701104] scsi4 : usb-storage 1-1:1.0
[17414.703016] scsi 4:0:0:0: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[17414.703016] scsi 4:0:0:1: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[17414.704007] sd 4:0:0:0: Attached scsi generic sg2 type 0
[17414.704467] sd 4:0:0:1: Attached scsi generic sg3 type 0
[17414.710003] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[17414.710003] sd 4:0:0:1: [sdc] Attached SCSI removable disk
Then I can mount either of them manually.
Yep! I didn't get to test it until just now, had some life things that took importance. Looks like the post about the probing for multiple LUNs was correct. The device now shows up as two drives as expected.
Has anyone managed to connect their S2 using MTP when running Ubuntu? Obviously I know that it's a very simple tast to just connect via mass storage instead, but I'm interested to know.
I think that Samsung have some weird implementation of MTP because I was able to connect and copy files when I was running CM9 but not on stock ICS. I always get the error message:
Unable to mount SAMSUNG_Android
Error initialising camera: -60: Could not lock the device
Though it does mount and I can see the root of both SDCards, all the folders are empty and I can't copy any files to the cards from the computer as I get a error message reading:
There was an error copying the file into gphoto2://[usb:001,010]/store_00020002.
The same happens whether I try to use MTP or PTP.
I think the problem lies in that libmtp-1.1.3 contains fixes for the S2 but that version isn't included with 11.10 or 12.04
hint
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
alpike said:
did you find out,
i got mine working by doing below guide,
think the issue is we have our phones in USB Debugging Mode
ubuntuforums.org/archive/index.php/t-1806119.html
Steps:
1. Go to: Settings ➔ Wireless and network ➔ USB utilities.
2. Connect your phone to your PC using a USB cable.
3. Tap Connect storage to PC.
4. Scroll down from the phone notification bar. Click USB Mass Storage and tap "Connect storage from PC". The android robot will turn from green to orange. (Important step!)
5. From your PC, open the folder to view your files.
6. Copy files between your PC and the memory card.
Click to expand...
Click to collapse
That's connecting via USB mass storage, not mtp. But thanks for trying.
Sent from my GT-I9100 using XDA
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
what I have found out that mtpfs is unable to preserve timestamps of the files at least on my install.
gphoto2 backend worked fine on CM9 now wile testing CM10 its a bit buggy, I can get the list of files but I am unable to read or rename them.
Most likelly it will improve as development of CM10 progresses rapidly.
Mounting my Galaxy S3 when connected via USB to my Ubuntu computer
D4rKn3sSyS said:
Very easy
Code:
cd ~
sudo apt-get install mtpfs
sudo mkdir /mtp
sudo chmod 775 /mtp
sudo mtpfs -o allow_other /mtp
For dismount
Code:
sudo umount mtpfs
You need to have your device rules ( Check how to install adb if you dont )
Click to expand...
Click to collapse
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
slubkin said:
I went through the steps above, except the last: How do I install adb? (device rules ?).
While my phone is so connected, the command:
cd /mtp
produces the result
bash: cd: /mtp: Transport endpoint is not connected
Help greatly appreciated.
Thank you,
-- Saul
Click to expand...
Click to collapse
Ubuntu 13.04 is a drastic improvement for MTP support. I have not got around to trying my S II but I successfully managed a family friends Galaxy TAB 2 with MTP with zero manual modifications to Ubuntu. Everything worked perfect plug and play out of the box.
I have also tried old versions to know how bad they were compared to 13.04.
No luck with S2 and Ubuntu 13.04
I'm on Android 4.1.2 and trying to connect via USB to Ubuntu 13.04. Error I get is that my device is not an MTP device, which it's not as its using USB
Issue is that I don't see the mounted android partitions. To make this worse, it works every now and then. Following is the syslog and the outpu of lsusb
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Aug 26 23:04:00 ml kernel: [134718.425536] usb 1-5: new high-speed USB device number 11 using ehci-pci
Aug 26 23:04:00 ml kernel: [134718.558636] usb 1-5: New USB device found, idVendor=04e8, idProduct=685b
Aug 26 23:04:00 ml kernel: [134718.558647] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Aug 26 23:04:00 ml kernel: [134718.558655] usb 1-5: Product: SAMSUNG_Android
Aug 26 23:04:00 ml kernel: [134718.558661] usb 1-5: Manufacturer: SAMSUNG
Aug 26 23:04:00 ml kernel: [134718.558666] usb 1-5: SerialNumber: 001964815b817e
Aug 26 23:04:05 ml kernel: [134723.546077] usb 1-5: can't set config #1, error -110
Aug 26 23:04:05 ml mtp-probe: checking bus 1, device 11: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5"
Aug 26 23:04:05 ml mtp-probe: bus: 1, device: 11 was not an MTP device
[email protected]:~$ lsusb
Bus 001 Device 011: ID 04e8:685b Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II] (mass storage mode)
Bus 003 Device 002: ID 046d:c52e Logitech, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Hi Guys,
my Samsung Galaxy S 2 died below my bike. Sadly I have important data on my internal storage. I can switch it on and on my console looking for
Code:
tail -f /var/log/syslog
I get only an
Code:
Sep 17 19:54:44 goshbook kernel: [ 5098.941930] scsi13 : usb-storage 2-1.2:1.0
Sep 17 19:54:44 goshbook mtp-probe: checking bus 2, device 17: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
Sep 17 19:54:44 goshbook mtp-probe: bus: 2, device: 17 was not an MTP device
Sep 17 19:54:45 goshbook kernel: [ 5099.938528] scsi 13:0:0:0: Direct-Access Samsung File-CD Gadget 0000 PQ: 0 ANSI: 2
Sep 17 19:54:45 goshbook kernel: [ 5099.939126] scsi 13:0:0:1: Direct-Access Samsung File-CD Gadget 0000 PQ: 0 ANSI: 2
Sep 17 19:54:45 goshbook kernel: [ 5099.940753] sd 13:0:0:0: Attached scsi generic sg1 type 0
Sep 17 19:54:45 goshbook kernel: [ 5099.941471] sd 13:0:0:1: Attached scsi generic sg2 type 0
Sep 17 19:54:45 goshbook kernel: [ 5099.948449] sd 13:0:0:0: [sdb] Attached SCSI removable disk
Sep 17 19:54:45 goshbook kernel: [ 5099.948517] sd 13:0:0:1: [sdc] Attached SCSI removable disk
but I can't access anything.
Installed is Cyanogenmod 9 nightly from end of june.
Do you have any advices how I could get to my data - because I can't see anything on the display anymore.
When switching on it makes a strange sound "Drrrammmm" or so...
Any hint appreciated...
Regards - Gosh
Mr.Gosh said:
Hi Guys,
my Samsung Galaxy S 2 died below my bike. Sadly I have important data on my internal storage. I can switch it on and on my console looking for
Code:
tail -f /var/log/syslog
I get only an
Code:
Sep 17 19:54:44 goshbook kernel: [ 5098.941930] scsi13 : usb-storage 2-1.2:1.0
Sep 17 19:54:44 goshbook mtp-probe: checking bus 2, device 17: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
Sep 17 19:54:44 goshbook mtp-probe: bus: 2, device: 17 was not an MTP device
Sep 17 19:54:45 goshbook kernel: [ 5099.938528] scsi 13:0:0:0: Direct-Access Samsung File-CD Gadget 0000 PQ: 0 ANSI: 2
Sep 17 19:54:45 goshbook kernel: [ 5099.939126] scsi 13:0:0:1: Direct-Access Samsung File-CD Gadget 0000 PQ: 0 ANSI: 2
Sep 17 19:54:45 goshbook kernel: [ 5099.940753] sd 13:0:0:0: Attached scsi generic sg1 type 0
Sep 17 19:54:45 goshbook kernel: [ 5099.941471] sd 13:0:0:1: Attached scsi generic sg2 type 0
Sep 17 19:54:45 goshbook kernel: [ 5099.948449] sd 13:0:0:0: [sdb] Attached SCSI removable disk
Sep 17 19:54:45 goshbook kernel: [ 5099.948517] sd 13:0:0:1: [sdc] Attached SCSI removable disk
but I can't access anything.
Installed is Cyanogenmod 9 nightly from end of june.
Do you have any advices how I could get to my data - because I can't see anything on the display anymore.
When switching on it makes a strange sound "Drrrammmm" or so...
Any hint appreciated...
Regards - Gosh
Click to expand...
Click to collapse
You can use ADB if u can still connect your device to your Pc.
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.76B
GT I9100
Next phone: Galaxy NOTE II
Below the Bike... Happened to me once...
Anyways as Jokesy said adb can help...
And jokesy i stole a part of your sig... And you leaving SII :'(
Who solve people's problem? :'(
[India Only] The OTG Giveaway
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1
Omaxe said:
Below the Bike... Happened to me once...
Anyways as Jokesy said adb can help...
And jokesy i stole a part of your sig... And you leaving SII :'(
Who solve people's problem? :'(
[India Only] The OTG Giveaway
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1
Click to expand...
Click to collapse
I'll be keeping both phones, so I'll still be a little active here. No worries!
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.76B
GT I9100
Next phone: Galaxy NOTE II
Jokesy said:
I'll be keeping both phones, so I'll still be a little active here. No worries!
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.76B
GT I9100
Next phone: Galaxy NOTE II
Click to expand...
Click to collapse
M also waiting for nexus device... If samsung launch it
[India Only] The OTG Giveaway
Peace
Hit Thanks & It will Disappear
Sent from S II Running Fully Modified Official ICS 4.0.4
Next Device: Upcoming Nexus
Data Recovery on Galaxy s 2
OK, I got to the Device via adb / QtADB - but only in recovery mode I can connect.
Now I cant find the data on the phone...
any idea where the fotos are stored when I take pictures to the internal storage?
Regards - Gosh
Photos: are under DCIM\Camera, not sure what the root file structure is exactly, I think it goes /mnt/sdcard/DCIM/Camera
Mr.Gosh said:
OK, I got to the Device via adb / QtADB - but only in recovery mode I can connect.
Now I cant find the data on the phone...
any idea where the fotos are stored when I take pictures to the internal storage?
Regards - Gosh
Click to expand...
Click to collapse
Seems i got a similar problem here: I just see the file structure but most folders (especially sd / emmc / etc.) seem to be empty. => There is no DCIM folder in any of the given folders.
Does anyone know, what should be seen, if there was usb-debugging allowed or not? And I assume usb-debugging is not allowed on my phone. So is there any opportunity to get to the storage data?
jammerlappen said:
Seems i got a similar problem here: I just see the file structure but most folders (especially sd / emmc / etc.) seem to be empty. => There is no DCIM folder in any of the given folders.
Does anyone know, what should be seen, if there was usb-debugging allowed or not? And I assume usb-debugging is not allowed on my phone. So is there any opportunity to get to the storage data?
Click to expand...
Click to collapse
Type the following
adb device
#it will show your device info if it's connected via ADB. Now try to pull everything in your sdcard by typing,
adb pull /sdcard
Swyped from my Samsung Galaxy SII
Supercharged ParanoidAndroid 2.12
Dorimanx kernel 5.76B
GT I9100
Next phone: Galaxy NOTE II
If I do so (in recovery mode), there are 0 files detected / copied. The device id is something like 12345678ABCDEF.
jammerlappen said:
If I do so (in recovery mode), there are 0 files detected / copied. The device id is something like 12345678ABCDEF.
Click to expand...
Click to collapse
The reason why you could not copy anything was because you need to manually mount your /emmc under mounts and storage in recovery. you cannot do this since your screen is not readable.
There are two ways to copy out your files:
A. Boot your phone normally, then follow these steps:
1. Connect your device to your pc
2. Open command prompt from Adb folder. (hold shift key, then right click on a blank space, select open command window here)
3. #check if your device is connected via adb by typing in the command window: adb devices
4. #copy all the content of your sdcard by typing in the command window:
adb pull /sdcard \mysdcard
wait for the process to finish
Check you C: drive for a folder named "mysdcard". all the files and folders in your internal storage will be there.
B. Boot to recovery, then follow these steps:
1. Connect your device to your pc
2. Open command prompt from Adb folder. (hold shift key, then right click on a blank space, select open command window here)
3. #check if your device is connected via adb by typing in the command window:
adb devices
4. adb shell
5. mount sdcard
6. ## check the directories of the sdcard just to be sure by typing:
ls /sdcard
7. exit
8. adb pull /sdcard \mysdcard
wait for the process to finish
Check you C: drive for a folder named "mysdcard". all the files and folders in your internal storage will be there.
If you face any errors, let me know
Good luck
This is my first post, please bear with me if I'm asking an obvious question. I am trying to update my WinCE 6.0 sat nav to an Android OS (I believe my current version is known as S100 and (I think) I am upgrading to S150)
Here's what I have been supplied by the manufacturer of my sat nav:
SD Boot Fusing Tool
2 x BIN files to be fused to the SD card; SD-bl1-8k.bin and u-boot_sdboot.bin
A Panasonic SD card formatter
I have followed their rough instructions which are converted from Chinese:
1. Format SD card to FAT32 format performing complete erase
2. Add the 2 x BIN files to the tool for fusing to the SD card. This is where I am stuck.
I am receiving the following error message "Can't Read MBR Sector from Drive"
To confirm the SD card is not the issue I have swapped SD cards, run chkdsk /f against the drive and used the Rufus tool to obtain the following log output:
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Windows 7 MBR
Found volume GUID \\?\Volume{d9671328-5dee-11e5-825a-5442490c7ece}\
Successfully remounted Volume{d9671328-5dee-11e5-825a-5442490c7ece}\ on G:\
Found USB 2.0 device 'HSDPA MMC Storage USB Device' (1C9E:6061)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 483, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x065A8C2D
Drive has a Windows 7 Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 3.7 GB (3979345920 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Can anyone help me as I do not understand what the issue is. This is the first time I have attempted this type of thing.
Cheers
Chris
This is the error I am seeing:
66chrisscott99 said:
This is my first post, please bear with me if I'm asking an obvious question. I am trying to update my WinCE 6.0 sat nav to an Android OS (I believe my current version is known as S100 and (I think) I am upgrading to S150)
Here's what I have been supplied by the manufacturer of my sat nav:
SD Boot Fusing Tool
2 x BIN files to be fused to the SD card; SD-bl1-8k.bin and u-boot_sdboot.bin
A Panasonic SD card formatter
I have followed their rough instructions which are converted from Chinese:
1. Format SD card to FAT32 format performing complete erase
2. Add the 2 x BIN files to the tool for fusing to the SD card. This is where I am stuck.
I am receiving the following error message "Can't Read MBR Sector from Drive"
To confirm the SD card is not the issue I have swapped SD cards, run chkdsk /f against the drive and used the Rufus tool to obtain the following log output:
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Windows 7 MBR
Found volume GUID \\?\Volume{d9671328-5dee-11e5-825a-5442490c7ece}\
Successfully remounted Volume{d9671328-5dee-11e5-825a-5442490c7ece}\ on G:\
Found USB 2.0 device 'HSDPA MMC Storage USB Device' (1C9E:6061)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 483, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x065A8C2D
Drive has a Windows 7 Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 3.7 GB (3979345920 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Can anyone help me as I do not understand what the issue is. This is the first time I have attempted this type of thing.
Cheers
Chris
This is the error I am seeing:
Click to expand...
Click to collapse
Might help you to provide a pic of the unit itself. There are literally hundreds of these devices.
Sent from my SGH-I337M using Tapatalk
Flukester69 said:
Might help you to provide a pic of the unit itself. There are literally hundreds of these devices.
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Good shout. Here it is:
m.alibaba.com/product/1447649060/ZESTECH-2-DIN-CAR-DVD-STEREO.html
And the spec:
m.alibaba.com/product/1447649060/ZESTECH-2-DIN-CAR-DVD-STEREO/specifications.html
Sorry, I'm too new to post urls ?
Sent from my D6603 using Tapatalk
Bump. Anyone? Ty
Sent from my D6603 using Tapatalk
Solved. It appears that you cannot write to that sector unless you run the application as an administrator
Sent from my D6603 using Tapatalk