yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] pogodancer:
Hi fun_,

it's working perfect now:

- No skipping cursor

- No slowlyness (Everything reacts and runs as quick as on other devices: Moving in menu, backing up, restoring, flashing zips). Maybe my backup before was too big (2GB) when I told you that it is slowly (15 or 20 minutes). Or maybe the changes you made with your last version did improve the recovery. Anyway I did a backup today of a naked system and it was done quickly (about 3 minutes).

- No lags and no issues

There is no need to adjust something in your last version. I am really happy with it. You can make it public as fully working. Maybe others feel the letters a bit too small, but I don't have any problems to read everything in the menu.

Thanks a lot.

Edit:

But if you want to adjust your last version. I would like to test it. Just give me a link. Thanks.
[Miscellaneous Android Development] fun_:
I see. thanks.

I'll put it on public soon... currently I'm preparing tooooo many RK3066 images ;)

font size issue is in my todo list.
[Miscellaneous Android Development] VitorMSA:
Excelent job. Works perfectly on my bq Curie :thumbup:
[Miscellaneous Android Development] PanGalactic:
Sources

As I have said to you before I can't thank-you enough for your continued efforts with CWM & these Rockchip Devices, I've learn't much by inspecting your files and have been able to create my own full Touch CWM recovery for Pipo M9 using recovery builder and adding and editing missing files required. It's not perfect but is fully functional for my needs and works well.

Do you have any intentions of releasing your sources as I would really like to try to build from source myself based on your work and learn a little more.

Thanks again and keep up the Great Work.
[Miscellaneous Android Development] 900supersport:
I've tested your recovery for the cube u30gt2 and got the same issue with the navigation buttons moving the highlight every second press.

Tried your updated N90FHDRK and this seemed to work well but the graphics are not right so unpacked to remove the embedded kernel. This recovery seems to be working correctly with the cube kernel.

Thanks for the work.
[Miscellaneous Android Development] PanGalactic:
With the cube U30GT2 & also the pipo M9 you don't actually need to include the kernel just rkcrc the updated N90FHDRK ramdisk to kernel recovery.img and it works fine.

I found if there is a kernel mismatch it could stop recovery from booting which is why I tested the above.

[MENTION=2864694]fun_[/MENTION] is there any reason you can't build the full touch version in the same way recovery builder does?
[Miscellaneous Android Development] leolias:
I think is more safe include a kernel in recovery, if you lose your main kernel, you have a functional way to restore the system.

Fun a really great work.
[Miscellaneous Android Development] fun_:
sorry, is there any reason you can't wait?
[Miscellaneous Android Development] fun_:
working device specific images for RK3188 will be available when it's available.

generic ramdisk for RK3188 devices will be available too. (it will be same as one for RK3066)

what's "same way recovery builder does"?
[Miscellaneous Android Development] PanGalactic:
I agree with you :) But

In the case of Pipo M9 & Cube U30GT2 if the kernel in the recovery was different from kernel flashed to kernel partition recovery would not boot.

Therefore having to produce a new recovery for every update with new kernel.

As the RK3188 have such good tools to flash updates & individual partitions I see it safer to get CWM on my device and get a backup of my setup as quick as possible.

So by having a recovery not reliant on kernel would mean if a new kernel were released you wouldn't have to wait for the creation of a new recovery getting your data backed up in the shortest possible time.

IMHO

---------- Post added at 08:42 PM ---------- Previous post was at 08:33 PM ----------

Yes I can wait :)

I don't wish to build from source to get CWM any quicker, I have a working version for my Tab, I wish is learn :)

---------- Post added at 08:53 PM ---------- Previous post was at 08:42 PM ----------

I've extracted the latest ramdisk already and tested on Pipo M9 function works fine, it's just the ease of use as the M9 has no volume rocker.

see this picture

http://www.google.co.uk/imgres?clie...bnh=171&tbnw=248&start=0&ndsp=16&tx=109&ty=93

This is like the version I created using recovery builder you just tick the touch box and its created like this therefore I would have thought it's an option in the build process?

I can just scroll & touch the option I want unlike your version which is the old style for non touch devices.

Recovery Builder

http://builder.clockworkmod.com/
[Miscellaneous Android Development] fun_:
http://androtab.info/clockworkmod/rockchip/rk3188/

http://androtab.info/clockworkmod/rockchip/rk3066/

all images are updated now.

there are 70 images for RK3066. if I missed your request, sorry, please request again.
[Miscellaneous Android Development] fun_:
sorry, your request is not clear for me.

which do you want?

A. recovery with touch GUI

or

B. Web interface to build my CWM-based recovery

or

C. something else

if you are talking about A, please tell where is the source code and how to control without touch screen.

btw, my CWM-based recovery is not old. it's CWM recovery, not CWM touch recovery.
[Miscellaneous Android Development] fun_:
really?

at least, in PiPO M9 20130315 firmware (for old rev), kernels in kernel partition and recovery partition are different. same for PiPO M9 20130319 firmware (for new rev).

I never heard such a thing for any other Rockchip devices.

my device specific image doesn't depend on kernel in kernel partition.
[Miscellaneous Android Development] PanGalactic:
Sorry I didn't mean to imply your CWM was old, just the gui is in the original style not newer touch gui style.

Yes A. Touch Gui

Recovery Builder uses hudson

https://github.com/CyanogenMod/hudson

I will glady look closer to find the source for touch gui if it would help but I assumed you would be drawing sources from Cyanogen and they would be part of your sources already.
[Miscellaneous Android Development] moezaka:
am pretty sure koush haven't released sources for touch based cwm ...
[Miscellaneous Android Development] fun_:
I can't believe "hudson" contains the source of recovery with Touch GUI.

and please tell me how touch recovery works on device without touch screen.

please tell me where is source for touch recovery in https://github.com/CyanogenMod/android_bootable_recovery/
[Miscellaneous Android Development] fun_:
me too, but I wish I'm wrong.
[Miscellaneous Android Development] PanGalactic:
These are two good reasons why I wish to view your source, to learn how you have solved these issues. I respect the knowledge you have with Rockchip devices as you know and simply want to learn from the best.

All I'm after is your latest RK3188 generic with Touch Gui as recovery builder can create which I feel better suits a touch tablet

---------- Post added at 10:14 PM ---------- Previous post was at 10:04 PM ----------

If that is the case and I'm asking for the impossible then I'm sorry for being a ****!

I'll go off an have a read again
[Miscellaneous Android Development] pppos:
Does this CWM support MK802 II which is AllWinner A10 cpu?

I try to run CWM-MK802 III. But got a error message. looks like it can not recorgnize the MK802 II's partitions.

root@android:/sdcard # flash_image recovery recovery.img
error scanning partitions: No such file or directory

Are you will to supply a MK802 II version？Thank you very much!:good:
[Miscellaneous Android Development] evildave_666:
Will this work on either version of the 808B? (I assume so)

Sources? I wouldn't mind porting to Pipo S1 (very similar to original Yuandao N70).
[Miscellaneous Android Development] fun_:
I got your information. thanks.

then, sorry, I noticed I confused a bit about DPAD. as you said, it works.

about right button, if you tried it in "key test" on CWM, it should act as BACK(cancel) and you'll get menu.

btw I guess you tried some another app on Android for testing key codes, right?

I hope you tried it with same kernel as mine(from 0117 rom). I think scanCode is the raw code what I need.

from your information, I think VOLUME DOWN/UP, BACK, DPAD UP/DOWN/LEFT(as select)/RIGHT(as back) should work. and all other keys have no effect. right?

I think I should add a code for "OK" button as select.

I see. really thank you!
[Miscellaneous Android Development] fun_:
sorry, I don't know about "either version of the 808B". please tell me detail, or pointer about it.

I'll do things eventually. I'm always busy. and now I'm extremely busy for answering feedbacks and random questions :(

I couldn't touch my code for several days...

you can try ramdisk-only image for now. feel free to port it to your tablet.

if you want a image from me, please tell me about latest official image. probably I can find latest official rom for Yuandao N70 from official site. if you are sure Pipo S1 and Yuandao N70 are 100% same, I'll make CWM for N70, then you can try it too.
[Miscellaneous Android Development] fun_:
I got a report that mouse doesn't work on CWM for UG007. I'm asking detail now, but if you know something about this, please let me know.
[Miscellaneous Android Development] onelovekir:
Yes I used an app called Key Test and it was on the same kernel as 0117

having the "ok" button would be awesome! Just let me know if you need me to test anything for you, thanks a lot!
[Miscellaneous Android Development] evildave_666:
There are 2 major versions of MK808B out there. They're using the same case and markings so its causing people making roms a lot of trouble.

Main difference seems to be which BT and Wifi devices they're using. The second version is using a Mediatek Wifi/BT chip instead of RK902.

As for the PiPo S1, the latest official image I know of is here. There is a january image that is supposed to be official but I can't find a direct link from pipo for it.

It seems to be same hardware (screen resolution, wifi device, etc.) as Yuandao N70 except 8gb flash not 16. Can't say for sure if button definitions are the same.
[Miscellaneous Android Development] stephencapes:
iRulu AS107 Tablet

Hey guys, first off just let me give huge kudos to your guys for your contribution to these devices. I am actually looking to port this to this particular device iRulu AS107 Tablet which is of course based on the RK3066. I have tried repeatedly to use the build.clockworkmod.com to compile the recovery. Even tried it by including the recovery.fstab. Can you guys possible point me in the direction of how to get this working? I have a full original "update.img" firmware image. I've decompiled it all the way down to the zimages.... What do I need to do and what do you need from me. Leg work is not a issue. Thanks guys.

BTW this devices Boot and Recovery.img's both have a identical zimage is that normal.
[Miscellaneous Android Development] fun_:
thanks. then I need to get rom for different one. CWM doesn't use wifi/bt so CWM for MK808B may work on different one, but I don't recommend to use CWM on different hardware.

I'll try to make CWM for these devices when I can get enough time.
[Miscellaneous Android Development] fun_:
well... I do "compile" things to port original CWM to RK3066 device, but my "compile" is not same as what you called "compile". I call them "unpack" "repack" like as "unzip" "zip".

you really want to do "compile", you need to know how to modify CWM source code and how to "compile"(not "repack") CWM from source code, without build.clockworkmod.com. it may be long legwork.

if you just want to "use my CWM" on your tablet, it's relatively easy. please do "unpack" and "repack" things with your zImage and my ramdisk. you may try my ramdisk-only image.

please make sure what you want.
[Miscellaneous Android Development] stephencapes:
Thats what I was going to do but I could not get your recovery.img to unpack with what i'm using i get a response about it missing a android header, what utility do you use to pack/unpack? BTW I get ya on the compile, I ment pack, just a mix up of words. :)
[Miscellaneous Android Development] fun_:
well... you quoted entire my message. so, I'm not sure what is "Thats what I was going to do". later you mentioned about pack/unpack so I guess you want "pack/unpack" thing, not "compile" thing. right?

then, which "recovery.img" you tried? I made some kind of "recovery.img", so proper utility (e.g. unpackbootimg or rkunpack) need to be used. but for any image, there is no "special utility only for my CWM". they are common in Rockchip custom rom world.

I'm not sure about you. do you have any experiment about custom rom for Rockchip's devices? if this is first time, you should try google to learn about it. here is not the place to talk about general custom rom things for Rockchip.

if you are sure about kernel/boot/recovery partition and images for Rockchip devices, you can try my ramdisk-only image w/o unpack/repacking.

I want to add more information to my site including about these things. it will be done eventually. but I'm always busy and now I'm very busy to answer random questions from some people. I really want more free time...

if you can, please write question more clearly. I don't want to waste my time to guessing or asking "what you asked?" :(

thanks.
[Miscellaneous Android Development] evildave_666:
This is stock firmware for the Mediatek-chip version of the 808B: http://depositfiles.com/files/qjs0nsr0l

There does not seem to be any official source for it and I have not yet personally encountered the version with Mediatek.

People are calling the Rockchip version "real" and the Mediatek version "fake/clone".
[Miscellaneous Android Development] fun_:
thank you for your infomation. I'll add image for Mediatek version too.
[Miscellaneous Android Development] fun_:
I noticed some person misunderstand about me and my CWM-based Recovery.

my CWM-based Recovery has no relation to other CWM-based Recovery except they're based on original CWM. this is the reason that there is no credit for others who made CWM-based Recovery on my site/this thread.

well, actually, I should add credit for original CWM author and all contributors(include me). anyway, I'm not a person who uses others' work and hides about it.

if I need to explain about myself much more, I'll do it. but I guess no one has interest about me except what I'm currently offering ;)
[Miscellaneous Android Development] onelovekir:
don't worry buddy, I hear you loud and clear. No misinformation was intended. You are awesome! don't worry about the other people, and I look forward to working with you, thank you so much for your work!!
[Miscellaneous Android Development] fun_:
I added "all credit goes to ..." sentence to my site and post#1 here. it should be done in the first place and I shouldn't be lazy to do it even for I was/am busy.
[Miscellaneous Android Development] fun_:
thank you too. I'm naive for this kind of thing because of my past work.
[Miscellaneous Android Development] flibblesan:
Just dropping in to say that the Generic image works perfectly on the RK3066 tablets I have here (Gemini branded). Thank you for making these as I tried so many other versions that didn't work at all.:good:
[Miscellaneous Android Development] SoulReaver75:
Any hope that cwm will work on MK809II stick?

Original fw and tools are here: http://www.mk809.com/cs102II/en/Download.html
[Miscellaneous Android Development] fun_:
what I wanted to say is "all rockchip devices has no dependency between kernel in kernel partition and kernel in recovery partition".

some official firmware doesn't have kernel.img, some other official firmware has different kernel in kernel/recovery partition, but they all just work, ofcourse.

there is no code to solve this issue(?) in my source. please don't think I'm keep something secret.

EDIT:

in other words, "there is no rule that kernels in kernel/recovery partiiton must be same on rockchip devices".

I really don't like to use my time to explain something which is not existent :(
[Miscellaneous Android Development] pogodancer:
@ fun_

I guess that I don't really understand about the last posts are mentioning, because I am a Windows-Dummy. But I think 98% of the members visiting your thread and belonging for a CWRM are dummies like me. And they only want to have one aim: Getting an Clockwork to work with it. But they never mind if touch or no-touch. If your way for recoveries is no-touch I think 99,99% of the users agree with you. They only hope to get a recovery for their devices.

Excuse me, but I recommend: Don't care about extra-special-wishes. We need recoveries. And that's what you're making. For most of the RK3066s and some RK3188s you made them. Please keep working for the usual (non-touch) in the first degree, because that's everybody's first aim.

I appreciate your excellent work and your aim to help so many tablet users for free (nothing but a thanks). Really great !!!!:good:

Edit: Hope to have this message translated with a POSITIVE evaluation with my old school english.
[Miscellaneous Android Development] Olioaglio:
Thanks a ton, man. Will test on my xoro asap and report.

Cheers, Olioaglio
[Miscellaneous Android Development] rocketero:
I know this is a though question, but do you know why the rockchip kernel (boot.img, system.ext4.tar) can not be extracted by dxda's kitchen tool ? .. the boot.img is not compatible with this tool, and I haven't been able to find, after doing a lot of Google research, a suitable tool to extract this image. What I plan to do is try to swap the nand flash internal storage with the external Sdcard so I can work on another project that is mounting /data original partition onto a partition on the Sdcard.
[Miscellaneous Android Development] fun_:
at first, please understand here is not general Q&A forum, and is not support forum for tools made by others.

I may be able to answer questions related to my work on here, but non-related questions may not be answered.

and currently I'm very busy. even if it's related to my work, I may not have enough time to explain detail.

I don't know about "dxda's kitchen tool" (sorry, I have no time to google it), if you have a question about it, please ask its author.

then, my CWM-based recovery doesn't use any special file format. all output files are made as same as original CWM.

some files are raw partition image, its format may vary by devices(it's usual thing).

please understand that ".img" is just a suffix of file name. it doesn't specify content of the file.

there is no all-purpose tool for all ".img". you need to find & learn about .img file *used in rockchip device*.

I already mentioned about name of tools I'm using in post#3.

there are some boot.img formats used in rockchip device, so there are some tools such as unpackbootimg and rkunpack.

you have to identify type of format at first.

about ".a" file, please see https://github.com/CyanogenMod/andr...mmit/d9115b7888a4423116f819c89f0dc868f2916544

about ".c" file such as rkunpack.c, you need to understand how to compile C source code into executable file.
[Miscellaneous Android Development] fun_:
thank you for your comment. I think I understand 100% correctly :)

then, why I'm asking about device without touch screen is because my CWM supports non-tablet devices. it's very clear that any other recovery which doesn't support any input other than touch screen, is unusable for non-tablet devices.

I also like recovery with nicer GUI for touch screen, it must be nice. I never say I don't like touch interface. but currently I have no reason to change my base to TS-only recovery.

I'm not sure it's really TS-only, so I asked about it. or if it's easy to add support for non-touch inputs, it may be ok to change my base, when I have enough time ;)

----

everyone, thank you for your help. feel free to post any request(related to my CWM), but sorry I can't guarantee I'll give positive answer.

EDIT:

I'm reading (some of) old posts from new to old to find missed request/questions, but for now please post it again, it will be faster ;)

EDIT2:

oh I remebered I need to update changelog at first...
[Miscellaneous Android Development] saleandoli@aol.com:
Hi Fun, does an Idea USA ct705 need a device specific cwm recovery? Sorry to bother you.
[Miscellaneous Android Development] fun_:
sorry, currently I have no information about it(I read your old posts on here). please give more information such as detail about "generic CWM doesn't work" to solve issue, and/or link to official firmware to make device specific CWM image.
[Miscellaneous Android Development] rocketero:
don't worry, you're doing a great job, I just asked this in case you have knowledge but it's a very though and complicated subject, I'll keep doing my own research, I have the mk808b stick just for fun as I don't use it much because I use a tablet and a pc.

thanks for your inside anyways. About the ".a" type of files the link is hard to understand the content, so in your own words what are those .a type of files in your cwm backup ?
[Miscellaneous Android Development] saleandoli@aol.com:
I will try and find it, thank you for your kindness.
[Miscellaneous Android Development] TTaba74:
Flash image for Bq Curie RK3066, Linux version 3.0.36+, work perfectly, thanks a lot fun_ :):)

Will follow all your work
[Miscellaneous Android Development] Jhonsonlee:
Can't control in CWM

Stressful flashed CWM on MK809II but can't conrol it with mouse, keyboard?

Need Help to control in CWM Please.

Thanks.
[Miscellaneous Android Development] PanGalactic:
I don't think you are keeping secrets, I also don't think you should release your source if you don't want to.

I would just be interested to see how you have been able to make CWM backup and restore the kernel partition as the recovery builder .img does not do this and therefore your CWM is much better.

Again I'm sorry for any confusion I may have caused this was not with your CWM, it was with CWM created with recovery builder.

---------- Post added at 02:02 PM ---------- Previous post was at 01:36 PM ----------

The Touch Gui that recovery builder uses is not Touch ONLY, on the Pipo M9 the Power Button still works the same in that it actions whatever option is highlighted in the menu and the Esc button will take you Back from a sub menu. As the M9 doesn't have a volume rocker I can't confirm 100% this works the same but I believe it does.

I thought as I could build this with recovery builder that Touch Gui in CWM was completely open source and it would be a simple option in the build process as it is with recovery builder but I was Wrong and probably should have known better.

I hope the source for Touch Gui will be released as this would make your CWM even better.

I'm sorry if I'm a pain in the Arse, unlike most users I don't want you to do all the work, I want to do as much as I can myself and to learn the process along the way. I do understand you are very busy and I do not expect an answer or explanation.
[Miscellaneous Android Development] VitorMSA:
Could you tell me how can I enter to recovery menu on boot. I have your Bq curie latest recovery build.

Thanks.
[Miscellaneous Android Development] pogodancer:
On the most devices you can boot into recovery when:

1. Keep holding Vol.+

2. Keep holding Power until you see the devices is turning on. Then release the Power button.

3. When you see the recovery menu you can also release the Vol.+ button.

Maybe you have to try the Vol.- button or the Menu-button if this does not work. Good luck.
[Miscellaneous Android Development] VitorMSA:
Thanks for advice, but that method only works with previous release (version 6.0.2.8). Strange... :eek:
[Miscellaneous Android Development] :
Hi Fun,

Again if possible could you create a device specific CWM Recovery image for the Zoostorm PlayTab 3305-1030 (UK), it's an RK3066 device.

I have a link to a the Update.img - http://downloads.zoostorm.com/drivers/android/PlayTab/

Also if needed here are the separate boot.img, kernel.img, misc.img & recovery.img from a backup I made on the Zoostorm PlayTab tablet - http://www.mediafire.com/?jfqmjppyk83ih82

Thanks again ;)