sdcard can't mount - AT&T Samsung Galaxy S II SGH-I777

Hi ,
This is new my first post.
I have samsung SGH-i777 initiallly when i bought it has 4.3& it has 16GB card. cyanogenmod10.2 with rooted. but it always restarted because of OOM.
so i installed kitkat 4.4 omnirom and few day it was working good,no problem arise. after week it doesn't show external storage it only show internal storage of 2GB. so again flashed ROM this time with 4.1 & it shows 16GB memory then i could use those space. but problem is if i go to CWM revcovery(i tried latest or old versions) take backup or installing zip got error like this "sdcard can't mount"
kindly help me out of this issue.
Thx

Switching to a different kernel/recovery affects whether the card can be mounted? This sounds like the CWM recovery that you chose doesn't support the filesystem of the Sd Card.
What file system is the SD card using?
For greatest compatibility, I suggest formatting the external Sd Card to Fat32.
If you're going to stay on 4.4, AND if you plan on playing music from the sdcard, I suggest formatting it to exfat (successful workaround for a KK bug).
^^beware, the stock recovery and firmware will NOT be able to read any exfat formatted partition
^^once formatted to ExFat, apps will install to the external SD, but will not survive reboot (keep them on the internal SD)
welcome to XDA,
happy flashing
-Cyril
harmonica.ss said:
Hi ,
This is new my first post.
I have samsung SGH-i777 initiallly when i bought it has 4.3& it has 16GB card. cyanogenmod10.2 with rooted. but it always restarted because of OOM.
so i installed kitkat 4.4 omnirom and few day it was working good,no problem arise. after week it doesn't show external storage it only show internal storage of 2GB. so again flashed ROM this time with 4.1 & it shows 16GB memory then i could use those space. but problem is if i go to CWM revcovery(i tried latest or old versions) take backup or installing zip got error like this "sdcard can't mount"
kindly help me out of this issue.
Thx
Click to expand...
Click to collapse

Sdcar can't mount
cyril279 said:
Switching to a different kernel/recovery affects whether the card can be mounted? This sounds like the CWM recovery that you chose doesn't support the filesystem of the Sd Card.
What file system is the SD card using?
For greatest compatibility, I suggest formatting the external Sd Card to Fat32.
If you're going to stay on 4.4, AND if you plan on playing music from the sdcard, I suggest formatting it to exfat (successful workaround for a KK bug).
^^beware, the stock recovery and firmware will NOT be able to read any exfat formatted partition
^^once formatted to ExFat, apps will install to the external SD, but will not survive reboot (keep them on the internal SD)
welcome to XDA,
happy flashing
-Cyril
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
This is my sdcard partition
/dev/block/vold/259:3 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0

The total size of the internal storage of the i777 is 15.8 GB, and it is partitioned as shown in the table below.
From: Settings > Storage, you should see reports for:
- "INTERNAL STORAGE" ~2GB
- "INTERNAL STORAGE" ~11.5GB
- IF you have an SD Card installed, you should see a third report named "SD CARD"
(Using the partition table as reference)
The first "internal storage" is partition #10, or /dev/block/mmcblk0p10
The second "internal storage" is partition #11, or /dev/block/mmcblk0p11
The SD Card is not captured in the partition table below, but if installed, would be found at /dev/block/mmcblk1 or /dev/block/mmcblk1p1
I'm not sure how to interpret your partition report, because it appears that it is reporting the statistics of the internal memory module, and NOT of a particular partition, which is more valuable to us.
-What do you see in Settings > Storage?
Stock I777 Partition Table:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
harmonica.ss said:
Hi,
Thanks for your reply.
This is my sdcard partition
/dev/block/vold/259:3 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
Click to expand...
Click to collapse

Hi,
This is my partitions of my phone,
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async
_commit,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_c
ommit,data=ordered 0 0
/dev/block/mmcblk0p12 /preload ext4 ro,nosuid,nodev,noatime,barrier=1,data=order
ed 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,
journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:3 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
When i see in storage,it shows like
Total space -> 1.97 GB
USB Storage --> 11.36GB

@cyril279 you should make reference thread on this subject. I'm going to have to bookmark this in case i need it later. Damn....

So CM 10.2 crashed a lot; Omni drops emmc (embedded multimedia card) after one week; 4.1 works fine until you change CWM recovery, and your partition report seems to be spitting back that your internal storage partition (emmc) is formatted as vfat.
It is entirely possible that your partition-reporter is calling a FAT32 partition VFAT, at which point there's nothing wrong with the partition format, and I have no idea what your i777 is going through. Based on the information provided, It sounds to me as though your internal Sd Card partition is formatted to something that is causing issues running the firmwares and kernels that you have chosen,
If the partition format is indeed the issue, then the solution is to backup the contents of emmc, format mmcblck0p11 to FAT32, and try your favorite firmware/kernel again.
I suggest that you verify the file system of the internal sdcard, using a different means than you have been.
The difference in FAT and FAT32 is well documented, but I am unclear on the importance of the differences in between VFAT and FAT32. A quick google session has lead me to understand that they are NOT the same, but quite a few threads in various forums seem to refer to them interchangeably.
Maybe I'm completely on the wrong path here, I welcome any input.
harmonica.ss said:
[...]when i bought it has 4.3& it has 16GB card. cyanogenmod10.2 with rooted. but it always restarted because of OOM.
so i installed kitkat 4.4 omnirom and few day it was working good,no problem arise. after week it doesn't show external storage it only show internal storage of 2GB. so again flashed ROM this time with 4.1 & it shows 16GB memory then i could use those space. but problem is if i go to CWM revcovery(i tried latest or old versions) take backup or installing zip got error like this "sdcard can't mount"[...]
Click to expand...
Click to collapse

cyril279 said:
Maybe I'm completely on the wrong path here, I welcome any input.
Click to expand...
Click to collapse
No, you're on your OWN path. That was great, razen's right: you should consider creating a reference guide and we could get it stickied. As new users come in (which amazes me, due to the age of our device), it would be a wonderful asset to have a reference written by someone who understands this.
Great post!

SteveMurphy said:
No, you're on your OWN path.
Click to expand...
Click to collapse
...That's the part that concerns me, I'm not totally convinced that this issue should have lead me in this direction, but the only time I've ever had an issue with firmware recognizing the SD Card was when I started playing around with formatting partitions, so it seemed reasonable. Looking back, the original post points several directions all at once, and without a more systematic approach (like installing the firmware clean, then installing one app at a time, NOT from TiBu backup) we won't know what the real issue(s) is/are/were.
That was great, razen's right: you should consider creating a reference guide and we could get it stickied. As new users come in (which amazes me, due to the age of our device), it would be a wonderful asset to have a reference written by someone who understands this.
Click to expand...
Click to collapse
These handsets are old, but when my wife and I finally decided that we wanted smart-phones, the i777 met the criteria of inexpensive, well-rated, dual-core, and well-supported, Android devices. Regarding a reference post, I managed to cobble-together a rough understanding from guides for other devices, but my understanding on the partition madness still isn't the strongest. Either way, I certainly don't mind compiling what I've found into something concise and specific to the i777.

harmonica.ss, are you still there? don't give up on me just yet.
I did finally get a chance to check the "mount" stats of my wife's i777, which also reports the user-storage partition as vfat. Her i777 has spent significant time on SHostock3, cm 10.1.3, & Omni 4.4; all without internal storage issues.
harmonica.ss said:
[...]so again flashed ROM this time with 4.1 & it shows 16GB memory then i could use those space. but problem is if i go to CWM revcovery(i tried latest or old versions) take backup or installing zip got error like this "sdcard can't mount"[...]
Click to expand...
Click to collapse
What kernel, and what firmware are you using? <-- this should have been my first question.
from my wife's i777:
Code:
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #

cyril279 said:
harmonica.ss, are you still there? don't give up on me just yet.
I did finally get a chance to check the "mount" stats of my wife's i777, which also reports the user-storage partition as vfat. Her i777 has spent significant time on SHostock3, cm 10.1.3, & Omni 4.4; all without internal storage issues.
What kernel, and what firmware are you using? <-- this should have been my first question.
from my wife's i777:
Code:
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
Click to expand...
Click to collapse
How do I partition the sd card? I kind of got myself into a rut and then after the fact finding out that I needed to partition the sd card. Maybe you can help? I can send you a message of what I did. It's kind of a long message.

ms.journie said:
[ ... ] I can send you a message of what I did. It's kind of a long message.
Click to expand...
Click to collapse
So what happened?

cyril279 said:
So what happened?
Click to expand...
Click to collapse
Sorry had left. I'll try to send you the message either tonight or tomorrow.

cyril279 said:
So what happened?
Click to expand...
Click to collapse
This is the forum that I had followed. http://forum.xda-developers.com/gal...ta-storage-t2839161/post54633983#post54633983
1. Went into download mode using usb jig
2. Odin on PC. I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5 in "PDA SLOT" flashed
3. Phone boots up went through all set up.
4. Enabled USB debugging, checked allow install on unknown resources.
5. Installed "framaroot v.1.4.1 Root - Installed Odin Mobile – Reboot - flashed (zImage) jeboo_kernel_i777_v2-3a through Mobile Odin.
6. Boot into download mode.
8. Odin on PC - i777_4GB data - 45mb preload - 1GB system_pit in "PIT SLOT". I did not uncheck the reboot. Phone rebooted.
9. When it powered on, I would see the AT&T and then it would blink in and out and then it looked like it was shut off but it wasn’t.
I am able to go into download and recovery mode.
When I go into the recovery mode this is what it says. I have attached the picture.
In that forum step 10 says if internal cannot format then ......... Well I'm unable to mount storage or I just don't know how to.
Well after all of that the other day I thought I well maybe I can just flash back to stock tried that didn't work.
After 12 hours of trying to research I finally gave in to ask.
Are you able to help?

OMG!! The excitement is for real! I flashed back to SGH-I777_UCLE5 and now the phone actually boots up!! Thank you for your help!

@cyril279
So I'm trying to partition my I777 for more storage. I've been trying to follow this post - http://forum.xda-developers.com/gal...ta-storage-t2839161/post54633983#post54633983 .
I'm having a bit of issues with Post #10. 10. If internal cannot format or gives error, connect phone to pc and mount storage, you can then format as fat32 from windows or whatever operating system you are using (recommended system). When done, unmount and try step above again just to be certain.
I connect my phone to PC and I'm unsure how to mount the storage and format to fat32. I click onto the Samsung phone, then it shows the external sd card and the phone. I have right clicked on the phone and scrolled to format but it doesn't specifically state it formats to fat 32.
Can you try to help me again?

ms.journie said:
@cyril279
So I'm trying to partition my I777 for more storage. I've been trying to follow this post - http://forum.xda-developers.com/gal...ta-storage-t2839161/post54633983#post54633983 .
I'm having a bit of issues with Post #10. 10. If internal cannot format or gives error, connect phone to pc and mount storage, you can then format as fat32 from windows or whatever operating system you are using (recommended system). When done, unmount and try step above again just to be certain.
I connect my phone to PC and I'm unsure how to mount the storage and format to fat32. I click onto the Samsung phone, then it shows the external sd card and the phone. I have right clicked on the phone and scrolled to format but it doesn't specifically state it formats to fat 32.
Can you try to help me again?
Click to expand...
Click to collapse
Oh my, what a journey you've had in the last few days, I'm glad to hear that you got the initial problem sorted.
It has been some time since I messed with formatting the internal storage partition, so I would have to re-familiarize myself with the process before issuing further advice, and I don't have as much time as I once did (I have two young children now) but I will look into it. My responses will not likely be swift.
Have you read over the partition/formatting guide?
-Cyril

Any Success in Internal SD Partition?
ms.journie said:
OMG!! The excitement is for real! I flashed back to SGH-I777_UCLE5 and now the phone actually boots up!! Thank you for your help!
Click to expand...
Click to collapse
Does the phone internal storage partition remain the same or has been successfully partitioned as per the guide?

Related

How to natively boot Android OS with root

I have managed to natively boot Urokdroid's OS in my Archos-70 device. This means that I don't need to go to the boot loader menu and select Developer to boot into my SD card which contains my Android OS. Upon power-up or reboot without pressing the volume -, I can have rooted Android OS.
First and foremost I'd like to give credits to where credits are due. I'd like to thank $aur0n for his excellent work on allowing us to boot our Archos device to external SD card. This has paved the way for many enhancements that we have now, and soon to come. I'd also like to give thanks to apr24991 for discovering a way to always boot in Developer mode. This has given me a chance to tweak my OS and allow Urokdroid's kernel to boot natively. And for all those generous people here who have willingly share their knowledge in this forum, I appreciate all your work. Now it's time for me to share what I've learned.
I'm no expert of Linux or Android. This was just based on my experience and there may be better ways to do this. Having said that, I just want to lay out some precautions.
Be prepare to lose data. So as preparation, please back-up your data.
Don't blame me if you brick your device. I would say that instructions here are easy enough for those knowledgeable in linux. However there may be few cases that you don't get the expected results. In any case, you can still restore your original Android OS by going to recovery menu and applying the stock 2.0.71 firmware from Archos.
This works on my A70, and I cannot guarantee that it will also work on A101 and other Gen8 devices. I'm suspecting it will.
After applying this successfully, you will lose the capability to dual boot. Meaning you will only be able to boot in SDE mode with rooted Android. Again you can still restore the stock firmware in the recovery menu.
Pre-requisites
Please download the SDE firmware from here. You can also download the stock 2.0.71 firmware in case you want to recover your original OS.
You should have already installed Urokdroid's kernel & this is properly working on your Archos device. In other words, you are already running Android on external SD card. $aur0n has setup a comprehensive guide here. The guide here is based on 0.3 version of Urokdroid's kernel.
Steps
Warning. On this step, you will lose all data in your device but excluding contents of external SD card. Please backup important data before continuing. Apply SDE into your Archos following phase 1 of apr24991's post here. This method will actually erase your stock Android firmware and only the SDE (AngStrom) will be present. So whenever you power on or reboot,
it will always boot AngStrom.
Now the trick now is to modify the kernel & initramfs of SDE so it will boot into external SD which contains your Android OS.
Insert your external SD card into your device.
Go to recovery menu. Press volume - while powering on.
Chose Developer Menu from the Recovery Menu.
Select flash kernel & initramfs.
Attach the device to your PC via USB. Your device will now appear as mass storage device in your PC. Copy 0.3 zImage from Urokdroid's, and the modified initramfs.cpio.gz, attached in this post (Extact it from the zip file first). This is the same initramfs.cpio.gz as Urokdroid's except I've modified /init to disable the checking of squasfs file in mmcblk0p2.
Safely unmount your device from your PC. Afterwards, select ok in your device. This would apply the copied zImage and initramfs.cpio.gz. And then it will prompt you that it will boot the device. Press power
button to reboot.
If everything is ok, you will now always be booted into Urokdroid's Android OS, rooted, and able to do other things. If you wish to restore stock firmware from Archos, just go to recovery menu and apply the firmware version you want. You may follow phase 2 of apr24991's post
here and just use your desired firmware version (2.0.54 or 2.0.71).
So far my setup is stable.
Optional: If you look at /data.old (mmcblk0p4), there is no longer data there. You have additional 300MB of partition where you can setup swap space.
Why?
You can remove the Android (Original Archos Android - not the SD-One!) in the Developer Menu in the Recovery - so no need to flash a special modified initramfs?!
Or am I missing something?
As I've mentioned, I'm no expert on Linux or Android. I've just laid out what I did. I did a lot of trial and error. If I did not flash a modified initramfs it will always boot AngStrom. What I want is to always boot on rooted Android in SD. The only thing I modified from Uruk's initramfs is to bypass the checking of squash file in /dev/mmcblk0p1. Since we reformat the device, the squash file in /dev/mmcblk0p1 has been erased. The only way to bring it back is either copy from backup or reapply the stock firmware.
I have also managed to boot a rooted Android using the built-in mmcblk0p2, mmcblk0p4 block devices. When I got to AngStrom, I just copied a backup of squash file to mmcblk0p2, and backup of data to mmcblk0p4, and then flash the kernel & initramfs from this thread. My only problem here is I'm limited to 300MB for apps.
There may be more efficient ways to do this, and if you have suggestions that will achieve the same results I'll be happy to include them in this guide.
I think I did it in a different order but it still worked.
1- SDE
2- New kernel
3- Remove "Andriod" from recovery
I liked this way since I knew the new kernel booted before I erased Archos's.
xnatex21 said:
I think I did it in a different order but it still worked.
1- SDE
2- New kernel
3- Remove "Andriod" from recovery
I liked this way since I knew the new kernel booted before I erased Archos's.
Click to expand...
Click to collapse
That works for sure and is the simplest way I know of.
A possible dangerous, scary way?
Thinking out loud here... but
the archos/sde bootloader is mounted by Uruk in /mnt/rawfs (currently the permissions seem to prevent write access)
rawfs contains, among other things, a file called 'custom' (which is a copy of the zImage and initramfs.cpio.gz flashed under developer edition menu and packaged together) and 'avboot', which looks to be the archos kernel/loader.
Does anyone else think it might be possible to rename custom->avboot and avboot->custom to swap both the behavior of the bootmenu and default boot around? Rooted android booting by default, stock android boots when developer edition is selected?
Ok so is there a way now that we can move the sdcard android files over to the system as a re-write-able system?
sent from epic 4g
There isn't enough space where the stock android is atm (mmcblk0)
I have put Uruk onto the internal storage (mmcblk1) because my sdcard is slow and rubbish.
so how big is the file? cant we just edited and delete some junk apps to make it enough?
I think it's possible to use mmcblk0p4 as storage for root fs. It has 300MB of space. The other partitions are too small. I'm not sure if it's possible to consolidate mmblk0 to 1 partition, but i've managed to convert mmcblk0p4 to ext4.
Update:
I consolidated mmcblk0p2, mmcblk0p3 and mmcblk0p4 into 1 ext4 partition. It's about 450MB. I put the rootfs here and use 2GB of internal storage as /data partition.
Code:
# mount
mount
rootfs on / type rootfs (rw)
/dev/mmcblk0p2 on / type ext4 (rw,noatime,barrier=1,nodelalloc,data=ordered)
/dev/mmcblk1p2 on /data type ext4 (rw,noatime,barrier=1,nodelalloc,data=ordered)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw,devuid=1000,busuid=1000,listuid=1000)
debugfs on /sys/kernel/debug type debugfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
/dev/block/vold/179:9 on /mnt/storage type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fma
sk=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015
,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,utf8,errors=remount-ro)
tmpfs on /mnt/storage/.android_secure type tmpfs (ro,size=0k,mode=000)
/dev/block/mmcblk2p1 on /mnt/storage/sdcard type vfat (rw,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask
=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,utf8,errors=remount-ro)
fusesmb on /mnt/storage/network/smb type fuse (rw,nosuid,nodev,user_id=0,group_id=0,allow_other,max_read=32768)
djmount on /mnt/storage/network/upnp type fuse (ro,nosuid,nodev,user_id=0,group_id=0,allow_other)
# df -h
df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 448M 313M 112M 74% /
/dev/mmcblk0p2 448M 313M 112M 74% /
/dev/mmcblk1p2 2.0G 268M 1.6G 15% /data
tmpfs 120M 12K 120M 1% /dev
tmpfs 120M 0 120M 0% /mnt/asec
/dev/block/mmcblk0p1 32M 13M 20M 40% /mnt/rawfs
tmpfs 120M 4.0K 120M 1% /dev/shm
/dev/block/vold/179:9
4.6G 464M 4.1G 11% /mnt/storage
/dev/block/vold/179:9
4.6G 464M 4.1G 11% /mnt/secure/asec
/dev/block/mmcblk2p1 1.4G 4.0K 1.4G 1% /mnt/storage/sdcard
fusesmb 448M 313M 112M 74% /mnt/storage/network/smb
#
As a newer Archos buyer, I'm very happy about this info. I'd like to get some additional info tho. Firstly, you consolidated mmcblk0p2, mmcblk0p3, and mmcblk0p4 into a 400MB part for the rootfs. Were you unable to consolidate mmcblk0p1 in as well?
Secondly, you allocated 2GB of internal storage for /data, but what do you use this for? Also, this leaves you about 5GB of internal storage (as the internal storage shows approx. 7GB on my stock 101IT)? And, you're able to utilize your entire SD for storage data, as opposed to booting and keeping your OS here?
Thirdly, do you think, if necessary this could be rolled back to stock? Would a flash back to the stock ROM package restore the original partition table? The only reason I ask this, is that I've been considering selling this in a short while, when the verdict comes in on which tablets will get Gingerbread updates. Also, the pontential performance gains on a Viewsonic GTablet with it's Tegra2 based chipset intrigue me (I hadn't heard of this device when I chose my 101IT), and with it's horsepower, I think it might be a surer bet for Gingerbread love. But, if I sell it, I'd like to give my buyer an option to recieve a ROM'd/rooted or stock device depending on preference.
Lastly, as if I haven't asked enough already ;-) , could you provide detail on how one could replicate your processes? I imagine you'd start with installing SDE on your storage card to have root access to the mmcblk0 devices and install the new kernel to the consolidated mmcblk0 partition? Are there any other steps that one would need follow?
If you've read this far, thanks much for your patience and assistance!
As a newer Archos buyer, I'm very happy about this info. I'd like to get some additional info tho. Firstly, you consolidated mmcblk0p2, mmcblk0p3, and mmcblk0p4 into a 400MB part for the rootfs. Were you unable to consolidate mmcblk0p1 in as well?
Click to expand...
Click to collapse
I didn't try to include mmcblk0p1 since the boot process is still accessing this partition. One access i've seen is the flash image at boot up is taken from this partition. There may be more. So to be safe, i've excluded this partition.
Secondly, you allocated 2GB of internal storage for /data, but what do you use this for? Also, this leaves you about 5GB of internal storage (as the internal storage shows approx. 7GB on my stock 101IT)? And, you're able to utilize your entire SD for storage data, as opposed to booting and keeping your OS here?
Click to expand...
Click to collapse
/data is used to be mounted to mmcblk0p4 which has about 300MB of space. I've transferred this to internal storage with 2GB, which allows me for more apps to be installed. In the internal storage, I've allocated 4.5GB as vfat (/sdcard), 2GB as ext4 (/data), and 500MB as swap.
Thirdly, do you think, if necessary this could be rolled back to stock?
Click to expand...
Click to collapse
You can always go to recovery menu, and reformat the device. This will repartition the internal storage, and install a stock firmware. This, however, will erase all your data in the internal storage.
Lastly, as if I haven't asked enough already ;-) , could you provide detail on how one could replicate your processes?
Click to expand...
Click to collapse
I'll back trace my steps later, and post them here.
Here are the steps I did to use mmcblk0p1 as rootfs and a partition in mmcblk1 (internal storage).
I assume you are already on Urukdroid's kernel running on external SD.
Partitioning Internal Storage
1) I first partitioned the internal storage. To partition without destroying existing data, I used GParted from Ubuntu desktop. Connect Archos to PC running Ubuntu via USB. Mount the USB Mass Storage. A70S will appear as one of drive in Ubuntu.
2) Open GParted and select the device for the Archos internal storage. You will see 1 fat32 partition labeled A70S. Unmount the partition. Upon unmounting, you will be able to resize the partition. In my case, I put 2500 free space after the partition.
3) After resizing, I have 2500MB free space. I created 2 primary unformatted partitions, 2GB (/data), and the last one 500 (swap). After this, apply the changes in GParted.
4) Afterwards, from linux command line I formatted the 2 partitions using the following command:
Code:
mkfs.ext4 -O ^huge_file -L data /dev/sdb2
mkswap /dev/sdb3
5) Unmount USB from Archos.
Partitioning System Storage
6) Use adb shell. Unmount /dev/block/mmcblk0p4, /dev/block/mmcblk0p3, /dev/block/mmcblk0p2, /dev/block/mmcblk0p1. Using fdisk, delete partitions 2, 3, 4 from /dev/block/mmcblk0, then create 1 partition utilizing the rest of the disk space. This will give you about 450MB, that you can use as root.
7) format the partition.
Code:
mkfs.ext4 -O ^huge_file -L root /dev/block/mmcblk0p2
Copying files to the created partition
8) I mount /dev/block/mmcblk0p2 to /tmp/root, /dev/block/mmcblk1p2 to /tmp/data
Code:
mkdir /tmp/root
mkdir /tmp/data
mount -t ext4 /dev/block/mmcblk0p2
mount -t ext4 /dev/block/mmcblk1p2
8) I grabbed Urukdroid's 0.4 rootfs.tgz, and extract them mmcblk0p2.
Code:
cd /tmp/root
tar zxvf /sdcard/rootfs.tgz
9) Since 0.4 already contains Gapps, I've uninstalled Gapps first on my archos.
10) I copied the data files
Code:
cp -a /data/* /tmp/data/.
11) I modified /tmp/root/init.rc and comment out mounting /mnt/system, /cache & /data. I've attached my modified init.rc.
12) Unmount /tmp/data, and /tmp/root.
Apply kernerl & modified initramfs
13) I then rebooted to recovery, on Developer Edition Menu, flash new kernel & initramfs. Use zImage, and modified initramfs.cpio.gz which I have attached here. The modification I did in initramfs is use mmcblk0p2 as root and mmcblk1p2 as data, and if it finds /dev/mmcblk1p3 (assuming mkswap has already been applied) use it as swap.
Hope this helps.
Will this work on the 101 too?
Sent from my A101IT using Tapatalk
hexto said:
Will this work on the 101 too?
Click to expand...
Click to collapse
Also curious about this
Thanks for your walkthrough! I greatly appreciate it. I'm testing this on my 101IT now. However, I seem to be boot-looping (Archos Entertainment your way screen flashes on, off, and on repeatedly). However, for the first boot of the Urukdroid kernel, it took a significant amount of time as well. I'm going to give it a few, and if there's no change, I'll retry. I may have made a mistake someplace causing this issue, so I'll see what I can dig up.
nmyron said:
Thanks for your walkthrough! I greatly appreciate it. I'm testing this on my 101IT now. However, I seem to be boot-looping (Archos Entertainment your way screen flashes on, off, and on repeatedly). However, for the first boot of the Urukdroid kernel, it took a significant amount of time as well. I'm going to give it a few, and if there's no change, I'll retry. I may have made a mistake someplace causing this issue, so I'll see what I can dig up.
Click to expand...
Click to collapse
Are you following the guide from the 1st post or from the 13th post? What version of Urukdroid kernel are you using?
I was totally incorrect. When I boot with the dev edition option, I'm booting off the two internal partitions. To be honest, when I made that first post, I had been at work all night, then did this, and just didn't think to check "mount" in the terminal to see the result.
However, it's performing somewhat sluggishly. I'm unsure what's going on there. I'm going to look at some things and see what might be going on. But, the tutorial was spot on.
Is there a way to force it to boot Dev Edition (so it boots this OS) automatically upon logon?
Edit: And, I'm running the Urukdroid 0.4.1 currently, I just downloaded the latest before I began this process
On recovery menu, select Developer Edition, then select delete android's kernel. After this you'll always boot in Developer mode.
________________________________
Sent from my GT-I9000 using Tapatalk
... And you would've thought that I'd have noticed that, being all the in/out of that menu I've done in the last two days...
As far as the sluggishness goes, it seems to be mostly directly after boot. After about 2 minutes, it fades, and performance improves drastically. I'm guessing it ties mostly to swappiness, and the system making initial use/caching data.
You have no idea how much of an amazing help this walkthrough has been. Just a little messing around with the file system, and moving things around, and now it's just cooking along, running an internally booted os with root access... Great work here!

[Q] change internal memory and adb logcat

Hi all,
I just replace the internal memory with an 8 GB microSD, then I run the adb logcat and there is a message as follows:
EXT2-fs error (devices loop0): ext2_lookup:
deleted inode referenced: 20679
What does it mean? whether there are errors in the partition?
Hi, after you replaced the internal sdcard... i think you need a "new" Rom... flash... (Factory Reset?)
MfG
UKSheep
UKSheep said:
Hi, after you replaced the internal sdcard... i think you need a "new" Rom... flash... (Factory Reset?)
MfG
UKSheep
Click to expand...
Click to collapse
Yes, I already did flashing a new rom. But that doesnt fix it
hm, sorry...
i know no solution.
There is a thread over at MoDaCo that tells you how to do it. You will need to keep the partition sizes the same and use a modified boot.img file in order for your streak to recognise the bigger card.
I'm also pretty sure that there is the modified boot.img files for all versions of the streak roms on that thread for you to download.
I've often thought about doing it, but I'm not brave enough yet
I am intersted in this too but still no clarity, for me at least. Glad you are braver than some of us.
There is also a thread
http://android.modaco.com/content/d...6477/lcd-replacement-and-internal-sd-upgrade/
Keep us informed and I, for one, will follow. 32Gb Class 10 cards are no longer outrageous prices and that capacity will make the exercise worthwhile for me.
According to the other thread you can go to at least 4gig without any special files.
Btw, previously I have made 3 partitions for the internal memory card as follows:
-- Partition 1: 2GiB ext2
-- Partition 2: 1GiB ext3 (named cache)
-- Partition 3: 5 GiB ext4 (named Data)
Is there an error in setting up partition?
I use steve streak droid 1.7. And the system read 6,12GB for internal memory
Please help
Hello, the partitions you are showing seem to be ok...
what was the use for you to swap the internal sd ? speed, more space for apps ?
How did you manage to obtain those partitions ? did you followed the howto from modaco's forum ?
Could you provide me the output of a mount command ?
to finish, did you change the original boot.img to a modified one, provided in the same forum ?
I'm willing to help you, but you need to provide me those informations !
Good luck,
Boujou bien,
K.
kwenteen said:
Hello, the partitions you are showing seem to be ok...
what was the use for you to swap the internal sd ? speed, more space for apps ?
How did you manage to obtain those partitions ? did you followed the howto from modaco's forum ?
Could you provide me the output of a mount command ?
to finish, did you change the original boot.img to a modified one, provided in the same forum ?
I'm willing to help you, but you need to provide me those informations !
Good luck,
Boujou bien,
K.
Click to expand...
Click to collapse
Hi, my priority is the speed in running application. To obtain those partition i use gparted live via usb. honestly I didn't follow the howto from modaco forum and I didn't change the original boot.img.
What should I do now? Thanks for your support.
here is the output of mount command:
export PATH=/data/local/bin:$PATH
sh-4.1$ export PATH=/data/local/bin:$PATH
sh-4.1$ root
sh: root: command not found
sh-4.1$ su
sh-4.1# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 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
/dev/block/mtdblock6 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock7 /firstboot yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/innersd0p5 /cache ext3 rw,noatime,nodiratime,errors=continue,commit=99999,data=writeback 0 0
/dev/block/innersd0p6 /data ext3 rw,noatime,nodiratime,errors=continue, commit=99999,data=writeback 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/loop0 /mnt/asec/extdata ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0
/dev/block/vold/179:17 /mnt/sdcard 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 0 0
/dev/block/vold/179:17 /mnt/secure/asec 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 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.ArtInGames.AirAttackHDLite-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.agilesoftresource-2 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed, utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.rovio.angrybirdsrio-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.rovio.angrybirds-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
sh-4.1#
up up please help
/dev/block/innersd0p5 /cache ext3 rw,noatime,nodiratime,errors=continue,commit=99999 ,data=writeback 0 0
/dev/block/innersd0p6 /data ext3 rw,noatime,nodiratime,errors=continue, commit=99999,data=writeback 0 0
/dev/loop0 /mnt/asec/extdata ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0
apparently, your /data and /cache partitions seem to be found by your device, and well mounted... which is quite weird, because you didn't changed your boot.img.
I'm wondering if you're not using a mod made to speed up the rom, by using your external sd to be used for data ? That could be related to the loop line in your mount command, that may be related to the error you see in logcat...
what are the symptoms on your phone, besides the message ? can you install apps ?
I would advise you to try a modded boot.img, you will find the file for your streakdroid version on the modaco link that someone posted earlier... it won't delete your files, and should help ! use fastboot to flash it !
I think it should solve your problem !
good luck,
Boujou bien,
K.
kwenteen said:
I'm wondering if you're not using a mod made to speed up the rom, by using your external sd to be used for data ? That could be related to the loop line in your mount command, that may be related to the error you see in logcat...
what are the symptoms on your phone, besides the message ? can you install apps ?
I would advise you to try a modded boot.img, you will find the file for your streakdroid version on the modaco link that someone posted earlier... it won't delete your files, and should help ! use fastboot to flash it !
I think it should solve your problem !
good luck,
Boujou bien,
K.
Click to expand...
Click to collapse
so the setting is still using the external card for data? how do I move it to an internal card which is certainly faster (class 10 vs class 2)?
Apart from these error messages, no problems when using the handset. I also can install the application.
I've tried boot.img and it seems an error message is gone. I'm still wondered the use of data in the internal card, please guide.
Up ul about internal sd
normally by flashing the new boot.img, you should have a "normal" setup, meaning without the loop device...
just run once more the mount command, and see if you still have this loop mounted !
And if yes, I suggest you to flash a fresh rom, that doesn t have this option, like the streakdroid 190, and be sure to replace in the update.zip file the original boot.img with the alternate one available on modaco...
And beware of the option you select with this install, some of them are incompatible with the innersd mod !
good luck !
K.

Increase SYSTEM PARTITION on GT-I9100

Hi guys !
The system partition on SGS2 is 512MB and i would like to increase it to 1GB aka 1024MB.
Is there any way to do that without destroying all the partitions on the device ?
brucewein said:
Hi guys !
The system partition on SGS2 is 512MB and i would like to increase it to 1GB aka 1024MB.
Is there any way to do that without destroying all the partitions on the device ?
Click to expand...
Click to collapse
what? by default out of 16gb it has 2 be 2gb internal storage and rest is internal sdcard, is ur phone really GTi9100
the SYSTEM partition is 512MB not 2GB
Same problem here, but I want to increase my app-storage (from 2GB to 4GB). After a while of googling I could not found any way to manage these partitions seperately.
BUT: There are PIT-files, which are used to set the values of the system-partition. There are 3 different PIT-files, one for 512 MB system-storage, one for 513 MB and one for 803 MB. I think, that's the only way... But at first, you have to found them via Google
Unless you really do your homework and know what you're doing, I would strongly advise NOT using Odin to re-partition with PIT etc.
High success rate of many screwing up and hard bricking.
Just warning........
Sent from my GT-P6810 using XDA Premium HD app
Earlier this week I thought of a good way to do this, safely using LVM and the spare partition. I messaged gokhanmoral and he liked the idea and said he would look into it this weekend. So hopefully it should be possible soon.
Merging the /preload and/system partition is a good idea to get a full 1gb system partition. Though there is no need of more than 512 mb in s2 as of now it would be handy when jelly bean gets released.
# tapatalked from my core i3 pc #
bala_gamer said:
Merging the /preload and/system partition is a good idea to get a full 1gb system partition. Though there is no need of more than 512 mb in s2 as of now it would be handy when jelly bean gets released.
# tapatalked from my core i3 pc #
Click to expand...
Click to collapse
I dunno how hard it is to merge those 2, but a good dev will have an idea on this
# tapatalked from my core i3 pc #
i recently talked back with gokhanmoral
and made some experiements with vlm
so far what i could get is:
- merging /preload with /cache ---> phone boots fine without any issue
- merging /preload with /data ---> phone boots fine without any issue
- create /system as lv without merging any other disk ---> phone does not boot
- create /system as lv whith merge of /preload ---> phone does not boot
when using a LV as /system the phone simply does not boot while it works fine when using /data or /cache as a LV
what i have expierienced is that when using a LVM LV as /system the phone
goes into black screen but after a bit (~1min) the adb shell becomes avaible
so i had a look into the shell
what i got is:
/system is mounted as the LV, i can see/list all files on it so i guess its mounted right
also seems that all other related services are up and running just the graphical side of the phone does not work
i have no idea what makes this happen ...
probably some software is trying to interact with the system partition during bout up using the /dev/mmc... device which is replaced with the lvm device
well ...
i made some real succes this night i got the lvm thing setup right and booted up AOKP on a 1GB /system lvm partition
the problem was/is simple as it is
samsung stock based roms do not support LVM i think there are some libs or some kind of this missing
Code:
/lvmpool/system
~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 416.1M 32.0K 416.1M 0% /dev
tmpfs 416.1M 0 416.1M 0% /mnt/asec
tmpfs 416.1M 0 416.1M 0% /mnt/obb
/res/dev/system 1000.0M 279.1M 720.9M 28% /system
tmpfs 416.1M 4.0K 416.1M 0% /system/lib/modules
/res/dev/cache 98.4M 4.1M 94.4M 4% /cache
/res/dev/data 2.0G 236.9M 1.7G 12% /data
/dev/block/mmcblk0p1 19.7M 8.2M 11.5M 42% /efs
tmpfs 416.1M 0 416.1M 0% /mnt/ntfs
/dev/block/vold/179:24
7.5G 697.7M 6.8G 9% /mnt/sdcard
/dev/block/vold/179:24
7.5G 697.7M 6.8G 9% /mnt/secure/asec
/dev/block/vold/259:3
11.5G 5.1G 6.4G 44% /mnt/emmc
Code:
~ # mount
mount
/res/dev/system on /system type ext4 (ro,noatime,barrier=1,data=ordered)
Code:
~ # ls -la /res/dev/system
ls -la /res/dev/system
lrwxrwxrwx 1 root root 19 Jun 1 07:10 /res/dev/system -> /dev
/lvmpool/system
~ #
Incrase /data
Hello, nice work. I woner of you.
But I have Idea. How can I increase /data partition. I want to give 500 MB from /sdcard.
How can I do?
Tahnks
gyurman said:
Hello, nice work. I woner of you.
But I have Idea. How can I increase /data partition. I want to give 500 MB from /sdcard.
How can I do?
Tahnks
Click to expand...
Click to collapse
that works excactly the same way as it is working for system if u need help to set that up contact me ...
Sent from my GT-I9100 using xda app-developers app
i just checked with LINK2SD that i have only 4-5% free on /SYSTEM
and 67% free on /mnt/sdcard
so this is it?
how to force apk's to install to /mnt/sdcard instead to /system?
kmetek said:
i just checked with LINK2SD that i have only 4-5% free on /SYSTEM
and 67% free on /mnt/sdcard
so this is it?
how to force apk's to install to /mnt/sdcard instead to /system?
Click to expand...
Click to collapse
you could simply add another 500mb to /system so you can simply install apps to system as u did before ...
may i will write a small Tutorial how to increase a specific partition etc when back home from work
Sent from my GT-I9100 using xda app-developers app
Tallustus said:
you could simply add another 500mb to /system so you can simply install apps to system as u did before ...
may i will write a small Tutorial how to increase a specific partition etc when back home from work
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
I'd be interested in that tutorial to increase my data partition... thanks.
b631nz said:
I'd be interested in that tutorial to increase my data partition... thanks.
Click to expand...
Click to collapse
will see if i get some time to
write that tut today
Sent from my GT-I9100 using xda premium
Tallustus said:
will see if i get some time to
write that tut today
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I would really apreciate it too:]
Any news on the tutorial?
SaschaHa said:
Same problem here, but I want to increase my app-storage (from 2GB to 4GB). After a while of googling I could not found any way to manage these partitions seperately.
Click to expand...
Click to collapse
have you solved the problem already?
I would also like to do so

ext4 SD mount data not persistent across reboot

Hi,
Got this Desire Bravo with low internal memory so thought I should mount the app and data dirs to a ext4 partition on my SD card instead so I can install a lot of apps.
Followed this howto:
newton dot cx/~peter/2012/12/how-to-increase-app-space-with-a-partitioned-sd-card-on-an-htc-nexus-one-running-android-2-3-6-on-linux/
I found that my ext4 partition is mounted at boot time.
mount command gives the below:
/dev/block/mmcblk0p2 /mnt/sd-ext ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
I can copy the data to the ext4 partition without any problem using "cp -rlp /data/app /mnt/sd-ext/data" and "cp -rlp /data/data /mnt/sd-ext/data" .
I can see the data when doing a "ls /mnt/sd-ext/" - looks ok.
But after reboot the data is just gone - just dont get it. Grateful for any help for troubleshooting this.
Running ROM CM10.1_VJ_4.2.2_V6.3_May24 .
Thanks...
EDIT: installed S2E app (Simple2Ext) instead, which didnt work well, so tried Mount2SD instead and appears to be working OK.

[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.

Categories

Resources