yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] dibnah:
Hi fun_, I realise you are really busy but I was wondering if you have an image for the Versus touchtab 9.7 DC. The original firmware can be found at http://www.versusuk.com/assets/downloads/dc/97dc/versus-touchtab-97dc-firmware.img

I have tried the manual install using ADB and all seemed to go well, but when I reboot I still get the black screen that you get with the standard versus recovery

Many thanks for your help
[Miscellaneous Android Development] fun_:
sorry for late reply. I'm very happy that there is new developer!

as you know, Rockchip's code is available.

please go ahead, you'll be faster than me :)
[Miscellaneous Android Development] Shmarkus:
heh, I doubt it! Anyway, sorry to be taking Your time, but could You tell me wheres the init binary taken from that You use in Your recoverys? I mean, standard init doesn't work with CWM and also compiled init doesn't seem to cut it either! So I am curious to know how to get a working init to a rockchip device besides snatching it from Your CWM.

Thanks in advance and hope to see a generic CWM 6.0.4.x!
[Miscellaneous Android Development] fun_:
I didn't take init from anywhere. everything was built from cm-10.x source. and, if my memory is correct, I didn't change init. it worked fine.

there is my old source on my old disk, but I don't touch it for a while. current build machine is remote machine and small disk. it's difficult to restore old build environment for now.

I want to continue to make cm-11.0 based new recovery...
[Miscellaneous Android Development] fefifofum:
Where did you get the update-binary to flash the recovery.img? Only that binary works to flash mtd partitions, but it has a problem with CM11 and "set_metadata".

EDIT: nevermind, I figured it out.
[Miscellaneous Android Development] s7yler:
Does this work if I have 4.4.2 kitkat none-rooted on my tablet with RK3188 ??
[Miscellaneous Android Development] Cass1977:
Hi guys

Is there any way I could get a port of this for the rk3026? Ive got the stock rom but not sure how to build cwm from it. Ive seen a few of these about now so might be worth supporting them ;)

Cheers
[Miscellaneous Android Development] fun_:
I don't have any device with RK3026 and any information about it.

I'm preparing new CWM images based on cm-11.0 branch now. if there is official rom for any RK3026 device, I'll prepare CWM for RK3026 too.
[Miscellaneous Android Development] dermousis:
REP Electronics Android Gaming MID KST-GAME-2CR

Hello, I installed the "ARCHOS GamePad" CWM recovery (RK3066) on a "REP Electronics Android Gaming MID KST-GAME-2CR" (which have almost similar specs with ARCHOS GamePad 1), but in recovery mode (Power + Start on this model, but also tried Power + Volume combinations) it only showed a gray screen.

I also tried the RK30GENERIC_CWM and the screen was black (not even grey) in recovery mode, but it boot normally to android.

I had previously made nandroid backups of all the partitions, so I booted to recovery again (black screen) and flashed the recovery.img with RKAndroidTool.

Unfortunately the screen remain black in recovery mode, but still boots normally to android.

Can anyone help me find a compatible CWM recovery (and even better a stock or custom rom) for "REP Electronics Android Gaming MID KST-GAME-2CR"?

I 'm also quite certain that this model (KST-GAME-2CR) is completely identical (except installed apps/games) with those ones:

Tekniser Tek 807D

GAMEING MID GameMid

DEAFactory DEA Tablet 807 D (1402) "MyPlay 2"

TUVVA Power Play GameTab

NIB Spec Computer Supergamer Ole SG001

Global Systems Phantom Gaming Tablet

thnx
[Miscellaneous Android Development] Cass1977:
Ive got the stock firmware for the 3026 if that helps? I can dump just the kernel.img if you like?

Chris
[Miscellaneous Android Development] AbduL_PT:
_fun i love your work. :good:

I have no intentions to hijack :angel: this thread. But if anyone is interested in TWRP, you should check out this thread.

Cheers.
[Miscellaneous Android Development] pogs24ever:
Nice...

Sent from mobile
[Miscellaneous Android Development] fun_:
no problem. thank you for your information. someone who needs TWRP, please try it.

I don't have enough time to do anything(develop myself, try someone's work, etc) about TWRP for now

EDIT: I read that thread just now. I don't say good/bad/etc about it.

what I know about (generic) TWRP is, it include important change for Rockchip devices from 1 year ago. https://github.com/TeamWin/Team-Win-Recovery-Project/blob/twrp2.7/mtdutils/rk30hack.c

other things such as handling misc partition and factory reset from android should not be so difficult.
[Miscellaneous Android Development] bhiga:
Thank you for this collection of recoveries!

I made a version for Insignia Flex 8 (Android 4.2.2 Jellybean version), model NS-14T002 by replacing the kernel in the CX-803 version.

Download: CWM for Insignia Flex 8 (Android 4.2.2 Jellybean version), model NS-14T002
[Miscellaneous Android Development] blenderbros1:
sorry

. Hey. Thank goodness I'm not alone. I own the tuvva tablet yes its the same in a lot of ways. I too am trying to find a user base for our tablets....it seems there is no info on these tables....I bricked mine the first time and was able to get the IMG file back after days of contacting tuvva so that's a plus so now if I can find a group of people in need of the IMG file I can give into them...maybe mod it you see the tablet is not normal its hard to accour the IMG file or firmware for these as there is no info anywhere. I do belivve once I upload this IMG file I'll be the first to set off a wave of mods for the tyoe of tablets we own...I hope some one out other can help us
[Miscellaneous Android Development] bhiga:
The Generic recovery requires that you have a valid kernel in your kernel partition. The tablet I worked on did not (Insignia Flex 8). I don't remember if I got just black screen or gray screen, regardless, it did not work.

I had extra challenge because a lot of the firmware tools did not work - rkdump, RKBatchTool (I tried from v1.4-v1.7), thus I had no means to flash except for root shell. Extra risky since that mean the only flash option I had was ADB root shell, which of course requires it to boot normally, so I was very cautious in my approach.

Here is how I "adapted" the CX-803 CWM to the Insignia Flex 8:

Root the device

Dump ROM via romdump - this resulted in .img of all the partitions except for misc.img

If that does not work, you may be able to dump the partitions manually with dd.

I did this with 4096 blocksize as a sanity check. The result was binary-identical to what romdump gave me, but I also had the opportunity to grab the misc.img

Back up the ROM dumps somewhere safe.

Extract the boot.img with RK3xxx Firmware Tools (make sure you extract to a short filepath like C:\rk3xxxft and Run as Administrator - this was also helpful information)

Save the kernel.img from the unpacked boot.img - we will need this kernel.img to put into a compatible recovery, this will be your kernel.img

Extract the recovery.img with RK3xxx Firmware Tools and save the recovery.img.cfg file - we will need this to find a compatible recovery

Found a number of potentially-compatible models and downloaded corresponding CWM recoveries on androtab.info

Extract candidate recovery.img and compare the recovery.img.cfg content to my recovery.img.cfg - check the offset values and such, also check the size of its kernel.img to your kernel.img

Once a matching one is found, replace the kernel.img in the extracted recovery with your kernel.img

Rebuild recovery.img with RK3xxx Firmware Tools

Copy new recovery.img to tablet storage and flash via root shell method

Reboot to recovery and test

If test successful, save it! If test unsuccessful, try other candidate recoveries. In my case the first one with matching recovery.img.cfg (CX-803, not the 2GB one) worked, though I had tried some non-matching ones earlier that did not work (Pipo-M8).

So even if the specs are very similar, I think it comes down to the memory map that recovery loads into, which is described by recovery.img.cfg.

I never tried to write the kernel into the kernel partition as I was not 100% convinced that the format of the extracted kernel.img matched what was needed to write it - and again, because I couldn't use any of the bootloader download tools, I would be hosed if I wrote something that prevented normal boot.

Hope that helps someone.
[Miscellaneous Android Development] dermousis:
Thanks for this "guide"! Will be very useful.

I also asked (the great) [MENTION=4751990]Oma7144[/MENTION] (RK3066 Tab Genio by Oma rocks!) for help, and he extracted the Kernel, so I manage to flash CWM Recovery.

Unfortunately I couldn't manage OMA's CM10.1 Rom to work for more than... two minutes. :(

I hope that someone, with the same kind of tablet, can make CM Rom to work.
[Miscellaneous Android Development] fespafer:
CWM for cloudnetgo Cr11S 5Mpx

Hi! and thanks for your help with our little toys. I'm the owner of an android TV from Cloudnet model Cr11S 5Mpx cam. It's supposed to use the RK3166 chipset and I tried to install the CWM you posted following your instructions (putting update.ZIP into root folder of sdcard). After first reboot the system asked for installing the package and reboot in recovery mode (just the green android screen) and a status bar began to increase until it stopped 1/4 of total. Then it rebooted and showed up a message saying it failed and requested for deleting the file update.zip

Could anyone tell me if that CWM can be flashed in my android TV?. And one more doubt, since it has no hardware buttons, how I'm I supposed to move over the CWM options?.

Thanks in advance for your replies guys!
[Miscellaneous Android Development] xdrc45:
Hey guys,

Anyone know if this cwm will work on a visual land prestige pro 7d?

It has a -

Rockchip rk3066

Kernel v 3.0.8

Android 4.1.1

I'm assuming it will... But assuming can get you into trouble lol
[Miscellaneous Android Development] bhiga:
Yes, not good to assume when it comes to firmware/ROMs... ;)

Kernel is key and the wrong kernel can mean things don't work - or worse, work improperly and overwrite or corrupt things.

If your specific model isn't listed on androtab.info (doesn't look like it) and you are not 100% sure that another listed model is an exact match (rebadged, not re-engineered in any way other than make/model identifiers), I recommend extracting your current kernel and trying to find a compatible existing "template" recovery that you can replace the kernel with your kernel, like I described a couple of posts back.
[Miscellaneous Android Development] xdrc45:
[MENTION=3050092]bhiga[/MENTION]

Thanks for the information, I really appreciate it. I can't seem to find a working recovery for this thing anywhere so I think this is my best opportunity. I believe that the visual land prestige line is a rebadge of the allwinner "A" line tablets.

This rockchip is a different beast than I'm use to.... The bootloader is just a blank black screen and shows up as mass USB device on the PC (think this is where you use livesuit) and when I try to boot to stock recovery through adb it just shows the android guy laying on its side. I've read that people have to use livesuit to flash the firmwares on the device. So I'm trying to learn the ins and outs of this device still. I've had the tablet just a couple of days, I actually bought it for my 7yr old son so that he will get off my lenovo a2109 tab lol. I managed to root it with cydia just fine and it would be nice to have a working recovery then build a stock debloated ROM.
[Miscellaneous Android Development] bhiga:
I hear you - Rockchip is way different from the HTC and Samsung devices I've used before.

Definitely back up what you have partition-wise, especially boot and recovery as you'll need those.

The Android on its side is the stock Rockchip recovery - press Vol+ and Vol- simultaneously and you should get a menu appear. (I had to ask for help on that too) :D You'll need that to get your kernel to try injecting into other recoveries. I guess the stock recovery works, but I don't have a clue what the "RK" update format is, heh.

I had the same trouble with bootloader mode, and none of the Rockchip (RKFlashTool, RKBatchTool, etc) would recognize the Insignia Flex 8.

The computer did recognize the bootloader-mode device and installed drivers, but all the utilities refused to see it.

That's why I ended up using romdump to get my partitions. Grab them all and be sure to copy them to computer or other storage.

From what I gleaned over at Vondroid and Freaktab, Allwinner may be "special" (as in not-so-winner) there were a few notes about them being different in some way, so you may want to poke around there first.

Here are the threads that I dug through as I did my research:

Rockchip Batch Tool v1.5

https://sites.google.com/site/tweakradje/android/rockchip-device

(there's also a v1.6 and v1.7 version if you search around)

romdump

http://vondroid.com/threads/updated-27-08-2012-how-to-dump-current-rom.322/#.Us_-z7TWu-M

reboot app (to avoid the button dance to get into recovery)

http://www.freaktab.com/showthread.php?1050-Reboot-App

Really long, but really informative thread about Rockchimp ROM building and the different variations

http://www.freaktab.com/showthread.php?287-RockChip-ROM-Building-Tips-and-Tricks-by-Finless

Hopefully you can find an existing recovery with an identical recovery.img.cfg as yours, on the same platform, of course. If you do, you should be good to go with kernel replacement.

I failed the first few attempts (before I learned to check the recovery.img.cfg) and booting to recovery just gave me a blank screen.

As long as you have root and can still boot normally (or at least enough to get shell over ADB), you can rewrite your stock recovery (or a new potential replacement) using flash_image

Good luck!!
[Miscellaneous Android Development] xdrc45:
[MENTION=3050092]bhiga[/MENTION]

Man that's some great and very useful information that you've given me. I'll check around and see what more info I can find on this tablet. Hopefully it has a valid kernel in the kernel partition, so that I don't have to go through all the troubles that you did. I'll give the RK tools a go too and hope that they work. I just found out that the pro 7d is a refresh of the vl prestige 7L (it shipped with a single core, rock chip, ICS and no Google play store) and they have a working recovery for the 7L... Not sure if that will help me but I'll investigate into that as well.
[Miscellaneous Android Development] bhiga:
If there is a kernel in your kernel partition, the generic ramdisk recovery on androtab should at least boot and probably work fine.

Otherwise the 7L recovery should give you a starting point.

The recovery extract and rebuild was pretty fast, I think it took 5-10x longer just doing the research digging around.

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] DaRkSe7eN:
CWM

How to flash CWM?...

What is the riht CWM to my Device?..

Model : RK2928sdk
[Miscellaneous Android Development] bhiga:
Check http://androtab.info/clockworkmod/rockchip/

Looks like there aren't many built CWM recoveries for RK2928/2926 devices, so unless you have a valid kernel in your kernel partition and the generic ramdisk image works, or one of the others works properly, it's not going to be straightforward.
[Miscellaneous Android Development] Vicolodo:
hello ,

i would like to modify the updater script of the zip

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

to be loaded on recovery from sdcard

my device is a rockchip 3188, in the script there is assert for rk3066,

so the update stops..

i tried with auto-sign but the signed zip is found not valid by my device...

instead the original zip is found valid....

i dont know why...

perhaps because otacert is missing?

in the new zip i removed it...perhaps it is mandatory?

in this case how can i generate it?.

thanks!

please help me...
[Miscellaneous Android Development] DaRkSe7eN:
[Help] flashing cwm & kernel.

Thanks for the reply.

Now i finally found the right cwm to my device. CWM-based Recovery images for RK2928/RK2926 devices. Thanks for providing the link.

But before i proceed. Do i need to flash RK2928GENERIC_CWM.zip before i proceed flashing cwm via CWM?. Do i need busybox installed before flashing any thing.

--

Off topic question.

- how to unbrick/ flash to stock rom & recovery?. My device is rk2928.
[Miscellaneous Android Development] bhiga:
The check is there so you don't flash the wrong image for the device. Are you trying to modify a 3066 updater to contain a 3188 image?

That doesn't sound like a good idea to me, but I haven't looked at the differences between platforms.

If you already have CWM loaded, then you can update via the zip. But you'd only need to do that to update an already-loaded CWM, otherwise it's a chicken-and-egg scenario - need CWM to install CWM ;)

I recommend using one of the other methods for flashing. I used the root shell method, as the RK tools refused to recognize my tablet.

My understanding is that the Generic version of the recovery should work for most/all device on the specified platform as long as there is a valid kernel in the kernel partition - in my case, there was not, the kernel partition was blank (embedded kernel from the boot/recovery partition gets loaded).

It's worth a try - I tried it first and boot to recovery was just a blank screen which is how I confirmed the kernel partition was empty.

If it does work for you, then that's all you need and you're done.

Unbrick, I don't know. I assume you would need one of the RK flash tools to recognize your tablet. I never got them to work, so brick would've been brick for me. Luckily here we're only working with the recovery so as long as you don't flash the wrong partition or something, you can fix recovery by booting normally and flashing again via ADB (root shell method).

It is important to

back up your ROM partitions before you start flashing anything

!

You definitely will want a backup of your stock recovery so you can restore it if you can't get CWM working.

I used romdump which I mentioned in my earlier post that described how I got CWM on my Insignia Flex 8 (rk3066) tablet, but looks like dump_image in the CWM zips may do the same. I liked romdump because it dumped almost all of the partitions (IIRC, it didn't do the misc partition).

For brick recovery and more in-depth info about how these devices boot and such, check with the folks over at Freaktab and/or Vondroid - they have lots more experience with Rockchip - that's where I learned most of what I know now.
[Miscellaneous Android Development] Vicolodo:
thanks,

i dont know if it is only for 3066,

i see it is under the directory 3188,

and there are two directories, one for 3066 and one for 3188

the script under 3188 seems the same as that under 3066... so perhaps it works also for 3188

i tried loading it from recovery, but i get the error on

assert(getprop("ro.product.device") == "rk3066" || getprop("ro.product.device") == "rk30sdk");

BUT

the package is verified valid for my device , perhaps it is the only zip i found valid to be loaded on recovery

(i have recovery 4.2.01, loaded when i flashed a wrong custom firmware that bricked my device ...that is lewys ROM v2.0)

My device is bricked, no more visible from pc (i tried also to put it into Mask Rom Mode shortening two pins on NAND flash)

this is the last chance...
[Miscellaneous Android Development] bhiga:
:eek: Yeah, that's way beyond my knowledge base.

Definitely ask [MENTION=2864694]fun_[/MENTION] for advice, and/or check with the folks on Freaktab and Vondroid.

Good luck!!
[Miscellaneous Android Development] Shmarkus:
try recovery from here: http://xdaforums.com/devdb/project/?id=2708#downloads or here: http://xdaforums.com/showthread.php?t=2612105
[Miscellaneous Android Development] fun_:
generic image for RK30 and for RK31 are same, it's not mistake.

"ro.product.device" may vary. current assert line is correct for some devices, and wrong for other devices. it can be changed or removed from updater-script.

zip is signed by very common "testkey", but there are also some other methods to install CWM.
[Miscellaneous Android Development] Vicolodo:
thank you,

fortunately i found a tool to sign the zip,

and the zips signed with this tool are accepted by my device...

i already wrote an updater script, that only prints some infos on the screen ...

tried it and it works...

so now i am able to interact with my device and write on it all the stuff i need

now i am searching for an example update script that writes all components...

boot,kernel,system etc

i have all the components .img extracted from the stock whole img with a tool i found on xda...

now i have only to write the updater script...

perhaps do you have an example that works on rk devices?

thanks!!
[Miscellaneous Android Development] grävling:
I think Cass1977 has one. http://xdaforums.com/showthread.php?t=2631876
[Miscellaneous Android Development] xdrc45:
[MENTION=3050092]bhiga[/MENTION]

I got all the RK Tools working and recognizing my tab. I used romdump and got -

boot.img

Recovery.img

System.tar

System.info.gz

Config.gz

Checksum.md5

I extracted the boot.img and got

zImage

Boot.img-cmdline

img-ramdisk

I extracted the stock recovery and got

zImage

Recovery.img-cmdline

img-ramdisk

I'm still not sure if I have a valid kernel in the kernel partition and or what to do next as I didn't have recovery.img.cfg when I extracted the recovery. IMG

This has been a pretty cool experience so far and can't thank you enough for all your help so far
[Miscellaneous Android Development] bhiga:
[MENTION=4644989]xdrc45[/MENTION]

Looks like your recovery is in a different format, unless you're using a different unpack tool or zImage is a folder.

I'd try flashing the generic CWM to try. Worst case it doesn't boot and you just flash your recovery.img back to the recovery partition.

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] xdrc45:
That's what I was thinking since I couldn't find the recovery.cfg. I used RKxxx_firmware_tools to extract the boot and recovery.img. Do I need to put the kernel into the generic cwm?

I just tried to extract the zImage and the recovery.img-cmdline but they fail to extract. It shows them as file. The only folder is the img-ramdisk
[Miscellaneous Android Development] Shmarkus:
Kernel in boot.img is unsigned (the zImage). You can sign it with "rkcrc -k" (https://gitorious.org/rockchip-android/tools/source/9fcc93db2dce873a786b469bc041f7566f38f92b:) and flash it to kernel partition, OR you could pull kernel image with dd (in adb shell type: dd if=/dev/block/mtdbloc<partition number where kernel is> of=/sdcard/kernel.img). Your kernel should be on sdcard now. Just to be sure that it is a working image, check it with hexeditor or similar. It should start with KRNL. After KRNL chars, real kernel image starts with symbols: D3 F0 21 E3

hth
[Miscellaneous Android Development] xdrc45:
[MENTION=4449638]Shmarcus[/MENTION]

Thanks for the information. Just want to say thank you guys for working with me and being patient as well. I'm pretty familiar with most android, but I've never really messed with kernel's, other than flashing them to a device. Lol

If I did pull the kernel with dd command how could I know what partition its in?

The rkcrc -k tool must be for Linux... I wish I had a liux machine. I might have to set up a VM or a dual boot to run Ubuntu, some of this stuff would be much easier
[Miscellaneous Android Development] xdrc45:
Ok I just used a different method to pull a full backup from the device.

I now have the -

kernel.img

recovery.img

boot.img

system.img

backup.img

userdata.img

cache.img

kpanic.img

misc.img

I opened the kernel.img I just pulled with hex editor and the top line was KRNL. So I'm thinking there is a valid kernel in the kernel partition.
[Miscellaneous Android Development] pogodancer:
Which method did you use ?