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.
Related
Hi,
Am in a fix as to what to do... I flashed my Folio AS100 successfully to load into Honeycomb 3.04, but for some reason, the wi-fi refuses to start up, and I only get "error" when trying to start up my wifi.
I have tried reloading different roms to no success...
Any help will be appreciated!
L
Is AS new version???
Solution Resolved!
Found out that somehow it booted into safe mode, just needed to boot it to recovery and it started to work! Thanks to all the developers!
So, it seems I've broken my android device down just right after I bought it.
I tried to enable connecting to AdHoc wi-fi network on my laptop following a guide from galaxytabhacks.com and in order to do that I needed my device to be rooted and busybox installed. There were no problems with the first step, but my device crashed after installing busybox: after Samsung logo appears, I see artifacts on the screen and nothing happens.
I performed wipe data/factory reset via ClockworkMod but it didn't help.
Now I've formatted /system and I'm gonna download full version of official firmware and flash it using Odin. Am I doing it the right way? Will my device survive after crash I've just described?
Thanks in advance.
Hi
Seems I have the absolute identical problem...
Did you find a way to solve it?
Thanx in advance!
- I have an Atrix with Aura 1.2.2.2 and Android 2.3.4
- The superuser wasn't working properly and long story short I tried installing BusyBox app from the market.
Here is where the problems start and I made them worst................
So in BusyBox I hit install and I see things being remove to then get a message about permission are not set. With this SuperUser stopped working I tried rebooting the phone and wifi is looping in trying to obtain IP.
I am so mad and tired that decided alowing the OTA 2.3.6 update to install since I am tired of the never ending message...
Now when the install is about to start CWM stops and leave me with Android and an exclamation mark in a triangle.
If I restart the phone and boots to the login screen.. after a minute i will shut down and go to CWM.
Help!!
Self reply for me an others..
Read read read.. Seems installing BusyBox from the Market has cause this issue to several people. So make sure you know what works for your phone or be a guinea pig like me
Currently I just finish reinstalling Aura rom which I am pretty sure will fix the issue.
hope it will be all fixed by now. let us know please.
FYI, there is a Super User Update Fix on the market/play which would solve your original issue.
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?
Hi everybody thanks for your help in advance,
My SGs2 is currently running siyah kernel v6.0.0.12 (the fancy one with touch recovery and dual boot).
The problems started when i recently switched from SuperSu to the open-source alternative Superuser. I'm using an app called live logcat (by Chainfire). It shows the logcat entries live as a boot animation. It was all hassle free when I used SuperSu with it. After switching to Superuser it kept getting root permission over and over for at least a minute (a previously common problem). So I was looking forward to getting it fixed since other users reported the same problem. So whenever a new version came out, I tried if it was finally fixed.
After updating to the latest version yesterday and starting the app once again, the phone crashed with the screen turning black (status bar still visible). It then rebooted and a message stating
Android is upgrading..
Starting applications
Click to expand...
Click to collapse
appeared. Whenever I reboot my phone this message appears and won't go away. I can access recovery but clearing cache and/or dalvik cache makes the window say: Optimizing application <x> out of <y>. When it is through with optimizing, 'starting applications' reappears.
I honestly have no idea what else to do.
So my question is how can I get that darn thing to boot correctly?
I'm looking for a solution which doesn't involve factory reset.
If anybody can help he/she is much appreciated.