Related
This is a strange problem that I only started to have once I installed Team Nekkid 7.2 RC dated 3/29.
I can flash the ROM no problem, wipe dalvik and fix permissions and I'm good to go without any issues. But if I flash the ROM, then either morfic or faux kernel, then gapps, when I go to wipe dalvik, all I get is a quick screen flash with no option to actually wipe dalvik.
I go back and wipe the overall cache completely, fix permissions, the reboot. I am now stuck at the morfic boot animation until i pull battery.
If i try to install a Faux kernel, same thing happens with dalvik, but gets stuck at the blue LG screen.
Once i battery pull and get back to CWM, i wipe everything, reflash ROM and gapps, wipe dalvik and fix permissions no problem and boot up into whatever ROM i choose.
EDIT: Went back and flashed Bionix 1.4.1 and was able to flash a Faux kernel and wipe dalvik. Booting up this ROM now.
I also have NO problem with ICS ROMS/kernels.
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did all of that. I flashed the kernel before and after gapps but end up with the same result.
I have a feeling there is an issue with the CWM since I am constantly flashing roms/kernels and have never had these problems before. I'm at work so I cant use the Nvidia tool to flash CWM so I have to wait until I get home.
mariuscm said:
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Click to expand...
Click to collapse
I meant I have no problem flashing ICS roms and kernels.
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
[UPDATE] Ok I got it now. Just read your last message
mariuscm said:
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
Click to expand...
Click to collapse
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
stevew84 said:
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
Click to expand...
Click to collapse
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
mariuscm said:
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
Click to expand...
Click to collapse
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
stevew84 said:
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
Click to expand...
Click to collapse
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
mariuscm said:
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
Click to expand...
Click to collapse
If the maps shows up and then goes blank, simply close the map and re-open it.
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
All the important information will be in the first post of his thread. he doesn't include a change log, though.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
Yes, it's 4.0.4 with all of the latest CM9 commits.
Sent from my LG-P999 using xda premium
This Rom is a pure AOSP build.
Built off 100% unaltered AOSP source. Stock kernel and everything. For those purist's amongst us.
New links added since you guys killed my db links lol. Give the db links 3 days and they should be working again.
Download
http://db.tt/ciISJwOJ or
https://docs.google.com/file/d/0Bz2CXfDCvI5XbGxRbC04NVRRWkU/edit
Installation:
1) WIPE
2) Flash via your prefered recovery
3) Flash JB GAPPS http://db.tt/UH68DdvP or https://docs.google.com/file/d/0Bz2CXfDCvI5XazNOMTE3dWpidEU/edit
4) (optional) root by flashing JB-SuperSU.zip http://db.tt/fqxlYoP5 or
https://docs.google.com/file/d/0Bz2CXfDCvI5XZW9DdTBGMC1hT0U/edit
ouch so it isnt rooted, gotta flash the SU.zip for root, will we loose custom recovery or not?
nicknowsky said:
ouch so it isnt rooted, gotta flash the SU.zip for root, will we loose custom recovery or not?
Click to expand...
Click to collapse
Nope did not loose my custom recovery. Its very clean and appears to be stable.
P.S. I flashed all 3 with TWRP in order
1) ROM
2) GAPPS
3) SU
After a full wipe of course...
My Nexus 7 isn't here yet, but this is incredible. I'm coming from a Droid Charge and HTC Rezound-- I won't even know what to do, its almost confusing to have choice.
You beat me to the punch I just compiled 4.1.1 r3 late yesterday. Thank you from a fellow purist.
Sent from my Galaxy Nexus
Great job man,downloading now .
I'm confused, how is this any different from the official 4.1.1 OTA update? What does Google add or change from source other than the Google Apps?
Kitten Mittens said:
I'm confused, how is this any different from the official 4.1.1 OTA update? What does Google add or change from source other than the Google Apps?
Click to expand...
Click to collapse
AOSP roms if they are the latest build include the newest fixes and updates straight from Google. Also true AOSP roms do not include gapps. Gapps are not open source like Android. That's why they are flashed separately
Sent from my Galaxy Nexus
rsxtypes72 said:
You beat me to the punch I just compiled 4.1.1 r3 late yesterday. Thank you from a fellow purist.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
well drop it like its hot, can never have enough ROMs especially good stock releases
---------- Post added at 11:09 AM ---------- Previous post was at 10:49 AM ----------
Kitten Mittens said:
I'm confused, how is this any different from the official 4.1.1 OTA update? What does Google add or change from source other than the Google Apps?
Click to expand...
Click to collapse
there is also no Nexus boot animations just the old fashioned ANDROID bootscreen
You will not lose your custom recovery, as i removed the stock recovery from this rom. Glad you guys like it.
rsxtypes72 said:
AOSP roms if they are the latest build include the newest fixes and updates straight from Google. Also true AOSP roms do not include gapps. Gapps are not open source like Android. That's why they are flashed separately
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Plus the stock aosp lockscreen includes unlock to camera option....
Asus/google didnt even give us an option to get to the camera except via certain apps...
Xi2wiked said:
Plus the stock aosp lockscreen includes unlock to camera option....
Asus/google didnt even give us an option to get to the camera except via certain apps...
Click to expand...
Click to collapse
That's weird. I thought nexus 7 was supposed to be stock AOSP Jellybean.
Lucky people with the device. I'm still waiting on mine to ship. 16gb version.
how is this rom running? really smooth and fast? im planning to flash this tomorrow..sounds very appealing to me. pure aosp should mean fast.
Running great for me.
great rom...really smooth and fast.
is it possible to lower the nav bar like how it is in jr5? i think it looks better that way lol.
jarjar124 said:
great rom...really smooth and fast.
is it possible to lower the nav bar like how it is in jr5? i think it looks better that way lol.
Click to expand...
Click to collapse
This is a pure AOSP Rom, and I'm gonna keep it as such unfortunately. However if you wanna rip this Rom apart and edit the nav bar to whatever specs you desire go right ahead, that's why I uploaded this so we can have a stock base Rom to do with as we please.
So given that this aosp does the op know what main differences are between it and the jb that comes with the n7?
Sent from my GT-N7000 using Tapatalk 2
nandihno said:
So given that this aosp does the op know what main differences are between it and the jb that comes with the n7?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Since I have been running it on my n7, I sure hope so....
no man. It same JB but with NO CRAP !!
Faster as hell :highfive:
Well, I didn't try to download the rom, since I can build this just fine at home (and do).
But I did try and grab your gapps, since I was having a hard time finding a gapps package that mirrored my original factory gapps.
But I figured I would let you know your dropbox has been suspended for large activity. Maybe you know, but since it isn't in the OP...
Edit: And if you are selecting option 4 in lunch (userdebug) then root access is included. Are you building 'user'?
Edit2: Looked at the fixed link. eng has root too. So they're gonna be rooted, whether the flash the su or not. Although most builds just go for the userdebug. eng just adds more logging services, FAIK.
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
bananagranola said:
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
Click to expand...
Click to collapse
Sure wish i could get some help with this too.
Have you guys tried the latest releases? When full wiping include format all partitions except sd card.
Sent from a dream.
What latest releases are you referring to? Could you please be more specific?
EDIT: I did a full wipe and reformat of everything, including system, data, and cache.
Right now they are on beta 10. Funny thing, I don't recall anyone mentioning a need to do a adsp firmware update. I don't even know what it is.
Sent from a dream.
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Sent from my Desire HD using xda app-developers app
jlochamy said:
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Click to expand...
Click to collapse
Are you referring to this one?
bananagranola said:
Are you referring to this one?
Click to expand...
Click to collapse
That is the one. But if you don't do a full wipe before you do beta 10 it will have errors. It would still boot but have lots of errors.
Sent from my Desire HD using xda app-developers app
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
bananagranola said:
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
Click to expand...
Click to collapse
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
uss..p8triot said:
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
Nope. You only need to flash the stock once; after that, flash back and forth to your heart's content.
uss..p8triot said:
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
fatboyRICH said:
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
Click to expand...
Click to collapse
usspatriot is actually referring to a separate question. Some of us need to update our firmware to run JB, which can only be done by flashing the latest stock before flashing JB. He wanted to know if the updated firmware would be overwritten by flashing ICS, requiring a reflash of stock before reflashing JB. The ICS and JB kernels are not at issue.
I wonder if this has anything to do with my issue with JB on a Desire HD:
I came from SmartDroid_Reloaded_wwe_1.5.2, did a full wipe, installed, everything works fine for me except for cellular data.
I'm wondering if it's something to do with JB not liking my phone? I've also tried a couple of ICS roms.. See below:
SmartDroid_Reloaded_wwe_1.5.2 = cell data works
Sabsa_Prime_v5.0 = cell data works
TrickDroid_v1.1.1 = cell data works
cm-cfX-20120925-OFFICIAL-ace = no cell data
cm-JellyTime_R10 = no cell data
cm-JellyTime_R10.1 = no cell data
cm-JellyTime_R11 = no cell data
i set my APN's to suit my network (crazy johns in australia) but nothing works..
If i connect to wifi, both the wifi signal and cell signal turn blue, if i disconnect from wifi, both turn grey.
MMS, SMS, Phone calls work fine..
Click to expand...
Click to collapse
Hello all,
I made this over at the GNex forums for a stock GNex 4.2/4.2.1 kernel... here it is for the Nexus 7 for those that accidentally flashed a 4.1.2 kernel or just want to get back to stock.
Flash at your own risk, should work just fine though!
UPDATED: Kernel should work now! Sorry about the bad zip before!
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
where were you couple of days ago when I was dealing with the issue - trying to flash stock kernel.....wish you posted this before.
I will save this just in case :silly:
thanks!!!
I flashed LeanKernel and then wanted to go back to stock kernel before flashing latest Faux Kernel.
So I have just flashed your kernel but "about tablet" is telling me I still have LeanKernel installed?
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Caliyork said:
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
I urge you to take this down and make sure you know you've got it right before you put it up again. Only saving grace here is you were using the platform by-name method (which just plain won't work on the N7) instead of the actual mmc block names or you could have really messed up some peoples' devices.
osm0sis said:
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
Click to expand...
Click to collapse
My mistake. I thought it would just transfer over. I will fix the link... Didn't realize when I tested it I already had the stock kernel on there. Gimme a minute to fix it!
OK should be fixed and good to go! Again, my apologies!
Sent from my Galaxy Nexus using Tapatalk 2
stonebear said:
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
Click to expand...
Click to collapse
Please try again... I have updated my zip and tested it by flashing a 4.1.2 kernel, having the device sit at the X for a few minutes without doing anything (to test a non-working kernel) then flashing my zip, and my N7 is back up and running again.
I am still learning about kernel stuff... sorry about any confusion!
SkaldfraNorden said:
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Negative. This is the stock 4.2 kernel... I found the stock 4.1.2 kernel on XDA... Should be easy to find!
Sent from my Galaxy Nexus using Tapatalk 2
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
evaradar said:
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
wasn't that hard to find out, but here you go: stock kernel
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
I've added this kernel to the Nexus 7 Complete Index
Sent from my Nexus 7 using xda premium
..
BTW..Excellent system stability with this kernel and rasbeanjelly ROM. Tested on my daughter.
cydef said:
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
Click to expand...
Click to collapse
+1
Sent from my Nexus 7 using xda app-developers app
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
annoyingduck said:
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
Click to expand...
Click to collapse
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
khaytsus said:
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
Click to expand...
Click to collapse
As it turns out, I built a "slightly rooted" JOP40D stock flash kit yesterday (mods to build.prop in boot.img, and su/SuperSU in system.img). I'm posting this reply from that.
I started with the Google JOP40D (grouper) distro to do that. I thought I was going to need to unpack the boot.img from the OP's .zip to do comparisons of the kernels (to answer your question) ... but it turns out that his boot.img has the same MD5 sig as the boot.img from Google's JOP40D... and the OP's updater-script merely flashes boot.img to the /boot partition.
That means one of two things: either the two successive Google releases (for grouper) had identical boot images (which implies identical kernels), or there is some mistake by the OP. (I don't have the 40C distro to check ... only picked up my N7 a few days ago.)
It should work in your specific case though, as you are on JOP40D.
In any event, flashing boot.img is way way more than just a kernel replacement. I haven't looked at it for a while, but I would suppose that Koush's kernel flasher is a much more appropriate technique for switching ONLY the kernel out from underneath an arbitrary ROM.
cheers
That's great info there. I'm searching for the simplicity of just flashing a kernel instead of pushing the entire boot image. Thanks for a step in clarifying this question
Sent from my Nexus 7 using xda premium
I was looking at:
http://forum.xda-developers.com/showthread.php?t=2063058
I'm not sure which to flash as I don't know the difference. One is based off of LK3 and I don't know what that is. The other 2 I do know, CM 10 or 10.1. Could anyone explain or suggest which is good to try? I am currently only rooted and not using any ROMs.
Please inform yourself! The kernel is the communicator between the hardware and software. It is imperative you flash a kernel designed for your device/rom!
If you're on Stock, you'll want one labeled TW (or TouchWiz). Make sure you download the JB (Jelly Bean) version. LK3 is the radio baseband of the phone. You can check in Settings > About Phone then last 3 digits of Baseband Number.
Based on the information you've said, I'd recommend looking into LeanKernel or 747. Hope I've helped. All the info you need is on this site, just gotta read it. GL
Sent via SGS3 using Tapatalk
And backup your imei if you haven't
Sent from my SCH-I535 using xda app-developers app
sweeds said:
Please inform yourself! The kernel is the communicator between the hardware and software. It is imperative you flash a kernel designed for your device/rom!
If you're on Stock, you'll want one labeled TW (or TouchWiz). Make sure you download the JB (Jelly Bean) version. LK3 is the radio baseband of the phone. You can check in Settings > About Phone then last 3 digits of Baseband Number.
Based on the information you've said, I'd recommend looking into LeanKernel or 747. Hope I've helped. All the info you need is on this site, just gotta read it. GL
Sent via SGS3 using Tapatalk
Click to expand...
Click to collapse
Thanks and informing myself is exactly what I'm doing! I don't want to screw anything up. Currently, I only plan on flashing a kernel which is why I wanted a backup of the stock kernel that comes with the phone just in case anything stupid happens. I'll check out leankernel and 747. Thanks!
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
spurnout said:
I was looking at:
http://forum.xda-developers.com/showthread.php?t=2063058
I'm not sure which to flash as I don't know the difference. One is based off of LK3 and I don't know what that is. The other 2 I do know, CM 10 or 10.1. Could anyone explain or suggest which is good to try? I am currently only rooted and not using any ROMs.
Click to expand...
Click to collapse
You got the first step right, and that's asking questions if you don't understand.
sweeds said:
... LK3 is the radio baseband of the phone. ...
Click to expand...
Click to collapse
Not entirely. When talking about official (or leaked) Service provider (and phone) specific builds of Android, they're each given a build number.
The latest "build" of Jelly Bean 4.1.1 from Verizon for the SGS3 has a build identifier of VRBLK3. That covers everything from the stock kernel, to the stock ROM, to the version of the radio for that particular build (you can apply any radio to any other build without an issue, though).
Since the LK3 build is the latest official from Verizon, that's the base (not baseband - 2 different things) that most of the custom verizon roms are built off of. (latest = greatest, at least sometimes ).
As sweeds points out, there are two main "strains" of Android (for us samsung guys). The first is based off of Samsung's take on Android with their tweaks, features, etc and that's called TouchWiz (TW).
The other is Android built straight from Google, without any of the Samsung proprietary stuff. It's called AOSP (Android Open Source Project). ROMs like CM, ParanoidAndroid, AOKP, are based on AOSP code.
You cannot mix and match AOSP and TW kernels and ROMs, which is why you'll have the choice of downloads that your initial question addressed. Most developers will release a version of what they code for each version of Android. Things will go bork if you flash a TW kernel on an AOSP ROM and vice versa.
sweeds said:
Based on the information you've said, I'd recommend looking into LeanKernel or 747. Hope I've helped. All the info you need is on this site, just gotta read it. GL
Sent via SGS3 using Tapatalk
Click to expand...
Click to collapse
I wouldn't knock KOR - I've been having good luck with it (TW) on both GalaxyMOD and Synergy....
bobAbooE said:
And backup your imei if you haven't
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1 Do this. (see here for how: http://forum.xda-developers.com/showthread.php?t=1852255 )
letinsh said:
You got the first step right, and that's asking questions if you don't understand.
Not entirely. When talking about official (or leaked) Service provider (and phone) specific builds of Android, they're each given a build number.
The latest "build" of Jelly Bean 4.1.1 from Verizon for the SGS3 has a build identifier of VRBLK3. That covers everything from the stock kernel, to the stock ROM, to the version of the radio for that particular build (you can apply any radio to any other build without an issue, though).
Since the LK3 build is the latest official from Verizon, that's the base (not baseband - 2 different things) that most of the custom verizon roms are built off of. (latest = greatest, at least sometimes ).
As sweeds points out, there are two main "strains" of Android (for us samsung guys). The first is based off of Samsung's take on Android with their tweaks, features, etc and that's called TouchWiz (TW).
The other is Android built straight from Google, without any of the Samsung proprietary stuff. It's called AOSP (Android Open Source Project). ROMs like CM, ParanoidAndroid, AOKP, are based on AOSP code.
You cannot mix and match AOSP and TW kernels and ROMs, which is why you'll have the choice of downloads that your initial question addressed. Most developers will release a version of what they code for each version of Android. Things will go bork if you flash a TW kernel on an AOSP ROM and vice versa.
I wouldn't knock KOR - I've been having good luck with it (TW) on both GalaxyMOD and Synergy....
+1 Do this. (see here for how: http://forum.xda-developers.com/showthread.php?t=1852255 )
Click to expand...
Click to collapse
Somehow I missed this response so I just read it and wanted to say thanks for the very detailed explanation! I finally ROM'd this phone yesterday and I have Hyperdrive RLS7 running with Galaxy KOR kernel. I haven't had any issues at all yet and the battery life definitely seems better even with the OC'd processor. I also started using SPB Shell 3D since this phone seems powerful enough to run it completely smoothly versus some old phones I had where I had some reservations about that.