Loading a module - Android Q&A, Help & Troubleshooting

Hello,
So I have a module that I'm trying to load which is a touch screen driver for my cheap chinese tablet, Allwinner A13. Everytime I add the insmod line it won't stick after reboot, I've tried making a script to do it at every boot, but it still does not work. Any tips? P.S: I'm a noob.

Related

[Q] TUN.KO causing reboot cycle

Hi there,
while trying to test a VPN client, I installed TUN.KO into /data/local/kernel_modules on my ROOT'd Vibrant, which immediately reloaded and then once the reboot is finished it reboots again, and never stops.
I think I installed the wrong version of TUN.KO (possibly a Galaxy Tab version), and the VPN client I am running automatically starts on reboot, so I guess is triggering the crash.
Does anyone know if there is there a way I can delete the TUN.KO file? Or is there a way to stop the VPN client starting at boot time? Or would flashing to a new ROM get rid of the offending file ?
Please help !!!
Thanks in advance,
Ronnie
So ... I went into recovery mode and reset to factory default ... problem solved ... now to get everything reinstalled.

[Q] Allwinner A13 CWM boot & Touchscreen failure

Hello everyone,
Here is my problem of which I hope you can help me out.
I own a Allwinner A13 7 inch tablet, on which I installed the Cyanogen 10 mod (Due to restrictions I cannot place the link to the mod)
The problem is I probably installed the wrong touchscreen driver, so the tablet boots perfectly into the Mod but I can't do anything.
Normally it would be no problem to just put back my backup, but I can't get it to boot into CWM.
In the first place I rebooted into CWM to instal the mod by adding the following command through the "terminal app" before rebooting,
Command: "echo -e 'boot-recovery\0' > /dev/block/nandf; sync"
Now I cannot use the screen so i cant use the terminal.
I also cannot use ADB because USB debugging is standard switched of after flashing a new MOD.
Does anyone know if there is another way to get into CWM??
Thanks a LOT!
Thanks a lot!
I will have a look
Do you by change know where to get a working stock rom? I flashed one which i found using google a couple of times but it only results in a Boot loop (I have no luck at all!).
Thanks!
Update: found a stock version that works. But no my touchscreen is inverted.
Also I probably made another **** up, because I accepted the format option of Livesuit, so now I lost my backup.....

[Q] Wifi driver not loading on V88 OMA rom

Hi all,
I'm not sure this thread goes here, sorry if it doesn't.
I bought a Chuwi V88 tablet one month ago. When i received it, everything was running ok. About a week later, WiFi started to fail, i couldn't click the "no/yes" switch to enable it (in the best case, when i could click it, only "enabling wifi" message appeared indefinitely). I tried to flash OMA (http://forum.xda-developers.com/showthread.php?t=2310818) rom to solve it but anything changed. Now i have time again to try to repair the chuwi, but i don't know how to continue.
My actual status is:
V88 S/N (in the backside): 16G2131100086
ROM: Oma_RK31_Chuwi_V88_JB_4.2.2_windoof_v5.2 (multiwindow version)
Kernel: bob #445
WifiFix installed
Factory wipe done (no changes)
When I connect the tablet to ADB, logcat says:
E/WifiHW(412): Timeout to wait for Wifi interface within 15 seconds.
D/WifiHW(412): wifi_unload_driver
D/WifiHW(412): Check driver status: not loaded
E/WifiStateMachine(412): Failed to load driver!
E/WifiStateMachine(412): DriverFailedState
Could someone helps me to solve the problem? I've read the original thread, but i can't post there by now.
I have the exact same problem, hopefully me posting this here will give it more chance of someone more knowledgeable finding it. I'd ask Oma but I first need 10 posts. 9 to go I suppose...

all winner A13 tablet help!!!

hi,
i have a Generic - Tablet screen 7" Allwinner A13 1.0GHz CPU Android 4.0, 4 GB HDD 512 MB , and i used live suit to flash a rom, but the problem is that always when i try to flash a room the touch screen do not work, i am a newbie with this high tech stuff, if anyone could help me i would appreciate a lot .
i installed this rom <> A13-EVB-V1.0-20130926-Android4.2.2-Os-root-MaPan from this site >>>>http://www.androidtablets.net/thread...13-roms.72449/
and i tried to install some drivers of this link but did not worked, i dunno if i run it correctly, i simply downloaded and pressed run.exe in the file of the download, this is the site of the modules>>>http://forum.xda-developers.com/show....php?t=2447819
i also tried installed the FaaastJB v2.5 rom and the touchscreen driver did not worked and any of those modules worked. so if anyone could help me please write me ....
What touch screen fix worked for me.
I have an A13 running FaaastJB v2.5 and struggled for a long time getting the touch screen working.
The ROM I'm using came from
http://forum.xda-developers.com/showthread.php?t=2447819
The set of drivers that worked for me were the FOC110 which is the last of the SPECIAL TS modules listed
One time I had to load them twice in a row to get them working. It complains about missing directories when loading but worked for me.
Hope they work for you also

Trouble booting after install

So i have this problem on my compuiter, it's an Acer iconia tab w500, i had linux on it and a friend of mine told me about Remix os, i installed the latest version of it almost without any trouble, but afert playing with it for a while and turning it off it wouldn't turn on again, at first when it went in to grub rescue but i couldn't get further from there; then i tried installing the os again without grub, and after restarting it it said there was no bootable device...
I don't know what to do as i want to keep this system on my pc in single boot.
Thanks for any advice on this matter.

Categories

Resources