Hard Bricked Galaxy S3 SPH-L710 - Sprint Samsung Galaxy S III

I've read a number of forum posts about how to unbrick a hardbricked galaxy S3 and followed them all and even tried countless times the same method as is suggested, yet I can't get my phone to boot at all. Anyone out there have any advice? I rooted my phone just fine and then flashed Android_Revolution_HD-SGS3_53.0.zip onto it through clockwork mod. Everything appeared to be installing fine and when it came time to reboot, clockwork mod notified me that something appeared wrong in my boot file and I may lose root priveledges. It then asked if I wanted clockwork mod to fix it and I unfortunately said yes. The screen immediately went pitch black and nothing I have tried gets it to show any signs of life.
I have a 64 GB micro SD that I've used with the command
Code:
sudo dd if=Desktop/debrick_sph_l710.img of=/dev/mmcblk0
I then check it with
Code:
sudo fdisk -l /dev/mmcblk0
and get
Code:
GPT PMBR size mismatch (30777343 != 122241023) will be corrected by w(rite).
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
Disk /dev/mmcblk0: 58.3 GiB, 62587404288 bytes, 122241024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Device Start End Sectors Size Type
/dev/mmcblk0p1 8192 131071 122880 60M Microsoft basic data
/dev/mmcblk0p2 131072 131327 256 128K unknown
/dev/mmcblk0p3 131328 131839 512 256K unknown
/dev/mmcblk0p4 131840 132863 1024 512K unknown
/dev/mmcblk0p5 132864 136959 4096 2M unknown
/dev/mmcblk0p6 136960 137983 1024 512K unknown
/dev/mmcblk0p7 137984 158463 20480 10M unknown
/dev/mmcblk0p8 158464 159487 1024 512K unknown
/dev/mmcblk0p9 159488 160511 1024 512K unknown
/dev/mmcblk0p10 160512 180991 20480 10M Linux filesystem
/dev/mmcblk0p11 180992 208895 27904 13.6M Linux filesystem
/dev/mmcblk0p12 208896 215039 6144 3M unknown
/dev/mmcblk0p13 215040 221183 6144 3M unknown
/dev/mmcblk0p14 221184 3293183 3072000 1.5G Linux filesystem
/dev/mmcblk0p15 3293184 28958719 25665536 12.2G Linux filesystem
/dev/mmcblk0p16 28958720 28975103 16384 8M Linux filesystem
/dev/mmcblk0p17 28975104 30695423 1720320 840M Linux filesystem
/dev/mmcblk0p18 30695424 30715903 20480 10M unknown
/dev/mmcblk0p19 30715904 30736383 20480 10M unknown
/dev/mmcblk0p20 30736384 30748671 12288 6M Linux filesystem
/dev/mmcblk0p21 30748672 30754815 6144 3M unknown
/dev/mmcblk0p22 30754816 30754831 16 8K unknown
/dev/mmcblk0p23 30754832 30765071 10240 5M Linux filesystem
The phone acts no differently with the flashed sd card than it does without it. Is the only way to fix it with a JTAG?

U need 16gb sd card, debrick image for your phone. Then you can boot into download mode and flash in odin! Get a high quality 16gb card

hilla_killa said:
U need 16gb sd card, debrick image for your phone. Then you can boot into download mode and flash in odin! Get a high quality 16gb card
Click to expand...
Click to collapse
I'm using a 32 GB SanDisk micro sd, could it just be that all the debrick images I've used are just the wrong ones?

Its possible but i think if your phone is 16gb than you need 16gb sd

Related

[Q] SD Card write speed dropped!

Well, I got a new Class 10 SD card, Transcend, from an online shop.
First few days it gave me great speeds. ~15mbps. Now, I'm getting not more than 4mbps!
I guess this happened mostly after using Data2SD or Partitioning the SD card
Anyone has any clue?
Hi,
I'd suggest formatting your memory card, then re-partitioning/re-doing whatever you've done to it.
Sent from my very dumb HTC Wildfire S (Stock Euro 2.3.5)
Did that a couple of times already
Well then I really don't know, sorry ...
Sent from my very dumb HTC Wildfire S (Marvel - Stock Euro 2.3.5)
Try using an SD Card reader and check its speed on your PC so that you know whether it's the card or the phone.
Then try a fresh ROM without Data2SD and check the speed.
Do each of the tests more than once cause sometimes there can be anomalies.
Same problem here
Bout a Samsung class 10 ,16gb sdhc and transfered some files to test the speed on my computer
I got 21mb write and 24mb read speed just as it said on the box
made partitions with Minitool to creat ext4 at a 32 cluster size
next thing you know even in windows my speed went down to 1mb/ and 2mb/sec
Anyone know whats going on here ?
Partition Alignment
SharpKami said:
Bout a Samsung class 10 ,16gb sdhc and transfered some files to test the speed on my computer
I got 21mb write and 24mb read speed just as it said on the box
made partitions with Minitool to creat ext4 at a 32 cluster size
next thing you know even in windows my speed went down to 1mb/ and 2mb/sec
Anyone know whats going on here ?
Click to expand...
Click to collapse
There are several factors that could play into it here.
How are you accessing the microSDHC? USB cable to phone / plugged with card reader?
Can you test with a more reliable tool, like CrystalDiskMark?
Windows may be buffering the transfer and giving wrong numbers.
It could be that Minitool did not align the partition(s) properly, as it would have done for built-in SSDs.
Did you shrink the (first) FAT32 partition and create the ext4 at 'the end' of the available space?
On my WFS + SanDisk 16GB, Class 10, I created the partitions with CWM, and DATA2SD (Data2sdV2withA2sdremover_by_jikantaru) had to recreate the ext3 partition, because it was improperly aligned. This is from the data2whateverlog.txt:
Code:
=============================
Fri Nov 2 10:44:17 PDT 2012
=============================
+++ Your Partition(s) are NOT aligned and data2whatever modified them:
----------------------------------------------------------------------
+++ Your SD-Ext Partition started at sector: 29617188
=> your SD-ext partition was NOT 1024k aligned
and it should start at following sector: 29618176
+++ Your Swap Partition started at sector: 30617188
=> your Swap partition was NOT 1024k aligned
and it should start at following sector: 30617600
+++ OLD Partition table of your SD-Card:
----------------------------------------
__________________________fdisk_Partition_table_____________________________
Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 29617187 14808593+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 29617188 30617187 500000 83 Linux
/dev/block/mmcblk0p3 30617188 31116287 249550 82 Linux swap
____________________________________________________________________________
+++ The Partitiontable has been modified
----------------------------------------
__________________________fdisk_Partition_table_____________________________
Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 29617187 14808593+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 29618176 30617599 499712 83 Linux
/dev/block/mmcblk0p3 30617600 31116287 249344 83 Linux
____________________________________________________________________________
+++ The SD-ext partition got formated with EXT3 afterwards:
-----------------------------------------------------------
_________________________mke2fs+tune2fs_output______________________________
Filesystem label=userdata
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
124928 inodes, 499712 blocks
0 blocks (0%) reserved for the super user
First data block=1
Maximum filesystem blocks=524288
61 block groups
8192 blocks per group, 8192 fragments per group
2048 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
tune2fs 1.41.6 (30-May-2009)
Creating journal inode: done
This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.6 (30-May-2009)
Filesystem volume name: userdata
Last mounted on: <not available>
Filesystem UUID: 5e4066d3-bb6c-4ef9-8081-03c03cecfce7
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal dir_index filetype sparse_super
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 124928
Block count: 499712
Reserved block count: 0
Free blocks: 475708
Free inodes: 124917
First block: 1
Block size: 1024
Fragment size: 1024
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2048
Inode blocks per group: 256
Filesystem created: Fri Nov 2 17:44:20 2012
Last mount time: n/a
Last write time: Fri Nov 2 17:44:44 2012
Mount count: 0
Maximum mount count: 31
Last checked: Fri Nov 2 17:44:20 2012
Check interval: 15552000 (6 months)
Next check after: Wed May 1 17:44:20 2013
Reserved blocks uid: 0 (user unknown)
Reserved blocks gid: 0 (group unknown)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: 611421e5-1bfd-44b8-95d8-8af4c40c053b
Journal backup: inode blocks
____________________________________________________________________________
+++ Filesystem check found no errors - no log attached
-------------------------------------------------------
I checked the speed with RoboCopy over USB to the WFS, it was about 4MB/s.
CrystalDiskMark reports 4.5MB/s write speed over the same connection (with 5 runs of 100MB data).
Try using SD-Booster app
You're right litemaster ! my windows was showing the wrong figures while transferring files .
i tried the sd tester and booster ,speed results weren't all that bad , 10mb read /10mb write.
and in windows it shows 2mb but file transfers at a much higher rate some times 30mb/sec.
Appreciate your your help buddy and Eduardo
P.S... By the way , given the results , this samsung class 10 isnn't that bad. Bought it for £12.00 from amazon.

[Info] List of Samsung Galaxy Nexus GT-I9250 devices and partitions

List of devices by name:
Code:
su
ls -l/dev/block/platform/omap/omap_hsmmc.0/by-name/
lrwxrwxrwx root root 2012-07-01 01:03 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-07-01 01:03 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-07-01 01:03 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-07-01 01:03 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-07-01 01:03 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-07-01 01:03 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-07-01 01:03 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-07-01 01:03 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-07-01 01:03 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-07-01 01:03 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-07-01 01:03 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-07-01 01:03 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-07-01 01:03 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
Code:
su
find /dev/block/platform/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_gnex_partitions.txt
Code:
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot0: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot0 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot1: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0boot1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p13: 0 MB, 65536 bytes
4 heads, 16 sectors/track, 2 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p12: 14.5 GB, 14539537408 bytes
4 heads, 16 sectors/track, 443711 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p11: 452 MB, 452984832 bytes
4 heads, 16 sectors/track, 13824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p10: 685 MB, 685768704 bytes
4 heads, 16 sectors/track, 20928 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p9: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p8: 12 MB, 12517376 bytes
4 heads, 16 sectors/track, 382 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p7: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p6: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p5: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p3: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p2: 3 MB, 3670016 bytes
4 heads, 16 sectors/track, 112 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p1: 0 MB, 131072 bytes
4 heads, 16 sectors/track, 4 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0p1 doesn't contain a valid partition table
Disk /dev/block/platform/omap/omap_hsmmc.0/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/omap/omap_hsmmc.0/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Mounted filesystems:
Code:
su
df
Code:
Filesystem Size Used Free Blksize
/dev 347M 32K 347M 4096
/mnt/asec 347M 0K 347M 4096
/mnt/obb 347M 0K 347M 4096
/system 643M 347M 295M 4096
/factory 19M 8M 11M 4096
/cache 425M 7M 418M 4096
/data 13G 773M 12G 4096
/storage/sdcard0 13G 773M 12G 4096
Temporary fstab:
Code:
su
mount
Code:
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/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
ytwytw said:
Hi
Here is my copy of Partition Table
It's Samsung Galaxy Nexus (GSM) and its Bootloader PRIMEKL01
Code:
(parted) print
print
print
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 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB cache
12 1218MB 15.8GB 14.5GB userdata
hope to be useful to whoever stuck
cheers
Click to expand...
Click to collapse
Links:
How to install Jelly Bean 4.1 on Galaxy Nexus GSM edition
[GUIDE] Making Dump Files Out of Android Device Partitions
I run df on my Nexus and see in the last line:
/mnt/asec/com.meteonova.markersoft-1 13M 11M 1M 4096
What's this?
Is it possible to repartition my nexus ?
Sent from my Galaxy Nexus using xda premium
siealex said:
I run df on my Nexus and see in the last line:
/mnt/asec/com.meteonova.markersoft-1 13M 11M 1M 4096
What's this?
Click to expand...
Click to collapse
/mnt/asec/ is used when an application uses encryption
http://www.androidpolice.com/2012/0...n-the-play-store-google-disables-drm-for-now/
http://nelenkov.blogspot.com/2012/07/using-app-encryption-in-jelly-bean.html
seriousia said:
Is it possible to repartition my nexus ?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Probably, you'll have to generate a valid pit file.
Hi! Sorry for this very noob question but I just want to ask how did you do this? I really really wanted to know what my device's memory block/partition is because I wanted to recover some files.. I have a sony xperia J phone with me btw.. Thanks!
shael1992 said:
Hi! Sorry for this very noob question but I just want to ask how did you do this? I really really wanted to know what my device's memory block/partition is because I wanted to recover some files.. I have a sony xperia J phone with me btw.. Thanks!
Click to expand...
Click to collapse
There's no exact procedure. The best way is to check under /dev/block of there is any block device listed. You can use adb shell to list all mount points and see if something coherent comes out.
scandiun said:
There's no exact procedure. The best way is to check under /dev/block of there is any block device listed. You can use adb shell to list all mount points and see if something coherent comes out.
Click to expand...
Click to collapse
I'm sorry again for this second noob question but how do you check "under /dev/block".. or "adb shell" Is it by using the command prompt or cygwin terminal? really confused with all these stuffs. sorry :/ just new to this.
shael1992 said:
I'm sorry again for this second noob question but how do you check "under /dev/block".. or "adb shell" Is it by using the command prompt or cygwin terminal? really confused with all these stuffs. sorry :/ just new to this.
Click to expand...
Click to collapse
You need to have adb installed on the computer and then enable USB debugging on the phone, and connect it via USB to the computer. That's basic stuff you should learn first.
The other are basic unix commands.
scandiun said:
You need to have adb installed on the computer and then enable USB debugging on the phone, and connect it via USB to the computer. That's basic stuff you should learn first.
The other are basic unix commands.
Click to expand...
Click to collapse
Yes. I already have adb installed on my pc and I already enabled USB debugging.. what's next?
shael1992 said:
Yes. I already have adb installed on my pc and I already enabled USB debugging.. what's next?
Click to expand...
Click to collapse
Run adb shell from Windows Command Prompt and then you have some examples on the first post.
scandiun said:
Run adb shell from Windows Command Prompt and then you have some examples on the first post.
Click to expand...
Click to collapse
Thank you so much for your help. I now get it. This happened when I tried to do the first code you posted on the first post:
shael1992 said:
Thank you so much for your help. I now get it. This happened when I tried to do the first code you posted on the first post:
Click to expand...
Click to collapse
There is an space after the l. Try this other command:
Code:
ls -lR /dev
scandiun said:
There is an space after the l. Try this other command:
Code:
ls -lR /dev
Click to expand...
Click to collapse
Hi! Just wanna say thanks a lot for answering all my questions, you really helped me and I got the whole thing running and successfully retrieved some files, which is my purpose in going all these hassle. :good:
pictures partition?
Hi!
This guide really helped my to identify some partitions, but some questions came to my mind. I hope you can help me.
Do you have any idea where are the photos saved by default in the Galaxy S3 (i9300)?
I'm trying to recover my girlfriend's photos that I accidentally deleted
Thanks a lot!:victory:
supermaton said:
Hi!
This guide really helped my to identify some partitions, but some questions came to my mind. I hope you can help me.
Do you have any idea where are the photos saved by default in the Galaxy S3 (i9300)?
I'm trying to recover my girlfriend's photos that I accidentally deleted
Thanks a lot!:victory:
Click to expand...
Click to collapse
They are in data partition, where the sdcard is.
scandiun said:
They are in data partition, where the sdcard is.
Click to expand...
Click to collapse
Thanks a lot.
So I mount the partition and I'm able to see a lot of files but none of them are photos taken with the camera.
As soon as I noticed that the photos were gone I rooted the phone, installed CM10.1, then installed CM9, then I started to pull out the partitions,I know this may affect the data and some photos may not be recovered, but I was hoping to recover at least some of them.
--My mmcblkop12 partition (userdata) is about 11.5gb, is it possible that I did something wrong when pulling the .raw of the partition file out of the phone?
Should I pull out the raw file again from the phone?
Should I try another recovery software?
Thanks in advance
supermaton said:
Thanks a lot.
So I mount the partition and I'm able to see a lot of files but none of them are photos taken with the camera.
As soon as I noticed that the photos were gone I rooted the phone, installed CM10.1, then installed CM9, then I started to pull out the partitions,I know this may affect the data and some photos may not be recovered, but I was hoping to recover at least some of them.
--My mmcblkop12 partition (userdata) is about 11.5gb, is it possible that I did something wrong when pulling the .raw of the partition file out of the phone?
Should I pull out the raw file again from the phone?
Should I try another recovery software?
Thanks in advance
Click to expand...
Click to collapse
On Nexus devices the internal sdcard is just a folder inside userdata, so if you formatted userdata is probably that they got affected.
Try here
http://forum.xda-developers.com/showthread.php?t=1994705
scandiun said:
On Nexus devices the internal sdcard is just a folder inside userdata, so if you formatted userdata is probably that they got affected.
Try here
http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
Yep, that's the guide I'm following, the problem is that I can't find a single photo taken with the camera .. just old images of apps installed or cache files
scandiun said:
List of devices by name:
Code:
su
ls -l/dev/block/platform/omap/omap_hsmmc.0/by-name/
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
Code:
su
find /dev/block/platform/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_gnex_partitions.txt
Click to expand...
Click to collapse
Hi,
I tried this command but get an error. "Permission denied"
I have SU & busybox installed. Running PSX custom rom.
How can I fix it.

SD Card Is Damaged error, but card is OK

Does anyone know what Android is doing to check the external SD card before producing the error that the SD card is damaged? I get that error after every reboot the card card is then fully functional (camera can write to it, file browsers can access it). I have reformatted the card in the phone and in Windows 7. Here is the output from fsck from a linux box:
[email protected]:/media$ sudo fsck -v /dev/sdb1
fsck from util-linux 2.19.1
dosfsck 3.0.9 (31 Jan 2010)
dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "MSDOS5.0"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
32768 bytes per cluster
596 reserved sectors
First FAT starts at byte 305152 (sector 596)
2 FATs, 32 bit entries
1944576 bytes per FAT (= 3798 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4194304 (sector 8192)
486032 data clusters (15926296576 bytes)
63 sectors/track, 255 heads
2048 hidden sectors
31114240 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/sdb1: 1 files, 2/486032 clusters
Time to reflash the ROM maybe? (Diet ICS) I'd just like to know what command is being run to trigger the error. It is a 16GB card formated as fat32
ok, while I was spinning my wheels someone else had posted in the Diet ICS thread that this is apparently a known issue with the toggles being used.
I had to make sure my card was formatted to FAT32 for it to recognize my card. try that.
MentalDragon said:
I had to make sure my card was formatted to FAT32 for it to recognize my card. try that.
Click to expand...
Click to collapse
In this case it was specific to the ROM and reflashing the theme fixed it. While I was trying to figure out what was going on and ended up posting this question, someone else was already posting the fix.

Read-only file system on microSD

Hi everybody..
I have a strange and boring issue with my micro SD card that I use with my smartphone.. Today, while I was reading a PDF book the phone freezes it self: the only solution was to reboot it!
But.. WOW; 'till that moment the phone doesn't recognize my micro-SD any more!! It doesn't give warnings or messages.. nothing.. the only problem is that my SD card is inserted but the phone won't read it..
I mount the micro sd into my Slackware laptop and it still have partitions but they are all read-only! Every thing I try to do (copy files, move, delete etc) fails with a read-only warning!
So I try to format all from the scratch.. but it is not possible!! It doesn't let me format my SD for the same reason: read-only file system!!
WOW!! It's absurd!!
What can I do? is there a solution for that?
I tried to use fsck, badblocks, mkfs but nothing helped!
fdisk -l output
Code:
Disk /dev/sdb: 15.9 GB, 15918432256 bytes
255 heads, 63 sectors/track, 1935 cylinders, total 31090688 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00031a4f
Device Boot Start End Blocks Id System
/dev/sdb1 1 29027343 14513671+ c W95 FAT32 (LBA)
/dev/sdb2 29027344 31027343 1000000 83 Linux
/dev/sdb3 31027344 31090687 31672 82 Linux swap
I have a FAT partition for data, a ext2 one used with Link2sd and a swap one.
This is the result I got when trying to format the second partition..
Code:
# mkfs.ext2 /dev/sdb2
mke2fs 1.41.14 (22-Dec-2010)
/dev/sdb2: Read-only file system while setting up superblock
The same to me. Wish a help!! Thanks

Internal Storage 0mb after changing partition tables and converting

So i followed this post exactly http://forum.xda-developers.com/showpost.php?p=64862885&postcount=2 and now my internal storage is at 0mb i cannot put the rom into it via my windows pc or transfer with adb
I currently just have access to recovery
xboxhaxorz said:
So i followed this post exactly http://forum.xda-developers.com/showpost.php?p=64862885&postcount=2 and now my internal storage is at 0mb i cannot put the rom into it via my windows pc or transfer with adb
I currently just have access to recovery
Click to expand...
Click to collapse
Transfer the ROM to /tmp/ in recovery and flash it. I think You are using old recovery hence size is not shown properly. If issue still exists, post Your partition table output here.
i was able to do that, however in the rom i get an encryption error and it wont let me get past that, TWRP is now at version 3 but the internal storage now called sdcard in twrp is still a 0mb
this is the info
C:\adb>adb shell
~ # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 954240 29161464 83 Linux
~ #
for now i just flashed a stock rom via flashtool, installed the latest twrp and internal storage is 26410mb should that be the right size at default
xboxhaxorz said:
i was able to do that, however in the rom i get an encryption error and it wont let me get past that, TWRP is now at version 3 but the internal storage now called sdcard in twrp is still a 0mb
~ #
Click to expand...
Click to collapse
What error do You get exactly when You say encryption error? And where do You get this error, in TWRP or after booting up? If You are using correct TWRP, then You shouldn't get these errors such as sdcard being 0mb. Because the TWRP automatically maps to new storage.
xboxhaxorz said:
for now i just flashed a stock rom via flashtool, installed the latest twrp and internal storage is 26410mb should that be the right size at default
Click to expand...
Click to collapse
26410 MB = 25.79 GB, so it is the default size.
So i flashed a stock rom to restore everything, put the latest twrp on the phone, and then followed this guide to format
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
Converted to new partition structure and flashed rom now all is working well
Thanks

Categories

Resources