-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD
So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Do these include google now, if not where can I get it?
ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.
ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)
neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III
TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:
XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Can I use TWRP recovery to flash this Rom?
TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.
neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6
WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.
Related
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
pplayz18 said:
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
Click to expand...
Click to collapse
Which CM10 build are you using? It's my understanding that on the current build of the official CM10 NFC is not yet supported. This could be the case on the unofficial ones as well but I'm not sure.
Relentless D said:
Which CM10 build are you using? It's my understanding that on the current build of the official CM10 NFC is not yet supported. This could be the case on the unofficial ones as well but I'm not sure.
Click to expand...
Click to collapse
A nightly unofficial one released last night. 3.0.39
The only thing that is different about getting GW working on CM10 is you don't need to flash anything (except Google Wallet if you are using the .zip provided by ogdobber) and editing the build prop. NFC is currently broken on the newer CM (and all others based off of CM code) for the time being but I would imagine it would be fixed after the main bugs are all squared away.
The last unofficial build I that had NFC working was InvisibleK's 8/13 but that was before the recent MMS or RIL fixes.
Marcismo55 said:
The only thing that is different about getting GW working on CM10 is you don't need to flash anything (except Google Wallet if you are using the .zip provided by ogdobber) and editing the build prop. NFC is currently broken on the newer CM (and all others based off of CM code) for the time being but I would imagine it would be fixed after the main bugs are all squared away.
The last unofficial build I that had NFC working was InvisibleK's 8/13 but that was before the recent MMS or RIL fixes.
Click to expand...
Click to collapse
I figured it out. I was trying to use the same verizon zip file when I needed to use one specifically for aosp roms.
pplayz18 said:
I figured it out. I was trying to use the same verizon zip file when I needed to use one specifically for aosp roms.
Click to expand...
Click to collapse
Do you have a link to get it working?
pplayz18 said:
I don't know if this is a general problem or just me but every time I change the build.prop codes then flash wallet,I reboot back up and the NFC options are gone. Im using the latest cm10 on Verizon's s3. I had wallet working on bean stock rom before this as well. Is there a different method for cm10 or is it just not available yet?
Click to expand...
Click to collapse
if you took the time to read the notes on the release, you would see that it is not supported yet.
Since you did not, now you will likely have a ton of people telling you to read next time.
NFC DOESNT WORK. THEREFORE NOTHING THAT RELIES ON IT WORKS.
Its a piece of hardware, that does not FUNCTION yet.
did you also figure out that NFC doesn't work on any CM10 build yet so it doesn't matter what you flash?
Not to thread jack... but...
It's been quite a few days without any action on this thread and NFC is one thing I'd really like to try out. With that said I love CM10, currently running the 8-27 nightly without any other issues and love it... NFC isn't that important that I'd go back to a TW/Stock Rom for it.
Any word from the CM guys on when/if the rils and NFC functionality will be fixed up? Patiently waiting and love everyone working on CM10 D2VZW! :good:
Flashed the 8-31 nightly and NFC just greys out after ticking the box still. Wake me up when September comes
Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies
I was reading in the official CM10 thread that someone had developed a fix and that it would soon be implemented into the Nightlies
Edit:
http://forum.xda-developers.com/showpost.php?p=30952627&postcount=1317
Fourth Night NightliesFreshly 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
*** Latest Build 10-11-2013 ***
For d2vzw! Note the forum you're in!
If you're as big of a fan as I am of KToonsez's KT747 kernel then you'll be happy to know there is now an updated version.
This is a forked version of KToonsez's KT747 kernel with commits pulled from the CM10.2 branch of the d2 kernel.
Disclaimer: Standard disclaimer goes here. I nor KToonsez are responsible for the actions you take when working with your phone. I've done a significant amount of testing and so have others but situations arise where a hiccup could cause data loss, IMEI loss, or phone failure. You, the flasher, assume these risks. Please make sure you backup/nandroid, use nvbackup, etc.
Note:
It has been reported that this kernel will not work with 4.3.1 ROMs, notably the latest nightlies of PAC-MAN. If you're on a 4.3.1 ROM flash with extra caution. If you find otherwise please alert me.
Branch "currentCherry" (my cherry picking branch) CI status:
Branch "mr2" (KT's 4.3 branch) CI status:
Instructions:
There seems to be an odd permissions issue that we've uncovered. Follow these exact steps so when you boot you'll have working cell data:
Reboot Recovery
Clear Caches
Flash your current ROM
Flash kernel
Reboot
Profit!!!
I'm working on clearing this up. I've verified the above process against mastamoon's unofficial CM10.2 10/07 build.
Download Link:
10-11-2013
A big thanks to shane269 for helping me test this from a bootlooper to working kernel!
Thanks!
KT747's sources can be found here:
https://github.com/ktoonsez/KT747-JB
Visit the official KT747 thread here:
http://forum.xda-developers.com/showthread.php?t=1853816
Visit kt's original, ORIGINAL kernel thread here:
http://forum.xda-developers.com/show....php?t=1756776
Also if you like this kernel then please consider donating to the dev that made it all happen, ktoonsez: http://forum.xda-developers.com/donatetome.php?u=4325945
Previous Builds
10-10-2013
10-09-2013
XDA:DevDB Information
KT747 For D2VZW Cherry Picked, a Kernel for the Verizon Samsung Galaxy S III
Contributors
mikejr83, KToonsez
Kernel Special Features: KT747 kernel with latest CM10.2 commits
Version Information
Status: Beta
Created 2013-10-09
Last Updated 2013-10-16
Change log:
-10/11/2013
* Merged the commit for touchscreen optimizations
* Cherry-picked commit for reverting portions of the touchscreen optimizations which may cause us camera issues.
* Changed updater-script to hopefully resolve issue with no data after flashing (still researching issue)
First?
Looking forward to this
tapped from a carbonized d2vzw
ktoonsez gave the OK. Download link is now up. Please follow the instructions or you'll get no data. If you accidently goof and do this just reflash your ROM and then in the same session flash the kernel.
Thanks!
Mike
Thanks for this I've been using this without issues pacman ROM.
Sent from my SCH-I535 using Tapatalk 2
Just flashed on Slim 1.6 weekly and set my kernel settings. No initial issues, thanks for the update. I was going through kernel flashing withdrawals.
Sent from my SCH-I535 using Tapatalk 4
Well @mikejr83 so far so good, thanks for the update!
sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
mikejr83 said:
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I normally don't overclock my phone doesn't do well with it. I tried 1728 and it wasn't ever using it. Then I bumped it up to 1809 and it instantly rebooted. As expected, my processor just won't do it. After the reboot the phone was still set at 1728 and it was using that frequency. So maybe requires a reboot work?
Sent from my SCH-I535 using Tapatalk 2
Rebooting seems to make it stick or show up in the apps where I see freq values.
Sent from my SCH-I535 using xda app-developers app
OP Updated
Went through my cherry pick branch and realized I missed some commits. I missed about 2 days worth of merges at the end of August. These are now all added.
There is a gerrit reviewed commit for touchscreen optimizations (and a subsequent fix for camera issues). I'm having trouble merging this commit into my branch. I'll try to get that into the build for tomorrow.
Thanks!
Mike
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Rinkle McBally said:
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Click to expand...
Click to collapse
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Are you using CWM? If you are what version?
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
jamminjon82 said:
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
See responses below. Thanks!
mikejr83 said:
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Yep 10/10 for sure.
Are you using CWM? If you are what version?
Yes. 6.0.4.3
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
Yes, all in the same session
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Correct. I'm running android 4.3
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
Click to expand...
Click to collapse
Eclipse build 6
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
^
SAME
New build in the OP.
Also, changelog is in the second post.
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
grislieber said:
^
SAME
Click to expand...
Click to collapse
Thanks for the reports guys. Researching this issue is proving difficult as no one seems to have documented it in the "usual" places. The only suggestion I have so far is checking to make sure the permissions are correct on everything that is flashed. I took a look at a couple of other kernel dev's updater-scripts and tried to modify this one accordingly. Flashing from 10/10 to 10/11's still gave me working data. I'm trying to follow up with a few other devs so please don't think that I'm not working on this. If you flash 10/11 please report your findings!
Thanks!
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Atlantic_Rim said:
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Click to expand...
Click to collapse
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Ok thanks for reply !
Then I think I will wait for the official release, because I want a fully functional version for my moto G
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I know the great job devs are doing for us before the moto G I had a LG optimus L7 and thanks to cyanogenmod I had kitkat on it.
But as far as this phone just came out, I'm asking myself if it's good to avoid my warranty just to have the same version of android ...
(correct me if I say bad words because I have to train my english :laugh: )
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Entropy512 said:
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Click to expand...
Click to collapse
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
i_rnb said:
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
Click to expand...
Click to collapse
There could be risks if you flash an unofficial build from someone who is not at all working on merging a device into CM - they often cherry pick all sort of stuff that causes incompatibilities with upstream to the point where the product really shouldn't be called CM. (I've seen lots of "CM" kangs that had all sorts of extra crap added beyond just doing what is required for device bringup...)
dhacker, however, is an official CM maintainer for many devices, so his builds are the ones that are "on track" for official inclusion.
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK thanks, then I think I will flash the unofficial ROM when I have time
Atlantic_Rim said:
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
Click to expand...
Click to collapse
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Entropy512 said:
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Click to expand...
Click to collapse
Ok thanks for the informations ! After one hour of intense fighting with my computer, I finally unlocked bootloader, rooted, and flashed cyanogenmod I prefer this rom to the stock one, I find it more smooth, and more costumization
i think its ok for daily use. At least i use it everyday.
I posted this question in a couple other places, but no reply.
I have the GPE version of the Moto G, and I want to run the CM11 builds on it.
Will the fact that the GPE version has the ext4 fs on it prevent me from getting these to work?
I know there are recoveries available specifically for the GPE, but will getting the CM11 builds to work be just a matter of changing a few entries in fstab?
And finally, do either of the recoveries allow you ro format /data from either f2fs to ext4 or the other way around?
Thanks/
I've replaced stock Rom (4.4.2 US Global Version) for unofficial CM11 (2014-02-16's release) and for now CM works more stable than stock.
I had few reboots or issue with .flac, in CM's everything is OK, for now of course. Very good stuff even that is only nightly's release.
[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. ???