I've been trying to get morfic's Trinity UV11 kernel to work with both the Cyanogenmod 7.1-RC1 as well as reddev1's AOSP kernel. I've flashed everything through Clockworkmod as well as cleared the Dalvik-cache with the provided zip in the thread. The issue that comes up is that the phone boots into the sign-in screen fine but later on the touch response stops working and then the phone restarts. Is there something wrong with the roms/process that I'm using or is it just that my phone cannot handle the undervoltage of the ROM? Any suggestions would be welcome!
boredomkillz said:
I've been trying to get morfic's Trinity UV11 kernel to work with both the Cyanogenmod 7.1-RC1 as well as reddev1's AOSP kernel. I've flashed everything through Clockworkmod as well as cleared the Dalvik-cache with the provided zip in the thread. The issue that comes up is that the phone boots into the sign-in screen fine but later on the touch response stops working and then the phone restarts. Is there something wrong with the roms/process that I'm using or is it just that my phone cannot handle the undervoltage of the ROM? Any suggestions would be welcome!
Click to expand...
Click to collapse
update your cm7, rc1 is old and outdated. try the latest cm nightly or cm kang. flash the latest, your gapps, and the kernel. in that order, then reboot.
simms22 said:
update your cm7, rc1 is old and outdated. try the latest cm nightly or cm kang. flash the latest, your gapps, and the kernel. in that order, then reboot.
Click to expand...
Click to collapse
Do you have any suggestions for stable AOSP roms that would work with this kernel? I'm trying to avoid the CM7 nightlies just because of any possible stability issues.
boredomkillz said:
Do you have any suggestions for stable AOSP roms that would work with this kernel? I'm trying to avoid the CM7 nightlies just because of any possible stability issues.
Click to expand...
Click to collapse
na.. i run either nightly or kang as a daily. should be much more stable than rc1 in any case
Hmm I've done what you suggested (flashing the latest nightly, then gapps, then kernel) and still no luck getting past the sign in screen. I've also used the "battery pull" method of rebooting the phone that was noted in the thread and still have the same situation.
boredomkillz said:
Hmm I've done what you suggested (flashing the latest nightly, then gapps, then kernel) and still no luck getting past the sign in screen. I've also used the "battery pull" method of rebooting the phone that was noted in the thread and still have the same situation.
Click to expand...
Click to collapse
does it work with any other rom/kernel?
simms22 said:
does it work with any other rom/kernel?
Click to expand...
Click to collapse
I've done a CM7/Netarchy(BFS) as well as reddev1's/Netarchy(BFS) combination which have both worked well without a hitch.
Related
I just flashed the ROM "Team Tiamat Xoom Rom 2.1 Hammerhead". The first thing that pops up is a system update notification, should I update it? Am I running the risk of bricking it? Thank you
chui1989 said:
I just flashed the ROM "Team Tiamat Xoom Rom 2.1 Hammerhead". The first thing that pops up is a system update notification, should I update it? Am I running the risk of bricking it? Thank you
Click to expand...
Click to collapse
If you are rooted/with custom rom, don't accept any OTA system updates. It will mess you up.
No instead you should make a nandroid backup and flash one of the ics roms.
i flashed the custom rom but I don't know if I can still receive ota after a custom rom. Also I tried ics rom and it messed up my ram so much
chui1989 said:
i flashed the custom rom but I don't know if I can still receive ota after a custom rom. Also I tried ics rom and it messed up my ram so much
Click to expand...
Click to collapse
Don't accept an OTA update. Also, ICS has improved my memory management. What happened?
I flashed the unofficial cm9 ics, it is unstable and slow, my ram usage is up high. I saw the one you are using, but it says night built that scares me a little. How is it?
chui1989 said:
I flashed the unofficial cm9 ics, it is unstable and slow, my ram usage is up high. I saw the one you are using, but it says night built that scares me a little. How is it?
Click to expand...
Click to collapse
It is stellar! Build #59 is really fine.
Absolutely...the Team EOS Nightlies are perfectly complete builds at this stage they seem to be making minor changes in each nightly but the latest build (#61) is definitely stable and I use it as my daily driver with no problems...
If you flash it be sure to do a full wipe to avoid any problems...after the installation is complete be sure to also flash the latest gapps package 10.5 before leaving Clockwork
Everything should work just fine : )
Sent from my DROIDX using xda premium
I have a B50 101 running AOKP Build 4. I tried installing Harmony Kernel and it won't go past the boot animation. I had this same problem trying to flash the K.A.T. kernel on Eos 3, it just won't go past the boot anim. Why is it doing this? I really want to run a different kernel on these roms.
:cyclops:
t1.8matt said:
I have a B50 101 running AOKP Build 4. I tried installing Harmony Kernel and it won't go past the boot animation. I had this same problem trying to flash the K.A.T. kernel on Eos 3, it just won't go past the boot anim. Why is it doing this? I really want to run a different kernel on these roms.
Click to expand...
Click to collapse
I'm having the same problem since flashing #76 , also the tablet shuts down when not in use which it didn't do before. I've tried flashing KAT and something with Voodoo in the name but same as you stuck at boot animation. Let me know if you find a fix.
I haven't been able to figure it out. I was also having problems with the eos 3 nightlies with rebooting my tablet when hooking up the charger and the lock screen disappearing when waking from a long deep sleep.
t1.8matt said:
I have a B50 101 running AOKP Build 4. I tried installing Harmony Kernel and it won't go past the boot animation. I had this same problem trying to flash the K.A.T. kernel on Eos 3, it just won't go past the boot anim. Why is it doing this? I really want to run a different kernel on these roms.
Click to expand...
Click to collapse
According to the thread on Rootzwiki, the ROM is not compatible with other kernels than stock: http://rootzwiki.com/topic/31009-tf101-kang-aokp-jb-preview-rolling-release/
Thanks for the info. Do you happen to know which jb roms are compatible with kernels?
t1.8matt said:
Thanks for the info. Do you happen to know which jb roms are compatible with kernels?
Click to expand...
Click to collapse
I'm on EOS with the KAT kernel, but make sure you have the latest version of KAT (47b), on RaymanFX CM10 already has a kernel which can OC, so I would suggest not to flash a different kernel.
Thanks. Where can I find rayman fx or should I just Google it?
t1.8matt said:
Thanks. Where can I find rayman fx or should I just Google it?
Click to expand...
Click to collapse
Look here for TF101 ROMS: http://forum.xda-developers.com/forumdisplay.php?f=1107
For the past few days now, I've been attempting to flash $droyd$'s unofficial AOKP and thicklizard's komodo kernel, with no success. I've fastboot flashed before and/or after, wiped everything, run wipe scripts, chanted voodoo prayers, but nothing has worked. It either hangs on the boot animation, or occasionally makes it to the welcome screen before freezing and rebooting. I've been flashing ROM's on this thing for a while, and have been using unofficial cm10.1 so far as my daily driver. What the hell am I doing wrong?
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
AKToronto said:
Not sure but you may also still want to flash the kernel zip and then fastboot flash. There may be kernel modules that the zip needs to install for the kernel to work well on 10.1
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Still no dice unfortunately, I guess it's just not meant to be. CM10.1 is running great so I don't have much to complain about.
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
trathiang said:
Ok I think I've pinpointed the problem-it has something to do OC kernels. I just flashed your new Canuck kernel with PACman and I'm getting the same freezing and rebooting issue. Is my phone overheating somehow?
Click to expand...
Click to collapse
Are these kernels being flashed with arioma installer... If you go to my aokp thread 2nd post you will see a tweaked 4.2 version-- it already has komodo modules installed and komodo is the boot.IMG inside the zip... Do this no skipseys---download that rom-- fastboot the boot.IMG in my zip---boot to recovery and wipe every thing INCLUDING SD CARD..x3---- now mount your phone to PC and copy and paste the ROM zip to your SD card..it will look weird cause it will be the only thing on there. ----- now install ROM then wipe only the caches after that--- hit reboot----system
And enjoy aokp with komodo kernel... Now to explain---every time you re flash that kernel you are stacking modules that is why you won't boot and also why you now need to do the spring cleaning wipe.... If you follow those steps exact no skipseys you will get it done---
Sent from my Nexus 7 using xda premium
Eureka! Did adb bugreport while it was booting to see what was going wrong, and I saw that there was something up with the voltages. Set the clock speed to minimum and then turned up the voltages in kernel tuner and VOILA, working overclock! I guess my phone, for whatever reason, disliked the undervolted voltages.
I got my N5 yesterday
unlocked bootloader
running TWRP
can flash and setup any rom
CAN NOT GET ANY KERNEL TO BOOT (using CM types when available, latest try was running sylentprofet minimal}
not sure what is going on, probably something small that I am missing.
tried:
faux
franco
N3o
ElementalX
Sorry if it is a simple fix. Did try to search but no real results that helped
If you're running cm look for CAF kernels.
As stated above, the problem started when you flashed, faux, franco kernel. Elementalx has a version which is compatible to CM Roms but need to read well. I heard of some people having problems after flashing franco, where another kernel wouldn't boot after franco.
Do a clean Rom installation, boot the phone with the stock CM kernel, then try to flash Chaos kernel and see how it does
thanks
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
orvon.freeman said:
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
Click to expand...
Click to collapse
Glad you got it working
A quick search returned this from faux. more CAF info available around:
http://forum.xda-developers.com/showpost.php?p=46098546&postcount=15393
I've been using Temasek's UNOFFICIAL Build, for his last 3 build updates with TYR kernel. I decided I wanted to try out AK, or Render Kernel with Tamasek. Flashed new UKM update from AK, flashed new kernel. Restarted the phone and it constantly reboots on One+ logo. Never loads boot animation. Decided to fully wipe the phone, including system and reflash Tamesek. Then tried flashing AK. Same problem. Tried full wiping again and flashing a different rom and AK kernel or Render kernel and same issue. Reflashed TYR kernel and it works perfectly fine.
I have no idea what's going on. But, I don't want to be stuck using only 1 kernel. Any ideas?
garz said:
I've been using Temasek's UNOFFICIAL Build, for his last 3 build updates with TYR kernel. I decided I wanted to try out AK, or Render Kernel with Tamasek. Flashed new UKM update from AK, flashed new kernel. Restarted the phone and it constantly reboots on One+ logo. Never loads boot animation. Decided to fully wipe the phone, including system and reflash Tamesek. Then tried flashing AK. Same problem. Tried full wiping again and flashing a different rom and AK kernel or Render kernel and same issue. Reflashed TYR kernel and it works perfectly fine.
I have no idea what's going on. But, I don't want to be stuck using only 1 kernel. Any ideas?
Click to expand...
Click to collapse
Better ask your question in AK or Temasek thread
A friend of mine is having touch issues with his opo! It's unresponsive sometimes! He is on stock unrooted 05q. Will flashing a custom kernel help?
If yes please suggest a good one
garz said:
I've been using Temasek's UNOFFICIAL Build, for his last 3 build updates with TYR kernel. I decided I wanted to try out AK, or Render Kernel with Tamasek. Flashed new UKM update from AK, flashed new kernel. Restarted the phone and it constantly reboots on One+ logo. Never loads boot animation. Decided to fully wipe the phone, including system and reflash Tamesek. Then tried flashing AK. Same problem. Tried full wiping again and flashing a different rom and AK kernel or Render kernel and same issue. Reflashed TYR kernel and it works perfectly fine.
I have no idea what's going on. But, I don't want to be stuck using only 1 kernel. Any ideas?
Click to expand...
Click to collapse
Dirty flash the ROM first to get the stock kernel back, then try flashing another kernel.
Flash latest twrp.
Sent from my bacon!!!!!
Use twrp recovery
loridoo said:
Use twrp recovery
Click to expand...
Click to collapse
What a useful answer.
Sent from my bacon!!!!!
timmaaa said:
Dirty flash the ROM first to get the stock kernel back, then try flashing another kernel.
Click to expand...
Click to collapse
I tried this, I now tried 3 different roms. SlimSaber unnofficial, Robbie's CM12, and Euphoria and all of them do now allow me to flash AK kernel or any other kernel. I think something borked on one of TYR's kernel flashes. May I should reset the phone completely. Is there an option to do this with ODIN that someone can point me into?
NickosD said:
Flash latest twrp.
Sent from my bacon!!!!!
Click to expand...
Click to collapse
Duh...
garz said:
Is there an option to do this with ODIN that someone can point me into?
Duh...
Click to expand...
Click to collapse
Odin is just for Samsung phone
We use fastboot instead
waterdaan said:
Odin is just for Samsung phone
We use fastboot instead
Click to expand...
Click to collapse
Right, just wiped/restored my phone to stock/factory all the way back to CM11S30R. Unlocked bootloader, rerooted, upgraded firmware and reflashed Euphoria and still can't flash AK without bootloopingon the ONE+ logo. I then clean wiped, and flashed Euphoria and same issue. I am at a loss, I have no idea what else to do.
garz said:
Right, just wiped/restored my phone to stock/factory all the way back to CM11S30R. Unlocked bootloader, rerooted, upgraded firmware and reflashed Euphoria and still can't flash AK without bootloopingon the ONE+ logo. I then clean wiped, and flashed Euphoria and same issue. I am at a loss, I have no idea what else to do.
Click to expand...
Click to collapse
No need to flash back to 30R
I'd flash the 05Q stock using fastboot
That comes with latest modem etc
Then if you'd like flash custom rom in recovery
Unlock bootloader?? Did you lock it after unlocking it?
What version of recovery are you using?
waterdaan said:
No need to flash back to 30R
I'd flash the 05Q stock using fastboot
That comes with latest modem etc
Then if you'd like flash custom rom in recovery
Unlock bootloader?? Did you lock it after unlocking it?
What version of recovery are you using?
Click to expand...
Click to collapse
I am using TWRP 2.8.5.1.. I just figured I'd redo everything from scratch. Nothing is working. I can only flash TYR with all the roms I've tried, where it successfully boots. I'm also flashing UKM 3.8.1.
garz said:
I am using TWRP 2.8.5.1.. I just figured I'd redo everything from scratch. Nothing is working. I can only flash TYR with all the roms I've tried, where it successfully boots. I'm also flashing UKM 3.8.1.
Click to expand...
Click to collapse
try to redownload AK kernel, Maybe a bad download
Anyway good luck
waterdaan said:
try to redownload AK kernel, Maybe a bad download
Anyway good luck
Click to expand...
Click to collapse
Did that twice. Installs perfectly every time.