[Q] Create full backup and restore it - Android Q&A, Help & Troubleshooting

[Q] Create full backup and restore it - Android Q&A, Help & Troubleshooting

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.

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.

[Q] Overmax Quattor 10+ flashing custom rom / recovery

Hi,
I bought an Overmax Quattor 10+ tablet and I would like to flash a new recovery with touch screen support (has no volume buttons) to it then later install a custom rom.
However I can't find any information about this tablet anywhere, I would like to know if anyone knows anything about this device.
Note that this is my first android device ever, and I bought it 3 days ago.
I ask for any kind of help you can give me with this tablet, pointing me to the right direction.
Thank your very much.
Please continue reading below where I detail what I did so far.
This is the tablet: I'm new so I can't post links.
Information I know so far about the device
Hardware
CPU: Allwinner A31
RAM: 1GB - 7XXMB usable
Internal memory is actually an sdcard, at least it shows up as one. When I put in an sdcard it mounts it into /mnt/extsd, while /mnt/sdcard is the internal storage.
The tablet has no volume buttons, only power and home buttons.
OTG and usb host mode.
Software
Code:
Android version 4.2.2
Firmware version v3.2
Kernel
Code:
3.3.0
[email protected] #64
Thu Aug 1 14:58:11 HKT 2013
Build
Code:
fiber_a31st-eng 4.2.2 JDQ39 20130807
What I was able to do so far
I was able to root it following this guide: I'm new so I can't post links. I followed guide on f-droid wiki.
TL;DR
1. adb shell gives root
2. i push su with adb
3. change permissions
4. with installed superuser i have root
I tested my root using root checker app and with a terminal emulator which gives me the root prompt after using su.
Got adb to work
The google usb driver didn't work on my windows desktop. However windows update found Alcatel drivers which worked.
When I boot into recovery then I the device reports itself differently. In window's device manager it changes from Alcatel Android to OV-10+, however forcing the use of the Alcatel driver enables adb to see the device.
Problems
I can't find anything about this tablet.
Has no volume buttons, only power and home buttons. Which makes recovery unusable.
adb shell doesn't work in recovery. "- exec '/system/bin/sh' failed: No such file or directory (2) -"
I tried rom manager apps from google play which could install both custom roms and custom recoveries without luck. So nothing supports it as far as I know.
Some thoughts / facts
I bought this tablet in a store in hungary.
It was made in china, but I didn't order it from china.
More information, anything I think can be useful
I don't know how much useful are these thing I come from a linux past, but I don't know much about android's internal structure.
Everyting here is without external sdcard inserted.
It uses Alcatel android drivers on windows(installed by windows update). Google usb driver doesn't recognizes the device.
Dmesg from linux (ubuntu 13.10) when I connect it
Normal
Code:
usb 3-2: new high-speed USB device number 2 using xhci_hcd
usb 3-2: New USB device found, idVendor=18d1, idProduct=0003
usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 3-2: Product: Android
usb 3-2: Manufacturer: USB Developer
usb 3-2: SerialNumber: 20080411
Recovery
Code:
usb 3-2: USB disconnect, device number 4
usb 3-2: new high-speed USB device number 5 using xhci_hcd
usb 3-2: New USB device found, idVendor=18d1, idProduct=d001
usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
usb 3-2: Product: OV-Quattor
usb 3-2: Manufacturer: unknown
usb 3-2: SerialNumber: 20080411
Info about installed (stock) recovery
Code:
Android system recovery <3e>
Android sdk reversion:exdroid4.2.2_r1-a31-v3.2
adb shell mount
Code:
rootfs / rootfs rw 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
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 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
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,nomblk_io_submit,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=continue 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=continue 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
adb shell cat /proc/cpuinfo
Code:
Processor : ARMv7 Processor rev 3 (v7l)
processor : 0
BogoMIPS : 2013.59
processor : 1
BogoMIPS : 2013.59
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xc07
CPU revision : 3
Hardware : sun6i
Revision : 0000
Revision : a320
adb shell ls /dev
Code:
alarm
android_adb
ashmem
aw_i2c_ts1
binder
block
bus
cachefiles
cedar_dev
console
cpu_dma_latency
cpuctl
cuse
device-mapper
disp
full
fuse
g2d
graphics
hdmi
input
ion
kmem
kmsg
lcd
log
loop-control
mem
mtp_usb
network_latency
network_throughput
null
ppp
psaux
ptmx
pts
ptyp0
ptyp1
ptyp2
ptyp3
ptyp4
ptyp5
ptyp6
ptyp7
ptyp8
ptyp9
ptypa
ptypb
ptypc
ptypd
ptype
ptypf
pvr_sync
pvrsrvkm
random
rfkill
rtc0
snd
socket
sunxi-reg
sunxi_hw
sunxi_mem
sw_sync
tty
tty0
tty1
tty10
tty11
tty12
tty13
tty14
tty15
tty16
tty17
tty18
tty19
tty2
tty20
tty21
tty22
tty23
tty24
tty25
tty26
tty27
tty28
tty29
tty3
tty30
tty31
tty32
tty33
tty34
tty35
tty36
tty37
tty38
tty39
tty4
tty40
tty41
tty42
tty43
tty44
tty45
tty46
tty47
tty48
tty49
tty5
tty50
tty51
tty52
tty53
tty54
tty55
tty56
tty57
tty58
tty59
tty6
tty60
tty61
tty62
tty63
tty7
tty8
tty9
ttyGS0
ttyGS1
ttyGS2
ttyGS3
ttyS0
ttyS2
ttyp0
ttyp1
ttyp2
ttyp3
ttyp4
ttyp5
ttyp6
ttyp7
ttyp8
ttyp9
ttypa
ttypb
ttypc
ttypd
ttype
ttypf
tun
uinput
urandom
usb_accessory
vcs
vcs1
vcsa
vcsa1
video1
xt_qtaguid
zero
Code:
[email protected]:/ # cat fstab.sun6i
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/nandd /system ext4 ro wait
/dev/block/nandh /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
#/dev/block/nandi /databk ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/nande /data ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check,encryptable=/dev/block/nandi
Code:
[email protected]:/dev/block # ls -l
brw------- root root 7, 0 2013-12-21 14:40 loop0
brw------- root root 7, 1 2013-12-21 14:40 loop1
brw------- root root 7, 2 2013-12-21 14:40 loop2
brw------- root root 7, 3 2013-12-21 14:40 loop3
brw------- root root 7, 4 2013-12-21 14:40 loop4
brw------- root root 7, 5 2013-12-21 14:40 loop5
brw------- root root 7, 6 2013-12-21 14:40 loop6
brw------- root root 7, 7 2013-12-21 14:40 loop7
brw------- root root 93, 0 2013-12-21 14:40 nanda
brw------- root root 93, 8 2013-12-21 14:40 nandb
brw------- root root 93, 16 2013-12-21 14:40 nandc
brw------- root root 93, 24 2013-12-21 14:40 nandd
brw------- root root 93, 32 2013-12-21 14:40 nande
brw-rw-rw- system system 93, 40 2013-12-21 14:40 nandf
brw------- root root 93, 48 2013-12-21 14:40 nandg
brw------- root root 93, 56 2013-12-21 14:40 nandh
brw------- root root 93, 64 2013-12-21 14:40 nandi
brw------- root root 93, 72 2013-12-21 14:40 nandj
drwx------ root root 2013-12-21 14:41 vold
Thank you very much for any help.

Data-Partition isn't there

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.

[Q] Request for rooting/modding orbsmart soundpad400 rk3028a

Hi,
I tried all root methods on the net but nothing worked.
Now I tried to add the su binary and the other files how it is described on the rockchipfirmware page.
But it didn't work either. Than I changed the boot.img to get write permission on the /system partition.
The permissions are now VERY unsafe, but nothing is working.
Info:
ro.build.description=rk3028a-user 4.4.4 KTU84P user.lucid.20141014.100831 release-keys
ro.com.google.gmsversion=4.4.4_r4
ro.product.version=1.0.3
Code:
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
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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/mtd/by-name/system /system ext4 rw,seclabel,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mtd/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mtd/by-name/metadata /metadata ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,noauto_da_alloc,discard 0 0
/dev/block/mtd/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,user_xattr,barrier=1,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,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.maxmpz.audioplayer.unlock-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/system:
drwxr-xr-x. 16 root root 4096 Jan 1 1970 ./
drwxr-x---+ 4 root root 4096 Mai 24 19:52 ../
drwxrwxrwx. 2 root root 4096 Mai 24 00:58 app/
drwxrwxrwx. 3 root 2000 4096 Mai 24 20:18 bin/
-rw-r--r--. 1 root root 3783 Dez 1 03:46 build.prop
drwxr-xr-x. 10 root root 4096 Dez 1 04:03 etc/
drwxr-xr-x. 2 root root 4096 Sep 30 2014 fonts/
drwxr-xr-x. 3 root root 4096 Sep 30 2014 framework/
drwxr-xr-x. 8 root root 8192 Dez 1 03:41 lib/
drwx------. 2 root root 4096 Jan 1 1970 lost+found/
drwxr-xr-x. 3 root root 4096 Dez 1 04:07 media/
drwxr-xr-x. 2 root root 4096 Okt 14 2014 preinstall/
drwxr-xr-x. 2 root root 4096 Okt 10 2014 priv-app/
drwxr-xr-x. 3 root root 4096 Sep 30 2014 tts/
drwxr-xr-x. 8 root root 4096 Sep 30 2014 usr/
drwxr-xr-x. 5 root 2000 4096 Sep 30 2014 vendor/
drwxrwxrwx. 2 root 2000 4096 Mai 23 23:28 xbin/
/system/bin(shorted)
drwxrwxrwx. 3 root 2000 4096 Mai 24 20:18 ./
drwxr-xr-x. 16 root root 4096 Jan 1 1970 ../
-rwsrwsrwt. 1 root 2000 1062992 Mai 24 20:18 busybox*
-rwsrwsrwt 1 root 2000 83 Mai 24 00:17 remount.sh* (self written script to remount /system in rw mode...did not work)
-rwsrwsrwt 1 root 2000 91980 Mai 24 20:18 su*
/system/xbin
drwxrwxrwx. 2 root 2000 4096 Mai 23 23:28 ./
drwxr-xr-x. 16 root root 4096 Jan 1 1970 ../
-rwsr-sr-x 1 root root 1062992 Mai 23 22:07 busybox*
-rwxr-xr-x 1 root root 104800 Mai 23 23:28 daemonsu*
-rwxr-xr-x. 1 root 2000 59748 Sep 30 2014 dexdump*
-rwxr-xr-x. 1 root 2000 9620 Sep 30 2014 io*
-rwsr-sr-x 1 root root 104800 Mai 23 23:27 su*
Do I have to do something else to get root access?
Thanks
Chrno219

Better Mobile App

welcome