Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
What gingerbread roms have you tried? Also, what kernels were you using?
Sent from my ADR6400L using Tapatalk
don't have this issue on Synergy 3.0 running the latest ziggy kernel
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
I would try wiping, then installing the setup in my signature, but don't restore any apps at first or sync with Google so they're downloaded automatically. I think that you've got an app and a kernel that's interfering with one another. Try the ROM bone stock before you start restoring apps and see if the problem is there.
Rooted Thunderbolt on BAMF Sense 3.0 RC 4 with MR2 radio and latest dreamKernel.
Silentdawn3 said:
I've tried every GB rom on here, as well as both kernels
also, Ziggy kernel? You in the right section?
Click to expand...
Click to collapse
when you say both kernels are you referring to the radios? cause mr2 and mr.5 are radios not kernels
Silentdawn3 said:
Okay I've posted about this before, but still can't figure it out...
My issue is this: When I install a GB rom, everything runs fine until my screen goes off.... its even fine if it goes off for a second, but if it sits for more than one second it reboots. A full reboot. I've tried both GB kernels, as well as MR 2 and 2.5. I've also tried using setcpu to set the minimum all the way up to 1.4GHz with no help.
Can someone help me fix this screen off issue? PLEASE?
Seems to have something with the dip in processor speed because when my phone is downloading from the market or signing in to google, or doing anything for that matter... the problem doesnt occur.
I don't really accept that I can't use Gingerbread because of this... there HAS to be a fix.
Thanks yall
Click to expand...
Click to collapse
I share your pain with this exact problem. I have been doing all types of testing these last two days to see if there is any combination of ROMS and Kernals that would work for me.
I can flash any ROM I want, and the only Kernal that I can successfully use is this one:
Imoseyan GB Stock Kernal
With this Kernal, I can use my phone all I want, let the screen go black, hit the lock screen button and I have never had a reboot.
I have run Thunderstick, BAMF 2.1, BAMF 3.0, Gingertheory, with this kernal and it will run fine.
When I change to any of these Kernals, I get the constant reboots when my screen goes off, just like the OP described.
* Imoseyon Lean Test
* Imoseyon 184mhz
* Imoseyon USBfix
* Imoseyon 2.5.3 test 7
* Nerozehl's dreamkernal 2.3.2
Of course, when flashing any ROMS and Kernal combinations, I would do a complete wipe before doing so. I should also mention that I am using MR2 radio. I can also use MR2.5 with the GB Stock Kernal and it runs fine.
So like the OP, it seems to be something to do with the kernal that my phone does not like and can't figure out. Anything other than the stock kernal, and my phone will constantaly reboot after the screen goes black.
I should also mention that I have used the speektweah.sh in terminal emulator and tried all of the different voltage settings and it had no effect. Also disabled it and tried using SetCPU and no luck either.
I have also tried all of the ROMS without allowing any apps to update by skipping the google account sign in. So basically all of the ROMS were running in their native state, and the outcome would be the same.
FOR THE OP
Try running the stock kernal and let us know if that works for you. You should just be able to flash it in CWM, reboot and you will know right away if it is working correctly.
The real question I need to figure out is this. What is different about the GB Stock Kernal from all the others that would be having this impact on our phones?
I've tried all of this except installing the above kernel. I'll give that a shot, thanks.
As for installing without apps, I've tried that. Tried everything. Lets hope the stock kernel works!
I've been running Das BAMF Gingerstripped with Imo's kernel and never had this issue. It sounds like maybe something is bad with the cpu profiling becoming unstable when screen-off profiles kick in.
sg1dan said:
don't have this issue on Synergy 3.0 running the latest ziggy kernel
Click to expand...
Click to collapse
I can confirm that this one worked for me too. Synergy 3.0 running Ziggy's Kernal and everything works well.
Anyone know where to grab just the Kernal? Can't seem to find the latest download.
I should also add, that when I do flash the Stock GB kernal so that my ROM will be stable.... my camera freezes everytime I try to take a picture. Happens in every ROM I mentioned above. However, it works fine before I flash the stock kernal.
running "stock kernel" it looks to be fixed. Looks like I tried this before as I already had the file but.... works now for some reason
Thanks.
Will report back if it ****s up
Related
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
yes its a kernel issue. what version of software are you running?
I had the wifi error issue, and i flashed the kernel on top of the rom and it works now
Depending on the ROM you flashed, it may or may not display "Flash Kernel after." In which then you flash it. This'll take care of all Bluetooth and Wi-Fi Issues!
If you're having issues let me know.
I had the same issue I was using stock kernel for tmobile version 1.36.531.6 on mine which I had over the air updated to 1.43.531.3. This created the wifi error and bluetooth issue, I had to try different kernels to try to figure this thing out...It will posted in my read me page when I get a chance
It's a kernel issue, there are actually three different kernels, not two, I posted this in xboarders thread, but He hasn't updated his page.
kernels
1: for tmobile software stock 1.43.531.3, this is not available anywhere on the amaze forums, i had to personally extract this from the rooted stock rom that xboarder provided
2: for tmobile software stock 1.36.531.6 and 1.36.531.5 and lower, this stock i believe is the one xboarder has up as the original boot.img
3: faux's custom kernel, this kernel will work with all versions i believe
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
andy55 said:
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
Click to expand...
Click to collapse
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
I told you rooting is not for you but you thought I was attacking you. But seriously if you do not know what you are doing you will mess up the phone. you still havent because there still is no s-off so pretty much your phone is kinda locked
seansk said:
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
Click to expand...
Click to collapse
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
seansk said:
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
Click to expand...
Click to collapse
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
yes lets wait, with people with lets experience, I tend to dumb things down when asking questions...I am not doing it to demean them, but It's the only way to get any real good answers and being able to help them. Then over time they'll learn
sean, I was running the android revolution 1.1, and tried a couple different kernels and nothing
But I ended up fixing the issue finally. The super wipe zip file I downloaded with AR 1.1 was corrupt, and wouldn't load properly, so I was installing a rom without doing a wipe every time. So, I put a working copy of the zip on the sd card, and did a manual wipe of the caches, re-installed AR 1.1 and all is well.
So, even though I was following all necessary steps, I failed to realize that the wipe zip was faulty, and really messed everything up, and when I changed the rom again to beastmod, I didn't install the correct kernel with it, so yet more issues.
Happy to say that it's all over, and I have a much faster phone with alot less bloat on it. Thanks to everyone!
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Flashed the kernel as xboarder showed in his thread and video.
ok, is there ANY POSSIBLE WAY to downgrade from the leaked firmware we had to flash for the RUU back to the stock one that came with the phone?
this phone has been utter garbage ever since i've done it (7 hour battery life, down from 15-17 hours...random reboots ALL THE TIME etc) and i'm sick of it, to the point where i'm ready to sell the phone and get something else.
is there ANY way to go back?
It is possible but as far as I know you'll need s-off
Sent from my cm_tenderloin using xda premium
well crap. here's hoping they get a nice method that's proven to work, because i need to drop this crap firmware. these reboots are reaaaaaaally annoying me. just had two within 10 minutes.
unless you have s-off there isnt.
but you should try reflashing the RUU.
I know youve probably heard this so many times but i cannot stress how important it is that you let it finish.
and then install a ROM and you should be fine
poison, i've reflashed the RUU three times already. the initial time, where it hung at the white htc screen after 10 min, i battery pulled, rebooted, and let it finished...
then the second time where it didn't hang, and a third time where it didn't hang, and it went through everything twice.
nope you're stuck here for now... but have you tried doing a full wipe and starting from scratch? I know plenty of people are using the latest leak firmware without any significant issues.
yeah man, i wipe it all..data,cache,dalvik,system,boot etc
my buddy did the leaked firmware and gets like 7 hour battery life too, when both of us got 17 hours pre-leak firmware. so it's not just me
Go back to the Inc for now I'm honestly thinking of it lately, feeling a bit nostalgic of Sense 2.1.
i used my inc with stock sense 1.5 from the froyo upgrade..it was so fast and apps opened instantly. damn good phone!
Or run a gb Rom....all you need to do is flash the sd card fix after installing the Rom and you are good to go. I was having some heat issues before on ics and my phone acted funny , went back to gb and my phone is back to being perfect.
Sent from my ADR6425LVW using XDA
hmm really? so maybe it's a combo of the new firmware and ics? if gb runs fine, that is
Sent from my ADR6425LVW using XDA App
jayochs said:
hmm really? so maybe it's a combo of the new firmware and ics? if gb runs fine, that is
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Just out of curiosity, what kernel are you using?
whichever kernel the devs make us flash. joel's, nils', etc
jayochs said:
whichever kernel the devs make us flash. joel's, nils', etc
Click to expand...
Click to collapse
Give SebastianFM's kernel a shot. Its been working amazing for me. Most of the weird issues I had were gone after wiping caches and flashing that kernel. I kinda made my own Senseless ROM out of the first couple ICS leaks - its still mostly based off the first 4.0.1 leak, but its playing very nicely with Sebastians kernel.
I find that the kernel generally has much more influence on things like charging, heat, performance, battery life, etc., than the ROM does.
hmm...is there a way to go back to the stock kernel incase it F's things up? cuz i know nils' rom,w hich i'm running now, boots you back to bootloader to install it..
maybe i'll give it a shot. does it help with the constant 1.5 ghz processing speed with screen on?
and are you on new firmware?
jayochs said:
hmm...is there a way to go back to the stock kernel incase it F's things up? cuz i know nils' rom,w hich i'm running now, boots you back to bootloader to install it..
maybe i'll give it a shot. does it help with the constant 1.5 ghz processing speed with screen on?
and are you on new firmware?
Click to expand...
Click to collapse
yeah, if you're using Nils ROM, it has the boot.img inside the PH98IMG.zip file. So you can open the zip, find PH98IMG.zip, and extract boot.img from it. That is your backup of the kernel that comes with Nils' ROM. You can re-flash this from fastboot if you need it later.
Then, using your file manager, go to /system/lib/modules and make a backup of the .ko files in there, as these are specific to the current kernel. If you do end up rolling back to the stock kernel, you'll need to also go back and restore these modules to get wifi working again with the original kernel.
After you've backed up your modules (just save them to a folder on your SD card or something) just flash Sebastians kernel from recovery. It will then reboot to bootloader and flash the kernel, just like you're used to with your ROM install.
Oh, and yes Sebastians kernel does scale correctly. I use setCPU profiles to set the frequencies I want, and while the min/max frequencies do still jump around all over the place in between the range I've specified, watching the current frequency shows that it does scale in between min and max correctly.
**edit
Also, I'm on hboot/firmware 2.11 from the last OTA. I have not installed the leaked firmware.
thanks man! i'd thank ya but i already used my 8 today lol...so i'm on new leak firmware, would that still work with this kernel then?
jayochs said:
thanks man! i'd thank ya but i already used my 8 today lol...so i'm on new leak firmware, would that still work with this kernel then?
Click to expand...
Click to collapse
I have no way to say so for certain since I haven't flashed that firmware - but this kernel works the best of all the rest so far on my phone. The kernel is based off the kernel FROM the leak though, so my guess is you should have no issues at all.
sweet! thanks, i'll give it a shot soon!
jayochs said:
sweet! thanks, i'll give it a shot soon!
Click to expand...
Click to collapse
The Problems you've been having sound a lot like the ones I have too. Sebastian's kernel made my phone run real hot. I would stick with either the stock ICS kernel or wipe and flash a GingerBread ROM. I flashed Ineffabilis 1.4 the other day and ran it for a couple days. My phone never hit over 90F. On most of the ICS ROMS my phone would jump over 100F most times
Before you reply - let me lay a story for ya!
I bought a bran new TBolt off of my friend. I was using a fascinate up to that point and never had any issues. I loved my fassy - it was fast, reliable, and everything worked well.
Now onto the TBolt - I got the SOFF, rooted, got recovery, and got a few Roms. It is still working fine. What's the issue?
Well, I posted this on this forum and other forums more than once, but I can never seem to get an answer. After a few ROMS - Infected, Vicious, ThunderShed - I get a splash screen, or if it does boot it freezes as soon as it accesses the radio components. I have CM7.1 on it right now, ran liquid, vicious miui and other roms. Most roms do work in fact without any problems - but the few that I heard are amazing - do not.
What I have done:
Made sure my recovery is upgraded: I have tried latest CWM, EXT, CWM Touch, and the other one that was popular - all updated and did not work.
Always make sure to wipe: I always format all partitions. I have even used the Superwipe script as well, but to no avail.
I have installed a stock rom, wiped and then installed: Someone said that would work - it did not.
Double, no - triple checked my roms': Checked the MD5 sum of all ROMS and Recoveries.
Different Radios: My phone came with newest radios, and I downgraded, upgraded, and nothing.
Now, I do not mean to sound picky - but I am not happy with the TBolt at all. It works at half the quality that I had from my fassy. Wifi errors out sometime, Tether errors out sometime, it lags some of the time, and most of all - no ICS. Liquid worked well, but the touchscreen wouldn't respond during some games - not that I use it for gaming much anymore - but the idea remains.
It sounds like you are trying all of the right things, so unfortunately I don't really have anything helpful to offer. Just curious though, If you were happier with the fascinate, why stop using it? Did it break?
As far as your issues, I have found CM 7 based ROMs (or any roms not based off of sense builds) to be less reliable and have more "glitches" than sense roms. That certainly could explain some of your gripes with the TB. Have you been able to install any Sense roms other than stock?
I have long since settled on Chingy's gingeritis rom as the most reliable and feature filled, but obviously that opinion differs depending on who you talk to.
To answer your question first: I started using the TBolt because it was 4G and that was important for me at the time (I was a student and had no reliable internet). Things have changed now and I am most likely going to change back sooner than later.
I haven't tried many Sense roms. Which would be the most reliable and recommended?
I know you said you tried downgrading your radios and that your phone came with the newest ones flashed but if you haven't already done so, check this out.
http://forum.xda-developers.com/showthread.php?t=1048128
and here is the radio I've been using with no problems:
gu1dry said:
From the 2.11.605.3 RUU:
CDMA: 1.48.00.0906
md5: c6a5a9eee78e0f33267fa80ced3c49b8
LTE: 0.01.78.0906
md5: 6f33809cf2253c38a3c6bb970f030eee
Click to expand...
Click to collapse
One thing with switching to a AOSP rom from a sense based rom is that you have to use very specific radios. this page will help you find the exact radios you need to use for the rom you are running.
I am running Thundershed 1.6 with these:
http://forum.xda-developers.com/showthread.php?t=1605557
newest leaked radios and they work fine for me.
I use...
I use these with no problems.
Rom: http://forum.xda-developers.com/showthread.php?t=1409703
I use the 605.19 Radios.. http://forum.xda-developers.com/showthread.php?t=1605557
Flashed this kernel.. http://rootzwiki.com/topic/603-kern...minimalistic-kernel-620-6312-camcorder-fixed/
Click the "v6.2.0dev13 - Fixed camcorder again." link at the bottom.
I am running the kernel in "normal" mode.
No issues that I know of but I am still a noob with a post count of 2...
Alright. Thx for the help guys - for the time being I am back to the fascinate, but I will try your suggestions.
One thing I am also trying is the using the "non-semsung" micro sd card in the TBOLT.
I will report back after this weekend with the results.
I want to give my wife's rezound more options that she is looking for out of her phone. Mainly wifi hot spotting. I installed RLS 4.0 two days ago and everything worked great except for her wifi would not turn on. Though maybe it was the kernel I used. So last night flashed the RLS 5.0 and the recomended "S-on" stock boot.img afterwards. Still the same thing. Everything seems to work great except for her wifi trys to work but will not. I've toggled the settings, turn on and off airplane mode many times etc etc. still nothing will get her wifi to run. I clean system, dalvic, cache etc each time as well. Is there something I am missing? I seen in the developers forum that a few others are having the same issue but not many. Any way to get this to work? Or is there another ROM to try? She really likes the latest sense in this ROM.
Try flashing the kernel using adb from your computer. Either that or flash a different kernel like dsb's kernel then flash the one xxx kernel over it
Sent from my ADR6425LVW using xda app-developers app
Just what the title states, I have just switched over from HTC sense based Operation Jelly Bean 3.15.651.16 to Official BlakCM. My EVo 4gLTE is s-off and rooted with latest TWRP 2.5 for recovery. I followed defection as how to install this particular ROM. What I am not sure on is the kernel. Do I need to install a custom kernel to run this Rom properly and which one if that is the case. I also have the latest base band 1.12.11.1210 installed without TP firmware upgrade. Thanks
You don't need to run custom kernel to run cm10 roms. You can if you want to and komodo is the only one I know of
Sent from my EVO using xda app-developers app
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
LemonNinja said:
It's not necessary to flash a custom kernel (in this case Komodo), but it does make the ROM even better: battery life almost doubles (on the stock ROM I'm usually at about 18% by 10:00 while with Komodo at that time I'm still at 45% or so), it also helps boost the audio volume and you can use swipe functions on the capacitative keys to turn on the screen (swipe from the left to right), turn off (inverse of the turn on function), increase and decrease volume (swiping halfway) and other functions.
Oh forgot to mention: flash the ViperBoy voltage fix. When I first used to flash it I'd get all sorts of random reboots and such, but since I flashed it it's so much smoother and doesn't reboot randomly
Click to expand...
Click to collapse
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
cpt.kraker said:
To flash the custom kernel do I drop it on sd/root like a firmware upgrade or flash using recovery/zip method, also for the voltage fix.
Click to expand...
Click to collapse
Both have to be flashed in recovery, only if you are s-off... But thicklizard has s-on kernel installers...
Sent from my EVO
Komodo a no go.
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
cpt.kraker said:
Thanks for all the help. Currently i am running carbon ROM (I like it so far) I tried installing komodo kernel but I always get boot loop. I tried to instal rom first let it load. Reboot into recovery and install komodo, i get a boot loop tried reversing the process and same thing. I am s-off lazy panda. Hboot 1.12.1111 radio 1.12.11.1210 I dont know if i am doing somethin wrong some pointers needed. Thanks.
Click to expand...
Click to collapse
Might want to hit Thick up and see if he can get you pointed in the right direction.
Sent from my EVO using xda premium
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
talroot said:
Which version of Komodo? I was reading the carbon thread a while back and remember Jamie saying a certain version for Carbon. Unfortunately I can't remember which version he said...probably have to search the thread again. I'm hopping back and forth between sense and aosps right now so I'm interested in trying this rom again with a different kernel as well.
Click to expand...
Click to collapse
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Ah, I want to say rls29 was recommended somewhere back on that thread. I haven't tried any of them yet though.
cpt.kraker said:
I was trying to instal the latest version of komodo rls31 capped at 1.7 both sweep gestures and standard versions and no luck. I was reading that tread and others have had same problems with boot loop after installs. Thread also mentioned that others had success installing rls31 capped at 1.998 with no gestures and rls31 capped at 1.5 with no gestures. I have not tried installing these versions yet.
Click to expand...
Click to collapse
You might need to run the kernel stabilizer in thick's dev host forum... I got the same result as you until I flashed th stabilizer...
Sent from my EVO