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!
Related
Well since the international hox has jb (not justin beiber) already http://forum.xda-developers.com/showthread.php?t=1737736 I'm wondering if anyone is working on getting jb (still not justin bieber) running on the xl?
G4 Man2 said:
Well since the international hox has jb (not justin beiber) already http://forum.xda-developers.com/showthread.php?t=1737736 I'm wondering if anyone is working on getting jb (still not justin bieber) running on the xl?
Click to expand...
Click to collapse
we need kernel source. After that it will be just a matter of time. The International HOX also shares a chipset with the Nexus 7 so that helps
gunnyman said:
we need kernel source. After that it will be just a matter of time. The International HOX also shares a chipset with the Nexus 7 so that helps
Click to expand...
Click to collapse
Any news on getting that kernel source?
I'm assuming that we wont have full AOSP roms until we have that source?
Any news on getting S-OFF?
Man, I really cant stand sense anymore
zoltrix said:
Any news on getting that kernel source?
I'm assuming that we wont have full AOSP roms until we have that source?
Any news on getting S-OFF?
Man, I really cant stand sense anymore
Click to expand...
Click to collapse
Go pester HTC and att to release kernel source.
Sent from my HTC One X using xda app-developers app
zoltrix said:
I'm assuming that we wont have full AOSP roms until we have that source?
Any news on getting S-OFF?
(
Click to expand...
Click to collapse
Have you tried the CM9 ROM in development or the AOKP ROM over on Rootzwiki? They are both functional enough to be used as a daily driver.
Why do we need S-off? We can already do basically everything through recovery without it. Would it be nice to have, sure I guess, but definitely not needed.
Kernel source will be released. Could be soon, could be September. We don't know when. But it will be released. Once it is available we will have answers.
Sent from my HTC One X using xda app-developers app
pside15 said:
Have you tried the CM9 ROM in development or the AOKP ROM over on Rootzwiki? They are both functional enough to be used as a daily driver.
Why do we need S-off? We can already do basically everything through recovery without it. Would it be nice to have, sure I guess, but definitely not needed.
Click to expand...
Click to collapse
yea s-off isn't needed, but nice to have.
i've been following the cm9 thread, and it seems great but ive been using my camcorder almost non-stop and i'll miss it for sure
I saw on one of the threads for either MIUI or CM9 but I don't remember which that someone got the camcorder working? I have the file in my download folder on my phone but I haven't tried it yet. I'm just keeping it for if and when I decide to try out MIUI or CM9.
I loaded an unofficial CM9 Alpha 5 ROM on my North American HTC One X and the camera worked, although nowhere near as good as the camera app in the stock HOX software. Camcoder was flaky and crashed periodically. A video I posted on YouTube circa 4:50 has a demo of it: http://www.youtube.com/watch?v=XPi8a5SvJvQ.
If interested, the build I loaded was the alpha5 in the thread "[ROM][WIP] Unofficial CM9 Port - Alpha 5" http://forum.xda-developers.com/showthread.php?t=1688448. Beware of rapid battery drain if you choose to load this alpha5 build I recommend taking 30 minutes and reading through the thread prior to flashing this ROM for details.
Note, however, that this ROM is based off Android 4.0.4 (Ice Cream Sandwich), not 4.1 (Jelly Bean), so this discussion might be a little off topic for this thread
Has the Samsung JB source dropped yet? I've been waiting patently for a 100% stable JB AOSP ROM for GS3 since I got it in June, and since we have official TW JB build now, I was wondering when we can expect to see a fully functional CM10 build, it still looks like there are quite a few bugs with CM10, I haven't tried any of the other unofficial AOSP builds because CleanROM is just running too damn good
Sent from my SCH-I535 using Tapatalk 2
Try 'Beans' B6, it's pretty stable and completely aosp themed, even has the aosp lockscreen. Depends on what you use but I don't see how CM10 has enough bugs to not be a daily driver.
AegonTheDragon said:
Try 'Beans' B6, it's pretty stable and completely aosp themed, even has the aosp lockscreen. Depends on what you use but I don't see how CM10 has enough bugs to not be a daily driver.
Click to expand...
Click to collapse
JB AOSP has been my daily driver for months now... not sure what bugs you're having issues with. Aside from the random bluetooth issues (which don't bother me much) its perfectly stable.
Shibby87 said:
I've been waiting patently for a 100% stable JB AOSP ROM for GS3 since I got it in June
Click to expand...
Click to collapse
100% stable?
You will never find that.
Sent from my SCH-I535 using Tapatalk 2
Neverendingxsin said:
JB AOSP has been my daily driver for months now... not sure what bugs you're having issues with. Aside from the random bluetooth issues (which don't bother me much) its perfectly stable.
Click to expand...
Click to collapse
You misunderstood, I was saying that it DOESN'T have enough bugs to NOT to be a daily driver.
1ManWolfePack said:
100% stable?
You will never find that.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
CM9 was incredibly stable.. wonder If we'll ever get to that point with CM10 or CM10.1 for the GS3.
Sent from my SCH-I535 using Tapatalk 2
aside from some quirks im going to echo what neverendingsin said.
theres no reason you should not try AOSP roms right now. theyve been 100% stable for me.
I sent a FOSS request to Samsung, they should get back to me tomorrow.
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=i535
The sprint JB kernel source was released, thats what ktoonsez and leankernel are going off at the moment for our device.
Shibby87 said:
CM9 was incredibly stable.. wonder If we'll ever get to that point with CM10 or CM10.1 for the GS3.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
CM9 for the s3? "Incredibly stable" and "100% stable" are two far different beasts....
As the title says. I'm looking for a kernel that allows overclocking. I've been looking for a long time but I can't find any. SiyahKernel appears to only work with the i9300 and 4.1. Unless I'm wrong. Thanks.
Also, is CM 10.0 android 4.1? Because im cool with switching to that if it will work with Siyah.
uromastix87 said:
As the title says. I'm looking for a kernel that allows overclocking. I've been looking for a long time but I can't find any. SiyahKernel appears to only work with the i9300 and 4.1. Unless I'm wrong. Thanks.
Also, is CM 10.0 android 4.1? Because im cool with switching to that if it will work with Siyah.
Click to expand...
Click to collapse
Anything you intend to flash is in the Verizon Galaxy SIII Dev or Original Dev section. Do not flash anything labeled for any other GSIII model, you'll brick your phone. I'm certain each custom kernel allows for OCing, you can find most in the Verizon Original Dev section.
CM10 is 4.1. You need to flash CM10.1 which is 4.2.2 because 4.2.2 is under active development. Something to note, flash kernels released either AFTER the date of your rom/nightly OR within a week or two week span. Often enough, there are updates in the rom source that render kernels prior to the rom's release incompatible. You'll know it's incompatible cuz after flashing your screen will be completely black when booting into the rom.
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
Anything you intend to flash is in the Verizon Galaxy SIII Dev or Original Dev section. Do not flash anything labeled for any other GSIII model, you'll brick your phone. I'm certain each custom kernel allows for OCing, you can find most in the Verizon Original Dev section.
CM10 is 4.1. You need to flash CM10.1 which is 4.2.2 because 4.2.2 is under active development. Something to note, flash kernels released either AFTER the date of your rom/nightly OR within a week or two week span. Often enough, there are updates in the rom source that render kernels prior to the rom's release incompatible. You'll know it's incompatible cuz after flashing your screen will be completely black when booting into the rom.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the reply.
So, even if the rom was intended for an i9300 it will work on my 535? Are there any kernels for 4.2.2 that allow OCing?
Will this work with my setup? http://forum.xda-developers.com/showthread.php?t=2226894
My G2 broke last week and I am using this Galaxy S3 until my G2 gets repaired.
It is currently running a VERY old version of CyanogenMod - CM10.1 20130713 EXPERIMENTAL version and ClockworkMod Recovery V6.0.3.1 which I know is quite old version.
I was wondering what steps I need to take to get this phone running a 4.4.x ROM? What should I flash first? Also any recommendations on 4.4.x ROMs - AOSP vs. TouchWiz?
Thanks in advance.
Stigy said:
My G2 broke last week and I am using this Galaxy S3 until my G2 gets repaired.
It is currently running a VERY old version of CyanogenMod - CM10.1 20130713 EXPERIMENTAL version and ClockworkMod Recovery V6.0.3.1 which I know is quite old version.
I was wondering what steps I need to take to get this phone running a 4.4.x ROM? What should I flash first? Also any recommendations on 4.4.x ROMs - AOSP vs. TouchWiz?
Thanks in advance.
Click to expand...
Click to collapse
My recommendation would be to update ClockworkMod Recovery first. I think they're on to version 6.0.4.5 now, not sure though since I'm using TWRP instead.
In regards to choosing a ROM I think that depends on what you're into. Since you're already running CyanogenMod and you want 4.4 then you should probably take a look at CM11. I had mobile network/signal problems using the "Official" build so I'm using a Mastamoon unofficial build, it works great. Search for: cm-11-20140709-unofficial-mastamoon-d2lte.zip
CrustyMcLovin said:
My recommendation would be to update ClockworkMod Recovery first. I think they're on to version 6.0.4.5 now, not sure though since I'm using TWRP instead.
In regards to choosing a ROM I think that depends on what you're into. Since you're already running CyanogenMod and you want 4.4 then you should probably take a look at CM11. I had mobile network/signal problems using the "Official" build so I'm using a Mastamoon unofficial build, it works great. Search for: cm-11-20140709-unofficial-mastamoon-d2lte.zip
Click to expand...
Click to collapse
Do I need to flash anything before going to a CM11 ROM from CM10?
I see in a lot of ROM threads about locked bootloader or certain baseband, etc.
Any advice on that? Anything I should be weary about?
Stigy said:
Do I need to flash anything before going to a CM11 ROM from CM10?
I see in a lot of ROM threads about locked bootloader or certain baseband, etc.
Any advice on that? Anything I should be weary about?
Click to expand...
Click to collapse
Yeah you should probably upgrade to MF1. There is a link to it on the page for that particular ROM i had recommended. I don't think a locked bootloader will be an issue at this point since you've already got CM10 on there.
http://forum.xda-developers.com/showthread.php?t=2569769
Ok I'm lost. I've been reading around for the past few hours & I've been out of the loop for too long to make sense of this.
I have scrosler's [ROM][1/27/14] - Stock Rooted Knoxless - VRUCML1 - Android 4.3. I have the unlocked bootloader because I have TWRP installed (right?). I did NOT take the OTA to get to 4.3.
With baseband VRUCML1 can I jump to any other ROMS still? Or what should/shouldn't I be looking for?
I'm thinking of trying CM11 or SlimKat
If you can list the version then that would be great. If you do have TWRP installed, yes your bootloader is unlocked and you can flash any Touchwiz rom up to 4.3 or any AOSP rom.
Sent from my SCH-I535 using Tapatalk 4
Darn, only up to 4.3...
Versions:
Android: 4.3
Baseband: I535VRUCML1
Build #: JSS15J.I535VRUCML1
TWRP: v2.6.3.1
Finch32786 said:
Darn, only up to 4.3...
Versions:
Android: 4.3
Baseband: I535VRUCML1
Build #: JSS15J.I535VRUCML1
TWRP: v2.6.3.1
Click to expand...
Click to collapse
I think you misinterpreted me. You can flash any AOSP rom that you want since you have TWRP installed. You're limited to 4.3 roms for Touchwiz. CM and SlimKat are ok.
Word of advice, if you're looking to use KitKat AOSP, the S3 has unified builds. One zip for multiple carriers. KitKat AOSP roms will be listed as "d2lte" when you search for recently updated downloads.
Sent from my SCH-I535 using Tapatalk 4
As you told you have custom recovery and unlocked bootloader...
I have tried many ROMs and personally will suggest you to go with cm11 .
Slim is also cool but cm has good features and gets updated quickly as there is a Professional team working on it.
Where as on slim if some one ports or adds some more stuff then u will get update which won't be ota ( cm will have some ota update )
Cm is cool ASOP is also cool.
Visit www.learnhacking.net
Please thank me if I helped
Sent from my Micromax AQ4501 using XDA Free mobile app
SlimSnoopOS said:
I think you misinterpreted me. You can flash any AOSP rom that you want since you have TWRP installed. You're limited to 4.3 roms for Touchwiz. CM and SlimKat are ok.
Word of advice, if you're looking to use KitKat AOSP, the S3 has unified builds. One zip for multiple carriers. KitKat AOSP roms will be listed as "d2lte" when you search for recently updated downloads.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
THANKS SLIM!
Next time I'm dropping the $ on an unlocked phone so I don't have to "think" about what I can & can't do (Stupid Verizon).
Finch32786 said:
THANKS SLIM!
Next time I'm dropping the $ on an unlocked phone so I don't have to "think" about what I can & can't do (Stupid Verizon).
Click to expand...
Click to collapse
You're welcome, always here to help out :good::good:
Also, I'm thinking the same as well in terms of an unlocked phone. Tired of worrying about which OTA is not for my phone or things like that.
kustom.hackers said:
( cm will have some ota update )
Click to expand...
Click to collapse
This is actually a question I've had for a while. What sorts of things have OTA updates on CM? Does CM update "OTA" often or rarely? I used CM years ago on my OG Droid, but they didn't have updates back then. I keep hearing there are some kinds of updates on CM, but I can never find out what this really means... can you elaborate for me, please?
Reply
schwinn8 said:
This is actually a question I've had for a while. What sorts of things have OTA updates on CM? Does CM update "OTA" often or rarely? I used CM years ago on my OG Droid, but they didn't have updates back then. I keep hearing there are some kinds of updates on CM, but I can never find out what this really means... can you elaborate for me, please?
Click to expand...
Click to collapse
It depends actually if the developers will fix and update your device ... its on luck ... for example if the developer has the device and he will update for himself. Also it depends on device if it is capable of running the new android , means the hardware capablitity .... You can install cm11 as they are fast in fixing stuff and if you have some problem , xda will help you as cm is common on xda...
I had used cm11 on galaxy tab 2 and it worked like charm ... i was update ( android version v4.4.4 where as on stock they use v4.2 ) f***ing nice.... thanks to xda and cm.... love you all....