yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] itiskonrad:
Just FYI, also using an AT&T UCUAMDB s4. Nougat-based roms (like this one) flash just fine, but absolutely no root methods work. Tried all of them. Must be related to the bootloader being locked and having to use Loki. Can get root OR Nougat roms, but can't get both. I don't know of any solution.
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
Is this only an issue with the ATT phones? I have a Canadian model (cause I am one :) ) and am considering flashing but forgot about this whole root side of things.
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
I'm running a jfltecan device and I've been able to root all past builds (haven't tried the exact latest one, still one behind) but I havent had any issues when the others have.
[AT&T Samsung Galaxy S 4 Original Android Developme] itiskonrad:
To my knowledge, no Canadian variants of the Galaxy S4 have locked bootloaders.
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
Ya, I knew that the Canadian version is not bootloader locked but I was just trying to find out if the issue with not being able to root the last stable release of this ROM was the fault of the ROM or the hardware.
[AT&T Samsung Galaxy S 4 Original Android Developme] Rishabh Bhardwaj:
Hi, i am Using samsung galaxy s4 sgh-1337 at&t with android 4.3 on it. I tried to install twrp recovery but my phone got bricked. though i recovered it but still i am not able to install twrp on my s4. But i installed safestrap and tried to flash octos rom and gapps package. safestrap is showing that it is correctly installed but when i am rebooting my phone android 4.3 is coming up. I am very confused please help, you know it is very awkward using jellybean in naugot times.
[AT&T Samsung Galaxy S 4 Original Android Developme] MikeOnX:
I managed to root the last release on the second try. If i remember correctly i just reinstalled everything + SU package without wipe and got root.
[AT&T Samsung Galaxy S 4 Original Android Developme] Tubifex:
I am guessing you are on a firmware version above MDL?
[AT&T Samsung Galaxy S 4 Original Android Developme] MikeOnX:
I haven't used a Samsung Firmware in a long time, that software is crappier than a buggy AOSP or LineageOS rom. I have an International version of the i337 with unlocked bootloaders so I don't get what your issue is. I think that if you have an unlocked bootlader everything else is irrelevant, specially FW version since this is not a FW.
[AT&T Samsung Galaxy S 4 Original Android Developme] Tubifex:
You answered it. I have the ATT with the MDL firmware. Locked boot loader and such. I am unable to root. There was a little hope there but since you are on the international variant we can't compare.
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
Well, I took the dive 3 days ago and all is well so far!

The one weird thing that happened was that when I did the install, I accepted that it would do its own wipes on first flash so I never did anything. When it was done the first boot, all my settings and accounts were still in place! I like this greatly and never encountered any of the classic issues like force crashes, from what feels like a dirty flash.

Thanks to all that contributed to this ROM!!!
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Anyone having crap battery with the release? I don't know if its my battery, but I've barely been getting a day out of the phone where in last release it was just fine.
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
Not here. I occasionally have an app that goes stupid and eats some battery but that has always been a problem on Android since the beginning of time.

Sadly, there is always a point where your battery goes from bad to worse and coincidence is a pain. I can say on the note of bad batteries, they can cause some weird behaviour. My old S3 would look like the screen was in total freakout mode. I thought the hardware was dead, but with it doing the mystery plummet from 50% to almost nothing in only a couple hours, I went with a brand new genuine battery and all was well. My friend who also has an S4 JFLTECAN like mine, he thought his hardware was going bad too. Tried a new genuine battery and has been very happy. He is on stock.

Considering that most S4 hardware is at least 2 years old and as much as 4 years old, I would go with the battery first.
[AT&T Samsung Galaxy S 4 Original Android Developme] droiduzr2:
Use a new battery. I had the same problem.

Dead in 2 hours, drain real fast...It was in airplane mode and all things turned off.
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Just in case Anyone is wondering. LineageOS is still supporting the jfltexx (which works fine on the Canadian s4)
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
I figured it would but I started here first just for the fun of it. I guess the biggest reason to switch to full LineageOS would be to get the security patches.
[AT&T Samsung Galaxy S 4 Original Android Developme] Tubifex:
That is for the international variant. So my guess is that it won't work for the AT&T variant right?
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
I can't say for sure, but I would bet it is dependent on how you ATT(i337) owners have to deal with the locked bootloader. The hardware will work as the only differences between the Canadian i337m and the non-m are the bootloader state and possibly some radio frequencies, but that should be it.

So at the core, if it works on the Canadian variant, it should be fine on the ATT short of the bootloader. Key word "should".
[AT&T Samsung Galaxy S 4 Original Android Developme] Tubifex:
Unfortunately for the US Carriers the bootloaders are locked. My guess is you want to stay away if you have a US carrier variant.
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
If I were American and stuck with that model, agreed indeed.

It is quite strange that there has been no addition of proper support for the jflteatt or jfltecan on Lineage though.
[AT&T Samsung Galaxy S 4 Original Android Developme] Tubifex:
I agree. But I am only using this for a Chromecast remote so having ongoing support and root is not needed. So I have no need to complain. It would just be nice to have both.
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
True. I am just stubborn and don't want to spend money on a new phone when my S4 with Nougat is working awesome :)
[AT&T Samsung Galaxy S 4 Original Android Developme] Tubifex:
It would save me a lot of money if if I was stubborn like that.
[AT&T Samsung Galaxy S 4 Original Android Developme] ItzBluestone:
Could I Flash This With Flashfire?
[AT&T Samsung Galaxy S 4 Original Android Developme] mkoev:
Hello guys,

Coming from the Nexus 5 forum and I've got some questions. I've got a buddy of who owns a AT&T S4 and would like to try newest Android.

I read through the thread and found out several things, kindly confirm.

1. https://dl.twrp.me/jflteatt/ - this recovery must be used. Can you confirm if it is patched properly so I won't see the yellow triangle?

2. After I flash the recovery via fastboot I can go ahead and factory reset phone (do a back up before that);

3. Flash Octo-N;

4. Flash Gapps;
[AT&T Samsung Galaxy S 4 Original Android Developme] SLEVIN_46:
Which root zip are you guys using for the canadian ver.? thanks in advance
[AT&T Samsung Galaxy S 4 Original Android Developme] que3jxp:
So far, nothing at all. I just use Magisk to get around all the Netflix foolishness with the playstore.

I am test driving pure Lineage on my older S3 so I may not be on OctOS for much longer where development for the S4 has stopped.
[AT&T Samsung Galaxy S 4 Original Android Developme] ahurst12:
Helium working?

Has anyone had success getting Helium backup to work with this ROM? The Windows desktop program says it has enabled Helium, but the app just continues waiting to be enabled. I am using the final version of this ROM 20170413 on an SGH-I337 with the MDL boot loader.
[AT&T Samsung Galaxy S 4 Original Android Developme] ahurst12:
Got root working on AT&T MDL

I was able to get root working on the final version of this ROM on the AT&T MDL loki by flashing the addonsu-14.1-arm-signed.zip file from the Extras download area of the LineageOS site using TWRP. You need to make sure root is enabled for both ADB an apps in the developer options after flashing. The root manager is built in so SuperSU app is not needed.
[AT&T Samsung Galaxy S 4 Original Android Developme] nafeel1990:
bro i am currently running 4.4.4 on my SGH-i337UCUFNJ4 can i update to this ROM
[AT&T Samsung Galaxy S 4 Original Android Developme] okbaa113:
How download and installe firmware and ROM Integral root & service Google play stable
[AT&T Samsung Galaxy S 4 Original Android Developme] chemao:
I read through the thread but I didn't find anyone mention if I can run this with Safestrap. Man I want this ROM so badly but I'm one of the idiots that updated and got a locked bootloader. I'm rooted and I debloated but I'm still on 4.4 and all of my banking apps don't work any longer. FML I have a Galaxy S7 Edge that can't be rooted and a Galaxy S4 with a locked bootloader. ****ing Samsung man I'm done with them.
[AT&T Samsung Galaxy S 4 Original Android Developme] exalented:
I feel you bro..
[AT&T Samsung Galaxy S 4 Original Android Developme] gorgy76:
do anyone have working magisk module for this rom?
[AT&T Samsung Galaxy S 4 Original Android Developme] jrdlee:
Cannot flash Oct-N-M1 . . . or use TWRP . . . Any suggestions?

Have a SGH-I337 that is rooted, no subsidy lock with the NB1 (4.4.2) ROM using Towelroot, SuperSU, Busybox, and Safestrap. This configuration runs without any problems. Yeah!

Cannot boot any version of TWRP (including 2.7.1.0 - the version that Safestrap uses). TWRP app installs OK, flash is successful. Restarting results in the message that unauthorized software was detected . . . Attempted 6 different versions of the TWRP .img file for jflteatt without success.

Used ODIN to flash back to stock NB1, then rooting, etc. Then used Safestrap to flash OCT-N-M1, this results in a soft-brick with 3 volumes being unmountable (per Safestrap logfile).

It appears using the rooted NB1 ROM, this device can be updated to Nougat 7.1.2 or Marshmallow 6.0.1. Is this true? If so, what ROM(s) were flashed and with what bootloader (stock, Safestrap, TWRP)? I'm trying to update to the highest possible Android version that is stable. Next will be attempting to install the RR 5.7.4 build to see if this sticks.

Any suggestions would be greatly helpful and appreciated!
[AT&T Samsung Galaxy S 4 Original Android Developme] jabulon:
Call recording

Have anyone successfully recorded calls on Oct-N? None of the apps and their methods works for me - the other side is never recorded, only mine.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yes, apps can write to external SD card. It works.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Hey GTA, you planning a release this week?

Edit: sorry, I found the weekly. I thought that you always announced it. My bad.

Back button long press to kill not working for me in the 02/03 weekly. Verify anyone?
[AT&T Samsung Galaxy S 4 Original Android Developme] manfromgta:
I usually do announce it. Sorry about that. OTA is built in now. You can check for updates there. Friday will be another weekly.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Do you use the back button to kill?
[AT&T Samsung Galaxy S 4 Original Android Developme] canodroid15:
I do, are you having issues with it? I assume you mean long press back to kill?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yes, it doesn't kill for me on the latest. On 1./27 it works fine. Is it working for you on this weekly?
[AT&T Samsung Galaxy S 4 Original Android Developme] cantenna:
anyone manage to get video camera to work?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Hmmm... No, not working here. Was working on previous builds.
[AT&T Samsung Galaxy S 4 Original Android Developme] canodroid15:
Actually, no its not. Thank you for bringing it to my attention ;)

---------- Post added at 10:53 PM ---------- Previous post was at 10:52 PM ----------

(The kill app back button)

We will look into the camera issue but it looks like an upstream issue with LineageOS. Could you guys try Google camera & let me know how it goes?
[AT&T Samsung Galaxy S 4 Original Android Developme] cantenna:
Did some googling, you can install ucam from Play store for camera/video record functionality in the interim.

Great room dev! Can't beleive S4 running Nougat very well:)
[AT&T Samsung Galaxy S 4 Original Android Developme] TheShamus:
Thank you manfromgta and macwindows,

Noobie here. I have stock FIDO ROM but if I understand the steps to install Oct-N I need to:

1. Use Odin to install ATT stock ROM 4.4.2 from StockRoms.net (Sammobile free d/l server down today)

2. Use Odin to install auto root for jfltecan

3. Use Odin to install TWRP for jfltecan or use Android app

4. Flash recovery Oct-N and favourite Gapps.

Seems to me since the hardware didn't change the auto root and TWRP will always be for SGH-I337M. We are just installing ATT stock as the base since Oct-N is essentially an upgrade from that. So far I haven't bricked my phone on any of the custom ROMs I've installed but they've all been designed for SGH-I337M up until this one. And I get why we wouldn't need to edit the updater-script once we've changed our phone to stock ATT.

Well if I missed a step or lost some logic I'll either brick my phone :silly: or manage to get the custom ROM installed. If I brick my phone then I buy the Oneplus 3T. If I figure this out I can wait until Oneplus 5 is released. I'm too cheap to buy the S7 or S8 anymore.

Cheers,

TheShamus (otherwise know as the maneastofGTA)

UPDATE: I definitely overthought what macwindows said he did. Odin wouldn't install the stock custom att ROM...probably a very good thing. Literally just change TWRP for jflteatt and Oct-N installs per instructions. What a maroon I am lol. Well now I can wait out the spring/summer flagship releases since my S4 has been given a freath breath of life!!! Thank you manfromgta and the whole XDA community.
[AT&T Samsung Galaxy S 4 Original Android Developme] manfromgta:
Weekly 02/10

Weekly is up on site

Download: https://www.teamoctos.com/download/oct-14.1/jflteatt/OCT-N-WEEKLY-20170210-2355-jflteatt.zip

Changelog: https://www.teamoctos.com/download/...N-WEEKLY-20170210-2355-jflteatt-changelog.log
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Nice update. Stable quick and good battery. The camera and the video are now working perfectly for me. The only problem I seem to have right now is that the long press back button does not kill current app
[AT&T Samsung Galaxy S 4 Original Android Developme] sotoxf:
Did you enable the option in the developer settings menu??? All the way at the bottom enabling back long press kill app worked for me. The only trouble i'm having is i cant get my phone to read any LTE band, if i enable LTE only in the service menu it will remain without service. Besides that, its incredibly stable!! Will donate when i get the chance.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Yeah, thanks, that's the first thing I checked. I've gone there just now and disabled it and re-booted. I'll see if it comes on now... Nope. long press back button does nothing when turned off and back on in Developer Options.

My Lte is working... strange. If it was working before this update, try re-flashing?
[AT&T Samsung Galaxy S 4 Original Android Developme] sotoxf:
I flashed the stock firmware and realized the old MDL baseband wont connect to any LTE bands even in stock form. LTE Discovery reads eCSFB while trying to connect to LTE, whatever that means hopefully flashing a newer baseband will fix the issue.

My phone randomly rebooted and afterwards wouldn't load further than the loading screen with the moving circles, nor a factory reset or flashing any version of the rom would make it go pass that screen. I tried with a different rom also to no avail so i had to flash stock firmware through odin. I had the phone rooted with towelroot before flashing loki+recovery the first time, so hopefully that caused the conflict ??? im going to try and run the rom again.
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Audiofx no longer works (changes in app dont affect music), also, replying to texts using quick reply causes app behind to close. Will upload bug report.

Edit: https://drive.google.com/file/d/0B8wGZifBbicPSXg3OWRsbEQycWc/view?usp=drivesdk

Excuse the screenshot.. Ran outta time.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
sounds like you almost had a brick! Good luck on your next try... yeah, maybe it was loki. I never flashed it. ROMs have it included if it's needed from my understanding.

---------- Post added at 12:57 AM ---------- Previous post was at 12:48 AM ----------

I don't think audiofx ever worked for me for music. I use Jetaudio plus which has pretty good controls for cheap (free version is great).
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
It worked on the last couple versions, but for some reason doesn't on this one.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] fromthestars:
Great rom, I have been loving it for a few weeks now. My only issue is no audio when using facebook messenger video chat. Also I had a question. Last time I updated with the weekly update, I lost my gapps. Am I being dense? are you guys just flashing with no wipe? maybe I spaced and wiped too much.
[AT&T Samsung Galaxy S 4 Original Android Developme] roujinz:
Quick questions...

Can the weeklies be flashed without a wipe?

Just hate having to reset all of my custom settings mainly because it takes me a long time, and I am lazy.... :(

And anyone else having issues with enabling the Portable Wi-Fi HotSpot?

Mine won't enable as of the 2/3/17 Build date. It just says ERROR. Hoping its a fluke and the flashing the latest weekly will resolve this issue.

Any big THANKS for keeping my S4 alive! Had actually considered getting a new phone, but now I don't have too!
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
And @ post above me

Yes you can flash without wiping. As the ROM zip has a script to auto wipe system only, (still keeping settings and such), you do need to flash gapps with the rom every update though.

Though i think its more stable if you do a clean flash (based on my last year knowledge flashing resurrection and lollipop cyanogen) but who knows. Maybe technology has fixed itself now! Been testing with no manual wipe, and beside the weird sluggishness at the start, seems to be stable.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] fromthestars:
I did the dirty flash tonight and all seems well so far. Has anybody else has the fb messenger video chat audio issues? Literally my only gripe
[AT&T Samsung Galaxy S 4 Original Android Developme] manfromgta:
Update feb. 17/17

Weekly is up.

Check OTA or download from OP.
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Heres an issue that keeps annoying me. I dont think its a "feature" at all as it defeats the purpose of using the quick sms feature.

https://youtu.be/QUTyhl1SM04

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] Mr.Doge:
Hi im stuck on infinitive loading screen it happend before with same rom but at start and i just re-flashed it

but now i got ton of apps i didnt backup and i dont wana delet em all so if someone got any solution pls help

I got latest weekly ... and btw for some reason md5 was "not found " during installation so that might be reason?? PLS SEND HELP
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
First boot takes a while. Thats normal. Try letting it sit for a couple minutes and make a sandwich. As for the md5. Thats just an optional security check. No need to worry.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] Mr.Doge:
nahh i wrote it wrong i already booted it first time and used it for 2 days then i needed to reboot it and then it happend again :crying:

also i let it all night on loading screen nothng happend
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Did you update it or just reboot? Thats honestly odd.. You could try a reflash without wiping. It wont delete your apps aslong as you dont wipe internal storage.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] Mr.Doge:
i just reboot it... and i already did reflash 2 days ago thoe i wiped everything and it still got in this state also i think it will happen again if i do just system cuz it happend when i wiped everything so idk what to do.. :crying: :crying: just hoped someone got solution i guess il wipe it again and see what happens then if it happens again il just go back to 6.1 until next update that somehow fixes this tnx for help thoe [MENTION=6753088]J.Naw[/MENTION] <3
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
No worries. Try wiping everything except external storage in the wipe menu of TWRP, then install octos and gapps in that order.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] roujinz:
So, I performed a clean wipe and installed the latest nightly (2/17), which resolved most of the issues I was having (camera, button lights, notifications, etc.) However, I am still having problems with enabling the HotSpot. Every time I try to start my HotSpot, it says ERROR. This was the same issue as with the previous nightly, but it did work just fine with the previous version of this ROM (6.1).

I heavily rely on my HotSpot when working at client offices, so I am hoping the issue with the ROM and not my phone. :/

Any help would be greatly appreciated.

And thanks again for the hard work you guys put into this ROM!!
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
How am i to report bug reports to you guys? [MENTION=4478916]manfromgta[/MENTION] ? Ive left a bug report file, unless you guys just strictly want logcats? Multiple bugs im still experiencing on the newest (02/17) build:

Quick reply causing window behind to close.

Automatic rules for do not disturb do not come into effect.

Audiofx no longer has effect on audio.

And whatever else ive left on this thread.

Just havent heard anything from the team.. Great work though. Octos is easily better than alot of roms out.

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] manfromgta:
I've seen your posts. No worries. I don't reply a whole bunch as my time is better spent on troubleshooting the issues reported. Thanks for the feedback.
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Alright. Good to know youre a silent worker. Haha. Thanks for your hard work

Sent from JFLTECAN.
[AT&T Samsung Galaxy S 4 Original Android Developme] manfromgta:
[MENTION=6753088]J.Naw[/MENTION] I am seeing the foreqround app minimizing on send of quick reply. Is this new behaviour? Tbh I've never used it until now.
[AT&T Samsung Galaxy S 4 Original Android Developme] Nik1703:
Going to try this on two SGH-i337's tonight.

Just to confirm - no firmware downgrade is necessary? Both S4's mentioned are on 5.0.1.

So from my understanding -

0. backup

1. root

2. flash TWRP

3. Boot TWRP wipe

4. install rom from zip, install Gapps from zip, wipe cache, boot
[AT&T Samsung Galaxy S 4 Original Android Developme] J.Naw:
Been happening for the past couple updates. (Infact, since i updated to your version. Believe it was occurring on the jfltexx version as well.)

Sent from JFLTECAN.

---------- Post added at 09:32 PM ---------- Previous post was at 09:31 PM ----------

I've done a straight rom flash from lollipop without issues. If anything, an update for firmware would be good. Afaik. Not necessary though.

Sent from JFLTECAN.