[CM12][Q/A] Discussion thread for CM12 - Samsung Galaxy SL i9003

This thread is for any questions regarding the CM12 build I'm making.
Link to ROM thread: Coming soon.
Sent from my GT-I9003 using XDA Free mobile app

Waiting for the rom
Excited to test it.

Still building..... Keeping my fingers crossed
Sent from my GT-I9003 using XDA Free mobile app

God I'm *this* close to success and it just won't get to the boot animation. *sigh*
Sent from my GT-I9003 using XDA Free mobile app

Has there been any progress on this ROM?

Why is porting so hard
As far as I understood, to get a new Android on Device X is as following: :silly:
1) Download latest CM-ROM
2) Copy drivers from Device X´s stock ROM to latest CM-ROM
3) Configure build.prop eg. screen resolution/DPI&co.
4) Zip and flash it
Am I right? Wrong? :cyclops::fingers-crossed:

[email protected] said:
As far as I understood, to get a new Android on Device X is as following: :silly:
1) Download latest CM-ROM
2) Copy drivers from Device X´s stock ROM to latest CM-ROM
3) Configure build.prop eg. screen resolution/DPI&co.
4) Zip and flash it
Am I right? Wrong? :cyclops::fingers-crossed:
Click to expand...
Click to collapse
I wish it were that simple
The thing is that there could be kernel and initramfs changes necessary, which is something to be built from source. Also, there are device specific files spread all over the ROM, not to mention architecture differences and lack of space. Therefore, it's better to build from source by forward porting the device

ahsanovich said:
Has there been any progress on this ROM?
Click to expand...
Click to collapse
I have a build of NamelessROM 2.0 on GDrive but it's not suitable for daily use. Also, due to the ever-increasing resource usage of Google Play Services, Android seems to be no match for our low end devices. I'm giving one last try for Omni 7.1 and if that doesn't work out, I'll scrap Android for Ubuntu Touch

Thread closed as per OP request.
Wood Man
Forum Moderator

Related

[UNOFFICAL] [CRACKFLASHER] [ROM] CM7 Build #29

So the crackflashers have done it again - Gingerbread is now on the Desire / Bravo
Based on CM 7 Source
Thanks to Cyanogen, #teamdouche and @gridlock32404 (Thatguy32404) - These are unoffical builds based on their code as such..
Code:
These builds have nothing extra added, they are just like the usual
"nightly" builds. There is no support provided, this is just a hobby and
I thought I would share. If you don't know how to flash a unofficial build,
don't want possible bugs or don't like living on the edge, go away!
Do a nandroid backup first!
OK so here is how to get it up and running:
Step 1 - Download the latest build from http://www.crackflashers.com look in the builds folder for the latest file - The build will increment by 1 each time there is a new build so if there is one there greater than b#29 download it << In case I don't get the thread updated at the same time
Step 2 - Download the Gingerbread apps from NEEDS UPDATED TO POINT TO DESIRE / BRAVO. crackflashers.com/ace/[/URL] look in the google-apps folder for the file gingerbread-gapps-12302010.zip
Step 3 - Place all these files onto your sd card reboot into recovery
Step 4 - Flash the files using the install zip from sdcard option (do the rom first then the gapps)
Step 5 - Reboot phone and enjoy the Gingerbread goodness
Current Issues
Current Issues
#17 - APN list may be empty and you will need to manually enter this - a complete list can be found at http://code.google.com/p/cyanogenmo...orum.xda-developers.com/show...&postcount=271 for resolution
does it can be use with n1 table hboot?so, you will update nightly?
anyway, nice work!
nice work, will surely give it a try
any benchmarks?
najar360 said:
does it can be use with n1 table hboot?so, you will update nightly?
anyway, nice work!
Click to expand...
Click to collapse
Check out the N1 thread http://forum.xda-developers.com/showthread.php?t=883605
I only tested it and maintain the thread - the guys above deserve the kudos
gilmorenator said:
Check out the N1 thread http://forum.xda-developers.com/showthread.php?t=883605
I only tested it and maintain the thread - the guys above deserve the kudos
Click to expand...
Click to collapse
how bout a2sd+?does it work with dark tremor or firerat?
edit : confirm can't use with firerat.
najar360 said:
how bout a2sd+?does it work with dark tremor or firerat?
Click to expand...
Click to collapse
This is the first build that I actually made for the desire so to say we don't exactly know what other additions made outside the source/gingerbread will or won't work. The only way to try is to make a nandroid backup after you flash this in and try it
Ps. The new recovery image is not supported in rom manager so everything will need to be done in the recovery manually even thought the code of the recovery is made by koush it is not an official release by him at all, just built from it. it is the only recovery currently that can handle ext 4 /system partion that cm7 source is based on.
You will not be able to restore a pre-cm7 source build on this recovery or flash a pre cm7 rom on it either (hence the backup recovery.img if you decide to go back) you can backup and restore any cm7 source rom on this recovery
Yes the new recovery is needed to flash gapps and newer updates as they become availible.
This is on the list of many devices I am compiling for. Currently g2, mt4g, evo4g, droid, desire hd, desire and sometimes the n1. If you can't seem to find an answer to something there is a good chance you will find it in one of those sections. Just look for posts from me
Sent from my HTC Vision using XDA App
Thatguy32404 said:
This is the first build that I actually made for the desire so to say we don't exactly know what other additions made outside the source/gingerbread will or won't work. The only way to try is to make a nandroid backup after you flash this in and try it
Ps. The new recovery image is not supported in rom manager so everything will need to be done in the recovery manually even thought the code of the recovery is made by koush it is not an official release by him at all, just built from it. it is the only recovery currently that can handle ext 4 /system partion that cm7 source is based on.
You will not be able to restore a pre-cm7 source build on this recovery or flash a pre cm7 rom on it either (hence the backup recovery.img if you decide to go back) you can backup and restore any cm7 source rom on this recovery
Yes the new recovery is needed to flash gapps and newer updates as they become availible.
This is on the list of many devices I am compiling for. Currently g2, mt4g, evo4g, droid, desire hd, desire and sometimes the n1. If you can't seem to find an answer to something there is a good chance you will find it in one of those sections. Just look for posts from me
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
thanks for explanation. anyway i try firerat and it failed. not yet try with dark tremor.
question, if i use current recovery such amon ra or previous clockworld, is it give diff outcome?
najar360 said:
question, if i use current recovery such amon ra or previous clockworld, is it give diff outcome?
Click to expand...
Click to collapse
You may flash the ROM with your current recovery but you won't be able to flash GAPPS - making it a bare rom
Sent from my HTC Desire using XDA App
Sorry to get your hopes up guys, the code for the cm parts is there in the source and was all good to be added in but what the main code (not just the app but the framework parts of it) were removed till implemented. Still a build 13 coming shorty. It is compiling but will be missing the cm parts
Sent from my HTC Vision using XDA App
Build 13 is up, has gps fixes and other things. Too tired to list all changes check @cmsrc on twitter or github for what's been added
Sent from my HTC Vision using XDA App
deleted.....
woa.. just another cyanogen copy
For those having problems with Gapps on newer htc phones like g2, mt4g and desire hd try the new gapps I have posted up at http://gridlock.euroskank.com and grab the EMMC ones
Everyone else can grab the MTD gapps
This should remove having to mount /system in recovery but run fix permissions in the advanced section of the recovery just in case
Sent from my HTC Vision using XDA App
Midian666 said:
woa.. just another cyanogen copy
Click to expand...
Click to collapse
It isn't one bit at all a copy, just doing the service of basicly compiling the cm7 source just like a nightly untill buildbot is back building them (should be after a official rc1 release) and sharing
Sent from my HTC Vision using XDA App
Build #14 will be up on http://gridlock.euroskank.com within minutes. This should have a fix for data, if so thanks to phunkycow for the fix
Sent from my HTC Vision using XDA App
nice... auto-nightly builds of cm7... how i missed that
whats cwm3 originate from? is there also a changing codebase, or is this a static build, which wont change at all?
mad-murdock said:
nice... auto-nightly builds of cm7... how i missed that
whats cwm3 originate from? is there also a changing codebase, or is this a static build, which wont change at all?
Click to expand...
Click to collapse
There isn't any nightlies that I know of! Cwm3 is the recovery that is in the cm7 source code and it builds a recovery for the device that you compile for. Only when someone changes something in the recovery does it change
Sent from my HTC Vision using XDA App
Why are we unable to flash G-Apps with older recoveries?
Thanks for the effort, it's great to see some progress on this front!
bemymonkey said:
Why are we unable to flash G-Apps with older recoveries?
Thanks for the effort, it's great to see some progress on this front!
Click to expand...
Click to collapse
Once you flash a cm7 source based rom the system becomes ext4, other roms/cm6 are only ext 4 so in order for the /system to mount in recovery for making nandroid backups or to flash anything it needs to have a recovery that can support ext4, which currently is the recovery posted with these builds which is based on clockworkmod recovery because koush hasn't released a official recovery yet (also since it is unofficial rom manager does not support it, so everything has to be done manually in the recovery)
Sent from my HTC Vision using XDA App

[WIP][ROM][SLIMCM][4.2.2]by DroidModderXtreme

Hi guys ,today i'll show you a ROM built from Cyano's sources which is very fast,stable and slim
FEATURES
1)Based on the latest nightly version of cyanogenmod
2)Android 4.2.2
3)Nova and Trebuchet Launcher
4)Build.prop full tweaked
5)158 mb
DOWNLOADs
1)ROM : HERE
2)GApps JB : QUI
INSTALLATION
1) Reboot in CWM
2) 3 WIPEs
3) Install zip from SDcard > choose zip of ROM/GApps and install them
4)Reboot:laugh:
WARNING
1)Don't upgrade via OTA the ROM ( wait my release )
2)My release will arrive every 2 weeks or before
First! #YOLO
Second and finally first page. Ill give it a spin when I get home.
Downloading now. Any bugs or issues that I will encounter or is that something I'm looking for?
Sent from my SCH-I535 using xda premium
Are you really 11?
Signature:
Please read this:https://plus.google.com/app/basic/stream/z12bhtd4nwvmihxsi232wldpfo3mfj3pl04
Thread moved and retitled as work in progress, let's give the OP the benefit of the doubt and try to help him get the build working correctly.
To the OP, you need to provide kernel source and proper credits and thanks. I highly suggest you read the following link and try to get your thread caught up to standard. Then let us know for proper thread assignment.
http://forum.xda-developers.com/showthread.php?t=1728748
Could be cool. Post your source.
Sent from my SCH-I535 using XDA Premium HD app
I asked in PM and did not get a response. Kernel source must be posted.
Please do so asap
Thank you for your cooperation
Friendly Neighborhood Moderator

[ROM][4.3][UNOFFICIAL] CyanogenMod 10.2 [08-18-13]

Fourth Night Nightlies​Freshly build every fourth night
Disclaimer
YOUR WARRANTY IF NOW VOID
I am not responsbile for bricked devices, dead SD Cards,
or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in the ROM
before flashing it!! YOU are choosing to make thse modifications, and if
you point the finger at me for messing up your device, I will laugh at you!​
I would still consider this a "beta" release as its still so new and there will be bugs with it. I don't do anything to this version besides sync repo, small changes, and build. If you looking for a modified version of CM10.2 Check out my androfly for flo. Its modified and has linaro
Features:
CM10.2
Android JB 4.3
Root
Busybox
Working OTA system
Apollo
Camera/ Focal
CM File Manager
Zipaligned
All Images, Sounds, APK's Optimzed
Install Instructions
Download Latest ROM
Place on the Root of your SDCard
Reboot into Recovery
Scroll down and select "wipe"
Select factory reset/wipe data
press return
Select install ROM
Install GAPPS (optional)
Reboot and Enjoy all the Happiness that is CM10.2
Downloads
ROM Builds - ACTIVE-
Download the Latest
FAQ​
Q: After I flash your ROM, I lost root. How do I regain root access
A: You actually didn't lose root, you just need to re-enable root access. Follow these steps
Settings
Click on Developer Options (if you don't see developer options follow the next 2 steps)
Scroll to About Tablet
Click on Build Number 7 times to enable Developer Options
Then click on Developer Options
click on root access and change to apps and ADB
Q:
Mine too
Can't wait to get home and download!
Sent from my SCH-I605 using XDA Premium HD app
Just curious, are you actually part of the team or just posting the thread?
whoamanwtf said:
Just curious, are you actually part of the team or just posting the thread?
Click to expand...
Click to collapse
No not part of the team, I downloaded the source code a while ago, but updated and built this this morning. It was official as of last night I was following cm10.2 pretty closely as I was working on stuff for a couple other devices i build for. Im also working on a Linaro stock version for us
Upload is almost done...a few more mins
Was emoji support removed? I swear I had emojis when I used Tablet Talk on my 2012 Nexus 7, but it's not working here. Am I missing something?
A.C.Sanchez said:
Was emoji support removed? I swear I had emojis when I used Tablet Talk on my 2012 Nexus 7, but it's not working here. Am I missing something?
Click to expand...
Click to collapse
Not that im aware of, I can look and see if it was or not. I normally dont use emoji's
Official build!! Sweet!
Sent from my Nexus 7 using Tapatalk 4
Thread title should be UNOFFICIAL to avoid confusion.
CMNein said:
Thread title should be UNOFFICIAL to avoid confusion.
Click to expand...
Click to collapse
This is the Official source, not modified, so its the same builds as you will see from them and its also officially supported by them. Unofficial would be something that is not support by the cyanogenmod team... so its really not unofficial
clmowers said:
This is the Official source, not modified, so its the same builds as you will see from them and its also officially supported by them. Unofficial would be something that is not support by the cyanogenmod team... so its really not unofficial
Click to expand...
Click to collapse
Anything not built by the CM Jenkins is considered "unofficial", builds are automatically flagged as such unless you export them in a special way. I've been building my own completely "unofficial" builds, from the official repos, for quite a while.
Anybody having any luck using this build with SlimPort?
When I plug in to an HDMI device the Nexus 7 soft resets.
Thank you for any insights.
CMNein said:
Anything not built by the CM Jenkins is considered "unofficial", builds are automatically flagged as such unless you export them in a special way. I've been building my own completely "unofficial" builds, from the official repos, for quite a while.
Click to expand...
Click to collapse
He's right this is not an official thread. Hope mods see this and get the title changed. Fooled me.
Don't like me........BITE ME!!!
justibasa said:
He's right this is not an official thread. Hope mods see this and get the title changed. Fooled me.
Don't like me........BITE ME!!!
Click to expand...
Click to collapse
Yeah, not trying to give him a hard time, but XDA readers can get confused easily at times.
Wow just flashed and got 6799 on quadrant.
Sent from my GT-N7105 using xda app-developers app
CMNein said:
Anything not built by the CM Jenkins is considered "unofficial", builds are automatically flagged as such unless you export them in a special way. I've been building my own completely "unofficial" builds, from the official repos, for quite a while.
Click to expand...
Click to collapse
Yeah, I found out lol. I was under the impression that if its officially supported by them and source was from their repo, and built using their stuff, it was official my b./..but either way every 4 nights official or not lol
digweed4me said:
Wow just flashed and got 6799 on quadrant.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
How can I enable root?
I've read a few things that we have to manually root after we flash roms, but my toolkit isn't reading my tablet when I connect it...
Is there a flashable zip for root?
Kevin Goot said:
How can I enable root?
I've read a few things that we have to manually root after we flash roms, but my toolkit isn't reading my tablet when I connect it...
Is there a flashable zip for root?
Click to expand...
Click to collapse
Root is installed already, What you might have to do is to enable it in the dev options

[ROM][AOSP][DEV][WIP][S4] Unofficial OmniROM 4.4 CLOSED!

Why Omni?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Taken from http://omnirom.org/why-omni/
Screenshots and more info are here
BACKUP YOUR PHONE!!!
* Your warranty was void when you started messing around with your phone.
* These builds are unofficial and are unsupported.
* ONLY YOU AND NO ONE ELSE IS RESPONSIBLE FOR ANYTHING BAD THAT MIGHT RESULT FROM FLASHING THIS ROM!
* Finally Blah Blah Blah good luck!
This ROM probably has the same requirements as any other AOSP 4.4 based rom with the 3.4.x kernel.
Nandroid and then a full wipe.
ROM when its up you can Download Here
PA 0-Day Gapps Get it here
if needed SuperSU 1.75
KNOWN BUGS
Probably whatever is wrong with other KitKat 4.4 roms so...you tell me?
This is based on work done by xHausx for the HTC Evo 4g LTE. You can view the original thread HERE
Thanks
Especially xHausx for the device and common repos and for taking the time to help me get the build process running.
intervigilium for kernel and device repos, because without him most HTC devices would still have Sense
XpLoDWilD, pulser_g2 and all of Team OmniROM
CM for the various repos and for all they've done for the community
XDA:DevDB Information
OmniROM, a ROM for the HTC One S
Contributors
mo976, xHausx
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Abandoned
Created 2013-10-31
Last Updated 2013-12-03
Reserved
NO SD CARD!!!
A fix is being worked on but... NO ETA's
Looks promising. Cant wait to try it.
Thanks for keeping the One S alive.
Gotta try this! Thanks
Sent from my One S using XDA Premium HD app
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
yooouuri said:
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
Click to expand...
Click to collapse
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
mo976 said:
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
Click to expand...
Click to collapse
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Flashalot said:
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Click to expand...
Click to collapse
Well I'm trying anyhow after going through the various dependency files just to double check. I'm hoping it was just a bad build or something so I am pulling down the repo from scratch and hopefully will have a new build in a few hours.
Sent from my One S using XDA Premium 4 mobile app
Looking forward to this
And maybe try the 1.20 radio...
First working build is up try it out let me know!
mo976 said:
First working build is up try it out let me know!
Click to expand...
Click to collapse
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
nespresso33 said:
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
Click to expand...
Click to collapse
I noticed that but wasnt sure if its a feature or bug...lol it seems to come and go...
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
yooouuri said:
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
Click to expand...
Click to collapse
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
mo976 said:
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
I will check if that's whats missing. I am not sure how to disable strict mode by default since its a setting. Lock screen delay should be the same as cm since its the same kernel.
Sent from my One S using XDA Premium 4 mobile app
yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
mo976 said:
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
Click to expand...
Click to collapse
Maby a logcat will give the information you'll need?
yooouuri said:
Maby a logcat will give the information you'll need?
Click to expand...
Click to collapse
I understand what it says but...it may as well be Chinese because I am not any closer. I attached if you want to take a look.

[ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw)

[ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw)
CyanogenMod and D2VZW: Together Again!
--------------------​DANGER!! CMUpdater is providing the new CM13 Marshmallow nightly builds and notifying you of an update. IT SEEMS THERE ARE NO MORE UPDATES FOR CM12! 12/10 seems to be the last one. If you flash CM13 without looking into things first, you could be in for a world of hurt! Check out invisiblek's Official CM13 Nightlies thread in this same forum. BEWARE!!​--------------------​
De-unified Lollipop builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances... If you've done it or want to try, please tell us what happens.)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will put a picture
* of you up and throw darts at it.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit the Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Regarding the Stagefright Exploit: The latest patch update to protect against the security vulnerability was merged for the 8/14 nightly. Please update to that or later to make sure you are fully protected, though work still continues.
XDA Article on the Stagefright Exploit: http://www.xda-developers.com/stagefright-explained-the-exploit-that-changed-android/
Download Links :: Download Links Broken!! - On or about 12/18 the links for 12.1 ceased to function. The links for 12.1 and 13 are all listed on the same page at the moment as well. While 12.1 builds have continued to come out every few days or so for other devices, the last one for the d2vzw is for 12/10 at the moment. I don't know if this is a temporary of permanent state of affairs but inquiries are forth coming. In the mean time, the 12/10 build is in the "d2vzw ROM Extras" link below so at least we got that, thanks to XdrummerXboy.
Also, if you have a build from about 11/15 and later hanging around you could upload it for others to access, if need be, by following the instructions from this post: Upload Instructions ​
CyanogenMod:
Nightly: http://download.cyanogenmod.org/?device=d2vzw&type=nightly LINKS ONLY WORKS FOR CM13 NOW!!
Download with daily commits tracked:http://www.cmxlog.com/12.1/d2vzw/
>>These are the de-unified d2vzw builds now instead of the d2lte builds you previously used<<
Google apps addon:
TK Modular GApps by TKruzze. Get your GApps from the Master. Follow his installation instructions.
Open GApps:opengapps.orgThey are modular AND have the option of Aroma Installer. Updated daily. Very interesting story on these. There is the website, and an XDA thread.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
Other Options:
The Gapps Central For those of you who just have to be different, a GApps Smorgasbord, by TheXGX
Banks Gapps removed after just one too many malfunctions... If you use 'em and have a problem, update from the Play Store your offending app or flash one of these others, but don't come complainin'.
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
A MF1 firmware only zip is in the "d2vzw ROM Extras" link below, as well as individual modem choices.
Other Possibly Useful Stuff
d2vzw ROM Extras
Link to TWRP Recovery You can flash the .img file right in TWRP recovery 2.8.4 or later!
- All you ever wanted to know about how Cell service works but were afraid to ask: Cell Wiki
- Samsung Galaxy S 3 the most popular phone of all time? Still? https://en.wikipedia.org/wiki/Samsung_Galaxy_S_III
Notes - Possible Bugs
Bluetooth observed as flaky with some connected devices.
CMUpdater apparently only functional with TWRP 2.8.7.0
4G/LTE Data might not start on bootup (lately) - With Wifi disconnected or off, go to Settings>Mobile Networks>Access Point Names and select one of those not already selected. Give it a few seconds. Should be good till next reboot.
Addendum to Data Issue: If you can't live with the above solution (like me) then downgrading to the ML1 modem has fixed it, seemingly without any ill effects. Modem is in the "d2vzw ROM Extras" link above.
>>Attention ATT, T-Mobile and other GSM Network Users (International)<<
If you use your d2vzw on one of the GSM networks, you will have to flash the d2gsm_rilblobs.zip file in the 'd2vzw ROM Extras' link above or your phone won't operate properly!
The CyanogenMod team (of which I'm not a member) always thanks everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Another Note: CM12 was introduced to our phone first by mastamoon and Invisiblek: Many thanks to them! There may be data on those threads that can help someone, so I've included those links for reference:
Mastamoon's Unofficial CM12 (and cm11) thread.
Invisiblek's Unofficial CM12 thread by amf66.
<Disclaimer: OP is not a Dev. Just a normal schlub.>
XDA:DevDB Information
[ROM][Official] CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
Master Cylinder, Nardholio, Device Maintainer: Nardholio
Source Code: http://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: VRBMF1
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-05-20
Last Updated 2017-06-10
YES!!! Long live the GS3... ?
Would it be a good idea to link the old thread in the OP? I can understand both sides, including it or leaving it out, though.
Sent from my SCH-I535 using XDA Free mobile app
NoCrAppleHere said:
YES!!! Long live the GS3... ?
Click to expand...
Click to collapse
Agreed!
Sent using Tapatalk
Master Cylinder said:
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1
Click to expand...
Click to collapse
A link or two would be a great addition.
Thanks for the thread!
phonetool said:
A link or two would be a great addition.
Thanks for the thread!
Click to expand...
Click to collapse
@Master Cylinder, you can use mine for now.. http://mastamoon.truelinux.net/firmware/ Just note that you have to flash the firmware first, then the modem. Otherwise the firmware, which contains a modem, will overwrite the newer modem.
CyanDelta sounds greate. However, I get FC with it. Reboot does not help.
I'm on 5/13 nightly.
Anyone has the similar problem?
yorkwar said:
CyanDelta sounds greate. However, I get FC with it. Reboot does not help.
I'm on 5/13 nightly.
Anyone has the similar problem?
Click to expand...
Click to collapse
And you downloaded or had a 5/13 build zip to operate from to setup? And you had at least 750mb free space before pushing the zip over or dloading it? Maybe one needs more than that amount space? When did it fc?
When looking at the Google Apps linked above, what is the difference between arm and arm64?
Sent from my ME173X using XDA Free mobile app
XdrummerXboy said:
Would it be a good idea to link the old thread in the OP? I can understand both sides, including it or leaving it out, though.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
It's a good thought. Hmmm.... In 2 weeks this will have 15 pages and probably no need to go back, but I'm certainly still open to it if others want it.
phonetool said:
A link or two would be a great addition.
Thanks for the thread!
Click to expand...
Click to collapse
mastamoon said:
@Master Cylinder, you can use mine for now.. http://mastamoon.truelinux.net/firmware/ Just note that you have to flash the firmware first, then the modem. Otherwise the firmware, which contains a modem, will overwrite the newer modem.
Click to expand...
Click to collapse
Thanks masta. Yeah, I was contemplating putting up Dropbox links (was a little blurry eyed last night.) I just remembered Invisiblek still has some up. Also, I guess I could put up Google Drive links which are never gonna go away....
brandonb0013 said:
When looking at the Google Apps linked above, what is the difference between arm and arm64?
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I knew I'd left an unanswered question there. They just started listing them this way. Use the 'arm' which is for our phone. I'll update that on the OP, maybe put a little explanation, when I get more coffee in me... :silly:
Yeah I knew I'd left an unanswered question there. They just started listing them this way. Use the 'arm' which is for our phone. I'll update that on the OP said:
Great. I love how everyone is quick to answer any questions people have. That's what makes flashing so enjoyable. Anywho, when I do my next flash, I'm going to try using those linked gapps. Changing of it fixing my BT crashes? Probably slim to none. But it's worth a shot!
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
1 vote to link both earlier threads
Would be good to link MM's and amf66’s Invisiblek threads. There's a lot of info and the Cm12x development progressed very quickly, so most info is still fairly current.
But then, I minored in history, sooo....
XdrummerXboy said:
Would it be a good idea to link the old thread in the OP? I can understand both sides, including it or leaving it out, though.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
AyUaxe said:
Would be good to link MM's and amf66’s Invisiblek threads. There's a lot of info and the Cm12x development progressed very quickly, so most info is still fairly current.
But then, I minored in history, sooo....
Click to expand...
Click to collapse
The speed of progress is what makes those threads age so quickly, but for those of you who are sentimantal, and to afford worthy applause to @mastamoon and @invisiblek, I've put in links.
"Another Note: CM12 was introduced to our phone first by mastamoon and Invisiblek: Many thanks to them! There may be data on those threads that can help someone, so I've included those links for reference:
Mastamoon's Unofficial CM12 (and cm11) thread.
Invisiblek's Unofficial CM12 thread by amf66."
Links work there.
OK, gonna try a clean install with the gapps in the op. Try not to restore from titanium as much as possible. This last install I had bluetooth problems and lost count of the restarts whether charging or not. See how this goes.......
stevet86 said:
OK, gonna try a clean install with the gapps in the op. Try not to restore from titanium as much as possible. This last install I had bluetooth problems and lost count of the restarts whether charging or not. See how this goes.......
Click to expand...
Click to collapse
What kind of bt issues? Bt share has stopped? Also, i never had issues with reboots on any flashes I've performed. Only issue for me is bt.
Sent from my ME173X using XDA Free mobile app
Why no updates since the 18th?
Shakes The AssClown said:
Why no updates since the 18th?
Click to expand...
Click to collapse
Yeah, it's been a few and there's a lot of commits piling up but he did put out builds for 17 days in a row so I guess we got to cut him some slack.
brandonb0013 said:
What kind of bt issues? Bt share has stopped? Also, i never had issues with reboots on any flashes I've performed. Only issue for me is bt.
Sent from my ME173X using XDA Free mobile app
Click to expand...
Click to collapse
I have to go into the Bluetooth settings and manually connect my headset whenever I turn it on. I can see it there but it never connects until I select it.
stevet86 said:
I have to go into the Bluetooth settings and manually connect my headset whenever I turn it on. I can see it there but it never connects until I select it.
Click to expand...
Click to collapse
Hmm. Mine always connects, just shuts off randomly. Let me know if it helps. I see the next nightly is quite extensive but so far no BT changes. I plan on trying it though
Fyi, I'm going to go into rehab soon bc I'm having nightlies withdrawal. ???

Categories

Resources