yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobor9:
I recently had to start using my old s3 while I kept my eye out for a new phone again as my daily driver S7 was stolen :(

The s3 is on Android 4.4 and quite slow. Thinking of installing Resurrection for the speed boost and to be able to use certain apps that don’t seem to run on 4.4 anymore.

Question that I haven’t been able to find an accurate response to: Will the Resurrection ROM impact battery life compared to the stock 4.4? Will I need different kernel to improve battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] newbe1droidx:
I have an s3 also so go to the group for your phone and carrier and read a lot as you have to upgrade right or it will brick. Most ROM development is over but a couple exist. Carbon ROM and slim and octos I think. Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobor9:
Thanks, is there any issue with installing a rom that’s no longer in development such as Resurrectuon Remix (assuming a copy is available)?

Don’t plan on continuous modding, only looking for something more up to date than what I have that’s also stable and with decent battery life
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] newbe1droidx:
The only issue might be security updates that I can think of. Check the s3 forum and see. Good luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goldenboy104:
I have a galaxy s3 I747. I apologize for asking this as I know that digging for answers is the preferred way to get questions answered. I have looked, and queried and followed links for a few (full) days now, and can't find a nougat or marshmallow rom to burn. It seems all the links are dead. Please help! I have some critical apps that require a new OS than 4.4.2. Suggestions for a rom and instructions? I'm using the latest TWRP recovery if that matters.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
I'm pretty sure this ROM is abandoned, and we don't have a los maintainer for d2att anymore that I'm aware of.

octos is a solid choice for a nougat rom, but their final release is from August of last year.

Mokee is still posting new weekly builds that I assume have newer security patches merged. I've never used it on this phone, but might give it a shot next time my d2 needs a wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
Mokee dropped support too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goldenboy104:
A Very grateful Noob

Very thankful for your helpful reply, and the urls, Jason2678! I have downloaded the Lineage d2att rom, and they have instructions for the installation. Nice to know that I have a choice with Mokee, also! The platform is old, but it seems that the i9300 has gotten a lot more attention.

Nevertheless, I am SO grateful for you pointing me in the right direction. I was not aware of the Lineage website, nor had I even heard of Mokee. I was so lost. Just a noob in the wilderness.

Thanks again,

Goldenboy104
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ipnosomar:
Why in the menu says 7.1.1 and on the description say 6.0.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Juleast:
Mokee?

Mokee supports I747s but does it matter what version TWRP u have to install it?

Also does it take very long to install this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] user-747:
ROM link does not work

Is there an updated link for the resurrection ROM for d2att phone. The link on the front page yields 'file not found'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
Glad you're loving this ROM :)

And yes I used their MM ROM before using any other, it's really really good :good: I'm working with bthorne79 on something special for d2 users so stay tuned :victory:

And app circles can be found in Settings > Configurations > Gestures > App Circle Bar

Enjoy ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ZentixZaneic:
I'm kind of new to reporting bugs on stuff, so just tell me if it isn't helpful, but I'll try to report bugs on things that I personally see. Let's hope this helps! *crosses fingers*

Google Apps:

Google: 'Now on Tap' isn't available.

Google Keyboard: occasionally, swipe input doesn't register a word, and regular, typing input sometimes lags depending on the app (I've noticed this with only FB Messenger, currently)

Play Music: locking the device works without lag, but pressing the power button or home button to turn the screen on makes you wait 1-3 seconds before the screen turns on.

Settings/System

When configured, double pressing the home button doesn't bring up a prompt to select your search assistant or open up Google (you can use Home2 Shortcut to work around this)

Sliding down from the notification bar on the lockscreen doesn't pull out quick settings.

That's all I've really found out, I hope it helps! If it doesn't, I'm sorry, I'm only a teenager so I don't know everything about Android :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Got it! Thanks skatter! ....Bliss:D now, guess you'll be looking into that bug in "Performance" for the next weekly huh! it force-closes immediately you touch the button, perhaps i can be of some assistance?; I've got "CatLog" installed, what area specifically, do I need to check for that bug?

:fingers-crossed::good::good: eagerly waiting to see what you guys cook up man! Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
Not sure about play Music, I don't use that app and I don't see a lag while turning on screen,

For home button, you have to configure & download a search client. & slide down twice on lockscreen.

I probably won't be able to this weekly as I'm working on other stuff too, but I will get that fixed :o

I also don't see AICP for d2att users... I will probably look into that as well ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Uninstall the update to kernel adiutor in the play store & performance will stop force closing in settings. I would uncheck auto update just for kernel adiutor in the 3 dot menu in the top right while on the apps page as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bloodflame:
Might be a dumb question, but I have zero experience with the Galaxy SIII, although I am quite familiar with many other phones (including the S4 Mini). Basically what I'm getting at, it appears the AT&T version (d2att) of this phone is pretty much the same as the Canadian models. So is this ROM (and any d2att ROMs) compatible? The phone I have to work with is a SGH-i747M from Bell Canada. Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kent_geek:
I installed this ROM today, and it's very nice. Seems well equipped and very smooth. I had to go back to my Oct-L Lollipop, though, because of one problem: my stereo bluetooth headset, the LG HBS 730, connects and can listen to media, but will not receive phone calls. I get no indication that a call is coming in if the headset is connected, until I get the "missed call" notification. If I try to make a call, the called phone rings, but no audio can be heard in either direction after they answer.

Any idea what could be causing this? I'd be happy to try again and get the log data, if you think that would help. I have exactly the same symptom when I try the Oct-M and CM weekly builds, so it's clearly not a pure RR problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
I wanna upgrade to this ROM. But i'm pretty noob at this kind of thing. I was able to use a ROM from this forums as well ( [ROM] [4.4.4] SlimKat d2att (at&t) Stable 9.0). But i already forgot how i did it. If you could be so kind to provide a detailed step on what to do to install this ROM I'd very much appreciate it. Thanks in advance.

btw is it safe to install this ROM if i already have the 4.4.4 Slimkat installed on my AT&T Galaxy S III?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osk4rin:
Does anyone has the zip file of the Rom?

Can't get it from the link,(Site Upgrade in Progress )

Thank's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
First you'll need to update your recovery to TWRP 3.0.2 for d2att. (Use the flashify app it's the easiest)

Download the ROM & 6.0 gapps package of your choice fro opengapps.org

Boot into recovery

Make a backup first!

After backup is finished...

Wipe data factory reset

Then in advanced wipe system, dalvik cache & cache

Flash ROM and gapps at the same time (DON'T reboot in-between flashing ROM and gapps)

Reboot & enjoy.

Note: All Marshmallow Roms take awhile to boot be patient.

---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------

Yes, just use the d2att version of twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osk4rin:
Hello guys!

After flashed Resurrection remix on my s3 i747 at&t and flashed the gapps,the phone is stuck on the Resurrection remix Logo,(bootloop)I tried the same step many times with a clean flash.

Any help please?

Thank's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nhail47:
Does anyone experience reboots when installing applications? Or just random reboots in general? I love the ROM tho. It's amazing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
Okay, i was able to install the ROM properly. But after installing, the phone doesn't detect my sim card anymore. installing this ROM locks the phone to AT&T again? BTW i'm using a different sim card since i'm from asia, But i was able to unlock this phone before i install the Slimkat 4.4.4 custom rom. Any ideas guys?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Thanks! that was the culprit alright! Still this doesn't happen with Oct M so it may be something to look into, anyway that's a minor bug and you've provided a solid workaround :good: still running smoothly thus far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
Is there any fix regarding my problem? After installing this ROM. i'm receiving an "insert sim card/no sim card" message. No signal, no GPS, Cannot activate mobile network/cellular network. Weird thing is i can receive calls/texts from another phone, but i cannot send a text or make a call. Please help :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
A few questions here, just trying to help:

Is your device

AT&T SAMSUNG-SGH-I747

?

Is your baseband version

I747UCUFNJ2?

Are you using TWRP recovery version 3.0.2.0 -

FOR

d2att?

Gapps Package: open_gapps-arm-6.0-*stock/mini/nano-20160802 (*your preference)

Make sure to check the md5sum (I use Marxio File Checksum Verifier 1.6.17)on both ROM(39055163e2bfa8081f8f73df3ad2c5dd) & GAPPS(the package changes from day to day so MD5sum will be different) it is possible you got a bad download on one or both of them, these are some of the things than can cause problems when flashing. Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
Hi, my device is AT&T SAMSUNG-SGH-I747

Baseband is I747UCDLK3

Used TWRP 3.0.2-0 (d2att)

What is the md5sum do?

The one i used are these links that the op provided

http://opengapps.org/

https://www.androidfilehost.com/?fid=24671309938032667
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
You have a big journey ahead of you if you want to run anything above KitKat. The LK3 bootloader & modem is old as my grandmother lol. You'll to update to at least NJ1 (preferably NJ2) !!!YOU MUST EXERCISE EXTREME CAUTION HERE!!!

Bootloader & modem must match before proceeding further. So if you run this command in terminal as root

type su

hit enter

You should get the #

type getprop ro.bootloader

hit enter post the results here.

See the attached picture of terminal output

!!DO THIS AT YOUR OWN RISK!!

Research & research again! I'm not responsible if you brick your device, you are!

Don't try to update until you have confirmed both bootloader & modem are both LK3. Once confirmed you'll have to incrementally update until you get to NJ1 or NJ2. YOU CANNOT SKIP VERSIONS. You MUST flash each bootloader & modem combo in the correct order or you WILL BRICK. From LK3 you'll have to flash in the following order, MG2, MJB, NE4, NJ1, NJ2. (MJ2) was a leaked unofficial version of MJB You don't have to flash it but it won't hurt if you do. You can get the update zips from enewman17's AFH here https://www.androidfilehost.com/?w=files&flid=10522 as I said before, use extreme caution. Research enewman17's threads & do your homework. I've seen way to many people, way to many times brick their d2att because of mismatch or skipping a step. Flash only one zip at a time & reboot into ROM & check in settings/about phone to verify the flash took by checking the baseband also use the get prop command to check the bootloader to be sure it matches baseband. If it's a match continue to the next combo. You should do this while on the custom ROM. If you do it on stock ROM you most likely will have issues with wifi etc..

Md5 sum is used to verify the file you downloaded is correct and not corrupt.

I recommend checking the md5 b4 flashing anything! Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
Is this a guaranteed fix? so the problem is the modem of the phone. Can i flash these using Rashr (TWRP recovery)?

After i updated to NJ1/NJ2, the phone will detect the sim card again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
I can't & won't guarantee anything as I can't be there to see how you do everything lol. I can confirm that this is why you don't have any data or signal. You're (firmware) bootloader & modem are out dated. This is just one way to update your bootloader & modem (firmware). The only other option is to flash back to un-rooted stock & take the OTA updates until you reach NJ2. I will say that when done correctly, yes it's the only way to fix your issue. Ultimately the choice is up to you. This is how I & many others have updated our firmware. The obvious safest route would be to take the OTAs from un-rooted stock & stock recovery.

If you choose the other way then the zips must be flashed thru TWRP recovery NOT thru any apps like rashr or flashify. You must check as mentioned in my previous post to ensure your bootloader & modem match now & after every flash as mentioned before. Take the time to do your homework and research the other threads here on XDA.

You'll need to be on TWRP 2.8.7.0 or higher. You can flash TWRP recovery many ways.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Well there you go, your firmware is very much out of date!! But, If you follow the excellent instruction given by @canodroid15 below you should be fine, but i must reiterate!! Above all: read,read,read!!do your research!! follow @enewman17 threads; install and get familiar with

Odin

- it's you best friend in a crisis. If you did a backup,(I sure hope you did!!) restore that backup until you are comfortable with these step and try again. Good Luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
Thanks [MENTION=5382467]CoperaN[/MENTION] & [MENTION=5806583]canodroid15[/MENTION] for helping around the thread :D :good:

And will release version 5.7.3 later on today for d2att users :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=6249123]Lonelyskatter12[/MENTION], no probs man, I gotcha homie ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Yeah! no worries man,... keep your hands free for that nex nother ROM! :):good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
I have the aicp mm source on my box. Saw this post and it made me decide to check. It has d2att makefiles, but it can't get all it is looking for from github and fails during breakfast.

Strange, it has a relatively recent KitKat build fingerprint, but I don't recall ever seeing it posted anywhere. Maybe it was someones wip or abandoned project.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CwalkPinoy:
by the gods, you are a lifesaver. i was worried that i couldn't go back to stock for a working camera but somehow you fixed it. everything is just amazing. you saved me 65 dollars on this used phone. it's blazing fast, no crashes yet, and everything i use works like a freaking charm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
---------- Post added at 09:36 AM ---------- Previous post was at 09:29 AM ----------

[/COLOR]

Is the TWRP recovery you're mentioning an app in google play called TWRP Manager?

EDIT: Downloaded twrp manager. I will give it a try later. Thanks for helping guys.

Last question, Do i need to Wipe Cache and Dalvik Cache each time i flash a modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
No wipes in-between flashes. Flash one at a time, reboot to OS check baseband in settings/about phone & bootloader in terminal to be sure they match. Repeat untill you reach NJ2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
Seems to be working just fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sinsfromhell:
[MENTION=5806583]canodroid15[/MENTION] and [MENTION=5382467]CoperaN[/MENTION] Hi, fixed my gs3 at&t. Big thanks to you guys. You guys are the living proof that not all heroes wear capes!!:victory::victory::good::good::D:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Very good! glad you got things sorted out, just proves the old theory: if at first you don't succeed.....:good::)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galvao10:
That's Truth

I have the same problems with LP and MM ROMs for the d2att , I'll try your ROM and see if I get lucky ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
[MENTION=5665543]sinsfromhell[/MENTION], great! Glad you got it, now just always remember that you can't downgrade. Stay at NJ2. Honestly, NJ2 is likely the last update we'll ever. NJ2 is where it's at ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Just installed this build in my old s3 it's very nice but I can't find where can I change the back light of the button

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Galvao.. Please before trying.. Make sure to clean flash.. So as to firmly ascertain the cause of the prob. Busy with school issues.. So can't really do much with ROMs at the moment.. But pls make sure u report the outcome asap.. Tnx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
This is such a great rom. Would dev add the setting to toggle off the charging Led when the screen is on? Also can you give an option of turn off the key Led? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Bug Report

Okay, so I did a dirty flash over the previous build with the 20160807 build, all went well but there's just one annoying bug I've had from the previous build and it's persisting with this one: "SCREEN OVERLAY DETECTED" I've googled it and searched here in XDA and it's a problem with quite a few people, more so,it seems, with those who've gotten OTA updates, there are a lot of workarounds but I've found nothing thus far to address the issue on this build. So if anyone else has been experiencing the same issue feel free to chime in, maybe there's someone out there who found a cure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
I don't know about dirty flashes, I never dirty flash I the d2spr , which is almost like the same phone and I'm not having this issue

Have you tried clean flashing this one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
It's working perfectly fine with a dirty flash and i only did it because it's what i have to do with the Oct M, their releases are done weekly so it'd be a real bummer to have to go through the entire setup every week but like i said the issue was on your first release as well so could be a bug. However I will do a clean flash and see if the problem is fixed. "Almost" might be clincher!!;) ...it's been known to happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Just to be clear, do you mean you dirty flashed Oct ROM over this ROM without glitches.. ??

---------- Post added at 05:34 AM ---------- Previous post was at 05:28 AM ----------

Edit: Finally understood your post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Whew!!! Now that would've made me into a Super Noob:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
:D:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rickymills:
Can you read and write to your SD card in this rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
Sorry for the delay guys.

Been working on something else.

Running a build right now, will be up tonight
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CwalkPinoy:
facebook messenger

hey so everything seems to work except that facebook messenger is laggy and crashes every so often. also the kernel auditor update keeps installing on me so i have to keep resetting it. but the latter i've already seen reports on.

another thing is that the battery life is awful on normal settings and a bit better on efficient mode. it can last maybe a day on idle or 4 hours of activity. not sure what to change to improve life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibuddler:
Did you install lmt or using Pie? Disable them first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoperaN:
Actually that Issue has been resolved! I did a clean flash and used a test Kernel from [MENTION=6249123]Lonelyskatter12[/MENTION] and I haven't had the problem since! So I'm good now but thanks all the same will save that to list of tests.:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brainstorrrm:
root missing / recovery inop / VPN / Micro SD card

I was running fully functional Liquidsmooth rom 5.1.1 with TWRP 3.0.2.0

Updated bootloader and modem from NJ1 to NJ2 per instructions in this thread - thanks for the instructions.

Checked for full functionality and made a full nandroid backup to the SD card.

I used RR rom successfully in a Samsung S4 recently, so I thought I'll try this one for the S3 d2att.

Nice rom, almost everything I've tested in the last two hours seems to work.

However, I have some vexing issues that prompted a first post on this fine forum. :eek:

- I did a clean flash after wiping system, dalvik, data, etc.

- Looked for root setting, and could not find it. Google tells me CM13 root control is in advanced developer settings, between "Running services" and "Update Cyanogen recovery."

See attached screenshot. It's not in that location. Maybe somebody can point me in the right direction. :confused:

- Looked everywhere in settings for root control and failed. Thought I'll flash SuperSU from TWRP recovery (Vol up, home, power) only to find I can no longer boot into recovery. No software option, of course, without root.

ADB works, but fastboot no longer works.

I would appreciate some direction on what to try next.

- VPN entry in settings is empty. No big deal as "I have an app for that," but I'd like to know if this entry is supposed to be empty.

- Somebody asked repeatedly what happens to Micro SD card access after flashing. PC via USB no longer works after flashing, you have to use a file manager like ES File Explorer to ftp into Android and you can access the SD card that way. Kinda lame, but it works.

UPDATE: Root fixed!

I was going to delete my post, but maybe it can help some other soul with similar testing issues.

In the adb command line (SDK platform-tools folder in Windows file explorer) I used "adb reboot recovery" and booted successfully into the TWRP recovery.

Flashed Chainfire's latest beta SuperSU and now I have root again via SuperSU.

Now I can continue some happy testing with this very nice RR rom. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lonelyskatter12:
I sync straight from RR's sources which is why it doesn't have SuperSU in the zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Basmatek:
Can anyone with active sim card check if in-call speaker volume level adjustment is functional? In all CM13 Roms i tested, speakerphone is always at full level.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yosmokinman:
^Yup I can confirm. Can't lower speakerphone volume. Official cm here.