[firomi]

Hello

You are doing it on your own risk i dont care if u brick your device

Take special care about touch driver if u flash wrong u may briock your digitalizer

Take care about afi config becouse if sth went wrong u wont be able to connect your tab to computer

Always check do you know how to connect adfu (connect to pc) on powered off tab before u flash new firmware!

Becouse some tablets arent support by their sallers and we are all know how atm7029 is weak on old 4.1.1 android and old 4.2.2 on newest ainol fw is liitle better but it still need to be update I wannt to tell you how to port any fw on your device.

Ofcourse sometimes you didnt get 100% working fw becouse some fw are using lcd0 not lvds other wifi fw may inculde bt module or may doesnt include bt so this tutorial is only "how to make bootable any fw on your device" then to make it 100% work u need to make more changes in porting fw.

I flashed touch driver for ainol novo 7 venus to my bmorn k22 and then my digitalizer get brick, work with not correct points etc becouse in my stock fw touch driver doesnt include fw for digitalizer i started looking for solution flashing other one fw for tablet "looks like my". This wont help me then i start dont having care about do i brick my device or not i flashed on my tab arround 100~~ different firmwares for other tablet my tab is 7 inch i flashed for 10inch also. i didnt care about it. Sometimes i flshed fw without any changes. And what i saw 95% of modules and boot.img are universal if u use it with their system.img. I know that it can looks wiried that we have a lot of different tablets and producents may said that same is only cpu and graphics but firmwares works on any device same. I was close to brick only 3 times. first when i flashed fw for colorovo citi vision 2.1 becouse there wer home button to enter adfu mode. 2. when i flashed crystal 2 newest fw without any changes becouse newest (01.14.2014) isnt include "adfu keys" in afi config and i coudnt get recovery or connect my tab to pad product tool. 3. when i flashed fw for newsmy 7 (i dont know why). So i have to say thats its rlly hard to brick our device. Once time i flashed fw for atm7021 and i didnt get brick too.

Ok lets start

what we need?

winrar 7zip notepad++ ect

Ultraiso or any other program which will able to open unpack and save misc.img.

Actions PAD Firmware Modify Tools (v1.7 or newer) (PFM)

http://www.slatedroid.com/topic/94521-actions-pad-tools-developer-editions/

1.Fw for your device(if u dont have it may be backup specila misc.img and build.prop)

2.Fw which u want to port.

1.

Unpac misc.img for your own device to any folder





open Yor fw in PFM



open build prop and save it



now open program files->afi.cfg



open pinctr.cfg and chack do your fw use lcd0 or lvds



ok now open firmware which u want to port



make sure have same value in afi.cnf becouse if isnt u wont able to connect adfu on powered of tab if sth went wrong and u will have problem



check pinctr.cfg



if fw to port include lcd0 and your value is lvds i prefer u to use other fw to port but if u still want to port then at last step u have to replace in misc.img/modules

atv5202_de.ko

atv5202_backlight.ko

atv5202_fb.ko

atv5202_lcd.ko

but i have to say that atv5202_de.ko isnt universal so if u have android 4.1 then u can replace it in 4.1 if 4.2(with galcore 170kb) to 4.2(with galcore 170kb) if 4.2(with galcore 188kb) u can raplece ist only in 4.2(with galcore 188kb) but it wont work always

also u have to replace in /misc/

boot_lcd.bin

 

[firomi]

open build.prop there: and change it to correct value

the most important value is:
ro.sf.hwrotation=270 change it to value from your build.prop
ro.sf.hdmi_rotation=0 change it to value from your build.prop
ro.sf.default_rotation=1 change it to value from your build.prop

if u have one camera delete this (if fw is for one camera add this)
ro.camerahal.prevres1=QCIF,CIF,QVGA,VGA
ro.camerahal.imageres1=QVGA,VGA
ro.camerahal.prevresdft1=VGA
ro.camerahal.imageresdft1=VGA
ro.camerahal.fpsdft1=30
ok save and go to program files change this



and edit this





now save your new fw go to folder where did u save it
open misc.img and replace your modules for camera, touch, gsensor



save it and its ready to flash

If sth isnt clear post here

devices used in this tutorial
my :
http://www.pentagram.pl/produkty/tablety/quadra-7-ultra-slim
my fw:
https://s3-eu-west-1.amazonaws.com/fs.siteor.com/pentagram/files/Downloads/Quadra_7_US_Android_4_2.zip
ported:
http://www.tablet.globo.com.pl/
ported fw
http://pan.baidu.com/s/1gdywFAV

Fast FAQ For PAD PRODUCT TOOL(PPT) ISSUE

1.PPT crash when u chose .fw
Make sure that all files are in folder with example.fw file(example.fw, misc.img, system.img, rec.img .... data and databak if needed)
If Your examlpe.fw is rlly deep lik c:/x/x/x/x/x/x/x/x/x/x/x/s/s/xs/example.fw chage it to c:/firmware/example.fw

2.PPT cant load partition for example (!ext4)
download file which pad dont want to load or instal older pad tool or newer if u are using old one

3.PPT do not recognize your device (DOWN button dont flash green) or after connect tab and push button down it flash in 2s~ and call u back that its succesful but it isnt
A) Go to settings->developer options->chose debuging on (v)
still same issue
B) Turn off your tablet
connect your tablet to pc
push both volume if battery icon shows push power also (still hold both volume button)
You wont show any difference on your tab it will still blackscreen you have to look on pad product tool during hold buttons
If cant connect unplug usb cable then plug it once again push power button for arround 10 secound then hold both volume etc
If still PPT still do not reconize your tablet
C) Check other usb cable
D) uninstal PPT and turn off, disable driver signature for example in win 8

Then instal PPT once again and follow step B once again

E) If still cant connect u can follow this instruction on same one on slatedroid i dont have time to found it
http://forum.xda-developers.com/showthread.php?t=2537189

4. PPT turn red on 35% of flashing
You checked wrong example.fw for example partition size is set to 360mb and your system.img after flash is 480mb

5.PPT turned red on 15% of flashing
You checked wrong example.fw becouse there is to much ram raise

6. PPt flash firmware normal but after bootlogo u see only blacksreen with some lights
Your fw is issue for example galcore.ko for 4.1 and system.img for 4.2

You can add some tweaks to make your firmware faster etc:
1.Edit FMTool.cfg in program files and replace:

REPLACE&EDIT = "FMTool.cfg";
REPLACE&EDIT = "afi.cfg";

REPLACE&EDIT = "misc.img:\bin_cfg.xml";
REPLACE&EDIT = "misc.img:\config.xml" & "config.xml";
REPLACE&EDIT = "misc.img:\gpiocfg.xml" & "gpiocfg.xml";
REPLACE&EDIT = "misc.img:\pinctrl.xml" & "pinctrl.xml";

REPLACE&EDIT = "misc.img:\boot.img:\init.extra_modules.rc";
REPLACE = "misc.img:\modules\gsensor_*.ko";
REPLACE = "misc.img:\modules\camera_*.ko";
REPLACE = "misc.img:\modules\ctp_*.ko";
REPLACE = "misc.img:\modules\act_vibrate.ko";

REPLACE&EDIT = "misc.img:\boot.img:\init.modules.rc";
REPLACE = "misc.img:\modules\atv5202_lcd.ko";
REPLACE = "misc.img:\modules\atv5202_backlight.ko";
REPLACE = "misc.img:\modules\atc260x_adckeypad.ko";

REPLACE = "misc.img:\lpow_pic.bin";
REPLACE = "misc.img:\boot_pic.bin";
REPLACE = "misc.img:\charge_anim_pic.bin";

REPLACE&EDIT = "system.img:\build.prop";
REPLACE = "system.img:\app\Settings.apk";
REPLACE = "system.img:\app\Settings.odex";
REPLACE = "system.img:\app\Laucnher2.apk";
REPLACE = "system.img:\app\Laucnher2.odex";
REPLACE = "system.img:\app\SystemUI.apk";
REPLACE = "system.img:\app\SystemUI.odex";
REPLACE = "system.img:\framework\framework-res.apk"

REPLACE = "misc.img:\boot.img:\initlogo.rle";
REPLACE&EDIT = "misc.img:\boot.img:\default.prop";
REPLACE&EDIT = "misc.img:\boot.img:\charger";
REPLACE&EDIT = "misc.img:\boot.img:\cp_vendor_app.sh";
REPLACE&EDIT = "misc.img:\boot.img:\fstab.gs702a";
REPLACE&EDIT = "misc.img:\boot.img:\fstab.sdboot.gs702a";
REPLACE&EDIT = "misc.img:\boot.img:\init";
REPLACE&EDIT = "misc.img:\boot.img:\init.eth0.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.goldfish.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.gs702a.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.gs702a.sdboot.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.gs702a.usb.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.modules.sdboot.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.quickboot.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.trace.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.usb.rc";
REPLACE&EDIT = "misc.img:\boot.img:\init.wifi.rc";
REPLACE&EDIT = "misc.img:\boot.img:\quickboot.sh";
REPLACE&EDIT = "misc.img:\boot.img:\ueventd.goldfish.rc";
REPLACE&EDIT = "misc.img:\boot.img:\ueventd.gs702a.rc";
REPLACE&EDIT = "misc.img:\boot.img:\ueventd.rc";
REPLACE&EDIT = "misc.img:\boot.img:\usbmond.sh";
REPLACE&EDIT = "misc.img:\boot.img:\lib\modules\atv5202_mmc.ko";
REPLACE&EDIT = "misc.img:\boot.img:\lib\modules\blk1drv.ko";
REPLACE&EDIT = "misc.img:\boot.img:\lib\modules\blk2drv.ko";
REPLACE&EDIT = "misc.img:\boot.img:\lib\modules\mmc_core.ko";
REPLACE&EDIT = "misc.img:\boot.img:\lib\modules\quickboot.ko";
REPLACE&EDIT = "misc.img:\boot.img:\lib\modules\tsd_block.ko";



save and now u r able to edit files which are in boot.img

as we know after each one reboot our first core is "conservativ or ondamended" to fix it edit init.gs702a.rc



change chmod to 777

to fix 252 scaling first core after rebot edit init.rc



change chmod to 777

to make fw little faster in quadrant and games u can edit afi.cfg



and change ddr scale to 533 its safe if u change it to 600 then when u want to flash your fw pad tool wit crash at 15% (not on all devices but on most so 215 is safe value)

 

[sad_but_cool1]

Cool....will test and feed back my experiment here soon.
Thank you!!

 

[Alv]

Thanks!

I'll try this to port your rom to my tablet. With this and cwm's compatibility rom maker, our pieces of shit could be tablets!

 

[firomi]

im w8 for your experience

tomorrow i gonna add some tricks to this tutorial

 

[dimomnia]

hi

i ve to thank you first for your very nice and usefull post.

some questions

1) any rom means really any rom? i can port slims roms or pandroid roms to my hero2, using directions above?

2) the final result of the porting will be in flashable mode with tprw or cwm recovery ? or the pad tool will be needed?

3)i thing that arrows in lines, showing what replacing where and some more details for the procedure will be extremelly helpfull.

cant wait to try...

thanx again for your post

 

[firomi]

Hello,

1. any rom mean any stock rom mean any rom made for pad product tool. as information in post i have rebranded bmorn k22 and i flashed arround 100 different fw for other tablet and i was close brick only 3 times once when i flashed fw for newsmy 7 once when i flashed fw for colorovo visin tab 2.1(u wont found it in internet) and once when i flashed fw for crystal 2 without any changes becouse in newest crystal 2 fw there is no "adfu" keys in afi config and i was not able to connect my tab to pc or get recovery.

2.Pad prduct tool

3.Ok i gonna add arrows , but i thought that its easy to get that if we open fw which we want to prot then we need replace there value from firmware for our tablet

 

[Alv]

firomi, later I'll try this. One question: What fiw is the best option to flash? (less laggy)

Thanks!

 

[firomi]

my port for venus based on this fw:

http://pan.baidu.com/s/1vOwIM

but fw with galcore.ko in misc.img /modules 188kb are not so easy to port

the one which is easy to port is include in tutorial

http://pan.baidu.com/s/1gdywFAV

its from 05 03 2014 and works like newest ainol so i recomand u to start porting on this one or one from the newest one from ainol's

the best for u is using fw for device which is most close same as your

 

[Alv]

Ok, thanks.

Other question. When I connect my tablet to the computer and run any actions tool, my device not reconice them. Maybe is this in relation with afi.cfg? How can I fix it?

 

[firomi]

sellect debugging in developer options and use 1.05.02 tools

or follow step 3 in pad tool issue

 

[mgforce]

my port for venus based on this fw:

http://pan.baidu.com/s/1vOwIM

but fw with galcore.ko in misc.img /modules 188kb are not so easy to port

the one which is easy to port is include in tutorial

http://pan.baidu.com/s/1gdywFAV

its from 05 03 2014 and works like newest ainol so i recomand u to start porting on this one or one from the newest one from ainol's

the best for u is using fw for device which is most close same as your

Hey,

Can I use the second link you mentioned in the post(latest ROM) & the above mentioned process, can I build a new ROM for Venus & would it be as fast as yours? Does it have galcore driver?

I am not a good developer & wouldn't like to brick my device in testing. :huh:

 

[firomi]

there is galcore 170kb

idk if it will be faster than my one u have to check it if u follow tutorial u gonna do almost same things which i did in irbis rom for venus.

 

[klincharov]

Does this mean we could get a KitKat rom ported from another 7029 device ? I don't think the chances of Ainol releasing a KK anytime soon are very high...

The ART could really boost the user experience a little more.

 

[firomi]

i think that it is possible to do but if ainol wont realise KK then noone do it..

 

[LuckyMe]

Does this mean we could get a KitKat rom ported from another 7029 device ? I don't think the chances of Ainol releasing a KK anytime soon are very high...
The ART could really boost the user experience a little more.

Hmmmmm. Any 7029? Klincharov, you should be careful porting 'any' 7029 rom. You have a 7025. It might not be compatible.

 

[firomi]

@LuckyMe

Ofcourse i cant confirm that it is compatibie becouse i didnt check it with atm7025 but my rom for irbis is for one of bmorn k22 and it is compatibile same as newest ainol roms. So i think that all atm7029/7025 are made in same technology (sth like 32/64 bits in computers) and for it firmwares made for 7029 will work in 7025 and vice versa.

 

[klincharov]

Hmmmmm. Any 7029? Klincharov, you should be careful porting 'any' 7029 rom. You have a 7025. It might not be compatible.

I think the difference is just the max cpu speed. And I'm not so much of a developer, just speaking hypothetically

i think that it is possible to do but if ainol wont realise KK then noone do it..

I see, we still need a 4.4 rom for Venus as a base.

 

[LuckyMe]

I think the difference is just the max cpu speed. And I'm not so much of a developer, just speaking hypothetically
.

If they were the same then the 7029 tools would work. But they don't. don't play with fire. Some ROMs aren't meant to be flashed and some are. Why do you need to flash those other roms anyway? They can't make our tablets perform miracles. The hardware can only perform a certain way. The best thing you could do is find the best 4.1 based rom and tweak it for your needs. You already know all the tools.

Xposed installer
Gravity box
Kernel tuner.
Smart launcher pro. - add the kitkat theme packs

Remove all the pre installed apps you know you'll never use.

Just say'n… unless you want to switch out your GPU…

 

[tweak45]

Firomi, can one use this tutorial to also root a stock image?

If so, how would one go about doing so?