Develop Bugs

[GUIDE] Restore Bootloader Bricked S3 to Stock Firmware AFTER 4.3 update. No Jtag

Hello, I know there are many threads on restoring a bricked S3, some of them for hard bricks, and some for soft bricks. None of the guides I found by scouring these forums provided all of the answers I needed.
INFO PLEASE READ ALL
Here I hope to outline how I restored my T999 Tmobile S3 to stock firmware after the 4.3 MJC update, and after bootloader bricking the phone. I do assume you are capable of using ADB, ODIN and TWRP. I believe this method will work for other S3 models, but I have no ability to test it. If it will work, firmware and debrick IMGs will have to be found for the specific device. The T999 firmware and IMGs will NOT work with other devices. This will restore to stock UVUEMJC 4.3 firmware. Will not be rooted, but existing 4.3 roots for the device should work.
I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE. THE TOOLS USED IN THIS GUIDE HAVE THE POTENTIAL TO BRICK, OR OTHERWISE DAMAGE YOUR DEVICE. USE AT YOUR OWN RISK
So as context, I had been flashing different ROMS; then I updated to stock 4.3 UVUEMJC Firmware. This updated the bootloader, and installed the Samsung KNOX security upgrade. Both the bootloader and the KNOX are problems regarding rooting, rom installation, and downgrading (which I still have not achieved)
After upgrading, I installed a vanilla rootbox. I then attempted to flash the UVDMD5 bootloader at mnasledov's thread here: http://forum.xda-developers.com/showthread.php?t=2282603
Lacking my present understanding, of the 4.3/KNOX problems, I managed to brick my phone by effectively attempting to downgrade the bootloader. Phone appeared to be hard bricked.
I tried many things to fix the phone, these are what worked:
GUIDE:
1. Get a Class 10 MicroSD card and follow KAsp3rd's guide to boot from the SD card: http://forum.xda-developers.com/showthread.php?t=2439367
You should now be able to boot to download mode, recover, and system if it was undamaged when you bricked your phone.
2. Boot into download mode and install TWRP via ODIN
3. Boot into your new TWRP recovery. Do an ADB sideload of the KNOX removal script found in Kaito95's thread here: http://forum.xda-developers.com/showthread.php?t=2507931 Check the clear cache and clear dalvik recovery boxes. You have to do an ADB sideload, because your SD card is in use as a bootloader.
4. Use ODIN with Download Mode to Re-Partion by flashing the PIT file found in invisiblek's downloads here: http://forum.xda-developers.com/showthread.php?t=1848267
The Re-Partition box will have to be checked, and the PIT file loaded under Re-Partition. This is what I believe corrected the download mod fails I had been getting.
5. Use ODIN and Download mode to flash the original UVUEMJC firmware found in DocHoliday77's thread here: http://forum.xda-developers.com/showthread.php?t=1949687
6. In TWRP do a factory reset, and a fix permissions. Reboot into system, (without the SD card)
If all went well you should be in business!
If you see any error in my guide, or have another correction, please let me know. If I have posted this in the wrong section I'll be happy to move it.
I hope this helps you.
ROOTING:
So after fixing my phone via the steps above, I still wanted to root it. To root it I simply ODIN flashed mrRobinson's rooted/deKNOXED 4.3 stock rom from here: http://forum.xda-developers.com/showthread.php?t=1771687
It seemed very stable to me.
I then decided to use TWRP to install the CyanogenMod 10.2. If you choose to install CM, I believe you must use the 10.2 branch, because it is 4.3 based. Prior versions are not 4.3, and won't work with the 4.3 bootloaders. You can find the appropriate CM download by selecting your device here: http://download.cyanogenmod.org/ The T999 is d2tmo.
EDIT: YOU CAN RUN OLDER VERSIONS AFTER UPDATING TO 4.3.
This was pointed out to me by Adreaver. I personally am using rootbox 4.2.2 after having done the 4.3 official update. Any rom for the device should work, but certain lines may need be removed form the updater script. I am still looking into this.
NOTES
This has been confirmed to work on the T999L, but you need a different PIT file, and different firmware for the model. See @mrspock08 's post on page 2 of this thread for more info on the T999L
THANKS
I could not have debricked my phone or created this guide without referencing and using the work of several fine members of this forum. Particular thanks to:
@mnasledov for providing a thread with information about bootloaders.
@KAsp3rd for providing a way to boot from the SD card, enabling the entire rest of the debrick.
@Kaito95 for the deKNOX script.
@invisiblek for the PIT file for correctly repartitioning the phone.
@DocHoliday77 for the MJC 4.3 Stock Firmware mirror.
@mrRobinson for the rooted MJC Stock firmware
@Adreaver for correcting me that you can run an older version of android
And the threads of many many others who's work I read through while learning about how all of this works.

Nice guide. I think @DocHoliday77 could use this method because I believe he bricked his phone the same way.
Oh, and I believe you might have made a typo SDB is actually ADB Android debug bridge.

sswb27 said:
Nice guide. I think @DocHoliday77 could use this method because I believe he bricked his phone the same way.
Oh, and I believe you you might have made a typo SDB is actually ADB Android debug bridge.
Click to expand...
Click to collapse
Of course! You're right, a typo on my part. Thanks for pointing that out!

TronMinecraft said:
Of course! You're right, a typo on my part. Thanks for pointing that out!
Click to expand...
Click to collapse
No problem, I made more then 1 mistake when I made my first page. So your doing good with only 1.

TronMinecraft said:
Hello, I know there are many threads on restoring a bricked S3, some of them for hard bricks, and some for soft bricks. None of the guides I found by scouring these forums provided all of the answers I needed.
Click to expand...
Click to collapse
Cool guide! Thanks for the write-up!

Thanks for guide and explaining very clearly
Surely if it worked for you then it is going to help others too
Thanks once again
Sent from my SGH-T999 using Tapatalk

Nice writeup. I assumed that a bootloader brick was the point of no return, thanks for proving me wrong.
Worth noting that you can flash any d2tmo ROM on the new bootloaders, even cm9 or 4.0.4 tw, but you may need to remove asserts from the updater-script.
Sent from my SGH-T999 using XDA Premium 4 mobile app

Great tutorial. An extreme amount of time went into this I can see. Hopefully it'll be able to get @DocHoliday77 back up and running tho. I miss that guy!
Sent from my Nexus 5 using Tapatalk

TheLastSidekick said:
Great tutorial. An extreme amount of time went into this I can see. Hopefully it'll be able to get @DocHoliday77 back up and running tho. I miss that guy!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I spent a few days on it, I hope it helps people. I hope it gets Him back up and running, his MJC mirror was instrumental in my fix.
Adreaver said:
Nice writeup. I assumed that a bootloader brick was the point of no return, thanks for proving me wrong.
Worth noting that you can flash any d2tmo ROM on the new bootloaders, even cm9 or 4.0.4 tw, but you may need to remove asserts from the updater-script.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For most phones the bootloader brick would require JTAG; fortunately several of the Samsungs have the SD as default boot.
And you can flash older ROMs? I was unaware of this; every attempt I've made to run something older has resulted in a getprop(ro.bootloader) error. But that updater script assert makes sense. Thank's for letting me know. I'll check that out and add it to the OP

so what?
i want to update my phone to T999UVUEMJC 4.3 firmware
currently i'm on T999UVDMD5 4.1.2
is it safe to update using Odin?
sorry for noob question

Restoring bootloader to bricked S3 T999L
TronMinecraft said:
Here I hope to outline how I restored my T999 Tmobile S3 to stock firmware after the 4.3 MJC update, and after bootloader bricking the phone. I do assume you are capable of using ADB, ODIN and TWRP. I believe this method will work for other S3 models, but I have no ability to test it. If it will work, firmware and debrick IMGs will have to be found for the specific device. The T999 firmware and IMGs will NOT work with other devices. This will restore to stock UVUEMJC 4.3 firmware. Will not be rooted, but existing 4.3 roots for the device should work.
Click to expand...
Click to collapse
Great guide, thanks a ton to @TronMinecraft for this writeup! I've been lucky and haven't bricked my S3 T999L (the T-Mobile LTE variant), but a relative wasn't so lucky. She took the OTA upgrade and when she wasn't happy with the result tried to just restore to her old 4.1.2 backup. Needless to say she bricked her phone.
So, I can confirm that this method DOES work on a T999L. However, there are a couple of things to note (these should be no-brainers, but in the interest of saving questions from the newbies out there...) Of course like Tron said, I take no responsibility for damage to your device should you try this. I can only tell you that it worked fine for me. Here's the things to watch out for, listed by the steps in the OP:
4. Make certain that you use the correct PIT file for the T999L. The proper PIT file for the T999L is the one DocHoliday uploaded here http://forum.xda-developers.com/showthread.php?t=1848267&page=3. Do not use the regular T999 PIT file from @invisiblek's first post in that thread, which is what was linked to in the OP.
5. Make sure you use the correct firmware for the T999L, NOT the T999. If you're trying to recover from a brick then most likely you're going to want the Original UVAMB7 firmware (JB 4.1.2), since it seems most bricks lately are caused by trying to downgrade after flashing the 4.3 update. Of course if you want to you can also flash the UVUBMK4 (4.3) firmware and get the complete stock 4.3 system, including the bootloader, KNOX, etc.
However, if you're just recovering from a brick and want 4.3 I would recommend not just flashing the UVUBMK4 firmware directly. Rather, I would flash the older UVAMB7 firmware, and then once your phone is back up and running flash DocHoliday77's UVUBMK4 4.3 Rooted, deodexed_KnoxFREE ROM from http://forum.xda-developers.com/showthread.php?t=2370981&page=58. Once you've done that, just flash the updated modem from http://forum.xda-developers.com/showthread.php?t=1880987 as needed. This way you end up with the full rooted version of the 4.3 firmware but without the 4.3 bootloader which includes KNOX and causes so many problems with downgrading.
Of course that's just my two cents. I've been running my S3 with DocHoliday's stock UVUBMK4, KnoxFree, rooted ROM with the UVAMB7 bootloader and UVUBMK4 radio for over a month now and haven't had any problems. As always, your mileage may vary.

mrspock08 said:
Great guide, thanks a ton to @TronMinecraft for this writeup! I've been lucky and haven't bricked my S3 T999L (the T-Mobile LTE variant), but a relative wasn't so lucky. She took the OTA upgrade and when she wasn't happy with the result tried to just restore to her old 4.1.2 backup. Needless to say she bricked her phone.
So, I can confirm that this method DOES work on a T999L. However, there are a couple of things to note....
Click to expand...
Click to collapse
Thank you for confirming this worked for somebody else. I'm working on a slightly re-factored version of this based on input, and I'll be sure to note your findings about the T999L. Thanks!

SignalX said:
so what?
i want to update my phone to T999UVUEMJC 4.3 firmware
currently i'm on T999UVDMD5 4.1.2
is it safe to update using Odin?
sorry for noob question
Click to expand...
Click to collapse
This really isn't quite the right place for such a question. A search will yield you great results.
But yes, there's no reason you couldn't if you're sure you have the right firmware for your GS3 model. However if you simply want a stock update, I'd just use the OTA update function, or kies. Its a bit safer than manually messing with Odin, and won't void your warranty.

Very useful thread. Bricking is actually a lot easier than I thought.

hi does this guide help downgrade a 4.3 without loosing imei ? thank you
hope to receive a answer to this noob question
Sent from my SGH-T999 using XDA Premium 4 mobile app

FINNIX1996K said:
hi does this guide help downgrade a 4.3 without loosing imei ? thank you
hope to receive a answer to this noob question
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You CAN NOT DOWNGRADE 4.3.
This guide is to unbrick you and return you to 4.3 if you tried to downgrade (which won't work, ever).
Sent from my SGH-T999 using XDA Premium 4 mobile app

Actually, from my own experimentation you were right, you can in fact downgrade from 4.3. You just can't flash a rom that tries to change the bootloader. You cannot downgrade the 4.3 bootloader; but there isn't any reason why you can't run an earlier version of android.
I am currently running 4.2.2 rootbox AFTER having having done the official 4.3 update.
I did this with TWRP, and a rootbox flashable zip.

TronMinecraft said:
Actually, from my own experimentation you were right, you can in fact downgrade from 4.3. You just can't flash a rom that tries to change the bootloader. You cannot downgrade the 4.3 bootloader; but there isn't any reason why you can't run an earlier version of android.
I am currently running 4.2.2 rootbox AFTER having having done the official 4.3 update.
I did this with TWRP, and a rootbox flashable zip.
Click to expand...
Click to collapse
You did not downgrade. You flashed a custom ROM.
An example of downgrading would be a user on md5 flashing ljc with Odin. This puts bootloader, ROM, kernel, and baseband exactly as Samsung intended when LJC was released.
Sent from my Cleared Out T999L on CM11

Should be pinned. Very useful indeed

Adreaver said:
You did not downgrade. You flashed a custom ROM.
An example of downgrading would be a user on md5 flashing ljc with Odin. This puts bootloader, ROM, kernel, and baseband exactly as Samsung intended when LJC was released.
Sent from my Cleared Out T999L on CM11
Click to expand...
Click to collapse
Okay, thank you for the clarification. I was incorrectly applying the term downgrade.

[Q] Update to 4.3 from rooted 4.1.1

Could some one answer a few questions I have on how to go from rooted 4.1.1 to latest build. I have read and DL'd the zip from the "[LEAK] AT&T 4.3 UCUEMJ2 (Root & Knox versions)" thread and was wondering if the the rom can be loaded directly from CM recovery. Is the new bootloader required or optional?
Thanks
Zb
Model
SGH-I747
Android Version
4.1.1
Baseband
I747UCDLK3
Build
JR003L.I747UCDLK3
Recovery
CM 6

ZKornecki said:
Could some one answer a few questions I have on how to go from rooted 4.1.1 to latest build. I have read and DL'd the zip from the "[LEAK] AT&T 4.3 UCUEMJ2 (Root & Knox versions)" thread and was wondering if the the rom can be loaded directly from CM recovery. Is the new bootloader required or optional?
Thanks
Zb
Model
SGH-I747
Android Version
4.1.1
Baseband
I747UCDLK3
Build
JR003L.I747UCDLK3
Recovery
CM 6
Click to expand...
Click to collapse
Have you checked to see if you can get OTA update or update via the latest version of Kies? I was able to update from 4.1.1 to 4.3 with 2 different pre-rooted i747s - one officially via OTA and the other by flashing the same zips you refer to via cm recovery so maybe that answers your question. Before taking the one-way trip to 4.3, however, be sure you are done messing with your phone at the older firmware including unlocking, if required, as you may not be able to go back.

Larry2999 said:
Have you checked to see if you can get OTA update or update via the latest version of Kies? I was able to update from 4.1.1 to 4.3 with 2 different pre-rooted i747s - one officially via OTA and the other by flashing the same zips you refer to via cm recovery so maybe that answers your question. Before taking the one-way trip to 4.3, however, be sure you are done messing with your phone at the older firmware including unlocking, if required, as you may not be able to go back.
Click to expand...
Click to collapse
I wasn't able to update via Kies. If I use CM recovery is there a specific order I need to install with and can I install the new bootloader with CM Recovery or do I need to use odin?

ZKornecki said:
I wasn't able to update via Kies. If I use CM recovery is there a specific order I need to install with and can I install the new bootloader with CM Recovery or do I need to use odin?
Click to expand...
Click to collapse
I'm not aware there is any Odin flashable file for 4.3 yet. You may follow the steps in the link below for manual update via CM...
http://www.smartphonejam.com/2013/1...fficial-android43-i747ucuemjb-ota-update.html
You didn't say if you tried the OTA update? If you want to remain on stock, this is always the safest bet. If you are currently on official 4.1.1 you should be able to get this via WiFi with a valid AT&T sim card in your phone.

Me personally would avoid the official OTA update unless you're absolutely sure you want to keep it. Once you take the bootloader MJB you cannot flash any stock rom anymore unless you have an I747M then you can only flash the official 4.3.
I am on the MJ2 leak bootloader and have no issues, running S3Rx with the MJB modem phone runs great, if something happens I can simply flash anything I want to with Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Me personally would avoid the official OTA update unless you're absolutely sure you want to keep it. Once you take the bootloader MJB you cannot flash any stock rom anymore unless you have an I747M then you can only flash the official 4.3.
I am on the MJ2 leak bootloader and have no issues, running S3Rx with the MJB modem phone runs great, if something happens I can simply flash anything I want to with Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Exactly. I have also stayed away from the official 4.3. I have no idea why so many people around here just insist that their phone be on the latest update. Ok, the ones that had some major issues previously I could see, and yes you're going to have your exceptions whose phones will work just fine on 4.3. But all this 4.3 has done is create even more issues, with no flash-able firmware to go back to when something goes wrong. Some say there is no major reason not to update, but I say that there is no major reason to update, as most never give a reason to why they want to update. I just don't get it, other than these updates have become like new toys, just something new to play with.

shortydoggg said:
Exactly. I have also stayed away from the official 4.3. I have no idea why so many people around here just insist that their phone be on the latest update. Ok, the ones that had some major issues previously I could see, and yes you're going to have your exceptions whose phones will work just fine on 4.3. But all this 4.3 has done is create even more issues, with no flash-able firmware to go back to when something goes wrong. Some say there is no major reason not to update, but I say that there is no major reason to update, as most never give a reason to why they want to update. I just don't get it, other than these updates have become like new toys, just something new to play with.
Click to expand...
Click to collapse
shortydoggg thanks for your post and you actually hit the nail on the head. I can't think of reason I NEED to update, I just get bored and like to play. My warranty is up so voiding that isn't an issue and my 4.1.1 runs just fine, but by playing I learn so I like to play. 4.3 has a few nice features but if prevents the phone from being re-flashed then the risks most-likely aren't worth the benefits. I am just doing my due diligence, researching and asking questions. I really appreciate all the input and advice I get from forums such as this so I can make an intelligent decision.

ZKornecki said:
shortydoggg thanks for your post and you actually hit the nail on the head. I can't think of reason I NEED to update, I just get bored and like to play. My warranty is up so voiding that isn't an issue and my 4.1.1 runs just fine, but by playing I learn so I like to play. 4.3 has a few nice features but if prevents the phone from being re-flashed then the risks most-likely aren't worth the benefits. I am just doing my due diligence, researching and asking questions. I really appreciate all the input and advice I get from forums such as this so I can make an intelligent decision.
Click to expand...
Click to collapse
If you really want to try and want it to be reversible you can use the 4.3 leaked MJ2 bootloader if you decide you don't like the 4.3 stuff you can simply Odin back to stock. But if you use the MJB bootloader you cannot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Me personally would avoid the official OTA update unless you're absolutely sure you want to keep it. Once you take the bootloader MJB you cannot flash any stock rom anymore unless you have an I747M then you can only flash the official 4.3.
I am on the MJ2 leak bootloader and have no issues, running S3Rx with the MJB modem phone runs great, if something happens I can simply flash anything I want to with Odin.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I was running the same set up with MJ2 OS on MJB modem and the system was running fine until I recently flashed TWRP and SU to root and now the phone keeps booting to TWRP. I've run reset and reboot to system several times and even reflashed the system and modem files to attempt a reset but the same thing keeps happening - booting to TWRP. Will appreciate all steers on how I can rectify this.
Thanks

Larry2999 said:
I was running the same set up with MJ2 OS on MJB modem and the system was running fine until I recently flashed TWRP and SU to root and now the phone keeps booting to TWRP. I've run reset and reboot to system several times and even reflashed the system and modem files to attempt a reset but the same thing keeps happening - booting to TWRP. Will appreciate all steers on how I can rectify this.
Thanks
Click to expand...
Click to collapse
You're on the MJ2 leak bootloader you can use Odin to flash a stock image on the phone if you can get it into download/Odin mode.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
If it won't let you into download mode then format the internal SD card which should erase everything for the most part and flash everything fresh.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth

theramsey3 said:
You're on the MJ2 leak bootloader you can use Odin to flash a stock image on the phone if you can get it into download/Odin mode.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
If it won't let you into download mode then format the internal SD card which should erase everything for the most part and flash everything fresh.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
Click to expand...
Click to collapse
Thanks. It does get into download mode. Is there an Odin flashable file for the MJ2 and, if so, where can I find this? I'm wary about flashing an older ROM (e.g. 4.1.1) to avoid any further conflicts as I still have the official MJB modem or can this be done safely?
I've tried clearing the system and reflashing but it was the same result or perhaps I wasn't doing this the right way?

Larry2999 said:
Thanks. It does get into download mode. Is there an Odin flashable file for the MJ2 and, if so, where can I find this? I'm wary about flashing an older ROM (e.g. 4.1.1) to avoid any further conflicts as I still have the official MJB modem or can this be done safely?
I've tried clearing the system and reflashing but it was the same result or perhaps I wasn't doing this the right way?
Click to expand...
Click to collapse
I have been told by very reliable sources that you can Odin to an older version safely regardless of modem as long as the bootloader isn't MJB or MK5 so I am pretty confident it is safe. At this point there isn't too much to loose.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
---------- Post added at 11:47 PM ---------- Previous post was at 11:42 PM ----------
While you're there I would flash 4.1.1 and do the free unlock. If my laptop charger wasn't broken I would test it for you I would love to unlock my phone.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth

theramsey3 said:
I have been told by very reliable sources that you can Odin to an older version safely regardless of modem as long as the bootloader isn't MJB or MK5 so I am pretty confident it is safe. At this point there isn't too much to loose.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
---------- Post added at 11:47 PM ---------- Previous post was at 11:42 PM ----------
While you're there I would flash 4.1.1 and do the free unlock. If my laptop charger wasn't broken I would test it for you I would love to unlock my phone.
Sent from my SAMSUNG-SGH-I747 running S3Rx MJ2 bootloader MJB modem and it is smooth
Click to expand...
Click to collapse
Thanks. Just tried Odining to 4.1.1 but it failed, however. Would you recommend wiping the system in TWRP and booting to download to try again?

Larry2999 said:
Thanks. Just tried Odining to 4.1.1 but it failed, however. Would you recommend wiping the system in TWRP and booting to download to try again?
Click to expand...
Click to collapse
Odining to an older ROM is apparently not an option as this is isn't working. Thankfully, the phone is still booting into both download and recovery modes without difficulty so there is hope. I flashed CWM recovery via Odin thinking the problem may perhaps be with TWRP. However, the result was the same and the phone kept booting back into recovery mode rather than to the system. I also tried to see if was the bootloader so I flashed the MJB bootloader as well as reflashed the MJ2 system zip. The flashings were successful so, at least, it's unlikely to be a bootloader conflict but still the system will not boot.
Will greatly appreciate steers from the community on how to get the thing back working. n Thanks

Larry2999 said:
Odining to an older ROM is apparently not an option as this is isn't working. Thankfully, the phone is still booting into both download and recovery modes without difficulty so there is hope. I flashed CWM recovery via Odin thinking the problem may perhaps be with TWRP. However, the result was the same and the phone kept booting back into recovery mode rather than to the system. I also tried to see if was the bootloader so I flashed the MJB bootloader as well as reflashed the MJ2 system zip. The flashings were successful so, at least, it's unlikely to be a bootloader conflict but still the system will not boot.
Will greatly appreciate steers from the community on how to get the thing back working. n Thanks
Click to expand...
Click to collapse
Finally got it back up and running today. Cant be sure what really led to the soft brick but I simply wiped out everything in TWRP mode and then re-flashed the (MJ2) system, modem and kernel zips. This time it worked, I'd tried the same thing before but without the kernel. Now I'm back to the same configuration as before.

[Q] Need Absolutely Pure AT&T 4.4.2

I apologize in advance if this seems like a repeated question.
I have a carrier-locked Galaxy S3 from AT&T. I have a modified 4.4.2 image running. As a result it appears the network unlock code does not work. I've tried a couple of alternatives ways to unlock but none have worked. I'm on my fifth attempt... and if this doesn't work the device will be permanently locked to AT&T's network.
I'd like to flash with ODIN a completely stock 4.4.2 image. No root, no busybox, no additions, no subtractions, no changes whatsoever.
I cannot seem to find a link which has an absolutely pure AT&T image. If someone would post a link to a pristine 4.4.2 image I'd appreciate it. Thank you in advance
I'm running 4,4,2 baseband NE4, The "about" shows "Device status Custom".

From everything I have seen and read, there is no such thing as a pure stock ATT 4.3 or 4.4.2 ROM. ATT never released a full 4.3 or 4.4.2 Odin flashable ROM for the i747. 4.3 and 4.4.2 were only available as OTA updates.
Now that you are on 4.4.2 bootloader and modem, don't flash anything that attempts to downgrade the bootloader.
When you say "modified image", do you mean a custom ROM?

The closest I have seen is the stock rom posted by enewman17. However, it does still have busybox and root. He does give a download of the stock recovery. Maybe it would be possible to install, remove root and busybox, then go back to stock recovery. Keep in mind that you only have one attempt remaining and I have not tried this.
http://forum.xda-developers.com/showthread.php?t=2789917
http://forum.xda-developers.com/showthread.php?t=2788357

Audit13, I say modified because, as best I can remember, I used this process: http://forum.xda-developers.com/showthread.php?t=2789917
I typically keep records of what I do to my phones but I figured that 4.4.2 would be the last upgrade from AT&T. I never expected network unlocking to be such an ordeal.

Dawgdoc, I think I will try to reflash the OTA. I think I saw a post suggesting it can't be done twice. I'll do a little research and report what I find.
I suspect this phone will end up a gift to one of my niecies or nephews. Thanks for your advice.

You can't reflash the ota. You MUST be running stock MJB for it to work because all it does is patch the files on your device.
It'll be late before I can try, but I'll try to put up a purely stock NE4 rom. I've seen several people needing one, and am sure it will be needed again down the road...
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[Q] sgh-i747 original updates

Hi all, I have an SGH-i747 with ver 4.0.4 which has been rooted. I will like to update my version systematically with the original updates i believe there where from 4.0.4 to 4.1.1 then 4.1.2. then 4.3, 4.4.2 etcc.. its there a place where i can find the original ups, my phone will not take the original firmware updates on its own. Reason is once i try to flash any ROM pass 4.1.1 i loose the Mobile Data getting the no sim inserted msg and no signal, forcing me to go back the original state in order to work. seems there is a problem with the modem once i go pass 4.1.1. .. thank you.

What bootloader version is on the phone? Where did you get the firmware to flash? You're using desktop Odin to flash?

Are ota updates an option for you? If they are you can unroot and flash the stock recovery; it might be easiest just to Odin back to stock.
Otherwise enewman has posted firmware updates to xda. They are bootloader + modem zips you can flash in custom recovery. You have to flash them incrementally, mjb then ne4 then nj1. Search the forum here and you'll find them. Just be careful and read read read those threads. Messing with bootloaders is the best way to hard brick this phone.

I'm in a similar situation - I've been on a custom version of the Stock ROM for 4.1.2 - never bothered to update the bootloader because I had the soft unlock done, didn't want to lose it. Now I'm bored with it. I'd love to get up to 4.4, or even a 5.0 ROM... but not sure the steps needed to do so. I'm vaguely aware that I have to update the bootloader/kernel, etc... but it seems like I'm 4 years behind the curve with all the ROMs and threads about bootloaders, and I've lost my touch.
That thread with the list of bootloaders sounds good though, I'll go looking for it to start I guess.

gfinockio said:
I'm in a similar situation - I've been on a custom version of the Stock ROM for 4.1.2 - never bothered to update the bootloader because I had the soft unlock done, didn't want to lose it. Now I'm bored with it. I'd love to get up to 4.4, or even a 5.0 ROM... but not sure the steps needed to do so. I'm vaguely aware that I have to update the bootloader/kernel, etc... but it seems like I'm 4 years behind the curve with all the ROMs and threads about bootloaders, and I've lost my touch.
That thread with the list of bootloaders sounds good though, I'll go looking for it to start I guess.
Click to expand...
Click to collapse
Here you go. This TLDR post has all enewman's firmware update threads linked to it.

jason2678 said:
Here you go. This TLDR post has all enewman's firmware update threads linked to it.
Click to expand...
Click to collapse
Thanks! I'll give it a look, down a couple of shots of liquid courage, and give it a go this weekend.
EDIT: Yikes, didn't take long for that to fizzle out. I'm using a i747M. Noticed that my current baseband version isn't listed anywhere on that thread. Hmmm. Oh well, guess I'll do some more digging later...

With an i747m, you can flash the latest 4.4.2 using firmware from sammobile.com and desktop Odin.

Do I need to do them in sequence, or can I jump to the latest? I'm assuming once I've flashed the stock firmware, I can load any current custom ROM?

@gfinockio, is your phone sim unlocked? If not and you don't see any mention of the warranty bit in download mode, you could flash back to stock 4.1.1, use the free method to sim unlock, and then run OTA updates until you are running the latest ROM. OTA updates are the safest route to upgrade the phone.
If you phone is sim unlocked already, you could flash directly to the latest ROM; however, you will not be able to downgrade the bootloader as any attempts to downgrade the bootloader could hard brick you phone.

audit13 said:
@gfinockio, is your phone sim unlocked? If not and you don't see any mention of the warranty bit in download mode, you could flash back to stock 4.1.1, use the free method to sim unlock, and then run OTA updates until you are running the latest ROM. OTA updates are the safest route to upgrade the phone.
If you phone is sim unlocked already, you could flash directly to the latest ROM; however, you will not be able to downgrade the bootloader as any attempts to downgrade the bootloader could hard brick you phone.
Click to expand...
Click to collapse
I used the "free unlock" in 4.1.2 (so it's unlocked) but I thought when you upgraded the bootloader you lost that lock. Now that I believe that isn't the case (and I've used a different tool to unlock as well), I may just try the OTA updates. I was with MTS (Manitoba), but now I'm with Rogers, so I guess I would just use the Rogers OTA images to upgrade from 4.1.2 to 4.4? Do I use Odin or whatever to do that? Once I upgrade to a "stock" image, won't the updater just prompt me to upgrade again and again until I'm "up to date"?

Unlocking the phone via code or the free method is permanent even after upgrading the ROM, bootloader, and modem.
The carrier ROMs for the i747m are pretty much identical but I always recommend sticking with the original carrier's ROM. If you download the stock image from sammobile.com, use Odin to flash the ROM.
OTA updates will not work with a rooted stock ROM too.

When i search for the stock firmware on sammobile for the i747m, it doesn't have any listings. Are you able to find it on there? I don't see it.

Search for the sgh-i747m.

komali2 said:
When i search for the stock firmware on sammobile for the i747m, it doesn't have any listings. Are you able to find it on there? I don't see it.
Click to expand...
Click to collapse
Check here: http://www.sammobile.com/firmwares/database/SGH-I747M/
you can sort by carrier or country.

delete

[Q] Help with going back to stock (from CM11)

Hey, sup?
I need your help, I'm trying to go back to stock firmware on my i747, currently I'm running CM11 latest snapshot.
Background: Some time ago, I accidently erased my imei. Took the phone to a guy who restored it but the phone doesn't work with 3G now, only 2G. So I wanted to try going back to stock firmware to see if that fixes the issue.
I tried downloading the CUEMJB file from here, but it doesn't work (keeps looping the same page) http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Can you help me? Also, it is safe what I'm trying to do?
Thank you!

Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes the IMEI matches.
I was able to download the file.
Unfortunately, the thing didn't went ok. After flashing my phone is unresponsive, black screen, no more boot
If I connect it to the computer at this point, it tries to search for a QHSUSB_DLOAD driver. Not sure what is that, I think I bricked my phone.
I've seen some guides for unbricking by placing a sd card in the phone at boot but so far it haven't worked

Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.

dawgdoc said:
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
Click to expand...
Click to collapse
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back

Alright! I just tried the SD card method w/ one of the files in the threads linked. Phone boots!
So it seems my bootloader is bad right?

japi2000 said:
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Click to expand...
Click to collapse
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.

dawgdoc said:
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
Click to expand...
Click to collapse
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?

japi2000 said:
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
Click to expand...
Click to collapse
That is the stock recovery. If you were successfully running one of the latest CM11 snapshots, you were probably on one of the three 4.4.2 bootloaders ( and modems ), they are NE4, NJ1, and NJ2. This would explain why the MJB (4.3) image you downloaded and flashed would soft brick your phone. It looks like that flash may be responsible for you being back on stock recovery, at best guess. Before anything else, do a factory reset from the stock recovery. This is frequently necessary to boot when going from a CM/AOSP LP rom back to stock.
Since you can get to download mode, I think the best bet would be to install a custom recovery. TWRP for the i747 is here, the top image is flashable with Odin while in download mode. Remember not to reboot from Odin. Instead remove the cable, pull the battery, then boot straight to recovery. Once you have TWRP loaded, boot into recovery and use the terminal emulator in it to determine bootloader and modem with these commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Once you know the version of bootloader and modem you had been on, reflash that version from TWRP you will probably need the file on an external sdcard to do so. After this you can flash your rom of choice from TWRP, stock or otherwise. Since you were having imei issues go with one of enewman's stock roms, as @DocHoliday77 suggested. He can then help you with the imei issues if still necessary. Any other ideas Doc?

Ok, so
Bootloader = I747UCUEMJB
I don't get anything when running getprop | grep version.baseband in the recovery.
This is what I've done so far.
Booted w/ the sdcard trick (bootloader in the sdcard).
Installed twrp
Installed the following files:
AT&T_I747UCUEMJB.zip
d2att_I747UCUEMJB_bootloader.zip
d2att_I747UCUEMJB_modem.zip
d2att_Kernel_Stock_init.d_4_3_MJB_v1.0.zip
That brought the phone to life again (w/ stock 4.3). Then I flashed CM12 from the recovery. All went ok.
Problem is, I still don't have 3G connectivity, only edge.
What would you recommend try next?
Thank you

Alright, I was able to upgrade to UCUFNJ1 for both the bootloader and baseband. Still no 3G. Ideas?

Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright thank you

Alright, I'm happy to say that with the help of our fellow DocHoliday77 I was able to solve the issue !
Thanks everyone!

Glad you have it working.
Way to go Doc.

Damn japi2000. You did that quick good job.

Thank you!
I can't believe I went from a almost dead phone to a fully working one in only a few days, even with the 3G/4G working again !
This forum and people are amazing! Thank you!