Other omap4 based tablets rooting? - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

Anyone know if a generic tablet using the omap4 cpu (OMAP4430 dual core 1k mhz) can use the cyanogen rom for the archos? Picked up this pos for $13 (still overpriced) and am have a tough time finding a route to root and the archos seem about as close a cousin as I can find, thanks..
http://www.amazon.com/gp/product/B00JDRYKHK?psc=1&redirect=true&ref_=oh_aui_search_detailpage

---

Your link on Amazon gives 404 error. It's hard to tell beforehand, Archos boards have slightly modified kernel in comparison with Blaze platform (TI OMAP4 processors). Do you have /mnt/rawfs/tags file on your device?

---

Yeah listing has disappeared and I don't see a way at /mnt/rawfs/tags without root, I just did a factory reset though and am using the built in fm, don't have es on there, each time set this thing up through google it slows to a crawl and is close to being introduced to a brick wall..
This is the best tech info I've found so far, as far as I can ferret out this is the cpu it's using, really need to figure away to root on this pos..
http://system-on-a-chip.specout.com/l/388/Texas-Instruments-OMAP-4430
emailed svp support.. giving 1/100 odds that they are of ANY help..

---

Yup, you need root to read that file. It's FTAGs file with device's TAGs of it's parts (CPU, memory, display, etc.). This file is used on Archos devices for initialisation. Without root you may try to type "lsmod" to figure out your drivers/devices on your tablet. Also "uname -a" will give you current kernel without root. Also try "cat /proc/cpuinfo" and "cat /cpu/meminfo." Also you may try to investigate inside /sys/ directory for devices and its config and so on.

---

Uname-a and /cpu/meminfo not found
[email protected]:/ $uname -a
/system/bin/sh: uname: not found
____________________
127|[email protected]:/ $ cat /cpu/meminfo
/system/bin/sh: cat: /cpu/meminfo: No such file or directory
[email protected]:/ $cat /proc/cpuinfo
Processor : ARMv7 Processor rev 1 (v7l)
processor : 0
BogoMIPS: 1114.46
processor : 1
BogoMIPS: 1114.46
Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
Hardware: gs702a
Revision: 0000
Serial : 0000000000000000
____________________
[email protected]:/ $lsmod
wlan 594404 0 - Live 0x00000000 (O)
camera_drv 31073 0 - Live 0x00000000 (O)
camera_gc0309 27899 1 - Live 0x00000000 (O)
flash_light 2676 0 - Live 0x00000000 (O)
bma250 14186 0 - Live 0x00000000 (O)
ctp_icn83xx 23001 0 - Live 0x00000000 (O)
atc260x_cap_gauge 7631 0 - Live 0x00000000 (O)
gl5202_hdmi 68657 2 - Live 0x00000000 (O)
gl5202_tvout 11843 1 - Live 0x00000000 (O)
atv5202_vout 12533 0 - Live 0x00000000 (O)
atv5202_mmc 21991 0 - Live 0x00000000 (O)
mmc_block 16654 2 - Live 0x00000000 (O)
mmc_core 94484 2 atv5202_mmc,mmc_block, Live 0x00000000 (O)
option 16371 0 - Live 0x00000000 (O)
usb_wwan 8745 1 option, Live 0x00000000 (O)
galcore 150096 16 - Live 0x00000000 (O)
vce_drv 13768 0 - Live 0x00000000 (O)
vde_drv 15187 0 - Live 0x00000000 (O)
sndrv 35748 3 - Live 0x00000000 (O)
atc260x_audio 1355 1 sndrv, Live 0x00000000 (O)
monitor 17307 0 - Live 0x00000000 (O)
acts_hcd 83675 1 wlan, Live 0x00000000 (O)
g_android 110371 1 - Live 0x00000000 (O)
dummy_udc 4267 0 - Live 0x00000000 (O)
atc260x_rtc 5323 0 - Live 0x00000000 (O)
atc260x_power 16614 2 atc260x_cap_gauge,monitor, Live 0x00000000 (O)
atc260x_adckeypad 4520 0 - Live 0x00000000 (O)
atc260x_onoff 2969 0 - Live 0x00000000 (O)
atv5202_fb 8504 2 - Live 0x00000000 (O)
atv5202_lcd 8652 0 - Live 0x00000000 (O)
atv5202_backlight 5363 1 atv5202_lcd, Live 0x00000000 (O)
atv5202_de 54619 9 gl5202_hdmi,gl5202_tvout,atv5202_vout,atv5202_fb,atv5202_lcd)
blk2drv 4267 0 - Live 0x00000000 (O)
blk1drv 202004 8 gl5202_hdmi,g_android,blk2drv, Live 0x00000000 (O)
1|[email protected]:/ $ cd /sys
[email protected]:/sys $ ls
block
bus
class
dev
devices
firmware
fs
kernel
module
monitor
power

---

These are the other devices I find using this cpu
gs702a unknown TAB-700QC full_gs702a full_gs702a ARMv7 Processor rev 1 (v7l)
g
s702a Ramos Ramos W17Pro V3.0 full_gs702a full_gs702a ARMv7 Processor rev 1 (v7l)
gs702a ainol Novo8 Dream QuadCore full_gs702a full_gs702a ARMv7 Processor rev 1 (v7l)
gs702a unknown Full AOSP on Leopard SOC full_gs702a full_gs702a ARMv7 Processor rev 1 (v7l)
gs702a ainol Novo 10 Hero QuadCore full_gs702a full_gs702a ARMv7 Processor rev 1 (v7l) gs702a

---

Did I say "cat /cpu/meminfo"? Sorry, it was misspelling. Use "cat /proc/meminfo" instead. It will show memory of the device. uname command probably doesn't present to save up a bit more space.
What's the name of your device BTW?
"Hardware: gs702a" isn't device name, it's most probably the name of the motherboard on your device. Ainol Novo7 Venus device may also have this board. I don't think Archos gen9/gen10 kernel is compatible with "gs702a" boards. Take a look there:
https://github.com/archos-sa/archos-gpl-gen9-kernel-ics/tree/master/arch/arm/mach-omap2
I don't see board-gs702a there. Maybe you should try to search in older Gen8 kernels, IDK:
https://github.com/archos-sa/archos-gpl-gen8-kernel/tree/master/arch/arm/mach-omap2
Also do not see any gs702a here. You may try to look also in gen7/gen6 yourself.
Also, your modules from lsmod look very different. Here is an example of lsmod on Archos 80 G9 Turbo (A80S board with OMAP4460 ES1.1 CPU with Cypress tma340 touch screen chip modification):
$ lsmod
wl12xx_sdio 2674 0 - Live 0xbf172000
omaplfb_sgx540_120 18406 0 - Live 0xbf169000
pvrsrvkm_sgx540_120 305403 39 omaplfb_sgx540_120, Live 0xbf10c000
wl12xx 139383 0 - Live 0xbf0e2000
mac80211 254440 1 wl12xx, Live 0xbf097000
cfg80211 147250 2 wl12xx,mac80211, Live 0xbf06c000
bnep 8582 0 - Live 0xbf062000
btwilink 2515 0 - Live 0xbf05e000
hidp 11082 0 - Live 0xbf057000
rfcomm 26927 0 - Live 0xbf04c000
bluetooth 168422 7 bnep,btwilink,hidp,rfcomm, Live 0xbf01b000
compat 4281 5 bnep,btwilink,hidp,rfcomm,bluetooth, Live 0xbf016000
hso 24457 0 - Live 0xbf00c000
cypress_tma340 9736 0 - Live 0xbf000000
And example of its CPU info:
# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 10 (v7l)
processor : 0
BogoMIPS : 580.40
processor : 1
BogoMIPS : 582.85
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10
Hardware : ARCHOS A80S board
Revision : 0005
Serial : 0000000000000000
OMAP revision : OMAP4460 ES1.1
Boot : 5.05.000009
Also be careful. Make full backup of the whole MMC or other storage you have on device. And try to install some kind of Special developer edition firmware (backup menu in case some kind of partition is bad and do not load). Different devices may have different partitioning schemes with a lot of different partitions on the same device. Also, you should know that Archos firmware is encrypted and there are decryptors for it. Also, Archos kernel is signed, you will have problems with it because of checksum mismatch (if you will be doing strange things without understanding). There are also special tools for firmware modification like ACT Pad Firmware Modify Tool. But you should know what you are doing and double-check if you do not want to brick your device.

---

Ok, thanks for your help, I was guessing that this might be compatible. At least you got me thinking linux rather than android, funny if I install linux I usually don't even install a gui and use ssh for everything, but with android it just as likely I won't even have terminal installed, pretty good trick hiding the linux bones so well you forget it's just another desktop env.
And since I reset, and have not mainlined the goo, (ie not entering any google account info) I've side-loaded my apps instead, and it's running reasonably well vs slowing to a crawl once it gets hooked on the goo, so I'm sticking with the side, and kids.. just say no to the goo!!
thanks..