Develop Bugs

4.1.2 to 4.3 or not? t999v

Hey just wondering if I should do the update to stock 4.3 OTA or not. I've been looking at the root66 knox free 4.3 and it sounds good. Any Issues with it? or stock OTA? I've read mixed reviews, and am now confused. Also if I do install root66 on this wind t999v, am I required to install the stock OTA 4.3 update for it to work? Or am I in a better situation if I just install it from 4.1.2? Also any basic instructions on what I would have to do to install root66 would be much appriciated. I'm technologically inclined, just been out of the cellphone moding scene for quite some time, and just want to ask before I start asking how to unbrick. Thanks in advance.:good:

Knox Free Root 66 is always preferred over Stock update. The instructions and all the necessary files are in the Root66 Thread.
In short you need Odin v 3.xx Need to have the Drivers installed for your phone. Make sure Kies is not installed on your PC. Put your phone in Download mode and then connect to pc. Flash the Root66 file and you are done. There are several tutorials on Youtube for how to use Odin.
Note - For your Knowledge, please read on the 4.3 and its locked bootloader.

The root66 works fine on the wind phone and disables knox. it doesn't trip the flash counter so warranty is still intact if you had to flash back to a knox-rom. once you get into custom roms', the flash counter gets tripped though.
i just installed the 4.4.2 likewise rom, and it is smoooooooth. lol. it's not official though.

Perseus71 said:
Kox Free Root 66 is always preferred over Stock update. The instructions and all the necessary files are in the Root66 Thread.
In short you need Odin v 3.xx Need to have the Drivers installed for your phone. Make sure Kies is not installed on your PC. Put your phone in Download mode and then connect to pc. Flash the Root66 file and you are done. There are several tutorials on Youtube for how to use Odin.
Note - For your Knowledge, please read on the 4.3 and its locked bootloader.
Click to expand...
Click to collapse
How do I know which wind pre-installed root firmware to install:
WIND Image
December 2013 - 4.3 JellyBean
Note: This is based off of the stock image GLW T999VVLUEMK5
Download :: Download - root66_GLW_T999VVLUEMK5.7z
June 2013 - 4.1.2 JellyBean
Note: This is based off of the stock image GLW T999VVLDMF2
Perm Mirror: Download - root66_GLW_T999VVLDMF2.7z
December 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image GLW T999VVLDLL1
Perm Mirror: Download - root66_GLW_T999VVLDLL1.7z
my s3 is on 4.1.2 so do I download that one or is that the firmware that will be newly installed? I want 4.3 newly installed.

Please flash root66_GLW_T999VVLUEMK5.7z

Also on http://forum.xda-developers.com/showthread.php?t=1949687 they have 4 files, sorry for all the questions
Wind_VLUEMK5
Updated JB Firmware
Wind_VLDMF2
Updated JB Firmware
Wind_VLDLL1
Updated JB Firmware
Wind_VLALH2
Updated ICS Firmware

Perseus71 said:
Please flash root66_GLW_T999VVLUEMK5.7z
Click to expand...
Click to collapse
Even if my current s3 firmware is 4.1.2 baseband t999vvldmf2 ?

Yes that's fine. It will update your Bootloader.

upgrade not good
kreso3k said:
Hey just wondering if I should do the update to stock 4.3 OTA or not. I've been looking at the root66 knox free 4.3 and it sounds good. Any Issues with it? or stock OTA? I've read mixed reviews, and am now confused. Also if I do install root66 on this wind t999v, am I required to install the stock OTA 4.3 update for it to work? Or am I in a better situation if I just install it from 4.1.2? Also any basic instructions on what I would have to do to install root66 would be much appriciated. I'm technologically inclined, just been out of the cellphone moding scene for quite some time, and just want to ask before I start asking how to unbrick. Thanks in advance.:good:
Click to expand...
Click to collapse
i want to downgrade, but cannot find any way to downgrade.

welcome2you said:
i want to downgrade, but cannot find any way to downgrade.
Click to expand...
Click to collapse
because you cannot downgrade from 4.3 firmware.

[Q] Back to 4.3 Stock Rom to Unlock the phone?? HELP

Hello everyone,
I have searched the site for some ways to unlock my device. I am running liquidsmooth 4.4.4 and as far as I know there is no way to unlock customs Roms running 4.3/4.4, unless you go back to the original stock rom and use either AT&T or third party site unlock code. So, I called AT&T and they provided me with the unlock code and they told me the same thing, the unlock code will not work until you go back to the original factory stock rom!
So, I have been searching here for the right 4.3 stock rom and I found out many posts and I got confused which to use. I would highly appropriate it if any one can help me and direct me to the right source/process for 4.3 stock rom steps and installation so I won't brick my phone.
Thanks in advance

GueSs_me said:
Hello everyone,
I have searched the site for some ways to unlock my device. I am running liquidsmooth 4.4.4 and as far as I know there is no way to unlock customs Roms running 4.3/4.4, unless you go back to the original stock rom and use either AT&T or third party site unlock code. So, I called AT&T and they provided me with the unlock code and they told me the same thing, the unlock code will not work until you go back to the original factory stock rom!
So, I have been searching here for the right 4.3 stock rom and I found out many posts and I got confused which to use. I would highly appropriate it if any one can help me and direct me to the right source/process for 4.3 stock rom steps and installation so I won't brick my phone.
Thanks in advance
Click to expand...
Click to collapse
If your bootloaders are on 4.4, you can't downgrade them (or you'll brick!).
You can use Terminal Emulator to know which one you're on:
Code:
getprop ro.bootloader
Once you know which one you have, you can go ahead and grab its stock version.

http://forum.xda-developers.com/showthread.php?t=1968625
i think this thread provides stock downloads.
good luck.
err on the side of kindness

BWolf56 said:
If your bootloaders are on 4.4, you can't downgrade them (or you'll brick!).
You can use Terminal Emulator to know which one you're on:
Code:
getprop ro.bootloader
Once you know which one you have, you can go ahead and grab its stock version.
Click to expand...
Click to collapse
Thanks for the reply, I checked the bootloader as you said and I got ( I747UCDLK3 ). So, I am guessing that I am still on 4.3 because the last bootloader update was through this process:
http://forum.xda-developers.com/showthread.php?t=2387423
I tried to flash the stock file update4.3.zip on that thread using TWRP but it did not work.
Any idea?
Thanks again

mrrocketdog said:
http://forum.xda-developers.com/showthread.php?t=1968625
i think this thread provides stock downloads.
good luck.
err on the side of kindness
Click to expand...
Click to collapse
Thanks for your kind reply. Is there any different to choose between the download options. I know it says the first one is the newest one, I am downloading
http://forum.xda-developers.com/showthread.php?t=2496425
So I hope it is the right one!?
I already have the stock rom 4.3 from
http://forum.xda-developers.com/showthread.php?t=2387423
But as I said on the previous reply not sure why I can't flash the update43.zip through the recovery?
Best,,,,

GueSs_me said:
Thanks for the reply, I checked the bootloader as you said and I got ( I747UCDLK3 ). So, I am guessing that I am still on 4.3 because the last bootloader update was through this process:
http://forum.xda-developers.com/showthread.php?t=2387423
I tried to flash the stock file update4.3.zip on that thread using TWRP but it did not work.
Any idea?
Thanks again
Click to expand...
Click to collapse
LK3 is 4.1.1. I'm guessing the 4.3 bootloaders update didn't work at all.
Now that you know you have LK3, just grab the stock firmware and flash it. (backup first)

thanks @BWolf56.
:GOOD:
err on the side of kindness

BWolf56 said:
LK3 is 4.1.1. I'm guessing the 4.3 bootloaders update didn't work at all.
Now that you know you have LK3, just grab the stock firmware and flash it. (backup first)
Click to expand...
Click to collapse
This is really strange. So, if I may ask, how my bootloader is still 4.1.1 and I am able to flash 4.3/4.4 roms? Also, if I install I747UCDLK3 can I go back to 4.3 custom roms without updating the bootloader!!! because that what I did last time I follwed the steps in below web site to be able to flash 4.3 rom,,,,, but apparently I am still on 4.1.1 bootloader!!
http://forum.xda-developers.com/showthread.php?t=2387423

4.3 roms could still be flashed on older firmware. 4.4 roms too as long as they are not touchwiz. If its a touchwiz 4.4.2 rom you must have at least 4.3 firmware though.

Hi i want to know if i can flash an original 4.3 firmware my bootloader is I747MVLUFNE6 can i go back or i will brick my phone if i tried?

No you cannot downgrade firmware. You can only flash the same or newer builds. Or you can flash older roms and kernels, but nothing else.

[Q] N900TTMBBMI7 to N900TUVUDNF1 Upgrade

Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!

re: NF1 firmware
calderonr said:
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
Click to expand...
Click to collapse
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!

Misterjunky said:
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Click to expand...
Click to collapse
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!

calderonr said:
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
Click to expand...
Click to collapse
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
---------- Post added at 11:27 AM ---------- Previous post was at 11:16 AM ----------
In case you can't see my sig due to being in xda app or tapatalk:
NF4 files and instructions: http://forum.xda-developers.com/showthread.php?t=2834398
Or if you're dead set on NF1, there's a link to that thread at the top of the NF4 post. The instructions in post 2 of the nf4 thread are valid for nf1 add well.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T

toastido said:
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF4 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF4 there is no way to revert back to MI7?
3) Does your NF4 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
5) What about rooting? Is your firmware rooted or do I need to do it myself? If so, what do you recommend for rooting?
Thanks!!!

calderonr said:
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF1 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF1 there is no way to revert back to MI7?
3) Does your NF1 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
Thanks!!!
Click to expand...
Click to collapse
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T

toastido said:
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!

calderonr said:
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
Click to expand...
Click to collapse
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T

toastido said:
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!

calderonr said:
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
Click to expand...
Click to collapse
No it would not work. The reason, as stated in a previous post, is due to eFused bootloaders. Once the efuse is tripped, it cannot be reset, and the bootloader will fail if it's value is lower than the fused value. Otherwise just flashing the bootloader backwards would work. If you go the odin route you will be protected by odin mode. If you try via recovery of a nandroid that contains the bootloader, it'll either just not work, or (worse) brick your device.
The fuses are tripped in a sequential order. 0,1,2,3 etc. JB BL can only operate on fused value of 1 or lower. KK BL can only install and function (depending on current version) at 3 or lower.
NB4 will fuse to 2. NE6 through NF4 I believe will fuse to 3, thus preventing the JB BL from functioning.
Hope that helps.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T

Let me know how it goes. I have to update mine to.. I'm on NB4 with no issues but I should update anyways.
Sent from my SM-N900T using XDA Free mobile app

[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?