Porting Clockwork Recovery To Tablets

[foxmotoracer23]

The issue is a few of you guys/girls tablet use ubifs as filesystem and I am not used to that, I do manually unpack yaffs2 images but thats usually the common use. UBIFS is quite different and so far I can mount some of the images on here and others I can not plus
I still haven't found a way to repack the images I modify.

It's not that its extremely difficult, its also partial the issue that I been busy with RL things (school/work)

I hear you with school starting back up for myself also. I would love to get recovery working and don't want to sound pushy but would you be able to write up a quick how to and I'm sure most of us here could start and try to create one for ourselves. If you feel that creating an how to would take too long I will just patently wait. I know real life things like school and work always take priority. Just let me know what you think. And either way Thank You for all your work and time on this project.

 

[betolley]

I have a FR-809 mx515.

It has a up/down switch on the side, a toggle power button on the side and a back button on the front.

When I run cat /proc/mtd I get no devices but I do for the partitions. Which will have the recovery. Recovery menu says version 3e when I go into it.

#cat /proc/mtd
dev: size erasesize name
#


cat /proc/partitions
major minor #blocks name

7 0 2111 loop0
7 1 18743 loop1
7 2 5229 loop2
7 3 16664 loop3
7 4 22901 loop4
7 5 6269 loop5
7 6 6269 loop6
7 7 2111 loop7
179 0 3872256 mmcblk0
179 1 3199572 mmcblk0p1
179 2 155062 mmcblk0p2
179 3 1 mmcblk0p3
179 4 7564 mmcblk0p4
179 5 310123 mmcblk0p5
179 6 155061 mmcblk0p6
179 8 1985024 mmcblk1
179 9 1984992 mmcblk1p1
254 0 2110 dm-0
254 1 18742 dm-1
254 2 5229 dm-2
254 3 16663 dm-3
254 4 22900 dm-4
254 5 6268 dm-5
254 6 6268 dm-6
254 7 2110 dm-7
#

 

[betolley]

Ok just found out recovery is in partition 4. The system uses uboot to boot like the nookcolor.

 

[betolley]

Could you help me with a clockworkmod recovery file for my tablet. It uses ext4 for the system partitions. It does not use a standard recovery image.

/dev/block/mmcblk0p1 /disk ext4 <This is the built in mmc that is available to the user to store files Not good to use to mount because you have to open to copy files to it.
/dev/block/mmcblk0p2 /system ext4
/dev/block/mmcblk0p4 /recovery ext4
/dev/block/mmcblk0p5 /data ext4
/dev/block/mmcblk0p6 /cache ext4
/dev/block/mmcblk1p1 /sdcard ext4 <This is the external mmc that is available to the user to store files. It would be great to use this to mount with.


This is the key codes and what would work great for control
key 28 MENU ->UP
key 158 HOME ->Down
key 139 BACK ->Select


I have tried to compile myself and can't get it to work. I just need the recovery file that would go in the image. Not the recovery image itself. I can mount the ext4 file and add the file myself.

 

[Biotic]

I've found the nook color clockwork recovery to boot and function with the flytouch2 or wowpad but it doesn't mount anything properly
Just modifying that nookcolor img is all we wowpad users need. Can you work with that one? All we need is mount fixes. Can't be to hard since everythings already there

 

[giveen]

Razor,
if you had the source code for the device would that help at all? I've been in contact with the producers of the Slyvnia and they told me they should get to the source code to me as soon as the managers approve it.

 

[ImagineThat]

mtd2 is definitly the recovery partition on the SYNET7LP.

Razor - I understand you're busy, so perhaps could you give as a brain dump as to where you were at if you started looking at the Sylvania SNET7LP? Is it one with a UBIFS or other file system that you're having problems extracting?

 

[giveen]

https://docs.google.com/leaf?id=0B0...IwZWEtNzIxY2NjMGVhNGY4&hl=en&authkey=CI-4loEF

Recovery.img for the Sylvania. I checked with a hex editor and there appears to be data inside.

 

[ImagineThat]

https://docs.google.com/leaf?id=0B0...IwZWEtNzIxY2NjMGVhNGY4&hl=en&authkey=CI-4loEF

Recovery.img for the Sylvania. I checked with a hex editor and there appears to be data inside.

Giveen - is this an img made directly from the mtd2 partition, or is this a modified recovery image?

I'm a windows geek, so I'm slow to learn linux/android. What do we do with this file?

 

[giveen]

it is a direct image of the mtd2 directory, resv

It probably needs to be extracted on a linux box and examined.

 

[ImagineThat]

it is a direct image of the mtd2 directory, resv

It probably needs to be extracted on a linux box and examined.

OK, I thought for a minute there maybe you got clockwork recovery injected into it!

Have you tried unpacking it using unyaffs? I'm not that familiar with images and partitions in linux land, but based on the "mount" command it looks like all the partitions are yaffs2.

I'm asusming you used the "cat" or "dd" functions to write mtd2 to recovery.img, perhaps it needs to be packed with mkyaffs2image and then extracted?

Another thought I had was trying to mount the mtd2 partition, does that make sense? I thought perhaps it could just be mounted to /test or something so then we could sift through it and see what files it contains. Can it really be that simple? I've fooled around with the mount command, though, and can't seem to get anything to happen. I don't really know how to properly use the mount command, I tried

mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /local

but it doesn't seem to do anything. Nothing extra in my local folder...which is what I was expecting if something did work

 

[giveen]

I don't actually have access to a linux box easily so I am not sure how unpacking it would unfold.

 

[ImagineThat]

unyaffs doesn't want to extract it, it says "broken image file"

 

[giveen]

Odd, I wonder what file system they use then.

 

[giveen]

Alright lets try this one. I did the command differently.
https://docs.google.com/leaf?id=0B0...EwNjQtM2M2NmM0YTJkYTdk&hl=en&authkey=CMmypbIK

Rather than doing

dd if=/dev/mtd/mtd2 of=/sdcard/recovery.img bs=4096

I did

cat /dev/mtd/mtd2 > /sdcard/mtd2.img