Data-Partition isn't there - Android Q&A, Help & Troubleshooting

Hi Guys,
I've an Amlogic MX based Tablet and played a little around with some Kernel and ROMs and now I have the problem that my Data-Partition (/dev/block/data) is gone.
Code:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,size=410328k,nr_inodes=74092,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 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
none /proc/bus/usb usbfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
tmpfs /storage/external_storage tmpfs rw,relatime,size=410328k,nr_inodes=74092,mode=775,gid=1000 0 0
/dev/block/system /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/cache /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /factory yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/253:1 /storage/external_storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Code:
ls -l /dev/block/
brw------- root root 250, 28 2014-07-26 11:21 cache
brw------- root root 253, 0 2014-07-26 11:21 cardblksd
brw------- root root 253, 1 2014-07-26 11:21 cardblksd1
brw------- root root 250, 24 2014-07-26 11:21 factory
brw------- root root 7, 0 2014-07-26 11:21 loop0
brw------- root root 7, 1 2014-07-26 11:21 loop1
brw------- root root 7, 2 2014-07-26 11:21 loop2
brw------- root root 7, 3 2014-07-26 11:21 loop3
brw------- root root 7, 4 2014-07-26 11:21 loop4
brw------- root root 7, 5 2014-07-26 11:21 loop5
brw------- root root 7, 6 2014-07-26 11:21 loop6
brw------- root root 7, 7 2014-07-26 11:21 loop7
brw------- root root 31, 0 2014-07-26 11:21 mtdblock0
brw------- root root 31, 1 2014-07-26 11:21 mtdblock1
brw------- root root 31, 2 2014-07-26 11:21 mtdblock2
brw------- root root 31, 3 2014-07-26 11:21 mtdblock3
brw------- root root 31, 4 2014-07-26 11:21 mtdblock4
brw------- root root 31, 5 2014-07-26 11:21 mtdblock5
brw------- root root 31, 6 2014-07-26 11:21 mtdblock6
brw------- root root 31, 7 2014-07-26 11:21 mtdblock7
brw------- root root 31, 8 2014-07-26 11:21 mtdblock8
drwxr-xr-x root root 2014-07-26 11:21 platform
brw------- root root 1, 0 2014-07-26 11:21 ram0
brw------- root root 1, 1 2014-07-26 11:21 ram1
brw------- root root 1, 10 2014-07-26 11:21 ram10
brw------- root root 1, 11 2014-07-26 11:21 ram11
brw------- root root 1, 12 2014-07-26 11:21 ram12
brw------- root root 1, 13 2014-07-26 11:21 ram13
brw------- root root 1, 14 2014-07-26 11:21 ram14
brw------- root root 1, 15 2014-07-26 11:21 ram15
brw------- root root 1, 2 2014-07-26 11:21 ram2
brw------- root root 1, 3 2014-07-26 11:21 ram3
brw------- root root 1, 4 2014-07-26 11:21 ram4
brw------- root root 1, 5 2014-07-26 11:21 ram5
brw------- root root 1, 6 2014-07-26 11:21 ram6
brw------- root root 1, 7 2014-07-26 11:21 ram7
brw------- root root 1, 8 2014-07-26 11:21 ram8
brw------- root root 1, 9 2014-07-26 11:21 ram9
brw------- root root 250, 20 2014-07-26 11:21 system
drwx------ root root 2014-07-26 11:21 vold
If I flash an older Stock-ROM with UBIFS the Data-Partition is there, but not as Ext4-Partition.
Code:
ubi0_0 /system ubifs rw,relatime 0 0
ubi1_0 /data ubifs rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
After flashing back to a newer Stock-Rom with Android 4.2.2 (EXT4-ROM), I have the same issue as above,
Recovery stops with following output:
Code:
Finding update package...
Openning update package...
Verifying update package...
Installing update...
Formatting /cache...
Formatting /data...
Formatting /cache...
Data wipe failed.
Formatting /cache...
Cache wipe failed.
CWM is a little more verbose with this:
Code:
E:format_volume: make_extf4fs failed on /dev/block/data
Anyone a Idea how to recover Ext4-Data-Partition?
Thanks.

Related

[CWM]Samsung Galaxy PRO b7510 (ALPHA )

please don't try it if you don't know how to handle it
hello guys
i ported CWM recovery for our device b7510
but it still alpha and i hope some one can help me
the problem is stock kernel rfs i can't mount system or data and cache
only sdcard
i need help guys
Download
up .
can you post the output of:
Code:
mount
or the boot.img ?
hey
mount
rootfs / rootfs rw,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
# ls -l /dev/block
ls -l /dev/block
brw------- root root 138, 14 2011-12-27 19:12 stl14
brw------- root root 138, 13 2011-12-27 19:12 stl13
brw------- root root 138, 12 2011-12-27 19:12 stl12
brw------- root root 138, 11 2011-12-27 19:12 stl11
brw------- root root 138, 10 2011-12-27 19:12 stl10
brw------- root root 138, 9 2011-12-27 19:12 stl9
brw------- root root 138, 8 2011-12-27 19:12 stl8
brw------- root root 138, 7 2011-12-27 19:12 stl7
brw------- root root 138, 6 2011-12-27 19:12 stl6
brw------- root root 138, 5 2011-12-27 19:12 stl5
brw------- root root 138, 4 2011-12-27 19:12 stl4
brw------- root root 138, 3 2011-12-27 19:12 stl3
brw------- root root 138, 2 2011-12-27 19:12 stl2
brw------- root root 138, 1 2011-12-27 19:12 stl1
brw------- root root 137, 14 2011-12-27 19:12 bml14
brw------- root root 137, 13 2011-12-27 19:12 bml13
brw------- root root 137, 12 2011-12-27 19:12 bml12
brw------- root root 137, 11 2011-12-27 19:12 bml11
brw------- root root 137, 10 2011-12-27 19:12 bml10
brw------- root root 137, 9 2011-12-27 19:12 bml9
brw------- root root 137, 8 2011-12-27 19:12 bml8
brw------- root root 137, 7 2011-12-27 19:12 bml7
brw------- root root 137, 6 2011-12-27 19:12 bml6
brw------- root root 137, 5 2011-12-27 19:12 bml5
brw------- root root 137, 4 2011-12-27 19:12 bml4
brw------- root root 137, 3 2011-12-27 19:12 bml3
brw------- root root 137, 2 2011-12-27 19:12 bml2
brw------- root root 137, 1 2011-12-27 19:12 bml1
brw------- root root 137, 0 2011-12-27 19:12 bml0!c
drwxr-xr-x root root 2011-12-27 19:12 vold
brw------- root root 7, 7 2011-12-27 19:12 loop7
brw------- root root 7, 6 2011-12-27 19:12 loop6
brw------- root root 7, 5 2011-12-27 19:12 loop5
brw------- root root 7, 4 2011-12-27 19:12 loop4
brw------- root root 7, 3 2011-12-27 19:12 loop3
brw------- root root 7, 2 2011-12-27 19:12 loop2
brw------- root root 7, 1 2011-12-27 19:12 loop1
brw------- root root 7, 0 2011-12-27 19:12 loop0
brw------- root root 1, 7 2011-12-27 19:12 ram7
brw------- root root 1, 6 2011-12-27 19:12 ram6
brw------- root root 1, 5 2011-12-27 19:12 ram5
brw------- root root 1, 4 2011-12-27 19:12 ram4
brw------- root root 1, 3 2011-12-27 19:12 ram3
brw------- root root 1, 2 2011-12-27 19:12 ram2
brw------- root root 1, 1 2011-12-27 19:12 ram1
brw------- root root 1, 0 2011-12-27 19:12 ram0
#
boot.img here
thanks
updated here cwm recovery
enjoy
thanks to Skin1980
updated
download here
thanks
Is it for the Gingerbread version? Thanks
netomx said:
Is it for the Gingerbread version? Thanks
Click to expand...
Click to collapse
no it is for froyo
Thanx for the efforts mazen, could u please re-upload the last file "recovery1" if not updated with another one.
i can't update it any more i lost my phone
ok i uploaded it to dropbox
download here
Thanx alot, and sorry about ur phone..
nothing for gingerbread???
soory about ur phone
it is work? anyone try this file on b7510?
pls answer galaxy pro user or anybody can help me for back up my stock rom?
it is not work.................
اهلا الاخ مازن ,,, انا وليد الهادي
اسف على الازعاج ,
حبيت اسالك ايش اللي صار في جوالك
is that still ALPHA?
---------- Post added at 07:11 PM ---------- Previous post was at 07:06 PM ----------
is that still alpha version?
any updates to this?
Samsung Galaxy pro CWM
hiii........can you again post the download link as the link you have mentioned doesnt have any file or its been deleted...thanks
dropbox link is dead or blocked
vikd007 said:
hiii........can you again post the download link as the link you have mentioned doesnt have any file or its been deleted...thanks
Click to expand...
Click to collapse
Please share an updated link of CWM recovery for B7510
Thanks
Hey anyone still use galaxy pro?
Sent from my GT-I9300 using XDA Free mobile app

Pledge a Bounty for Unlocked Bootloader for Sony Tablet S [$103 Pledged]

BOUNTY FOR UNLOCKED BOOTLOADER FOR SONY TABLET S
$103 PLEDGED!
Following the successful root of our devices, one would expect that more developer support should come to Sony Tablet S. Yet, having root is but one of the two 'holy grails' which will turn our devices into hot properties.
As such, I suggest we begin a second bounty, this time for the first person to successfully unlock the bootloader and provide a working proof of concept for its implementation*. Given that the ICS update will (likely) remove our root, we will still be back to square one unless someone can couple the first success with a working unlocked bootloader which will finally let us install recovery and hopefully install custom ROMs or customized official ROMs.
I hope we can get as many people aboard as possible, and at least some of the usual suspects from the root equivalent bounty topic.
*The Rules:
'Unlocking the bootloader' refers to: An exploit, method or application/software which unlocks the bootloader and allows us to install custom recoveries, kernels or ROMs.
To earn the bounty, you simply have to find the exploit which will allow the above first. You do not have to develop a recovery, or a kernel or a ROM, but you must provide with a working proof of concept, i.e. with a way which allows us to verify that the bootloader has been completely unlocked and that other developers can use this method to install recovery, kernel and ROMs.
Here's hoping there are some who will take this new challenge up with renewed vigour, now that root is here!
The pledgers:
1. grcd: $12
2. condi: $10
4. wintermute000: $10
5. kvssvarma: $10
6. [email protected]: $25
7. eldron: $16 [Pledged via PM]
8. xaviorffviii: $20
NOTE: THIS TOPIC ALSO CONTAINS AN ACTIVE TECHNICAL CONVERSATION REGARDING THE TOPIC. SEE HERE AND FOLLOW ENSUING CONVERSATIONS.
10$ from me
$10 from me too
Is there actually any evidence that the bootloader is locked? Keep in mind there's a difference between a locked bootloader and a bootloader that doesn't support flashing by default.
A truly locked bootloader (like HBOOT on HTC devices or Motorola's MBM bootloader) actually verifies a digital signature on the boot or recovery partition before booting it, so it's not possible to run custom ROMs without using workarounds like 2nd init.
On the other hand, some bootloaders don't allow you to *flash* images by default, but if you manage to get root and flash a new recovery or boot image, it will boot without complaint.
Unless someone has a reason to believe otherwise, it might be possible that the Sony Tablet S falls into the second category. Now that root has been achieved, it's possible to flash custom recovery images by writing to a block device using ADB.
It's definitely worth trying this out. Someone who knows what they're doing should create a full backup of the original recovery partition (using "dd" from a root shell) and flash a custom recovery image to the appropriate block device and see what happens when you try to boot into recovery mode. There's a chance it "just works".
You are right about this. If you could provide a little bit more information I would be willing to try it out myself. Sometimes you have to treat everyone as a complete newbie. I have a degree in Computing -- although I have never professed it and I am now in an entirely different academic field (Sociology/Cultural Anthropology), and to be entirely frank, I am adept at following instructions but not trying things on my own which might brick my device
Well, the first step is easy: make a backup of the existing recovery partition.
Load up an ADB shell and type "su" to assume root privileges. Next, you can make an exact copy of the recovery image by using dd:
dd if=/dev/block/recovery of=/sdcard/recovery.img
This is assuming you have enough room on your SD card to fit the recovery image. At this point, it would be helpful if you could pull that off the phone ("adb pull /sdcard/recovery.img") and get it in the hands of someone who knows what they're doing.
The next step involves flashing a recovery image to the device. Basically just the reverse of the previous step:
dd if=/sdcard/new_recovery.img of=/dev/block/recovery
Where you've placed a new recovery image on the SD card as "new_recovery.img". Of course, this is the part where someone with experience needs to do some work. I doubt most custom recoveries are going to work right off the shelf. You'll have to get someone who's used to developing custom recoveries to get involved to port it to the Sony Tablet S.
'ls' od /dev/block:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
mmcblk1
mmcblk1p1
platform
svold
vold;
Detailed structure:
# find
find
.
./vold
./vold/179:11
./vold/179:10
./vold/179:9
./vold/179:8
./vold/179:7
./vold/179:6
./vold/179:5
./vold/179:4
./vold/179:3
./vold/179:2
./vold/179:1
./vold/179:0
./svold
./svold/179:17
./svold/179:16
./loop7
./loop6
./loop5
./loop4
./loop3
./loop2
./loop1
./loop0
./mmcblk1p1
./mmcblk1
./mmcblk0p11
./mmcblk0p10
./mmcblk0p9
./mmcblk0p8
./mmcblk0p7
./mmcblk0p6
./mmcblk0p5
./mmcblk0p4
./mmcblk0p3
./mmcblk0p2
./mmcblk0p1
./platform
./platform/sdhci-tegra.2
./platform/sdhci-tegra.2/mmcblk1p1
./platform/sdhci-tegra.2/by-num
./platform/sdhci-tegra.2/by-num/p1
./platform/sdhci-tegra.2/by-name
./platform/sdhci-tegra.2/mmcblk1
./platform/sdhci-tegra.3
./platform/sdhci-tegra.3/mmcblk0p11
./platform/sdhci-tegra.3/mmcblk0p10
./platform/sdhci-tegra.3/mmcblk0p9
./platform/sdhci-tegra.3/mmcblk0p8
./platform/sdhci-tegra.3/mmcblk0p7
./platform/sdhci-tegra.3/mmcblk0p6
./platform/sdhci-tegra.3/mmcblk0p5
./platform/sdhci-tegra.3/mmcblk0p4
./platform/sdhci-tegra.3/mmcblk0p3
./platform/sdhci-tegra.3/mmcblk0p2
./platform/sdhci-tegra.3/mmcblk0p1
./platform/sdhci-tegra.3/by-num
./platform/sdhci-tegra.3/by-num/p11
./platform/sdhci-tegra.3/by-num/p10
./platform/sdhci-tegra.3/by-num/p9
./platform/sdhci-tegra.3/by-num/p8
./platform/sdhci-tegra.3/by-num/p7
./platform/sdhci-tegra.3/by-num/p6
./platform/sdhci-tegra.3/by-num/p5
./platform/sdhci-tegra.3/by-num/p4
./platform/sdhci-tegra.3/by-num/p3
./platform/sdhci-tegra.3/by-num/p2
./platform/sdhci-tegra.3/by-num/p1
./platform/sdhci-tegra.3/by-name
./platform/sdhci-tegra.3/mmcblk0
./mmcblk0
Unfortunatelly:
# dd if=/dev/block/recovery of=/sdcard/recovery.img
dd if=/dev/block/recovery of=/sdcard/recovery.img
/dev/block/recovery: cannot open for read: No such file or directory
Ah, some devices have a "recovery" symlink and others don't. Process of elimation it is.
Try typing "mount", or "cat /proc/mounts". This will list all currently mounted filesystems and which block devices are mounted. That way we can eliminate which block devices *aren't* the recovery partition.
For the record, in case this wasn't clear, I don't own a Tablet S and have never actually physically touched one. Otherwise I'd just do it myself. ;-)
10 bucks USD pledged from me
djrbliss said:
Ah, some devices have a "recovery" symlink and others don't. Process of elimation it is.
Try typing "mount", or "cat /proc/mounts". This will list all currently mounted filesystems and which block devices are mounted. That way we can eliminate which block devices *aren't* the recovery partition.
For the record, in case this wasn't clear, I don't own a Tablet S and have never actually physically touched one. Otherwise I'd just do it myself. ;-)
Click to expand...
Click to collapse
if you need djrbliss i mounted QuickSSHD on my tablet!!!
10 usd from me.
djrbliss said:
Ah, some devices have a "recovery" symlink and others don't. Process of elimation it is.
Try typing "mount", or "cat /proc/mounts". This will list all currently mounted filesystems and which block devices are mounted. That way we can eliminate which block devices *aren't* the recovery partition.
For the record, in case this wasn't clear, I don't own a Tablet S and have never actually physically touched one. Otherwise I'd just do it myself. ;-)
Click to expand...
Click to collapse
Let me know if you want to set TeamViewer session with me.
This way we can work out whatever is possible.
Just the output of the following commands will be fine:
adb shell "ls -l /dev/block"
adb shell "cat /proc/mounts"
djrbliss said:
Just the output of the following commands will be fine:
adb shell "ls -l /dev/block"
adb shell "cat /proc/mounts"
Click to expand...
Click to collapse
adb shell "ls -l /dev/block"
Code:
brw------- root root 254, 0 2012-02-09 00:21 dm-0
brw------- root root 254, 1 2012-02-09 00:21 dm-1
brw------- root root 254, 2 2012-02-09 00:21 dm-2
brw------- root root 7, 0 2012-02-09 00:20 loop0
brw------- root root 7, 1 2012-02-09 00:20 loop1
brw------- root root 7, 2 2012-02-09 00:20 loop2
brw------- root root 7, 3 2012-02-09 00:20 loop3
brw------- root root 7, 4 2012-02-09 00:20 loop4
brw------- root root 7, 5 2012-02-09 00:20 loop5
brw------- root root 7, 6 2012-02-09 00:20 loop6
brw------- root root 7, 7 2012-02-09 00:20 loop7
brw------- root root 179, 0 2012-02-09 00:20 mmcblk0
brw------- root root 179, 1 2012-02-09 00:20 mmcblk0p1
brw------- root root 179, 10 2012-02-09 00:20 mmcblk0p10
brw------- root root 179, 11 2012-02-09 00:20 mmcblk0p11
brw------- root root 179, 2 2012-02-09 00:20 mmcblk0p2
brw------- root root 179, 3 2012-02-09 00:20 mmcblk0p3
brw------- root root 179, 4 2012-02-09 00:20 mmcblk0p4
brw-rw---- root system 179, 5 2012-02-09 00:20 mmcblk0p5
brw------- root root 179, 6 2012-02-09 00:20 mmcblk0p6
brw-rw---- root system 179, 7 2012-02-09 00:20 mmcblk0p7
brw------- root root 179, 8 2012-02-09 00:20 mmcblk0p8
brw------- root root 179, 9 2012-02-09 00:20 mmcblk0p9
drwxr-xr-x root root 2012-02-09 00:20 platform
drwxr-xr-x root root 2012-02-09 00:20 svold
drwxr-xr-x root root 2012-02-09 00:20 vold
adb shell "cat /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/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=iso
8859-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,iocharse
t=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.halfbrick.ageofzombies-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.jakyl.spirithd-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixe
d,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.playcreek.DeathWorm-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
Here is my config...
Android version 3.2.1
Kernel version 2.6.36.3 [email protected] #1
Build number THMAS0182400
# mount
Code:
# 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
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.outfit7.talkingginapro-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.jakyl.tilestormhd-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-2 /mnt/asec/com.outfit7.talkingbenpro-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-3 /mnt/asec/com.quoord.tapatalkxdapre.activity-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-4 /mnt/asec/com.outfit7.talkingtom2-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-5 /mnt/asec/com.outfit7.talkingroby-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-6 /mnt/asec/com.eamobile.tetris_eu-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-7 /mnt/asec/com.outfit7.talkingtompro-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-8 /mnt/asec/com.fullfat.android.flickgolf-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
# cat /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.outfit7.talkingginapro-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.jakyl.tilestormhd-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-2 /mnt/asec/com.outfit7.talkingbenpro-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-3 /mnt/asec/com.quoord.tapatalkxdapre.activity-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-4 /mnt/asec/com.outfit7.talkingtom2-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-5 /mnt/asec/com.outfit7.talkingroby-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-6 /mnt/asec/com.eamobile.tetris_eu-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-7 /mnt/asec/com.outfit7.talkingtompro-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-8 /mnt/asec/com.fullfat.android.flickgolf-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
# ls -l /dev/block
Code:
brw------- root root 254, 0 2012-02-09 22:46 dm-0
brw------- root root 254, 1 2012-02-09 22:46 dm-1
brw------- root root 254, 2 2012-02-09 22:46 dm-2
brw------- root root 254, 3 2012-02-09 22:46 dm-3
brw------- root root 254, 4 2012-02-09 22:46 dm-4
brw------- root root 254, 5 2012-02-09 22:46 dm-5
brw------- root root 254, 6 2012-02-09 22:46 dm-6
brw------- root root 254, 7 2012-02-09 22:46 dm-7
brw------- root root 254, 8 2012-02-09 22:46 dm-8
brw------- root root 7, 0 2012-02-09 22:45 loop0
brw------- root root 7, 1 2012-02-09 22:45 loop1
brw------- root root 7, 2 2012-02-09 22:45 loop2
brw------- root root 7, 3 2012-02-09 22:45 loop3
brw------- root root 7, 4 2012-02-09 22:45 loop4
brw------- root root 7, 5 2012-02-09 22:45 loop5
brw------- root root 7, 6 2012-02-09 22:45 loop6
brw------- root root 7, 7 2012-02-09 22:45 loop7
brw-rw---- root root 7, 8 2012-02-09 22:46 loop8
brw------- root root 179, 0 2012-02-09 22:45 mmcblk0
brw------- root root 179, 1 2012-02-09 22:45 mmcblk0p1
brw------- root root 179, 10 2012-02-09 22:45 mmcblk0p10
brw------- root root 179, 11 2012-02-09 22:45 mmcblk0p11
brw------- root root 179, 2 2012-02-09 22:45 mmcblk0p2
brw------- root root 179, 3 2012-02-09 22:45 mmcblk0p3
brw------- root root 179, 4 2012-02-09 22:45 mmcblk0p4
brw-rw---- root system 179, 5 2012-02-09 22:45 mmcblk0p5
brw------- root root 179, 6 2012-02-09 22:45 mmcblk0p6
brw-rw---- root system 179, 7 2012-02-09 22:45 mmcblk0p7
brw------- root root 179, 8 2012-02-09 22:45 mmcblk0p8
brw------- root root 179, 9 2012-02-09 22:45 mmcblk0p9
brw------- root root 179, 16 2012-02-09 22:45 mmcblk1
brw------- root root 179, 17 2012-02-09 22:45 mmcblk1p1
drwxr-xr-x root root 2012-02-09 22:45 platform
drwxr-xr-x root root 2012-02-09 22:45 svold
drwxr-xr-x root root 2012-02-09 22:45 vold
#
---------- Post added at 09:06 AM ---------- Previous post was at 09:02 AM ----------
I'll give 25 $ if we can have custom recovery and roms...
Just made the much deserved contribution to djrbliss, now onto the next bounty!
Put me down for $20!
Seeing as there haven't been any recent pledges/developments, I want to reiterate (and bring new attention) this topic pledge and focus. Even if the method is simple (and was available to us right from the beginning), the person who will first discover a way to install custom recoveries and ROMs will get the amount above. If it is simple, this is one more reason to get on with this! Let's hope some more pledges come our way. Root was important, but here is where things get really important -- after all if the Sony ICS update blocks Root and our current exploit, then we will be virtually left with the choice of staying in 3.2 or losing what we've gained.
Let's see some more support for this topic!
I'm getting custom ROM withdrawal...... ROFL
(thats what happens when your first droid was a nexus)
grcd said:
Seeing as there haven't been any recent pledges/developments, I want to reiterate (and bring new attention) this topic pledge and focus. Even if the method is simple (and was available to us right from the beginning), the person who will first discover a way to install custom recoveries and ROMs will get the amount above. If it is simple, this is one more reason to get on with this! Let's hope some more pledges come our way. Root was important, but here is where things get really important -- after all if the Sony ICS update blocks Root and our current exploit, then we will be virtually left with the choice of staying in 3.2 or losing what we've gained.
Let's see some more support for this topic!
Click to expand...
Click to collapse
Custom recovery was in the works as well as init.d scripts. However, I broke the device and am now having a difficult time getting my new tab to be recognized by adb and rooted. Hoping updating it will fix that. If so, I have a modded 3e recovey nearly working. As for the bootloaders, we need a kernel DEV...lol... I have sent a shot out to some kernel DEVs and am hoping for some help from them...
thomas.raines said:
Custom recovery was in the works as well as init.d scripts. However, I broke the device and am now having a difficult time getting my new tab to be recognized by adb and rooted. Hoping updating it will fix that. If so, I have a modded 3e recovey nearly working. As for the bootloaders, we need a kernel DEV...lol... I have sent a shot out to some kernel DEVs and am hoping for some help from them...
Click to expand...
Click to collapse
That's certainly good news. I will be looking forward to this. If two devs participate for the bounty, I will be happy to come to a solution in order to split the reward between them. Perhaps I can assign people into two different teams who will give bounties to each person separately.

676.999.999 [ICS Dummy update] for 676.226.3.XT910.Retail.en.EU

Interesting update found from cheesecaking on the build.prop 676.226.3.XT910.Retail.en.EU. It has an upgrade to the cdt.bin so it may not be fastbootable from back to .33....
It is still 4.0.4 by looking at the updater-script.
http://crackflasher.com/dev/mattlgr...Blur_Version.676.226.3.XT910.Retail.en.EU.zip
Might as well post it, feel free to flash at your own risk, I sure am not though.
mattlgroff said:
Interesting update found from cheesecaking on the build.prop 676.226.3.XT910.Retail.en.EU. It has an upgrade to the cdt.bin so it may not be fastbootable from back to .33....
It is still 4.0.4 by looking at the updater-script.
http://crackflasher.com/dev/mattlgr...Blur_Version.676.226.3.XT910.Retail.en.EU.zip
Might as well post it, feel free to flash at your own risk, I sure am not though.
Click to expand...
Click to collapse
Thanks.. Will look into it & extract usable stuff
Update :
the new cdt.bin will remove webtop partition. Not good for those using my dual boot solution (BootMenu).
The main secure version is not upgraded, so it can be downgrade back to .33 cdt.bin. It's not a big problem now.
Not sure how it will be in official release though, but this is an early signed that Moto will removed the abandon webtop partition in future.
or maybe this file is for their internal use.(development unit) because this new cdt.bin also remove emstorage partitition.
post-build=RTGB/XT910_RTGB/umts_spyder:4.0.4/6.7.6_ICS_DUMMY/1341969974:user/release-keys
post-timestamp=1341967314
pre-build=RTGB/XT910_RTGB/umts_spyder:4.0.4/6.7.6-226_SPU-DE-TA-2/1340775289:user/release-keys
pre-device=umts_spyder
Click to expand...
Click to collapse
It's hard for an badass Crackflasher, not to try this. But if it will remove the Webtop Partition, it's not worth it.
The Fastboot ICS got no webtop in it, so there's no way to get this Partition back, right?
Gesendet von meinem XT910 mit Tapatalk 2
.33 cdt.bin still has webtop in its partition table.
But where did they relocate the space?
HSD-Pilot said:
It's hard for an badass Crackflasher, not to try this. But if it will remove the Webtop Partition, it's not worth it.
The Fastboot ICS got no webtop in it, so there's no way to get this Partition back, right?
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
If you fastboot back and restore someone's extracted webtop.img it should work fine... in theory?
I will try to patch whole system tmr and c if theres anything new on framework and app. (or something we could use without new cdt.bin)
I would try patch kernel as well but i won't test it on my phone(i dont rly like to mess with my cid)
Enviado desde mi XT910 usando Tapatalk 2
My Cid is dead already XD...should be an warning to myself not to try anything...
Gesendet von meinem XT910 mit Tapatalk 2
HSD-Pilot said:
The Fastboot ICS got no webtop in it, so there's no way to get this Partition back, right?
Click to expand...
Click to collapse
cdt.bin is like a partition table in PC.
farhanito said:
But where did they relocate the space?
Click to expand...
Click to collapse
the removed webtop partition space is assign to userdata (/data). You got a big data partition with this cdt.bin.
If this is happening, we'll multi-boot from userdata partition. It's a good thing, it solve the 2nd-system size limitation.
leisures said:
I would try patch kernel as well but i won't test it on my phone(i dont rly like to mess with my cid)
Click to expand...
Click to collapse
upgrading kernel like this is safe
Code:
fastboot flash boot ics_dummy.img
if it failed verification, jut flash again with previous flash-able version
i don't dual boot so there shouldn't be any reason not to flash this? :fingers-crossed:
Thanks for the leaks matt!
tomow said:
i don't dual boot so there shouldn't be any reason not to flash this? :fingers-crossed:
Thanks for the leaks matt!
Click to expand...
Click to collapse
You got my OK, so run Forest, run
Gesendet von meinem XT910 mit Tapatalk 2
tomow said:
i don't dual boot so there shouldn't be any reason not to flash this? :fingers-crossed:
Thanks for the leaks matt!
Click to expand...
Click to collapse
It's your phone, it's up to you. we have nothing to do with it. Just sharing info here
whirleyes said:
It's your phone, it's up to you. we have nothing to do with it. Just sharing info here
Click to expand...
Click to collapse
Thanks for the insight whirleyes, it seems like I found an interesting update here...
Hello just a request. Can someone make a tutorial for users like me who dualbooted or used the 2nd system to flash this new update?
Sent from my XT910 using xda premium
Thought by the file size that this was an update like 676 was. Wiped my whole system instead that's all my fault though. Runs very nicely though
tomow said:
Thought by the file size that this was an update like 676 was. Wiped my whole system instead that's all my fault though. Runs very nicely though
Click to expand...
Click to collapse
Can you share the output of these command (using adb)
Code:
adb shell mount
Code:
adb shell ls -la /dev/block/
Code:
adb shell df
Can you post an Screenshot of the Info (Baseband, Builddate and stuff)
Gesendet von meinem XT910 mit Tapatalk 2
thanks matt.
@Whirleyes
If they remove webtop partition, you said we'll dual boot from data partition. Does that mean that both system will use same data? Or different data on same partition?
i wonder if this update really update system or if it just a dummy to try the partition switching.
adb shell mount
C:\Android\platform-tools>adb shell 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/system /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/pds /pds ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barr
ier=1,data=ordered 0 0
/dev/block/preinstall /preinstall ext3 rw,nosuid,nodev,noatime,nodiratime,errors
=continue,barrier=1,data=ordered 0 0
/dev/block/userdata /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continu
e,barrier=1,data=ordered 0 0
/dev/block/cache /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,
barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,d
efault_permissions,allow_other 0 0
/dev/block/vold/179:97 /mnt/sdcard-ext vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
C:\Android\platform-tools>adb shell ls -la /dev/block/
lrwxrwxrwx root root 2012-07-17 07:47 boot -> /dev/block/mmcblk
1p14
lrwxrwxrwx root root 2012-07-17 07:47 cache -> /dev/block/mmcbl
k1p21
lrwxrwxrwx root root 2012-07-17 07:47 cdrom -> /dev/block/mmcbl
k1p16
lrwxrwxrwx root root 2012-07-17 07:47 cid -> /dev/block/mmcblk1
p18
lrwxrwxrwx root root 2012-07-17 07:47 kpanic -> /dev/block/mmcb
lk1p19
brw------- root root 7, 0 2012-07-17 07:47 loop0
brw------- root root 7, 1 2012-07-17 07:47 loop1
brw------- root root 7, 2 2012-07-17 07:47 loop2
brw------- root root 7, 3 2012-07-17 07:47 loop3
brw------- root root 7, 4 2012-07-17 07:47 loop4
brw------- root root 7, 5 2012-07-17 07:47 loop5
brw------- root root 7, 6 2012-07-17 07:47 loop6
brw------- root root 7, 7 2012-07-17 07:47 loop7
lrwxrwxrwx root root 2012-07-17 07:47 misc -> /dev/block/mmcblk
1p17
brw------- root root 179, 96 2012-07-17 07:47 mmcblk0
brw-rw---- root mot_tcmd 179, 97 2012-07-17 07:47 mmcblk0p1
brw------- root root 179, 0 2012-07-17 07:47 mmcblk1
brw------- root root 179, 32 2012-07-17 07:47 mmcblk1boot0
brw------- root root 179, 64 2012-07-17 07:47 mmcblk1boot1
brw-rw---- root mot_tcmd 179, 1 2012-07-17 07:47 mmcblk1p1
brw------- root root 179, 10 2012-07-17 07:47 mmcblk1p10
brw------- root root 179, 11 2012-07-17 07:47 mmcblk1p11
brw------- root root 179, 12 2012-07-17 07:47 mmcblk1p12
brw------- root root 179, 13 2012-07-17 07:47 mmcblk1p13
brw------- root root 179, 14 2012-07-17 07:47 mmcblk1p14
brw------- root root 179, 15 2012-07-17 07:47 mmcblk1p15
brw------- root root 179, 16 2012-07-17 07:47 mmcblk1p16
brw-rw---- root mot_tcmd 179, 17 2012-07-17 07:47 mmcblk1p17
brw-rw---- root mot_tcmd 179, 18 2012-07-17 07:47 mmcblk1p18
brw------- root root 179, 19 2012-07-17 07:47 mmcblk1p19
brw------- root root 179, 2 2012-07-17 07:47 mmcblk1p2
brw------- root root 179, 20 2012-07-17 07:47 mmcblk1p20
brw------- root root 179, 21 2012-07-17 07:47 mmcblk1p21
brw------- root root 179, 22 2012-07-17 07:47 mmcblk1p22
brw------- root root 179, 23 2012-07-17 07:47 mmcblk1p23
brw------- root root 179, 24 2012-07-17 07:47 mmcblk1p24
brw------- root root 179, 25 2012-07-17 07:47 mmcblk1p25
brw------- root root 179, 26 2012-07-17 07:47 mmcblk1p26
brw------- root root 179, 3 2012-07-17 07:47 mmcblk1p3
brw------- root root 179, 4 2012-07-17 07:47 mmcblk1p4
brw------- root root 179, 5 2012-07-17 07:47 mmcblk1p5
brw------- root root 179, 6 2012-07-17 07:47 mmcblk1p6
brw------- root root 179, 7 2012-07-17 07:47 mmcblk1p7
brw------- root root 179, 8 2012-07-17 07:47 mmcblk1p8
brw------- root root 179, 9 2012-07-17 07:47 mmcblk1p9
lrwxrwxrwx root root 2012-07-17 07:47 pds -> /dev/block/mmcblk1
p7
drwxr-xr-x root root 2012-07-17 07:47 platform
lrwxrwxrwx root root 2012-07-17 07:47 preinstall -> /dev/block/
mmcblk1p22
brw------- root root 1, 0 2012-07-17 07:47 ram0
brw------- root root 1, 1 2012-07-17 07:47 ram1
brw------- root root 1, 10 2012-07-17 07:47 ram10
brw------- root root 1, 11 2012-07-17 07:47 ram11
brw------- root root 1, 12 2012-07-17 07:47 ram12
brw------- root root 1, 13 2012-07-17 07:47 ram13
brw------- root root 1, 14 2012-07-17 07:47 ram14
brw------- root root 1, 15 2012-07-17 07:47 ram15
brw------- root root 1, 2 2012-07-17 07:47 ram2
brw------- root root 1, 3 2012-07-17 07:47 ram3
brw------- root root 1, 4 2012-07-17 07:47 ram4
brw------- root root 1, 5 2012-07-17 07:47 ram5
brw------- root root 1, 6 2012-07-17 07:47 ram6
brw------- root root 1, 7 2012-07-17 07:47 ram7
brw------- root root 1, 8 2012-07-17 07:47 ram8
brw------- root root 1, 9 2012-07-17 07:47 ram9
lrwxrwxrwx root root 2012-07-17 07:47 recovery -> /dev/block/mm
cblk1p15
lrwxrwxrwx root root 2012-07-17 07:47 system -> /dev/block/mmcb
lk1p20
lrwxrwxrwx root root 2012-07-17 07:47 userdata -> /dev/block/mm
cblk1p23
lrwxrwxrwx root root 2012-07-17 07:47 utags -> /dev/block/mmcbl
k1p8
drwxr-xr-x root root 2012-07-17 07:47 vold
brw------- root root 253, 0 2012-07-17 07:47 zram0
C:\Android\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 420M 76K 420M 4096
/mnt/asec 420M 0K 420M 4096
/mnt/obb 420M 0K 420M 4096
/system 770M 751M 19M 1024
/pds 3M 1M 2M 1024
/preinstall 8M 3M 5M 1024
/data 1G 786M 524M 2048
/cache 708M 16M 691M 4096
/mnt/sdcard 1G 786M 524M 2048
/mnt/sdcard-ext 14G 8G 6G 8192
C:\Android\platform-tools>
sevenup30 said:
thanks matt.
@Whirleyes
If they remove webtop partition, you said we'll dual boot from data partition. Does that mean that both system will use same data? Or different data on same partition?
i wonder if this update really update system or if it just a dummy to try the partition switching.
Click to expand...
Click to collapse
Opps... the /data partition didn't grow.
the /mnt/sdcard-ext (fat) grow to 14GB?
thanks HSD-Pilot
But sdcard-ext doesn't count, right?
He's using 16Gb microsd
/mnt/sdcard is shrunk to 1Gb?

[Q] Create full backup and restore it

Hi,
i rooted my T15A tablet with "Root_with_Restore_by_Bin4ry_v17" tool and then installed/flased "SuperCharger_Starter_Kit_RC12". After the flash my internal storage shows up with 0 byte and i am not able to install any app. A factory reset did not help too.
I´ve got another original T15A tablet and want to create a full backup of this and flash it to the bricked one.
I found some guides on how to create a backup by connecting to an adb shell. This guides are all device specific and i now dont know
what to backup under /dev/blocks/ ....
- Any idear/guide how to do a full backup / restore?
- Maybe we just can fix the 0 byte error (but i didnt find generic solution about that)
Code:
[email protected]:/ # ls -al /dev/block/
ls -al /dev/block/
brw------- root root 7, 0 2012-12-04 22:12 loop0
brw------- root root 7, 1 2012-12-04 22:12 loop1
brw------- root root 7, 2 2012-12-04 22:12 loop2
brw------- root root 7, 3 2012-12-04 22:12 loop3
brw------- root root 7, 4 2012-12-04 22:12 loop4
brw------- root root 7, 5 2012-12-04 22:12 loop5
brw------- root root 7, 6 2012-12-04 22:12 loop6
brw------- root root 7, 7 2012-12-04 22:12 loop7
brw------- root root 93, 0 2012-12-04 22:12 nanda
brw------- root root 93, 8 2012-12-04 22:12 nandb
brw------- root root 93, 16 2012-12-04 22:12 nandc
brw------- root root 93, 24 2012-12-04 22:12 nandd
brw------- root root 93, 32 2012-12-04 22:12 nande
brw-rw-rw- system system 93, 40 2012-12-04 22:12 nandf
brw------- root root 93, 48 2012-12-04 22:12 nandg
brw------- root root 93, 56 2012-12-04 22:12 nandh
brw------- root root 93, 64 2012-12-04 22:12 nandi
brw------- root root 93, 72 2012-12-04 22:12 nandj
brw------- root root 1, 0 2012-12-04 22:12 ram0
brw------- root root 1, 1 2012-12-04 22:12 ram1
drwxr-xr-x root root 2012-12-04 22:12 vold
[email protected]:/ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 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
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/vold/93:72 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:72 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
*bump* (is this allowed here?)
Solved, after opening the tablets back cover and searching for the mainboard model i found out that the generic "T15A" tablet uses the same covers and the same mainboard than the goclever.com tablets. So i used the goclever stock rom and flashed it, works quite nice now.
Mod, please close.

Lost recovery mode after resizing system partitions

Hi everyone,
I was trying to flash a nightly update from cyanogen and was getting the error : CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system and so, troubleshooting the problem, I tried to extend the system partitions through the procedure I found in a thread that contained the code down bellow and I believe that was after that that I lost my recoverymode. After this I tried do full wipe and flash an earlier ROM to see if I could get the phone back and that was the last time I was able to enter in the recoverymode. Now I just have a black screen and also when I try to start my phone it took about 2 min on a black screen and then the OS starts. Besides that, all network connectivity was lost (wifi, call signal, 4g/3g) and user space-sdcard (/data partition) too (althoug it seems to be mounted). It appears that was all disabled. Without a recovery mode and internet I am completely stuck. I tried to install a cwm and a twrp through adb after install flash gordon and flashify apk but it did not worked since it cannot recognize a file inside my /data . And the idea I had to restore from rommanager apk failed in the moment it tried to connect on internet to download content.
Please help!! Follow details:
LG_E975
I did a full wipe partition / cache/ dalvik
cyanogemMod version: 11-20141115-SNAPSHOT-M12-E975
android : 4.4.4.
kernel version: 3.4.0-CM+
Code I found and ran when trying to solve CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
fi
Output from df command:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 905.8M 128.0K 905.6M 4096
/sys/fs/cgroup 905.8M 12.0K 905.8M 4096
/mnt/asec 905.8M 0.0K 905.8M 4096
/mnt/obb 905.8M 0.0K 905.8M 4096
/mnt/fuse 905.8M 0.0K 905.8M 4096
/system 1.5G 401.3M 1.1G 4096
/cache 788.4M 14.4M 774.0M 4096
/data 25.0G 271.0M 24.8G 4096
[email protected]:/ $
Output from /proc/partitions
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Output from /dev/block directory :
Code:
[email protected]:/dev/block $ ls -l
ls -l
brw------- root root 7, 0 1970-01-02 12:07 loop0
brw------- root root 7, 1 1970-01-02 12:07 loop1
brw------- root root 7, 2 1970-01-02 12:07 loop2
brw------- root root 7, 3 1970-01-02 12:07 loop3
brw------- root root 7, 4 1970-01-02 12:07 loop4
brw------- root root 7, 5 1970-01-02 12:07 loop5
brw------- root root 7, 6 1970-01-02 12:07 loop6
brw------- root root 7, 7 1970-01-02 12:07 loop7
brw------- root root 179, 0 1970-01-02 12:07 mmcblk0
brw------- root root 179, 1 1970-01-02 12:07 mmcblk0p1
brw------- root root 179, 10 1970-01-02 12:07 mmcblk0p10
brw------- root root 179, 11 1970-01-02 12:07 mmcblk0p11
brw-rw---- system system 179, 12 1970-01-02 12:07 mmcblk0p12
brw-rw---- system system 179, 13 1970-01-02 12:07 mmcblk0p13
brw-rw---- system system 179, 14 1970-01-02 12:07 mmcblk0p14
brw------- root root 179, 15 1970-01-02 12:07 mmcblk0p15
brw------- root root 179, 16 1970-01-02 12:07 mmcblk0p16
brw------- root root 179, 17 1970-01-02 12:07 mmcblk0p17
brw-rw---- root system 179, 18 1970-01-02 12:07 mmcblk0p18
brw------- root root 179, 19 1970-01-02 12:07 mmcblk0p19
brw------- root root 179, 2 1970-01-02 12:07 mmcblk0p2
brw------- root root 179, 20 1970-01-02 12:07 mmcblk0p20
brw------- root root 179, 21 1970-01-02 12:07 mmcblk0p21
brw------- root root 179, 22 1970-01-02 12:07 mmcblk0p22
brw------- root root 179, 23 1970-01-02 12:07 mmcblk0p23
brw------- root root 179, 24 1970-01-02 12:07 mmcblk0p24
brw------- root root 179, 27 1970-01-02 12:07 mmcblk0p27
brw------- root root 179, 28 1970-01-02 12:07 mmcblk0p28
brw------- root root 179, 29 1970-01-02 12:07 mmcblk0p29
brw------- root root 179, 3 1970-01-02 12:07 mmcblk0p3
brw------- root root 179, 30 1970-01-02 12:07 mmcblk0p30
brw------- root root 179, 31 1970-01-02 12:07 mmcblk0p31
brw------- root root 259, 0 1970-01-02 12:07 mmcblk0p32
brw------- root root 259, 1 1970-01-02 12:07 mmcblk0p33
brw------- root root 259, 2 1970-01-02 12:07 mmcblk0p34
brw------- root root 259, 3 1970-01-02 12:07 mmcblk0p35
brw------- root root 179, 4 1970-01-02 12:07 mmcblk0p4
brw------- root root 179, 5 1970-01-02 12:07 mmcblk0p5
brw------- root root 179, 6 1970-01-02 12:07 mmcblk0p6
brw------- root root 179, 7 1970-01-02 12:07 mmcblk0p7
brw-rw---- system system 179, 8 1970-01-02 12:07 mmcblk0p8
brw-rw---- system system 179, 9 1970-01-02 12:07 mmcblk0p9
drwxr-xr-x root root 1970-01-02 12:07 platform
brw------- root root 1, 0 1970-01-02 12:07 ram0
brw------- root root 1, 1 1970-01-02 12:07 ram1
brw------- root root 1, 10 1970-01-02 12:07 ram10
brw------- root root 1, 11 1970-01-02 12:07 ram11
brw------- root root 1, 12 1970-01-02 12:07 ram12
brw------- root root 1, 13 1970-01-02 12:07 ram13
brw------- root root 1, 14 1970-01-02 12:07 ram14
brw------- root root 1, 15 1970-01-02 12:07 ram15
brw------- root root 1, 2 1970-01-02 12:07 ram2
brw------- root root 1, 3 1970-01-02 12:07 ram3
brw------- root root 1, 4 1970-01-02 12:07 ram4
brw------- root root 1, 5 1970-01-02 12:07 ram5
brw------- root root 1, 6 1970-01-02 12:07 ram6
brw------- root root 1, 7 1970-01-02 12:07 ram7
brw------- root root 1, 8 1970-01-02 12:07 ram8
brw------- root root 1, 9 1970-01-02 12:07 ram9
drwx------ root root 1970-01-02 12:09 vold
[email protected]:/dev/block $
Output from cat /proc/mounts :
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,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
debugfs /sys/kernel/debug debugfs 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
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,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,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $

Categories

Resources