Hello all,I had bought a local tablet from calcutta called ICE Xtreme on which I had nightmares,but it also helped me learn n now here is it,a short yet complete guide for ur allwinner devices.
Like me,some of u might have been bored enough abt the stock rom that we decide to experiment.since allwinner CPUs can boot over USB(livesuit mode) n SD cards (phoenixcard) we think nothing will b wrong n flash without a full rom backup (i hav a script uploaded here,find it n hav a look), after the flash we find the stock ROM gone,camera,touch,wi-fi etc gone haywires n cache is mounted as SDCARD!!! Yes,those who used livesuit hav been in stuff lik this. Now I was also in one n upon reading alot I hav seen ppl editing bootloaders,using keyboard mouse,plugging HDMI(lcd broken). After a month of fiddling wit my device its time i share a shortcut that can save many hours of ur life.
Also do backup the boot n bootloader on ur pc as sumtimes flashing destroys the SD.
1st step. Backup ur bootloader n boot images. Use "cat dev/block/nandc > sdcard/dump/boot.img" to backup boot..nw backup bootloader the same way,by replacing nandc wit nanda.
Now u use adb pull method to backup ur system,etc,data(its optional,only do it if u want ur apps).n any other folder from the root of ur device.my script can help u do it instantly. Anyways,u must get the etc n system folder.
After that ur free to flash any ROM image through any method (actually,livesuits the best if u can find the img). Now after flash ur device is on right?? Does the SDCARD mount??if no then turn on USB debug,in adb shell type cd dev/block <enter> then type ls n ull see a list of nand partitions,the last one is the SDCARD in raw format.so format is by: su busybox mkfs.vfat dev/block/nand[drive letter,i.e. nandj] n then type vold.ur sdcard will mount.
Now send those boot n bootloader files to SDCARD/dump. U can use mkdir or mannually make the dir n copy. Thn simply type "cat sdcard/dump/boot.img > dev/block/nandc" n same way type nanda n bootloader to restore the bootloader. Now use adb to push the files of ur stock ROM system/vendor/modules(which u backed up earlier) to tablets system/vendor/modules. N the contents of etc folder to etc on the tablet.nw reboot.
Hey!!! Its working.the LCD shift is gone,cam n wi-fi doing good,touch is not reversed or stuff. Congratulations u restored ur tablet,n now running a completely diffrent ROM on it.enjoy.
Heres another shortcut ive learned. U can get any update.zip n convert it to licesuit image. Just extract the system dir. Thn copy it to ur SDCARD. Make modification if needed,copy the modules u backed up.In adb shell type make_ext4fs -s -l 300M -a system <filename.img> (dir of ur system,i.e mnt/sdcard/system) it will make u a .img file which is same as the system.fex file u get when u break a livesuit image. Copy n replace the ROMs boot n bootloader.fex files wit ur backed up boot n bootloader.img (rename .img to .fex) pack the image again to livesuit format n burn it. It will install like a normal ROM. BUT MAKE SURE FILE PERMISSIONS OF READ WRITE N EXECUTE IS INTACT. ELSE ULL ENJOY HOURS OF BOOTANIMATION. but if ur stuck use the method above n flash any other ROM n fix the RON fr ur device. Guys ROM developing n editing fr allwinner devices are not easy...BTW id lik to thank user [iamabadduck] fr his actual A10 backup script. On which i made mine. Im still doing experiments. Hope this info i shared makes the readers modest enough to make the hit thanks. Bye. [ ill b around,so if any quests,ill ans them].
I was very excited to see someone finally post a guide for these mysterious tablets! Thank you!
However, I ran into some difficulties trying to make use of them, but I think this has more to do with my hardware and trying to match it with the appropriate ROM and compatibility zip.
You see, I have a Kocaso M1060W. It's a very nice little tablet but trying to identify it has been difficult. As far I can tell, it's a clone of the Protab2XXL (I don't know what version) or something called the BC1077. It seems easier identifying other Allwinner A10's, apparently. I know some identifying information can be found in the build.prop file and that's how I figured out the tablets of which it is a clone. I even tried finding a database of different ImageSuit images I could try to use, but either there is none or my Google skills are suffering. Does it matter that Kocaso chose to go with PhoenixCard for flashing their tablets? Some documentation suggests the images for both are the same.
Can you help me find documentation that would help me identify the board and the hardware? Let me know what information you need from the tablet, and I will get it to you. Identification would go a long way towards me making use of your steps.
Also, a question. After the rom is flashed and you "adb shell" in, you have me trying to mount the sdcard directory via the nand block devices, and then entering "vold". It doesn't error but nothing seems to happen. Even stranger, running "mount" tells me that it's done something. Is it because most of the ROM flashes require the data wipe that I should assume I have the capability to read/write within the SDCARD directory?
Allwinner A10 ghost touch (Icoo D70W, goodix chip)
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Compatability
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
If you could Post an lsmod from both the Working Firmware and the Non-Working I will take a swing at answering your question...The problem is likely one compat file is installing drivers for one of Your pieces of hardware and not the other and the other compat file is istalling the driver for the other piece but not the One... confusing sounding...
But Bottom Line is If I had the Lsmod from the working Hardware and the 2 compatability files you tried I could likely alter one of the compatability files to cover All of your hardware.
Or better yet pull the Bootloader.img and the Boot.img out of your Tab and send them to me...
you can do this by opening a cmd window from a directory where you wish to store the .img files then type the following :
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
That will give you the Boot.img (named nandc-root.img)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
That will give the bootloader.img (named nanda-bootloader.img)
send those from both your OEM Rom that is working and the Target Rom you wish to make work .... from that I can either write a compat patch for it or send back the edited ones from your Target Rom (the one you wish to work)
Srry i cudnt keep my promise of being around. Had been pretty busy looking for stock JB ROMs in livesuit format. Found some. Some worked n some didnt. Will abt the touchscreen issue if that Rom has a focaltech ftx_5x touchscreen its broken. U hav to compile it again leaving out the multitouch part in a header file. Do a google search. There r alot of articles. N abt da nand part well not all roms break the internal SD partition. The busybox thing u do only when ur internal cards dont mount. It will NOT WORK FOR A MICROSD IF U HAV ONE. Its generally mounted as extsd.
Try reading from here:
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520943
It's a thread about the allwinner A10 or EKEN T01A.. it shows how to reflash to original and updated EKEN firmwares via livesuit. And also i think they mentioned something about touchscreen issues. Hope it helps
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
accessing nand
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
nacxo said:
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
Click to expand...
Click to collapse
You need to edit your script.bin inside the bootloader.img... there is a utility to do this on techknow.me...
to do it manually you need to extract the script.bin file from the bootloader.img ... easiest way is from adb shell
Open a windows command window (this assumes you have adb.exe in your Path .. if not you must do this from the
same folder where adb.exe is located)
type the following
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img"
adb pull /mnt/sdcard/nanda-bootloader.img
this will place a file called nanda-bootloader.img in the folder where you ran the windows command window.
Now copy the file to your Linux Machine or VM
and from a terminal do the following:
mkdir bootloader
sudo mount -t vfat ./nanda-bootloader.img bootloader
This mounts the bootloader image to the bootloader folder.... in the bootloader folder copy the script.bin file to another location for editing.
to edit it must be converted to fex... you will need the fex tools for this I have them posted here: http://www.4shared.com/zip/Nzn6PV-b/tools.html
your Linux machine has to be x64 for those to work.
from the folder containing the tools folder and script.bin file open a terminal and do the following:
./tools/bin2fex script.bin > script.fex
this will create the script.fex file which is editable in a linux text editor, open the file and edit the [lcd0_para] section
to correct your screen shift ... the exact settings needed are impossible for me to determine as I do not
have your tab nor the rom you originally had on it.. if you have the original rom available (with screen position correct)
you can pull the script.bin from that rom and replace the entire [lcd0_para] section with the same section from your working rom
to solve the issue.
once edited convert back to .bin from a terminal with the following commands:
./tool/fex2bin script.fex > script.bin
now open the bootloader folder as superuser and delete the script.bin and script0.bin located inside...
copy the new script.bin file in and also copy it and rename the copy to script0.bin and place that there as well.
then from folder containing bootloader folder open a terminal and do the following:
sudo umount bootloader
now copy nanda-bootloader.img to windows machine.
open a Command window in the folder containing your new nanda-bootloader.img file and do the following
adb push nanda-bootloader.img /mnt/sdcard
adb shell su -c "cat /mnt/sdcard/nanda-bootloader.img > /dev/block/nanda"
adb shell rm /mnt/sdcard/nanda-bootloader.img
adb shell su -c "sync"
adb shell su -c "reboot"
if all was done properly your tab should now reboot with the correct screen geometry. The utility I mentioned does
pretty much all of this for you, but i cannot link it here as it is on techknow.me which requires registration to
download ... and the rules forbid links to such sites here.
I hope that all helps you.
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
djahma said:
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
Click to expand...
Click to collapse
You must have the ADB drivers installed and know where they are located, placing them in your Path statement is a good idea if you intend to do much ROM editing or direct Tablet commands from and adb shell.
NOTE: To open a command window from any folder on your computer in Explorer browse to the folder you want to open command window from
then in an area of the folder window that is empty right click mouse while holding shift then select open command window here
Once you have ADB INstalled, if the adb.exe is in your path open a command window from any folder you like on windows and type the commands in the command window. If ADB.exe is not in your path you must open a command window in the folder containing adb.exe
(Usually the android SDK Platform tools folder)
I Hope that helps
Thanks fsebentley, I've now copied all nandX partitions.
what I'm trying to do now, is to create a bootable sd card. I believe I must tailor u-boot.bin to boot a specific kernel with my specific hardware setup.
I've found a lot of resource for arm boards, but almost none for tablets, except for direct flashing but I'm not ready to go this far.
So, do you know about a nice tool to read what's in u-boot.bin and eventually modify it?
Touchpad driver
Hi!
I need some help!! I want to include touchpad driver an cm9 installer because when I instal the system with CWM but the touchpad not working!!!
Here is the topic where you can find the ROM: http://forum.xda-developers.com/show....php?t=1861445
Sorry I write here because I can't write in the original topic.
Thank for help!!!
Apad 711 stuck at boot logo
Hi Guys,
I need help. one of my friend has a Apad711 tablet and his stock android recovery was changed by cwm 5.08 incorrect version and hence the power + - or power button was not responding.
I took over and had flashed 6.0.2 8 cwm by following this forum http://forum.xda-developers.com/showthread.php?t=2189640
and recovery was working properly, but then i though of upgrading it to cyanogen mod 9 and downloaded the files using this forum
http://forum.xda-developers.com/showthread.php?t=1760929
however after the update was completed the touchscreen didnt work and I had to connect a usb OTG cable along with usb mouse to get into recovery. I then did a little research and tried flashing a couple of compatibility zip
711i_compatibility_1.1.0.zip, lyf1_compatibility_1.1.0.zip, 711i_compatibility_1.2.0.zip, lyf1_compatibility_1.2.0.zip which had similar specs from this website http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
but even after doing so touchscreen,camers etc didnt work.
since i had made a backup of stock rom using cwm before flashing cyanogenmod 9 i thought of restoring it back using cwm 6.0.2.8
i was able to restore the back up but to my surprise i am now stuck at apad boot logo and cannot boot to recovery using the volume - and power key. i tried to connect the tablet to pc so that i can get into adb interface and reboot to recovery but the computer detects the tab as unknown device
I now need help to get into recovery and flash a rom that would make it work or complete tutorial to install/flash a new /stock rom or cyanogenmod to get the device back to life.
please refer to the manufacturers website link listed below for specs:--
http://www.apadtab.com/711_spec.php
Any help would be greatly appreciated.
allwinner a10., broken bootloader
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
sammekevremde said:
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
Click to expand...
Click to collapse
If you can't flash it from your pc, create a bootable sd card. For example, you could copy your berryboot image to the sd card and boot from it.
Supposedly, you saved your tablet nand into an image before messing up with that nand. Once you boot from sd, flash the nand again with that saved image. Good luck to you
need a little help
i wnt to increase resolution of my a10 tab from 800x480 to 1024x600....to do so i need to edit the bootloader(bootloader.fex)
but,the problem is i can't edit the bootloader.fex correctly......how to edit properly
Hello,
THBK1-10 is a cheap dual system (Android 4.2.2 /Windows 8.1) tablet based on Bay Trail (Intel Atom Z3740D). More details http://www.thomsoncomputing.eu/dualboot.html
I'm trying to hack it, and especially get root and use non-signed zip in recovery. Basically i'm stuck at theses points, and i'm requesting directions to continue the work.
I have posted in W8 section, but obviously, this is no longer the place
General
------------
* i can use a work-around to write system (/system, /data) partitions
* i can flash signed updates via recovery
* google apps are working flawesly. Only thing is to keep original files (stock keyboard and layout)
-> i would like to flash non-signed zip via recovery, but i guess i have to build a custom recovery, or can i exploit something else ?
Root:
-------
* no auto root is working (z4root, towelRoot). Regarding towelRoot, i tryed each 8 common parameters, and i don't really know how to do others. I have also heard this is only working in 4.4.2+
* pushing su is not working. When i'm launching it, let's say from terminal, i have a code 255 return (-1). Tested with both arm and x86 version (i'm still wondering why arm su is also returning -1, i would have expect a non valid binary. Or perhaps my x86 version is bad ?
-> i'm still trying to dig this issue, and idea on how i could do ? i believe running SU was enough... but it seems not. Any idea ?
Many thanks !
Bump. the way it is booting is based on ramdisk images (one for normal android boot, one for android recovery).
I have acces to theses img, and i can, with hexedit (perhaps mounting them directly at a filesystem), view the whole init sequence.
My question is : what triggers the root invalidation ? AFAIK, everything is done as root (mounting FS, updating permissions, etc....). Basically i can't really figure how it is handled.
Thank you !
Solved !
Graveen said:
Solved !
Click to expand...
Click to collapse
Woaw ! I'm very happy to see that somebody tried and succeed to root the THBK1 ! Please can you share your method in a tutorial when you'll have time ? :laugh:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Yes ! I confirm ! Graveen has installed GAPPS on Thomoson THBK1 / Danew Dualboot tablet with sucess ! I'm not familiarised with linux environnement and realize it, but it requires some knowledges of linux command (coLinux especially)
Graveen is the only one users identified that it can put GAPPS on android environnement concerning this tablet.
Big thanks to him !
Graveen said:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Click to expand...
Click to collapse
7600
I own a Cube U100GT and it's one of the many Chinese brothers of your THBK1-10. But mine came only with W 8.1.
I just start looking for a dual boot solution and I'm happy to know that it's is possible.
I don't need root for while, just play some games and apps.
So the original Android "ROM" of the tablet can do the job.
My version have 64Gb SSD and I've already resize the Win partition to make room for a new system.
Where can I look for a dual boot tuto and find this Android version?
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: http://www.danew.com/support-pilotes-manuels.php?type=218&produit=219 but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Graveen said:
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Click to expand...
Click to collapse
The partition list is the standard for a windows installation (but no windows image on the end):
1: 300 Mb (Windows RE)
2: 100 Mb (System)
3: The rest (Windows). My SSD is 64Gb.
My tablet already comes with a dedicated keyboard cover, so I have full access to to UEFI Bios.
There's a lot of numbers:
Aptio Setup Utility Version 2.16.1242
Vendor - AMI
Core Version - 5.008
Project Version - 3BAGR 0.03
EC FW Version - 201401101A
Intel GOP driver - 7.0.1029
Sec RC Version - 00.05.00.00
TXE FW Version - 01.00.02.1060
I found the drivers pack for windows 8 and so I could install my PT-BR edition of W81. And reserve 20Gb at the end for another OS.
It's my first UEFI machine and I'm completely lost. There's a lot of options and I can't understand a quarter of that.
On the Tabletrepublic forum someone said that my bios recuse everything except a Windows pendrive. If is true, there's no way to put Android but changing/patching the UEFI.
Android x86 is for desktops right? And the Intel site, can I find Android images there?
Thank you. What i'll do is to check if my bios is identical to yours, because there are effectively numerous options. Then, i could finsh to dump my android partitions and let you play with them.
Honestly, the trick is the OS selection system, which is bring by the EFI bootloader (and certainly a dedicated partition). Once selection is done, another EFI bootloader (windows only) is called.
let's continue here: http://forum.xda-developers.com/showthread.php?t=2799404
Here's a noob question for y'all.
What criteria should I be applying when looking for a replacement/upgraded ROM for my tablet? The CPU architecture? The type of processor chip? The kernel version? The EXACT name/model number of my device? A combination of all these with some other ones too?
I recently bought an Odys Fusion 7-inch tablet running JB 4.1.1. According to CPU-Z it is Rockchip RK3066 with ARM Cortex-A9, dual-core 1.5GHz, kernel architecture armv7l, kernel version 3.0.8+.
The device is rooted (see below for a quick summary of how I did it) and I have also made a Nandroid backup of the stock factory ROM on to my PC (details likewise below) but I haven't yet tried a recovery with this file so I don't know if it 'works'.
As my tablet is a fairly non-run-of-the-mill make, and an even more obscure (now discontinued) model name, it is extremely difficult to find any information at all about it on the internet, even on this illustrious forum.
In general, I am fairly happy with this tablet, although I have a Bluetooth problem which I'm hoping will be solved by upgrading to 4.2x or even 4.3 (KitKat 4.4 would be nice but I think that would be beyond the realms of possibility).
The support department at Odys (aka Axdia) told me there would be no further OTA firmware updates. They also hinted that this particular device would be unable to cope with a higher OS version than I already have but I find this hard to believe.
How can I find out what is the highest API level (ie operating system version) my tablet can sustain, based on its hardware/current kernel?
http://forum.xda-developers.com/showthread.php?t=2108704
For example, I found in this forum the above-mentioned link for Oma's ROM which led me to his Crew RKTablets Genio AOSP 4.2.2 v3.3 – 20.11.2013 ROM which says it is also for the RK3066 and will run on 3.0.8+. Is it safe to flash my Fusion with this as it is intended for an Odys Genio (also no online information/specs)? If I brick my device with an incompatible ROM image, is it irreversible or can I can get back to where I was with my Nandroid backup or with a factory reset? Also, I don't understand what all the other associated downloads on the same web page as this ROM are for, eg format_NAND_fix, extSD_to_NAND, tablet and phablet UIs, homebrew kernel & CC kernel. Anyone care to explain for me please?
Thanx in advance peeps............
Disclaimer: these methods worked for me on my Odys Fusion. They may not work on your Fusion or other Odys tablet or other make of tablet. I put them here for guidance only - use them at your own risk!!
[How I rooted my Fusion: if you don't have the ADB drivers already installed on your PC, search on Google for the file adb-1.0.29.7z and unzip it. Copy from the rktools folder the file "android_winusb.inf" and move it to the usb_driver folder and OVERWRITE the file with the same name already there. Turn on your tablet, and in Settings>>>Developer Options put a tick in USB Debugging. Download from kingoapp.com or CNET the Android Root program "android_root.exe". Connect your tablet to the PC with the USB cable, preferably direct and not to a hub. If it needs the drivers, point it to the usb_driver folder containing that file you just copied. You should now see the ADB drivers in Device Manager. Run the Kingo program on your PC as Adminstrator, it should find after a few seconds the connected tablet, press 'Root' and it will take about 5 minutes. Disconnect the tablet using the Safely Remove Hardware icon in the system tray and unplug the cable. Reboot the tablet. Check the rooting was successful with the free app Root Checker Basic from the Play Store. Don't forget to uncheck USB debugging when you're done otherwise the normal USB Mass Storage operations will not work. This Kingo software can also be unused to unroot at any time you need to in the future.]
[How I made a Nandroid backup: No need to reboot into the bootloader this way but it does require root access. With your tablet on, download the two apps Busybox (free or pro version) and Online Nandroid Backup (H3RRT1C) (free or pro version) by Thomas Otero/Ameer Dawood and install them. Run the latter on your tablet (no connection with PC necessary) but check settings page carefully first. (I intended to do my backup to an empty external micro-SD card but I inadvertently selected the internal SD card. Luckily I had a enough space (5GB in total, 2.1 GB currently in use) to store it there but I'm sure the program would have told me if there wasn't. No problem - after the backup finished, I just copied the whole folder to the micro-SD card and then backed it up on my PC with a card reader and also to my Google Drive account for safekeeping). The whole backup process took about 8 minutes with clear on-screen infos about its progress and it produced a file about 1.1 GB in size which tallies with Settings>>>Storage figures. Afterwards, I uninstalled both apps. Like I said above, I haven't yet tested the validity and integrity of this backup by doing a recovery with it. Judging by the size of the file it is only my system that it has backed up, not my apps or SD card contents; these are all on my PC anyway.]
Example output log of Online Nandroid (some lines removed for reasons of clarity):
Starting backup...
Running with the following commands: -o --utc --storage /external_sd -pd -r
Using ash Shell
##########################################
Online Nandroid Backup v9.51
* A tool to perform a nandroid backup
without booting into recovery.
* It is fully compatible with nandroid.
* Type 'onandroid --help' for usage
instructions.
* Created by Ameer Dawood
##########################################
Starting time: Using busybox from: /data/data/com.h3r3t1c.onnandbup/files/busybox
Checking for root permissions...
Root permissions acquired!
Analysing battery level...
Sufficient battery available!
Checking version of BusyBox installed...
BusyBox version 1.20 or above installed!
.
.
.
.
Backing up the old backup for replace operation... 100%
Backing up /boot........... 100%
Backing up /recovery........ 100%
Backing up /kernel........... 100%
Backing up /system............................................................................... 100%
Backing up /data............................................................................... 100%
Backing up /cache... 100%
Backing up /.android_secure............................ 100%
.
.
.
.
Finish time: Online Nandroid Backup Completed in 8 minutes 18 seconds!
exitcode [0]
I'm badly need some expert advise.
.My china clone without name (rockchip-rk31sdk-WAWJMDN1KN).I decide to go ahead and try some custom rom using RKAndroidTool.
I did not realize that by cleaning IDB I will low level format..Before doing that I did save few pictures and run log via "android studio" also I backup whole unit via CWM hoping I will always have access to recovery.Unfortunately that not the case.The good think I still have access to RKAndroidTool( the tool is recognizing my device).There is the link to my CWM backup if may help
https://mega.nz/#!g8YgVKaa!209scxKfT...lRZ454peCCCsgU
https://mega.nz/#!gwRGhC7B!KFvTGpp4x...M2AHOKjT43VPQI
Inside that CWM backup is kernel.bin, system.bin recovery bin all
large sizes files (complete CWM of my last working tablet rk3188). Please ask me for pass to open 2x rar.
Maybe You will be able to advice me how to make proper files to revive my system from that backup I have, or help me some how to get CWM recovery working so I can use my CWM backup or any other way to make this tab back to life again.
Perhaps someone will give me idea to allocate proper parameter for recovery , kernel , boot , etc...
Usual location for tablet RK3188 Cortex A9 Quad core 1.6 ghz Governor interactive, Kernel 3.0.36+ ,Board hardware RK30Board/ 0000, Android 4.2.2 ;eng.root 20130912.185132 sdk 17, Display 1280x800; dpi;160 size 9.4'
GPU:Mali-400MP, RAM: 2048 Flash:32 gb Build in:16gb actual, wifi, usb, Bluetooth gps= all yes, camer 5MP additional 1.9MP.
Many thanks for your kindness and time.
Adam
styropian said:
I'm badly need some expert advise.
.My china clone without name (rockchip-rk31sdk-WAWJMDN1KN).I decide to go ahead and try some custom rom using RKAndroidTool.
I did not realize that by cleaning IDB I will low level format..Before doing that I did save few pictures and run log via "android studio" also I backup whole unit via CWM hoping I will always have access to recovery.Unfortunately that not the case.The good think I still have access to RKAndroidTool( the tool is recognizing my device).There is the link to my CWM backup if may help
https://mega.nz/#!g8YgVKaa!209scxKfT...lRZ454peCCCsgU
https://mega.nz/#!gwRGhC7B!KFvTGpp4x...M2AHOKjT43VPQI
Inside that CWM backup is kernel.bin, system.bin recovery bin all
large sizes files (complete CWM of my last working tablet rk3188). Please ask me for pass to open 2x rar.
Maybe You will be able to advice me how to make proper files to revive my system from that backup I have, or help me some how to get CWM recovery working so I can use my CWM backup or any other way to make this tab back to life again.
Perhaps someone will give me idea to allocate proper parameter for recovery , kernel , boot , etc...
Usual location for tablet RK3188 Cortex A9 Quad core 1.6 ghz Governor interactive, Kernel 3.0.36+ ,Board hardware RK30Board/ 0000, Android 4.2.2 ;eng.root 20130912.185132 sdk 17, Display 1280x800; dpi;160 size 9.4'
GPU:Mali-400MP, RAM: 2048 Flash:32 gb Build in:16gb actual, wifi, usb, Bluetooth gps= all yes, camer 5MP additional 1.9MP.
Many thanks for your kindness and time.
Adam
Click to expand...
Click to collapse
UPDATE____
RK3188 adb is running no screen__help PLEASE
After erasing IDB in my unknown china tablet and loosing my whole system I was able to load different custom firmware from Chuwi v88 + different kernel and my Tab popup in windows showing 2 extra drives F and G.I did open android studio and notice access to adb and all activity in my android.The RKandroidTool also recognizing my tab.
No reaction to power button only automatically connecting to my comp ( black screen on my tab).
I have original CWM backup of my device.
Can someone advise me how to access recovery from this point or find the way to completely start my tablet.Maybe is possible to recover CWM from adb?I will need some help to use a proper commands perhaps in adb.