Related
Hi Forum.
When i try to mount and push apk´s from my PC, i get an error, but i can´t figure out how to get past that, so pleace help me, as i´m proberbly not the only one with that problem...
When checking permissions i get:
-rwsr-xr-x root root 178 2010-11-07 17:19 sh
And that looks allright i think ?
But when i then try to mount and push with:
@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
@adb push content/Phonebook.apk /sdcard/Phonebook.apk
I get this in return:
mount: Operation not permitted
2219 KB/s (3195743 bytes in 1.406s)
/system/app/Phonebook.apk: cannot open for write: Read-only file system
I have installed app2sd, and jit002, and the phone is rooted (with the alternative rooting metod) and it works fine i think, no crashing or anything.
The only problem is that i can´t mount and push...
Here is what i get when i try to see what is mounted on the phone:
D:\>adb shell
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:2 /system/sd ext2 rw,errors=continue 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,gr
oup_id=0,allow_other 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
If you install Root Explorer then you can toggle RO/RW for the system folder.
And when you start Root Explorer, Superuser should say that Root Explorer has been granted superuser rights (or something like that).
Make sure you have superuser and busybox installed, that debugging is activated in the phone and also checkmark 'keep display on' in the debugging options so you can see popups from superuser.
good luck!
mattiL said:
If you install Root Explorer then you can toggle RO/RW for the system folder.
And when you start Root Explorer, Superuser should say that Root Explorer has been granted superuser rights (or something like that).
Click to expand...
Click to collapse
This didn't work for me when trying to install a theme.
mattiL said:
Make sure you have superuser and busybox installed, that debugging is activated in the phone and also checkmark 'keep display on' in the debugging options so you can see popups from superuser.
good luck!
Click to expand...
Click to collapse
Correct and...
when you enter "@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" on your PC, check your mobile and click OK at the message that ask for su access.
I don't know if it is anything to do with it, but if I
Adb kill-server and then
Adb start-server
Everything works fine. Without I always get 'permission denied'
sent from my rooted 2.1 X10i (+JIT) using XDA App
I'm running 2.03 and my browser started crashing so I did a reboot. Now I keep looping between the ViewSonic screen and gtablet screen. I've tried several restores through ClockWorkMod and it still doesn't work. I thought I could try to do the upgrade.zip off of a sd card but how do I get the system to recongize it and not the internal memory?
Stupid question : Have you done a user data wipe/system data wipe from CW?
If cw is not seeing the internal sd and the updates located on the internal sd are not working with full users data wipe, then a nvflash push from pc will have to be done to vanilla tnt, then do an update to get clockwork back, then tnt lite 2.0 with clockwork?
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
arrow21 said:
Stupid question : Have you done a user data wipe/system data wipe from CW?
Click to expand...
Click to collapse
Yes, tried nearly everything I can in Clock and nothing changes the loop. I thought in the worst case you could always find a way to get the system back to it's original state but no luck so far.
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partiton of my sdcard... so I guess that might work also.
arrow21 said:
another option is this
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
I have never done the partition of my sdcard... so I guess that might work also.
Click to expand...
Click to collapse
HELP!!! I think my data partition just go hosed, all I tried to do was restore a backup since I was getting a lot of FC, all trying to access my data folder according to logcat....what do I do, will redoing the partition of my sdcard fix the errors below. How do I repartition and what settings do I use? I was trying to do the restore since I too got stuck in reboot loop. I have the logcat ouput if any dev is interested in seeing it.
Trying to restore backup in clockworkmod I get this:
ClockworkMod Recovery v2.5.1.1-bekit-0.8
Checking MD5 sums...
Erasing boot before restore
Restoring system...
Restoring data...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Error mounting /data/!
Skipping format...
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Can't mount /data/!
rcgabriel said:
You might need to do a re-partition of your SD card (or rather, of the internal SD card memory) from clockwork mod. That has gotten other people out of a boot loop. This most likely has something to do with partitions getting corrupted, which seems to occasionally happen when you are flashing ROMs. You might want to search the forum for SD card partition and boot loop, I know several people have had the same issue.
There is also the APX mode as a backup mechanism if that fails. Search forum for that one too - it's basically a backup to the normal CW or other recovery that lets you flash a fresh ROM even if all else has failed. But I don't think you need to go there if your recovery is still working fine.
Click to expand...
Click to collapse
rc, thanks for the help. Honestly partitioning is something I've never fully understood so I wasn't even sure how to do that. I went into CW and then advanced settings and chose to partition the sd card. The only problem is I didn't know what settings to use so I just used the first ones to pop up. After doing that I did a reboot and things worked fine.
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
scmobileman said:
I was going to go back and try a CW restore and see if I could get everything back but now it can't find the restore file. I assume that happened when I tried to reformat the card.
Click to expand...
Click to collapse
The restore files were are stored on the internal sdcard, so when you formatted, you wiped them out...is my guess. You could have used adb to save them off before hand and then put them back after format.
For the benefit of others, here is how I fixed this:
-Boot into clockworkmod
-Used adb to copy off all sdcard files (including backup files to use in restore)
-Use CW to partition the sdcard (2048mb ext, 256mb swap)
-Tried to copy backup files back...see issues below
-Restore backup files
-Back to working tab
Two issues I had, one is that for the life of me, I could not get the backup files back onto the sdcard. adb must not like windows because it had issues copying the files back unless you copy them to the root of the device. Even then I tried to shell into the device and move the files to the sdcard, but then CW would not see the files, when I reboot the device and try again, the files were gone. I tried to just copy the update.zip file, again CW didn't see the file, and reboot caused it to disappear as well. I managed to mount the tab in USB mode and copy the files to the sdcard using windows. Afterwards CW didn't see the files either.
I figured the system image was good, rebooted to start from scratch, and the setup program ran. I tried to tap the screen bu nothing would happen. Issue two from the log, is that it the setup wizard ignores touch evens if there is no phone interface...reboot again, back into CW, and this time it saw my backup files, restore, then good to go.
My next step would have been to delete the setupwizard apk, wipe data, boot into android, copy backup files, reboot, restore, but not needed finally.
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
raydog.. thank you thank you thank you
thanks
raydog, your post helped greatly. thank you.
Life in LA said:
raydog, your post helped greatly. thank you.
Click to expand...
Click to collapse
Thanks, sad to say I am back in a reboot loop, so I have to do this all over again...uggg
I have shut my tablet off by holding down the power button and bypassing the shutdown screen, wonder if this corrupted the data partition.
I had the reboot problem when trying to load 2.0.0
My fix: Loaded original vanilla via sdcard (took two load tries) then retried 2.0.0 via sdcard and it worked.
please help to make my data read write
raydog153 said:
Have other people run into the above issue where you copy files to the sdcard uin adb while within CW, and the files don't stick. How do you get around this?
Click to expand...
Click to collapse
1|[email protected]:/sbin # su
[email protected]:/sbin # is
sh: is: not found
127|[email protected]:/sbin # cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 ro,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/sbin # fs
sh: fs: not found
127|[email protected]:/sbin # df
Filesystem Size Used Free Blksize
/dev 407.7M 32.0K 407.6M 4096
/sys/fs/cgroup 407.7M 12.0K 407.7M 4096
/mnt/asec 407.7M 0.0K 407.7M 4096
/mnt/obb 407.7M 0.0K 407.7M 4096
/system 1.3G 443.6M 934.3M 4096
/efs 19.7M 8.1M 11.5M 4096
/data 11.9G 5.5G 6.3G 4096
/cache 689.0M 129.8M 559.1M 4096
/mnt/shell/emulated 11.9G 5.5G 6.3G 4096
[email protected]:/sbin # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
[email protected]:/sbin # format 259
sh: format: not found
127|[email protected]:/sbin # del
sh: del: not found
127|[email protected]:/sbin # mount /efs rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /dev
[email protected]:/sbin # mount -o rw,remount /sys/fs/cgroup
[email protected]:/sbin # mount -o rw,remount /mnt/asec
[email protected]:/sbin # mount -o rw,remount /mnt/obb
[email protected]:/sbin # mount -o rw,remount /system
[email protected]:/sbin # mount -o rw,remount /syste
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,remount /efs
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /cache
[email protected]:/sbin # mount -o rw,remount /mnt/shell/emulated
[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw, del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # mount -o rw,del /data
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/sbin # help
sh: help: not found
127|[email protected]:/sbin # Read-only file system
sh: Read-only: not found
127|[email protected]:/sbin # rw
sh: rw: not found
127|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin # mount -o rw,remount /data
mount: Read-only file system
255|[email protected]:/sbin #
this is my partition table and errors for p3100.
please help me how to make it read write.
please mailm e the steps.
[email protected]
thanks in advance
Anybody with a Sony Tablet S, a few minutes to spare, and some basic ADB knowledge, can you please run the following command for me?
Code:
adb shell mount > sony-tablet-s-mounts.txt
Then simply upload the text file called sony-tablet-s-mounts.txt that is in your adb tools folder or whatever directory you ran that command from.
Also please run.
Code:
adb shell cat /proc/mounts/ > sony-tablet-s-proc-mounts.txt
Then again upload that file that was outputted.
Here we go:
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,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/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.bbb.btr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.polarbit.rthunderlite-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
proc/mounts
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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,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/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.bbb.btr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.polarbit.rthunderlite-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
Anything else?
Also tried proc/mtd but that had no output.
Sent from my Sony Tablet S using Tapatalk
manually push busybox to /data/tmp/local/ and try to remount /system as RW
then try to push su binary to /system/bin/ (give it permission 06755)
then try to push Superuser.apk to /system/app/
btw does this tablet have some sort of recovery mode? what abt bootloader status?
Code:
[email protected] ~/data/Android/exploits $ adb push busybox /data/tmp/local/
failed to copy 'busybox' to '/data/tmp/local/': No such file or directory
[email protected] ~/data/Android/exploits $ adb push busybox /data/local/
1322 KB/s (1062992 bytes in 0.784s)
[email protected] ~/data/Android/exploits $ adb shell
$ chmod 777 /data/local/busybox
$ /data/local/busybox su
su: must be suid to work properly
$ /data/local/busybox sulogin
sulogin: no password entry for root
$ /data/local/busybox mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: permission denied (are you root?)
$ mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: Operation not permitted
$ /data/local/busybox whoami
whoami: unknown uid 2000
So... stuck at remounting with rw permissions. no permissions
There is a recovery mode (power + volume-up key at boot).
abt bootloader status? Don't know what that is, and how to check.
Elkan85 said:
Code:
[email protected] ~/data/Android/exploits $ adb push busybox /data/tmp/local/
failed to copy 'busybox' to '/data/tmp/local/': No such file or directory
[email protected] ~/data/Android/exploits $ adb push busybox /data/local/
1322 KB/s (1062992 bytes in 0.784s)
[email protected] ~/data/Android/exploits $ adb shell
$ chmod 777 /data/local/busybox
$ /data/local/busybox su
su: must be suid to work properly
$ /data/local/busybox sulogin
sulogin: no password entry for root
$ /data/local/busybox mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: permission denied (are you root?)
$ mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: Operation not permitted
$ /data/local/busybox whoami
whoami: unknown uid 2000
So... stuck at remounting with rw permissions. no permissions
There is a recovery mode (power + volume-up key at boot).
abt bootloader status? Don't know what that is, and how to check.
Click to expand...
Click to collapse
why are u remounting as yaffs2?
just use:
Code:
busybox mount -o remount, rw /system
is adb active in recovery? if yes then try pushing su/busybox when in recovery mode...
ADB ain't active in recovery mode.
in fact we only have 3 choices in recovery mode:
- reboot
- update from sd-card
- return to factory settings
try to find a fastboot bin for linux, maybe can use it to
fastboot into bootloader(?)
Code:
$$ /data/local/busybox mount -o remount, rw /system
mount: permission denied (are you root?)
$$ mount -o remount, rw /system
mount: Operation not permitted
Elkan85 said:
ADB ain't active in recovery mode.
in fact we only have 3 choices in recovery mode:
- reboot
- update from sd-card
- return to factory settings
try to find a fastboot bin for linux, maybe can use it to
fastboot into bootloader(?)
Code:
$$ /data/local/busybox mount -o remount, rw /system
mount: permission denied (are you root?)
$$ mount -o remount, rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
There should be generic update.zip to flash via recovery for SU. Try if that works
Sent from my GT-I9100 using XDA App
DooMLoRD said:
There should be generic update.zip to flash via recovery for SU. Try if that works
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
found some...
But with all i get:
signature verification failed
anyway to avoid that?
Posted on the sony forum a request for the original update.zip
hope i can get something...
hi
i cant see anyway to go in fastboot.
boot with vol+ there are stop in the stock recovery "Android system recovery <Rev.7 <3e>"
3 Option in recovery:
1. cancel ans restart device
2. Update system from sd card.
3. Reset to factory setting
But with sdcard update there comes E:signature verfication fail i try this file http://forum.xda-developers.com/showthread.php?t=1288348
adb works with debugging is enable, but the remount of the /system dosnt work.
how we become root ?
The Sony Tablet has a 3e recovery, isn't this the same issue as with this >> http://forum.xda-developers.com/showthread.php?t=833423
here some infos
Code:
cat /proc/partitions
major minor #blocks name
179 0 15629312 mmcblk0
179 1 2048 mmcblk0p1
179 2 393216 mmcblk0p2
179 3 393216 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 393216 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 4194304 mmcblk0p10
179 11 9368576 mmcblk0p11
179 16 31702016 mmcblk1
179 17 31697920 mmcblk1p1
$
edit: add dmesg.txt
is there any way to make temporary root ?
jhepoy said:
The Sony Tablet has a 3e recovery, isn't this the same issue as with this >> http://forum.xda-developers.com/showthread.php?t=833423
Click to expand...
Click to collapse
Tried that, this aint gonna work because it try to mount /system rw.
Sent from my Sony Tablet S using Tapatalk
Elkan85 said:
Tried that, this aint gonna work because it try to mount /system rw.
Click to expand...
Click to collapse
You have /system in rw ? then you can make root.
PeterPan6754 said:
You have /system in rw ? then you can make root.
Click to expand...
Click to collapse
I wish i had rw in /system..
Still trying to exploit this ****..
Elkan85 said:
I wish i had rw in /system..
Still trying to exploit this ****..
Click to expand...
Click to collapse
hello
have you make chances in the instal.lbat file ?
and use the su from the honeycomb superuser files ?
im not at home and cant test it.
Code:
ECHO Installing modified recovery
%adb% start-server >nul
%adb% -d wait-for-device >nul
%adb% -d shell mount -o rw,remount /dev/block/mmcblk0p3 /system
%adb% -d push %su% /system/bin/su
%adb% -d shell chmod 06755 /system/xbin/su
GOTO :finished
Thanks for trying so hard guys, if you can crack this and bring root to the tablet s you will be legends. I will happily donate via paypal as a thank you.
PeterPan6754 said:
hello
have you make chances in the instal.lbat file ?
and use the su from the honeycomb superuser files ?
im not at home and cant test it.
Code:
ECHO Installing modified recovery
%adb% start-server >nul
%adb% -d wait-for-device >nul
%adb% -d shell mount -o rw,remount /dev/block/mmcblk0p3 /system
%adb% -d push %su% /system/bin/su
%adb% -d shell chmod 06755 /system/xbin/su
GOTO :finished
Click to expand...
Click to collapse
That doesn't work either..
Because we have no mountain permissions..
Sent from my HTC Desire using XDA App
Elkan85 said:
That doesn't work either..
Because we have no mountain permissions..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yes it dosnt work
Getting temporary root.
> Starting adb server: Success
Checking for temporary root.
Installing rageagainstthecage.
> Uploading rageagainstthecage: Success
> chmod rageagainstthecage: Success
> Running rageagainstthecage: Success
Checking for temporary root.
> Stopping adb server: Success
> Starting adb server: Success
> Checking for root: Error: timed out
temp root failed! install cannot continue.
Click to expand...
Click to collapse
Hey guys. I am working on a total recovery method for this device to assist you guys in making a Hard Bricked device work properly. I need to create a stock firmware package. I've been working my ass off trying to make this a reality.. I've downloaded 10 firmware packages with no success. So, now the only option left is to rebuild from a working device.
Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
So, in this thread I'm asking for community help. I'll post the task and anyone can execute the commands:
1. use a terminal emulator on your phone and execute 'su' and 'mount'
2. copy-paste from the terminal emulator into the forums so we can locate the proper devices per partition
3. execute some commands to dump some partitions which will be determined by step 2
4. post the dumped partitions here.
Anyone can participate in any of these steps... Lets do this quickly!
Task1:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copypasta the results of the mount command here.
Hello, I appreciate your work! Will this be able to fix a brick no matter how screwed it is?
The reason I ask is because I believe I have messed up something concerning the pit file.
I was about to send it into samsung to repair, but if this could fix it...
iJimaniac said:
Hello, I appreciate your work! Will this be able to fix a brick no matter how screwed it is?
The reason I ask is because I believe I have messed up something concerning the pit file.
I was about to send it into samsung to repair, but if this could fix it...
Click to expand...
Click to collapse
I need this information to develop a total recovery solution.
I'm breaking this down really simple. Please don't clutter this thread. I probly should have posted in development
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copy and paste the results of the mount command here.
Hope this helps
Also would you be able to create a rom for this device say ICS ?
Code:
$ export PATH=/data/local/bin:$PATH
$ su
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
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/mmcblk0p13 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p10 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p16 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p14 /dbdata rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p15 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p9 /mnt/.lfs j4fs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/259:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
AdamOutler said:
Hey guys. I am working on a total recovery method for this device to assist you guys in making a Hard Bricked device work properly. I need to create a stock firmware package. I've been working my ass off trying to make this a reality.. I've downloaded 10 firmware packages with no success. So, now the only option left is to rebuild from a working device.
Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
So, in this thread I'm asking for community help. I'll post the task and anyone can execute the commands:
1. use a terminal emulator on your phone and execute 'su' and 'mount'
2. copy-paste from the terminal emulator into the forums so we can locate the proper devices per partition
3. execute some commands to dump some partitions which will be determined by step 2
4. post the dumped partitions here.
Anyone can participate in any of these steps... Lets do this quickly!
Task1:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copypasta the results of the mount command here.
Click to expand...
Click to collapse
I can make this for you but do you need a US or EU version. Because I have a EU version. And for recovery it's recovery.bin? or .img?
---------- Post added at 01:16 PM ---------- Previous post was at 12:27 PM ----------
Here my mount command. Hope this helps.
Code:
$ su
su
# mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type rfs (ro,relatime,vfat,log_off,check=no,gid/uid/r
wx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid
/uid/rwx,iocharset=utf8)
/dev/block/mmcblk0p2 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=
no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no
,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,
gid/uid/rwx,iocharset=utf8)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,n
oatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codep
age=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,no
dev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utim
e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro
)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noe
xec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,
codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k
,mode=000)
alright. Now task 2,3 and 4.. Anyone can do this.
I need a copy of working partitions from a device. You must trust me that I will perform a master clear. I will not post your personal partitions. I need a template to work with in order to get this device working.
2: execute the following code on your device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere and send me a PM. If you would like, I have a private FTP site at ftp://adamoutler.com and I will give you a login/password to log into my personal network attached storage and upload the zip file containing the partitions.
zaclimon said:
I can make this for you but do you need a US or EU version. Because I have a EU version. And for recovery it's recovery.bin? or .img?
Click to expand...
Click to collapse
It does not matter.. US, EU.. They're all fine. I think I can make a recovery.bin.
Rueben_ said:
Hope this helps
Also would you be able to create a rom for this device say ICS ?
Click to expand...
Click to collapse
That's possible. I don't own a device to work with, but a total recovery solution comes before any development. You have to have a way to get back to stock.
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
AdamOutler said:
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
Click to expand...
Click to collapse
I can't help you with this. I have an error which is said there is no such files or directory.
zaclimon said:
I can't help you with this. I have an error which is said there is no such files or directory.
Click to expand...
Click to collapse
You may have typed it wrong. Please try again.
Another method for those of you with Linux or any type of SSH terminal like the windows tool puTTY, is to use an app like SSHDroid then terminal in to your device and copy-paste the code block in.
This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
I have the same error coming up ? :/
Error: cannot open for write: No such file or directory
Rueben_ said:
I have the same error coming up ? :/
Error: cannot open for write: No such file or directory
Click to expand...
Click to collapse
Do you have an SDCard in your device?
try the same lines with /sdcard instead of /mnt/sdcard.
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs
AdamOutler said:
Do you have an SDCard in your device?
try the same lines with /sdcard instead of /mnt/sdcard.
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs
Click to expand...
Click to collapse
It's not working either. I think the player don't have these blocks.
zaclimon said:
It's not working either. I think the player don't have these blocks.
Click to expand...
Click to collapse
The player has these blocks, you can't write them to the sdcard. it says can't write.
Code:
Error: cannot open for write: No such file or directory
what is the sdcard called on the filesystem?
try changing the blocksize... i belive it was 512 on this device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs bs=512
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs bs=512
I can get these files directly from your device if you want to add me on google talk.. we need to get market app wireless adb installed and put your device into the DMZ on your router. *myusername* @gmail.com
AdamOutler said:
try changing the blocksize... i belive it was 512 on this device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/data.rfs bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/cache.rfs bs=512
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.rfs bs=512
Click to expand...
Click to collapse
I checked my mount and used the stl block instead of mmcblk0p block. Is this matter? What is DMZ? I think data will take a little more time.
Ok I have my files. What do I do now?
EDIT: My blocks and Rueben_'s are different. That's why it don't work with me.
zaclimon said:
I checked my mount and used the stl block instead of mmcblk0p block. Is this matter? What is DMZ? I think data will take a little more time.
Click to expand...
Click to collapse
DMZ on a router is where you unrestrict the IP address of a device on your network. Everything is directed to that IP. Othewise I need ports 22 and 5555 directed to the IP address of your device running adbwireless.
AdamOutler said:
DMZ on a router is where you unrestrict the IP address of a device on your network. Everything is directed to that IP. Othewise I need ports 22 and 5555 directed to the IP address of your device running adbwireless.
Click to expand...
Click to collapse
It seems difficult to configure it on my router. It would be easier to upload it no?
zaclimon said:
It seems difficult to configure it on my router. It would be easier to upload it no?
Click to expand...
Click to collapse
PM sent with my information, login and password.
I hope this works, just in case, can you ALSO get the BML blocks for this?
If you are reading this, DON'T TRY IT UNLESS IT'S VERIFIED BY SOMEONE IN THIS THREAD.
First of all, this is my first post here in xda, so I'll try it to be as helpfull as possible to other users doing a guide of how to backup your international i9100 to an Odin flashable rom, so you can restore all of your configurations at once, including installed programs, accounts... everything in your phone.
But why? I want to backup my S2 to an Odin rom before I try ICS 4.0.3, because it could take my several ours to restore everything to the way it was before updating in case I don't like it. Yes, I know what Titanium backup is, I have my phone rooted and I do a programmed backup each day at 3am. But I still want to be able to do it in just ONE step with Odin without dealing with Titanium backup's filters and system's apps.
So it's a great way to restore your phone to it's previous state for all of you that install a new rom and doesn't like how it works, or may be you are having issues after upgrading, or just want to take a look and go back quickly. Just one step and three minutes with Odin.
But in the case of ICS 4.0.3 you have to repartition your phone both ways, when upgrading and when downgrading, and that's first rule of the Odin's club: Don't touch the repartition option (of course, it's also second rule ).
Anyway, I'm posting a guide to do it in i9100 that HAS TO BE VERIFIED by someone with enough knowledge about how the partitioning works. It must work fine if you stay between 2.x versions without repartitioning, but as I told before, I don't know for sure, as I'm a bit confused about which partition is each one and which ones are needed to be backed up.
So please, if someone has enough knowledge to do it safely, post a reply with corrections to this method.
Here is the guide
HOW TO BACKUP A PARTITION
To backup a partition, you must open a terminal emulator, or conect from your computer via adb shell, and use dd command (duplicate disk) in su mode to create a backup of your partitions. Don't ask me how, if you don't know, you shouldn't be reading this. You will compress them later to load them in Odin.
ABOUT PARTITIONS
Each device has different names for the same partitions. For example, /system partition might be /dev/block/mmcblk0p9 in i9100, but in Samsung Continuum it's /dev/block/stl9.
So, in Galaxy SII partitions are (taken from here by HellcatDroid)
To see them in your device, open an adb shell, and type cat /proc/mounts. If you do it in i9100, you will find something like this:
Code:
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
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
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[B]/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=writeback,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=writeback,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=writeback,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=writeback,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0[/B]
So... How do I backup partitions
According to HellcatAndroid, and for Galaxy S2 i9100, you have to backup using this commands:
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.bin bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.rfs bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
but as you see, not all of them are visible, but all of them will backup.
Some authors also claim you need to mount filesystem as RW (mount -o rw,remount /dev/block/mmcblk0p9 /system). It worked for me without mounting it as RW.
Someone please confirm this step is enough to backup everything, and there is no need to remount as RW.
If you want to backup your data, run Someone please confirm this step is correct
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10-DATA bs=4096
Creating Odin image
Next step is to create the tarball of the dumped partitions. Copy or move the generated .img files to another folder, and create the tarball typing the following command into a linux terminal (you can do it in a VM or in cywin):
Code:
tar -H ustar -c p9-FACTORYFS.rfs p8-MODEM.bin p5-KERNEL > i9100backup.tar
If you want to add your data, you must run instead Someone please confirm this step is correct
Code:
tar -H ustar -c p9-FACTORYFS.rfs p8-MODEM.bin p5-KERNEL p10-DATA > i9100backup.tar
After that, add the md5 checksum:
Code:
md5sum –t i9100backup.tar >> i9100backup.tar
mv i9100backup.tar i9100backup.tar.md5
And that's all, i9100backup.tar.md5 is your Odin rom.
CONSIDERATIONS IF YOU ARE MOVING TO ICS FROM GINGERBREAD AND BACK
Someone please confirm this step is correct
When you upgrade to ICS, you have to tick repartition option, and do it again when downgrading. So you will need a .PIT file with information about your partition table to be able to do it right without bricking your phone.
So if you want to enable your rom to be used for a downgrade from ICS, you must run
Code:
dd if=/dev/block/bml2 of=/sdcard/FILENAME.pit bs=4096
and add it to the rom when creating the tarball. READ BELOW
In this case, bml2 is for Galaxy S, NOT FOR GALAXY S2 I9100, so please someone help finding i9100 filesystem.
WARNING
Doing this step wrong, can brick your phone permanently.
Sources:
How to build ODIN flashable ROMs for Samsung Galaxy S Series
[Q] How to Backup and Restore Original Shipped Firmware? For warranty.
Creating Custom ROMs/Backups for Odin
Why just not use CWM to make a backup. Then flash a ROM from Intratech them recover your backup.
Sent from my GT-I9100 using XDA App
Odd guide post to help other users when the OP requires confirmation of a number of commands from others its pointless .
New phone download your firmware from branded provider roms post or via CHECKFUS .
Or a stock rom ..
You can then flash roms or not .
jje
That will leave you with the backup you did with cwm, just like you were, without the possibility to try ics due to the repartition issue. Also, with a new rom, cwm version might be changed, and backups from older versions won't work.
I've tagged the thread as question, not as guide. Maybe the title is a bit confusing but I'm looking for help from someone who knows better than me to make a guide to backup with odin, with repartition included, and safely. It could be really useful during transition to first versions if ICS.
Any help with partitions in i9100, Odin ant .PIT files is appreciated.
First of all I can say one thing - it is ALWAYS better to dump read only partition. So mounting /system as RW is a BAD idea. Well. you can't mounta ll partitions as R/O because phone is using them and you could break something, but where you can (system) dump while it's mounted as read only. Dumping restoring read-write partition will cause a possible lost blocks and will force a check, which will hopefully fix file system without permanent damage.
Now I was searching for information about i9100 partitions and backup/restore using dd and odin (or restore via something else). It's easy to answer Why, not easy to answer how.
Why?
1. Updating kernel image voids the phone warranty. So if you use CWM to make a backup - you already updated the kernel and you will be backing up the updated kernel.
1a. You'll say "you can use stock image". Well yes, but the phone has a serial number, from which they can see exactly which version your software should be. I've searched about sock kernels and they do not provide all versions of stock kernels. Yes, there is almost no difference in how your phone behaves if you don't get exact version for your location, but they will know that you've updated the kernel -> no warranty
2. Come one guys DD is universal. It's format doesn't change, simply because it's raw 1:1, byte-to-byte copy. I've already tried to use backup tools and they don't even detect if the phone, software, OS and kernel are the correct versions to allow backup. Sometimes they crash. When using dd it is all in your hands. If there is a mistake - it's yours. Yes, big responsibility, but it's the only way to be sure when you are about to update kernel.
3. For dd you need root. Yes, but root is reversable. you can restore the system like it was before rooting.
However...
Partitioning is kind-a tricky. I couldn't find any information about partitioning, partition files (.pit) and how to make them. Maybe it's because in forums read a lot of noobs and developers don't post that kind of info to save them troubles.
Are you sure that this is correct for galaxy S:
dd if=/dev/block/bml2 of=/sdcard/FILENAME.pit bs=4096
do they have a partition to store partition information ... that would be stupid
I wander what will happen if I dump the whole drive - like:
dd if=/dev/block/mmcblk0 of=/sdcard/galaxyS2.img bs=4096
Is there a way to make a restore script and run it in recovery mode. I guess I can compile/find static version of dd, but I'm not sure how recovery scripts work.
I'll appreciate Some links that lead to the right readings about making recovery images/scripts for update...