Database Info

Phone wont bootup on Imoseyon kernel

Just flashed imoseyon's kernel on my rooted thunderbolt and now I'm stuck in a bootloop...any advice? I've running stock rom.

It's the lean version of his kernel and thats the only thing I flashed. I cleared cache + davik cache before flashing.

I was able to do a restore, but I want to use this kernel

It sounds stupid, but try again. Clear cache and dalvik

I've tried 5 times Even tried uninstalling setcpu and unfreezing all the bloatapps that I had frozen. Still get stuck on boot

I've also tried re-downloading the kernal file in case it was corrupt...no luck still.

Which Imoseyon kernel are you running?
Could it be that your particular Tbolt won't handle the lower voltage? Also you might want to check the md5sum again.
Good luck.

brenick said:
Which Imoseyon kernel are you running?
Could it be that your particular Tbolt won't handle the lower voltage? Also you might want to check the md5sum again.
Good luck.
Click to expand...
Click to collapse
I said its the lean version, and he doesnt post md5sum so I have nothing to compare to. But thanks for using my thread to +1 your post count....

wifi is broke and my data is stuck on 1X only now after doing advanced restore-->reboot only.

Did you flash the GB Sense kernel instead of the Froyo kernel?

I used this 1... http://forum.xda-developers.com/showthread.php?t=1021404 It says Froyo... where can I find the stock kernel that you get after rooting? I need to get wifi/data working again now.

I mount the phone as disk drive on my computer, and I can only view the SD Card...ugh whats going on, so many issues after flashing this kernel

I did a factory reset now and I still cant connect to wifi/3g/4g...I think I need to flash the stock kernel to fix it. Can someone point me in the right direction please?

Flash another rom such as BAMF, whenever you flash a rom it flashes the kernel that is included in the rom as well.

I'm using his kernel just fine. Can you check your radio version?
Sent from my ADR6400L using XDA App

radio 1.16.00.0402, and Im on the stock ROM, dont want to use a special ROM...

Flash a rom or the stock rom that should get you on another kernel. Also, my TB couldn't handle some of the kernels. I was never able to get it at 1.92ghz. I can only use the normal version. Try one of the other versions. Best of luck!
Sent from my DROID PRO using Tapatalk

make sure the kernel is not oc'd to 1.92.................most phones can not handle that.

[Q] Cannot enable WiFi on TF101

Odd thing happened today. I was testing out the EOS cornerstone new rom and was having issues with WiFi so I restored my Stock ICS setup but now I can not enable the WiFi.
The WiFi icon is greyed out on the settings tab and I can not swipe the WiFi to on in the settings app.
Has anyone seen this before? Did the WiFi die?

Just flash the ROM you were using again without any wipe. (Flash the ROM that your backup is base upon)

It seems the backup has the HC version of the wifi. I flashed the other rom again and the wifi is working fine.
Thanks.

Same Problem
Hi Guys,
got the same Problem....
Had Revoler 4 1.3.1, tried CM9+Cornerstone, got back with backup.... now i cant turn on Wifi =(
any suggestions?

michl1303 said:
Hi Guys,
got the same Problem....
Had Revoler 4 1.3.1, tried CM9+Cornerstone, got back with backup.... now i cant turn on Wifi =(
any suggestions?
Click to expand...
Click to collapse
Just flash Revolver ROM again, no wipe needed

I installed the AOSP test build of ICS, now I too am having wifi issues. I saw the ROM had it listed that there was a bug with the wifi so I didn't think much of it at first. I then installed Android Revolution but now the wifi still doesn't work.
I accidentally deleted my backup ROM..
Tablet says no MAC address found, and wifi settings app just hangs when trying to turn on.. I've re-flashed numerous times.. I've formatted all the partitions, re-flashed again....
Any ideas?

I had to flash the rom again (EOS cornerstone) and the wifi started working. I just ended up flashing the stock ICS from the asus site to start freh again.
It seems like the backup in CWM does something strange with the wifi driver.

I'm start a new thread here.
http://forum.xda-developers.com/showthread.php?p=23221362
I reflashed EOS, wifi works, but i now have a different MAC address than I did before.

[Q] - Ruined for all other ROMs?

So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?

frankxanders said:
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
Click to expand...
Click to collapse
What recovery are you using? might pay to try another (Recommended: http://forum.xda-developers.com/showthread.php?t=1759452)

You may want to obtain a kernel compatible with the ROM you want to try and flash both the ROM and kernel at the same time. The wrong kernel could definitely cause both the booting problems and the wifi not turning on.

I think about a kernel problem too, go to your ROM thread and you'll see the best kernel to flash with it...

[Q] Does going back to stable CM7 leave some files behind?

Hi
So I was using CM7 with Link2SD and everything was going smoothly.
Then I discovered I could call using my headphones which was possible on stock ROM. After I searched, I found out that the nightly build had that bug corrected. So I update to nightly.
Then the you know what hit the fan
So I boot back and get a warning from Link2SD that my card could not be mounted during boot and that therefore my apps were not available and that I had to reboot. So I did. Same message. I recreated the scripts and rebooted, same message.
So I go back on the stable version of CM7. Same problem.
I tried recreating the partitions on gparted and using ClockWorkMod and trying different formats (ext2, ext3, ext4, Fat32), formatted everything including /system, went back to stock ROM and then back on CM7, nothing works! I keep getting the same error message.
I went to see the log and it says that it cannot be mounted because device or resource busy.
So, here are my questions:
- Does that mean that something from the nightly build has been left behind?
- If so, how do I get rid of it?
- If not, how can I get rid of this error. I tried everything I could find.
I also think that it may have left some files behind because I'm on Koodo. The only stock ROM I could find was Telus. The first time I restored stock ROM using the Telus ROM, I had to do some keypad numbering to get Koodo back. But the last time I restored the stock ROM it detected it as Koodo instantly.
Thank you

[Q] Here's a head scratcher! CM10 CWM problem?

I was happily running along with my GT2 10.1 5113 using CM10, updating nightlies, all is well. Then I put the CM 10.1 unofficial, that went well, was using it and put the 12/09 version on, that went well also. However I decided I didn't like it and wanted to go back to CM10. I had a back up that I made in CWM with the 12/08 nightly and had begun restoring it when an error came up stopping the restore, only said file error restore can't continue. OK, that kinda blows chunks cause I know my rom just got hammered. Tried to restart, boot loop. Got back into recovery re flashed the CM 10.1, trying to save my data, bootloop. Got back in recovery and wiped data re flashed, bootloop. On an act of desparation I flashed the 12/08 nightly and, viola she lit up and booted to the setup screen.
Set it all back up and updated to the next nightly, 12/10 and I'll be danged, bootloop. Went back to recovery re-flashed the 12/08 nightly and all went well. No data loss just worked fine.
Bottom line I can't get anything but the 12/08 nightly to boot up. I even flashed stock with Odin, that bootlooped too! So I'm stumped.
It boots into the 12/08 nightly just fine and that's it.
I know this is wordy, but I wanted to make a thorough explanation. I feel this is related to the CWM error, but I have no idea where to go from here.
Anybody got a suggestion? All help is greatly appreciated.

I think cm10 installs jelly bean on your system. and switching back to an older version will cause the bootloop. that's what i believed happened to me when I installed cm10 by mistake instead of cm9 which is what i wanted. it took me several tries with odin and the stock rom to be able to go back.
I think the key is when you have cm10 installed then you need to enable the "usb debugging" in the developers section. that is probably what is stopping you from switching back to an earlier version or a new version or the stock rom using odin.
anyway that's how I was able to switch back to stock.

I think the reason you can´t restore CM10 is the fact that Android 4.2 introduces muti-users management. Thus, the system do not store in /sdcard/ any longer, but in /sdcard/0/ (for the first user). Since you still have a 4.1 recovery version, it doesn´t find the backups files any more. A solution is to move your sdcard data from /sdcard/0/ to /sdcard/ before restoring your backup.
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.

Einril said:
As for CM10, the 12/09 and 12/10 nightlies don´t boot, due to kernel changes. These changes were reverted in 12/11, so this one should boot.
Click to expand...
Click to collapse
Bingo! That worked, 12/11 worked. I had no idea that was happening. I made all the file changes actually because I wound up with sdcard/0/0/0 from all the flashing back and forth, that was funny. All is normal now thanks!
Sent from my GT-P5110 using xda premium