yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] santij07:
Is a good news, we know now that this modded TetheringProvision.apk works.

---------- Post added at 10:06 AM ---------- Previous post was at 09:53 AM ----------

Is a good news to say that I found a good working TetheringProvision.apk, works for ATT I747UCUFNE4 Kitkat and S5 maybe others on 4.4.2, for all that need this Please Hit Thanks Bottom this is for days and hours of searching,modifying TetheringProvision.apk, testing and last I find a good working Tethering on this thread http://xdaforums.com/att-...rrier-t2801876 just follow the instruction. I have right now native tethering with this post I can confirm this works, in the post says remove the Oldest "TetheringProvision.apk" and "TetheringProvision.odex" but just only rename it to .bak both just in case, then replace it with the new one and check and set permission rw-r--r-- reboot phone, that all. Here Download link for modded TetheringProvision.apk: http://xdaforums.com/atta...8&d=1404254703 .

PS. Remember Hit Thanks Botton.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] demonflame5:
Can I safely go back to this?

CM11 updated my version to 4.4.4. I would keep CM11 but I really can't go on without answering calls with the home button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slinson:
wifi cannot be switched on after flashing. does any one happen to know the solution?

---------- Post added at 07:31 PM ---------- Previous post was at 07:29 PM ----------

Fixed after flashing kernal in original post. never mind :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nathanyang0428:
Whether this offical firmware version contains a lot of lanuages? As I remembered, the S3 I got from ATT did not have Chinese build-in and that's one of the reasons I installed S3Rx.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jakeuten:
i wish battery life wasn't so bad, love TouchWiz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mack49:
insecure kernel

Could you please post a different link to the insecure kernel. For some reason I cannot get it to download on mediafire.

Thanks for all your hard work!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Try again I fixed the link
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mack49:
Thanks, just downloaded. Have been on your Odex rom for about two days now, no problems except it went back to secure on selinux once I rebooted and I couldn't get it back to permissive even with the instructions in the OP. Again thanks for all your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Can't get this to boot at all. I came from CM11, formatted data/system. I have the MG2/MJB combo.

Have tried both Odex and Deodex versions, with the kernel, with the Kloontix kernel linked to. All I get is a white SAMSUNG logo for about a second then nothing.

I have to pull the battery to get back to recovery.

Am I missing something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mack49:
I followed the OP to the letter. I upgraded to MJB then NE4 and then flashed the odexed rom using the latest recovery from Phil's every thing worked great. Just couldn't fix permissive until I could get the insecure kernel downloaded and installed. I was on S3rx 3.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Viper67857:
Mg2 is too old... U need mj2 at least

Sent from my SAMSUNG-SGH-I747 running TMS3KK-2.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Yup, that got it. No idea why, but I'd swapped the versions around in my head. Could have sworn the mg2 was the leaked 4.3 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
Just flashed the ROM with the modified NE4 kernel on the op, everything seems to be working

the only issue I have found so far, is the battery depleting somewhat fast, android system seems to be high

I'll give it a couple battery cycles, hoping it will settle and improve the battery

great job from the developer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Just because i was having issues with the KTOONSEZ kernel wanting to charge , I decided to flash your insecure kernel [MENTION=2972841]enewman17[/MENTION]. And just for curiosity , I installed the performance control app that was developed by [MENTION=270650]Horn[/MENTION]t for aosp Roms. To my surprise a lot of the features worked. According to the app, this kernel is running at 1242 mhz minimum, and 1512mhz max. I changed it to 382 I believe, or whatever the lowest mhz available is for most stock kernels just to see if that may be the reason for battery consumption. However, the settings won't stick when exiting the app. The governor, the -25mv, the scheduler, and the read ahead values all stuck. So gonna leave the app running in the background just tobsee what happens. Just thought you might be interested in knowing this if you don't already. ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Deep sleep was great. Lost 15% over 8.5 hours. And looks like about 8-9 hours of normal use with stock battery. Average for an S3 I'd say.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
TouchWiz kernels don't usually report the correct MHz so the apps display them wrong. But you'll see that CPU spy will tell you that it is scaling and sleeping correctly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darian71:
Thanks for the information sir. Yea, CPU spy did in fact show it was scaling correctly even without the manual setting of the minimum. Also figure it worth mentioning, my charging issues are NOT related to KT's kernel. Definitely port issue. New cord, new charger=same problem. Took board out, slightly crimped the port, and made my cord fit much tighter now. Wish I had the tools to replace it. And the eyes. [emoji15] [emoji106]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I'm having around 20% less battery life on this rom compared to cm11. I though tw would have better battery life than aosp, but is not the case here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I think otherwise.. Lots depend on the apps we have on our mobile which are running in the background..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] barlie:
adding lockscreen widgets and camera icon on lock screen

Does anyone know if you can add widgets to the lockscreen on this ROM and how to remove the camera icon that shows up at the bottom right corner on the lock screen ? I've looked in various settings and couldn't find anything (in security or lockscreen).

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidBH:
Settings > My devices > Lockscreen > Shortcust "None"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chivas1311:
Yey! work on my I747M from Mexico, this is the first "rom" that works for me. c:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jakeuten:
wish the horrible battery life issue would go away...15% or more android system usage... 1 hour 15 mins SOT and at 27%... ridiculous.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgoe:
My battery life has been awesome! !!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chivas1311:
My battery has good durability, reaching for a labor day with normal use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shankar10:
Great battery life with normal usage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_geek_0507:
UCUDLK3 is TW4.1.1

UCUDMG2 is TW4.1.2

UCUEMJB is leaked TW4.3

UCUEMJ2 is TW4.3 release

UCUFNE4 is TW4.4.2 release.

Hope this helps clarify any issues you had.

Jason
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
MJ2 was the 4.3 leak

MJB is the official 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReddMOA:
The links are bad now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
This is interesting... if I look on my phone I get a 404 error not found but on the computer they are there and download so I don't know what the deal is. Might be something with AFH and there updates and mobile browsers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReddMOA:
Will try again on my pc

---------- Post added at 09:29 PM ---------- Previous post was at 09:28 PM ----------

Actually its working on my phone now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Finstababee:
late to the game

Hi,

I'm running CM11 M9, I have MJ2/MJ2 combo with CWM6.0.4.7. After I flash the deodexed rom should I flash the ktoonsez kernel or the stock insecure? Will I still be able to disable knox with the insecure kernel the same way as with ktoonsez?

Sorry for all the questions but want to get it right...

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Knox was introduced with the MJB firmware, it was not implemented in the previously leaked MJ2 firmware, unless I am wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
is the stock kernel in OP , o.k. to flash on non-stock/non-touchwiz ROMs.? have a feeling thats a big NO , but thought i would ask.

thanks for any info/comment.

err on the side of kindness
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Your correct. Fact it won't work on anything other the new tw 4.4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I'm running CM11 M9 (4.4.4) and having tons of issues, so I want to flash back to stock. Can I use this image or is it not compatible because of whatever upgrades may be in 4.4.4?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you are on at least the 4.3 bootloader and modem (MJB) then yes, but according to the OP you will need the KToonz kernel for that bootloader. With later bootloaders you should be good.

I haven't flashed this, merely spent time in the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
My baseband in the about phone info has the NE4 modem, so I should be good since this is the NE4 release, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Sounds good, from all I've read you would have bricked the phone if the modem and bootloader didn't match when on the latest versions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
It worked. Thankfully. I bricked my other SG3 a few weeks ago, so I was a bit worried. Haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 79TAKid:
Phone doesn't boot anymore, luckily download mode still works...... ugh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcr4m:
Is there any way I can get tar file and flash with odin because I can't get in to recovery mod Only mod I can get in is Downloading mod it's always restarting except in download mod
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Sorry I can't make an Odin file of this as I'm missing a few images that prohibit me from creating one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chargerdude70:
LK3 to NE4

Question please. I have looked and looked and the answer I am searching for is so confusing. I am currently running task650.20140729 build. Build number list it as 4.4.4 but fingerprint and description state it as 4.3 MJB. I am on LK3 bootloader and modem. I want to return my phone to latest stock firmware to sell. Do all I need to do is to flash MJB BL and Modem and then latest firmware? Or do I need to flash to a certain FW prior to flashing to the latest? If so, please list flashing order of FW to get to where I want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcr4m:
Hi guys I tried to update my 4.3 to 4.4.2 I use to have MJB bootloader than I just flash NE4 then I tried to flash I747UCUFNE4_Stock_Rooted_Odex but I didn't happen. Now I can't go back to MJB bootloader and I can't use 4.3 too , actually I couldn't flash anything it's giving some errors when I try it.Something like :

e error executing updater binary in zip ...

when I try to reeboot I can't pass At&t screen . So what should I do _?

I'm using costom teamwin recovery . I apply exactly steps and wipe. I try to back up from my restore it says restore Completed but again when I reboot I can't pass At&t screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OKAstro:
Did you try data format in TWRP as well as all the wipes before flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rogersb11:
Use philz or cwm. And pull the update binary from cm11 or something for the new one. I love twrp but started building my own philz for similar issues. I'm in note 2 or I'd link you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcr4m:
I just flashed 4.3 by odin ( thanks enewman17 ) now I'm working on it I'll change recovery mode than will try 4.4.2 agin :D

Edit: I couldn't update and it's broken, weirly when ever I try to update to 4.4.2 it's happening again I can't update I'll try with another recovery this time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gremmie:
I got this ROM loaded but my WiFi will not turn on ...Any ideas? thank you

***Never mind reloaded the kernel and 2nd time and worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brehon1104:
Hey guys, I've been doing some research and I can't find solid advice. Any help is appreciated.

I am on 4.2.2 AOSP based ROM, and I want to go back to stock because I am changing carriers from ATT to T Mobile. Assuming this is the right stock ROM I need, I'm trying to meet the "Prerequisites include a minimum of a 4.3 bootloader and modem." requirement, and I'm not sure how. Do I need to flash Ktoonsez "AOSP JELLYBEAN 4.3 Linux 3.4" and then flash this ROM?

Thanks in advance for any advice.

-brehon1104
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
What firmware and baseband are you currently on? In the terminal emulator you can run these commands

getprop ro.bootloader
getprop | grep baseband
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brehon1104:
Thank you so much for your help.

getprop ro.bootloader =I747UCDLK3

getprop | grep baseband =

[gsm.version.baseband]: [I747UCDLK3]

[ro.baseband]: [mdm]

[ro.boot.baseband]: [mdm]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 79TAKid:
I'm going to keep reading through the thread but i'm having internal storage permission errors I see DocHoliday wrote something about installing an unlocked kernal but that it can cause wifi not to work??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 79TAKid:
Okay I installed the kernel from the first post and it seems to have fixed my problems :)

It did pop up saying SE has been turned off though? I guess I'll do a factory wipe in TWRP and start over with the new kernel.

edit again, nevermind. I think just running SuperSU and having is disable KNOX worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stslimited84:
Will this work for me? I'm currently on lollipop on my i747 with I747UCUFNE4 using the latest TWRP build.

I need to get back to a stock rom so i can carrier unlock my phone. Will this fit my needs? If so, what procedure do i follow to successfully flash this and avoid bricking?

Thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Yes, this should work. Do a full wipe in recovery. You may even need to format system., but you can see how it works without doing so first.

You wil not be able to do the free carrier unlock from any stock ROM you can safely flash. The free unlock depends on the hidden menus that are based on the 4.1.1 modem. This leaves you with getting the unlock code from your carrier or purchasing one from an on-line vendor. For the unlock code from your carrier, you have a limited number of attempts ( 5 ? ). If you don't succeed on the first one or two, you may need to unroot, or even return to a stock recovery, be careful, check on this before plunging in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stslimited84:
I have the code from my carrier but it didnt work. I assume this is bc im not currently stock. Thats why i was looking into this rom but from what i think your saying this wouldnt work either?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
It should work once you are on stock. The question is, How stock do you need to be? You may need to flash the stock recovery and unroot for the code to work. The reason I made the caution above is due to the limited number of attempts the code allows, five. If it didn't work from a custom recovery go stock. If you only have one attempt remaining, go all of the way to a stock recovery and unroot before trying again.

I see where my wording from the previous post may have been confusing.

Since you are already on NE4 bootloader and modem you can not revert/downgrade to LK3 (4.1.1) and use the free unlock method posted in the forums. Trying to downgrade to LK3 from NE4 will brick your phone. If you haven't used up your attempts with the carrier code, you should be able to unlock from a stock rom with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stslimited84:
I have only tried the code on the cyanogenmod 12 lollipop with twrp as the recovery. I have yet to try any other configuration as I wanted to get clarification on what I needed to do. I have 3 attempts left.

So should I try this rom flashed via twrp or go all the way back to stock recovery? I'm relatively new to all this and have only ever flashed via twrp.

I want to switch carriers and keep this phone which is why I want to accomplish this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
If you are still on CM12, yes flash this ROM. I would not try more than once more before going all of the way back to a stock recovery. Enewman17 posted a download link for a stock recovery in this thread. That is a thread on updating to NJ1 (unecessary for you) but I believe in the pages it states that the recovery is the same as for NE4 - check and be certain.

Better yet might be to post in a new Q&A thread and see if anyone else agrees or disagrees about going all of the way back to stock recovery. I would not want to lead you into wasting your attempts and put you in the spot of being unable to unlock. If you do start your own post, feel free to summarize all of the above however you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stslimited84:
Flashed the rom and it seem to go through fine. I get the stock boot loading screen with the att sound (3 beeps) and the att globe but it stays stuck on this loading screen. Not sure what the problem is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Got your pm btw... try this out. https://www.androidfilehost.com/?fid=95784891001611561 flash this ne4 restore. I think I should update the op with this restore... either way if you have the unlock code from the carrier it should work just fine on any stock tw Rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stslimited84:
Thanks for your reply. To clarify, flash the above file in twrp as an installable file or do it as a restore? Any other files to install besides this one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Yeah just flash with twrp, and it will restore the system, boot and recovery... Btw you'll need to Odin recovery again once you unlock and your ready to flash a new Rom or restore your backup. The restore I just linked is completely stock, no root... nothing so if it doesn't work to unlock I'm afraid I don't know what to do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stslimited84:
Just flashed the file and having the same issue as before where the phone hangs on the screen with the att globe after the att sound plays and now no twrp :(

**Edit - accessed stock recovery and formatted user data after the flash. Currently running initial setup :)

Unlock code was accepted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Awesome!

Far as your pm about Odin... here are the links for the tar images for twrp http://techerrata.com/browse/twrp2/d2att

link for odin http://xdaforums.com/showthread.php?t=1722686 install on your pc

link for supersu http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

Transfer the super su zip to your sdcard.

Open Odin

The op of the link you'll see a screen shot of odin. in the top left box when you phone is connected it will say something like COM3

in the right hand side you see a list of buttons Bootloader, PDA, Phone, CSC. Check the box next to PDA and then press the PDA button and load the twrp.tar file into that slot. press flash and wait till it's done.

Now the phone will reboot when it's done... BE READY! once the phone starts to reboot you need to hold the POWER, HOME, and Volume UP to enter recovery, flash the super su zip. Now your ready to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] n_alvarez2007:
Need working debrick img for old I747

My S3 bricked using the original files posted in this thread. It rendered my S3 completely useless and I was forced to use and older phone to tie me over until my contract was up. I really miss Android and wanted to play with my S3 again. However, it is still bricked since, at the time, I never found a working solution.

Could someone link me to a working debrick for the i747 without the need for a JTAG? I flashed the Kitkat modem that bricked a lot of people's S3 models. Any links or helpful guides would be appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radoo7701:
I was having the same issue on my in-law's S3. This worked for me. Also since it was on NJ1 modem/bootloader I had to flash the NJ1 update in the stock recovery to get Wi-Fi working again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CB620:
I have stock rooted 4.1.1 with TWRP can i just download zip in OP+Kernel and flash and be on 4.4.2?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
No, you have to update incrementally, also you need to have the i747U & not i747M, what does your baseband say in settings, about phone?

Sent from my OctOS d2att

Beware "The Kraken"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chitown835:
I would just recommend unrooting your phone and download the 4.4.2 ota
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Before you do anything you may wish to consider, if your phone is not carrier unlocked, using the free method to take care of this: How to unlock your I747 (AT&T Galaxy S3)firmware 4.1.2 (FIRMWARE DOWNGRADE INVOLVED!) You would not be downgrading since you are on 4.1.1. This unlock could never hurt, and survives upgrades.

If you are wanting to update to KitKat it will take several steps to get there. As [MENTION=5806583]canodroid15[/MENTION] suggested you will need to go incrementally. The simplest way may well be as chitown835 recommends, unrooting and then taking each OTA in turn. I'm not sure, but you may also find you need to return to a stock recovery to receive the OTA updates. This will step you from 4.1.1 to 4.1.2 to 4.3, at which time you could then flash then ROM followed by the ktoonsez kernel. Or you simply take the next OTA to 4.4.2. Generally you are forced to wait a day between each OTA. This waiting period can be shortcutted by changing your system time/date after each OTA.

If you do not wish to unroot or remove TWRP to go through each OTA you will still need to update the bootloader and modem incrementally. Use caution, the bootloaders and modems are not the same for the i747 (AT&T) and the i747M (Canadian and Mexican variants). IF you are on the i747 go through each step. If you are on the i747M I would suggest doing the same, though it may not be required until you reach 4.3. To reduce chances of problems update the bootloader and modem together, keep them at the same version. Once you are at 4.3 you could do as you asked: flash the ROM and then the kernel.

Check the first post of the thread. It states that you must be on at least the 4.3 (MJB on the i747, or MK5 for the i747M) before flashing this zip. If this is the route you take, be sure you do not get the stock image dump from the first post, it includes the bootloader and modem, your day would be ruined if you are on the i747M.