I was using a March 3 stable release of CM10.1 for the Verizon Galaxy S3 and the cyanogenmod kernel, everything was working fine. I was using leankernel on a different build of CM, so I got an updated version of leankernel and made sure it was compatible with my version of CM. I flashed the kernel in CWM, made sure to clear the cache/dalvik and now boots, shows the Galaxy S3 logo for a split second, then the screen turns black and cannot do anything. Any help? I am pretty sure I was rooted considering I could give root access to applications, and it would appear under the superuser in the Settings.
What date is your current rom from? LK 5.5.5 should only boot on AOSP roms dated April 19th or newer.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
What date is your current rom from? LK 5.5.5 should only boot on AOSP roms dated April 19th or newer.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Current ROM is from March 3rd, I believe. I know it's from March. Is there a leankernel version that would work with a March 3rd release of CM?
Syflox said:
Current ROM is from March 3rd, I believe. I know it's from March. Is there a leankernel version that would work with a March 3rd release of CM?
Click to expand...
Click to collapse
I'm fairly certain AOSP roms from March 3rd are Linux 3.0 based. Which means you can only use AOSP LK 2.8 and LK 2.9. I don't run AOSP roms but I keep up with the AOSP kernel threads a good bit just for knowledge purposes.
I said this once but it needs repeating in a different manner. Imo isn't continuing work on Linux 3.0 kernels so you'll remain on that setup until you update your rom to one of the latest builds.
Sent from my SCH-I535 using xda app-developers app
I just flashed LK 2.8, booted up fine, thanks! Here's the leankernel builds for anyone who has the same problem as me http://imoseyon.host4droid.com/s3/aosp/#!/view=details/lang=en/sort=da
Related
OK I have been downloading and reflashing few ROMs and now I have forgotten which one I flashed in.
Here's what it reads on About the Phone.
Kernel Version: 3.0.38-Cyanogenmod-g2a514aa [email protected]#1
CM version: 10-20120802-SKANK-Crespo
I think it is either Jellybro or JellyBelly CMREX. I thought it's the latter, but not so sure anymore. Can anyone tell?
Check your build.prop, maybe something writes there.
Sent from SpeedMachine i9023
Build #: cm_crespo-userdebug 4.1.1 JRO03H eng.joey.20120802.150826 test-keys
Pretty cryptic. The Changelog lists some old CM 9 stuff!
OK I think I figured it out by downloading the two ROMs and matching the file size with the one in my sdcard. The CMREX Rom is way too big. Looks like I am running Jellybro.
Man I'm such a dork. Been hanging out at the wrong ROM thread asking questions on a different ROM.
In cm version it says SKANK which is is the euroskank version, jellybro
Sent from my Nexus S 4G using xda premium
AlphaEchoViktorSierra said:
In cm version it says SKANK which is is the euroskank version, jellybro
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Cmrex uses jellybro
This post was sent from a Nexus S running Cyanogen(mod)10
I see they made a stable build and then a new nightly the day after? Was this a mistake or what?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
kchen96 said:
I see they made a stable build and then a new nightly the day after? Was this a mistake or what?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
No, nightlies are automatically compiled whether there are new changes or not. The ones that are labeled RC2 or stable build are ones they feel that is good enough for release. Any new changes in nightlies can introduce new bugs so usually its test at your own risk but for the most part they should run fine.
Pretty much its like saying this build is stable, then they say oh lets change this to see if it helps with this but it ends up messing up so they revert back to the stable build. RC2 is more of a milestone and with the stable 9.0.0 build that one they announced was going to be the last build as they're going to be working on CM10/Jellybean. It will still get nightlies but most of the time additional changes will either be minor (that doesnt affect you) or critical (a bug that needs to be fixed). :good:
Is there any benefit for Verizon s3 owners to run cm9 over cm10 until an official jellybean rom is released, or have the leaked roms provided enough for code for the Verizon version of cm10 to no longer be a port from another carrier's rom?
I'm having maps flickering issues that are on the official cm10 bugs list, but I need something that works in the meantime.
Thanks!
Sent from my SCH-I535 using xda premium
tomster2300 said:
Is there any benefit for Verizon s3 owners to run cm9 over cm10 until an official jellybean rom is released, or have the leaked roms provided enough for code for the Verizon version of cm10 to no longer be a port from another carrier's rom?
I'm having maps flickering issues that are on the official cm10 bugs list, but I need something that works in the meantime.
Thanks!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Bumping the thread a bit. Nobody has any input? Also, if I'm phrasing something incorrectly please let me know. Thanks!
As far as I'm aware, there was no CM9 release for the Verizon SIII.
tomster2300 said:
Is there any benefit for Verizon s3 owners to run cm9 over cm10 until an official jellybean rom is released, or have the leaked roms provided enough for code for the Verizon version of cm10 to no longer be a port from another carrier's rom?
I'm having maps flickering issues that are on the official cm10 bugs list, but I need something that works in the meantime.
Thanks!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As previously stated there was no official CM 9 release for the Verizon Galaxy S3 because at the time when CM 9 was still current our phone still had a locked bootloader, however there was an unofficial CM 9 using kexec to circumvent the locked bootloader at the time (But that is very outdated now and shouldn't be used). I recommend you try the latest CM 10 nightly that fixed a lot of bugs since the CM 10 Stable release. If you really need something absolutely 100% stable I would recommend running the stock ICS Touchwiz ROM with root.
shimp208 said:
As previously stated there was no official CM 9 release for the Verizon Galaxy S3 because at the time when CM 9 was still current our phone still had a locked bootloader, however there was an unofficial CM 9 using kexec to circumvent the locked bootloader at the time (But that is very outdated now and shouldn't be used). I recommend you try the latest CM 10 nightly that fixed a lot of bugs since the CM 10 Stable release. If you really need something absolutely 100% stable I would recommend running the stock ICS Touchwiz ROM with root.
Click to expand...
Click to collapse
Sounds great. Thanks for the info!
CM-10 stable has been released on Nov 15. Why are there still nightly roms coming out these days? Shouldn't they work on cm-10.1 now?
Because there's always room for improvements, no software is perfect and somebody would stick to 4.1 instead of pushing his/her device too much with 4.2
Sent from my Nexus S using xda app-developers app
It could also be that these updates are leading into the 10.1 builds .... and also there is always something that needs getting fixed
HeavenObserver said:
CM-10 stable has been released on Nov 15. Why are there still nightly roms coming out these days? Shouldn't they work on cm-10.1 now?
Click to expand...
Click to collapse
Because stable != final. Misconception a lot of people seem to have.
Running a recent PACman ROM nightly (22.0.1) but the battery life is pretty bad. Absolutely love everything else so I was hoping a different kernel might help out a bit in the battery department. Tried flashing the latest Lean Kernel but when I tried to boot I got a pink "SAMSUNG GALAXY SIII" screen and it just hung there. I've got a backup so no worries on that front. Any ideas on what I may be doing wrong?
What is the file name of the Leankernel zip that you flashed? Sounds like you flashed the TW version.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
What is the file name of the Leankernel zip that you flashed? Sounds like you flashed the TW version.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think that's it:
lk_s3vzw_tw_jb-v2.2.zip
Tried flashing Zeus kernel too but I had the same issue minus the pink. I feel like I'm missing something really obvious. I'm new to all this stuff. What does the tw designation mean, exactly?
Figured out the TW thing. I'm guessing if they aren't in the dev forms then there are no AOSP versions available then? Hope they pop up soon.
TW = Touchwiz, which is the software that Samsung had on the phone before you flashed this custom rom. You're looking for the AOSP version of Leankernel, well any kernel you intend to flash, for PacMan. Go to the Verizon GSIII section of Rootzwiki and click on the AOSP Leankernel thread. Download any of the 5.0 versions of AOSP Leankernel.
Oh, and Imoseyon is not making an xda thread. So that isn't happening lol
Sent from my SCH-I535 using xda app-developers app
Awesome just got the latest LeanKernel build. already flashed Ktoonsez so i'll see how that works out for a few days then switch over and give Lean a try. Thanks for the info.