Develop Bugs

[Q] Official 4.3 Upgrade Issues

I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!

phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...

Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.

As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

I had the same problem
I just had this same problem and was lucky enough to fix it!!!!

vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l

I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you

vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it

Have you tried the auto root course??
Sent from behind you

Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.

Co-author root didn't work, and nor did Root66

I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!

This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.

DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?

You can try first wiping just dalvik and cache, then try factory reset.

Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.

I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.

I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?

DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?

bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk

How to have custom recovery

Hey guys its been a week since i bought the note 2 and i rooted it. But i cannot find how to flash a custom recovery tutorial anywhere. I am on jellybean 4.1 and the rest of the details (firmware etc) can be found on the screenshots attached..
I would highly appreciate if someone can send me a link to the guide for flashing.. thanks a lot in advance
Sent from my GT-N7100 using XDA Premium 4 mobile app

Just simply flash via Odin
You can choose CWM, Philz touch or TWRP

RazaVakil7995 said:
Hey guys its been a week since i bought the note 2 and i rooted it. But i cannot find how to flash a custom recovery tutorial anywhere. I am on jellybean 4.1 and the rest of the details (firmware etc) can be found on the screenshots attached..
I would highly appreciate if someone can send me a link to the guide for flashing.. thanks a lot in advance
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You got two options either root your phone while being on 4.1.2 or upgrade to official Indian 4.4.2 and then root it.Ofcourse once you root your current 4.1.2 you can try custom 4.4 ROM and if you don't like it you can go back to 4.1.2 or flash a 4.3 custom ROM. To root your 4.1.2 rom read this guide.If you decide to upgrade to 4.4.2 Indian firmware download it from here.
To flash the 4.4.2 ROM on your phone download it from the above link(there are 3 links where the ROM is uploaded) ,use any of the links and download the zip file,extract it you'll get a tar file,put your phone into download mode ,open odin v3.09 on pc and flash the official stock rom by checking the AP tab on odin.You can find tutorials on youtube on how to use odin to flash official stock firmware so just look them up if you need it.Once you flash stock ROM you can root your phone via this guide.
Okay so now things to remember.If you root your 4.1.2 ROM and want to try 4.3 or 4.4 custom ROM you need to flash MJ5 bootloader in order to have working wifi.Bootloader is flashed directly on your mother board and it cannot be downgraded only be upgraded.MJ5 is the last 4.3 bootloader which is KNOX free(what is knox ,blah blah,you can read about it on google).Advantage of MJ5 is you can try 4.1.2/4.3/4.4.2 rom and your warranty and knox remain intact but if you upgrade to official 4.3 or 4.4.2 ROM you'll be on knoxed bootlooader which means you cannot downgrade to 4.1.2 anymore plus rooting a phone with knoxed bootloader will trigger knox 0x1 and your warranty if any will be void (no way yet to reset Knox).So if you have warranty on your phone then my advise is root your 4.1.2 Rom,download any 4.3 or 4.4.2 custom ROM,you wont have wifi working then flash the MJ5 bootloader from here and read this post on how to flash bootloader.
I know it's a lot of info to you but your best guide is self reading from the above links i hooked you up with.Also read comments from people cause that's how I learned I read and read a lot before i jumped the rooting bandwagon cause wanted to make sure i don't brick my phone. Ofcourse whenever in doubt STOP RIGHT THERE and ask us.Dont attempt things that you are not sure of.Good luck.

Thanks for the help
singhpratik87 said:
You got two options either root your phone while being on 4.1.2 or upgrade to official Indian 4.4.2 and then root it.Ofcourse once you root your current 4.1.2 you can try custom 4.4 ROM and if you don't like it you can go back to 4.1.2 or flash a 4.3 custom ROM. To root your 4.1.2 rom read this guide.If you decide to upgrade to 4.4.2 Indian firmware download it from here.
To flash the 4.4.2 ROM on your phone download it from the above link(there are 3 links where the ROM is uploaded) ,use any of the links and download the zip file,extract it you'll get a tar file,put your phone into download mode ,open odin v3.09 on pc and flash the official stock rom by checking the AP tab on odin.You can find tutorials on youtube on how to use odin to flash official stock firmware so just look them up if you need it.Once you flash stock ROM you can root your phone via this guide.
Okay so now things to remember.If you root your 4.1.2 ROM and want to try 4.3 or 4.4 custom ROM you need to flash MJ5 bootloader in order to have working wifi.Bootloader is flashed directly on your mother board and it cannot be downgraded only be upgraded.MJ5 is the last 4.3 bootloader which is KNOX free(what is knox ,blah blah,you can read about it on google).Advantage of MJ5 is you can try 4.1.2/4.3/4.4.2 rom and your warranty and knox remain intact but if you upgrade to official 4.3 or 4.4.2 ROM you'll be on knoxed bootlooader which means you cannot downgrade to 4.1.2 anymore plus rooting a phone with knoxed bootloader will trigger knox 0x1 and your warranty if any will be void (no way yet to reset Knox).So if you have warranty on your phone then my advise is root your 4.1.2 Rom,download any 4.3 or 4.4.2 custom ROM,you wont have wifi working then flash the MJ5 bootloader from here and read this post on how to flash bootloader.
I know it's a lot of info to you but your best guide is self reading from the above links i hooked you up with.Also read comments from people cause that's how I learned I read and read a lot before i jumped the rooting bandwagon cause wanted to make sure i don't brick my phone. Ofcourse whenever in doubt STOP RIGHT THERE and ask us.Dont attempt things that you are not sure of.Good luck.
Click to expand...
Click to collapse
Wow that's a lot of info you provided there, thanks. I am not new to rooting as far it goes I have rooted and flashed many roms on my galaxy s advance and my micromax A87 before that. But note 2 was a flagship device so there are many complications that come along which got me confused. As for now, I have my rooted 4.1.2 stock rom along with cwm recovery flashed via rom manager. I am planning to flash either DN3 or the Xperia Z-ized rom. So my question is: do I have to flash mj5 bootloader to flash DN3 and xperia z-ized or can I directly flash it from cwm (with factory reset and necessary wipes of course)?
BTW, I have heard that knox is a security application that prohibits rooting on samsung phones. It also had a reward for $18k for those who can bypass the knox on the S5 and root it. If I am right, then I think I am fairly acquainted to knox.
Once again, thanks a lot for helping! Appreciate it

RazaVakil7995 said:
Wow that's a lot of info you provided there, thanks. I am not new to rooting as far it goes I have rooted and flashed many roms on my galaxy s advance and my micromax A87 before that. But note 2 was a flagship device so there are many complications that come along which got me confused. As for now, I have my rooted 4.1.2 stock rom along with cwm recovery flashed via rom manager. I am planning to flash either DN3 or the Xperia Z-ized rom. So my question is: do I have to flash mj5 bootloader to flash DN3 and xperia z-ized or can I directly flash it from cwm (with factory reset and necessary wipes of course)?
BTW, I have heard that knox is a security application that prohibits rooting on samsung phones. It also had a reward for $18k for those who can bypass the knox on the S5 and root it. If I am right, then I think I am fairly acquainted to knox.
Once again, thanks a lot for helping! Appreciate it
Click to expand...
Click to collapse
Since you are on stock 4.1.2 MJ5 is required for wifi to work.i learned 2 weeks ago that even mj5 is not required as previously thought by us at least not while flashing 4.4.2 TW rom.When you flash 4.4.2 custom ROM you wont have wifi working,then flash custom kernel like agni or nadia and wifi works flawlessly so one doesn't need to flash mj5 bootloader.I am not sure if this would work on 4.3 ROM you could try xperia z'd 4.3 custom ROM then flash a compatible 4.3 custom kernel and see if wifi works if it does you're set.This was new to most of us so I asked the person who told me about this how did he manage to do this and he told me apparently custom kernels have some sort of wifi drivers on them so when we flash custom kernels on 4.4.2 ROM wifi works but it wont work on stock kernel unless you upgrade to MJ5 and on stock kernel.MJ5 is safe to flash anyways since its knox free bootloader.
Actually 4.3 and 4.4.2 note 2 phones and others got knox on them but we found a way to disable knox after rooting our phone SuperSu disables it but knox is triggered to 0x1 and there's no way to reset KNOX since it's concerned with the motherboard of the phone which is the heart and soul of out note 2.So that bounty you might be talking about how to reset it perhaps.Even if they succeed in reversing it doesn't necessarily mean it would work on note 3 or note 2 cause of the phones being of different hardware .i don't know the technicalities of this.

singhpratik87 said:
Since you are on stock 4.1.2 MJ5 is required for wifi to work.i learned 2 weeks ago that even mj5 is not required as previously thought by us at least not while flashing 4.4.2 TW rom.When you flash 4.4.2 custom ROM you wont have wifi working,then flash custom kernel like agni or nadia and wifi works flawlessly so one doesn't need to flash mj5 bootloader.I am not sure if this would work on 4.3 ROM you could try xperia z'd 4.3 custom ROM then flash a compatible 4.3 custom kernel and see if wifi works if it does you're set.This was new to most of us so I asked the person who told me about this how did he manage to do this and he told me apparently custom kernels have some sort of wifi drivers on them so when we flash custom kernels on 4.4.2 ROM wifi works but it wont work on stock kernel unless you upgrade to MJ5 and on stock kernel.MJ5 is safe to flash anyways since its knox free bootloader.
Actually 4.3 and 4.4.2 note 2 phones and others got knox on them but we found a way to disable knox after rooting our phone SuperSu disables it but knox is triggered to 0x1 and there's no way to reset KNOX since it's concerned with the motherboard of the phone which is the heart and soul of out note 2.So that bounty you might be talking about how to reset it perhaps.Even if they succeed in reversing it doesn't necessarily mean it would work on note 3 or note 2 cause of the phones being of different hardware .i don't know the technicalities of this.
Click to expand...
Click to collapse
How do you know all this man??

RazaVakil7995 said:
How do you know all this man??
Click to expand...
Click to collapse
Lurking around in xda and reading as much as I can and participating in discussions related to Knox.I was clueless to all this Knox and how it works.My previous phone was HTC HD2 so samsung note II was the first serious smartphone I owned so just wanted to be extra careful that I don't end up bricking my device so read and read and asked questions.

[Q]Need clarification for rooted rogers note 2, android 4.4

Hello, I recently just updated my Rogers SGH-i317M to 4.3, which then downloaded a system update which put it at 4.4. I was running Jedi X20, which is based on 4.1.2, when I first tried updating, I flashed the "4.3param_tz" file in odin, and was left with an error screen saying I need to recover using Kies, so I downloaded the official release, flashed via odin, and thats how I got to where I am now. I want to try the "Ditto Note 3" rom, "Sky Note Air 4.3", "Mean Bean" and "Beanstalk". My main question is, can I just start flashing these roms like I was before on 4.1.2, or do I need to use the specific kernel listed on their page? Before you needed a specific kernel to run a touchwiz rom or an aosp rom, so is it still the same? Or can I use my stock 4.4 kernel and try both aosp and tw roms now? If so could you point out the kernels I would need? And educate me on anything else I should know about before flashing 4.3 and 4.4 roms, (I'm not worried about warranty), this would be greatly appreciated. Thanks for your time in reading this and helping me out, much appreciated!!

Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.

just_visiting said:
Regardless of where u are, I'd Odin to Rogers stock KK 4.4.2. Then Odin Twrp recovery, boot into twrp recovery and flash SU v.1.99. Finally choose your rom and flash away. This way you are on the lastest KK 4.4.2 Bootloader and KK Modem/Baseband.
Click to expand...
Click to collapse
I did all that except flash SU 1.99, so I tried flashing SKynote Air and it didnt work, upon restarting my phone it said no os is available. So I tried restoring from the backup I made of the official 4.4.2 Samsung rom in twrp, didn't work. Tried Odin, didn't work. Then I tried flashing the Skynote rom again and it worked. So I'm afraid of flashing any other roms now.

Need Help getting to stock rom!

Ok this is my problem, I was on a custom rom because kikat was not released for my device. when it was I used odin and flashed the stock jelly bean rom I had. it worked and I went into settings and clicked update. when I came back to my tablet it had stock kikat 4.4.2. I went into download mode to add twrp and root. in download mode there was a new string of text after I flash twrp:
ODIN mode
product name:sm-t310_NA
current binary:
system status:
AP SEREV: A1
the "AP SEREV: A1" was new, For some reason twrp worked but i could not get root access so in twrp I restored a backup of my custom rom. so I gave it another try but when I tried to flash jelly bean, it gave me an error(FAILED) in oden and gave me a "invalid magic string" error in download mode.
What should i do, I am stuck on a custom rom I dont want. if it is a matter of flashing kikat in odin, then please direct me to the American SM-T310 kikat STOCK ROM file
thanks
ps if there is some new way of getting root in kikat that would also help.

androidhacker007 said:
Ok this is my problem, I was on a custom rom because kikat was not released for my device. when it was I used odin and flashed the stock jelly bean rom I had. it worked and I went into settings and clicked update. when I came back to my tablet it had stock kikat 4.4.2. I went into download mode to add twrp and root. in download mode there was a new string of text after I flash twrp:
ODIN mode
product name:sm-t310_NA
current binary:
system status:
AP SEREV: A1
the "AP SEREV: A1" was new, For some reason twrp worked but i could not get root access so in twrp I restored a backup of my custom rom. so I gave it another try but when I tried to flash jelly bean, it gave me an error(FAILED) in oden and gave me a "invalid magic string" error in download mode.
What should i do, I am stuck on a custom rom I dont want. if it is a matter of flashing kikat in odin, then please direct me to the American SM-T310 kikat STOCK ROM file
thanks
ps if there is some new way of getting root in kikat that would also help.
Click to expand...
Click to collapse
Try towel root http://forum.xda-developers.com/showthread.php?t=2784152

androidhacker007 said:
Ok this is my problem, I was on a custom rom because kikat was not released for my device. when it was I used odin and flashed the stock jelly bean rom I had. it worked and I went into settings and clicked update. when I came back to my tablet it had stock kikat 4.4.2. I went into download mode to add twrp and root. in download mode there was a new string of text after I flash twrp:
ODIN mode
product name:sm-t310_NA
current binary:
system status:
AP SEREV: A1
the "AP SEREV: A1" was new, For some reason twrp worked but i could not get root access so in twrp I restored a backup of my custom rom. so I gave it another try but when I tried to flash jelly bean, it gave me an error(FAILED) in oden and gave me a "invalid magic string" error in download mode.
What should i do, I am stuck on a custom rom I dont want. if it is a matter of flashing kikat in odin, then please direct me to the American SM-T310 kikat STOCK ROM file
thanks
ps if there is some new way of getting root in kikat that would also help.
Click to expand...
Click to collapse
This thread DOESNT belong here!!!
This thread must be moved on q&a

Srry can u move it plz
Sent from my SM-T310 using XDA Premium 4 mobile app

androidhacker007 said:
Srry can u move it plz
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are still looking for a 4.4.2 stock rom, try SamMobile.com. I used this one:
SM-T310 Canada 2014 July 4.4.2 T310XXUBNE9 T310XACBNE8
After that, I used this guide to root:
http://www.droidviews.com/root-galaxy-tab-3-8-0-sm-t310-on-kitkat/
and this for getting TWRP:
http://forum.xda-developers.com/showthread.php?t=2619518

Never, ever do an OTA update. You never know what sort of turd you are going to get. See the Knox fiasco, or my iPad 2 that is going to be a rifle target after a retard I loaned it to updated to 7-whatever.
Two things to try.
The Toolkit and this ROM.
If you already have a recovery on your Tab, this should be simple. Download one of the rooted versions of the ROM, get it on to your tablet (SD card preferred), wipe and install.
If all else fails, try GalaTab3. It WILL work, unless your mo-sheen is broken.
ETA: Whoa, does the stock Samsung 4.4.x ROM have Knox as well?

Sgh-747 bricked

I was trying to change the firmware of my S3 but in the middle of the process the computer went off. Now is bricked showing the KIES message, when a try to go back to stock using the only official firmware that is in Sammobile it says AUTH error.
The screen of the S3 in download mode says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD:NO
CURRENT BINARY:SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 2
It was running the 4.2.2 that I got via OTA but I can not use the same because I do not have access to the recovery mode. I think that if I could find a .tar 4.2.2 I could solve the problem. Please guys I need your help on this. Any suggestion o way to solve?

wmobility00 said:
I was trying to change the firmware of my S3 but in the middle of the process the computer went off. Now is bricked showing the KIES message, when a try to go back to stock using the only official firmware that is in Sammobile it says AUTH error.
The screen of the S3 in download mode says:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD:NO
CURRENT BINARY:SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE
WARRANTY BIT: 1
BOOTLOADER RP SWREV: 2
It was running the 4.2.2 that I got via OTA but I can not use the same because I do not have access to the recovery mode. I think that if I could find a .tar 4.2.2 I could solve the problem. Please guys I need your help on this. Any suggestion o way to solve?
Click to expand...
Click to collapse
Were you running 4.2.2 or 4.4.2? I thought the AT&T SGS3 (i747) went from 4.1.1 to 4.1.2 to 4.3 to 4.4.2 for official ROMs. The 4.1.1 stock ROM on sammobile was the last full release, all since have been updates. The WARRANTY BIT: 1 output would indicate it was on at least the 4.3 release if not one of the 4.4.2 releases; NE4, NJ1, or NJ2.
While I am waiting for a reply I will search to see if any of the devs created a 4.4.2 stock tar, I have seen in done with an older version, but it is a rare occurrence.

Simplest way to get the phone up and running would be to flash TWRP and then cm11. By booting CM11, you could determine the bootloader and modem. Once these two things are know, you may be able to flash an updated bootloader, modem, and ROM from TWRP.

dawgdoc said:
Were you running 4.2.2 or 4.4.2? I thought the AT&T SGS3 (i747) went from 4.1.1 to 4.1.2 to 4.3 to 4.4.2 for official ROMs. The 4.1.1 stock ROM on sammobile was the last full release, all since have been updates. The WARRANTY BIT: 1 output would indicate it was on at least the 4.3 release if not one of the 4.4.2 releases; NE4, NJ1, or NJ2.
While I am waiting for a reply I will search to see if any of the devs created a 4.4.2 stock tar, I have seen in done with an older version, but it is a rare occurrence.
Click to expand...
Click to collapse
To be sincere I am not pretty sure, I think it was 4.4.2. I can not enter to recovery so installing the last one through it is not an option.

wmobility00 said:
To be sincere I am not pretty sure, I think it was 4.4.2. I can not enter to recovery so installing the last one through it is not an option.
Click to expand...
Click to collapse
If you can get to download mode you could do as audit13 suggested and flash the TWRP.tar.md5 (custom recovery) with Odin or Heimdall and then flash either CM11 as he suggested, or one if enewman17's stock 4.4.2 roms.

thank you all guys. I installed TWRP then CM11 and now is back! I appreciate your help. Have the best wishes and Merry Christmas! Greetings

wmobility00 said:
thank you all guys. I installed TWRP then CM11 and now is back! I appreciate your help. Have the best wishes and Merry Christmas! Greetings
Click to expand...
Click to collapse
Yeah, I was about to suggest flashing twrp but glad to find that you have fixed it. I used this same method to recover a galaxy tab GT-P6210 a while ago