Related
MAKE BACKUP - using Uberizer option i/3
Caution: don't flash this on KB901 with TS ft5x_ts
Rebased the whole ROM on various builds of JB 4.2.2 to run smooth without tweaks:
- cleaned up
- rooted
- adb enabled by default
- replaced the default launcher with GO Launcher HD
- adapted to accept my custom modules TS
lsmod on default ROM:
Code:
device 26862 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 34042 0 - Live 0x00000000
sp0838 19927 1 - Live 0x00000000
camera 53105 1 sun5i_csi0, Live 0x00000000
videobuf_dma_contig 6243 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
cedarx 11869 0 - Live 0x00000000
mali 200007 29 - Live 0x00000000
ump 34213 11 mali, Live 0x00000000
nand 225000 8 - Live 0x00000000
Partitions on default ROM:
Code:
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 176.8M 68.0K 176.7M 0% /dev
tmpfs 176.8M 0 176.8M 0% /mnt/asec
tmpfs 176.8M 0 176.8M 0% /mnt/obb
/dev/block/nandd 503.9M 398.1M 105.9M 79% /system
/dev/block/nande 1.2G 103.7M 1.1G 9% /data
/dev/block/nandh 315.0M 5.2M 309.8M 2% /cache
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/sdcard
/dev/block/vold/93:72 1.1G 48.0K 1.1G 0% /mnt/secure/asec
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 614400 nandd
93 32 1228800 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 327680 nandh
93 64 262144 nandi
93 72 1171456 nandj
DOWNLOAD ROM:
- New Version v2.5 -
4shared.com - FaaastJB-v2.5
mediafire.com - FaaastJB-v2.5
- Old version v2 -
4shared.com - FaaastJB-v2
mediafire.com - FaaastJB-v2
By default Touch Screen DON'T work
STEP BY STEP FOR INSTALLING TS MODULES:
You need to have ADB installed before proceed
1. Flash FaaastJB with Livesuit 1.11
2. Wait for tablet to boot and load
3. Connect your tablet to PC
4. Extract all content from TS MODULE archive to a directory
5. Execute run.bat
6. After press any key dialog the tablet will reboot
7. That's all folks
If you don't know what TS driver to use try Uberizer option k/22 and use command "lsmod" on original working ROM.
I recommend try all archives and test both TS and gsensor for better result, don't stop at the first working TS try more.
OLD TS from FaaastJB 4.1.1 don't work here
DOWNLOAD TS MODULE
* Single TS MODULE
- ekt3632.ko aka elan
- gt811_ts.ko
- gt828_ts.ko+mc32x0.ko
- gt811_ts.ko+dmard06.ko
- gsl1680.ko
- ft5x_ts.ko
- goodix_touch.ko
- gslx680.ko+mxc622x.ko
- ssd253x-ts.ko+dmard06.ko
- gslx680.ko
- gsl1680.ko+dmard06.ko
- ft5x_ts.ko
- gt828_ts.ko+mxc622x.ko
- zet6221.ko
- zet6221.ko+multiple gs
- ekt3632.ko aka elan
- ektf2k.ko aka ekt3632+mma7660
- ssd253x-ts.ko+dmard06.ko+mma7660.ko
- elan_ts+mxc622x
- goodix811.ko+mxc622x.ko
- ssd253x-ts.ko
* USERS TS MODULE
- gls1680+dmard06+mc32x0 - Thx to meatsos
- mg8698s+mxc622x+sp0838 - Thx to leoZ
- gt828_ts+mma7660 - Thx to goosen999
* Multiple TS MODULE
- TS: ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_cxx, gslx680, st1536_ts, elan_ts+ GS: bma250, mma7660, dmard06, mma8452, mxc622x, afa750
- ft5x_ts, goodix_ts, gslX680, nt11003+mxc32x0
- ft5x_ts, ssd253x-ts, gt811_ts, sitronix_i2c_touch+dmard06+mma7660
- ft5x_ts, goodix_touch, ssd253x-ts, zet622x, byd693x-ts, gt82x, gt811, pixcir_touch_811, gsl1680, st1536_ts+mxc622x
- aw5306_ts.ko-pixcir_ts.ko-gt811.ko-gsl168x.ko-sichuang.ko-ft5x_ts.ko+mma7660
- gt811_ts.ko-A13_gslX680.ko-ft5x_ts.ko+mxc622x
- S710TAB - ft5x_ts.ko-gt811.ko-gslX680.ko+mxc622x
* SPECIAL TS MODULE
- Ainol Novo7 Legend
- Multiple TS/GS: gslX680-ft5x_ts-gt818_ts-gt811_ts-zet6221+bma250-mma7660-dmard06-mma8452-kxtik-mxc622x-afa750-mma865x-lis3dh-mc32x0 after you use this module you will need to reflash ROM again if not works.
If you have found a TS and have reverse axes or screenshift i recommend to use this tools or try TSCalibration
More application for calibration need more people to test and confirm is working Touch Recalibrate
If you have inverted gsensor you will need to edit this file /system/usr/gsensor.cfg look for your gsensor name and play with this:
Code:
gsensor_direct_x = false
gsensor_direct_y = true
gsensor_direct_z = false
gsensor_xy_revert = false
Camera sux anyway on this tablet so no support.
Don't forgot to make BACKUP of default ROM
For backup i recommend Uberizer option i/3.
This devices can't be bricked but if you don't find the right ROM they don't work correctly so if you don't know what your doing don't try it.
I recommend this ROM for people who don't have a working TS.
- If you recommend this ROM and want to post links on other sites please redirect to this thread not personal sharing.
- I am not responsible for any damage you make to your tablet using this ROM
If you like this ROM please consider to make a small donation
mod edit
thanks a lot for ur rom I have a question actually my tablet is not recognized by live suit and I can find any drivers for my tablet do we require to install drivers on computer for it ?
I present you the most wanted tools for A13 tablets.
CAUTION: This tool don't work on multiple TS modules
*DOWNLOAD TOOLS :
4shared.com - scrip-bin.rar
mediafire.com - script-bin.rar
*HOW TO USE:
First of all extract the folder script-bin from archive you just downloaded to C:\
Now go to C:\script-bin directory and from there execute the wanted tools
Your tablet need to be rooted and adb enabled in order to use this fixes.
*FIX SCREEN SHIFT
- execute screenshift.cmd from C:\script-bin directory and follow the numbers
1. Pull script.bin from tablet
2. Transform script.bin to script.fex
3. Change lcd parameters to resolve screen shift
4. Transform script.fex to script.bin
5. Push scrip.bin to tablet
6. Reboot tablet
- on step 3 you will see current settings and most of the first 4 choice will fix your display, if not try the rest
*FIX INVERTED AXES
- execute changexy.cmd from C:\script-bin directory and follow the numbers
1. Pull script.bin from tablet
2. Transform script.bin to script.fex
3. Revert X axe
4. Revert Y axe
5. Revert X_Y axe
6. Transform script.fex to script.bin
7. Push scrip.bin to tablet
8. Reboot tablet
- on steps 3, 4 and 5 you will see the current settings and you need to choose to reverse
*TIPS:
- if you want to fix faster just copy your original script.bin to C:\script-bin and by executing one of the program you can find actual settings then after you know your setting just reuse program from first step
- you have x,y,xy try all combination: 0,0,0 - 0,0,1 - 0,1,0 - 0,1,1 - 1,0,0 - 1,0,1 - 1,1,0 - 1,1,1
If you like this TOOLS please consider to make a small donation
toxicro said:
You need to install drivers from LiveSuit and then your tablet will be see it from pc.
Click to expand...
Click to collapse
thanks a lot sir will try it besides I am using version 1 of faaastjb rom that's awesome thanks lot for both of the roms
Thank you very much, if is not too much to ask, can you provide me with a link of how to do everything you comment on the main post? I'm new with this tablet but i need it to run an apache server just for demos for my clients. Thanks a lot!
touch screen not work. please help.
install Jelly Bean 4.2.2 by Toxicro but touch screen not work. please help.
Backup Dump Rom Link
http://www.4shared.com/rar/Rp9scuCk/BackupROM.html
Using touch screen module with your rom
Hi Toxicro,
I'm trying (and failing) to use your rom in combination with the touchscreen drivers of my currently working rom.
I have used the lsmod command (sufficient?) to find which of the drivers/modules are used on the working rom and I have extracted these .ko and .idc files.
I had your 2.5 rom installed and copied/pushed these files to the vendor\modules and usr\idc folders but the touchscreen won't function.
Can u help me with this? Am I missing something? I'm not that great at linux but I know some basics and i'm able to use ADB.
Hope you can help.
Cheers,
Alchedin
Alchedin said:
Hi Toxicro,
I'm trying (and failing) to use your rom in combination with the touchscreen drivers of my currently working rom.
I have used the lsmod command (sufficient?) to find which of the drivers/modules are used on the working rom and I have extracted these .ko and .idc files.
I had your 2.5 rom installed and copied/pushed these files to the vendor\modules and usr\idc folders but the touchscreen won't function.
Can u help me with this? Am I missing something? I'm not that great at linux but I know some basics and i'm able to use ADB.
Hope you can help.
Cheers,
Alchedin
Click to expand...
Click to collapse
Upload a backup or original Rom to take a look.
Sent from my GT-I9100 using xda app-developers app
toxicro said:
Upload a backup or original Rom to take a look.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi Toxicro,
I have used this one: link
If possible can u help me with the sound drivers also? Last time I checked the sound wasn't working either. Thank you in advance.
Alchedin said:
Hi Toxicro,
I have used this one: link
If possible can u help me with the sound drivers also? Last time I checked the sound wasn't working either. Thank you in advance.
Click to expand...
Click to collapse
TS MODULE already exist : ektf2k.ko aka ekt3632+mma7660
toxicro said:
TS MODULE already exist : ektf2k.ko aka ekt3632+mma7660
Click to expand...
Click to collapse
Strange thing, I used all of the TS drivers in an previous installation but none of them responded to touch. I will try again then using this specific module. Thanks for your help so far, I appreciate it a lot.
Edit: Everything works! except for the camera but I don't mind, thanks a lot Toxicro :victory:
CWM dosnt work
as soon as I enter CWM with this firmware I cant exit the recovery mode and I must reflash. How can this be fixed? some patch or something?
Ada DJ said:
as soon as I enter CWM with this firmware I cant exit the recovery mode and I must reflash. How can this be fixed? some patch or something?
Click to expand...
Click to collapse
No problem with CWM here.
Why you need CWM ?
toxicro said:
No problem with CWM here.
Why you need CWM ?
Click to expand...
Click to collapse
look here:
http://www.techknow.me/forum/index.php?topic=5948.0
your firmware is like the only firmware I can flash to one of my tablets, but i have problem with touchscreen, gsensor and cwm.
the question is not about need. lets say i accidentally enter cwm, then i must reflash the tablet to get it working.
I hope you can help me in some way, thanks.
Edit: I forgot to add, I have a uberizerbackup, but I cant seem to recover back to it, it only gets stuck on the green android logo. would really appreciate your help, maybe I can send this backup (through http://www.dropsend.com/ or something else, if so, leave your mail in a pm to me) and you can see what drivers I have through it so I can get a custom patch or ROM, that would be awesome, thanks.
I have tried many patches, but still, the screen seems to spook. like it presses on places I didnt press on etc.
Maybe I should add, there is some firmwares I have found that have working cwm, but usually they are version 4.0.4, if that would help, I can look for one of these and send them to you?
finally got recovery dump working:
[email protected]:/ # lsmod
lsmod
rtl8150 10305 0 - Live 0xbf1aa000
mcs7830 7581 0 - Live 0xbf1a4000
qf9700 9152 0 - Live 0xbf19d000
asix 24601 0 - Live 0xbf191000
sun5i_csi0 37254 0 - Live 0xbf182000
bg0328_b 14558 0 - Live 0xbf17a000
gc2015_b 21406 0 - Live 0xbf16f000
sp2518_b 18789 0 - Live 0xbf165000
gt2005_b 20945 0 - Live 0xbf15a000
sp0838_b 21624 0 - Live 0xbf14f000
gc0329_b 19597 0 - Live 0xbf145000
gc0308_b 20059 0 - Live 0xbf13b000
gc2035 20405 0 - Live 0xbf132000
bg0328 14554 0 - Live 0xbf12a000
gc2015 21402 0 - Live 0xbf11f000
sp2518 18785 0 - Live 0xbf115000
hm5065 28575 0 - Live 0xbf109000
gt2005 20945 0 - Live 0xbf0fe000
gc0309 19834 0 - Live 0xbf0f4000
gc0329 19597 0 - Live 0xbf0ea000
siv121d 15447 1 - Live 0xbf0e1000
sp0a19 20151 0 - Live 0xbf0d8000
sp0838 21624 0 - Live 0xbf0cd000
gc0308 20333 0 - Live 0xbf0c3000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf0be000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf0b4000
mecs 4078 0 - Live 0xbf0ac000
mxc622x 6088 0 - Live 0xbf0a6000
cedarx 9351 0 - Live 0xbf09f000
mali 151084 4 - Live 0xbf06d000
ump 49382 9 mali, Live 0xbf059000
hv2605 5273 0 - Live 0xbf04f000
zet6221 20285 0 - Live 0xbf040000
nand 225008 4 - Live 0xbf000000
[email protected]:/ #
partition:
[email protected]:/ # busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 176.8M 44.0K 176.7M 0% /dev
tmpfs 176.8M 0 176.8M 0% /mnt/asec
tmpfs 176.8M 0 176.8M 0% /mnt/obb
/dev/block/nandd 503.9M 231.9M 272.1M 46% /system
/dev/block/vold/93:72
1.6G 42.1M 1.5G 3% /mnt/sdcard
/dev/block/vold/93:72
1.6G 42.1M 1.5G 3% /mnt/secure/asec
[email protected]:/ #
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
93 0 16384 nanda
93 8 16384 nandb
93 16 32768 nandc
93 24 524288 nandd
93 32 1048576 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 262144 nandi
93 72 1662976 nandj
[email protected]:/ #
toxicro said:
No problem with CWM here.
Why you need CWM ?
Click to expand...
Click to collapse
can't find working TS on softwinerevb 7" any idea?
Thant said:
can't find working TS on softwinerevb 7" any idea?
Click to expand...
Click to collapse
If no TS module from first post don't work on your tablet provide a backup or a working ROM.
toxicro said:
If no TS module from first post don't work on your tablet provide a backup or a working ROM.
Click to expand...
Click to collapse
after use A13 erase tablet to full empty device and install this ROM sun5i_android_a13-evb-q8-mxc622x-20121012work.img everything work.
Thant said:
after use A13 erase tablet to full empty device and install this ROM sun5i_android_a13-evb-q8-mxc622x-20121012work.img everything work.
Click to expand...
Click to collapse
That ROM have multiple TS loading i need a "getevent" using adb shell with the working ROM.
Hello, i just created cm10 for allwinner a13 tablets (EVB versions)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android 4.1.2
I compiled cm10 source and I made a custom kernel
Features:
- CyanogenMod Features
- Expanded desktop mode
- Init.d Scripts:
-- ZipAlign
-- Internal speed fix
-- Perfect Mounts
-- SQL Optimize
-- Auto setup sensors Script
- Xbox 360 gamepad support (xpad)
- PS3 USB gamepad support (hid-sony)
- PS2 USB gamepad support (hid-sjoy)
- Generic / chinese (Pantherlord / GreenAsia) gamepads support (hid-dr and hid-gaff)
- OpenVPN support (tun)
- NTFS and ExFat support
- Custom Kernel Features (based in stock kernel version 3.0.8+):
- Smartass2 governor (Default)
- SIO I/O Scheduler (Default)
- Mali OS = 90 mb
- Cyanogenmod compatible Sound
- Gamepad support
- Preloaded modules:
- Touchscreen:
-- ft5x_ts
-- gslX680
-- ft5x02 (Ainol novo7legend ts)
- Camera:
-- gc0308
-- gc0329
-- sp0838
- G-sensor:
-- mxc622x
BUGS: You tell me
Instructions:
ATTENTION: This rom is NOT compatible with faaastJB v2 rom, (You need to be in WORKING stock rom or faaastJB v1 to make all modules work)
FaaastJB v2 use a modified script.bin who BREAK modules in this ROM
REMEMBER BACKUP YOUR ROM AND HAVE .IMG IMAGE IN CASE IS SOMETHING GOT WRONG
DO THIS BEFORE FLASH To check what is your modules drivers, enter on terminal emulator or ADB and make:
Code:
lsmod
and
Code:
getevent
Check with
Code:
lsmod
the loaded modules (CAMERA MODULES: HAVE "1" number after module name, example:
Code:
gc0308 16888 1 - Live 0x00000000
this clear show gc0308 camera module loaded.
Code:
getevent
help you find touchscreen driver and also G-sensor driver
Example:
Code:
add device 1: /dev/input/event4
name: "gslx680"
add device 2: /dev/input/event3
name: "gt811"
add device 3: /dev/input/event2
name: "mxc622x"
add device 4: /dev/input/event0
name: "sun4i-keyboard"
Cleared show you "mxc622x" g-sensor module
"gslx680" touchscreen module
"gt811" in this case you need to test what is the proper touchscreen driver
After to know what is your driver, show the Proper patches and flash it!
Oh yeah :android-lol: welcome to test the most Smooth allwinner a13 CM10 rom!
- Install CWM
instruction here: http://forum.xda-developers.com/showthread.php?t=2189640
- Boot into CWM keeping pressed VOL- (MENU) and POWER for 3 secs, than release POWER and after another sec release VOL- (or use Novo7 tools if it doesn't work for your device)
- Select "wipe data/factory reset"
- Select "install zip from sdcard" -> "choose zip from sdcard" (or "choose zip from internal sdcard" if your files are into internal memory)
- Flash in this order:
1. ROM
2. JB G-apps
3. Compatibility patch (If available)
- Now go back, and select "Reboot system now
- Setup tablet with wizard and Reboot Again (to get g-sensor working)
- Enjoy CM10!
I have tested the rom with OEM A13 Tablet (Is smooth and stable)
I can play dead trigger!
I will try to support the rom and custom kernel
Also if is posible, I will update to CM10.1
- If you wanna use the "phablet" ui change the entry "ro.disable_phablet_ui=1" to "ro.disable_phablet_ui=0" in file /system/build.prop
- If you wanna change external SD card for Internal change the entry "persist.sys.vold.switchexternal=0" to "persist.sys.vold.switchexternal=1" in file /system/build.prop
Download:
Cm10: Mod Edit: Links Removed
G-apps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Compatibility patches
Touchscreen Download
- ssd-253x-ts
- goodix811
- zet6221_ts
- ct360_ts
- elan_ts
- gt811 (goodix811 alternative)
- gt818_ts
- gt828_ts
- gslx680 (gslX680 alternative)
- zet6221-ts (zet6221 alternative)
- goodix_touch
G-sensor Download
- bma250
- mxc622x
- mma7660
Camera Download
- gc0329
- sp0838
I make FREE job but you want support me for development and have more development devices?
Click "Donate to me" above on my profile picture or contact me
Screenshots:
Expanded desktop mode ON:
FAQ
1. Volumen keylayout is different?
A: copy and paste /system/usr/keylayout/sun4i-keyboard.kl from backup rom to CM10 and chmod 644
2. My touchscreen is working descalibrated, is shift inverted?
A. first check if backup rom have kernel version 1.5 and copy and paste your touchscreen from backup rom to CM10 and chmod 644
Example: you have ft5x_ts touchscreen
open windows adb command line and make this:
Code:
adb "root"
adb remount
adb push ft5x_ts.ko /system/lib/modules
adb chmod 644 /system/lib/modules/ft5x_ts.ko
adb push ft5x_ts.idc /system/usr/idc
adb chmod 644 /system/usr/idc/ft5x_ts.idc
3. My g-sensor is inverted?
A. first check if backup rom have kernel version 1.5 and Copy and paste your g-sensor module name from backup rom to CM10 and chmod 644
4. Nothing is working and I want make my own patches?
A. You can do it, if you want load unlisted touchscreen (for example):
edit /system/etc/init.d/07touchscreen
change this line: insmod /system/lib/modules/ft5x_ts.ko with your touchscreen module name, save and exit. chmod 755
copy the ts module into /system/lib/modules and idc /system/usr/idc
chmod 644 that for modules and idc
for camera edit this file: /system/lib/modules/08camera
and g-sensor edit: /system/lib/modules/09gsensor
5. I do not know what is my modules?
A. Extract script.bin and attach here with a post, use this tool:
Script.bin_Extract.zip
TWITTER: @freddyarenas4
Regards from Venezuela
Changelogs:
Code:
Build and Patches 08-28-2013
- New Rom Build
- Changed Default g-sensor: mxc622x
- Changed Default Camera modules:
-- gc0308
-- gc0329
-- sp0838
- Fixed Ainol Novo7 Legend touchscreen!
- New way to load modules in init.d:
-- 07touchscreen
-- 08camera
-- 09gsensor
In this case, nobody can get bootloop or black screen with patches
- Removed No Working Touchscreen patches
- Added ms8698s touchscreen module
- Important:
-- Changed Android Framework AV and added new cedarx to fix video HD decoding (NEED testers)
- Added a FAQ section with important answer to fix newbies issues
Code:
Update 07/09/13
Update main thread post with more help to know how find your device drivers,
Also warning with incompatible faaastjb v2 script.bin file
Code:
Update 07/03/13
Fixed and Update camera modules (this removed the TS modules load)
Try to flash ts again
added:
zet622x
goodix_touch
Code:
Build and Patches 07-03-2013
- New Rom Build
- Default g-sensor: dmard06
- removed auto setup sensors (did not work)
- Update dmard06 module
- Fixed xbox 360 module (was not present in modules folder)
- Added:
- G-sensor compatible patches
-- bma250
-- mxc622x
-- mma7660
- Touchscreen compatible patches
-- ct360_ts
-- elan_ts
-- gt811 (goodix811 alternative)
-- gt818_ts
-- gt828_ts
-- gslx680 (gslX680 alternative)
Update google drive shared folder
Code:
Patches 07-01-2013
Touchscreen: ssd-253x-ts.zip, goodix811.zip, zet6221.zip
Camera: gc0329.zip, sp0838.zip
Code:
Build 06-29-2013
Initial Release
Looking forward to flashing mine in the morning. Thank you very much. Though, I'm not clear: What are the EVB versions? Been out of the loop in watching development on the A13 tablets for a while, so forgive my ignorance. I have a generic Fleabay-bought Q88 with a Goodix touchscreen. Any chance this will work properly with a Goodix controller?
the720k said:
Looking forward to flashing mine in the morning. Thank you very much. Though, I'm not clear: What are the EVB versions? Been out of the loop in watching development on the A13 tablets for a while, so forgive my ignorance. I have a generic Fleabay-bought Q88 with a Goodix touchscreen. Any chance this will work properly with a Goodix controller?
Click to expand...
Click to collapse
EVB version is the allwinner a13 wifi model.
Yes, it is posible make a compatibility path for this, but I need know what is your camera and g-sensors modules too!
Thanks for the reply. Will an lsmod suffice?
the720k said:
Thanks for the reply. Will an lsmod suffice?
Click to expand...
Click to collapse
Yes this should work, I will waiting you
Sent from my Nexus 7 using xda app-developers app
Here's the output:
Code:
[email protected]:/ # lsmod
8192cu 515468 0 - Live 0xbf0bd000
rtl8150 10305 0 - Live 0xbf0b6000
mcs7830 7589 0 - Live 0xbf0b0000
qf9700 9152 0 - Live 0xbf0a9000
asix 24601 0 - Live 0xbf09d000
usbnet 26253 3 mcs7830,qf9700,asix, Live 0xbf090000
sun5i_csi0 31059 0 - Live 0xbf083000
gc0308 18408 1 - Live 0xbf07a000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf075000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf06b000
dmard06 7987 0 - Live 0xbf061000
mali 152158 10 - Live 0xbf027000
ump 49678 19 mali, Live 0xbf013000
hv2605 5273 0 - Live 0xbf00d000
goodix_touch_811 18030 0 - Live 0xbf004000
sun4i_keyboard 2677 0 - Live 0xbf000000
Thanks in advance. Looking forward to finally getting a decent ROM on this tablet!
the720k said:
Here's the output:
Code:
[email protected]:/ # lsmod
8192cu 515468 0 - Live 0xbf0bd000
rtl8150 10305 0 - Live 0xbf0b6000
mcs7830 7589 0 - Live 0xbf0b0000
qf9700 9152 0 - Live 0xbf0a9000
asix 24601 0 - Live 0xbf09d000
usbnet 26253 3 mcs7830,qf9700,asix, Live 0xbf090000
sun5i_csi0 31059 0 - Live 0xbf083000
gc0308 18408 1 - Live 0xbf07a000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf075000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf06b000
dmard06 7987 0 - Live 0xbf061000
mali 152158 10 - Live 0xbf027000
ump 49678 19 mali, Live 0xbf013000
hv2605 5273 0 - Live 0xbf00d000
goodix_touch_811 18030 0 - Live 0xbf004000
sun4i_keyboard 2677 0 - Live 0xbf000000
Thanks in advance. Looking forward to finally getting a decent ROM on this tablet!
Click to expand...
Click to collapse
Ok, when I get to home, I will try to make a patch
Sent from my Nexus 7 using xda app-developers app
AnonFBI said:
Ok, when I get to home, I will try to make a patch
Click to expand...
Click to collapse
Cool, very much looking forward to it. Have been trying to get CM on this tablet since I bought it a year ago. I am sure many other Q88 owners will be happy to have it working on their tabs as well.
How to flash compatibility?
AnonFBI said:
Hello, i just created cm10 for allwinner a13 tablets (EVB versions)
Android 4.1.2
I compiled cm10 source and I made a custom kernel
Features:
- CyanogenMod Features
- Expanded desktop mode
- Init.d Scripts:
-- ZipAlign
-- Internal speed fix
-- Perfect Mounts
-- SQL Optimize
-- Auto setup sensors Script
- Xbox 360 gamepad support (xpad)
- PS3 USB gamepad support (hid-sony)
- PS2 USB gamepad support (hid-sjoy)
- Generic / chinese (Pantherlord / GreenAsia) gamepads support (hid-dr and hid-gaff)
- OpenVPN support (tun)
- NTFS and ExFat support
- Custom Kernel Features (based in stock kernel version 3.0.8+):
- Smartass2 governor (Default)
- SIO I/O Scheduler (Default)
- Mali OS = 90 mb
- Cyanogenmod compatible Sound
- Gamepad support
- Preloaded modules:
- Touchscreen:
-- ftx5x_ts
-- gslX680
-- ft5x02 (Ainol novo7legend ts)
- Camera:
-- gc0308
-- gt2005
-- mt9m112
-- ov5640
- G-sensor:
-- dmard06
-- bma250
-- mxc622x
-- mma7660
BUGS: You tell me
Instructions:
- Install CWM
instruction here: http://forum.xda-developers.com/showthread.php?t=2189640
- Boot into CWM keeping pressed VOL- (MENU) and POWER for 3 secs, than release POWER and after another sec release VOL- (or use Novo7 tools if it doesn't work for your device)
- Select "wipe data/factory reset"
- Select "install zip from sdcard" -> "choose zip from sdcard" (or "choose zip from internal sdcard" if your files are into internal memory)
- Flash in this order:
1. ROM
2. JB G-apps
3. Compatibility patch (If available)
- Now go back, and select "Reboot system now
- Setup tablet with wizard and Reboot Again (to get g-sensor working)
- Enjoy CM10!
I have tested the rom with OEM A13 Tablet (Is smooth and stable)
I can play dead trigger!
I will try to support the rom and custom kernel
Also if is posible, I will update to CM10.1
- If you wanna use the "phablet" ui change the entry "ro.disable_phablet_ui=1" to "ro.disable_phablet_ui=0" in file /system/build.prop
- If you wanna change external SD card for Internal change the entry "persist.sys.vold.switchexternal=0" to "persist.sys.vold.switchexternal=1" in file /system/build.prop
Download:
Cm10: https://docs.google.com/file/d/0B240tVoN5YQPUmNFQW1ZQ0pCLUk/edit?usp=sharing
G-apps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Compatibility patches
ssd-253x-ts.zip
¿Do you want support me for development and have more developer devices?
Click "Donate to me" above on my profile picture or contact me
Screenshots:
Expanded desktop mode ON:
Regards from Venezuela
Click to expand...
Click to collapse
Hello sir! How to flash .zip compatibility patch?? it says error code 6 ??
at41man said:
Hello sir! How to flash .zip compatibility patch?? it says error code 6 ??
Click to expand...
Click to collapse
Added and fixed more patches, read main post for download links.
Try to download the patch again. now is fixed
TouchScreen Not Functioning?
AnonFBI said:
Added and fixed more patches, read main post for download links.
Try to download the patch again. now is fixed
Click to expand...
Click to collapse
Really good ROM, all things functioning, SMOOTH but.......
the touchscreen not functioning! I must use Mouse with OTG..
here the lsmod from my device, hope it helps:
[email protected]:/ $ su
[email protected]:/ # lsmod
8192cu 575431 0 - Live 0xbf0bb000
cdc_subset 1588 0 - Live 0xbf0b7000
cdc_eem 2915 0 - Live 0xbf0b3000
cdc_ether 7651 0 - Live 0xbf0ad000
rtl8150 10305 0 - Live 0xbf0a6000
mcs7830 7581 0 - Live 0xbf0a0000
qf9700 9152 0 - Live 0xbf099000
asix 24601 0 - Live 0xbf08d000
usbnet 26229 6 cdc_subset,cdc_eem,cdc_ether,mcs7830,qf9700,asix, Live 0xbf080000
sun5i_csi0 30803 0 - Live 0xbf073000
gc0308 18408 1 - Live 0xbf06a000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf065000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf05b000
mma7660 6857 0 - Live 0xbf055000
cedarx 9351 0 - Live 0xbf04e000
mali 150686 10 - Live 0xbf01c000
ump 48970 17 mali, Live 0xbf009000
gt811_ts 18014 0 - Live 0xbf000000
[email protected]:/ #
thank you sir!!
at41man said:
Really good ROM, all things functioning, SMOOTH but.......
the touchscreen not functioning! I must use Mouse with OTG..
here the lsmod from my device, hope it helps:
[email protected]:/ $ su
[email protected]:/ # lsmod
8192cu 575431 0 - Live 0xbf0bb000
cdc_subset 1588 0 - Live 0xbf0b7000
cdc_eem 2915 0 - Live 0xbf0b3000
cdc_ether 7651 0 - Live 0xbf0ad000
rtl8150 10305 0 - Live 0xbf0a6000
mcs7830 7581 0 - Live 0xbf0a0000
qf9700 9152 0 - Live 0xbf099000
asix 24601 0 - Live 0xbf08d000
usbnet 26229 6 cdc_subset,cdc_eem,cdc_ether,mcs7830,qf9700,asix, Live 0xbf080000
sun5i_csi0 30803 0 - Live 0xbf073000
gc0308 18408 1 - Live 0xbf06a000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0xbf065000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0xbf05b000
mma7660 6857 0 - Live 0xbf055000
cedarx 9351 0 - Live 0xbf04e000
mali 150686 10 - Live 0xbf01c000
ump 48970 17 mali, Live 0xbf009000
gt811_ts 18014 0 - Live 0xbf000000
[email protected]:/ #
thank you sir!!
Click to expand...
Click to collapse
do you tested goodix811.zip patch? it is working?
if do not, you need send me the gt811_ts.ko kernel module
and gt811_ts.idc
This is an excellent ROM. Much smoother than the stock ROM for my device. goodix811.zip worked perfectly. Wifi is working, camera is working, CPU governor has sped things up a bit, and I'm very pleased with how this device is running. All modules are working 100% except the G-sensor. My device has dmard06, but my X and Y axes are inverted, so when I turn my device to landscape, it goes to portrait, and vice-versa.
Otherwise, EXCELLENT ROM. My tablet has never run so smoothly. Hopefully a working dmard06.ko/sensors.exDroid.so can be found soon for a compatibility zip.
Good work, Anon!
I have a A13B tablet from ebay...its boot looping back into recovery...im a big fan cm10 any sugestions on a fix...downliading rom and gapps now also
Sent from my HTCONE using xda premium
AnonFBI said:
Changelogs:
Build 06-29-13
- Initial Release
Patches 07-01-2013
Touchscreen :ssd-253x-ts.zip, goodix811.zip, zet6221.zip
Camera: gc0329.zip
Click to expand...
Click to collapse
Yes this is the thing i am looking for from a year,good work man thinking about pac or aokp ?
goodix811 patch is not working !
icoolguy1995 said:
goodix811 patch is not working !
Click to expand...
Click to collapse
the patch is working, maybe you need edit your script.bin and give me the [ctp_para]
how to edit script .bin when ever i apply that patch screen goes black !
or can i apply that module from ics ?
---------- Post added at 07:14 PM ---------- Previous post was at 07:06 PM ----------
whenever i apply goodix patch the screen goes black after reboot to revive it i need to apply other touchscreen patch and then screen goes on but touch screen doesn't work why it is so ?
---------- Post added at 07:40 PM ---------- Previous post was at 07:14 PM ----------
here is lsmod
H:\program files\Virtuous Ten Studio\External\ADB>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ adb shell
adb shell
error: device not found
1|[email protected]:/ $
H:\program files\Virtuous Ten Studio\External\ADB>adb shell
[email protected]:/ $ lsmod
lsmod
8188eu 581006 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 33255 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
ov5640 31583 0 - Live 0x00000000
mt9m112 15359 0 - Live 0x00000000
gt2005 19412 0 - Live 0x00000000
gc0308 18408 1 - Live 0x00000000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 6857 0 - Live 0x00000000
mxc622x 6088 0 - Live 0x00000000
mecs 4078 0 - Live 0x00000000
bma250 7545 0 - Live 0x00000000
dmard06 11119 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
mali 150572 8 - Live 0x00000000
ump 48978 17 mali, Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
[email protected]:/ $
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
can i use this boot.img in stock 4.2.2 ?
icoolguy1995 said:
how to edit script .bin when ever i apply that patch screen goes black !
or can i apply that module from ics ?
---------- Post added at 07:14 PM ---------- Previous post was at 07:06 PM ----------
whenever i apply goodix patch the screen goes black after reboot to revive it i need to apply other touchscreen patch and then screen goes on but touch screen doesn't work why it is so ?
---------- Post added at 07:40 PM ---------- Previous post was at 07:14 PM ----------
here is lsmod
H:\program files\Virtuous Ten Studio\External\ADB>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ adb shell
adb shell
error: device not found
1|[email protected]:/ $
H:\program files\Virtuous Ten Studio\External\ADB>adb shell
[email protected]:/ $ lsmod
lsmod
8188eu 581006 0 - Live 0x00000000
rtl8150 10305 0 - Live 0x00000000
mcs7830 7581 0 - Live 0x00000000
qf9700 9152 0 - Live 0x00000000
asix 24601 0 - Live 0x00000000
sun5i_csi0 33255 0 - Live 0x00000000
cedarx 11869 0 - Live 0x00000000
ov5640 31583 0 - Live 0x00000000
mt9m112 15359 0 - Live 0x00000000
gt2005 19412 0 - Live 0x00000000
gc0308 18408 1 - Live 0x00000000
videobuf_dma_contig 6251 1 sun5i_csi0, Live 0x00000000
videobuf_core 20242 2 sun5i_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 6857 0 - Live 0x00000000
mxc622x 6088 0 - Live 0x00000000
mecs 4078 0 - Live 0x00000000
bma250 7545 0 - Live 0x00000000
dmard06 11119 0 - Live 0x00000000
ft5x_ts 44577 0 - Live 0x00000000
mali 150572 8 - Live 0x00000000
ump 48978 17 mali, Live 0x00000000
hid_sony 2377 0 - Live 0x00000000
hid_gaff 2817 0 - Live 0x00000000
[email protected]:/ $
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
can i use this boot.img in stock 4.2.2 ?
Click to expand...
Click to collapse
1 user tested the patch and worked perfectly, yes this kernel can used in every rom but you need export the modules too
TWRP v2.6.3.0 for Softwinners Wing-D9 (Allwinner A20)
aka JayTech PA1051DA
Warning:
This process might damage your device. Make yourself comfortable how to recover from a broken system (Livesuite, PhoenixCard..). Even though most Allwinners are unbrickable reviving might involve steps that are less suitable for beginners.
General info:
The Allwinner A20 devices are available in many variations. Use the informations below to figure out if your device might be compatible. It's important that the kernel command line (see below) includes a 'partition' section with aliases for the partitions because they are used in the filesystem table of TWRP (see below). Example: [email protected] -> Symlinks /dev/block/nandg to /dev/block/recovery.
Do not use on devices with resolution below 1024x600.
Installation:
Flash the image with dd to your device. Don't forget to backup your old recovery (see here):
Code:
busybox dd if=recovery.img of=/dev/block/recovery bs=1M
Boot into recovery with either <power> + <vol+> or by 'adb reboot recovery'.
If the recovery only works partially (eg. due to wrong display or touch driver) and you're stuck in a bootloop that always starts the recovery (instead of the system) and ADB is running properly you can write the boot command string to /misc partition manually that should point the bootloader back to Android OS.
Code:
echo -n bootloader | busybox dd of=/dev/block/misc bs=16 count=1 conv=sync; sync
It writes the string 'bootloader' and fills up the rest of the 16 char block with 0x00.
Device info:
Tablet brand name: JayTech PA1051DA (Germany 06/2013)
SoC: Allwinner A20 (sun7i)
ro.build.fingerprint=softwinners/wing_d9/wing-d9:4.2.2/JDQ39/20130619:eng/test-keys
ro.product.model=TPC-1051
ro.build.version.release=4.2.2
Dmesg info: Linux version 3.3.0+ ([email protected]) (gcc version 4.6.3 20120201 (prerelease) (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) ) #16 SMP PREEMPT Tue Jun 25 10:39:48 CST 2013
ARM Cortex A7 Dual Core 1.5 GHz
ARM Mali400MP2
Display: 10,1" 1024x600
Android 4.2
RAM: 1GB
Nand: 8GB
Kernel command line:
(cat /proc/cmdline)
Code:
console=ttyS0,115200 root=/dev/system init=/init loglevel=4 [email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]
cat /proc/partitions:
(Partition layout (size/position/count) doesn't matter. Kernel command line aliases handle that).
Code:
major minor #blocks name
7 0 12506 loop0
7 1 16664 loop1
7 2 17703 loop2
7 3 22901 loop3
7 4 37454 loop4
7 5 21861 loop5
7 6 7308 loop6
93 0 16384 nanda
93 8 16384 nandb
93 16 16384 nandc
93 24 524288 nandd (/system 512MB)
93 32 524288 nande (/data 512MB)
93 40 16384 nandf
93 48 32768 nandg (Recovery 32MB)
93 56 524288 nandh
93 64 262144 nandi
93 72 5521408 nandj (/sdcard 5.6GB)
254 0 12505 dm-0
254 1 16663 dm-1
254 2 17703 dm-2
254 3 22900 dm-3
254 4 37453 dm-4
254 5 21861 dm-5
254 6 7308 dm-6
TWRP recovery.fstab:
Code:
# mount point fstype device device2
# /bootloader vfat /dev/block/bootloader
/env emmc /dev/block/env
/boot emmc /dev/block/boot flags=backup=1
/system ext4 /dev/block/system flags=backup=1;wipeingui
/data ext4 /dev/block/data flags=backup=1;wipeduringfactoryreset;wipeingui
/misc emmc /dev/block/misc
/recovery emmc /dev/block/recovery flags=backup=1
/databk ext4 /dev/block/databk
/cache ext4 /dev/block/cache flags=backup=1;wipeduringfactoryreset;wipeingui
/sdcard vfat /dev/block/UDISK flags=backup=1;storage;settingsstorage;display="Internal SDCard";wipeingui
/external_sd vfat /dev/block/mmcblk0p1 flags=backup=1;storage;display="External SDCard";wipeingui;removable
Drivers (lsmod):
Code:
cdc_ether 2906 0 - Live 0x00000000
rtl8150 8154 0 - Live 0x00000000
mcs7830 4947 0 - Live 0x00000000
qf9700 5167 0 - Live 0x00000000
asix 12313 0 - Live 0x00000000
usbnet 12504 4 cdc_ether,mcs7830,qf9700,asix, Live 0x00000000
sunxi_csi1 27909 0 - Live 0x00000000
sunxi_csi0 28609 0 - Live 0x00000000
gc2035 12870 1 - Live 0x00000000
gc0308 10968 1 - Live 0x00000000
videobuf_dma_contig 3816 2 sunxi_csi1,sunxi_csi0, Live 0x00000000
videobuf_core 15283 3 sunxi_csi1,sunxi_csi0,videobuf_dma_contig, Live 0x00000000
mma7660 7318 0 - Live 0x00000000
ft5x_ts 66217 0 - Live 0x00000000 <-- Touchscreen
mali 183842 30 - Live 0x00000000 (O)
ump 29576 7 mali, Live 0x00000000 (O)
hdmi 22078 0 - Live 0x00000000
lcd 4126 0 - Live 0x00000000
disp 257984 14 mali,hdmi,lcd, Live 0x00000000
nand 132556 8 - Live 0x00000000 (O)
Source/device tree:
https://github.com/BlueMax/android_device_softwinners_wing_d9
Changelog:
- v1.0: Initial release (TWRP v2.6.3.0)
- Instructions: Replaced partition names with aliases
Any way to copy stock recovery for backup?
gerstavros said:
Any way to copy stock recovery for backup?
Click to expand...
Click to collapse
Yes, use this in Android.
Code:
busybox dd if=/dev/block/recovery of=/sdcard/recovery-backup.img bs=1M
DualJoe said:
Yes, use this in Android.
Code:
busybox dd if=/dev/block/recovery of=/sdcard/recovery-backup.img bs=1M
Click to expand...
Click to collapse
i found also Uberizer, for an easier way for simple users
Allwinner A20 9" 800x480
Hi mate
I have a Tablet brand name: Xtratech Tablet M905
SoC: Allwinner A20 (sun7i)
Android 4.2.2
Kernel 3.3
ARM Cortex A7 Dual Core 1.5 GHz
Display: 9" 800x480
RAM: 1GB
Nand: 16GB
Could you tell me if the information in this thread will work for my tablet?
Thanks so much...
dmonium said:
Display: 9" 800x480
Click to expand...
Click to collapse
Probably too low. You might be unable to reach some buttons. Never tested that.
DualJoe said:
Probably too low. You might be unable to reach some buttons. Never tested that.
Click to expand...
Click to collapse
I have a no brand tablet with similar specifications. Any way to have a custom recovery?
Hi there
I have been looking for something like this for my Cubietruck. There really is no one working on this on any of the Cubie forums. Here are the specs on this board.
CPU
Dual core ARM Cortex A7 processor, NEON, VFPv4, 512KB L2-Cache
GPU
Dual core ARM Mali400 MP2, 1 vertex shader, 2 fragment shaders, OpenGL ES 2.0
Memory
2GB DDR3 @480MHz
Video output
HDMI 1080p, VGA
Networking
10/100M/1G Ethernet, WiFi, Bluetooth
Internal storage
8GB NAND Flash
IO
2 x USB Host, 1 x MicroSD slot, 1 x SATA, 1 x IR sensor
Extended interfaces
54 extend pin interfaces to low level SOC functionality
Software
Android 4.2, Official Linux distribution available (not pre-installed)
Power
Requires regulated 5VDC 2A power supply with a 4.0mm(ext. diameter) x 1.7mm (int. diameter) barrel plug. Extra power may be required for some HDD
The version of Android is a striped down version. Im trying to get a custom recovery on this board. And an updated version of android.
Thanks
---------- Post added at 11:59 PM ---------- Previous post was at 11:58 PM ----------
Hi there
I have been looking for something like this for my Cubietruck. There really is no one working on this on any of the Cubie forums. Here are the specs on this board.
CPU
Dual core ARM Cortex A7 processor, NEON, VFPv4, 512KB L2-Cache
GPU
Dual core ARM Mali400 MP2, 1 vertex shader, 2 fragment shaders, OpenGL ES 2.0
Memory
2GB DDR3 @480MHz
Video output
HDMI 1080p, VGA
Networking
10/100M/1G Ethernet, WiFi, Bluetooth
Internal storage
8GB NAND Flash
IO
2 x USB Host, 1 x MicroSD slot, 1 x SATA, 1 x IR sensor
Extended interfaces
54 extend pin interfaces to low level SOC functionality
Software
Android 4.2, Official Linux distribution available (not pre-installed)
Power
Requires regulated 5VDC 2A power supply with a 4.0mm(ext. diameter) x 1.7mm (int. diameter) barrel plug. Extra power may be required for some HDD
The version of Android is a striped down version. Im trying to get a custom recovery on this board. And an updated version of android.
Thanks
touch doesn't work
I got the recovery installed but the touch support isnt working
max0r4axor said:
I got the recovery installed but the touch support isnt working
Click to expand...
Click to collapse
You probably need a different touchscreen driver (included is 'ft5x_ts'). Post an 'lsmod' output from the main system. It should be possible to swap or add the driver.
Also attach the log file from TWRP that is in /tmp.
Hi, i have a allwinner a20 tablet which has these spec:
Allwinner A20 ( Cortex a7 1.2GHz Dual core)
GPU Mail 400 MP2
1GB DDR3
4GB FLASH
9" 1024x768
Can you tell me if it will work?
Can you also send me the source code of this TWRP?
Which driver do you need to port TWRP for my devices? How can i give you them?
Thank you
lsmod for eken gc10x
[email protected]:/ $ lsmod
8188eu 628195 0 - Live 0x00000000
8192cu 626898 0 - Live 0x00000000
gslX680 113137 0 - Live 0x00000000 (F)
dmard10 7798 0 - Live 0x00000000
sw_device 11232 0 - Live 0x00000000
cdc_ether 2927 0 - Live 0x00000000
mcs7830 4948 0 - Live 0x00000000
qf9700 5168 0 - Live 0x00000000
asix 12318 0 - Live 0x00000000
usbnet 12521 4 cdc_ether,mcs7830,qf9700,asix, Live 0x00000000
sunxi_csi0 28746 0 - Live 0x00000000
gc03281 10793 1 - Live 0x00000000
gc0328 10821 1 - Live 0x00000000
videobuf_dma_contig 3817 1 sunxi_csi0, Live 0x00000000
videobuf_core 15292 2 sunxi_csi0,videobuf_dma_contig, Live 0x00000000
camera_led_con 1176 0 - Live 0x00000000
mali 115734 73 - Live 0x00000000 (O)
ump 30154 17 mali, Live 0x00000000 (O)
hdmi 22869 0 - Live 0x00000000 (O)
lcd 4127 0 - Live 0x00000000
disp 259894 18 mali,hdmi,lcd, Live 0x00000000
nand 133329 8 - Live 0x00000000 (O)
---------- Post added at 03:59 AM ---------- Previous post was at 03:39 AM ----------
well i unpacked your compiled recovery and my original recovery deleted ft5x_ts.ko from yours added gslX680.ko from mine changed /insmod ft5x_ts.ko to /insmod gslx680.ko and repacked going to flash and see if this fixes it
---------- Post added at 04:32 AM ---------- Previous post was at 03:59 AM ----------
I can provide a link to my reocovery extracted if it helps through a pm
L4ky said:
Can you tell me if it will work?
Click to expand...
Click to collapse
No, sorry. Its impossible to tell anything for sure. It depends on many things and i don't recommend trying this if you can't recover from a bootlooped state.
max0r4axor said:
i unpacked your compiled recovery and my original recovery deleted ft5x_ts.ko from yours added gslX680.ko from mine changed /insmod ft5x_ts.ko to /insmod gslx680.ko and repacked going to flash and see if this fixes it
Click to expand...
Click to collapse
That's the same thing i had in mind. Did it work?
DualJoe said:
No, sorry. Its impossible to tell anything for sure. It depends on many things and i don't recommend trying this if you can't recover from a bootlooped state.
That's the same thing i had in mind. Did it work?
Click to expand...
Click to collapse
I haven't gotten the chance to work the bugs out it semi works and since I can't really brick this cause I have the original firmware I'm trying lots of different things
max0r4axor said:
I haven't gotten the chance to work the bugs out it semi works and since I can't really brick this cause I have the original firmware I'm trying lots of different things
Click to expand...
Click to collapse
I would load all modules and see if it works. If not try switching to your kernel. Watch 'twrp.log' and 'dmesg' for errors to clean up at the end.
Hi,I want to install you TWRP,but i have Read-only file system. Can you help me to remount my Tablet on rw file system?
I have Assistant AP-110,on Allwinner A20 / 10,1"/ but command mount -o remount,rw /system or mount -o remount,rw /dev/block/system /system, or mount -o remount,rw /dev/block/nandd /system not work...(EXT4 FS)...
Help me please)
The device is probably not rooted. That's an individual problem i can't help you with.
@DualJoe can you share the device tree you used to build this? Trying to set up a device tree for a20
randomblame said:
@DualJoe can you share the device tree you used to build this? Trying to set up a device tree for a20
Click to expand...
Click to collapse
I've set up a git repo.
https://github.com/BlueMax/android_device_softwinners_wing_d9
I am the owner of the tablet Kalley K-BOOK10 and since a like install differents recovery in my devices, I bricked, but then I found that the company dont have any firmware to download yet, so I spend 26 hours trying differents firmwares until find one that works with mine: ICOU10GT2.
I will like to share the solution if anyone have the same problem. Before I bricked I took a backup and the build.prop has this info:
K-BOOK10 Original build.prop, no firmware download link yet.
Code:
ro.build.id=JDQ39
ro.build.display.id=K-BOOK10 20131017
ro.build.version.incremental=20131009
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.type=eng
ro.build.user=builder5
ro.build.host=next-huawen
ro.build.tags=test-keys
ro.product.model=K-BOOK10
ro.product.brand=KALLEY
ro.product.name=fiber_q10s
ro.product.device=fiber-q10s
ro.product.board=exdroid
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.board.platform=fiber
ro.build.product=fiber-q10s
ro.build.description=fiber_q10s-eng 4.2.2 JDQ39 20131009 test-keys
ro.build.fingerprint=Allwinner-Tablet/fiber_q10s/fiber-q10s:4.2.2/JDQ39/20131009:eng/test-keys
ro.build.characteristics=tablet
ICOU10GT2 build.prop, download firmware in soft.aoicoo.com,
the link is in: soft.aoicoo.com
/soft/show.asp?id=309,
download link: soft.aoicoo.com
/soft/downcopy.asp?id=309
Code:
ro.build.id=JDQ39
ro.build.display.id=fiber_q10s-eng 4.2.2 JDQ39 20130929 test-keys
ro.build.version.incremental=20130928
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.type=eng
ro.build.user=builder5
ro.build.host=next-huawen
ro.build.tags=test-keys
ro.product.model=ICOU10GT 2
ro.product.brand=深圳市爱可西谷科技
ro.product.name=fiber_q10s
ro.product.device=fiber-q10s
ro.product.board=exdroid
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.board.platform=fiber
ro.build.product=fiber-q10s
ro.build.description=fiber_q10s-eng 4.2.2 JDQ39 20130928 test-keys
ro.build.fingerprint=Allwinner-Tablet/fiber_q10s/fiber-q10s:4.2.2/JDQ39/20130928:eng/test-keys
ro.build.characteristics=tablet
There are really similar except for the front camera, the kalley has a 2MP front camera and 5MP rear camera, instead icoo wich has a 0.3MP front camera and 5MP rear camera. So the next thing was fixed the wrong driver to work with this other camera. For that I rooted the device with the application Unlock Root, then after that I rename the driver gc0308.ko (0.3MP) to another name like gc0308_1.ko and copy the driver gc2035.ko (2MP) to gc0308.ko. The driver ov5640.ko (5MP) was working perfect. For that I do the next commands in adb shell.
Code:
adb shell
rename /system/modules/gc0308.ko /system/modules/gc0308_1.ko
cp /system/modules/gc2035.ko /system/modules/gc0308.ko
Or that can be done with the app Root Explorer 3.1.7 too.
If everything works ok, the lsmod out will be:
Code:
adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # lsmod
lsmod
rtl8150 8522 0 - Live 0x00000000
mcs7830 5847 0 - Live 0x00000000
qf9700 7312 0 - Live 0x00000000
asix 16337 0 - Live 0x00000000
afa750 10419 0 - Live 0x00000000
mma8452 6675 0 - Live 0x00000000
mma7660 7259 0 - Live 0x00000000
sw_keyboard 2660 0 - Live 0x00000000
ft5x_ts 41850 0 - Live 0x00000000
g2d_33 37741 0 - Live 0x00000000
vfe_v4l2 183191 0 - Live 0x00000000
gc2035 11225 1 - Live 0x00000000
ov5640 25938 1 - Live 0x00000000
vfe_subdev 3998 3 vfe_v4l2,gc2035,ov5640, Live 0x00000000
vfe_os 2196 2 vfe_v4l2,vfe_subdev, Live 0x00000000
cci 3061 2 gc2035,ov5640, Live 0x00000000
cam_detect 30803 1 vfe_v4l2, Live 0x00000000
videobuf_dma_contig 5322 1 vfe_v4l2, Live 0x00000000
videobuf_core 15891 2 vfe_v4l2,videobuf_dma_contig, Live 0x00000000
dc_sunxi 6707 0 - Live 0x00000000 (O)
pvrsrvkm 298286 55 dc_sunxi, Live 0x00000000 (O)
hdmi 24878 0 - Live 0x00000000
lcd 10133 0 - Live 0x00000000
disp 1040937 9 dc_sunxi,hdmi,lcd, Live 0x00000000
nand 172747 8 - Live 0x00000000 (O)
[email protected]:/ #
How Upload the firmware:
The program to upload the firmware in format *.img to the table, is called: PhoenixSuit 1.0.6. The procedure is:
0. Open Phoenix Suit and load the image in Firmware part.
1. Shutdown off complete the tablet.
2. Press the button Upgrade in Phoenix Suit, press ok, ok, ok.
3. Hold the Volume - button.
4. Connect the mini usb to the PC at the same time you press 6 times the power button while holding the volumen -.
5. It will upload the firmware and ask for format yes or no, press yes and wait.
Hope this help somebody,
The question will be if anyone can make a custom recovery cwm o twp for this kind of tablet or even better a custom rom.
Original Firmware K-BOOK10
Hi, look at here, there is a firmware for your device. (sorry for my English, it isnt my native language )
Go to: w w w .kalley.com.co/manuales-y-descargas/16
Tablet 10" K-BOOK10 1.0 WinXP y Superior Espeñol 421,35Mb
Direct link: w w w .kalley.com.co//sites/default/files/k-book10.rar
Bye! :good:
you can share the firmware download link fallen
charlytrw said:
Hi, look at here, there is a firmware for your device. (sorry for my English, it isnt my native language )
Go to: w w w .kalley.com.co/manuales-y-descargas/16
Tablet 10" K-BOOK10 1.0 WinXP y Superior Espeñol 421,35Mb
Direct link: w w w .kalley.com.co//sites/default/files/k-book10.rar
Bye! :good:
Click to expand...
Click to collapse
you can share the firmware download link fallen
Hi, I have a problem with my phone, i dont know if is a hw or sw issue. When my phone is charging and i receive a call, rings for 2 or 3 seconds and then reboots. I tried many fw: .14, .17, cm11, and the behaviour is almost the same. (in .14 and .17 the phone suddenly shut down with no reason, in cm11 NOT ) I reach the klog and it seems to me a modem issue :S, please someone can give it a look and tell me, thanks in advance.
============================= KLog Information =============================
magic:FATALM003
prev_reboot_reason:FATALM
kernel_time:[000006EE.358A20E7]
first_rtc:[537A025A.1B89D3DE]
last_rtc:[537A0B5E.27AB99C4]
normal_boot:1
prev_normal_boot:1
klog_userdata_count:5
klog_internal_count:5
klog_external_count:5
system_on_off_state:0x10
sbl_bootup_time:0
aboot_bootup_time:0
android_bootup_time:0
android_shutdown_time:0
sysfs_sync_time:0
kernel_power_off_time:0
suspend_time:2335
resume_time:2870
android_version:4.2.2
modem_version:8930B-BAAAATAZQ-3228109-14-1014
flex_version:FF_SHP_SA77.0.1.1016
rpm_version:3.0.16842938
bootloader_version:1269-1300_S1_Boot_MSM_8X30_R1_25
linux_version:3.4.0-g74b701b-00054-gde56c65-dirty
version_id:15.3.A.1.17
build_version:SA77.0.1.1016
build_date:Wed Mar 26 00:50:55 CST 2014
build_type:user
build_user:cme
build_host:androidbs-desktop
build_key:release-keys
secure_mode:1
debug_mode:0
hw_id:7241
cpuinfo_max_freq:1026000
scaling_max_freq:1026000
sim_state:READY
============================= KLog Start =============================
KLog Category #0:
name:CRASH
size:8192
index:2290
overload:0
<2>[klog]fault_level=0x5, fault_type=-1, fault_msg=modem
<2>[klog]modem crash log:Error Crash Log Report. Version 3.
<2>
<2>Error in file: fws_task.c, line: 245
<2>Time of crash (m-d-y h:m:s): 05-19-2014 13:47:03
<2>Uptime (h:m:s): 0000:38:53
<2>Build ID: M8930B-AAAATAZM-3.2.28109
<2>REX_TCB ptr: 0x8cf18458
<2>tcb.task_name: IST 98
<2>Coredump ARCH type is: ERR_ARCH_QDSP6
<2>R0: 0x00000000
<2>R1: 0x8cee43f8
<2>R2: 0x00000000
<2>R3: 0x8ce28288
<2>R4: 0x000000fe
<2>R5: 0x06c0c5a0
<2>R6: 0x00000000
<2>R7: 0x00000001
<2>R8: 0xe353f7cf
<2>R9: 0x20c49ba5
<2>R10: 0xffdf7b00
<2>R11: 0x00000000
<2>R12: 0xffdf7b00
<2>R13: 0x0004afff
<2>R14: 0x8900cd98
<2>R15: 0x00000002
<2>R16: 0x8ad51378
<2>R17: 0x00000000
<2>R18: 0x00000000
<2>R19: 0x00000000
<2>R20: 0x89a76840
<2>R21: 0x00000000
<2>R22: 0x00000000
<2>R23: 0x00000000
<2>R24: 0x00000000
<2>R25: 0x00000000
<2>R26: 0x00000000
<2>R27: 0x00000000
<2>R28: 0x00000000
<2>SP: 0x8cf18d30
<2>FP: 0x8cf18d38
<2>LR: 0x89d6a88c
<2>PC: 0x895bab98
<2>
<3>modem subsystem failure reason: fws_task.c:245:Firmware generated fatal error..
<2>[klog]fault already exist:5, ignore:5
<2>[klog]klog_magic=FIQHNG###
<2>[klog]preset magic(warn-boot higher):magic=FATALM, state=1, buf=FATALM###
<2>[klog]new klog_magic:klog_magic=FATALM001, buf=FATALM001
<2>[klog]fault already exist:5, ignore:1
<0>Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
<2>[klog]klog_magic=FATALM001
<2>[klog]preset magic(warn-boot lower):magic=PANICA, state=2, buf=FATALM001
<2>[klog]new klog_magic:klog_magic=FATALM003, buf=FATALM003
<1>[<c0013e54>] (unwind_backtrace+0x0/0x11c) from [<c07fc2cc>] (panic+0x1c8/0x33c)
<1>[<c07fc2cc>] (panic+0x1c8/0x33c) from [<c005fd40>] (subsystem_restart_dev+0x29c/0x398)
<1>[<c005fd40>] (subsystem_restart_dev+0x29c/0x398) from [<c00369ac>] (notify_smsm_cb_clients_worker+0xa4/0x1c0)
<1>[<c00369ac>] (notify_smsm_cb_clients_worker+0xa4/0x1c0) from [<c009f4ec>] (process_one_work+0x280/0x488)
<1>[<c009f4ec>] (process_one_work+0x280/0x488) from [<c009f908>] (worker_thread+0x214/0x3b4)
<1>[<c009f908>] (worker_thread+0x214/0x3b4) from [<c00a3800>] (kthread+0x84/0x90)
<1>[<c00a3800>] (kthread+0x84/0x90) from [<c000eac8>] (kernel_thread_exit+0x0/0x8)
<3>wcnss_8960: crash shutdown : 0
<0>Rebooting in 5 seconds..
============================== KLog End ==============================
============================= KLog Start =============================
KLog Category #1:
name:APPSBL
size:6144
index:0
overload:0
<Empty>
============================== KLog End ==============================