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.
can anyone help!
i keep getting 'Error' when trying to turn wifi on,
i have tried :
installing a 354 recovery
installing a 354 package
wifi does not work at this point
installed a custom rom
wifi still does not work
have tried using qdl to repair but still not luck, anyone any ideas at all? other than sending it back to dell!?
when i finished flashing alpha3-cm-9.0.0-RC0-Atrix-KANG-signed.zip from this website http://goo-inside.me/roms/jokersax/ today.
i occured a strange problem.when i first entered the system correctly.
then phone reboot suddenly and stuck at the moto logo.
i don't know why and i did 3wipes and flashed the bell radio.
anyone has any answers?? thx a lot.
go here, there are 40 + pages that will help you http://forum.xda-developers.com/showthread.php?t=1445052
you have to format /system in recovery and install ICS again
I have a Transformer Prime and I decided to flash CM9. I installed CWM via Rom Manager. This was my first time flashing with my prime but I have flashed many times with my droid 1 so I'm not completely new to this. Wiped data, flashed CM9 and then flashed google apps on top of that. This created a bootloop for whatever reason which I fixed using adb. (First time ever using adb). CM9 booted up fine but when it goes to ask for my account info during first bootup, the wifi wont turn on. It says "Turning wifi on" but never does anything. Let it sit for half an hour and nothing. Decided to skip that thinking it might work when everything is booted up. Suffice to say, doesn't work. Says MAC address unavailable. Bluetooth wont turn on either. Can't browse files at all due to no file manager app. Rom manager is installed but says CWM is no longer installed. Can boot into fastboot only but not CWM. Can't reinstall CM9 or stock ROM due to no CWM. Anyone know how I can fix this? I would just like to get the wifi on or get back to stock if that is necessary. Any help would be appreciated.
EDIT: Correction, am now able to enter CWM, going to wipe and reflash.
EDIT2: Solved the issue. Figures, after 5 hours of trying to figure it out and then posting, I fix the issue in 10 minutes. Sorry for the post.
Glad you made it.
Thank you for getting through this either alone or through search. Also, thank you for sharing how you solved it. Can i also thank you again for editing the title of the thread to include a [SOLVED] tag?
Yesterday,after I flashed stock ICS rom through odin, I noticed that i can't connect to any kind of wifi connection, even wifi sharing from other devices! it says just "obtaining ip address" and nothing. stuck like that forever. What?
Liorgex said:
Yesterday,after I flashed stock ICS rom through odin, I noticed that i can't connect to any kind of wifi connection, even wifi sharing from other devices! it says just "obtaining ip address" and nothing. stuck like that forever. What?
Click to expand...
Click to collapse
My problem was unable to turn on wifi, wifi stuck at the stage of turning on.... and forever like that cant off and on.
Most probably is hardware problem coz i have tried many ways to solve including flash back to stock rom,change modem,change kernel and etc.
good luck for you,hope you are not the same problem with me.
Liorgex said:
Yesterday,after I flashed stock ICS rom through odin, I noticed that i can't connect to any kind of wifi connection, even wifi sharing from other devices! it says just "obtaining ip address" and nothing. stuck like that forever. What?
Click to expand...
Click to collapse
Wifi is kernel-related.
So, try to flash another kernel to test.
Or if you don't want to flash another kernel, check in menu Settings > wifi > (menu button) Advanced > Use static ip.
Try to enabled and connect.
Then disable and try to connect.
If that does not help, try to wipe cache (and Dalvik cache) in recovery mode.
Press Volume UP + Home + Power buttons as long as the recovery menu appears, then select wipe cache and reboot the phone.
P.S.: Check the configuration of your wifi router / WLAN access point, that is allows your phone to connect.
ok so i did everything again just to be sure and... my mistake! the problem starts not after the rom flashing but after cf root! have i done something wrong maybe?
I would say look for a custom rom that is already pre-rooted so then it should have all bugs to do with wifi removed.
I used to have a problem with the wifi myself which caused problems when turning it into a wireless hot spot and then wouldn't turn back off again.
But now im on the Custom Rom I am having no problems with wifi at all.
Hope this helps.
Galaxy S2 Running Paranoid v1.2a 4.0.4
Actually, I would say try a different kernel. CF-root is a kernel. Wifi drivers are in the kernel. Ergo... ?
Wifi is kernel related issue
try changing your kernel
you mite wanna chk dis
http://forum.xda-developers.com/showthread.php?p=27210265
lolamok said:
My problem was unable to turn on wifi, wifi stuck at the stage of turning on.... and forever like that cant off and on.
Most probably is hardware problem coz i have tried many ways to solve including flash back to stock rom,change modem,change kernel and etc.
good luck for you,hope you are not the same problem with me.
Click to expand...
Click to collapse
Im having the same problem here, any luck so far?
may have something to do with the root. my phone had this issues once. just flash your phone with the correct rom and do NOT root it again as it may have something to do with the root itself. or just something got messed up during the rooting process