Develop Bugs

[Q] Manually update At&t samsung galaxy s3 I747

I have i747 and update is only possible through ota that's what written on official website kies is not updating my phone as it is showing 4.1.1 is the latest firmware.
Please help me how can i update my Sgh-i747 manually or any other method.
I don't wanna root my phone.. I have also downloaded leaked 4.3 ROM I747UCUEMJ2.7z and after extracting i get different files.I didn't get any .md5 or .tar file which odin recognizes. So i can't update my phone maually to 4.3 by odin
Please help me how can i update my sgh-i747.
I have official samsung firmware 4.1.1.

samoudwfr said:
I have i747 and update is only possible through ota that's what written on official website kies is not updating my phone as it is showing 4.1.1 is the latest firmware.
Please help me how can i update my Sgh-i747 manually or any other method.
I don't wanna root my phone.. I have also downloaded leaked 4.3 ROM I747UCUEMJ2.7z and after extracting i get different files.I didn't get any .md5 or .tar file which odin recognizes. So i can't update my phone maually to 4.3 by odin
Please help me how can i update my sgh-i747.
I have official samsung firmware 4.1.1.
Click to expand...
Click to collapse
The update IS possible OTA. It does not show up in KIES for some reason.
A couple of things before you do this.
Be aware that once you have the MJB bootloader that comes with the 4.3 update, you cannot go back to anything lower without bricking the phone. Plenty of articles here about it. Until someone here finds a way, it's a one way trip, and there is no stock firmware available yet to flash via Odin. I'm also not sure if you can load one of the other 4.3 versions found here without bricking it after the OTA 4.3.
Some new features are added in 4.3, and some are broken. For me, after the update, s-voice no longer works via Bluetooth, and I'm pretty sure it is an S-voice and not BT issue. Others are reporting battery life issues, constant updates, etc. Research research research. (I wish I had)
Go to settings - about device - software update and follow the prompts to get an OTA. I don't think AT&T is pushing it, but is available. Probably not a bad idea to boot to recovery first and wipe the cache before you do.
You have to be running a stock recovery for it to install and its about a 1gig download, so be on wireless and have a fully charged battery.
In my case, I had the phone rooted with a toggles mod. The update went partially and broke some things. I had to flash to an unmodded unrooted 4.1.1 via Odin to get the update to go.

I made the mistake of trying to flash MJ2 bootloader after having the MJB bootloader. It boots now with the "unbrick" sd card. Would it be possible to ODIN stock 4.1 and still boot with the SD card so it could take the 4.3 OTA again?
Sent from my SAMSUNG-SGH-I317 using Tapatalk

RichMD said:
I made the mistake of trying to flash MJ2 bootloader after having the MJB bootloader. It boots now with the "unbrick" sd card. Would it be possible to ODIN stock 4.1 and still boot with the SD card so it could take the 4.3 OTA again?
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
I don't know. I've never bricked a phone. As I understand it, 4.3 BL blows e-fuses making it impossible to downgrade. If that is in fact an accurate description, then even if you were to get it to boot via SD card and installed 4.1.1, it would brick it again (double brick?)
Considering the dangers involved, I'm afraid to even sideload a different MJB 4.3 on mine.
You might just have to suck it up and send it off for a J-tag service. I've never done it, but I think others here have.
here's the link I've seen most.
http://www.ebay.com/itm/Unbrick-AT-T-SGH-I747-S3-SGH-T999-JTAG-service-I747-T999-Hard-Brick-Fix-USA-/160896407164
Sorry for your loss.

Michael503 said:
I don't know. I've never bricked a phone. As I understand it, 4.3 BL blows e-fuses making it impossible to downgrade. If that is in fact an accurate description, then even if you were to get it to boot via SD card and installed 4.1.1, it would brick it again (double brick?)
Considering the dangers involved, I'm afraid to even sideload a different MJB 4.3 on mine.
You might just have to suck it up and send it off for a J-tag service. I've never done it, but I think others here have.
here's the link I've seen most.
http://www.ebay.com/itm/Unbrick-AT-T-SGH-I747-S3-SGH-T999-JTAG-service-I747-T999-Hard-Brick-Fix-USA-/160896407164
Sorry for your loss.
Click to expand...
Click to collapse
I am trying to learn more about it but my "initial" understanding is that the "blown efuse" thing is that you can no longer boot from an earlier bootloader but it doesn't "damage" anything else. Therefore, since I already have a phone in that state but it can boot off the SD card I'm wondering if it doesn't make things worse to flash a 4.1 stock image. It would still fail to boot via EMMC but then boot off SD? Then the OTA could "possibly" happen? I doubt it is possible or someone would have posted about it but I haven't seen that you definitely CAN'T do it so I am continuing to look.

Reverting to 4.3 from official 4.4.2

I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?

gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though

zz1049 said:
Yep DONT UPDATE IF YOU DONT WANT ANY CHANGES!
edit; I think there will be a patch soon enough though
Click to expand...
Click to collapse
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.

gaww said:
I would not think of "updating" and get stuck with KNOXed bootloader. Absent that, i do not see why reverting would be a problem, but I have read otherwise.
That was my reason for asking.
Click to expand...
Click to collapse
Reason being is that the boot loader does not permit loading the old version of android onto it. If you update and then tried to flash the old Raum 4.3 it will cause errors and will ask you to reinstall the firmware, which is basically just the recovery part. 4.3 will flash this part of the image but then the rest of it will have problems. A lot of custom ROMs have been out there that run on 4.3 kernels but are running 4.4 ROMs and these are really actually 4.3. In those cases you can easily revert to stock 4.3. However, if you have updated then through Samsung software it will update the boot loader and you will no longer be able to revert.
For AT&T it is available to river, or at least reflash 4.4. I'm sure this will be fixed in time however at this point there is a lock or warning that has not been cracked basically. (Knox counter etc,)

gaww said:
I have read that after even just flashing 4.4.2 update, it will not be possible to revert (nandroid) to any 4.3 ROMs. If true - why if firmware the same ?
Click to expand...
Click to collapse
This is what I've read: if you update to official 4.4.2, you cannot flash back to official 4.3 in Odin. Likewise, if you updated to official 4.3, you cannot Odin back to official 4.2.2. If you try to, you'll soft brick. The Knox-secured bootloaders prevent Odin from successfully flashing a previous version.
Now, if you do this and therefore soft-brick, you need to pull the battery and re-enter Odin mode. Then you must Odin-flash a custom recovery (luckily there are some Odin-flashable recovery files out there). Then, after another battery pull, you need to manually boot into your custom recovery and flash a custom rom (or restore a Nandroid). This will save your soft brick.
What we don't know, because it hasn't been released yet, is if the official 4.4.2 tar file would successfully flash in Odin if you already have the 4.4.2 Knox bootloader.

How to unroot S3 with JB 4.3 and back to stock?

I have an ATT S3 SGH-I747. Some time ago I flashed the leaked 4.3 rooted with no KNOX.
No problems with it, but I want to get back to stock to get OTA updates in the future.
So far, it looks like I have to:
1-Run triangle away to reset counter
2-Flash the stock ROM.
3-Factory reset.
Is this good enough? Some extra step I have to do because of the insecure kernel I have?
I've been doing a lot of research and I'm still afraid to brick my phone if I try to do it.
If the above process is OK, which ROM should I flash? Just the original that came with the phone? I believe it was 4.0.4. Can I flash something newer?
I'll appreciate any help.

mito57 said:
I have an ATT S3 SGH-I747. Some time ago I flashed the leaked 4.3 rooted with no KNOX.
No problems with it, but I want to get back to stock to get OTA updates in the future.
So far, it looks like I have to:
1-Run triangle away to reset counter
2-Flash the stock ROM.
3-Factory reset.
Is this good enough? Some extra step I have to do because of the insecure kernel I have?
I've been doing a lot of research and I'm still afraid to brick my phone if I try to do it.
If the above process is OK, which ROM should I flash? Just the original that came with the phone? I believe it was 4.0.4. Can I flash something newer?
I'll appreciate any help.
Click to expand...
Click to collapse
Please check your phone's settings for your firmware version and let's know what you have under Android version, baseband version and build number. I expect the Android version should be 4.3, baseband I747UCUEMJB and build number ...MJ2 but please confirm all the same.
If the above details are correct, then you should be able to safely Odin to ver. 4.1.1. You do not need to run Triangle Away to flash a stock ROM but the other 2 steps are spot on. Once you are on stock 4.1.1, you can get an OTA update to the latest version. I would also advise you free unlock your phone before upgrading, if not done already, as you can only free unlock on 4.1.1. Before proceeding, however, please check and confirm your phone's current firmware settings. A different route may be required if you already have the 4.3 MJB bootloader.

Larry2999 said:
Please check your phone's settings for your firmware version and let's know what you have under Android version, baseband version and build number. I expect the Android version should be 4.3, baseband I747UCUEMJB and build number ...MJ2 but please confirm all the same.
If the above details are correct, then you should be able to safely Odin to ver. 4.1.1. You do not need to run Triangle Away to flash a stock ROM but the other 2 steps are spot on. Once you are on stock 4.1.1, you can get an OTA update to the latest version. I would also advise you free unlock your phone before upgrading, if not done already, as you can only free unlock on 4.1.1. Before proceeding, however, please check and confirm your phone's current firmware settings. A different route may be required if you already have the 4.3 MJB bootloader.
Click to expand...
Click to collapse
Thanks a lot for your help.
This is what I have:
Android Version: 4.3
Baseband Version: I747UCUEMJ2
Kernel Version: 3.0.31-1804024
Build Number: JSS15J.I747UCUEMJ2
SELinux status: permissive
That's all I can see in "About Device" I hope that's what you need.
You say no need to run Triangle Away. I still would like to reset the counter. Any risk in doing it?

mito57 said:
Thanks a lot for your help.
This is what I have:
Android Version: 4.3
Baseband Version: I747UCUEMJ2
Kernel Version: 3.0.31-1804024
Build Number: JSS15J.I747UCUEMJ2
SELinux status: permissive
That's all I can see in "About Device" I hope that's what you need.
You say no need to run Triangle Away. I still would like to reset the counter. Any risk in doing it?
Click to expand...
Click to collapse
Yes, that's precisely the info I need. You don't have the 4.3 bootloader yet so you should be able to safely Odin back to 4.1.1. There is no risk in resetting your flash counter. Usually, however, flashing a complete stock image should reset the flash counter. The only thing that can't be reset, once tripped, is your warranty bit. If your flash counter doesn't reset to zero, you can run Triangle Away. You can go to sammobile.com and download the Odin flashable 4.1.1 file (i747UCDLK3). Also download Odin from the thread below and then use it flash the UCDLK3 tar file. When you've successfully done this, please remember to free unlock your phone (if not done already) prior to taking any OTA updates.
http://forum.xda-developers.com/showthread.php?t=1722686

Larry2999 said:
Yes, that's precisely the info I need. You don't have the 4.3 bootloader yet so you should be able to safely Odin back to 4.1.1. There is no risk in resetting your flash counter. Usually, however, flashing a complete stock image should reset the flash counter. The only thing that can't be reset, once tripped, is your warranty bit. If your flash counter doesn't reset to zero, you can run Triangle Away. You can go to sammobile.com and download the Odin flashable 4.1.1 file (i747UCDLK3). Also download Odin from the thread below and then use it flash the UCDLK3 tar file. When you've successfully done this, please remember to free unlock your phone (if not done already) prior to taking any OTA updates.
http://forum.xda-developers.com/showthread.php?t=1722686
Click to expand...
Click to collapse
Just an update. I run Triangle away and now the counter is on zero and the status is showing "official". I didn't expect that. I'm thinking in just wait until the 4.4 update is released (assuming it does) and take my chances with Kies to make it.
If it does not work I still have the option to flash to 4.1 and do it the other way.
I believe it won't update with the regular OTA in it's current state because I have CWM.

mito57 said:
Just an update. I run Triangle away and now the counter is on zero and the status is showing "official". I didn't expect that. I'm thinking in just wait until the 4.4 update is released (assuming it does) and take my chances with Kies to make it.
If it does not work I still have the option to flash to 4.1 and do it the other way.
I believe it won't update with the regular OTA in it's current state because I have CWM.
Click to expand...
Click to collapse
OTA is hardly likely to work if the phone is not in (complete) stock state. The good thing, however, is that when Kit-Kat (and other future upgrade) is eventually rolled out for this device, the good guys in the development community can be trusted to ensure a manual update option is available.

[Q] Rooted at Jellybean, no KitKat update from AT&T. How to get KitKat

My galaxy siii was rooted before kitkat was out, and I have been using it until now and have not yet update to KitKat yet because AT&T is not part of it any more.
How do I get KitKat on my phone? Do I have to unroot the phone and put it back into AT&T mode to download or what should I do?

this might help.
remember:READREADREAD
BACKUPBACKUPBACKUP
http://forum.xda-developers.com/showthread.php?t=1802160
good luck
err on the side of kindness

You will need to unroot your phone and have the stock recovery.

Thank you for both replies gentleman

audit13 said:
You will need to unroot your phone and have the stock recovery.
Click to expand...
Click to collapse
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.

Id recommend flashing the 4.3 firmware via Odin to begin with. Its starting to seem like a lot of people who even just have to unroot are having problems with the ota. I think Odin flashing stock 4.3 will give the best chance of a successful update.

mwrobe1 said:
I might add to this...if you removed any stock carrier or vendor apps from 4.3 while being rooted...you'll have to restore them via a Titamium Backup or some other way or the OTA update will not install properly. (I realized that the OTA update from 4.3 to 4.4.2 will patch these apps to update them to 4.4.2 compatibility)
If you can't do that or if its unreasonable to do that based on the way the phone was modified while rooted...I suggest flashing the stock 4.3 rom via Odin and then take the OTA.
Click to expand...
Click to collapse
I am having this issue. I rooted on 4.3 and removed Google books and newsstand. I then uprooted and did a factory reset , so everything in download mode says "official" but the apps were still missing so I downloaded them from the play store. My question is will this let me get the OTA now or do I have to push the apps to the /system directory somehow? Also if I flash the 4.3 ODIN tar file, will it trip my warranty bit? It's at 0 right now and want to keep it that way until my warranty is up.

The firmware shouldn't trip the bit, but I can't promise that. Im sure its confirmed one way or the other in its thread though.
As for those apps, they'd have to be system apps, so just installing normally won't help. More importantly though, they would also need to be the same version that was originally built into the firmware. The apps you mentioned have seen many updates and using the current versions will not work.

I got the phone 2 weeks ago and it came with 4.3 installed on it. Would I be able to use the current version and just push them to /system/app with titanium backup? I am trying to get the OTA without tripping any warranty or security measures.

[Q] APN not listed and cannot add

I was on CM 10.2.1
I upgraded to CM11 - I get no wireless data. My phone works but I have no APNs and I could not add them.
I tried SlimKat 9.0 same issue with the APN
I upgraded my CWM to 6.4.0.7 as I heard that caused issues when upgrading to CM11.
I bought Mobile Odin and flashed that way as I thought it might help.
Ive done the following to fix my APN
1) Loaded an old one from working CM 10.2.1
2) Run Root Tweak with the fix APN for CM11 checked
3) Done the airplane mode trick
4) Attempt to add one manually
Does anyone know why this is happening and more importantly how to correct this issue?
Yes I did pore through other threads on how to fix this but no avail.
Thank you

What is your bootloader and modem? Do you get data if you re-install your previous ROM?

audit13 said:
What is your bootloader and modem? Do you get data if you re-install your previous ROM?
Click to expand...
Click to collapse
Bootloader = I747UCDLK3
Modem = I747UCDLK3
Yes I get data when I load a backup of CM 10.2.1
Thanks

Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.

audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
Thanks for the quick reply. That sounds hard. From what I'm reading going back is treacherous.
So these are the steps.
1. Load this firmware via ODIN -> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.zip -- What about gapps? Is that in this zip?
2. Run triangle away. (Do I need to do this?)
3. Contact my carrier to unlock my sim. (If this is carrier unlocking ie taking my att phone to Sprint etc, why is this needed?)
4. Get OTA updates. Will this come automagically because I'm on 4.1.1 and does it matter if my flash counter is gt 1?
5. Root phone via Odin with this file CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5.
6. Install CWM if it went away when I went back to firmware - Of course it would because I'll factory reset my phone in step 1.
7. Flash away to a 4.4.4 Rom
Did I miss anything?
Step 4 is the one that scares me -- That one is out of my control. Either I get the OTA or I dont. Anyway I can "request" the OTA?
Thanks again
Be Well

From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.

audit13 said:
From your custom ROM, run triangle away to reset counter and change things back to official.
Now flash back to stock 4.1.1 using Odin. If your phone does not boot, you need to get into recovery, do a factory reset, and reboot the phone and go through the set up routine.
After loading stock 4.1.1, do this to sim unlock your phone for free: http://forum.xda-developers.com/showthread.php?t=2529200. If you have a code from ATT, you must be running a stock ROM or a custom ROM that is based on a stock Samsung ROM in order to enter the unlock code.
You must be on a stock ROM in order to take OTA updates. OTA updates are the safest way to obtain an updated bootloader and modem.
After updating to 4.3, you cannot downgrade the bootloader as doing so may brick the phone.
The choice is yours in terms of what you want to do. As you found out, some ROMs will not function properly without an updated bootloader and modem. Mixing modem and bootloader versions may also result in a bricked phone.
Click to expand...
Click to collapse
To stick with 10.2 or not to that is the question. Everytime I flash or do anything like this on my phone - I get a small lump in my throat knowing I'm dancing in the razors edge of bricking it.

I know how you feel, but I've done it enough times and just accept the fact that I may brick the phone. Jtag service would cost me around $75 so I'm willing to take the chance. I'd be less willing if the phone still has warranty.
Flashing back to stock and running OTA updates is the safest route.
If you don't sim unlock while on stock 4.1.1 and you want to sim unlock your phone in the future, you will need to be on a stock or virtually stock ROM in order to enter the unlock code.

Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.

ddunleavy2 said:
Used ODIN to go back to stock 4.1.1.
Got the OTA update to 4.3
I have my MMS and cellular data back
I'll stick on stock, unrooted 4.3 for a minute.
I should be available to root and update to CM11 or SlimKat or any 4.4 rom whenever I so desire and still keep cellular data.
My baseband is I747UCUEMJB. How can I find out my bootloader and modem versions on UNROOTED device?
Your help is much appreciated and your instructions were flawless.
Click to expand...
Click to collapse
In a terminal or adb shell you can enter this to check your bootloader:
Code:
getprop ro.bootloader
In a terminal or adb shell you can enter this to check your modem (should match the baseband your phone reports in About):
Code:
getprop gsm.version.baseband
I don't believe either of these commands require root unless stock has getprop locked down tighter that AOSP ROMs; I just entered them in a user shell.
There are a couple of firmware updates for your device beyond MJB, NE4 and NJ1. Some users, myself included, had GPS problems that were a bit of a pain to fix on newer 4.4 AOSP based ROMs with the MJB firmware, but data was ok with MJB. Also, you'll need newer firmware if you decide to test drive the lollipop alphas that are floating around. There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route. You're already on MJB so there's no going back

The terminal worked
Bootloader and baseband = I747UCUEMJB
What???? I might need more updates for all the roms out there.....ugggh.
"There are custom recovery flashable firmware updates on XDA from a trusted developer if you decide you need that, or you might want to take a couple more OTAs if you're more comfortable going that route."
If I decide to use these flashable firmware updates on XDA from a trusted developer or OTA its same as this: going forward and NEVER going backward when getting firmware updates?, yes?

yes. downgrading bootloader will almost certainly cause a brick.
"all i can really do , is stay out of my own way and let the will of heaven be done"
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
audit13 said:
Data does not work on ROMs beyond cm10.2 because your bootloader and modem to too old.
I recommend flashing back to stock 4.1.1, sim unlock your phone if it is not already sim unlocked, and run OTA updates to at least 4.3, then install recovery and CM11.
Click to expand...
Click to collapse
+1
"all i can really do , is stay out of my own way and let the will of heaven be done"

You guys are on point.
Last night I received another OTA to 4.4.2.
Baseband now at NE4.
Thanks again for taking the time to answer all this -- Really really appreciate it.
EDIT: Can I still use this to root my phone via ODIN or is there a different process for this baseband?
CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5
I load this into ODIN, plug my phone in download mode and root away. Does either the file I use change or do I have to use something other than ODIN?
Thanks again

To get root, I would flash a custom recovery and flash supersu from recovery, then let supersu disable know.
The file you named looks to be outdated as it refers to the s3 as d2att. Since unified builds were released, the s3 is now referred to as the d2lte.

I have ROM Manager installed. It has an option to "Flash Clockworkmod Recovery". I just tried it and it failed and I think thats because I dont have root. In the past I've had to root my phone via ODIN, then flash custom recovery then MOD away.
In the past I rooted the S3 via ODIN. With this new 4.4.2 version do I still root via ODIN provide I find the correct file because -> CF-Auto-Root-d2att-d2uc-samsungsghi747.tar.md5 this one is probably for a 4.1.1 version phone?

I would not flash anything for the d2att at this point.
Try this:
Download the latest tar.md5 file from here: https://goo.im/devs/philz_touch/CWM_...Edition/d2lte/
Download supersu zip from here and place it onto an external SD card or copy it to the phone's internal storage: http://download.chainfire.eu/695/SuperSU/
In Odin, uncheck everything except f.reset time. Flash Philz. When you see reset in the status window, remove USB cable, pull battery, replace battery, boot into recovery, flash supersu, reboot.

I am fairly certain that AOSP, or at least CM, de-unified in the past few months. Not that it matters much, other than for the confusion it causes.