[Q] Help with going back to stock (from CM11) - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Glad you have it working.
Way to go Doc.

Damn japi2000. You did that quick good job.

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

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

UCUFNE4 to UCUFNJ1 update 16 gig AT&T I747

The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.​
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872
Thanks enewman for writing this up.
Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!
I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!
mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse

[Q] No carrier/SIM support after 4.3 stock restore

My ATT SGH-i747 was rooted and running 4.4.2 until an OTA this past weekend soft-bricked the phone. Phone would boot to a blank screen but still allowed access to download and recovery modes, thankfully.
With help from this awesome forum, and a stock 4.3 flash via ODIN, thanks to enewman17's epic efforts and thread , the phone is back, but now won't recognize the SIM - and baseband version is "unknown" - I suspect I need to now go up to 4.4.2 to get the hw recognized by the sw. Went to ATT and they put a new SIM in but to no avail
CWM recovery is gone, but I can reload that easily enough...
Do I need to just flash the modem, or is the bootloader involved too?
Is there a single flash or .zip that will get the ROM (incl CSC and Modem) up to 4.4.2 in one shot?
I never really wanted to go this deep but here I am so now I'm looking for advice or direction as there are so many directions to look... thanks in advance!
Mismatch in firmware
Digging deeper, using Phone Info *Samsung*, I have noted the following
bootloader version: I747UCUFNJ1
baseband version: <blank>
pda version: I747UCUEMJB
csc version: I747ATTEMJB
skip a bit...
modem version: <blank>
hardware revision: <blank>
mobile operator name: <blank>
mobile network code: <blank>
So it would seem I have a mis-match of versions, where it seems all should be the same..
Would it be safe to flash to MJB following this thread?
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
OCTANEJUNKIE said:
My ATT SGH-i747 was rooted and running 4.4.2 until an OTA this past weekend soft-bricked the phone. Phone would boot to a blank screen but still allowed access to download and recovery modes, thankfully.
With help from this awesome forum, and a stock 4.3 flash via ODIN, thanks to enewman17's epic efforts and thread , the phone is back, but now won't recognize the SIM - and baseband version is "unknown" - I suspect I need to now go up to 4.4.2 to get the hw recognized by the sw. Went to ATT and they put a new SIM in but to no avail
CWM recovery is gone, but I can reload that easily enough...
Do I need to just flash the modem, or is the bootloader involved too?
Is there a single flash or .zip that will get the ROM (incl CSC and Modem) up to 4.4.2 in one shot?
I never really wanted to go this deep but here I am so now I'm looking for advice or direction as there are so many directions to look... thanks in advance!
Click to expand...
Click to collapse
Your modem (baseband) appears to have been compromised in the process of downgrading from Kitkat. You could try either of the following solutions...
1) Flash the UCUEMJB modem via custom recovery to return you to complete stock 4.3. You can see the modem file here ....
https://www.androidfilehost.com/?fid=23269279319197285
2) Do a complete stock restore to 4.4.2. You can find the stock update zip via the following thread ...
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you can reflash the 4.3MJB modem, you can check to see if you can get an OTA update to 4.4.2. Using Option 2 requires you to be on complete stock 4.3 so this may not work if you currently don't have the baseband/modem. I would strongly advise you stick to the custom recovery flashable files for now and avoid Odin. You would, however, need to restore custom recovery via Odin.
Hope this works for you.
Larry2999 said:
Your modem (baseband) appears to have been compromised in the process of downgrading from Kitkat. You could try either of the following solutions...
1) Flash the UCUEMJB modem via custom recovery to return you to complete stock 4.3. You can see the modem file here ....
https://www.androidfilehost.com/?fid=23269279319197285
2) Do a complete stock restore to 4.4.2. You can find the stock update zip via the following thread ...
http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
If you can reflash the 4.3MJB modem, you can check to see if you can get an OTA update to 4.4.2. Using Option 2 requires you to be on complete stock 4.3 so this may not work if you currently don't have the baseband/modem. I would strongly advise you stick to the custom recovery flashable files for now and avoid Odin. You would, however, need to restore custom recovery via Odin.
Hope this works for you.
Click to expand...
Click to collapse
Thanks for the detailed reply with links, Larry :good:
So I guess my plan of actions will be
1) re-install custom recovery w CWM to my external SD card as was previous
-do I *need* later version of CWM? Previous one of mine was 6.0.2.3, IIRC, that is what I can easily flash back to the phone
2) install .zip (from https://www.androidfilehost.com/?fid=23269279319197285) via CWM
If that doesn't work, I was interested in the S3Rx ROM vs. a stock 4.4.2 ROM - is there any way to go straight to a custom 4.4.2 ROM or should I get the modem working in 4.3 first?
Lastly, Where can I find a later version of a CW Recovery Touch .tar to flash via ODIN? (third stoopid noob question in this post, I know...)
Attempt to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip via CWM Recovery FAILED with Status 7, Installation aborted...
Bootloader version: I747UCUFNJ1
Baseband version: <blank>
Blank stare into space...
OCTANEJUNKIE said:
Attempt to flash d2att_I747UCUEMJB_bootloader_modem_4.3.zip via CWM Recovery FAILED with Status 7, Installation aborted...
Bootloader version: I747UCUFNJ1
Baseband version: <blank>
Blank stare into space...
Click to expand...
Click to collapse
You aren't the first to have this issue. This is why I am still on NE4 and did not take the OTA to NJ1. The update is pointless anyway, all it does is patch the kernel so towelroot won't work anymore aside from updating the bootloader.
Since your bootloader is NJ1, that is your firmware which cannot be downgraded. If you try, you will brick. You have to work with NJ1 files here only. Sure you can flash older modems, but stick to NJ1. I suggest using ODIN to flash a custom recovery, then use enewman17's NJ1 .zip file in said recovery to reflash all the NJ1 stuff. Then do a complete factory reset. You might need to flash stock recovery to do the hard factory data reset, as I am not sure if it can be done in CWM or TWRP.
In the future, I suggest freezing the update and not upgrading until people on here do it and report how it's working or rather not working in this case.
StoneyJSG said:
You aren't the first to have this issue. This is why I am still on NE4 and did not take the OTA to NJ1. The update is pointless anyway, all it does is patch the kernel so towelroot won't work anymore aside from updating the bootloader.
Since your bootloader is NJ1, that is your firmware which cannot be downgraded. If you try, you will brick. You have to work with NJ1 files here only. Sure you can flash older modems, but stick to NJ1. I suggest using ODIN to flash a custom recovery, then use enewman17's NJ1 .zip file in said recovery to reflash all the NJ1 stuff. Then do a complete factory reset. You might need to flash stock recovery to do the hard factory data reset, as I am not sure if it can be done in CWM or TWRP.
In the future, I suggest freezing the update and not upgrading until people on here do it and report how it's working or rather not working in this case.
Click to expand...
Click to collapse
Thanks for the response, Stoney :good:
I have CWM and TeamEpic v5 on external SD, so a version of custom recovery is there (CWM 6.0.2.3) - but do you have a link to enewman17's NJ1 .zip /recovery?
As far as freezing the updates in the future, yes. I tried to keep the OTA push from happening, apparently not ardently enough :crying:
OCTANEJUNKIE said:
Thanks for the response, Stoney :good:
I have CWM and TeamEpic v5 on external SD, so a version of custom recovery is there (CWM 6.0.2.3) - but do you have a link to enewman17's NJ1 .zip /recovery?
As far as freezing the updates in the future, yes. I tried to keep the OTA push from happening, apparently not ardently enough :crying:
Click to expand...
Click to collapse
Not a problem, glad to help when I can. I THINK this is the link you need: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
You might want to post in that thread asking if it works when you are already on NJ1 though, or get a hold of enewman17 via PM or something.
SOLVED!
enewman17 posted NJ1 modem .zip here, and now me has modem and cellular service again!
Question: can I update the thread tag from [Q] to [SOLVED] myself?
Try editing your original post.
audit13 said:
Try editing your original post.
Click to expand...
Click to collapse
Yup... Done [emoji222] [emoji222] [emoji222]

[Q&A] [ROM] I747UCUFNE4_AT&T 4.4.2 Stock ROM & System Dump

Q&A for [ROM] I747UCUFNE4_AT&T 4.4.2 Stock ROM & System Dump
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] I747UCUFNE4_AT&T 4.4.2 Stock ROM & System Dump. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
help
i have being trying to update my samsung SGH i747 to version 4.4.2 for a very long time now but with no luck, i just saw your files at when i was doing a research now so i followed it untill i got to your thread here, i am so happy about it.
I will lke to ask you this, i followed some tutorials some months ago and i upgraded my fone (I747) baseband to I747UCUFNE4 also the build number is JSS15J.I747UCUEMJB. The andriod version is currently 4.3 but has 4.4.2 baseband. i will like to ask if i flash your provided file I747UCUFNE4_Stock_Rooted_Deodex or I747UCUFNE4_Stock_Rooted_Odex want i brick my phone?
also i will like to ask with the "Samsung_SGH-I747_4.4.2_OTA_update.zip" file you provided how can i use that to update my phone (if only possible). Should i use odin or via recovery. Thank you
flashable tar via odin for 4.4.2?
Does anyone know if there is a 4.4.2 flashable tar via odin? I was running on 4.3 with 4.4.2 baseband version and I couldn't install custom ROM so I use EZ unlock to unlock the bootloader (stupid me didn't know it only works on Verizon phone) and my phone went into hard brick. I was able to debrick and get into download mode but so far unable to start the phone without the microSDard. Any help would be appreciated. Thanks!
hatboy03 said:
Does anyone know if there is a 4.4.2 flashable tar via odin? I was running on 4.3 with 4.4.2 baseband version and I couldn't install custom ROM so I use EZ unlock to unlock the bootloader (stupid me didn't know it only works on Verizon phone) and my phone went into hard brick. I was able to debrick and get into download mode but so far unable to start the phone without the microSDard. Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
No ODIN tar file for 4.4.2 , Samsung and/or at&t only released it as an OTA update.
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
invisibleguy said:
i have being trying to update my samsung SGH i747 to version 4.4.2 for a very long time now but with no luck, i just saw your files at when i was doing a research now so i followed it untill i got to your thread here, i am so happy about it.
I will lke to ask you this, i followed some tutorials some months ago and i upgraded my fone (I747) baseband to I747UCUFNE4 also the build number is JSS15J.I747UCUEMJB. The andriod version is currently 4.3 but has 4.4.2 baseband. i will like to ask if i flash your provided file I747UCUFNE4_Stock_Rooted_Deodex or I747UCUFNE4_Stock_Rooted_Odex want i brick my phone?
also i will like to ask with the "Samsung_SGH-I747_4.4.2_OTA_update.zip" file you provided how can i use that to update my phone (if only possible). Should i use odin or via recovery. Thank you
Click to expand...
Click to collapse
Flashing the NE4_stock_rooted file shouldn't brick your phone, but don't quote me on it. You use the Samsung_SGH-I747_4.4.2_OTA_update.zip in a custom recovery like clockwork mod.
StoneyJSG said:
No ODIN tar file for 4.4.2 , Samsung and/or at&t only released it as an OTA update.
Click to expand...
Click to collapse
darn it. Thanks.
No O/S - can only boot into download mode
I've got an interesting one. I was prepping my phone for selling, decided to clear out all the memory. Somehow I must have deleted more than I meant to b/c when I restarted the phone, it just hangs on the Samsung screen. I can get into download mode, but not into recovery and nothing ever loads. I tried at least one version of installing CWM but it doesnt look like I can boot into recovery even after the Odin install appears ok. Before the crash, I was running a modded 4.4.2 rom with the bootloader and other things that come with it. Is there anything I can do to get this thing up and running again?
Thanks1
WIFI??
Just tried to flash ODEX version and now my WIFI is not working?
Any suggestions please?
EG777 said:
Just tried to flash ODEX version and now my WIFI is not working?
Any suggestions please?
Click to expand...
Click to collapse
Does the bootloader and modem on your phone match this rom? That could be why wifi won't work. You can check by entering this in a terminal app or adb shell; if they don't end in NE4 it is probably part of your problem:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
If you don't want to mess with the bootloader and modem on your phone you might be able to get everything working by flashing a custom kernel. Try the ktoonsez touchwiz versions with this rom. Just flash the kernel in recovery like you did the rom (no wipes for kernel, just install - although if you find it won't boot maybe try wiping cache and dalvik) and it will overwrite the default one the rom was packaged with. A nandroid backup of boot could revert the kernel if kt causes any problems.
Thank you!
jason2678 said:
Does the bootloader and modem on your phone match this rom? That could be why wifi won't work. You can check by entering this in a terminal app or adb shell; if they don't end in NE4 it is probably part of your problem:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
If you don't want to mess with the bootloader and modem on your phone you might be able to get everything working by flashing a custom kernel. Try the ktoonsez touchwiz versions with this rom. Just flash the kernel in recovery like you did the rom (no wipes for kernel, just install - although if you find it won't boot maybe try wiping cache and dalvik) and it will overwrite the default one the rom was packaged with. A nandroid backup of boot could revert the kernel if kt causes any problems.
Click to expand...
Click to collapse
Now I see what you mean! THANK YOU for your response.
It seems by Bootloader does not match after all as it ends in NJ1.
EG777 said:
Now I see what you mean! THANK YOU for your response.
It seems by Bootloader does not match after all as it ends in NJ1.
Click to expand...
Click to collapse
OK. Either flash the KT kernel, or this ROM https://www.androidfilehost.com/?fid=95784891001613266
Either one should get your phone working right again.
EG777 said:
Now I see what you mean! THANK YOU for your response.
It seems by Bootloader does not match after all as it ends in NJ1.
Click to expand...
Click to collapse
usually it is wise to have bootloader and modem match. if bootloader is NJ1 , then modem needs to match. there's a thread here somewhere.
http://forum.xda-developers.com/showthread.php?t=2941792
here is the link to a flashable nj1 bootloader/modem if you want. PLEASE - make a backup & read read read. good luck.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Help
My galaxy s3 I747 not start.
The phone won't power up or it won't fully boot the rom? Did something happen to the phone that may have caused the issue?

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