So my wife's S3 is SGH-i747M from Telus in Canada. Updated OTA to 4.3 (its unrooted) but turns out she doesn't like it at all and its buggy. I have read through several threads and am unsure how to go about downgrading safely.
I get that the MK5 modem in 4.3 updates EFS to v2, so I downloaded a .zip of MK5 modem to install after downgrading.
I downloaded MF1 firmware from sammobile with the intention of flashing in Odin.
My questions are:
Should I flash MF1 in Odin then flash a custom recovery, then flash back the MK5 modem? Or custom recovery first while on 4.3?
Also the MF1 4.1.2 firmware is 700+meg, I take it these are full firmwares, and I also read stuff about them including everything such as bootloader etc. If this has old bootloader and 4.3 had updated the bootloader would I be risking a brick?
Sorry if this has been explained elsewhere, seen alotta conflicting info and not sure what best way to proceed is. Thx alot!
I've heard it's impossible to downgrade. ...it's probably possible for those know-How but not to my knowledge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
skurys said:
...Updated OTA to 4.3 (its unrooted) but turns out she doesn't like it at all and its buggy. I have read through several threads and am unsure how to go about downgrading safely...
Should I flash [sammobile] MF1 in Odin then flash a custom recovery, then flash back the MK5 modem? Or custom recovery first while on 4.3?!
Click to expand...
Click to collapse
see below
skurys said:
...Also the MF1 4.1.2 firmware is 700+meg, I take it these are full firmwares, and I also read stuff about them including everything such as bootloader etc. If this has old bootloader and 4.3 had updated the bootloader would I be risking a brick?
Click to expand...
Click to collapse
definitely!
danchoi704 said:
I've heard it's impossible to downgrade.!
Click to expand...
Click to collapse
definitely!
danchoi704 said:
...it's probably possible for those know-How but not to my knowledge.
Click to expand...
Click to collapse
In OP "Updated OTA" scenario, definitely not possible. Brick City
re: similar question
I am in a similar situation; a friend of mine has a i747M SGS3 from Telus and is having issues with performance and crashes since updating to official 4.3, and wants me to help him deal with it.
I want to be unambiguously sure of this before I take any actions: if we attempt to DOWNGRADE to 4.1.2, will we brick the phone?
If so, do we have other options? For example, can an official 4.3 i747M be safely sidegraded to a stable Cyanogenmod 4.3 equivalent, or to the Cyanogenmod 4.4.2 equivalent?
pc103 said:
see below
definitely!
definitely!
In OP "Updated OTA" scenario, definitely not possible. Brick City
Click to expand...
Click to collapse
Your core question is popular these days. I will say this once for all:
OTA 4.3 (with bootloader)
Downgrade=Brick
It's possible the buggy etc complaints can be remedied by (backup, wipe & reflash via Sammobile, Keis or Odin.
The sideflashing issues are best taken to the appropriate forum thread for your custom rom.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Once on 4.3 you CANNOT go back
Sent from my SGH-I747M using Tapatalk
jimchee said:
Once on 4.3 you CANNOT go back
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
These are the statements that cause all the confusion.
Once on the new bootloader (MJB) included with the 4.3 ota you can't downgrade the BOOTLOADER, you can only reflash the same or newer. You can still install any custom ROM that has added the bootloader to the assert but does not contain a bootloader itself, or simply remove the assert lines from the updater script and the bootloader (if the ROM contains one) yourself. You could also look around to see if anyone has taken the time to gut the older firmwares to remove the bootloader which would make it possible to install those as well. So to review, any ROM that doesn't attempt to install a bootloader and either a) passes the assert check for MJB or b) has the assert removed from the updater script will work just fine. Anything that attempts to change the bootloader OR doesn't have MJB in the assert code will fail....or worse. If you don't know what an update script or the bootloader assert check is then you shouldn't mess with them, just look for something that says it will work specifically with the MJB bootloader.
this is certainly true enough but looking through the att development thread it is mostly impossible to tell what you can flash on what, I have an I747M from telcel and so far I have not found one rom that I can flash successfully to my device no matter what I have tried, but that is neither here nor there, so I stand corrected sorry I tried to help.
Sent from my SGH-I747M using Tapatalk
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
Oh and the original post says his wife's phone is unrooted so I stand by my original post
Sent from my SGH-I747M using Tapatalk
i went from "MJB" bootloader to "MJ2" bootloader, thought they were the same but apparently not and now i am bricked. is there any fix for this or did i just make myself a fancy looking paperweight???
by bricked do you mean no response whatsoever or can you get to download mode
Sent from my SGH-I747M using Tapatalk
jimchee said:
by bricked do you mean no response whatsoever or can you get to download mode
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
no response what so ever!!!!
Have you removed the battery? try holding volume down, home, and power while inserting the battery, if you get nothing you will probably need a jag to fix
Sent from my SGH-I747M using Tapatalk
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
jtag
Sent from my SGH-I747M using Tapatalk
I have downgraded from 4.3 to 4.1.1 on my SGH-1747 (AT&T) but using only the firmware and not the bootloaders I've gone so many times back to stock. I just stay away from flashing b ootloaders cause I'd hate a brick
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
A little confused
I will start by saying that I do know that trying to go backwards from the UCDMJB bootloader WILL BRICK the phone. Been there and done that. Not fun. However the directions in this thread do work to get you unbricked - http://forum.xda-developers.com/showthread.php?t=2549068 You are just stuck at using the UCDMJB bootloader which hasn't been a problem with any of the 4.3 and 4.4 ROMS I have been playing with on this phone.
Now about my confusion. From what I am reading in various threads, it looks like you can go from say the UCDLK3 or UCDMG2 bootloader to the UCDMJ2 bootloader and still be able to ODIN back to stock without bricking your phone. Is this correct? I have one phone that is currently on the UCDMG2 bootloader. As mentioned above, my other phone is on the UCDMJB bootloader. Is it possible to move forward from the UCDMJB bootloader without bricking the phone?
So in other words -
UCDLK3 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDMG2 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDLK3 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMG2 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMJB -> UCDMJ2 - Will BRICK phone ????
Thanks in advance for any responses.
poppo101 said:
I will start by saying that I do know that trying to go backwards from the UCDMJB bootloader WILL BRICK the phone. Been there and done that. Not fun. However the directions in this thread do work to get you unbricked - http://forum.xda-developers.com/showthread.php?t=2549068 You are just stuck at using the UCDMJB bootloader which hasn't been a problem with any of the 4.3 and 4.4 ROMS I have been playing with on this phone.
Now about my confusion. From what I am reading in various threads, it looks like you can go from say the UCDLK3 or UCDMG2 bootloader to the UCDMJ2 bootloader and still be able to ODIN back to stock without bricking your phone. Is this correct? I have one phone that is currently on the UCDMG2 bootloader. As mentioned above, my other phone is on the UCDMJB bootloader. Is it possible to move forward from the UCDMJB bootloader without bricking the phone?
So in other words -
UCDLK3 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDMG2 -> UCDMJB - NO DOWNGRADING TO OLDER BOOTLOADER WITHOUT BRICKING PHONE
UCDLK3 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMG2 -> UCDMJ2 - Can downgrade to older bootloader without bricking phone?
UCDMJB -> UCDMJ2 - Will BRICK phone ????
Thanks in advance for any responses.
Click to expand...
Click to collapse
To clarify your list there....
UCMJB - you are stuck here, the only way you can go is sideways (reflashing MJB) or up (doubt it will happen on this device). This is as far as bootloader goes anyways, this has no affect on recoveries, kernels, or ROMs*
UCDMJ2 - downgradeable like any other previous bootloader
The reason for this is MJ2 was from a leaked version of the 4.3 update that for whatever reason failed testing and was rebuilt. In this state the Qfuse that dissallows downgrading had not been implemented.
* There is a check built into most (probably all) custom, and every offical rom that checks the current bootloader against a list of acceptable bootloaders. If your device is loaded with one of these in the list, installation continues. If it is not, it fails the check and flashing is halted. Fundamentaly MJB is pretty much identical to several of the previous bootloaders with the exception of the new 'security' features, so in theory any current custom ROM CAN work if it doesn't pass the check by manually editing the updater-script in the rom.
[SOLVED] A little confused
dntesinfrno said:
To clarify your list there....
UCMJB - you are stuck here, the only way you can go is sideways (reflashing MJB) or up (doubt it will happen on this device). This is as far as bootloader goes anyways, this has no affect on recoveries, kernels, or ROMs*
UCDMJ2 - downgradeable like any other previous bootloader
The reason for this is MJ2 was from a leaked version of the 4.3 update that for whatever reason failed testing and was rebuilt. In this state the Qfuse that dissallows downgrading had not been implemented.
* There is a check built into most (probably all) custom, and every offical rom that checks the current bootloader against a list of acceptable bootloaders. If your device is loaded with one of these in the list, installation continues. If it is not, it fails the check and flashing is halted. Fundamentaly MJB is pretty much identical to several of the previous bootloaders with the exception of the new 'security' features, so in theory any current custom ROM CAN work if it doesn't pass the check by manually editing the updater-script in the rom.
Click to expand...
Click to collapse
So flashing MJ2 is not upgrading the MJB bootloader but actually a downgrade and will brick the phone that is on MJB if I flash MJ2. Correct? And the phone that is on MG2 will not brick if I flash MJ2 and will be able to be reverted back to stock via ODIN.
Thanks for the clarification. I knew MJ2 was from a leaked version of 4.3 but wasn't sure how it played into the scheme of things. So far I have had no issues flashing any of the 4.4 ROMS on the MJB bootloader.
Thanks button clicked.
dntesinfrno said:
...So to review, any ROM that doesn't attempt to install a bootloader and either a) passes the assert check for MJB or b) has the assert removed from the updater script will work just fine...
Click to expand...
Click to collapse
After further reading, apparently in mobile odin you can flash stock 4.1.2 and it will ignore the bootloader. Don't know if such a method would still require passing an assert check or if it bypasses this requirement. Haven't found enough success stories confirming yet to risk an angry wife if things go south
skurys said:
After further reading, apparently in mobile odin you can flash stock 4.1.2 and it will ignore the bootloader. Don't know if such a method would still require passing an assert check or if it bypasses this requirement. Haven't found enough success stories confirming yet to risk an angry wife if things go south
Click to expand...
Click to collapse
I've heard the same thing but have never used mobile odin to flash anything so i can't say for sure about the assert. I can say it wont hurt to try. Best case it bypasses the check, doesn't mess with the bootloader and flashes the remainder of the stock image. Worst case it does check the assert script and it fails before it ever writes anything.
Related
Okay, well I'm really starting to dislike this crap.
I replaced the board in my girlfriend s3, and it had 4.3 OTA on it -.-.
Now to my understanding, the OTA update comes with knox in the bootloader.This keeps anyone from flashing custom roms/recoveries.
I've followed all the guides and such. I dont care about 4.3. I just want knox completely removed, and revert it back to 4.1.2. I know that there is bootloaders floating around out there, that should overwrite the knox bootloader, and then flash a stock 4.1.2 rom. Now in theory that should work, but my googling skills have gone down the drain. I can't find any bootloader files, There has to be a way around this, its been over a month now. I honestly don't ever want to upgrade to 4.3. I'm happy with jellybean. It's stable, and smooth.
Just want to pick all your guys' brains xD.
Johnnysauur said:
Okay, well I'm really starting to dislike this crap.
I replaced the board in my girlfriend s3, and it had 4.3 OTA on it -.-.
Now to my understanding, the OTA update comes with knox in the bootloader.This keeps anyone from flashing custom roms/recoveries.
I've followed all the guides and such. I dont care about 4.3. I just want knox completely removed, and revert it back to 4.1.2. I know that there is bootloaders floating around out there, that should overwrite the knox bootloader, and then flash a stock 4.1.2 rom. Now in theory that should work, but my googling skills have gone down the drain. I can't find any bootloader files, There has to be a way around this, its been over a month now. I honestly don't ever want to upgrade to 4.3. I'm happy with jellybean. It's stable, and smooth.
Just want to pick all your guys' brains xD.
Click to expand...
Click to collapse
You should read THIS. It explains everything. You can't overwrite KNOX or downgrade boot loader or you will brick, but you can still root and have custom recovery, then flash a ROM of your choice. Downgrading includes flashing TAR files in ODIN and downgrading mk3 to md4 or lower via zip files.
sent from my GS3
Is there anything different you need to do for custom recovery on 4.3
Sent from my SPH-L710 using xda app-developers app
Johnnysauur said:
Is there anything different you need to do for custom recovery on 4.3
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I believe anything after md4 won't mount storage. Check THIS thread. I flashed the TWRP Tar in ODIN on a Boost GS3 that wouldn't mount storage.
sent from my GS3
joeyhdownsouth said:
You should read THIS. It explains everything. You can't overwrite KNOX or downgrade boot loader or you will brick, but you can still root and have custom recovery, then flash a ROM of your choice. Downgrading includes flashing TAR files in ODIN and downgrading mk3 to md4 or lower via zip files.
sent from my GS3
Click to expand...
Click to collapse
I thought you couldn't root if 4.3 was applied with ota
Sent from my SPH-L710 using xda app-developers app
Johnnysauur said:
Okay, well I'm really starting to dislike this crap.
I replaced the board in my girlfriend s3, and it had 4.3 OTA on it -.-.
Now to my understanding, the OTA update comes with knox in the bootloader.This keeps anyone from flashing custom roms/recoveries.
I've followed all the guides and such. I dont care about 4.3. I just want knox completely removed, and revert it back to 4.1.2. I know that there is bootloaders floating around out there, that should overwrite the knox bootloader, and then flash a stock 4.1.2 rom. Now in theory that should work, but my googling skills have gone down the drain. I can't find any bootloader files, There has to be a way around this, its been over a month now. I honestly don't ever want to upgrade to 4.3. I'm happy with jellybean. It's stable, and smooth.
Just want to pick all your guys' brains xD.
Click to expand...
Click to collapse
At this time, the only way to get Knox out of the bootloader is to write over it with an unknoxed bootloader that's signed by Samsung, and passes the version check by the current bootloader.
Knoxed bootloaders will reject previous bootloader versions, even if those are properly signed.
However, loading a current version bootloader (properly signed) without knox to replace the knoxed one should then allow you to revert back to a previous version.
The only way this wouldn't work is if the knoxed bootloader killed a q-fuse somewhere, but no one has found proof to this.
andyistic said:
At this time, the only way to get Knox out of the bootloader is to write over it with an unknoxed bootloader that's signed by Samsung, and passes the version check by the current bootloader.
Knoxed bootloaders will reject previous bootloader versions, even if those are properly signed.
However, loading a current version bootloader (properly signed) without knox to replace the knoxed one should then allow you to revert back to a previous version.
The only way this wouldn't work is if the knoxed bootloader killed a q-fuse somewhere, but no one has found proof to this.
Click to expand...
Click to collapse
Correction: nobody has positively verified the existence of an eFuse, to my knowledge, just yet. But there is a substantial amount of evidence to suggest its existence. If you try to revert from KNOX to a previous bootloader version, it has a pretty consistent knack for hard-bricking the devices so they won't even power to the download or recovery consoles. From what I've read, people have had similar experiences when attempting to run older versions of TriangleAway to zero out their flash counts. Additionally, every attempt that has been made to revert the KNOX Warranty Void flag that I've read about has resulted in a hard-brick as well.
It's also important to note: At this time, when people say they've removed KNOX what they're really talking about are the apps that came in the 4.3 update. Removing these does not have any impact on the bootloader's status. There is currently no way to remove the KNOX bootloader without irrevocably crippling your device.
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.
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.
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
Hi all.
Two weeks ago I got this device (sgh i747) was rooted and was stock 4.1.1. I installed cwm and made A backup of stock room. And flash AOKP custom kitkat rom. Now I want to downgrade back to stock. or if I cannot downgrade please suggest me a stable lollypop rom.
Things I have!
1:- rooted cwm installed (sgh i747)
Backup of stock rom 4.1.1
Please help .
Thanks
mango man said:
Hi all.
Two weeks ago I got this device (sgh i747) was rooted and was stock 4.1.1. I installed cwm and made A backup of stock room. And flash AOKP custom kitkat rom. Now I want to downgrade back to stock. or if I cannot downgrade please suggest me a stable lollypop rom.
Things I have!
1:- rooted cwm installed (sgh i747)
Backup of stock rom 4.1.1
Please help .
Thanks
Click to expand...
Click to collapse
If you are still on the original bootloader and modem you should be able to revert to stock 4.1.1 by simply restoring the backup from your recovery. Before you attempt to do so verify that you are indeed on the 4.1.1 bootloader. This can be done with the Phone Info *Samsung* app by VndNguyen (?sp) from the playstore or by a couple of terminal emulator commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
If you do not already have terminal emulator installed, it may have come with the ROM, you can get it from the Playstore. It may also be a part of CWM recovery, it is part of TWRP I know for sure.
If it turns out you are on a newer bootloader and modem then go with a stock ROM that matches the bootloader and modem on the phone. To run a lollypop rom you will need to be on at least the NE4 bootloader and modem.
Thanks for a very helpful reply. I m going to follow your instructions. Will soon replay. Thanks again.
dawgdoc said:
If you are still on the original bootloader and modem you should be able to revert to stock 4.1.1 by simply restoring the backup from your recovery. Before you attempt to do so verify that you are indeed on the 4.1.1 bootloader. This can be done with the Phone Info *Samsung* app by VndNguyen (?sp) from the playstore or by a couple of terminal emulator commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
If you do not already have terminal emulator installed, it may have come with the ROM, you can get it from the Playstore. It may also be a part of CWM recovery, it is part of TWRP I know for sure.
If it turns out you are on a newer bootloader and modem then go with a stock ROM that matches the bootloader and modem on the phone. To run a lollypop rom you will need to be on at least the NE4 bootloader and modem.
Click to expand...
Click to collapse
Okay got Samsung phone info app.
Boot loader version -------I747UCDLK3
Baseband version -----I747UCDLK3
And please explain LATEST NE4 BOOT LOADER.
Thanks
You are currently running the LK3 bootloader and modem. If I am not mistaken that's a pretty old one (original?). You will have to update to NE4 or newer firmware before you can flash any of the newer roms. They will not boot in the older ones.
Your firmware is actually the only one available for download so I recommend flashing it via Odin and factory resetting. Then update using the Software Update option in Settings > About Device.
You can download your LK3 firmware here: http://www.sammobile.com/firmwares/database/SGH-I747/
You may have to run Software update several times to fully update.
That is probably the safest and easiest course you can take.
After that, flash the latest custom recovery of your choice, then flash the rom you want.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
BTW, after flashing the LK3 firmware, you might want to consider using the free Sim unlock method. (Should be pretty easy to find).
Once you update past 4.3 you can no longer use it. It will allow the device to be used on other carriers networks, which can be beneficial if you ever want to sell it or switch carriers.
Sent from my SGH-T999 using Tapatalk
What DocHoliday77 suggests is probably the safest method to get what you want. After each update the system will force you to wait 24 hours before you can make the next update. That would be three days to get to NE4, the first 4.4.2 release by AT&T, which you need to run lollipop ROMs. If you want to update to the current release (NJ2) that would be two additional days.
You can shortcut the required waiting period by manually advancing the system date after each update.
In addition to not allowing you to use the free unlock, once you take the 4.3 bootloader it prevents you from downgrading bootloaders. Newer bootloaders do the same, downgrading will be a thing of the past. (I never took the official 4.3 bootloader until the stagefright scare came along and I went from my older custom ROM to a new release.)
dawgdoc said:
What DocHoliday77 suggests is probably the safest method to get what you want. After each update the system will force you to wait 24 hours before you can make the next update. That would be three days to get to NE4, the first 4.4.2 release by AT&T, which you need to run lollipop ROMs. If you want to update to the current release (NJ2) that would be two additional days.
You can shortcut the required waiting period by manually advancing the system date after each update.
In addition to not allowing you to use the free unlock, once you take the 4.3 bootloader it prevents you from downgrading bootloaders. Newer bootloaders do the same, downgrading will be a thing of the past. (I never took the official 4.3 bootloader until the stagefright scare came along and I went from my older custom ROM to a new release.)
Click to expand...
Click to collapse
1:- Okay I fully understood what I have to do to flash lolly pop . But confused a little bit . If I have original boodloader than it should be easier to restore my stock 4.1.1 . Backup (still not clear) .
2:- I am out of USA. The device in unlocked. I am using ZONG sim on it. So the question is can I still update the device via OTA.
Thanks
mango man said:
1:- Okay I fully understood what I have to do to flash lolly pop . But confused a little bit . If I have original boodloader than it should be easier to restore my stock 4.1.1 . Backup (still not clear) .
2:- I am out of USA. The device in unlocked. I am using ZONG sim on it. So the question is can I still update the device via OTA.
Thanks
Click to expand...
Click to collapse
When you say original bootloader I don't know which you have. My i747 came with 4.1.1 but before I could get it out of the clerk's hands they had taken the OTA to change it from DLK3/4.1.1 bootloader and stock rom to MG2/4.1.2 bootloader and stock rom. Even more confusing I have read reviews that state the SGS3 was originally released with android 4.0.4.
If your original bootloader was older than 4.3 (MJB) AND you have never upgraded to MJB or newer, then you can safely return to stock 4.1.1.
To get OTAs you need to be on the stock ROM, at least you do in the USA. I don't know if that holds true elsewhere.
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
dawgdoc said:
When you say original bootloader I don't know which you have. My i747 came with 4.1.1 but before I could get it out of the clerk's hands they had taken the OTA to change it from DLK3/4.1.1 bootloader and stock rom to MG2/4.1.2 bootloader and stock rom. Even more confusing I have read reviews that state the SGS3 was originally released with android 4.0.4.
If your original bootloader was older than 4.3 (MJB) AND you have never upgraded to MJB or newer, then you can safely return to stock 4.1.1.
To get OTAs you need to be on the stock ROM, at least you do in the USA. I don't know if that holds true elsewhere.
Click to expand...
Click to collapse
DocHoliday77 said:
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks men for quick response.
now I m fully confused. Don't know what to do. because I don't want to stuck on this battery enemy rom. (Aokp kitkat. Custom rom )
I am not clear about boootader version (PHONE INFO SAMSUNG APP SAYS ITS i747ucdlk3 ) but I know when got this thing. It was android 4.1.1 . Which I have back a backup. As per I am out of att network and I can't get OTA,s so I don't need to revert to 4.1.1 backup. I think I have to find out 4.3. For my device. So kindly please inform me if some one knows about . Iwill be very thankful to u people.
Again thanks
DocHoliday77 said:
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got this while searching online. Please tell me if it is helpful for.me.
http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup! I think it is. Will try . Thanks
mango man said:
Yup! I think it is. Will try . Thanks
Click to expand...
Click to collapse
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
DocHoliday77 said:
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
mango man said:
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
Click to expand...
Click to collapse
To be able to run a lollipop rom you will need to update bootloader and modem. Update them together, this is important once you reach the 4.4.2 level of bootloader and modem that you will need to run lollipop roms. Once you reach 4.4.2 you will brick your phone if the bootloader and modem versions are not the same.
Before starting to flash any of the files you need to get you up and running on lollipop, I strongly suggest you download all you need from start to finish. Store the files you will need in the upgrade process either on an external sdcard or on the root of your internal sdcard. I haven't used CWM Recovery on my SGS3 since shortly after rooting it, I have been using TWRP since then, and I don't recall all of the capabilities of CWM recovery. If the CWM version you have will not let you flash from an external sdcard you will need to store the files you will use on the root of the internal card to be able to flash them. It will be easier to do this before you start, unless you are comfortable with pushing files from a computer using adb.
BEFORE DOING ANYTHING I AM SUGGESTING read enough that you thoroughly understand what I am saying. After reading, ask questions for clarification. Be sure you have no doubts.
Decide if you intend to install a rom along with the bootloader and modem at each upgrade; or if you are going to install updating only bootloader and modem until you get them to them point that you can run a lollipop ROM. Since you said you can not do OTA updates, either way will work. Whichever you decide, you can not skip directly to the bootloader and modem you need for lollipop.
If you are installing bootloader and modems without the rom:
From the stock 4.1.1 rom and bootloader you can go straight to 4.3 bootloader and modem, skipping the 4.1.2 (MG2) version. I have personally done this with no ill consequences. After 4.3, install the first bootloader and modem version for 4.4.2, that is NE4. Lollipop will run with the NE4 bootloader. As DocHoliday stated, you can go on the the current bootloader and modem. After NE4 is NJ1. After NJ1 you come to the current bootloader and modem, which is NJ2
If you plan to install the full ROM at each step.
The page you linked to should work if all of the downloads are available. Go from 4.1.1 to 4.3 to 4.4.2 (NE4). If you want the newer versions (NJ1 or NJ2) do them in sequence, do not skip any that are mentioned. Read the instructions on your linked page carefully. If you want NJ1 and then NJ2 they can be found in threads by enewman17, as can NE4 and maybe 4.3. I didn't provide the links so that you will hopefully read the pages carefully after searching and before downloading. Be sure you understand what you are downloading to flash and how it should be used.
dawgdoc said:
To be able to run a lollipop rom you will need to update bootloader and modem. Update them together, this is important once you reach the 4.4.2 level of bootloader and modem that you will need to run lollipop roms. Once you reach 4.4.2 you will brick your phone if the bootloader and modem versions are not the same.
Before starting to flash any of the files you need to get you up and running on lollipop, I strongly suggest you download all you need from start to finish. Store the files you will need in the upgrade process either on an external sdcard or on the root of your internal sdcard. I haven't used CWM Recovery on my SGS3 since shortly after rooting it, I have been using TWRP since then, and I don't recall all of the capabilities of CWM recovery. If the CWM version you have will not let you flash from an external sdcard you will need to store the files you will use on the root of the internal card to be able to flash them. It will be easier to do this before you start, unless you are comfortable with pushing files from a computer using adb.
BEFORE DOING ANYTHING I AM SUGGESTING read enough that you thoroughly understand what I am saying. After reading, ask questions for clarification. Be sure you have no doubts.
Decide if you intend to install a rom along with the bootloader and modem at each upgrade; or if you are going to install updating only bootloader and modem until you get them to them point that you can run a lollipop ROM. Since you said you can not do OTA updates, either way will work. Whichever you decide, you can not skip directly to the bootloader and modem you need for lollipop.
If you are installing bootloader and modems without the rom:
From the stock 4.1.1 rom and bootloader you can go straight to 4.3 bootloader and modem, skipping the 4.1.2 (MG2) version. I have personally done this with no ill consequences. After 4.3, install the first bootloader and modem version for 4.4.2, that is NE4. Lollipop will run with the NE4 bootloader. As DocHoliday stated, you can go on the the current bootloader and modem. After NE4 is NJ1. After NJ1 you come to the current bootloader and modem, which is NJ2
If you plan to install the full ROM at each step.
The page you linked to should work if all of the downloads are available. Go from 4.1.1 to 4.3 to 4.4.2 (NE4). If you want the newer versions (NJ1 or NJ2) do them in sequence, do not skip any that are mentioned. Read the instructions on your linked page carefully. If you want NJ1 and then NJ2 they can be found in threads by enewman17, as can NE4 and maybe 4.3. I didn't provide the links so that you will hopefully read the pages carefully after searching and before downloading. Be sure you understand what you are downloading to flash and how it should be used.
Click to expand...
Click to collapse
Thanks **** I need to be extra careful before taking any step. I am going to collect all relesed OTA,s. By now I onky need the links for ota. Thanks
Flash MJB and NE4 from the site you linked to above. Then use enewman17's thread for the NJ1 and NJ2 updates. He also has NE4, in case you want to get all the OTA'S from him. (Downloads will be a lot faster) They've all been used many times. I'll try to post a direct link in a few...
Sent from my SGH-T999 using Tapatalk
---------- Post added at 09:48 PM ---------- Previous post was at 09:39 PM ----------
NE4
http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
NJ1
http://forum.xda-developers.com/showthread.php?t=2941792
NJ1 and NJ2
http://forum.xda-developers.com/showthread.php?t=2985006
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Flash MJB and NE4 from the site you linked to above. Then use enewman17's thread for the NJ1 and NJ2 updates. He also has NE4, in case you want to get all the OTA'S from him. (Downloads will be a lot faster) They've all been used many times. I'll try to post a direct link in a few...
Sent from my SGH-T999 using Tapatalk
---------- Post added at 09:48 PM ---------- Previous post was at 09:39 PM ----------
NE4
http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
NJ1
http://forum.xda-developers.com/showthread.php?t=2941792
NJ1 and NJ2
http://forum.xda-developers.com/showthread.php?t=2985006
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got this site having all ota, s . And is linked to the enewman17.
www.androidayos.com/samsung-galaxy-s3-stock-firmware-2/
Lol, I guess they thought they had to provide it somehow! It's a shame they didn't at least acknowledge enewman17 in their article there, but at least they direct linked to his thread.
Anyway, good luck! And if you have any other questions come up, let us know.
Sent from my SGH-T999 using Tapatalk