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.

[Q] Trying to downgrade from 4.4.2 (Cyanagenmod 11) to 4.1.2 stock (T999UVDMD5)

As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?

huz666 said:
As you'll soon discover, I'm a noob. I stupidly took the OTA update on my Samsung Galaxy S3 T-Mobile T999 from 4.1.2 to 4.3. Since doing so mine and my wife's phone (did the same thing to her also) gets in a mess after being connected to the car stereo bluetooth and prevents outgoing calls unless the phone is rebooted.
So to try to solve this, I rooted the phone and installed CM 11, so now I'm on 4.4.2. This didn't help the issue either and instead is worse at connecting to the bluetooth.
I want to get my phone back to the stock 4.1.2 rom, which I got from sammobile (PDA T999UVDMD5) or at worst back to the 4.3 stock rom (PDA T999UVUEMJC).
This morning I tried to flash T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar using ODIN 307 but it failed almost instantly with an Fail! Auth message.
I also tried to flash CM 10.1 zip on my SD card using ClockworkMod Recovery v 6.0.4.5 but again it failed almost instantly (sorry I didn't take note of the error).
So now I'm back to CM 11. So any suggestions for how to get back to either of the stock roms?
Click to expand...
Click to collapse
If you are getting errors in both odin and cwm, it sounds like it is a root issue. In other words, it sounds like the apps are being denied access to root and therefor cannot flash. Both odin and cwm are able to generate logs so you can tell the reason for the fail. Personally, I would recommend flasing twrp recovery instead of cwm since it seems to simplify alot and is a little better for our device. Without knowing exactly why the flash is failing, i would just recommend to try and re-root the phone again.

Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.

Perseus71 said:
Did you put the phone in Downloading mode before connecting to the Odin ?
Do not try to flash 4.1.2 ever. It will brick your phone.
Click to expand...
Click to collapse
Yes the phone was in downloading mode. I couldn't find any posts that thought that I would brick my phone for sure by downgrading so I thought I would try. Could I go back to the 4.3 Stock ROM with some degree of confidence?

Yes you can go back to 4.3 Stock.

Perseus71 said:
Yes you can go back to 4.3 Stock.
Click to expand...
Click to collapse
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.

huz666 said:
So I'm now back to Stock 4.3 by doing a flash via Odin. I did (stupidly) try to then go back to 4.1.2 again using Odin having put the phone in USB debugging mode first but I still got the same Auth Fail error.
Thanks for all the help.
Click to expand...
Click to collapse
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk

serio22 said:
You cannot downgrade like that once you have updated to official 4.3 firmware, no offence but why would you try it even after Perseus said not to? Anyway if you want to go back to 4.1.2 so badly just download a 4.1.2 ROM and flash it in recovery
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
.
Thanks for the advice. I think I'll just quit while I'm only slightly behind now and remain on 4.3 Stock. I appreciate everyone's help and suggestions.

Downgrade from CM11 4.4.2 to 4.3 on I747
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747

You seriously need to do some reading
Sent from my SGH-T999 using Tapatalk

nitagro said:
I went from 4.3 stock to CM11 on my i747 but i didnt like the update. So i am trying to go back to 4.3 however whenever i try to install the 4.3 zip file thru twrp or CWM, it fails. As far as i know there is no odin file for going back. I tried to flash rogers 4.3 file through odin (thinking i would flash at&t modem later) but that also failed.
I would appreciate any help on how to install 4.3 once 4.4.2 has been installed on an i747
Click to expand...
Click to collapse
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.

Perseus71 said:
For One, you are on the wrong forum. This is for T-Mobile's S3 not AT&T. Second, Like @passtheknowledge said, you really need to do significant research and reading here on XDA.
Click to expand...
Click to collapse
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.

nitagro said:
I was up all night reading and trying all the suggestions that have been posted so far. Nothing worked. I would appreciate if someone can throw some light on what might be wrong.
Click to expand...
Click to collapse
Please Read through this Thread. For Future Reference, all Odin Files for S3 in general are looked up by unique Keyword Root66. That thread is the right place for you to post errors or issues. If there's no 4.3 image for your phone there, you can post a request as well.
For your immediate Problem, there is a an alternate ATT StockMod Rom by @saranhai Please see this thread. Pay particular attention to the mandatory requirement of flashing a particular modem beforehand.

[Q] Flashed the stock rom but it is still showing cm 11 splash screen. . .

So, I'm not a complete noob to flashing roms/rooting devices. I flashed cm 11 to my s3, and decided I wanted to go back to stock via Odin. For some reason when I tried to turn on my device it was still showing the cm 11 splash screen and wouldn't proceed any further. It isn't technically bricked. I guess this would be classified as a boot loop to the nth degree. I tired to boot in recovery mode and wipe the cache partition and all user data to the same cm 11 robot taunting me. When I tried the process (flashing stock vi Odin) again to possibly fix whatever might have been a miss, I got the error message on the download screen "secure check fail: sb12." On the download mode screen it also says I am running the official system rom. I don't know what steps I need to take from here to get my phone to actually boot via the stock rom. Has anybody else had this issue or similar? Any help in resolving this would be greatly appreciated.

Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?

audit13 said:
Is your phone a i747? If you are you running a stock 4.3 bootloader on your i747, you can't use Odin to flash back to stock unless the ROM was specifically designed to be flashed in Odin.
What is shown on the screen in download mode?
Click to expand...
Click to collapse
I was under the impression the rom I was attempting to flash was indeed intended for Odin. It is the SGH-I747.
The download screen states,
Product Name: SGH-I747
Custom Binary: Custom
System Status: Official
Qualcom Secure Boot: Enable
Warranty Bit: 1
Bootloader AP SWERV: 2
Here is an added bit of fun, in the midst of the process I accidentally checked "Nand erase all," in Odin at one point.

Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486

audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
My next question would be how can I move the zip files I download to the internal storage of my phone to flash them through Philz Touch?

Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809

sjthuss said:
Have you tried using kies?
http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
I did. It said the the device couldn't be updated, or something to that effect.

Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.

audit13 said:
Kies will not work without a stock recovery or a rooted phone from my experience.
I would be surprised if kies can restore your phone as ATT never released a full 4.3 stock ROM. ATT only made 4.3 available via an OTA update.
Click to expand...
Click to collapse
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.

audit13 said:
Based on the information provided, your phone is running a stock ATT 4.3 bootloader. The CM11 splash screen is still showing up because the flash did not actually happen. You're lucky your phone was not bricked in the process of using Odin. I recommend not using Odin to flash a ROM that tries to alter the bootloader.
I recommend flashing a custom recovery such as Philz Touch in Odin and flashing a different KK ROM such as Valudis.
If you want to get back to stock, try this: http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So, I know there is a "thanks," button but I feel like that would be a little too informal for how much I appreciate your help! I downloaded ADB to move the rom (I went with AOKP because it was the first one that worked) to my phone, flashed it using TWRP and...BAM! We are back in business. Thanks for the direction, I thought I had a nice, new, shiny brick on my hands for about two days.

sjthuss said:
I don't know about AT&T, but I'm on Telus in Canada and I used kies to revert back to stock 4.3 with CWM recovery and phone rooted, and it worked no problem.
Click to expand...
Click to collapse
Canadian carriers use the i747m while att users get the i747.
The Canadian carriers did release a full 4.3 ROM unlike att who did not.

unbrick S3 sgh-i747m

hi
I think I just brick my roger SGH-I747m, I try to bring my phone back to 4.3 from 4.4.2, so I try to flash a 4.3 bootloader from twrp 2.6.3.0; but if give me a error message, then I took the battry out, and I can't start my phone anymore. Is there anything I can do to unbrick my S3 cause the phone is not mine and I will be kill from my sister if I told her I brick her phone. Please help!!!

Was it running stock 4.4.2 before you tried to go back to 4.3? If it was, there is no way to unbrick from 4.4.2 at the moment.
If you need it fixed really fast, a jtag service would be the quickest. Ming Wireless in downtown Toronto provides excellent service.

Actually, there may be hope here. Try the 4.4.2 256mb debrick.img in the debrick thread. Follow instructions there. Also please post there for further assistance.
There have been a couple of bricks recovered on NE4 firmware. As long as you didnt flash the new modem on 4.3 firmware there is hope.

DocHoliday77 said:
Actually, there may be hope here. Try the 4.4.2 256mb debrick.img in the debrick thread. Follow instructions there. Also please post there for further assistance.
There have been a couple of bricks recovered on NE4 firmware. As long as you didnt flash the new modem on 4.3 firmware there is hope.
Click to expand...
Click to collapse
If the OP was on stock 4.4.2 and tried to flash the 4.3 bootloader, would it actually flash the bootloader? If it did flash the 4.3 bootloader, would the debrick still work since the OP would have stock 4.4.2 with a 4.3 bootloader?

If he flashed it via custom recovery, and it wasn't protected by the assert function in the script, yes it could have flashed the older bootloader. Its not the attempt that bricks devices. Something has to actually be written (or corrupted) for it to brick. The only thing that worries me here is the modem. We know we cannot fix a device if it has the new modem flashed onto 4.3 firmware. However, I am not sure about flashing a full 4.3 package. If it does not include the modem, they will have ended up with the same resulting setup. Bust since it was done backwards, I do not know if it will be recoverable or not.
(I hope that makes sense)

[Q] Downgrade from Custom 4.4.2 to stock 4.3 possible?

Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.

zetrixNoob said:
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
Click to expand...
Click to collapse
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7

EverDawn4 said:
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
Click to expand...
Click to collapse
I already tried that but still the booting stuck on the t-mobile logo. I read somewhere that locked bootloader don't let you downgrade to previous version. Is this true?

In that case. Try finding a 4.3 rom that's close to stock.
Sent from my Nexus 7

The locked bootloader is always in stock firmwares i.e 4.3 for the Note 2 but not in custom roms meaning u can even install Lollipop custom on it & downgrade smoothly, i have done that many times. The problem is 4.3 stock firmware has locked bootloader hence downgrading still keeps u in 4.3 bootloader even if u remove all the KNOX files.

Stuck trying to downgrade from custom 5.1.1 to stock 4.3
Hi, i have a problem like this, upgrade to a custom 5.1.1 and then sell the phone, the new owner wants to have it stock, i try to downgrade to 4.3 but i cant, in odin i set the phone to flash it but seems like it doesn`t recognize the phone and i dont know why, so, i decided to try in recovery mode installing from the sd card but the sistem abort, so, i don`t know what to do, i`ll appreciates any help, sorry for my english, i do my best. (i have root access before upgrated to 5.1.1).