Firstly, sorry I had posted same question in (I don't know where). But I need to post it here in Verizon.
I have installed HE update, Rooted, Unlocked, IMEI backed up, Recovery installed.
#1 Do custom ROMS include the baseband or not? Meaning, does it override the HE I have installed?
#2 Do ROMS need to be specifically designed for HE baseband, for me to flash them and work properly?
Thanks.
PS I am waiting for the Milestone release of AOKP, how will I know if it is made for the HE, will mess up because of me having HE? Is it buried in the AOKP change log, or does the developer control that?
No and no
I may be wrong, but as far as I know, AOSP ROMs (including AOKP) don't build for a particular radio. Until we get an official Verizon TouchWiz jellybean update, the RIL and other networking tweaks in AOSP roms are made from scratch, and should work with any radio. Some radios may work better or worse for you with any given ROM, so you might as well try them all until you find the one that works best for you.
Sent from my SCH-I535 using Tapatalk 2
First things first....You didnt know where to post a question....there is a q&a section where you posted....dont be ignorant.
Thread moved to q&a.
Related
Hi everyone,
Quick question. I've been searching the forums and dev section for a while now, and couldn't find a concrete answer, so I made an account to simply ask. If I am on the Verizon OTA JB update, 4.1.1, rooted with an unlocked bootloader, can I flash the KT747 Kernel without any adverse impacts? I am looking to keep my rom stock for usability (I used to flash all the time on my Droid X and stability issues were problems), but would like to increase performance via a modded kernel. I am just wanting to make sure, since the dev section says I need either JB AOSP or TW. I assume my stock OTA JB is TW?
Sorry for any naive questions. Thanks in advance!
kude87 said:
Hi everyone,
Quick question. I've been searching the forums and dev section for a while now, and couldn't find a concrete answer, so I made an account to simply ask. If I am on the Verizon OTA JB update, 4.1.1, rooted with an unlocked bootloader, can I flash the KT747 Kernel without any adverse impacts? I am looking to keep my rom stock for usability (I used to flash all the time on my Droid X and stability issues were problems), but would like to increase performance via a modded kernel. I am just wanting to make sure, since the dev section says I need either JB AOSP or TW. I assume my stock OTA JB is TW?
Sorry for any naive questions. Thanks in advance!
Click to expand...
Click to collapse
Yes you can with custom recovery.
Ya you want the touchwiz kernel, here is the link http://www.mediafire.com/?ixn5n9xjnwbve8r
Thanks guys!
I flashed it and everything seems to be running perfectly fine. I will give it some time until I form an opinion, but I hope I can get the results that many others are reporting.
Basically, I'm trying to port this rom to the Samsung Vibrant. I am using the latest Cyanogen Mod nightly as the base rom and following the tutorials for porting roms to other devices. I just want to make sure that I have properly checked everything, since I'd rather not test the rom on my device without community help. I've checked to make sure that the resolutions are similar, etc. My question is, is there anything I'm missing or anything that I should fix?
Accidentally double posted: Can a mod delete this thread?
So, anyone willing to answer this question for me?
Question #1: GPS
I have the Samsung Galaxy S 4G which has been long rooted and I've installed a few roms now on it. Recently I upgraded to Revolt 4+ which is my first attempt to find a Jelly Bean ROM that will work for me. Well, I love it. Only problem is that it seems it doesn't have GPS? Google Maps work but Navigation doesn't follow me which I'm guessing means it's using internet to "find" me. There's no GPS flashing icons nor are there any settings for GPS. Is there anyway to get it working or is it just not working for this ROM?
Question #2: Aries?!
Many of the roms mention "Aries's common bugs" but google searching it gives me nothing. Where can I find information about Aries?
Question #3: The latest fully-working ROM?
There are soooo many ROMs to choose from for the SGS4G that I don't know what to look for. I found and have been using THIS page but not sure how outdated/accurate it is. Anybody know the best/most recommended ROM right now that has all the main parts working? GPS, WIFI...etc? I know wifi calling always has issues but not important.
:good: to anybody who is able to help with any of the above!
Hi.
#1 All JB ROMs (meaning 4.1.2 and above) have Aries kernel.
it is faster than Herrig kernel used before, and should be more stable, but, no developer was able to make GPS work with it. so, there's currently no JB ROM with a working GPS.
#2 If you want a working GPS you will need ICS (4.0.3/4.0.4) ROM :
CM9/AOKP/Slim/MIUI/Ultragen etc.
I'm a MIUI freak so I can say I love HebMIUI which is an upgraded MIUI version I came up with. you can try it (see my signature) or any of the others I mentioned.
Slight addendum to #1. Not entirely true. Some of the earlier JB ROMs were still Herring. The various 4.2 Wifi-bugs were on Herring. Any ROM where they tell you to do the 4.1.2 JB if you wanted Wifi, it's a Herring kernel. For that matter, I believe we've only had compiled 4.2.2 and above Aries here. So if the ROM is 4.1.2 JB, it's Herring. If it's 4.2.2 without working Wifi, it's probably Herring. If it's 4.2.2 with Wifi or 4.3, it's probably Aries.
Agree on ICS/GB for GPS though. HebMIUI or Ultragen 1.01 (DO NOT USE ULTRAGEN 1.00 AND POST BUG REPORTS) are probably your best ICS options.
THANK YOU both for clearing up alot of stuff for me. Thank you x2 for itzik2sh for recommending HebMIUI. I have it installed and I love it sofar. Hopefully somebody figures out JB GPS eventually.
I'll still check back here if anybody else has anything else to throw in.
So I've been rooting and dabbling with Android since Droid OG.... great start to the post right?! At this point I've successfully unlocked bootloader and put a few different ROMs onto my VZW GS3 16GB. I currently have Synergy 4.1.2 JB ROM with the stock kernel via AROMA installer from the ROM Dev. Everything worked from the gate, but my camera wouldn't initialize. Through searching these forums, I found that if I flashed the VRBMF1 Stock Kernel it should fix the camera. When I flashed it, the camera issue was fixed! The issue that I'm running into now is that my WiFi isn't operable. I can't turn it on at all. Through more searching, I learned that others had similar issues; however there seem to be various fixes/workarounds. Due to the fact that I need to have at least 10 posts before posting this to the OP/Original Thread, I figured that maybe some of you AMAZING community members would be kind enough to assist. So... thoughts?
Baseband
I thought that I should also add that I have the MF1 modem and baseband of I535VRUCML1.
LogCat
At this point I haven't got a logcat, so if one is needed I'll have to install it and attach the output here.
fixed it
Just in case anyone is curious about this, I dirty flashed the rom again with Stock Kernel. Then I flashed KT717 Kernel. This solved Wifi and Camera issues.
Is there any method we can change the build number on the cm13 zip file we download to be able to install it on a newer version?
or is there any method for us to build the cyanogenmod 13 rom on our own(since everything is available)? It should help many people. Also if possible I would like to build an aosp rom for our devices. I have another stupid question, please bear with me. Someone has created the cyanogenmod rom for us and it is official, but they did not make any posts in the xda forums .
Im curious about some of this stuff, too. Especially the reason why you can't flash on the newer firmware, and why no CM thread.
rouyal said:
Im curious about some of this stuff, too. Especially the reason why you can't flash on the newer firmware, and why no CM thread.
Click to expand...
Click to collapse
exactly! hope to find out soon.
newer builds have a different bootloader. probably just the guy hasnt noticed because he uses cm13 which doesnt touch the bootloader