[Q] Update to 4.3 from rooted 4.1.1 - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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.

Related

[Q] Official 4.3 Upgrade Issues

I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...
Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.
As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
I had the same problem
I just had this same problem and was lucky enough to fix it!!!!
vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it
Have you tried the auto root course??
Sent from behind you
Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.
Co-author root didn't work, and nor did Root66
I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?
You can try first wiping just dalvik and cache, then try factory reset.
Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.
I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.
I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. VoilĂ  !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?
DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk

[Q] Confused about downgrading 4.3 to 4.1.2

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.

[Q] Cannot update bootloader?

Hello, I was originally running a beta version of Panandroid 3.99, and then I flashed a Stock modified Tmobile Rom on 4.3. I wanted to see if I could get wifi calling to work on it and it did, then I wanted go back to Quantum Rom.
For some reason I could not get Quantum Rom to flash, TWRP would read a "unable to .zip or something like that. Then I read I should update my Bootloader and Modem. So I restored an old backup to Cyanogen mod 10.1.2 (4.2.2 Update). I was able to flash my modem to the MJB update, but whenever I tried to flash my bootloader to the MJB update, TWRP and CMW would both give me Status 6 errors.
I am currently on the LK3 modem as stated by my Terminal Emulator.
Any suggestions on what I should do?
I'm also confused on how I was able to flash Panandroid 3.99(4.4.2 KitKat) on the LK3 modem? Should I have needed the MJB modem in the first place?
The bootloader and device ID is normally what determines if a rom can be flashed to a phone, not the modem.
Visit the S3Rx post and scroll down to the download area and you will see the modem and bootloader flashable zips. I would go with the MJ2 bootloader /MJB modem combo to allow you to go backwards in bootloader if needed.
You may need to update TWRP to the latest, I understand that 4.4 roms require the latest.
Sent from my I-747 using xda app-developers app
Hay350 said:
Visit the S3Rx post and scroll down to the download area and you will see the modem and bootloader flashable zips. I would go with the MJ2 bootloader /MJB modem combo to allow you to go backwards in bootloader if needed.
You may need to update TWRP to the latest, I understand that 4.4 roms require the latest.
Sent from my I-747 using xda app-developers app
Click to expand...
Click to collapse
I think you meant the MG2 bootloader, which did install fine. After that, I was able to flash Quantum and GAPPS.
Thanks a bunch! :highfive:
Gamesrock22 said:
I think you meant the MG2 bootloader, which did install fine. After that, I was able to flash Quantum and GAPPS.
Thanks a bunch! :highfive:
Click to expand...
Click to collapse
Glad that fixed the issue. :good:
Actually, I meant MJ2. Interesting enough I now see is not on the boot loader list thread (http://forum.xda-developers.com/showthread.php?t=2321310) and appears to only be found on the custom 4.3 TW roms sites (which references to the S3RX rom thread (http://forum.xda-developers.com/showthread.php?t=2252932).
LK3 - 4.1.1
MG2 - 4.1.2 (OTA)
MJ2 - Leaked 4.3
MJB - Official 4.3 (OTA)(make sure you read the warnings if you go to this boot loader - there is no going backwards)
So unless you need to go to a 4.3 boot loader, which it sounds like you do not, I would stay where you are.

reverting to 4.1.1

i have the s3 att on a 4.4.4 CROM. the baseband says ...LK3. can i use any guide using odin to go back to 4.1.1 stock unrooted and then use OTA updates to get the latest baseband/bootloader/modem? just want to make sure before i do it. i hear this is the safest way and i want to make sure i have met the requirements before i do it so i dont end up having a brick! (not sure if it matters but i have never used OTA updates before)
thanks in advance.
Is your bootloader also the lk3? If the modem and bootloader are lk3, you can use Odin to flash back to stock using firmware from sammobile.com.
Ok, I'm on a similar boat. I tried several AOSP based ROMs, and while I like most of them a lot more than stock touchwiz, they all present the same problems:
- Camera stops working sometimes and I have to reboot device;
- Camera won't record videos in 1080p, even when it's selected in the settings;
- Cannot make video calls on Skype longer than 5 seconds before the call drops;
- Disconnecting a bluetooth media device while music is streaming causes sounds to stop working;
- Tap to pay doesn't work at all;
So because of these problems, I want to go back to stock . My phone is the AT&T version. Currently I'm running Carbon Rom with KitKat 444. The baseband version is I747UCUFNJ1. The latest version of the stock ROM available on sammobile is:
Version: Android 4.1.1
PDA: I747UCDLK3
CSC: I747ATTDLK3
MODEM: I747UCDLK3
Would I be able to revert my phone back to stock with Odin? If not, what would I have to do to revert? Am I stuck with custom ROMs?
I'm pretty new to this so I'd appreciate anybody's help.
If your bootloader and modem is the lk3, you should be able to Odin back to stock 4.1.1.
Ok, how do I find out if they are? And if they are not, do I have any other options?
Download and install the Samsung Info App from the Playstore. Report back here with your bootloader and modem.
audit13 said:
Download and install the Samsung Info App from the Playstore. Report back here with your bootloader and modem.
Click to expand...
Click to collapse
Ok, according to the Phone INFO *Samsung* app:
Baseband Version:
I747UCUFNJ1
Bootloader Version:
I747UCUFNJ1
There was no other modem info reported besides this
Modem Board:
MSM8960
someone correct me if i'm wrong.you cannot downgrade bootloader or it will brick. there is no stock rom for NJ1. this link will take you to a stock based 4.4.2 ROM which is safe to flash with the NJ1 bootloader/modem.
http://forum.xda-developers.com/showthread.php?t=2848080
"all i can really do , is stay out of my own way and let the will of heaven be done"
mrrocketdog said:
someone correct me if i'm wrong.you cannot downgrade bootloader or it will brick. there is no stock rom for NJ1. this link will take you to a stock based 4.4.2 ROM which is safe to flash with the NJ1 bootloader/modem.
http://forum.xda-developers.com/showthread.php?t=2848080
Click to expand...
Click to collapse
Well, that's a bummer if I can't restore stock rom to the phone. So there is absolutely no way of safely downgrading the booatloader?
nope. it will brick your phone if you try to downgrade your bootloader.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Have you tried CM-11-based or TW-based ROMs?
mrrocketdog said:
someone correct me if i'm wrong.you cannot downgrade bootloader or it will brick. there is no stock rom for NJ1. this link will take you to a stock based 4.4.2 ROM which is safe to flash with the NJ1 bootloader/modem.
http://forum.xda-developers.com/showthread.php?t=2848080
Click to expand...
Click to collapse
I tried to push that ROM the phone using adb to flash it with ClockWorkMod, but the file is 1.7 GB and the phone always shuts itself down during the push process... So I wasn't able to try that. Also, the instructions say you're supposed to be on UCUFNE4. Are you sure it's safe to flash it on I747UCUFNJ1?
audit13 said:
Have you tried CM-11-based or TW-based ROMs?
Click to expand...
Click to collapse
I have tried CM11 and Carbon ROM, which is CM based, both have all the same problems. I haven't tried TW-based ROMS. Do you have any suggestions?
What do you mean by the phone shuts down? Did you try copying the ROM to a microSD card?
Did you notice any bootloader or modem files in the S3Rx 4.0 (11-9-14) ROM? It may not include a modem or bootloader. In step 1 of the flash process, it says "AT&T I747 users should update bootloaders and modem to NE4 http://forum.xda-developers.com/gala...pdate-t2808654 I747M and T999 users need to be on 4.3 firmware or ROM will not boot. "
the link i posted is TW. post #1306 claims is o.k. to flash with UFNJ1.
did not see any mention of bootloader or modem in changelog or in list of 'extra' features.
"all i can really do , is stay out of my own way and let the will of heaven be done"
audit13 said:
What do you mean by the phone shuts down? Did you try copying the ROM to a microSD card?
Did you notice any bootloader or modem files in the S3Rx 4.0 (11-9-14) ROM? It may not include a modem or bootloader. In step 1 of the flash process, it says "AT&T I747 users should update bootloaders and modem to NE4 http://forum.xda-developers.com/gala...pdate-t2808654 I747M and T999 users need to be on 4.3 firmware or ROM will not boot. "
Click to expand...
Click to collapse
I reboot the phone in ClockWorkMod recovery. Then I go to the command prompt and type:
Code:
adb push S3Rx_UCUFNE4_AROMA_11-9-14.zip /sdcard/
It starts pushing the file to the phone, but after a while, the phone screen goes black, and I get a "Protocol failure" on the command prompt. After this the power button no longer works, I have to do a battery pull for the phone to work again. The phone has 10 GB of storage left so it didn't run out of space. The USB chord is brand new so I don't think it's that either. It worked fine before when I pushed other smaller roms.
In another question, would this process allow me to downgrade the modem and restore stock rom?
http://forum.xda-developers.com/showthread.php?t=1831898
i am pretty sure that since youre on MJ1 , your bootloader and modem have to match.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Did you try flashing the card from an external microSD card?
AT&T never released a stock ROM for the i747 beyond 4.1.1 afaik; therefore, you cannot get back to stock unless you flash an OTA ROM that has been compiled for flashing in Odin.
I do not recommend mixing and matching bootloaders and modems as a mismatch may result in a hard brick.
Downgrading only the modem will not allow you to flash back to stock.
audit13 said:
Did you try flashing the card from an external microSD card?
Click to expand...
Click to collapse
I haven't tried flashing from external microSD card as I don't have one.
audit13 said:
AT&T never released a stock ROM for the i747 beyond 4.1.1 afaik; therefore, you cannot get back to stock unless you flash an OTA ROM that has been compiled for flashing in Odin.
I do not recommend mixing and matching bootloaders and modems as a mismatch may result in a hard brick.
Downgrading only the modem will not allow you to flash back to stock.
Click to expand...
Click to collapse
So you're basically telling me I'm stuck with custom roms unless I find a 4.4.2 OTA ROM I can flash with Odin (which doesn't appear to exist)?
---------- Post added at 05:24 PM ---------- Previous post was at 05:01 PM ----------
Would it be safe to try this:
http://forum.xda-developers.com/showthread.php?t=2788357
Even though I'm on I747UCUFNJ1 and not on I747UCUFNE4?
Once you upgrade to the 4.3 or newer bootloader on the i747, you are stuck with either custom ROMs or OTA ROMs that have been compiled for flashing in Odin or CWM/TWRP.
You can try flashing the NE4 ROM because it doesn't appear to include a bootloader or modem. The first post says "Prerequisites include a minimum of a 4.3 bootloader and modem.
If you are not on the official 4.4.2 bootloaders and modem then you will need to flash ktoonsez kernel."
Thanks audit13 and mrrocketdog for all the help. I was able to get the AROMA rom installed on the phone. All functionalities lost with AOSP ROMs are back working so that's a plus. Still can't get updates OTA updates but this phone is probably not gonna have any new ones. Still hopeful that lolipop based AOSP ROMs fix the problems I had, but I'm not holding my breath.

Help me downgrade my galaxy s3 i747

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

Categories

Resources