Database Info

[Q] Flashing Other Carriers Kernels?

So someone please explain to me how This Is possible. I was under the belief in my understanding of android that this is a BIG NO NO. I do realize and I may not fully understand the similarities and differences between the different versions of the SGS3 but I would think that because of the Radio being different among all of the carriers that Kernels would be totally different as well. I will reference the Fascinate and the Mesmerize for example. Pretty much the same phone but completely different as far as anything and everything development wise. So what it boils down is this
1. Can we flash kernels designed for the At&t, Sprint, or T-Mobile versions of our phone.
2.What versions of the SGS3 can we SAFELY flash Kernels from.
3.How is this possible given the differences in the different phones.(Question for my sake cause I am really curious and hope i can get a good explanation regarding this)

Aali1011 said:
So someone please explain to me how This Is possible. I was under the belief in my understanding of android that this is a BIG NO NO. I do realize and I may not fully understand the similarities and differences between the different versions of the SGS3 but I would think that because of the Radio being different among all of the carriers that Kernels would be totally different as well. I will reference the Fascinate and the Mesmerize for example. Pretty much the same phone but completely different as far as anything and everything development wise. So what it boils down is this
1. Can we flash kernels designed for the At&t, Sprint, or T-Mobile versions of our phone.
2.What versions of the SGS3 can we SAFELY flash Kernels from.
3.How is this possible given the differences in the different phones.(Question for my sake cause I am really curious and hope i can get a good explanation regarding this)
Click to expand...
Click to collapse
There have been some successful instances of sprint kernels being flashed that I've seen, but it is never a great idea to flash kernels not specifically designed for your phone. btw. there are some pretty good kernels available for vzw now

It's a pretty bad idea. There is a very small chance it could work but more than likely it won't boot

arrogantS3 said:
There have been some successful instances of sprint kernels being flashed that I've seen, but it is never a great idea to flash kernels not specifically designed for your phone. btw. there are some pretty good kernels available for vzw now
Click to expand...
Click to collapse
And i figured as much. I am just REALLY surprised it worked and I just kinda wanna know why it worked. The technical reasons to be honest. But to play it safe i will just stick with those kernels that have been made for the Verizon version thus far. I am still hesitant using the Sprint Kernel even knowing it works.

Neverendingxsin said:
It's a pretty bad idea. There is a very small chance it could work but more than likely it won't boot
Click to expand...
Click to collapse
And based of of you saying this and me knowing this is why i ask lol. Cause like arrogant says there have been successful flashes of the Sprint Kernel. Again idk everything there is about Android but i wonder if it possible due to the fact our unlocked bootloader is partially sprint or something along those lines. That is why i was hoping someone would see this and chime in with a technical explanation and then either a go for it, no, or tread with caution. When the phone was being released there was talks of a rom kitchen being established between the carriers and i was hoping that this was a part of that. Meaning that someone who Devs for the AT&T version of the SGS3 can have their rom or kernel ported to Sprint version and then the Verizon and T-Mobile variants. Idk if the kitchen is still a possibility or in the works but it would be cool to see it kernel wise considering most are running AOSP based roms.

I tried to flash att one two days ago, can not turn wifi on....
So, not recommended

Aali1011 said:
And based of of you saying this and me knowing this is why i ask lol. Cause like arrogant says there have been successful flashes of the Sprint Kernel. Again idk everything there is about Android but i wonder if it possible due to the fact our unlocked bootloader is partially sprint or something along those lines. That is why i was hoping someone would see this and chime in with a technical explanation and then either a go for it, no, or tread with caution. When the phone was being released there was talks of a rom kitchen being established between the carriers and i was hoping that this was a part of that. Meaning that someone who Devs for the AT&T version of the SGS3 can have their rom or kernel ported to Sprint version and then the Verizon and T-Mobile variants. Idk if the kitchen is still a possibility or in the works but it would be cool to see it kernel wise considering most are running AOSP based roms.
Click to expand...
Click to collapse
Some kernels could very well work, same as some stock themes for sprint will work with stock roms on verizon (jellybomb domination being one of them) the issue is that some things could be carried over that may not play nice with our phones and vice versa. While it may run perfectly fine, there's a greater risk that it could break something.
I have yet to run an AOSP rom because of the IMEI issues, so i can't really comment on that, but i know if i was going to flash another carriers kernel i would make sure to make a backup first.

Are there any other kernels??

Are there any other kernels other than ktoonz and faux???
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta

What device are we talking about? that would be what needs to be asked first.
Oh I see at the bottom of your post i337, there are 3-4 that we can use in the Dev section of this forum.

mannyboy23 said:
Are there any other kernels other than ktoonz and faux???
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
If those two kernels are not working for you, stay with stock. You could try some of the t-mo kernels if you have the auto loki recovery.
Sent from my SAMSUNG-SGH-I337 using xda premium

mannyboy23 said:
Are there any other kernels other than ktoonz and faux???
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
As long as it's loki'd (or if you run an auto-loki recovery, it doesn't matter), you can run any GS4 i9505-based kernel your heart desires. I'd stick with AT&T and T-mobile ones (since their internal hardware is 100% identical), but you can run i9505 ones as well. There may be issues, but you can go ahead and see how it works. Worst case, just flash another one.
Better question is: do the current kernels not do something you want/need a kernel to do?
And an even better question is: if you don't like the current crop of kernels, why not fork one, and compile a new one yourself!
I'd be careful, as threads like this have a way of stoking the flames around here. Not all people particularly appreciate it when someone starts a whole new thread for a question like yours. I'm being nice, but as someone with an account as old as yours, you shouldn't ask questions that come off as "why don't more Devs get going and spend their unpaid time and energy to create something new that I'll take advantage of for free?". Cause the inevitable answer to that is "do it yourself, or shut up".
If I were you, I'd politely ask a mod to close your thread, but it's up to you.

kind of strange that you want to flash anything other than ktoonz and faux. both kernels are awesome

http://forum.xda-developers.com/showthread.php?t=2309442

Reported. This thread is totally useless a simple search would've got your answer.....

[KERNEL] StarKissed Kangerade [EK-GC 100/110]

Currently supported are the Wifi only and AT&T versions. The layout for Verizon is in the source but needs a ramdisk to modify. There are downloads for the boot.img, tar, md5, and zip packages. Md5 may not work due to variations building on a Mac, but with the custom recovery this is not an issue.
To clean things up, all new builds will be tagged -VERSION to easily determine what applies.
This kernel is about customization. It is based on the work done for the Galaxy Nexus to bring as many available options as possible without causing bloat that could weigh down the system. This thread is not directed to the elite few, so there is no need to put on your fancy hat when you enter. Relax and enjoy your device.
StarKissed Galaxy Cam Kernels
StarKissed Galaxy Cam Source
Guide to Governors, Schedulers, Etc.

Current Changes:
Governors:
Enable all
LulzactiveQ [Default]
Schedulers:
Enable all
V(R)
SIOPlus [Default]
TCP Algorithms:
Enable all
Default Westwood

Had to sort out some issues with the Mac md5 being a bit off from md5sum, but the first kernel should be available shortly. It's building and uploading now.

The md5 still isn't matching Windows when written from the Mac, but the good news is that the kernel does work when removing the .md5 extension.
For safety, it is a big concern to ensure this gets fixed to prevent any bricked or otherwise malfunctioning devices. If you do wish to test the kernel by removing the .md5 extension, please note that you do so at your own risk and should take precautions.

Congrats on the first custom kernel for the GC.
I take it that it's just a flash via Odin job?
Sent from my GT-N5100 using Tapatalk 4 Beta

RavenY2K3 said:
Congrats on the first custom kernel for the GC.
I take it that it's just a flash via Odin job?
Sent from my GT-N5100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, but currently wifi doesn't work. I just figured out the module layout while updating linux versions so the changes need to be tested. I came from a nexus so this Odin stuff is all new.

Alright, the wifi is fixed. Finally built Heimdall for Mac 10.7 so I was able to test without having to have access to a Windows machine.
The TCP options are not being picked up by my app to select a new default, but the configured default does work and should improve speed.
Currently this kernel is based on the newest GC110 firmware. If other version are needed, such as Verizon, please post which ones and, if possible, the current boot.img or a link to the firmware. This is to allow retrieving the ramdisk to modify.

EK-GC100
Just wondering, how easy is this to add the 3G support for the EK-GC100 camera, since with what you wrote you have an EK-GC110.
I would like to play with this kernel, and if I had spare time, I would love to sort out how to build a custom ROM, without losing the camera features.

mouse_man said:
Just wondering, how easy is this to add the 3G support for the EK-GC100 camera, since with what you wrote you have an EK-GC110.
I would like to play with this kernel, and if I had spare time, I would love to sort out how to build a custom ROM, without losing the camera features.
Click to expand...
Click to collapse
A few lines in the ramdisk. Which carrier? With the recovery available, I should add the other two to the source anyway.

I added source for the gsm one but I haven't found an updated kernel for verizon to add that yet.

To make life easier on everyone, I made all kernels into a single aroma installer. No worries about tracking down which name matches which kernel for a model. One installer with selections.

twistedumbrella said:
A few lines in the ramdisk. Which carrier? With the recovery available, I should add the other two to the source anyway.
Click to expand...
Click to collapse
At the moment I don't have a sim in it, but I am in Aus on Telstra.

mouse_man said:
At the moment I don't have a sim in it, but I am in Aus on Telstra.
Click to expand...
Click to collapse
I would hope in terms of hardware, it is an exact clone of the AT&T version. They are both GSM carriers and the kernel shouldn't know the difference. I ran an Aus firmware on mine and it worked, but my current one is the UAE. I would say it should work fine.

For anyone wondering, the "Wireless Fix" option in the kernel package will clear out the necessary files to prevent the wifi from being corrupted during a kernel or system install. This is what I use to avoid having to do a full wipe when switching similar builds.

twistedumbrella said:
Currently supported are the Wifi only and AT&T versions. The layout for Verizon is in the source but needs a ramdisk to modify.
Click to expand...
Click to collapse
twistedumbrella said:
I added source for the gsm one but I haven't found an updated kernel for verizon to add that yet.
Click to expand...
Click to collapse
My Verizon GC120 should be here in a couple of days. As far as I know it is untouched stock. Let me know the commands to pull the files you need for this and the other dev work you are doing.
Thank you for taking the time to do the work! We all appreciate it!

Jiggity Janx said:
My Verizon GC120 should be here in a couple of days. As far as I know it is untouched stock. Let me know the commands to pull the files you need for this and the other dev work you are doing.
Thank you for taking the time to do the work! We all appreciate it!
Click to expand...
Click to collapse
I understand the excitement, but posting the same message on three threads with the same OP is a little bit frustrating. Luckily I have notifications disabled.

In my opinion its all in how you look at it. Excitement can be contagious and maybe posting in a couple of the threads may get some folks that only have notifications set on one of them more interested and/or involved.
see isnt that smile contagious...

Jiggity Janx said:
In my opinion its all in how you look at it. Excitement can be contagious and maybe posting in a couple of the threads may get some folks that only have notifications set on one of them more interested and/or involved.
see isnt that smile contagious...
Click to expand...
Click to collapse
Actually it's a violation of the rules and for most people whose phones vibrated 12 times instead of 4, motivation to unsubscribe. Either way I will have to look at what options there are to pull the stuff and if it can be rooted before I give any official advice. That may take a bit. I am right in the middle of my thesis for my degree.

twistedumbrella said:
Actually it's a violation of the rules and for most people whose phones vibrated 12 times instead of 4, motivation to unsubscribe. Either way I will have to look at what options there are to pull the stuff and if it can be rooted before I give any official advice. That may take a bit. I am right in the middle of my thesis for my degree.
Click to expand...
Click to collapse
I think we are looking at it from different perspectives. I saw 3 different OPs that requested (at least by appearance) differing information. If the information required is all the same or can all be pulled through one set of instructions then that is great. But there was no violating the rules by responding to the requests the way I did.
I am also trying to look for options to root and asking of those who have accomplished it prior. Trying to find other devices that used the mdm9615 and if those devices on verizon have locked bootloaders with their latest updates, etc. Just doing whatever research I can as I do with all my new devices.
I wish you the best of luck with your thesis. We all do thank you for taking what time you have away from that to help us out.

Jiggity Janx said:
I think we are looking at it from different perspectives. I saw 3 different OPs that requested (at least by appearance) differing information. If the information required is all the same or can all be pulled through one set of instructions then that is great. But there was no violating the rules by responding to the requests the way I did.
I am also trying to look for options to root and asking of those who have accomplished it prior. Trying to find other devices that used the mdm9615 and if those devices on verizon have locked bootloaders with their latest updates, etc. Just doing whatever research I can as I do with all my new devices.
I wish you the best of luck with your thesis. We all do thank you for taking what time you have away from that to help us out.
Click to expand...
Click to collapse
All I'm saying is three different request, three different threads, same OP, whatever. Copy and paste, Boo!

No Love For Sprint N5?

What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.

Circaflex said:
What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Click to expand...
Click to collapse
Give it some time....... Its the ONLY CDMA carrier this phone works on... so for most of the devs this is a completely new thing
Or try fixing it yourself, like restore your APN's from a ROM with data working.

Rxpert said:
Give it some time....... Its the ONLY CDMA carrier this phone works on... so for most of the devs this is a completely new thing
Or try fixing it yourself, like restore your APN's from a ROM with data working.
Click to expand...
Click to collapse
the thing is there is a fix, and its proven to work on Slimrom/Slimkat and the code has been put up for use by other devs, that's why im asking this question is it just the devs don't want to support sprint or is there something else

I agree completely. The fix has been posted for weeks now. Any dev releasing a rom without it at this point is being sloppy.

Circaflex said:
What gives? It seems many of the roms in OG or in AD do not work with Sprint, data at least, on the nexus 5. A fix has been found by Team Slim, yet I don't see the roms being updated to work on Sprint. I understand some devs choose not to fix it as they don't run sprint which is fine but why not try fixing it, giving you a larger user base? I bought the N5 because I wanted a true google experience, and figured I would get to try out some awesome roms that were not available for my previous devices, but its almost the same here. This is a legitimate question, and I hope I don't get the usual high horse answer, "why don't you fix it" "we do this for free" etc etc I love that the devs put in personal time, im just looking for answers as to why a fix wouldn't be implemented if it is tested good and working.
Click to expand...
Click to collapse
While I agree that ROM devs should be updating their code with the fix from Slim, one thing I can suggest is maybe just try using a stock rooted ROM with Xposed framework. I am also on Sprint, and while I used to love using SlimBean for my Galaxy S 3, I am also perfectly satisfied with stock Nexus 5 ROMs with Xposed framework and GravityBox. If you're not happy with it, then it's easy to just disable the module and run along. Just something to try out if you're craving more customizability.

metayoshi said:
While I agree that ROM devs should be updating their code with the fix from Slim, one thing I can suggest is maybe just try using a stock rooted ROM with Xposed framework. I am also on Sprint, and while I used to love using SlimBean for my Galaxy S 3, I am also perfectly satisfied with stock Nexus 5 ROMs with Xposed framework and GravityBox. If you're not happy with it, then it's easy to just disable the module and run along. Just something to try out if you're craving more customizability.
Click to expand...
Click to collapse
side note do we know each other? lol same city

Is it only aosp that don't work? Stock works I assume?
Have you tried posting the link to the commit in dev threads asking for it to be implemented? If you're not doing it, maybe no one else is either
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

Circaflex said:
side note do we know each other? lol same city
Click to expand...
Click to collapse
Lol. I doubt it, though it is a small city. I wouldn't be surprised if I passed by you a few times.

Compatible ROMs from AT&T forum?

I didn't see a thread for this (unless I'm blind, which is partially true). I saw a post somewhere linking to the Dirty Unicorn ROM in the ATT gs3 section and saw that they had loads of roms. I simply wondered how compatible some of these were with the vzwS3 before I just started flashing away... Or maybe there is a list somewhere I failed to see?

That reminds me...
On my samsung galaxy nexus I used to use a script called rom switcher (or something like that) that allowed you to flash lets say a sprint rom on a gsm phone or a verizon rom on sprint and so on. Without the need for porting.
However I'm not sure if something like this would be applicable to the s3 because of bootloader differences (nexus is unlocked ofc) and other possible hardware issues. Samsung uses unified architecture on gnexus (kernel level at least) across all three platforms. So I'm guessing the same applies to the s3 and if so that wouldn't be a problem in itself so I think the only real major issues would come from the bootloader.
If there are any devs or someone with more knowldge than i who want to see the script just let me know and I'll see if I can get a link to the thread it's in the galaxy nexus apps and themes section.
Anyway just an idea that may be helpful to at least those who are not locked down.
Sent from my SCH-I535 using Tapatalk 2

Thanks for the response! Luckily I'm not locked which is exactly why I was curious. My friend just got a Galaxy S4 i337 and I rooted/safestrapped it for him but in the process noticed lots of Verizon and Sprint roms floating around which got me curious. There's gotta be someone here with said experience right?

Perhaps you could enlist the aid of mohammed.afaneh, shapesblue, prdog or mikeman?
All those guys are good people and always helping around the forums.
I've only had the s3 for a couple months (coming from a Galaxy Nexus r.i.p.) and locked on 4.3 when I got it so not really comfortable experimenting with things just yet. But basically the script just changes some very basic things like build.prop and updater script for example but it worked very well in my experience.
Sent from my SCH-I535 using Tapatalk 2

47th_Ronin said:
Perhaps you could enlist the aid of mohammed.afaneh, shapesblue, prdog or mikeman?
All those guys are good people and always helping around the forums.
I've only had the s3 for a couple months (coming from a Galaxy Nexus r.i.p.) and locked on 4.3 when I got it so not really comfortable experimenting with things just yet. But basically the script just changes some very basic things like build.prop and updater script for example but it worked very well in my experience.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I messaged prdog. Even if I can't get a specific answer I'll gladly accept any information on the topic. I'll even test out a lot of the roms if it isn't too "unsafe" and put together a compatibility list for other VZW users.

pyrite123 said:
I messaged prdog. Even if I can't get a specific answer I'll gladly accept any information on the topic. I'll even test out a lot of the roms if it isn't too "unsafe" and put together a compatibility list for other VZW users.
Click to expand...
Click to collapse
Ports are usually only problamatic with calls and messaging. You have to use Verizon modem and maybe even RIL cause ATT don't have CDMA. Biggest problem is you need Verizon kernel which we don't have.

prdog1 said:
Ports are usually only problamatic with calls and messaging. You have to use Verizon modem and maybe even RIL cause ATT don't have CDMA. Biggest problem is you need Verizon kernel which we don't have.
Click to expand...
Click to collapse
So you're saying there is no way to flash any of the roms and get them fully functioning without a supported kernel? :sadface:
I have an Aroma addiction >;O

pyrite123 said:
So you're saying there is no way to flash any of the roms and get them fully functioning without a supported kernel? :sadface:
I have an Aroma addiction >;O
Click to expand...
Click to collapse
No matter what we do we need a Kernel. Only option for now is AOSP.

prdog1 said:
No matter what we do we need a Kernel. Only option for now is AOSP.
Click to expand...
Click to collapse
Alright, thanks. It's a shame that companies overcomplicate things and can't all just see eye to eye. Oh well such is life. Maybe one day, when the world is taken over by Google, the world will be a happier place and things will be more simple.
[emoji16][emoji184]
Assuming everything applies to Sprint and i9300 ROMs as well?

pyrite123 said:
I didn't see a thread for this (unless I'm blind, which is partially true). I saw a post somewhere linking to the Dirty Unicorn ROM in the ATT gs3 section and saw that they had loads of roms. I simply wondered how compatible some of these were with the vzwS3 before I just started flashing away... Or maybe there is a list somewhere I failed to see?
Click to expand...
Click to collapse
Most of the AOSP ROMs for the S3 that are still being actively developed have moved to putting out one unified build that works on all US variants of the S3. They will use the tag [D2LTE] in the thread title to note that. [D2VZW] is the Verizon version of the phone. So you can use ROMs that advertise compatibility with either D2LTE or D2VZW. The only problem is that as you've seen, since development for the S3 was, for a long time, specific to each carrier's model, the various D2LTE ROMs are kind of spread around among the various forums for each individual S3 model. The LiquidSmooth thread in the AT&T forum, for example, seems to be the only one that gets updated anymore, even though that ROM is built for D2LTE now and works fine on the Verizon S3. Task650's AOKP build runs fine on our phones too and can be found in the AT&T S3 forum.
If you search all forums for the tag [D2LTE], that's a decent way to get an idea of what's out there now.
ETA: I left out something which I hope you know by now: your bootloader needs to be unlocked to use anything with a D2LTE tag. If you took either the Android 4.3 or 4.4.2 updates from Verizon and locked your bootloader, you're out of luck.

Jacquestrapp said:
Most of the AOSP ROMs for the S3 that are still being actively developed have moved to putting out one unified build that works on all US variants of the S3. They will use the tag [D2LTE] in the thread title to note that. [D2VZW] is the Verizon version of the phone. So you can use ROMs that advertise compatibility with either D2LTE or D2VZW. The only problem is that as you've seen, since development for the S3 was, for a long time, specific to each carrier's model, the various D2LTE ROMs are kind of spread around among the various forums for each individual S3 model. The LiquidSmooth thread in the AT&T forum, for example, seems to be the only one that gets updated anymore, even though that ROM is built for D2LTE now and works fine on the Verizon S3. Task650's AOKP build runs fine on our phones too and can be found in the AT&T S3 forum.
If you search all forums for the tag [D2LTE], that's a decent way to get an idea of what's out there now.
ETA: I left out something which I hope you know by now: your bootloader needs to be unlocked to use anything with a D2LTE tag. If you took either the Android 4.3 or 4.4.2 updates from Verizon and locked your bootloader, you're out of luck.
Click to expand...
Click to collapse
Thanks a lot for the tips. From my time at this forum I had kind of put two and two together and assumed that was what the tags stood for. I hadn't thought of using those tags for searching, though. And luckily I got my S3 last year when I did because my bootloader wasn't locked. And just days later I believe they released that dirty OTA