Develop Bugs

[Q] Backup/Restore partitions using dd command under ClockWorkMod?

Hello,
Is is possible to use dd command available under busybox when in recovery mode
to backup partitions?
Examples:
Backup data partition:
dd if=/dev/block/mmcblk0p26 of=/sdcard/data.img
Restore data partition:
dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
If yes, then what the needed mount commands to make the above work.
The reason is that I have a problem with nandroid restore:
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
Note: similar command apparently works for flashing recovery
image (which is partition /dev/block/mmcblk0p21).

Without appropriate answer, I have to try for myself, and finally get the answer to my own question.
The answer is YES, dd command could be used to backup/restore the entire system (so can replace
nandroid part of ClockWorkMod).
You need to know the mapping of the partitions for the Desire HD:
Code:
/dev/block/mmcblk0p21 recovery
/dev/block/mmcblk0p22 boot
/dev/block/mmcblk0p25 system
/dev/block/mmcblk0p26 data
/dev/block/mmcblk0p27 cache
The partitions backupped will result in same size each time, with same backup/restore time
since it is a "raw" backup (bit-to-bit copy, or sector-by-sector copy in hard disk terminology).
I use the .dsk for file extension to avoid confusion with .img extension used by CWM (since they
are not the same format, and cannot be used in fastboot command for example).
Backup sample log:
Code:
ls -l /sdcard/MyBackups/recovery/recovery*.dsk
-rwxrwxrwx 1 root root 8909824 Jun 16 10:17 /sdcard/MyBackups/recovery/recovery_3.0.2.8.dsk
2011-06-17-02:26:24 Backup boot...
512+0 records in
512+0 records out
4194304 bytes (4.0MB) copied, 0.208129 seconds, 19.2MB/s
-rwxrwxrwx 1 root root 4194304 Jun 17 02:26 /sdcard/MyBackups/LeeDroid_Froyo/boot.dsk
2011-06-17-02:26:24 Backup system...
71423+1 records in
71423+1 records out
585104896 bytes (558.0MB) copied, 188.697998 seconds, 3.0MB/s
-rwxrwxrwx 1 root root 585104896 Jun 17 02:29 /sdcard/MyBackups/LeeDroid_Froyo/system.dsk
2011-06-17-02:29:33 Backup data...
150399+1 records in
150399+1 records out
1232076288 bytes (1.1GB) copied, 370.469513 seconds, 3.2MB/s
-rwxrwxrwx 1 root root 1232076288 Jun 17 02:35 /sdcard/MyBackups/LeeDroid_Froyo/data.dsk
2011-06-17-02:35:43 Backup cache...
38399+1 records in
38399+1 records out
314572288 bytes (300.0MB) copied, 97.289337 seconds, 3.1MB/s
-rwxrwxrwx 1 root root 314572288 Jun 17 02:37 /sdcard/MyBackups/LeeDroid_Froyo/cache.dsk
2011-06-17-02:37:21 Done.
Restore sample code:
Code:
ls -l /sdcard/MyBackups/recovery/recovery*.dsk
-rwxrwxrwx 1 root root 8909824 Jun 16 10:17 /sdcard/MyBackups/recovery/recovery_3.0.2.8.dsk
2011-06-17-15:28:33 Restore boot...
-rwxrwxrwx 1 root root 4194304 Jun 17 14:58 /sdcard/MyBackups/LeeDroid_Froyo/boot.dsk
512+0 records in
512+0 records out
4194304 bytes (4.0MB) copied, 1.006897 seconds, 4.0MB/s
2011-06-17-15:28:34 Restore system...
-rwxrwxrwx 1 root root 585104896 Jun 17 15:02 /sdcard/MyBackups/LeeDroid_Froyo/system.dsk
71423+1 records in
71423+1 records out
585104896 bytes (558.0MB) copied, 405.526398 seconds, 1.4MB/s
2011-06-17-15:35:20 Restore data...
-rwxrwxrwx 1 root root 1232076288 Jun 17 15:08 /sdcard/MyBackups/LeeDroid_Froyo/data.dsk
150399+1 records in
150399+1 records out
1232076288 bytes (1.1GB) copied, 434.877655 seconds, 2.7MB/s
2011-06-17-15:42:34 Restore cache...
-rwxrwxrwx 1 root root 314572288 Jun 17 15:09 /sdcard/MyBackups/LeeDroid_Froyo/cache.dsk
38399+1 records in
38399+1 records out
314568704 bytes (300.0MB) copied, 49.197021 seconds, 6.1MB/s
2011-06-17-15:43:24 Done.
Now with "dd" backup, I can now have the liberty to try other ROMs without my dreaded problem with CWM .
Edit: let have a dream. How about using dd binary like nandroid currently invoked by CWM from it's menu?
CWM currently for backup or restore invoke the standalone nandroid binary with appropriate parameters, then it captures
(pipes) the output of e.g. tar utility to extract (restore) or compress (backup) the .img file.
With dd it would be simple to add to CWM menu to provide invocation of dd for a backup/restore using partition imaging method.
By doing this, no more need to plug an USB cable and use adb command.
Edit: Finally there is a simpler solution. Create an installation ZIP script (like the one used to flash ROM). Then in updater_script invoke a command (shell script, extension.sh) with the run_program(). You can provide parameters to this. You can have a zip to backup, a zip to restore etc...

Good idea. I've tried this on my U8510 (Android 2.3.3) but it doesn't work. This is my partition layout:
cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 00500000 00020000 "recovery"
mtd2: 00140000 00020000 "misc"
mtd3: 00060000 00020000 "splash"
mtd4: 0ba00000 00020000 "system"
mtd5: 03f00000 00020000 "cache"
mtd6: 0a0a0000 00020000 "userdata"
mtd7: 01400000 00020000 "userdata2"
mtd8: 01400000 00020000 "cust"
Click to expand...
Click to collapse
And this is "ls -l /dev/block":
brw------- 1 root root 7, 0 Oct 12 21:54 loop0
brw------- 1 root root 7, 1 Oct 12 21:54 loop1
brw------- 1 root root 7, 2 Oct 12 21:54 loop2
brw------- 1 root root 7, 3 Oct 12 21:54 loop3
brw------- 1 root root 7, 4 Oct 12 21:54 loop4
brw------- 1 root root 7, 5 Oct 12 21:54 loop5
brw------- 1 root root 7, 6 Oct 12 21:54 loop6
brw------- 1 root root 7, 7 Oct 12 21:54 loop7
brw------- 1 root root 179, 0 Oct 12 21:54 mmcblk0
brw------- 1 root root 179, 1 Oct 12 21:54 mmcblk0p1
brw------- 1 root root 31, 0 Oct 12 21:54 mtdblock0
brw------- 1 root root 31, 1 Oct 12 21:54 mtdblock1
brw------- 1 root root 31, 2 Oct 12 21:54 mtdblock2
brw------- 1 root root 31, 3 Oct 12 21:54 mtdblock3
brw------- 1 root root 31, 4 Oct 12 21:54 mtdblock4
brw------- 1 root root 31, 5 Oct 12 21:54 mtdblock5
brw------- 1 root root 31, 6 Oct 12 21:54 mtdblock6
brw------- 1 root root 31, 7 Oct 12 21:54 mtdblock7
brw------- 1 root root 31, 8 Oct 12 21:54 mtdblock8
drwxr-xr-x 3 root root 60 Oct 12 21:54 platform
brw------- 1 root root 1, 0 Oct 12 21:54 ram0
brw------- 1 root root 1, 1 Oct 12 21:54 ram1
brw------- 1 root root 1, 2 Oct 12 21:54 ram2
brw------- 1 root root 1, 3 Oct 12 21:54 ram3
brw------- 1 root root 1, 4 Oct 12 21:54 ram4
brw------- 1 root root 1, 5 Oct 12 21:54 ram5
brw------- 1 root root 1, 6 Oct 12 21:54 ram6
brw------- 1 root root 1, 7 Oct 12 21:54 ram7
Click to expand...
Click to collapse
'mmcblk0' is the sdcard.
When i enter 'dd if=/dev/block/mtdblock0 of=/sdcard/mtdblock0-boot.img' i get:
dd: /dev/block/mtdblock0: I/O error
Click to expand...
Click to collapse
CWM Recovery Backup gives me this files. I'm not sure if this are all files so i want to dump partitions manually.
.android_secure.img
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
Click to expand...
Click to collapse
Why is it not working?
Edit: When i enter 'dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img' dd does work but it copies the sdcard to itself.
Why are the other "blocks" not working and how can i get the working ones like your 'mmcblk0p21'?
Edit2: Got it. For the U8510 its 'dd if=/dev/mtd/mtd0 of=/sdcard/mtd0-boot.img bs=4096'.

busybox dd
dnlilas said:
Hello,
Is dd if=/dev/block/mmcblk0p26 of=/sdcard/data.imgis possible to use dd command available under busybox when in recovery mode
to backup partitions?
Examples:
Backup data partition:
dd if=/dev/block/mmcblk0p26 of=/sdcard/data.img
Restore data partition:
dd if=/sdcard/data.img of=/dev/block/mmcblk0p26
If yes, then what the needed mount commands to make the above work.
The reason is that I have a problem with nandroid restore:
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
Note: similar command apparently works for flashing recovery
image (which is partition /dev/block/mmcblk0p21).
Click to expand...
Click to collapse
Hi, I'm interested in using dd command to do a full backup but I don't know how to do.
Where I have to write the command "dd if=/dev/block/mmcblk0 of=/sdcard/data.img"?
In busybox?
Thanks in advance!

Hello,
You need to connect the phone to your PC with USB cable then reboot the phone in recovery. In your PC, start the adb.exe command, you should get a command prompt with root right (# instead of $). Then you can use commands in this prompt.

busybox dd without a pc
dnlilas said:
Hello,
You need to connect the phone to your PC with USB cable then reboot the phone in recovery. In your PC, start the adb.exe command, you should get a command prompt with root right (# instead of $). Then you can use commands in this prompt.
Click to expand...
Click to collapse
Thanks but I've read (http://forum.xda-developers.com/showthread.php?t=1124939) that is possible to use the command "dd" within the smartphone obtaining a full backup in the sdcard.
I've to use a terminal emulator in android, after installing busybox, to launch the command "dd if=/dev/block/mmcblk0 of=/sdcard/data.img"?
Thanks in advance!

OK, so you will need a rooted phone, then in terminal emulator, change to root with su command to get the root # prompt.
But the difference is that you may take a backup of a live (running) system : this may work (as some live online nandroid backup), but of course the safest/surest is to take a backup when the system is shutdown, as in recovery.
Also, to restore, of course you are required to use the recovery, you cannot restore from inside Android with dd.

busybox dd from inside Android
dnlilas said:
OK, so you will need a rooted phone, then in terminal emulator, change to root with su command to get the root # prompt.
But the difference is that you may take a backup of a live (running) system : this may work (as some live online nandroid backup), but of course the safest/surest is to take a backup when the system is shutdown, as in recovery.
Also, to restore, of course you are required to use the recovery, you cannot restore from inside Android with dd.
Click to expand...
Click to collapse
Thanks very much, now I've understand! :victory:
This guide (http://forum.xda-developers.com/showthread.php?t=1818321) says how to do a full backup via pc with the command dd but I don't understand if the phone is in recovery mode!?
Can you tell me if the guide is ok for you? because it says something different from what you have said in your first replay .

To to backup the phone must be powered-on.
But I would suggest you to use this application that will do all the backup for you from inside your running/live Android :
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup

Great app for full backup
dnlilas said:
To to backup the phone must be powered-on.
But I would suggest you to use this application that will do all the backup for you from inside your running/live Android :
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
Click to expand...
Click to collapse
Thanks, great app for a complete backup of the phone!
Just to learn something new: to do a backup with pc and dd command, the phone must be in recovery mode and then connected to the pc?
It is ok for you the guide that I linked in the previous reply?
You said, in your first replay, to use adb.exe: can you explain the procedure (like a small guide) or link a guide (if you know one web page that speaks about it)?
Thanks again!

From what I know :
adb.exe is part of the Android developer toolkit (ADK) that you can download. In fact for plain user (not Android developer), we only need the following 3 files that are usually available in many tools for customed ROM :
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
You would better download the ADK so you will get the latest version. When you connect the phone either in recovery mode with an USB cable to the PC, the PC has (at least under Win7/Win8) automatically Android adb device driver installed, so it recognizes the phone correctly. By launching adb.exe, you will get to an adb command prompt where you can issue several commands like reboot, restart to recovery, flash the partition etc.... (communication is established between adb.exe in PC and the phone ) You can also issue the su command as far as I remember, then you the the "Linux"-like shell prompt. And dd, ls, du, cat commands of busybox etc... are then all available. You exit the shell by 'exit'.
Searching for adb, fastboot etc.. would help you.
Hope this helps,

i'm confused by the code in this message.
it shows a `ls` command but the output of a `dd` one...

has anybody actually tried to write the live system partition this way? has his phone survived?

Is it correct to flash the data.img(user data image) by fastboot with this command:
fastboot flash userdata data.img
??

gcbxda said:
i'm confused by the code in this message.
it shows a `ls` command but the output of a `dd` one...
Click to expand...
Click to collapse
Agreed. I was looking on a way to restore a complete mmcblk0 raw backup to the device, but the restore sample code given is just the `ls -l` command.

Unable to mount data & cache

Hi all, got my kindle fire brick. I think my partition is messed up. I bought a factory cable which able me to install twrp and i succefully(i guess) flashed energy ICS. But it prompt me "e:unable to mount '/data" e:unable to mount '/cache". I were to boot to normal boot it will just boot endlessly but i still can access to fff and twrp.i did some research on repartitioning for kindle fire but i need some guidance. Help is much appreciated
Sent from my GT-I9100 using xda app-developers app

Usually this is a fairly bad indication but do this go to the mount section in twrp and make sure there are no checks in the boxes of data and system if so uncheck them, I know you said data and cache but this should have a check in the box then try a reboot also were you previously using cwmr? If so you may have been bitten by the bug a very unsightly one that generally means the death of your kindle unless you know how to repartition around a broken emmc. What did you do prior to this that caused this to happen?
Also energy is not the best for good mounting just saying...

I was using fireparted to backup my partition when my pc suddenly shut down. Thats when everything screws up. Also my data and cache are not able to check or uncheck. I hope theres a kind soul to guide me through this process
Sent from my GT-I9100 using xda app-developers app

If you ask me I would say its toast but maybe someone knows a way to restore factory partitions I know many are looking for a solution for thier parts only kindle....

From what I understand...
Code:
fastboot oem format
...will rewrite your partition table to stock. And as long as you haven't messed with the partition sizes, your data will stay intact.
Enter:
Code:
shell cat /proc/partitions
To get a list of your current partitions and sizes to check to see if they even exist to begin with. And if so, it's likely just a case of broken or missing mountpoints.
Now, whether or not "fastboot oem format" will restore broken or missing mountpoints, I couldn't tell you for sure; I've never had to try it. But in your situation, it probably couldn't hurt to try.
You can also recreate mountpoints manually if needed.
[Edit:] It has just been explained to me that "fastboot oem format" won't do anything about mountpoints.

Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?

dean11 said:
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?
Click to expand...
Click to collapse
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.

kinfauns said:
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.
Click to expand...
Click to collapse
OH MY GOOOOD!!!! MY KINDLE IS ALIVE!!!! THANK YOU SO MUCH @kinfauns!

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!

june12 said:
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!
Click to expand...
Click to collapse
I don't know who or what did that to your partition table, but partitions 10-12 are not right. It looks like mke2fs is complaining because your userdata partition is only ~178KB. I'm also a bit concerned that you've extended the media partition as far as you have. You might have some additional problems there.
The easiest way for you to get started on a fix is to get into fastboot mode with FFF and run...
Code:
fastboot oem format
That will bring your partition table back to stock, so you can run those mke2fs commands to remake those filesystems on the two partitions. You'll also have to remake the media partition in parted. You can find some instructions on how to do that here...
http://forum.xda-developers.com/showthread.php?t=1658885

Hey,
My current ROM is fine, but I can't mount data & cache in TWRP.
Nothing happens when I click mount data or mount cache in TWRP 2.6.3.1
I reflashed twrp two times and checked the md5sum.
When I try to backup my rom:
When I try a factory reset:
This is what I tried in fastboot:
Code:
fastboot oem format
...
OKAY [ 0.064s]
finished. total time: 0.065s
fastboot oem idme bootmode 4000
...
OKAY [ 0.081s]
finished. total time: 0.081s
fastboot reboot
rebooting...
finished. total time: -0.000s
adb shell cat /proc/partitions
major minor #blocks name
7 0 8348 loop0
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
179 64 512 mmcblk0boot1
179 32 512 mmcblk0boot0
254 0 8347 dm-0
The parted command isn't working for me.
I have never repartitioned them as far as I know.
Wha't wrong with my partitions?

Any alternative for flashing a recovery?

I'm using the U.S. Glide running dmans cm10.1 with the Aquethys touch CWM recovery and I have messed up my USB Port and cannot transfer any data what so ever. I decided to explore alternatives to update the recovery and I found the flash_image command to be the best option as I was unable generate a cwm flashable zip from the Odin tar file (a bit too complexed for me (I have a windows pc)) and while attempting the command flash_image recovery /sdcard/recovery. Img in the phones terminal (image extracted from the new cwm built from source (great job guys!!!!)) and got a partition error and after more research found this to be a common error with people with phones containing the Emmc layout. But of course no solutions presented themselves without needing a solid USB connection. Any help or troublshooting would be appreciated! Other routes included fastboot interface but I don't think this phone uses it (correct me if I'm wrong )
Sent from my SGH-I927

wat about twrp recovery... u can find it on the goomanager app

You should try the nontouch version of cwmr. I've heard several people running into similar problems as you with the touch version.
Sent form my SGH-i927 running dman's cm10.1

Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium

Cprager said:
Right but how do I flash it without a functional USB Port?
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
Now follow this http://forum.xda-developers.com/showthread.php?t=1630519 . Replce the .img file with the glide verison of recovery.
The above should work for you, though i've not tried it myself.

awesome, I will attempt this today and report back.

Cprager said:
awesome, I will attempt this today and report back.
Click to expand...
Click to collapse
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)

greeneyez15o said:
wat about twrp recovery... u can find it on the goomanager app
Click to expand...
Click to collapse
And what version of twrp did you flash and for what device to work on the glide? Without smashing your partitions..
Sent from my SGH-I927 using xda premium

Cprager said:
adb push recovery.img /data/local/
adb push flash_image /data/local/
(Permission denied, copied files to sdcard and then through phone moved to /data/local)
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
(Operation not permitted, I then decided to run the following commands:
adb shell
su
chmod 777 /data/local/recovery.img
chmod 777 /data/local/flash_image
no errors listed, it seemed to function)
adb shell rm /data/local/rights/mid.txt
(rm failed for /data/local/rights/mid.txt, no such file or directory)
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
(sh: syntax error: 'in' unexpected)
adb reboot
adb shell /data/local/flash_image recovery /data/local/recovery.img
(error scanning partitions: No such file or directory (seems like its failing because it doesn't know where the recovery partition is located maybe a DD command with the correct block containing the recovery partition??)
(I also tried the above in a root adb shell with the same error being encountered)
Click to expand...
Click to collapse
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app

ninthsense said:
Try this :
Adb shell
Su
Change to the directory you have your img file in.
./flash_image recovery filexxxxxxx.img
Sent from my SGH-I927 using xda app-developers app
---------- Post added at 10:09 PM ---------- Previous post was at 09:47 PM ----------
You can also try doing the same from inside a terminal emulator app from within the CM10. Just found out that CM10 comes with flash_image already loaded.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal

Cprager said:
Just attempted the following:
adb shell
su
cd /data/local
./flash_image recovery recovery.img
"error scanning partitions: No such file or directory" I am getting the exact same error through the terminal
Click to expand...
Click to collapse
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.

ninthsense said:
drop the "./" just try "flash_image recovery recovery.img" from the terminal. Remember to be "su" and in the same directory where the recovery.img is.
Click to expand...
Click to collapse
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx

Cprager said:
Ok, I just did the revised commands and got a different error output:
opened terminal:
su
cd /data/local (the directory where flash_image and the recovery.img are located)
flash_image recovery recovery.img
"failed with error: -1"
I believe the Flash_image cannot find the partition housing the current recovery but am unable/don't know how to find the correct partiton
but assuming the correct one is found, do you think the below command would be a viable option?
dd if=/data/local/recovery.img of=/dev/block/mmcblk0xxxxx
Click to expand...
Click to collapse
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img

ninthsense said:
Delete the flash_image you've downloaded and run the command again. The flash_image is inbuilt in CM10, so i guess using that one makes more sense.
Also rename the .img file to recovery .img and place it in the root of your sdcard and issue the following command :
su
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Same error, "failed with error: -1"

ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.

roothorick said:
ninthsense, dd'ing the image as he said should work, something like
dd if=/path/to/cwm/boot.img of=/dev/block/mmcblk0pX
But you'll have to do some digging to figure out what X is. Flash CWM the normal way, then head boot.img and each mmcblk0pX and find the one that's identical.
And DON'T just guess; flashing the wrong partition can brick your phone.
Click to expand...
Click to collapse
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.

ninthsense said:
didn't suggested cause i don't know the values for those xxx myself and don't want him to end up wiping/briking his phone.
Click to expand...
Click to collapse
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
edit** don't know if this helps
cat /proc/partitions
major minor #blocks name
179 0 7552000 mmcblk0
179 1 12288 mmcblk0p1
179 2 614400 mmcblk0p2
179 3 319488 mmcblk0p3
179 4 3932672 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2097152 mmcblk0p6
179 7 16384 mmcblk0p7
259 0 5120 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 512 mmcblk0boot1
179 8 512 mmcblk0boot0
179 24 7786496 mmcblk1
179 25 7785472 mmcblk1p1

Cprager said:
I appreciate the concern gentlemen! i definately WILL NOT execute a command without knowing full well its purpose.
Im a PC guy so this linux command stuff is a bit newer to me, that being said, there must be a way (command) to see the partitions?
**I have currently the touch CWM so if you need me to "then head boot.img and each mmcblk0pX" to find the one thats identical I may be able to do so.
Click to expand...
Click to collapse
Nothing really, besides just ls /dev/block/mmcblk0p*
Phone partitions are quite a bit different from computer partitions -- about half the partitions don't even have filesystems; the entire partition is dedicated to some image that is important to one thing or the other.
I've got a pretty good overview of the CGlide ICS partitions here: http://forum.xda-developers.com/showthread.php?t=2051327

From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state

ninthsense said:
From my touch recovery logs
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
Note : I would advise you to pull out the file system into a .img file and keep the backup before flashing it with recover.img. Jsut in case you need to restore back to the original state
Click to expand...
Click to collapse
YOU GUYS ROCK !!!!!
I understand the procedure for replacing the previous recovery with the new recovery.img through the DD command,
but am unsure how to backup the current one. I will do more research and run my procedure by you guys before attempting anything
**edit**
to backup:
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
to flash new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
there was an attribute listed bs=4096 (maybe bit size??)
please let me know if my commands are correct, and I will give it a go (fingers crossed lol)

[Q] 80G9 image with HDD support

Hi @all,
haven't found any definite answer to this unsing the search function.
Is there any image out there supporting the HDD version of the 80G9 tablet? Except the official image of course.
Installed the lastest 4.4.2 developer image, now I know what the H-Model is (No "H" model support)... otherwise working great so far.
Thanks for your answers!

martinwag said:
Hi @all,
haven't found any definite answer to this unsing the search function.
Is there any image out there supporting the HDD version of the 80G9 tablet? Except the official image of course.
Installed the lastest 4.4.2 developer image, now I know what the H-Model is (No "H" model support)... otherwise working great so far.
Thanks for your answers!
Click to expand...
Click to collapse
It's really confusing...
[URL="http://forum.xda-developers.com/showpost.php?p=50137500&postcount=61" @[email protected][/URL] has reported that it works... I really don't know whats going wrong...
 @[email protected]: Can you give a statement, if the harddisk storage works for you?

Quallenauge said:
It's really confusing...
[URL="http://forum.xda-developers.com/showpost.php?p=50137500&postcount=61" @[email protected][/URL] has reported that it works... I really don't know whats going wrong...
@[email protected]: Can you give a statement, if the harddisk storage works for you?
Click to expand...
Click to collapse
Yes, but I could only install till version 23_01_2014-21_52_56 yet.
And I need to mount it manually e.g. via 'adb shell':
[email protected]:/ # mount /dev/block/platform/omap/usbhs_omap/sdb1 /storage/sdcard1/

[email protected] said:
Yes, but I could only install till version 23_01_2014-21_52_56 yet.
And I need to mount it manually e.g. via 'adb shell':
[email protected]:/ # mount /dev/block/platform/omap/usbhs_omap/sdb1 /storage/sdcard1/
Click to expand...
Click to collapse
Can you please adapt the fstab file "/fstab.archosa101hboard" to this location?
Code:
[STRIKE]/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1/1-1.1:1.0/ auto auto defaults voldmanaged=sdcard1:auto[/STRIKE]
[B]/dev/block/platform/omap/usbhs_omap/sdb1 auto auto defaults voldmanaged=sdcard1:auto[/B]
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0
And see if it helps? (Maybe you can play with the old path definition; does it exist? Maybe this is sufficient:
Code:
/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/
)
Hint: Don't forget to unlock the device in order to modify the system file:
Code:
adb shell mount -o remount,rw /

Actually I am not used to writing in those forum systems, so my original try to answer is now blocked
---------- Post added at 01:10 AM ---------- Previous post was at 12:59 AM ----------
I try without any quotes and just a very short version:
Actually I forgot that I had a mini card reader and sdcard in the 3G USB plugged in, without this card it is in fact sda1
---------- Post added at 01:22 AM ---------- Previous post was at 01:10 AM ----------
... Nevertheless it didn't worked, so I searched and found fstab.archosa101hboard is not really in use and I changed init.archosa101hboard.rc first.
---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------
please try a grep fstab.archosa init* to find that always the sboard fstab files are mounted
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Don't know if this can be useful information for you in init.archosa.*board.rc files, but I found in init.rc this import line via ${ro.hardware}:
import /init.${ro.hardware}.rc
back to the harddisk:
still not knowing why it didn't work I changed fstab.archosa101hboard to double-check my fix above is okay:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0 none swap defaults zramsize=134217728
Okay I got the right file, as after reboot I got it mounted:
[email protected]:/ # df
Filesystem Size Used Free Blksize
...
/storage/sdcard1 231.0G 187.5M 230.9G 4096
...
I do not understand "voldmanaged=sdcard1:auto", so I need to stop here and wait for your further support.
I have already played around a lot also with the information from android source website, which I cannot link here (new user)

[email protected] said:
Actually I am not used to writing in those forum systems, so my original try to answer is now blocked
---------- Post added at 01:10 AM ---------- Previous post was at 12:59 AM ----------
I try without any quotes and just a very short version:
Actually I forgot that I had a mini card reader and sdcard in the 3G USB plugged in, without this card it is in fact sda1
---------- Post added at 01:22 AM ---------- Previous post was at 01:10 AM ----------
... Nevertheless it didn't worked, so I searched and found fstab.archosa101hboard is not really in use and I changed init.archosa101hboard.rc first.
---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------
please try a grep fstab.archosa init* to find that always the sboard fstab files are mounted
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Don't know if this can be useful information for you in init.archosa.*board.rc files, but I found in init.rc this import line via ${ro.hardware}:
import /init.${ro.hardware}.rc
Click to expand...
Click to collapse
Thanks for your report ! The fstab is loaded on specific archos model init file.
Code:
on fs
# mount partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
mount_all /fstab.archosa101hboard
swapon_all /fstab.archosa101hboard
This init file is loaded on top at the init.archos_init.rc file. The ${ro.hardware} reflects the model property. You can verify this with
Code:
adb shell getprop ro.hardware
.
Then the correct fstab should loaded.
please try a grep fstab.archosa init* to find that always the s board fstab files are mounted
Click to expand...
Click to collapse
PS: Which version do you use? I had a fix a few weeks ago (Correct fstab file name for non a80s devices.) which is used in newer releases.
back to the harddisk:
still not knowing why it didn't work I changed fstab.archosa101hboard to double-check my fix above is okay:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0 none swap defaults zramsize=134217728
Okay I got the right file, as after reboot I got it mounted:
[email protected]:/ # df
Filesystem Size Used Free Blksize
...
/storage/sdcard1 231.0G 187.5M 230.9G 4096
...
I do not understand "voldmanaged=sdcard1:auto", so I need to stop here and wait for your further support.
I have already played around a lot also with the information from android source website, which I cannot link here (new user)
Click to expand...
Click to collapse
The output of the df command is ok. Please check if it is possible to use the following:
Code:
/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
. The destination mount point is determined from the vold daemon, which starts the appropriate "sdcard" daemon.

Thank you all for your answers!
Great, the HDD is already avaliable in /dev/block/platform/omap/usbhs_omap/sda1... Why didn't I just do a find * | grep sda ...
I'm at the point where [email protected] is now, only difference is that I'm using the 80h files instead of the 101h ones.
- enable write on /
Code:
busybox mount -o remount,rw /
- edit fstab.archosa80hboard
Code:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto #original
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto #as suggested, doesn't work
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2 #works
- edit init.archosa80hboard.rc
Code:
#mount partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs #as is
mount_all /fstab.archosa80hboard #replace s with h
swapon_all /fstab.archosa80hboard #replace s with h
I'm using Image 12_02_2014-20_55_45.7z, which was current last weekend at least

Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56

[email protected] said:
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
Click to expand...
Click to collapse
That's weird.... I get this behavior in case I'm flash via SDE and when I choose "Flash kernel and initramfs" the USB drive is mounted on my PC.
When I copy the two files to the destination, sometimes I forget to unmount the removable storage drive and choose "continue" (or something like this) on the tablet. Then the incomplete kernel/initramfs files are written to the internal ssd which causes the black screen on start.
Can you please check if this was also the case?

[email protected] said:
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
Click to expand...
Click to collapse
If I don't open a terminal and sudo sync before disconnecting the usb cable it happens most of the time for me.

stevemp said:
If I don't open a terminal and sudo sync before disconnecting the usb cable it happens most of the time for me.
Click to expand...
Click to collapse
Quallenauge said:
That's weird.... I get this behavior in case I'm flash via SDE and when I choose "Flash kernel and initramfs" the USB drive is mounted on my PC.
When I copy the two files to the destination, sometimes I forget to unmount the removable storage drive and choose "continue" (or something like this) on the tablet. Then the incomplete kernel/initramfs files are written to the internal ssd which causes the black screen on start.
Can you please check if this was also the case?
Click to expand...
Click to collapse
Thank you for the suggestions, so I could find out a bit what is actually my problem:
I did in fact not disconnecting the USB cable before rebooting.
This was never a problem for the old versions - may be you could add this to your installation instructions if really necessary:
Quallenauge said:
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Nevertheless the device immediately stops (freeze) also directly when I later plug in the USB cable and further after a short time it shows again a black screen and the green LED. I have also tested to connect an OTG cable adapter and it also directly stops (with and without a mouse). Sometimes after plugging off the cable the device automatically reboots.
I switched the 3g dongle on to test the other USB port with a mouse, but no lights - it doesn't work either.
I have no time for testing now and for the rest of the week, I'll check next week for requested logs or a new version fixing it. :fingers-crossed:
Cheers!

[email protected] said:
Thank you for the suggestions, so I could find out a bit what is actually my problem:
I did in fact not disconnecting the USB cable before rebooting.
This was never a problem for the old versions - may be you could add this to your installation instructions if really necessary:
Click to expand...
Click to collapse
Sorry, I meant something different :angel: You can leave the USB cable plugged into the device. I mean, you have to eject (sign off,...) the drive removable in windows / linux after you finish the file transfer to the device (both when you copy the kernel+initramfs and also when updating the archos.ext4.update file). This way the data is synced on the device (to avoid corrupted data).
[email protected] said:
Nevertheless the device immediately stops (freeze) also directly when I later plug in the USB cable and further after a short time it shows again a black screen and the green LED. I have also tested to connect an OTG cable adapter and it also directly stops (with and without a mouse). Sometimes after plugging off the cable the device automatically reboots.
I switched the 3g dongle on to test the other USB port with a mouse, but no lights - it doesn't work either.
I have no time for testing now and for the rest of the week, I'll check next week for requested logs or a new version fixing it. :fingers-crossed:
Cheers!
Click to expand...
Click to collapse
Does at least the archos screen appear before the screen goes black?

Quallenauge said:
Sorry, I meant something different :angel: You can leave the USB cable plugged into the device. I mean, you have to eject (sign off,...) the drive removable in windows / linux after you finish the file transfer to the device (both when you copy the kernel+initramfs and also when updating the archos.ext4.update file). This way the data is synced on the device (to avoid corrupted data).
Does at least the archos screen appear before the screen goes black?
Click to expand...
Click to collapse
Actually I am using linux and I follow exactly your process with sync and umount ... and I was used to leaving the USB cable plugged into the device, but starting with CM 11.0 from 11_02_2014-23_03_07 the tablet was not booting and the archos screen did not appear any more.
I saw that you classified the kernel "Important: Highly experimental!" and "No "H" model support", so I thought just "bad luck" and went back to the old version. (and I bought a sony xperia tablet s)
stevemp wrote "before disconnecting the usb cable", so I tried also without the cable and it boots. Later I realized that I cannot use the micro USB plug at all, because the tablet directly freeze when I connect anything to it. (No problem with power, as the H model has a separated power plug)
May be I didn't explained it well: It always freeze: either before booting or/and also during booting or/and also after booting in normal operating: just plug it in -> directly freeze.
I have no idea what happens and how it can be analyzed.
This happens not when I run CM 11.0 version from 23_01_2014-21_52_56, so I do not believe in a hardware bug.

[email protected] said:
Actually I am using linux and I follow exactly your process with sync and umount ... and I was used to leaving the USB cable plugged into the device, but starting with CM 11.0 from 11_02_2014-23_03_07 the tablet was not booting and the archos screen did not appear any more.
I saw that you classified the kernel "Important: Highly experimental!" and "No "H" model support", so I thought just "bad luck" and went back to the old version. (and I bought a sony xperia tablet s)
stevemp wrote "before disconnecting the usb cable", so I tried also without the cable and it boots. Later I realized that I cannot use the micro USB plug at all, because the tablet directly freeze when I connect anything to it. (No problem with power, as the H model has a separated power plug)
May be I didn't explained it well: It always freeze: either before booting or/and also during booting or/and also after booting in normal operating: just plug it in -> directly freeze.
I have no idea what happens and how it can be analyzed.
This happens not when I run CM 11.0 version from 23_01_2014-21_52_56, so I do not believe in a hardware bug.
Click to expand...
Click to collapse
Thanks for your explanation! Now it's clear for me, the update process was done correctly.
Sadly, I updated the kernel since the 23_01_2014-21_52_56, so I think this is a kernel bug, which affects the JMicron USB SATA controller :-/
Sadly only a few people has a serial cable connected to their *H devices, so we don't have an easy way to track down this issue.
I see a light chance to get the boot log. I can send you a archive where you can test the kernel from your existing installation.
If you have time for some experiments, let me know.

Quallenauge said:
Thanks for your explanation! Now it's clear for me, the update process was done correctly.
Sadly, I updated the kernel since the 23_01_2014-21_52_56, so I think this is a kernel bug, which affects the JMicron USB SATA controller :-/
Sadly only a few people has a serial cable connected to their *H devices, so we don't have an easy way to track down this issue.
I see a light chance to get the boot log. I can send you a archive where you can test the kernel from your existing installation.
If you have time for some experiments, let me know.
Click to expand...
Click to collapse
Yeah, I can test it, but I think not before Monday next week.

Quallenauge said:
I had a fix a few weeks ago (Correct fstab file name for non a80s devices.) which is used in newer releases.
Click to expand...
Click to collapse
Sorry your fix does not really correct all:
Code:
localhost / # grep fstab.archosa init*
init.archosa101[B]h[/B]board.rc: mount_all /fstab.archosa101[B]s[/B]board
init.archosa101[B]h[/B]board.rc: swapon_all /fstab.archosa101[B]s[/B]board
...
After fixing this I have also tested a bit changing the fstab.archosa101hboard.rc file, as your described, but I couldn't get the hard disk mounted with the voldmanaged=sdcard1:auto setting.
Only this line automatically mount it:
Code:
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
I also wonder about a link (/sys/class/block/sda1) which has no correct target:
Code:
localhost / # find / -name sda1 2>/dev/null
/sys/class/block/sda1
/dev/block/sda1
/dev/block/platform/omap/usbhs_omap/sda1
localhost / # ls -l /sys/class/block/sda1 /dev/block/sda1 /dev/block/platform/omap/usbhs_omap/sda1
lrwxrwxrwx 1 root root 15 Mar 7 00:16 /dev/block/platform/omap/usbhs_omap/sda1 -> /dev/block/sda1
brw------- 1 root root 8, 1 Mar 7 00:16 /dev/block/sda1
lrwxrwxrwx 1 root root 0 Mar 7 00:22 /sys/class/block/sda1 -> ../../devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1/1-1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
/sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1 does not exist, just
/sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1:1.0
Code:
localhost / # ls -l /sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1
drwxr-xr-x 4 root root 0 Mar 7 00:22 1-1:1.0
-rw-r--r-- 1 root root 4096 Mar 7 00:22 authorized
-rw-r--r-- 1 root root 4096 Mar 7 00:22 avoid_reset_quirk
-rw-r--r-- 1 root root 4096 Mar 7 00:22 bConfigurationValue
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceProtocol
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceSubClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bMaxPacketSize0
-r--r--r-- 1 root root 4096 Mar 7 00:22 bMaxPower
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumConfigurations
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumInterfaces
-r--r--r-- 1 root root 4096 Mar 7 00:22 bcdDevice
-r--r--r-- 1 root root 4096 Mar 7 00:22 bmAttributes
-r--r--r-- 1 root root 4096 Mar 7 00:22 busnum
-r--r--r-- 1 root root 4096 Mar 7 00:22 configuration
-r--r--r-- 1 root root 65553 Mar 7 00:22 descriptors
-r--r--r-- 1 root root 4096 Mar 7 00:22 dev
-r--r--r-- 1 root root 4096 Mar 7 00:22 devnum
-r--r--r-- 1 root root 4096 Mar 7 00:22 devpath
lrwxrwxrwx 1 root root 0 Mar 7 00:22 driver -> ../../../../../../../bus/usb/drivers/usb
drwxr-xr-x 3 root root 0 Mar 7 00:22 ep_00
-r--r--r-- 1 root root 4096 Mar 7 00:22 idProduct
-r--r--r-- 1 root root 4096 Mar 7 00:22 idVendor
-r--r--r-- 1 root root 4096 Mar 7 00:22 maxchild
drwxr-xr-x 2 root root 0 Mar 7 00:22 power
-r--r--r-- 1 root root 4096 Mar 7 00:22 quirks
--w------- 1 root root 4096 Mar 7 00:22 remove
-r--r--r-- 1 root root 4096 Mar 7 00:22 speed
lrwxrwxrwx 1 root root 0 Mar 7 00:22 subsystem -> ../../../../../../../bus/usb
-rw-r--r-- 1 root root 4096 Mar 7 00:22 uevent
-r--r--r-- 1 root root 4096 Mar 7 00:22 urbnum
drwxr-xr-x 3 root root 0 Mar 7 00:22 usb_device
-r--r--r-- 1 root root 4096 Mar 7 00:22 version
localhost / # ls -l /sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1:1.0
-r--r--r-- 1 root root 4096 Mar 7 00:22 bAlternateSetting
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceNumber
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceProtocol
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceSubClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumEndpoints
lrwxrwxrwx 1 root root 0 Mar 7 00:22 driver -> ../../../../../../../../bus/usb/drivers/hub
drwxr-xr-x 3 root root 0 Mar 7 00:22 ep_81
-r--r--r-- 1 root root 4096 Mar 7 00:22 modalias
drwxr-xr-x 2 root root 0 Mar 7 00:22 power
lrwxrwxrwx 1 root root 0 Mar 7 00:22 subsystem -> ../../../../../../../../bus/usb
-r--r--r-- 1 root root 4096 Mar 7 00:22 supports_autosuspend
-rw-r--r-- 1 root root 4096 Mar 7 00:22 uevent

I've also played around a little bit, but without any further progress...
- tried to just mount hdd over whatever is on /storage/sdcard0 -> doesn't work as sdcard0 is a link to Storage/emulated/legacy which itself is again a link to /mnt/shell/emulated/0 and apps seem to use that. Mounting on top of /mnt/shell/emulated/0 also doesn't work for some reason unknown to me :crying:
- had a look at vold configuration file in /system/etc/vold.A80H.fstab (in the case of my A80), but I don't even know if that file is interpreted at some time. Changing the faulty hdd path in there had no effect whatsoever.
I'm back to one of the rooted Archos Images, as I want to actually use the thing again I don't think there is a way to dual boot to do some further investigations?

Hi @Quallenauge,
(I don't know if I can talk about it here but it has a relation with the latest kernel update you've done) With your last update, I have a little problem : Indeed my Internal storage is recognized as an external SDcard when I use the file explorer and also I don't have access to the contents of my Internal storage in my computer.
Thank you in advance.

Hi again,
I could actually manage to use the HD for apps and data. It was easier than expected, but still a hack and need some tuning. So don't blame me if it doesn't run on your device.
Okay here is what I have done:
(I use Ubuntu and don't know how to do it on Windows or iOS)
a) Reset and format the device and the HD to start with a clean environment. (Don't forget to save your data somewhere outside)
b) Download and extract @Quallenauge 's CM11 ROM 09_03_2014-12_04_52
c) Mount the archos.ext4.update file
d) Fix the init.archosa101hboard.rc (init.archosa80hboard.rc) file to get the correct file loaded fstab.archosa101hboard (fstab.archosa80hboard.rc)
-> Just seach for 101s (80s) and change to 101h (80h)
e) Change fstab.archosa101hboard (fstab.archosa80hboard.rc) to use the HD for /data:
Code:
#/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,barrier=1 wait
#/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1 wait,check
#/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer
#/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check
# mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# mount ext4 /dev/block/mmcblk0p2 /mnt/system noatime nosuid noexec
# mount ext4 /dev/block/mmcblk0p4 /data noatime nosuid
#/dev/block/mmcblk0p1 /mnt/rawfs rawfs
/dev/block/mmcblk0p2 /mnt/system ext4 noatime,nosuid,noexec wait
#/dev/block/mmcblk0p4 /data ext4 noatime,nosuid wait,check,encryptable=footer
/dev/block/platform/omap/usbhs_omap/sda1 /data ext4 defaults 0 2
/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
#/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/dev/block/zram0 none swap defaults zramsize=134217728
f) Unmount the archos.ext4.update file
g) Install as usual
My impressions:
- I could install all (!) my apps :laugh:
- I have still only 512 MB RAM, so e.g. Adblock Plus be stopped when Chrome is running. I have installed Greenify, which helps a bit. Need more investigation. Any thoughts are welcome!
- Booting takes a bit longer
- As the HD is used to falling quick back in sleep mode and it cannot cache all needed files, it takes some extra time to open an app or switch to one of the other screens.
- Don't know what to do with /dev/block/mmcblk0p4 - Can we use it for caching the HD or as swap device?
- After some time sleeping, the device need to reboot by long pressing on/off (I think that is in discussion in the main [ROM] [4.4.2] CyanogenMod 11.0 thread)
- Not tested yet, but activating the 3g dongle for USB memory would change the HD partiion from sda1 to sdb1, so wouldn't run. Maybe copying the HD to a SD card would be nice to have.
- Battery time: Don't know, as it is always plugged in
At the end I think it is the best ROM for this poor device - so thanks again @Quallenauge

[email protected] said:
Hi again,
I could actually manage to use the HD for apps and data. It was easier than expected, but still a hack and need some tuning. So don't blame me if it doesn't run on your device.
Okay here is what I have done:
(I use Ubuntu and don't know how to do it on Windows or iOS)
a) Reset and format the device and the HD to start with a clean environment. (Don't forget to save your data somewhere outside)
b) Download and extract @Quallenauge 's CM11 ROM 09_03_2014-12_04_52
c) Mount the archos.ext4.update file
d) Fix the init.archosa101hboard.rc (init.archosa80hboard.rc) file to get the correct file loaded fstab.archosa101hboard (fstab.archosa80hboard.rc)
-> Just seach for 101s (80s) and change to 101h (80h)
e) Change fstab.archosa101hboard (fstab.archosa80hboard.rc) to use the HD for /data:
Code:
#/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,barrier=1 wait
#/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1 wait,check
#/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer
#/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check
# mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# mount ext4 /dev/block/mmcblk0p2 /mnt/system noatime nosuid noexec
# mount ext4 /dev/block/mmcblk0p4 /data noatime nosuid
#/dev/block/mmcblk0p1 /mnt/rawfs rawfs
/dev/block/mmcblk0p2 /mnt/system ext4 noatime,nosuid,noexec wait
#/dev/block/mmcblk0p4 /data ext4 noatime,nosuid wait,check,encryptable=footer
/dev/block/platform/omap/usbhs_omap/sda1 /data ext4 defaults 0 2
/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
#/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/dev/block/zram0 none swap defaults zramsize=134217728
f) Unmount the archos.ext4.update file
g) Install as usual
My impressions:
- I could install all (!) my apps :laugh:
- I have still only 512 MB RAM, so e.g. Adblock Plus be stopped when Chrome is running. I have installed Greenify, which helps a bit. Need more investigation. Any thoughts are welcome!
- Booting takes a bit longer
- As the HD is used to falling quick back in sleep mode and it cannot cache all needed files, it takes some extra time to open an app or switch to one of the other screens.
- Don't know what to do with /dev/block/mmcblk0p4 - Can we use it for caching the HD or as swap device?
- After some time sleeping, the device need to reboot by long pressing on/off (I think that is in discussion in the main [ROM] [4.4.2] CyanogenMod 11.0 thread)
- Not tested yet, but activating the 3g dongle for USB memory would change the HD partiion from sda1 to sdb1, so wouldn't run. Maybe copying the HD to a SD card would be nice to have.
- Battery time: Don't know, as it is always plugged in
At the end I think it is the best ROM for this poor device - so thanks again @Quallenauge
Click to expand...
Click to collapse
Nice work [email protected] I'm glad someone is still trying to bring this tablet to the present. Let me know if you need a tester. I have a 80 G9 Turbo 250GB.

[Q] How to recover data and reset flash counter when phone won't boot

My S3 went haywire a few days ago and in my attempts to recover data I loaded the TWRP bootloader and a custom ROM hoping I could eventually reboot it and reset the flash counter. Unfortunately, it still won't reboot - it hangs on the pulsing SAMSUNG animation, after the "Samsung Galaxy SIII" splash screen and the Android blast-off animation.
I've already done a cache wipe and factory reset so ideally I'd like to get it into a state where I can run data recovery software to retrieve my deleted files. But if that can't be done, at the least I want to reset the flash counter so the phone will be replaced under warranty.
Since I received the last replacement in Oct 2013 I forgot to enable USB Debugging and I didn't root phone. In my searches, it looks like the power button is stuck (doesn't feel like it, though) and the phone randomly reboots when is Recovery Mode or Download Mode. About 10% of the time I can get it into either mode and remain stable.
Tools I downloaded & installed:
SkipSoft Android Toolkit (updated and registered)
Samsung USB Drivers v1.5.42.0
Google ADT (updated)
Odin 3.09
Here's what I haven/haven't done so far:
Haven't enabled USB Debugging in the OS
Haven't rooted phone
Installed TWRP 2.7.0.0
Installed root66_TMO_T999UVDMD5.tar, but device still won't boot completely
After TWRP installed, I had to updated driver in Device Manager to "Intel USB Flash Loader Utility" from Samsung. In the TWRP logs I see:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
Running boot script...
Finished running boot script.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
Do I have any hope of recovering the data or resetting the flash counter? I've also considered trying JTAG recovery through a local vendor, but still would like to reset the counter.
Thanks - any help would be GREATLY appreciated.

some progress
OK, with some persistence I managed to get the device to a bootable state. I managed to installed TWRP Bootloader and Chainfire's SuperUser, and that got the phone bootable. Android version is 4.1.2, USB Debugging is now ON, and I went through the setup process but disabled all antennas once I noticed it was downloading content.... PHEW...
For anyone dealing with this issue, here's what worked and didn't:
1 - Spraying CRC brand circuit cleaner on power button - didn't try it, too lazy/scared that I'd break something else
2 - Knocking Power button with a pencil eraser (found elsewhere in xda-developers forum) - this seemed to clear up the issue intermittently
3 - Loaded TWRP using Odin - this worked
4 - Loaded Chainfire AutoRoot - this failed when using miscellaneous tutorials online, BUT it worked when I went straight to the CF Autoroot site (autoroot.chainfire.eu) downloaded the specific file for my device, and loaded it via Odin
Now I'm trying to get data recovery software to recognize the device to analyze the drive and find any recoverable data. Any suggestions?
So far I've tried:
Recuva - unable to see phone
Asoftech Data Recovery - unable to see phone
Glary Undelete - unable to see phone
yodot - unable to see phone

Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.

DocHoliday77 said:
Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.
Click to expand...
Click to collapse
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.

maradamc said:
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.
Click to expand...
Click to collapse
It looks like BusyBox and the DD command can create a bit-by-bit partition dump but I'm not sure how to issue the commands. I have ADB and SU access, BusyBox installed.

dd if=/dev/block/mmcblk0p15 of=c:\path\saving\to
This will dump the entire userdata partition to an image file on your Windows computer. Note the direction of the /'s.

Thanks Doc! I reformatted my external SD Card to exFAT, then ran the DD command to dump the userdata partition. I'm using DiskInternals Linux Recovery right now to scan the image for any recoverable files.
Where can I find more info on those different partitions in /dev/block/? I think some of the files I want to recover are in /data/data/ and I don't know which partition that would be. I've tried "mount" and "ls -l /dev/block/platform/*/by-name/" but I can't find any reference to a /data/ mount.
My last shot will be to downgrade the OS to ICS version and try data recovery directly via the USB cable. All this stuff I'm finding sure will make a good tutorial afterwards.

The dump you created is the entire /data partition. So it should have everything you need. (Userdata/data, same thing in this case. Sorry if I wasn't more clear on that)
You can google t999 galaxy s3 partition layout and should be able to find the rest. Don't have time to look it up and write it ir I'd just post it here for you.

I did some digging and found I need to pull data from:
/sdcard/callrecorder/
/storage/emulated/0/sounds/
I'm trying to decipher if I need to dump any additional partitions. No luck finding much useful information on S3 partitions - this was the closest I found - http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-partition-layout-basic-efs-t1689623
In ADB, I retrieved the following, but none of them obviously map to sdcard or storage/emulated.
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 1969-12-31 22:16 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:16 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:16 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:16 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:16 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:16 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:16 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:16 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:16 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:16 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:16 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:16 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:16 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:16 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:16 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:16 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:16 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:16 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:16 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:16 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:16 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:16 userdata -> /dev/block/mmcblk0p15
[email protected]:/ # mount
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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Additionally, the DD for userdata is 12GB while the whole device is 16GB... still trying to figure out how to capture the remaining 4GB. And to complicate things, I've gotten data recovery software to recognize the image dump and scan it, but the files I want have uncommon file extensions (*.m4a, *.3ga) or no extensions at all. <sigh>... it's gonna be a long week...

The 4gb is reserved for the os and firmware. So a 16gb S3 will have 12gb allocated for /data.
The internal sdcard is not a partition of its own. Its simply part of the data partition.
Also, the link you provided is for the I9300, the international S3 which is a very different device with a different partition layout.
This is ours:
Code:
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
(Just thought it might be a little easier to read this way)
As for pulling the files you need from the .img and the unknown extensions, im not sure. Are you using linux or Windows?

Thanks for that table! I noticed that link wasn't for the T999, which is why I hesitated to rely on it. IDK why I'm having such a hard time finding info on the T999.
Anyway, I managed to DD every single partition by running:
dd if=/dev/block/mmcblk0p5 of=/storage/extSdCard/aboot.img
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/backup.img
dd if=/dev/block/mmcblk0p7 of=/storage/extSdCard/boot.img
dd if=/dev/block/mmcblk0p17 of=/storage/extSdCard/cache.img
dd if=/dev/block/mmcblk0p11 of=/storage/extSdCard/efs.img
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/fota.img
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/fsg.img
dd if=/dev/block/mmcblk0p23 of=/storage/extSdCard/grow.img
dd if=/dev/block/mmcblk0p9 of=/storage/extSdCard/pad.img
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/param.img
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/persist.img
dd if=/dev/block/mmcblk0p18 of=/storage/extSdCard/recovery.img
dd if=/dev/block/mmcblk0p6 of=/storage/extSdCard/rpm.img
dd if=/dev/block/mmcblk0p2 of=/storage/extSdCard/sb11.img
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/sb12.img
dd if=/dev/block/mmcblk0p4 of=/storage/extSdCard/sb13.img
dd if=/dev/block/mmcblk0p22 of=/storage/extSdCard/ssd.img
dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/system.img
dd if=/dev/block/mmcblk0p8 of=/storage/extSdCard/tz.img
dd if=/dev/block/mmcblk0p15 of=/storage/extSdCard/userdata.img
For data recovery, I'm running windows and have installed several tools so I'm able to mount the Linux image as a drive.
Cygwin - I've only played with basics in *nix terminal but am comfortable using command prompt
Ext2Fsd
DiskInternals (Linux Reader & Recovery)
OSFMount
I'll tally up the data recovery/carving tools I've downloaded and tried. Now that I have the images dumped, I'm installing ICS 4.0.4 in an attempt to get USB drive access and try the data recovery software directly against the device.

It may seem difficult to find info on the T999, but a lot of that is due to it being posted in other S3 forums. All US S3's are similar enough that most information applies to all of them. The partition table is one of these. They all are partitioned exactly the same.
Btw, when looking for the internal sdcard data, it will be in the /data/media folder. So in the image just look for the media folder.

I will remember that. Any suggestions where to track down /storage/emulated/0/sounds/ from a partition perspective?
I just finished flashing down to ICS 4.0.4. Even though Odin said it was successful, it's hanging on boot-up at the pulsing Samsung logo just like when this whole mess started. Time for another Factory Reset... not like I can do any more harm.

/storage/emulated/0 = /data/media

Nice! My list of pulled partitions matches the one you provided. Glad to know I was on the right track.
So now I have Android 4.0.4 installed on my device. The problem I have now is that the device isn't recognized in Windows and I can't find a driver for it to work. I've tried Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and v1.5.42.0 - no go. Also tried the ADT driver (android_winusb.inf), still no go. Also tried the driver bundled with the Unified Android Toolkit (by SkipSoft, an XDA dev'r) - no luck. Any suggestions? It must be a driver that supports the old USB Drive mode instead of MTP.
For others who might try this downgrade, I rebooted the device into Download mode and during installation, Odin kept getting an error before finishing. I think it was because I was trying to multitask on the computer because once I let Odin do its thing with and stepped away from the PC, the installation completed successfully. Reboots then kept freezing up but a Factory Reset resolved that.

The S3 never supported using UMS (USB drive), so using different driver versions won't make any difference there. Im honestly not sure if anyone's ever found a way to do this at all. Other than the Easy UMS app.