yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Wrathfulweasel:
The thing is, I don't need to update- I need to first root my phone. This update requires an already-rooted phone. Also, I don't need to update my phone.

Thanks for repsonding though!

EDIT: Wait, are you saying that I should first root using Kingroot, and then update to 1337_OC4?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jack_ssl:
No , Downgrade I337UCUFNB1_Rootable_Full_Odin : https://www.androidfilehost.com/?fid=23501681358548937

And Download I337_OC4_Stock_Rooted_ROM

https://www.androidfilehost.com/?fid=24052804347800728

If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+), root with Towelroot, then proceed with the above process.

https://www.androidfilehost.com/?fid=23681161096070831

Then Install FlashFire ... Give Root Permission

Attention! Set your screen timeout to 10mins before beginning!

1. Place the ROM onto your device (use either internal or ext-sdcard).

2. Open the FlashFire app and "Agree" to the Terms and Conditions.

3. Press "(+)" twice to bring up the "Actions" menu.

4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.

5. From the main menu Uncheck all options under "EverRoot" and set Reboot setting to "Download."

6. Press the lightning bolt then "Ok" to begin the flash.

7. Once the flash is complete and the device reboots into "Download" mode, flash the I337_OC4_Bootloader using Odin's PDA/AP slot. Done!

The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for about 1 - 2 minutes (15 - 20 mins for DeOdexed version) before completely rebooting. Done!

Tip: for blazing fast speed turn off animations from Developer Options and reboot!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Wrathfulweasel:
-_- I don't get it

:| Did I mention that I'm a noob too? I rooted a phone once before (Samsung Galaxy Mega GT-i9152) and it wasn't this complicated for me... and does this bypass Knox? Thanks for responding to me so fast though.

The thing is, I don't understand what its saying...

EDIT: Okay, I see what's going on now. I can't root directly from 5.0.1- need to downgrade.

http://xdaforums.com/galaxy-s4-att/help/help-rooint-galaxy-s4-5-0-1-t3235410

That link is a thread in which an answerer answered the question with two links. Its a two part process to rooting the 5.0.1 Android.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Wrathfulweasel:
Ah ha

I would just like to say I understand it now. Thanks! :)
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] XavierAD:
Exactly what I was looking for
[Verizon Samsung Galaxy S III] Stealth111:
For Future Use

First
[Verizon Samsung Galaxy S III] Stealth111:
For Future Use

Second
[Verizon Samsung Galaxy S III] Master Cylinder:
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)

And thanks a million for starting this thread!!!:good::good::good:
[Verizon Samsung Galaxy S III] Stealth111:
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone! :)

I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..

Stealth111
[Verizon Samsung Galaxy S III] Master Cylinder:
Thanks. I also misread the notation at OpenGApps, which said that need a "ROM" with the patch to allow Google services permissions. Also, there are some posts I've found about fixing permissions after boot then reinstalling GApps, but I won't post that here in case it misleads. I'll be the guinea pig as I've dloaded and backed up and ready to jump out the window!
[Verizon Samsung Galaxy S III] Ghost Protocol:
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM. :D

I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:

Error 404: Server be all like

Am I doing something wrong? If not... What next? :confused:
[Verizon Samsung Galaxy S III] Doctorimpossible:
I just finished booting it. It seems pretty nice, and I only noticed a few things. The boot time was around half an hour as usual with lollipop. I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
[Verizon Samsung Galaxy S III] Master Cylinder:
Yes, [MENTION=1782878]Stealth111[/MENTION] you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.

Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip

On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.):(
[Verizon Samsung Galaxy S III] Doctorimpossible:
I also can't access the camera even after installing a new camera app. A new file explorer took care of my sd card issues however.
[Verizon Samsung Galaxy S III] Stealth111:
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..

[MENTION=6567834]Doctorimpossible[/MENTION], glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
[Verizon Samsung Galaxy S III] Ghost Protocol:
So is this a hit or miss when flashing or not? :confused:
[Verizon Samsung Galaxy S III] Stealth111:
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
[Verizon Samsung Galaxy S III] Master Cylinder:
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.

Of course! It's the first unofficial build for us.
[Verizon Samsung Galaxy S III] Doctorimpossible:
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
[Verizon Samsung Galaxy S III] Stealth111:
Here is the MD5 from my file if it helps!

192BD2F6A83BCA791E0AFE9570134058

:)
[Verizon Samsung Galaxy S III] Stealth111:
Yuppers! :) Exposed for Android 6

Thanks for the report!

Fingers crossed for Master Cylinder!!
[Verizon Samsung Galaxy S III] Jaws4God:
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.

thanks.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Master Cylinder:
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.

Besides, it may even not be a problem if one had done that new method.
[Verizon Samsung Galaxy S III] Jaws4God:
all i rememeber was downgrading from h2 to h1 to get root access.. then flashed CM12.1 on top of that ..

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Fenix2002:
I'm not sure about our device (Straight Talk S968C, everyone) yet, Jaws. So far I haven't heard anyone say they'd tried our device and since it's my DD I'm probably not going to try it until someone else jumps out of the airplane first. =P Since everything else we use is d2vzw, I'd guess this will probably work, but I'm still going to hold off until someone confirms.

If anyone with the ST S3 does give it a shot, I'd be interested to hear.
[Verizon Samsung Galaxy S III] canodroid15:
I'll let you guys know how it goes 2moro.
[Verizon Samsung Galaxy S III] Fenix2002:
Thanks cano, I'm just not confident enough to test with a DD, despite having flashed my phone more times than I can remember.
[Verizon Samsung Galaxy S III] Master Cylinder:
Thanks Fenix2002. That's right, Jaws4God, I was referring to d2vzw. Now I see that in your big image sig, not that I would've known what it meant until Fenix2002's post, though.:eek:
[Verizon Samsung Galaxy S III] Droidriven:
No, you have the ST S3 s968c, the firmwares in this thread do not work for us, they are for the Verizon i535. you only want the ROM here, the firmwares will brick the s968c.
[Verizon Samsung Galaxy S III] Fenix2002:
I thought that was the case, but was unsure. Have you tried this build yet, [MENTION=5691352]Droidriven[/MENTION]?
[Verizon Samsung Galaxy S III] Droidriven:
Not yet, flashing it when I get home from work though. [MENTION=1782878]Stealth111[/MENTION] PM'd me yesterday evening that he has his OP up but I was busy doing other things and didn't get around to flashing it last night.
[Verizon Samsung Galaxy S III] Master Cylinder:
I've tried every trick I know (which probably ain't that many) and I get the same result. The ROM at first recognizes my SIM, then it doesn't and com.android.phone fc's continuously and that's it.

I used 3 different modems, reflashed the firmware, pulled the SIM, clean flash of course, reinstalled again and again, checked the files md5, loaded it this way and that, with or without GApps - nada. I used Voodoo, burned incense, prayed and held my left foot off the ground, nuthin'.

PS - also tried on 11/16 build without success.

:confused: :crying:
[Verizon Samsung Galaxy S III] Ghost Protocol:
REF: Twenty Four (24) Hours After with CM13 ROM.

Hello Everyone.

I jumped into the fire and tested the "UnOfficial CyanogenMod 13" ROM. Below are my experiences with this new ROM and I hope it helps the OP and others that would like to try it too.

I actually backed up my external SDCard to the computer, but of course backing up my important 'stuff' to the SDCard first.

Moved/Copy what I wanted/needed to the SDCard.

Booted into Recovery and Wiped "Dalvik Cache, System, Data, Internal Storage, Cache, and Micro SDcard" three times.

Did a "Factory Reset" three times.

Flashed CM13.

Flashed the AROMA NANO GApps 6.0 package.

Then restarted the phone, to load the new OS.

It loaded faster than expected. Especially after reading other experiences where it took thirty minutes or more.

I allowed it (the phone) to sit for a minute before beginning the setup process. The issues I encountered are listed below.

Had issues recognizing the external SDCard. Depends on the task trying to accomplish. I had to install a third party App like "ES File Explorer" to assist. Could not backup my SMS using "SMS Backup & Restore Pro". Well, it kept failing to backup.

I could receive text messages, but when sending a text message it would show an error like it was not able to send. The receiving party received the text message even though I kept getting the error not sent.

Cameras DO NOT work. Not to mention one does not come installed with the ROM either. I tried Snap and a Better camera.

At times it seem that many things was running in the background, because the OS would run sluggish.

Well, I listed the most noticeable issues that I have encountered. I believe with time, testing, and patience it will grow into another great AOSP ROM. Also giving us another reason to stay with the Samsung Galaxy S3.

Thank you,

~ Ghost Protocol :highfive:
[Verizon Samsung Galaxy S III] Droidriven:
Hmm....methinks I'll wait before giving this a try, I'll try it when there aren't so many kinks in it. Can't wait to try M though.
[Verizon Samsung Galaxy S III] Fenix2002:
**First things first: thanks go out to everyone who had a part in releasing this!**

StraightTalk/TracFone SCH-S968C/d2tfnvzw

Just flashed (11/17/15, 1:06am EST), still testing and messing around. Seems good so far. There's a small lag every so often, but not noticeable over some of the less-stable CM12.1 builds. Will keep you updated as I use it. I am confirming that on my device, it works. YMMV

INFO:

Build - 11/16

Recovery - TWRP 2.8.7.0 (d2vzw)

Install - Clean - Factory Reset (data, cache, dalvik), wipe System, Factory Reset, Factory Reset

GApps - gapps-5.1-arm-2015-07-17-13-29 from CyanogenMod/CGApps [Yes, I know it's an LP GApps. It works flawlessly so far. It just happened to be the package I had on my SDCard at the time, so I gave it a shot. Play Store works, haven't tested else. Haven't managed to get a clean download of openGApps for 6.0 yet. **EDIT: Play Services attempts to update, and begins crashing repeatedly, like a child on a sugar high**]

DEVICE:

SCH-S968C/d2tfnvzw [StraightTalk/TracFone MVNO version] for SCH-I535/d2vzw

Firmware - H1

Process:

Download CM13

Copy everything from internal to external to computer via USB (originals left intact)

Move CM13 to external SD

Reboot to TWRP

Backup current ROM

Clean - Factory Reset (data, cache, dalvik), wipe System, Factory Reset, Factory Reset

Install CM13 and GApps 5.1 back to back

Reboot (boot took about 3 minutes for a minimal GApps package)

Enjoy.

Thoughts/Issues so far:

Linux recognizes that phone is connected, but won't allow access to internal or external.

SDCard is recognized internally, CyanogenMod File Manager can't access SDCard, but you can access it by going to Storage&USB in settings. Not very pretty, or useful, though. I imagine setting it up as internal storage would allow it to be accessed by File Manager, although I haven't been brave enough to try it.

No camera app packaged with ROM, and third-party (Google Camera and Open Camera) can't connect to camera.

Voice/Data work (I have the SMS issue. Outgoing messages say failed, but go through.)

Most functionality seems to be working correctly so far, minus those mentioned above!
[Verizon Samsung Galaxy S III] Stealth111:
[MENTION=6342402]Fenix2002[/MENTION], Thanks for the AWESOME detailed post! I really hope the info helps some people out that may have a similar setup.

PS, Running ES File Explorer will fix the sdcard issues. Plus the program is sweet as well. Lots of nice features. I use it to backup my apps to local apk files, as well as a few other cool utilities it has built in. :)

Stealth111
[Verizon Samsung Galaxy S III] Droidriven:
As far as file managers go, you can't beat ES file explorer with a stick and two dudes holding it down for you, lol. I've used some with some cool features that ES doesn't have but they weren't as good all around as ES is. There are just too many features about ES file explorer that make it extremely valuable to power users.

Even the most experienced of us will probably never use all of its features.
[Verizon Samsung Galaxy S III] Z3R000:
Could this work for the us cellular s3?
[Verizon Samsung Galaxy S III] Deliquified:
Root Explorer is my go to. Simple, clean, powerful.
[Verizon Samsung Galaxy S III] toosurreal01:
Runs really well.

Biggest issue for not being a daily driver for me is the fact that no camera will work.

Also, SMS messages say they weren't sent, but they still send. MMS work fine.

Hopefully they get that ironed out soon and I'll return :)
[Verizon Samsung Galaxy S III] Fenix2002:
I've tried ES File Explorer and a bunch of others, they work pretty well.

Do we have any ideas how to fix the camera issue, even as a temporary fix? That's really the biggest issue standing in the way of using it as a daily driver, IMO.
[Verizon Samsung Galaxy S III] Master Cylinder:
This is the same thing that happened within the first days, weeks, (months?) of the Lollipop builds. Camera must be the hardest thing to accomplish across devices.
[Verizon Samsung Galaxy S III] Droidriven:
I think I read somewhere that Samsung won't release the source on stock camera so in the custom ROMs it has to be made from scratch, this makes things very difficult.
[Verizon Samsung Galaxy S III] Deliquified:
Yup the camera stuff is proprietary so it has to be hacked together with each new major android release.. It took about 2 months to get the camera working on LP.. What worries me is that with very few devs left working on the S3, who will be the one to get it working?
[Verizon Samsung Galaxy S III] Fenix2002:
If I knew anything about it, I would attempt it. But my knowledge on stuff for the camera stops at copying libs from ROM to ROM, and I'm not sure if that ever even worked.

I don't really have the capability to build & compile ROMs currently, but I can definitely look at source code and see if I can connect the dots and maybe come up with something. Just a thought. Maybe if I can do that, someone else could put it into a new build?
[Verizon Samsung Galaxy S III] Droidriven:
I would imagine that the camera can't necessarily get fixed in CM upstream because of the range of devices, I would think that it has to make things difficult because it probably can't be fixed in a source that all the devices can use. Does it come down to it having to be fixed in each individual devices source in a way that can't be shared with another device even at its base code?
[Verizon Samsung Galaxy S III] canodroid15:
Pretty much ?
[Verizon Samsung Galaxy S III] Fenix2002:
[MENTION=5691352]Droidriven[/MENTION], [MENTION=5806583]canodroid15[/MENTION]

Yeah, that sounds right to me. My next question is more because I've never fully built CM from source, although I'm currently syncing with the repo, but who knows if it will ever finish on my Dark Age internet..

Anyway, in the steps to build CM, there's "Extract proprietary blobs" using the extract-files script. If you grab the proprietary blobs from a ROM with a working camera, would that get the camera fixed, assuming the camera blobs are included in that script? [If not, I'd imagine you could probably modify the script to pull in any additional blobs, or modify it to suit what you need.]

Just a thought, and probably more ignorance than is good for me.. but I'm trying to be helpful and learn to successfully build along the way.
[Verizon Samsung Galaxy S III] Deliquified:
With every new Android release, the camera is almost always the last thing to work on the S3 and has been hacked together from the beginning. If I'm not mistaken the libs are proprietary and can't just be copied over or it would of been done already through the last few releases from kitkat onwards. When LP released it was a solid month or two with a couple different devs working on it before we even had a semi stable working camera state. If i recall correctly, the stock camera wouldn't work for awhile and we had to use other apps for a few weeks even after they had some solid code
[Verizon Samsung Galaxy S III] Master Cylinder:
Oh Baby! Munchin' on some Marshmallows now!! 11/18 went on without a hitch. [MENTION=2385005]invisiblek[/MENTION] is kickin' butt n' takin' names! Now trying to get this weird external SD card situation squared away. /storage/50AF-33E0? Okay. Maybe some symlinks might come in handy. :cowboy:
[Verizon Samsung Galaxy S III] Jaws4God:
for the ones who are trying M6.0 how is battery life with Doze?

any other advantages over Lollipop?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] thelangosta:
Yes, the way the external storage is handled on 6.0 takes some getting used to. Mine shows up as a series of numbers in ES file manager and [External storage] in titanium. It still works just fine but I'm on a different device with a different 6.0 rom. I might just flash the latest build from invisiblek on my old s3 for fun. It doesn't need to have a functional camera, GPS, data, etc. As long as WiFi works and the netflix works my kid will be happy.
[Verizon Samsung Galaxy S III] Deliquified:
Cm13 builds seem to be 40mb+ bigger than cm12 builds.. What causes them to be significantly bigger?
[Verizon Samsung Galaxy S III] Master Cylinder:
I noticed - probably NSA spyware... :p

[MENTION=1801772]Jaws4God[/MENTION], as far as advantages or LP, it's a little new on mine. I've had to go back to lolly to have functions I use a lot. Some of my apps that access the external SD card aren't functioning. I'm just booting up 11/20 and gonna see about finding a way to mount /storage/sdcard1 in an init script - just for fun. I've been playing with symlinks and getting mixed results, but still exploring. I could probably mount it easy enough - gonna give that a try when it's ready.

Of course this is real early days and Lolly is a fully developed ROM at the end of it's development cycle with CM, though they are still pushing out builds nightly. I noticed that 11/12 had a huge commit list but since then barely a trickle. It won't be long before all those Cats all over the planet hacking away in the dead of night turn their entire attention to Mr. Stay Puft. :silly:
[Verizon Samsung Galaxy S III] Stealth111:
My battery life on 6.0 has been phenomenal! :) YMMV

***IMPORTANT INFORMATION*** If you are going to flash to cm-13.0-20151121-UNOFFICIAL-d2vzw or later build, there have been some database changes. InvisibleK has provided a flashable zip file to accommodate nuking your old telephony and settings databases. Nandroid or backup files as needed if you want, as I seem to remember doing this with CM before, and clearing the database wiped texts and call logs I believe. This only needs to be done 1 time, the first time you flash any build from 11-21 on. After you have done this once, you are good to go moving forward, you will be upgraded to the new databases. If you do not flash the "Nuke_It" zip file, you will get phone FC's and a "No SIM Card" error message. So whether upgrading, dirty flashing or whatever, reboot into recovery, flash the ROM, and BEFORE you boot, flash the following zip!

Nuke IT Database Wiper

Profit! :)

Stealth111
[Verizon Samsung Galaxy S III] Shakes The AssClown:
This sounds awesome. I'm gonna wait a little more just till the camera and other minor bugs are worked out. Great job guys!!
[Verizon Samsung Galaxy S III] Fenix2002:
[MENTION=1782878]Stealth111[/MENTION]

Just wondering how this database change will affect S968C users, or if it will? What exactly is a database change?