yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] #000000:
Hi bros, just wanted to warn you, last build + dkp for MM caused me random reboots, and after I wanted to reboot to recovery just to reflash and it just didn't, neither back to ROM.

Strange, but I flashed recovery via ODIN, and ROM booted up back.

Idk , maybe it's just my case.

Plus WiFi was droing from time to time, and apps were crashing on pressing back key. Md5 was equal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anil2653:
I also tried to install this Rom and DKP but it was not even booting and stuck in bootloops but I was able to boot to recovery and working perfectly with inbuilt kernel.

Therefore I feel DKP doesn't support for this Rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
I tried two kernels, Shift 4.0 and I believe DKP as well. DKP wouldn't flash, Shift did, but wouldn't boot. But I had to actually switch back to 12.1 nightlies after having issues sending/receiving texts. I had to call my voicemail to refresh my service every time I wanted to send or receive, however now that I'm back on the nightlies that issue is back. It's weird to me, because I updated to 12.1 to fix those problems in the first place. Then to Oct-M to try and get Bluetooth working correctly again, and text issues came back. I basically have to pick what issues I want and don't want and go with it lol any other reasons this could happen? I'm on NJ2, so I know I'm as up-to-date as I could be. Should I reflash the modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Hey guys, I run DKP with OctOS all the time, have since LP. DKP works flawlessly on Oct-L & Oct-M. "However"... The newer builds aren't working with DKP. We'll have to wait for DKP to be updated again.

---------- Post added at 02:40 AM ---------- Previous post was at 02:37 AM ----------

I'm not having any of those issues on my d2att. I'm running NJ2 as well. A reflash of the modem shouldn't hurt anything. The only issue I've noticed is after a reboot I have to toggle airplane mode to get data to kick in. Not every time but almost.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Is your service usually very weak before the airplane mode method? I notice that when I call, I go from 1 bar to full once the call connects. Either way, once Oct-M is stable enough for Xposed and everything I use to get me comfy, I'll be switching right back over. Aside from the texting issue(which seems may just be the phone)and not being able to have my kernel, I had the best battery life, and I could fibally listen to my Bluetooth headset. I was happy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Oct-M works well with Xposed... thankfully!

If Oct-M is not working the way you want, you really shouldn't have any trouble with the final build of Oct-L known as M6. It is running flawlessly for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Not really, whenever I place a call or receive calls the signal drops from LTE to 3g or H+ but that's supposed to happen as we don't have VOLTE. We are working on the ROM & trying to get features back from LP so it'll get better with each update! Stay tuned ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Is it? V79 wouldn't play nice with it for me. I heard v78 was a bit more stable, but it seemed like there were mixed reviews with that theory.

---------- Post added at 08:00 PM ---------- Previous post was at 07:51 PM ----------

Will do! I already have the downloads page of the website bookmarked lol I did want to make a suggestion of using different colored Mr. Octo's instead of different colored droids in your version of the easter egg. Flying tentacles just sounds more fun than flying droids :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
v79 worked well for me with M. v78 works well with L. I'm currently using v79 with L which is also flawless. Actually, every now and then the screen will dim but not turn off. It is in a frozen state. Tapping the power button once fixes everything. I'm not sure if that is caused by Xposed or something else. This behavior occurs about once every other day. Not frequent enough for me to take the time to hunt down the cause.

What problems did you have with v79 on Oct-M?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Oh I didn't even get it flashed successfully. It told me it was successful but put me straight into a bootloop. My phone would actually half-ass bootloop with just Oct-M and GApps. It would get up to the boot animation, shut off, and reboot perfectly fine after. It made me much more wary of flashing anything to it. Alas, I tried anyway lol I ended up having to re-flash Oct-M a number of times and starting from scratch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Did you use the aroma installer for OpenGapps? For some reason, it does not work with Oct-M on my device but it did/does work perfectly with Oct-L. I had to use the micro package to get Oct-M to flash properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
No, I didn't, I've never tried Aroma, personally. I do have the material theme for twrp, not sure that really makes a difference though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I've heard of folks having problems with a themed TWRP but I don't know if that is what caused the problem in your case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Same here, but I haven't seen the themed TWRP do anything different than non-themed. It does have an option to use Aroma installer as a file manager, but you still need Aroma installed, and I don't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
All right here, it's been 2 days since Ive flashed the lastest weekly of Oct-M. I am already impressed by the stability of this build so far! Im running this baby as a daily and it only crashed twice! ?

Just wow!

But as well, new OS means new bugs. Here's a list of bugs that I've encountered since then. Canodroid, if you need any catlog of any of these bugs, just mention them right away, Ill send them straight to you!

So, here it is:

-Quick settings tiles editing: crashes as soon as you press the "+" button.

-Quick settings weather panel: doesn't shows up when enabling the option.

-Quick settings reset to default layout: not working at all.

-Bluetooth incall: phone's having a hard time switch the voice through a bluetooth device (been testing with a RK300 helmet) while this device is already BEFORE taking the call.

However, if you turn off the bluetooth function and the helmet while being incall and turn it back on, it works.

-Data connection: happens from time to time simply connect on his 3G/LTE network. Simple workaround would be to turn on & off the airplane mode as it was already mention above.

To identify the phone, it's officially a D2CAN running as a D2ATT. It's an unlocked phone going through Koodo network. And also, it's on the I747MVLUFOB1 baseband.

Before I end up this post, I've got to mention the positive marks!

-Facebook video playback doesn't bug anymore!

-The entire OS feels more faster than the LP one!

-Quick settings action tiles has swiping pages now!

No ****, I just can't ****ing wait to see the stable version already!

Hopefully, my post was helpful for you, Canodroid!

And keep up the good work! Im really loving! ???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] #000000:
There are some issues, but no need to reflash. It's only Android related. They exist on matrix one's builds cm13. Some of them will be fixed when CM team will deal with them.

Yesterday I was hardly able to boot even to download, it was refusing to boot. But it's okay now

---------- Post added at 12:19 PM ---------- Previous post was at 12:12 PM ----------

May be it's just device related.

I was able to boot, but it started to reboot unexpectedly.

I tried to boot to recovery, and it didn't and to rom also. I'd like to say that it's was difficult to even get to download. I mean it was starting to boot, 3-5 seconds, vibration and then bootloop. And strangest that after I flashed recovery it started to boot normally to rom + every time I was inserting battery it was trying to boot. No matter how long it was without it.

Edit 3

Odined again! Flashed to OctOs last lp build.

Edit 4

Managed to fix it. It was hardware issue. It's okay.

But don't flash dkp until it will be updated (should highlight than thus kernel is awesome battery saver) ! Or you will be bootlooped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
How can I turn of the notification light under "do not disturb"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Hello all

I am still running a Samsung Galaxy S3 (with SlimKat 4.4.4) -- I have had this ROM on for ages, as being an older version. It is CM11, and has been running really nice to be honest. I thought today I would come and check out XDA and see if my S3 is still being dev'd for and noticed this ROM here, CM13 Marshmallow!! I thought wow, awesome. I think the S3 is still a FANTASTIC phone! I have been using this phone for years being I thought I never needed anything more in the recent years. The hardware is great and CM11 runs OUTSTANDING on this phone.

I have been looking into new hardware in the future (Mainly the S7) but if the S7 doesn't have microSD AND a REMOVABLE BATTERY, I will probably pass on it (two selling features I like) I have been a galaxy fan for ever, never owned another android device but the samsung galaxy series.

Anyways there is my little ramble.... I guess I will get to my question.

How is everyone here finding this ROM to be running on the I747M (SGS3) ? I saw the topic and said to myself YAH RITE! 6.0.1 for the S3!!! I wanted to briefly ask how stable this ROM has been for people using it. I am really tempted to try it. I will be going from Android KitKat 4.4.4 to this 6.0.1

Is there anything I need to know before moving forward ? No bootloader flashing?

No upgrading CWM -- Philz Touch (which I can't recall is still in development... and no I am not a fan of TWRP you like what you like I guess)

I see from the install notes --> --- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---

Is there any reason not to use CWM (or it is just not tested) ?

Just really any insight to this ROM on the S3, I would really appreciate feedback on this matter.

For now, I am going to make a nandroid of my phone and get it prepped up for flash. I will wait for some responses. I hope everyone in this community is doing well. I LOVE XDA.

Thanks again everyone ! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I feel the same way! I'm hoping and praying Samsung returns to its roots and makes the S7 the new and improved S3.

Oct-M runs very well on the S3. Just make sure you have the lastest firmware (NJ2) and TWRP, take a nandroid backup and flash away!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
BOOTLOADER = MVLDMF1

Is there a flashable zip somewhere I can flash with CWM somewhere (NJ2) ? --I saw this, but this is older-- http://xdaforums.com/galaxy-s3-att/general/modem-4-4-2-modems-i747-i747m-t2856577

Is NJ2 Stock bootloader ?

Sigh I really don't want to flash over to TWRP (I like my CWM) lol

And yes, nandroid already made (while doing rom research here today)

I may just flash Oct-L being it is listed as stable, and that's what I need most is stable. I am on 4.4.4 which has been fine, just thinking time to update... I really want to try Oct-M but reading through the posts here, seems issue-ish (CM is though)

I even tried CM13 on an S5, what a horror show, went back to a TW rom (user needed a stable phone)

Suggestions / Opinions ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
Hey there, I'm glad I found this. Slightly new to XDA, so I like being able to see a post I can actually answer :P on the stability note though, I had it flashed on my I747(US AT&T version) and it worked amazingly, aside from issues I started to get. If it makes you feel better, said issues have followed me to official CM12.1 nightlies, so I'm 98% sure that it had nothing to do with Oct-M. I personally use TWRP, so I can't speak on CWM compatibility, but I do know that TWRP is more up-to-date for the S3 once moving past KK. You would definitely need to update the bootloader, and if you search XDA for "s3 update" it should be there somewhere, I know I got my copy of NJ2 bootloader from here, I just didn't sub to the thread(I'll search for it and link it when/if I do). Currently, every version of MM on the S3 is unofficial, CM hasn't rolled out that update, but are hard at work on it. The d2vzw already has official 13 nightlies, so it shouldn't be too long. If you're looking for pure stable, I'd stick with the Oct-L build, as there's been a lot more work making L more stable on the S3. However, I'm subbed to this thread so when a more stable version is released, I can get my hands on it right away. Definitely worth the wait.

---------- Post added at 01:52 PM ---------- Previous post was at 01:24 PM ----------

http://www.sammobile.com/firmwares/database/SGH-I747M/

This might be what you need. I don't see a 4.4.4 firmware, but I do see bootloader going up to OB3, which is all you really need. I believe it was Canodroid that helped someone else out on this thread recently who needed to update, so some of that info is a few pages back. Simple stuff, like flash one at a time, don't skip one, yada yada. Although it also looks as though your carrier is important, so the page linked has a few options. But the bootloader on the 747M are different than 747U, which is what I'm on currently. They're basically the same, but 747M is specific to Canadian carriers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Thanks for the responses

Guess I may need to research how to flash over from CWM to TWRP without issues, as recovery is the most important part of the phone

As for the list of firmwares NJ2 seems to be the latest (AUG 2015) -- which I guess is needed for 5.0 + ROMs if I plan to flash anything that is ...

https://www.androidfilehost.com/?w=files&flid=10522 -- I saw this a few pages back....

Being on 4.4.4 now, if I install this bootloader, would my current phone still boot I wonder (I am thinking it would being the latest bootloader)

Then I can flash over to this rom Otc-M, and if I run into issues and need to nanadroid back . I assume the latest bootloader NJ2 will work with my older builds (CWM Nandroids)

Perhaps I can just flash TWRP.zip from a CWM Recovery --- not sure if that is unsafe, flashing a recovery from a recovery (or if it is going to HAVE to be ODIN from Download mode to write the new recovery on the partition)

I know it IS NOT supported as per OP (CWM) -- I still may try to flash with it. I am trying to see what TWRP does different on the back end when installing ROMs -- if they set different permissions etc, to /system etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
No problem, I've run into many an issue in my short time on android(this phone hadn't been used in over a year before I got a hold of it, so there were lots of old and new things fighting each other, and a lack of updates from AT&T made me update forcibly), so I enjoy being able to help someone out when I can. However, I believe you said you were on a 747M right? The M variant uses different bootloaders, and OB1 is basically the 747M's version of NJ2. I'm not 100% sure what would happen if you flashed a US bootloader on the Canadian variant, but I imagine it would come with at least a few bootloops and a loss of service. 747M also uses different bootloader for different carriers, so Telus would be different than Bell or something. As far as recoveries, I'm pretty sure ODIN is the only way to flash them, but I could be wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Oh I see, OK I didn't catch that it was US bootloader... glad you posted that back

Yes because my CURRENT bootloader I am on now, I needed to updated it I think coming from 4.2 (ish) to 4.4.4 last time I was messing around. I was just going to flash Oct-M or L on my phone from CWM -- on my current bootloader, and just see the result (that's if OctOS will even flash) might error when extracting / installing zip

I kinda get confused with all these bootloaders / variants and what not -- trying to make a solid file set for this

Canadian bootloaded = needed

TWRP = needed

Might just flash rom on current bootloader MVLDMF1 and current recovery Philz_Touch_6.48.4-d2lte, just to try... I don't think flashing the rom and gapps on my current setup would harm anything (the ROM might not run correctly) is worst case I am thinking

I mean not following the OP to a tee, and if I run into issues, I can't really ask for support, however, if issues persist, at least I can flash back to my current build, and start over again ... I am not sure if that's wise, but as long as recovery is in tact, you can do anything you want to these phones :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
I've heard a lot of people using Philz, so I don't think it'd be too big a deal, but you'll definitely wanna be on the latest bootloader. I'm not a Dev, just someone who always tweaks with any computer-like object I get a hold of(its an addiction, I swear), so I'm not 100% sure what'll happen if your bootloader isn't updated, but just from my knowledge, I would guess the ROM won't be able to read the older bootloaders, therefore not being able to give you service. I hear most of the service issue complaints surrounding data and MMS, so texts and calls might work fine? I personally wouldn't skip anything if you want OctOS as stable as possible. I feel your pain on the variants though, especially since this is my intro to android lol but d2lte is usually used to indicate compatibility with any of the lte variants, as I believe there's 5 versions or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Hm I see, yeah I am not sure where to find the most up to date bootloader for the I747M (canadian) --- I wouldn't mind getting on the most current, been hunting around XDA but find mostly older posts with no up to date bootloaders :-/

http://xdaforums.com/showthread.php?p=63829519#post63829519

I noticed this note

Once you are on any of the 4.4.2 bootloaders, from the first to the latest, you can never downgrade the bootloader or modem. You can change between Kitkat and Lollipop roms. There are even Marshmallow roms in development that you can use. Once you are on a Lollipop or Marshmallow rom you can still go back to KitKat rom. If you want to go back to one of the KK roms based on Touchwiz, whether stock or custom, there is often a bit more work involved but nothing you couldn't handle by that time. You can not go back to a stock rom that flashes an older bootloader and modem than is already on your device. If you find a stock image, say NE6, that does not flash bootloader and modem, while you are running OB3 bootloader and modem you are safe to use it. If you are on OB3 bootloader and modem and you flash a stock NE6, or even OB2, rom that includes bootloader and modem you will brick your device.

As of now there is no 5.x.x modem for either the i747M or i747. The custom 5.x.x roms are all either based on CM or AOSP. They will all run on the 4.4.2 bootloaders and modems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
u can update your modem and bootloader by flashing a newer 4.4.2 stock rom via odin.u need twrp to flash octa-m because it's more compatible. and if u don't want to lose your current rom then flash twrp first do backup then do your things if u ain't satisfied with the result u can restore your current rom .. it's not that hard just follow instructions. if u need more help i'm here cuz i'm a i747m user:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Yes, I realize that in regards to backup. I have my backup with CWM (for now)

I think I am going to play around with CWM / and my current bootloader. See how she works. It would have been nice if there was a flashable bootloader.zip rather then flashing back to stock, then forward to this ROM etc.

Going to try with LP first then maybe Marsh. I don't think I will be moving to TWRP as of yet anyways. I'd have to odin to install TWRP, overwriting the recovery. I am not too sure if it is as easy as installing TWRP from a zip withing CWM recovery.

appreciate the help buddy. Good to see you're using M and it seems to be working well for you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
yes it's working well..as for flashing twrp u can use twrp manager from the play store no odin needed.. cwm is outdated and i don't think it'll be able to install any lp or m roms.. twrp is mandatory in this case..for bootloaders u can search for one u jst need a 4.4.2 bootloader and modem and if u install lp or m over a an old bootloader the room will not boot and u'll be stuck with bootloops .. anytime bro :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
[MENTION=4335664]unibombz[/MENTION]

If you are looking for something REALLY stable like before, go get the final build of Octos-L.

You won't be disappointed for sure; it is my actual safe backup ROM in case the weekly had to crash.

Be sure to update your firmware to the lastest before doing so and unfortunately, i guess you might have to consider moving with TWRP.

Hope your Odin.exe file aight far away :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] #000000:
So found a bug in latest weekly.

Theme engine is broken or what? Just won't apply theme even after reboot.

Tried pitch black /chummy devs / any theme.

Thanks for your great work:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] #000000:
But be careful! Install bootloaders and modems only step by step, don't flash very old bootloaders with newest ones. You know what I mean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Socomfort99:
123 nightly is running great.

Only issue so far is theming is broke. Applying fonts works but not style and status bar. I tried a couple up to date cm13 themes and none of them worked for status bar and style.

Thanks for the hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
This rom doesn't install a bootloader I am assuming, I was just going to try LP, ROM on my current config, see if it takes ... If anything it won't install

As well I can't find the latest bootloader for the Canadian variant without flashing a full stock rom with ODIN to get the bootloader changed over, which is a waste of time -- if that's the case may have to look for a different rom or .... just keep what I got, which has been stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] #000000:
I got my i747 d2att not very long time ago.

I was reading tons of stuff. Than i decided to flash bootloaders and modems step by step as they rolled out.

Try to read a bit more or ask for in Help section.

Maybe Odin is the only one way for you.

I cannot lend a hand to in that situation :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
So being on the Canadian model and network, could you post the version bootloader you are on right now ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronpelayo:
Hi we're exactly in the same situation. I'm using I747MVLUFOB1 but I want to update to the latest version which is I747MVLUFOB3. Can I just flash the official firmware directly as PDA on Odin? Btw I'm on OCT-OS M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Hey guys, the theme engine is broken across the board on all supported devices with the 1-23 weekly build. We're working on it & should have it fixed by the next build! Thanks for the support fellas! ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MatAccord:
That's how I did on mine. But just to be sure, wipe off the phone via TWRP to be sure to start off a clean plate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronpelayo:
So can I flash directly on Odin without following the bootloader version in order?

Can you please tell me on how to flash it via Odin and how to root my phone again.