yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] xdrc45:
[MENTION=4546777]pogodancer[/MENTION]

I found a modified RK Android tool v2.1 by Bob finless with full directions on how to use it and pull a full backup and with a method to reflash the img's back to the device. Check it out, it's a pretty cool tool and really easy to use -

http://www.freaktab.com/showthread.php?10129-Backing-up-your-RK-device-(ROM)-with-the-new-RK-2-1-tool&p=138835&viewfull=1#post138835

You just put the device into bootloader mode connected to the pc and then follow his instructions.
[Miscellaneous Android Development] bhiga:
I forgot to mention that I used the "single" tools button at the bottom of the RK firmware tools, in case you used a different function.

Generic CWM doesn't need modification, it'll fall back to kernel partition since there is no embedded kernel in the recovery.

Looks like you may have a kernel in your partition so flash the generic CWM and see if it boots. :)

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] xdrc45:
[MENTION=3050092]bhiga[/MENTION]

I thinks so too... I've been trying to flash the generic but adb push is giving me "Permission denied error"

I'm trying to figure out how to use terminal to move the files from sdcard. Do the files just go on the root of /dev/ if so I'll just move them with root browser and set permissions and then use terminal
[Miscellaneous Android Development] bhiga:
adb push will likely give you an error because it's not operating as root so it can't write to /dev

You can move the files around with any root-capable file manager. Permissions to make flash_image executable can also be done there, but just as easy in shell (chmod 755 flash_image).

The location of the files don't really matter too much - I copied flash_image from the external SD card into /data/local and left the recovery.img on the external SD card.

Here's what I did. Your paths may be different, especially if your system doesn't mount the sd card as /mnt/external_sd

adb shell
su
cp /mnt/external_sd/flash_image /data/local
chmod 755 /data/local/flash_image
/data/local/flash_image recovery /mnt/external_sd/recovery.img
[Miscellaneous Android Development] xdrc45:
[MENTION=3050092]bhiga[/MENTION]

Success! I ended up installing a generic twrp v2.7 instead of the generic cwm... But either way I now have a recovery. Thanks for all your help, I really appreciate it!
[Miscellaneous Android Development] Shmarkus:
you'd have to set adb to root mode via

adb root

and then push files wherever you need!
[Miscellaneous Android Development] xdrc45:
I'll give that a try and see if it works for adb push
[Miscellaneous Android Development] freibergisch:
Hi,

is there anywhere a CWM Recovery for RK3026 devices?

3026 is new and so I don't know if there is a cwm, yet.

CWM Builder didn't work. So I wanted to ask you :)

Best regards

Marcus
[Miscellaneous Android Development] xdrc45:
[MENTION=2084601]freibergisch[/MENTION]

You should be able to use the generic RK30xxx cwm from androtab here - http://androtab.info/clockworkmod/rockchip/rk3066/

Also on freaktab there is the generic RK30xx twrp, that's what I used. Just select the twrp that that has the same resolution as your tablet, if there's not an exact match to you resolution then select one that is a lower resolution but close to your tablets

http://www.freaktab.com/showthread.php?11324-TWRP-2-7-0-0-For-Rockchip-s

I would also highly recommend to backup your device first before doing anything to it.... You can use this simple and easy tool with full directions to do it -

http://www.freaktab.com/showthread.php?10129-Backing-up-your-RK-device-(ROM)-with-the-new-RK-2-1-tool&p=138835&viewfull=1#post138835
[Miscellaneous Android Development] d1wepn:
I am trying to flash cwm from the stock recovery on my MK908. This work perfectly with a MK808 and this RK30GENERIC_CMW.zip. Just renamed it to update.zip. Android detects the update.zip, flashes it and works great. :D

Is anyone able to modify the install script in the zip so that it checks for RK3188 instead of RK3066 but remain flashable from stock recovery? I have tried to modify myself but no matter which utility I use to remake/sign the zip file the stock recovery says its not a valid update.zip file. :o

Thanks in advance :cool:
[Miscellaneous Android Development] bhiga:
[MENTION=2234343]d1wepn[/MENTION] The 3188 generic from http://androtab.info/clockworkmod/rockchip/rk3188/ doesn't fit the bill?

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] d1wepn:
This is actually the same file as the 3066 generic :(

First line of the updater-script is as follows:

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

If it wasn't for that line checking for the wrong model it would work flawlessly. :) Changing it to this below would fix it, and being able to sign the zip correctly of course.

assert(getprop("ro.product.device") == "rk3188" || getprop("ro.product.device") == "rk31sdk");
[Miscellaneous Android Development] bhiga:
Bummer, sorry, don't know how to sign CWM zips yet.

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] xdrc45:
[MENTION=2234343]d1wepn[/MENTION]

Just a thought but did you try to edit the updater-script with Note Pad++ ?

Also cass1977 said he use this cwm on his RK3188... It looks like the one from androtab but he may have edited it. You could check the updater-script.

You can also try the generic twrp v2.7, it's set to work with all RK devices. You just have to choose a generic version that has the same resolution as your device, or if there's not an exact match then select a lower resolution but as close to your devices as possible.

http://www.freaktab.com/showthread.php?11324-TWRP-2-7-0-0-For-Rockchip-s
[Miscellaneous Android Development] fun_:
I'm sorry for posting silly message...

is there any advantage of my recovery compared to TWRP? (I really don't know well about it)

if nothing, I will close this project. it's better to follow more active project for everyone.
[Miscellaneous Android Development] AbduL_PT:
Please don't, your work is much appreciated.

Guy's please don't spam this thread with things not related with _fun's fantastic CWM.
[Miscellaneous Android Development] fun_:
thank you. there is no spam. I really think there is no reason to use my free time for not better one.

and I never say I will stop all my work.
[Miscellaneous Android Development] pogodancer:
@ fun_

Keep the fire burning please. Thanks for your great job.
[Miscellaneous Android Development] bhiga:
Please continue. I use both CWM and TWRP, and while I find TWRP useful, I like having options and for non-mainstream/popular devices, I really like being able to use the hardware buttons for navigation as CWM does. Sometimes I just don't trust the touchscreen. :)
[Miscellaneous Android Development] fun_:
I really don't know about TWRP. I thought it's good for everyone.

probably I should try myself (if I have enough time...).

and if there is a reason for CWM, I will continue, of course. (but slow, sorry)
[Miscellaneous Android Development] saleandoli@aol.com:
[MENTION=433592]FUN[/MENTION], without your generic CWM I would not have a recovery your work is greatly appreciated and jas been invaluable to many.
[Miscellaneous Android Development] AbduL_PT:
No, they both perform the same operation's.

But TWRP has some refresh problem's on RK31 tablet's.

Yes, you should try it.

There is a reason to continue with CWM. :good:
[Miscellaneous Android Development] hafeez2001:
sir i installed this recovery through "Finless ROM Flash Tool v1.37", when i want to boot to recoevry (through MTK Mobile Uncle Tools or ROM Manager app on the tablet, the tablet reboots with blank screen.

do i have to reflash your attached recovery.img file again and then execute the above command in Terminal Emulator installed in the tablet ?

P.S>

i have rooted the tablet and it does not have volume buttons. only on/off button and the reset hole on the back.

plz help

View attachment 2638311

View attachment 2638312

View attachment 2638313

View attachment 2638314
[Miscellaneous Android Development] bhiga:
Exactly which version did you install?

If you installed the generic ramdisk-only version, blank screen on recovery boot probably means there is no valid kernel in your kernel partition (kernel will load from what is embedded in recovery partition).
[Miscellaneous Android Development] hafeez2001:
should this mean i have to reflash kernel.img with your file recovery.img ?

sir i installed the recovery.img file given in the zip file u attached file RK2928GENERIC_CWM.zip.

thanks for the quick reply sir
[Miscellaneous Android Development] bhiga:
You need to *extract* your current kernel from boot.img or your *original* recovery.img (I hope you saved it) and write that into your kernel *partition*. Then the generic should work.

It would be helpful to know exactly what make and model device you have.

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] hafeez2001:
sir very thankful for your replies !

i have GEEX branded 7 inch tablet with model "278". the screenshots are attached here

View attachment 2638416

View attachment 2638417

View attachment 2638418

View attachment 2638419

and i dumped the tablet's original ROM through AndroidTool v2.1 (Rockchip flasher tools etc.) and separate .img files : recovery.img, boot.img, backup.img, kernel.img etc.....

my device is rk2928sdk board.

now i want to know how to do the procedure u have given in your recent reply to me.

thanks you again !
[Miscellaneous Android Development] bhiga:
Good, you have all your partitions backed up. :) You'll need to extract the embedded kernel.img from your boot.img or original recovery.img (I would use recovery.img to be safe, though both might be the same).

I don't know exactly how to flash the extracted kernel.img to the kernel partition though. I never tried because the RK flash tools didn't work on my tablet, so I could only flash from root shell so I was afraid of brick without being able to recover.

The flash_image that the CWM install script uses might be able to flash_image kernel kernel.img - I really don't know. Need [MENTION=2864694]fun_[/MENTION] wisdom on that. :)
[Miscellaneous Android Development] hafeez2001:
sir very sorry to bother u again and again, but u r dealing with a really noob here !

i dont even know how to extract an .img file.

kindly help me on this also.

a bundle of thanks !
[Miscellaneous Android Development] freibergisch:
I dont know if it reaches to unpack recovery.img and put the kernel from original recovery into the unpacked recovery.. So the recovery comes with the builtin kernel and maybe it boots.. This could help to start in recovery mode..

Gesendet von meinem BRAVIO mit Tapatalk
[Miscellaneous Android Development] bhiga:
I used RK3xxx-Firmware-Tools to unpack the recovery.img to its component files. I'm not sure if that tool works for 29xx platforms, so you may need to find something else.

Yes, that's what I did for the Insignia Flex 8 - pulled the kernel.img from the stock recovery.img and replaced kernel.img of another existing recovery. The trick there is to find an existing recovery that uses the same memory configuration/offsets as your stock recovery, which I believe is stored in recovery.img.cfg
[Miscellaneous Android Development] freibergisch:
I opened it and used the stock recovery.img to extract but there is an error..

Also using the recovery.img extractor on second page did not work..

Maybe for rk3026 we need other tools.. But thank you for the link :)
[Miscellaneous Android Development] bhiga:
Make sure you put the tool on a short path, like c:\rk or something - it has terrible with long/deep paths. Also, be sure to right-click and Run as Administrator if using Win 7

The "old" single-file tool choice is what I used.

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] freibergisch:
Yes I put the files in a shorter path and check it again :) i used the recovery.img extractor.. Without success. But with long path to the img.. Hm will see if shorter path works. Thank you :)

Gesendet von meinem BRAVIO mit Tapatalk

EDIT: d:\rk30ft works! Thanks!! :) TWRP now really works on my ODYS Bravio, CWM now to check! :)
[Miscellaneous Android Development] hafeez2001:
sit thanks a million

it worked :good:: i unpacked my stock recovery with RK3xxx-Firmware-Tools http://www.freaktab.com/showthread.php?6997-RK3xxx-Firmware-Tools

and then build again with your generic ramdisk_only recovery.img.

THANK U VERY MUCH SIR ! :laugh:
[Miscellaneous Android Development] freibergisch:
I built CWM with my zImage. Now I have to set up the recovery.fstab because cwm tells me it can not find the right partitions..

CWM is on the way, I hope :)

http://goo.gl/o58Hyk Here one working CWM with zImage from my ODYS tablet. Maybe it works on other tabs? :)
[Miscellaneous Android Development] fun_:
put proper rknand.ko for your CPU into ramdisk at first.
[Miscellaneous Android Development] Shmarkus:
check out my cwm build sources, maybe they'll come in handy! https://github.com/Shmarkus/android_bootable_recovery
[Miscellaneous Android Development] freibergisch:
Interesting source.. :) could you make a cwm for rk3026? What information do you need? Boot.img and recovery.img (stock)?

Gesendet von meinem BRAVIO mit Tapatalk
[Miscellaneous Android Development] freibergisch:
Recovery and boot.img --> https://dl.dropboxusercontent.com/u/82635069/recovery_boot.zip

Gesendet von meinem BRAVIO mit Tapatalk
[Miscellaneous Android Development] Shmarkus:
Since I do not have rk3026 device, It might be hard and time consuming. If You have the means and will, I suggest you try to port my efforts or find another source that is meant for rk3026 and build the rom for Yourself!

Best of luck!
[Miscellaneous Android Development] freibergisch:
I only need a cwm :) not a whole rom :)

But i could pull cm sources to port your cwm sources.. which sources did you pull for compiling cwm? cm, aosp, omni, ... ? aospa didnt work at my setup.. could not make recovery (unpackbootimg bnot present)

Gesendet von meinem BRAVIO mit Tapatalk
[Miscellaneous Android Development] Shmarkus:
could you please post the output of (as root)

cat /proc/mtd

and

cat /proc/partitions

when in android and when in recovery. I'll see what I can do
[Miscellaneous Android Development] freibergisch:
MTD: https://dl.dropboxusercontent.com/u/82635069/mtd.txt

Partitions: https://dl.dropboxusercontent.com/u/82635069/partitions.txt

Thank you :)

Edit: is the proc/mtd content in recovery other than in android??
[Miscellaneous Android Development] Shmarkus:
Yes, usually it's the parameter partition that shifts the other partitions. I can assume this is the case but just to be on the safe side!

also, please post the content of

cat /proc/cmdline

This can be done in recovery or android, doesnt matter
[Miscellaneous Android Development] freibergisch:
https://dl.dropboxusercontent.com/u/82635069/mtd_rec.txt

Partitions: https://dl.dropboxusercontent.com/u/82635069/partitions_rec.txt

both in recovery (twrp - not stock - but works not because wrong resolution or orientation..).

https://dl.dropboxusercontent.com/u/82635069/cmdline.txt
[Miscellaneous Android Development] fun_:
this doesn't work?

or should I leave this to other people?
[Miscellaneous Android Development] freibergisch:
I dont know where i should find the rknand.ko file? And i had no time to do this last days, sorry :) so i hoped he could build the cwm :) but thank you for your reply.

Gesendet von meinem BRAVIO mit Tapatalk
[Miscellaneous Android Development] Shmarkus:
rknand ko is in recovery and boot.img

I have ported some of my code to 3026 but I cannot be sure it works, I can upload it tomorrow night
[Miscellaneous Android Development] freibergisch:
no problem, I will test it tomorrow.. it works or it works not.. Main thing is that we are one step further :) Because this will be the first working one for this device, sounds brilliant ;) We will see :) Thank you for your work

Last time I looked into my recovery.img I did not find rknand.ko file.. Maybe I should look again tomorrow, when I am at home again.. I'm absent today..
[Miscellaneous Android Development] Shmarkus:
Try this: http://d-h.st/jHH

cfaf5307eb89a962b0c0dcf23e2e5125 recovery.img

but remember: theres 80% chance it wont work. This is build without kernel, so valid kernel in kernel partition is a must!
[Miscellaneous Android Development] freibergisch:
Ok then i will put the kernel into it and give you a report. Thanks a lot for doing this!

Gesendet von meinem BRAVIO mit Tapatalk

---------- Post added at 08:22 AM ---------- Previous post was at 07:41 AM ----------

I got problems with the rebuilding process.. I don't know why but my windows program does not rebuild with zImage.. Maybe I have to use older version.. :(

https://dl.dropboxusercontent.com/u/82635069/zImage.img

Here, maybe you get a workin rebuild.. I will try it in linux later this day..
[Miscellaneous Android Development] bhiga:
Just a general note, deep paths are often problematic for Windows.

-= this post enhanced with bonus mobile typos =-
[Miscellaneous Android Development] freibergisch:
i know, because of this I switched the files to a folder in the root.. :)

But since today it always rebuild with kernel, now it does not.. it's magic?!

---------- Post added at 11:20 AM ---------- Previous post was at 10:41 AM ----------

I got this working.. :) But there are again the following lines:
[Miscellaneous Android Development] ELITAZER:
can I use it with lava etab xtron plus? I have rooted already :), It has rk3066
[Miscellaneous Android Development] xdrc45:
More than likely one of the 2 CWM version should work for you, either the RK3066 generic CWM or a device specific CWM.

The generic cwm requires that you have a valid kernel in the kernel partition.... If this is the case then you can use and write the generic CWM to the device via adb/terminal emulator, using the provided flash_image file to write the recovery.img. to the recovery partition.

If your device doesnt have a kenel in the kernel partition, then you can try and sift through the devices specific CWM's for one that will work/be compatible for your device. This will require more work. You will need to extract your kernel.img and then go through the device specific cwm's and try to find a couple that might be compatible using recovery.img.cfg file. [MENTION=3050092]bhiga[/MENTION] did an EXCELLENT job at explaining the process of adapting a device specific CWM to another device here -

I would also highly recommend that you do a full backup you device with the modified RKTools 2.1, (which includes full directions on how to perform a backup and restore) before doing anything to the device, plus this will also extract your kernel and then you can open the kernel.img with a hex editor (like Neo Hex Editor) and if the first line starts with "KRNL" then you have a dedicated kernel in the kernel partition and you can just use the generic CWM.

http://www.freaktab.com/showthread.php?10129-Backing-up-your-RK-device-(ROM)-with-the-new-RK-2-1-tool
[Miscellaneous Android Development] ELITAZER:
OMG I'm not a dev

Well, by using nandroid online I have done a backup , without the cwm actually Installed I am not familiar with hex edtor and programming I'm just a teen, now listen very carefully, I found the only ROM here http://www.freaktab.com/showthread.php?10688-Lava-Xtron-RileyROM-1-1 can yo tell em how can I flash only the image and not anything else , you have been very helpful But I'm not an expert and only a normal user who knows to root, nandoird scripts etc..OHHH AND SORRY OF THE PREVIOUS MESSAGE, now I will see the kernel in hex editor , please stay connected man!I I am using the root explorer to fing the image and then transfer to a usb stick on to pc and then hex editor..I COULDN'T USE THE ROOT EXPLORER BUT I have a backup and I got a kernel.img opening it now..Uploading it also...so now I see that the first word is KRNL$x, is is safe?Model:JB7+

Battery:65%

Firmware version:4.2.2

Wi-Fi:eek:ff

Status:ROOTED

Resolution:1024*600

Manufacturer:Unknown

Serial:0123456789ABCDEF

IMEI:Unknown

IMSI:Unknown

MAC:Unknown

Android Version:4.2.2

Baseband version:Unknown

Kernel version:rk30sdk-user 4.2.2 JDQ39 eng.dzy.20130506.194800 test-keys

EDIT: Also when I tried to use the stock recovery method I coulndn't doit cause I don't know the steps and adb is not recognizing my tab!
[Miscellaneous Android Development] xdrc45:
No worries... It's ok that your not a dev and it great that your a teen. This is the best time to learn and You can still do this without any problems, it's pretty easy, plus you have support here.

OK technically you can use either adb commands or use terminal emulator to install the recovery. I recommend that you install via adb commands because this is a universal tool for android devices and an excellent learning experience for you in becoming familiar with how things work, plus I still recommend using the modified RK tools 2.1 to get a proper backup of the device. The online nandroid will only be beneficial if you cave a custom recovery already installed.

Ok to get adb working you need to download and install either the Android SDK to the root of your C:\ hard drive on your PC. This will have the adb drivers that you need to get it working. Install the SDK, and update it using the SDK Manager. Inside the "Platform tools" folder is adb. I recommend just using the full Android SDK as this has many beneficial tools and utilities, for android devices. So get that installed. Once installed, turn on USB debugging on the device and then connect it to the PC, open command prompt and type "adb devices" if it's installed correctly it will list "attached devices" with a serial number following.

You said in your pm that your unsure of the RK version. I see it shows as rk30sdk. This is another opportunity to learn how to get this information. You could do this with adb or terminal emulator.

Install a terminal emulator from the play store, you can use something like RomTool Box lite, it has terminal emulator, root browser and other utilities. Open terminal emulator and type -

su

cat /process/cpu info

This command will give you information on the device and the rockchip version.

Yes it looks like you have a valid kernel in the kernel partition. So the RK3066 Generic CWM should work just fine.

Also, once adb is working, you need to boot the device to bootloader mode and install the proper driver for it, the rockusb driver v3.5 from here -http://www.freaktab.com/showthread.php?5173-New-Rockchip-Batch-Tool-v1-7-Plus-v3-5-Drivers

Type -

adb reboot bootloader

The device will reboot to a blanc black screen. This is the bootloader. The PC will recognize it as USB device. Open the PC's device manager. Look for the unknown USB device with a yellow exclamation, right click on it and update the driver, browse and navigate to the rockusb driver v3.5 and install it.

Now you can use the rk tools.

Here's an easy installation guide for the Android SDK. You do need to install the java JDK also. You don't need to install eclipse though.

http://xdaforums.com/showthread.php?t=967290