Im missing clockwork recovery, i think its a wonderfull tool. And i think life on the Folio would be much easier with it. I dont have the skills my self to make it happen. I dont even know if its possible. But i thought i put the question out there to see if something happens. And i must say we all own Dexter a big thanks, because he seams to be the only one with any rom cooking skills for the Folio. Ican say that its only because of him that i bought the Folio. I also saw in the Tnt0.4 thread a question about Cyanogen and if we wanted it, HELL YEEAAAH!!!! I know tthat GTab have a beta for it. And also read that GTab and Folio are very close hardware wise so maybe a port is possible. But again i dont have the skills
No one? Am i the only one wanting these things? I thougt if we could get a thread going on the matter we might inspire someone with the skills to do a Cyanogen port for the folio. Cyanogen is almost ready to start the nightlies on CM7 so maybe we could have Gingerbread.
Clockwork recovery would be nice to have its alot easyer to do things with it, im still waiting for stable CyanogenMod on my galaxy s to be able to say if i want it on my tablet i have no idea how to get clockwork to work though and if its even possible
i'm sure its possible, but reading the Gtab thread on Cyanogen i'm waiting for a stable release before i would consider wasting time on it, and currently my "compiling" environment is still VMWare based, and i simply dont like compiling in it, since it takes like 30x the time i got on my debian..(will be ubuntu very soon)
It sounds promissing that you keep track on the development of the Cyanogen rom for Gtab. There seams to be some more work being done over Irc on freenode. Its a beta 6.2 thats been released there, but it seams to have some issues. But for sure Cyanogen would be exellent. Im currently running Gridlocks "Crackflashers" CM7-Rc0 on my Desire HD, and Gingerbread is so smooth and it runs so well. And Koush has a guide on how to get clockwork recovery on to new devices on his site. But hey, i dont got the skills. I just enjoy all the Devs work and try to help out with some beta testing if needed.
nickwarn said:
And Koush has a guide on how to get clockwork recovery on to new devices on his site. But hey, i dont got the skills. I just enjoy all the Devs work and try to help out with some beta testing if needed.
Click to expand...
Click to collapse
i was considering testing the Gtab edition, and modify the parts that point to wrong partitions and make it folio compatible.. thats probably the easy one..
but maybe i should check that site? you got a link? or should google help?
Dexter_nlb said:
i was considering testing the Gtab edition, and modify the parts that point to wrong partitions and make it folio compatible.. thats probably the easy one..
but maybe i should check that site? you got a link? or should google help?
Click to expand...
Click to collapse
Yes its "Koushikdutta.com" he has a guide its called "Porting clockwork recovery to new devices" Its a little hard to find. Just go to bottom on the site and click on 2010 articles and scroll down and there it isorting Clockwork Recovery to New Devices
I pasted the begining of the guide:
It is difficult for me to port recovery for a device I don’t have. So, people can attempt to port it using this guide. However, if you want it done properly, and probably quicker, you can loan the device to me personally at:
Koushik Dutta
2721 1st Ave 507
Seattle, WA 98121
The package must include:
The rooted phone.
A return packing slip to your address.
A signed statement saying: “I, <your name here>, am lending this device, <name of device>, to Koushik Dutta so that he can try to port Clockwork Recovery to the device. I understand that rooting a phone voids the warranty and tampering with the software may render the device nonfunctional. I realize and accept that the phone may not be functional when it is returned. Koushik Dutta is not liable for any damages to the device.”
And so on, have a look.
The folio seem to be very close to the Gtab, what about Advent Vega? because the guys in Gtab thread are using Vega rom and it also has a clockwork recovery. I dont know , but maybe having a look at that would help. If looking aat the differrent parts of recovery.img and where they differ one can see where changes need to be made? I dont know, just trying to help. I really want this clockwork rec, i think we all and the folio would take a step forward. And maybe have a look at VeganTab rom, if possible to port?
I've used clockworkmod recovery since G1 era and it has saved my b*tt several times. The built-in nandroid support, permission fixing, unsigned zip flashing, etc are very useful and user-friendly.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
nickwarn said:
Yes its "Koushikdutta.com"
Click to expand...
Click to collapse
ok, will check it out this weekend.
That would be great dexterr
I just read in the Avent Vega forum that Apache14 maid a port of GTab cyanogen for them and it seems to work ok. And he also said that he is now concentrating on Gingerbread, proberly that means CM7. And judging from the work Apache14 has done for us with Desire HD, Z, G2. This sounds really promising
Hi,
I'm trying to port ClockworkMod Recovery v3.0.0.5.
For now it's partially working. I can't mount some part.
This is my recovery.fstab :
Code:
# mount point fstype device [device2]
/boot auto /dev/block/mmcblk0p5
/cache auto /dev/block/mmcblk0p2
/data auto /dev/block/mmcblk0p6
/misc auto /dev/block/mmcblk0p3
/recovery auto /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8
/system auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk1p2
/boot and /recovery don't mount.
any idea is welcome
wolfx said:
/boot auto /dev/block/mmcblk0p5
/recovery auto /dev/block/mmcblk0p7
/boot and /recovery don't mount.
Click to expand...
Click to collapse
you should not mess with 5 and 7, those are in a stock rom boot and recovery images, not a filesystem. so they cannot be mounted.
wolfx said:
Hi,
I'm trying to port ClockworkMod Recovery v3.0.0.5.
For now it's partially working. I can't mount some part.
This is my recovery.fstab :
Code:
# mount point fstype device [device2]
/boot auto /dev/block/mmcblk0p5
/cache auto /dev/block/mmcblk0p2
/data auto /dev/block/mmcblk0p6
/misc auto /dev/block/mmcblk0p3
/recovery auto /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8
/system auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk1p2
/boot and /recovery don't mount.
any idea is welcome
Click to expand...
Click to collapse
I dont know, but im glad someone taking the first step. Maybe you could mail Koush, its a link in the guide for porting clockwork recovery. I dont know how much support he does. But writes that one can send ones device to him and he will port it, so i think if hes willing to that kind of work, he probably answers some question. I wish you the best of luck and i will follow your progress with great interest
My port of the ClockworkMod recovery is about fully working.
update from .zip, wipe, backup and restore ... are working but i still have some minor issue.
Partitions don't automatically mount and actually backup of boot part don't work.
I'm asking if bootloader could be the problem.
wolfx said:
My port of the ClockworkMod recovery is about fully working.
update from .zip, wipe, backup and restore ... are working but i still have some minor issue.
Partitions don't automatically mount and actually backup of boot part don't work.
I'm asking if bootloader could be the problem.
Click to expand...
Click to collapse
yes, according to DerArtem, you cannot see the partitions which contain that information its located outside of the mmc.
but sounds great you got it running, alot will appreciate it...
Rom cooking
moved.............
Maybe I'll make a stupid question ... but .. not really for serving or clockwork recovery that can help.
Can anyone explain to me that extra utility of this tool?
thanks
i just started hacking my Legend some time ago and got the liking of RomManager. my friend have a as100 rooted and flashed rom manually. Clockwork port to this device will be great on the go.
So I have been out of the rom game since Bionic. I recently upgraded to Chimra from team passion, I have tried a few different kernels and have noticed that none use Voodoo.
Is this something we have gone away from? or am I missing something?
Thanks!
http://forum.xda-developers.com/showthread.php?p=27030609
Check this out. Go to second from last page (I think) for updated download. Devil 3.0.75
What are you looking at shortbus......
Post #99 has the newest version, Thanks!
After reading it all 10 times over I used the "mount" command in terminal and figured out that I am on YAFFS2 and ext4 already. Depending on the mount.
That Kernel is so fast I am not going to worry about it any further!
Thanks.
Hi everyone,
I am eager to try out ICS' disk encryption feature. One thing is it requires that /data is in ext4 format. This is on a SonyEricsson Active and the default FS type for /data is yaffs2.
I've tried a few different things but I'm not getting anywhere. I've also seen a few threads here with posts of zip files that should do it but none for the SE Active. I would like to try this from the Recovery mod CLI. I already have ICS 9.2 installed and running on it no problem.
Any suggestions?
Thanks! I hope this is the right forum to post this in.
Ok so i'm not a big linux user but can grasp the basics and solve most of my problems alone, this ones had me scratching my head for days though......
On every rom i've downloaded for this phone i've had major problems trying to mount my external partition to compensate for the lack of int memory, well after trying just about every script out there i began to think something else wasn't right, a little digging and a lot of log catting pointed me in the direction of /system/bin/e2fsck which well basically doesn't seem to be present in any of the roms i've downloaded.
A little more digging and I found out that simply copying this file wouldn't work and i'd need some other files too, namely /system/bin/mke2fs and tune2fs + the relevant lib files [ libext2_blkid.so, libext2_com_err.so, libext2_e2p.so, libext2_profile.so, libext2_uuid.so, libext2fs.so]
I looked in a cm7 rom zip from one of my other phones for the files and pushed them to my ace after wiping everything and doing a fresh install, I then ran a data2sd script and hey presto everything has moved to my sd-ext partition first time without any messing about.
So anyway as i said i'm not very linux savvy and have no idea what these files actually do so please can someone enlighten me and or explain why we don't have them in our roms in the first place??
Sent from my GT-S5830i using Tapatalk 2
You didn't require these files to complete the data2sdext process. That's why they weren't present
I want to edit the partition layout (HDX 7", 13.3.2.3.2, TWRP). But seems that I am missing the knowledge
Imho /system(1.2GB) and /cache(1GB) are oversized, when using a Custon ROM. For me /system with around 500MB is more than enough. And /cache 200-300M(?), so around 1.5GB to free and add to /datamedia
After reading around, I am more confused than before. I am not able to hex-edit appsboot (do not find matching values?), nor I am able to use the Qualcomm-Tool in the right way. Maybe the info was right, that appsboot.mbn (partition.mbn?) has to be compiled from the scratch(?) Not my league.
Long story for explaining question
Is somebody out there with a solution, e.g. something I can flash? :fingers-crossed: