Develop Bugs

[Q] did i just bricked my phone???

i have seen all the "once you change to the new 4.3 bootloader you can't go back" comments which i thought was no big deal. i don't plan on going back to an older version. anyways here's the story.... i flashed "Stock MOD ROM" by saranhai and the "MJB" bootloader as per the directions for that ROM. i just wasn't feeling that ROM after i used it for a couple weeks but i wanted something stock looking so i thought i would give the "i747z" ROM by agriff a try. so i flashed that rom and the "MJ2" bootloader for that per the directions. In my not so infinite wisdom they are both "4.3" based roms so shouldn't be a problem right???? well as soon as i rebooted the phone after flashing it shut off and has no response after that. soooooooooo did i just brick my phone???

lfaulkner29 said:
i have seen all the "once you change to the new 4.3 bootloader you can't go back" comments which i thought was no big deal. i don't plan on going back to an older version. anyways here's the story.... i flashed "Stock MOD ROM" by saranhai and the "MJB" bootloader as per the directions for that ROM. i just wasn't feeling that ROM after i used it for a couple weeks but i wanted something stock looking so i thought i would give the "i747z" ROM by agriff a try. so i flashed that rom and the "MJ2" bootloader for that per the directions. In my not so infinite wisdom they are both "4.3" based roms so shouldn't be a problem right???? well as soon as i rebooted the phone after flashing it shut off and has no response after that. soooooooooo did i just brick my phone???
Click to expand...
Click to collapse
Checked here when I saw this. http://forum.xda-developers.com/showthread.php?t=2576895 see the linked post in dntesinfrno's post #5.
Bottom line: MJ2 is the leaked firmware & its bootloader behaves similarly to MJB. dntesinfrno's link shows the special handling regarding asserts & the updater script that flashing over MJB demands.

ok.... i read all that and the links and other posts around dntesinfrno's links. still confused.... part of what you said is "they are similar" so to me that means "should be fine" and dntesinfrno talks about "special handling" which i did not do, so now what??? i can't get into download mode or recovery mode from the standard button pushing method so is there anyway to fix this?

lfaulkner29 said:
ok.... i read all that and the links and other posts around dntesinfrno's links. still confused.... part of what you said is "they are similar" so to me that means "should be fine" and dntesinfrno talks about "special handling" which i did not do, so now what??? i can't get into download mode or recovery mode from the standard button pushing method so is there anyway to fix this?
Click to expand...
Click to collapse
I apologize. I get how you saw the v4.3 similarity of MJ2 & MJB but what I am referring to is their similar restrictions limitations & exclusions. Even against each other.
"No Response" describes a hard brick condition. DIY fixes using the phone alone require Odin mode & / or custom recovery.
Odin (download mode) requires an OTA 4.3 flashable tar of UCUEMJB which is not yet available for i747.
That unavailable firmware or its bootloader component is the only safe odin flash for bringing back your phone.
custom recovery would add the safe alternative of reflashing Stock MOD so you could begin again.
I may have seen something helpful for the hard brick. I'll check back & post if I find it.

These are the threads I mentioned:
http://forum.xda-developers.com/showthread.php?t=2559684
http://forum.xda-developers.com/showthread.php?t=2549068
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

AWESOME.... thanks for the help. I think i will attempt to do the fix myself this weekend and if that doesn't work then i will try the ebay fix route. thanks again for your help and i will update as to my success, or lack there of, depending on the outcome.

pc103 said:
Checked here when I saw this. http://forum.xda-developers.com/showthread.php?t=2576895 see the linked post in dntesinfrno's post #5.
Bottom line: MJ2 is the leaked firmware & its bootloader behaves similarly to MJB. dntesinfrno's link shows the special handling regarding asserts & the updater script that flashing over MJB demands.
Click to expand...
Click to collapse
Just to clarify any confusion, my post was regarding installing a ROM that doesn't contain the MJB bootloader in the assert and the dangers involved in attempting to downgrade the bootloader. This will have no affect on recovering from a possible brick after downgrading MJB.

dntesinfrno said:
Just to clarify any confusion, my post was regarding installing a ROM that doesn't contain the MJB bootloader in the assert and the dangers involved in attempting to downgrade the bootloader. This will have no affect on recovering from a possible brick after downgrading MJB.
Click to expand...
Click to collapse
As such I believe your posts detail precisely why downflashingover the MJB, even with MJ2; bricks. Once that happens, the other thread I linked details a possible way out for flashers who missed out on the asserts & updater script due diligence you described. Thanks again for documenting that & for your clarification.

I would like to thank both of you and all the other great people that contributes to this awesome forum!!!
I followed the directions in the link about flashing a debrick image on a 16gb sd card and it worked flawlessly. was almost easier than flashing a Rom to begin with. although I have no intention of having to do that again.
but I have a question, now that I am on the MJB bootloader, when flashing other 4.3 roms from now on I shouldn't need to flash a new bootloader.... correct???
Sent from my SAMSUNG-SGH-I747 using Tapatalk

You're welcome sir. Congrats!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Just recovered from bad encription and need a little help

first of all i was lucky all I had to do was go back and use a root 66 image to recover using odin.
Now i know i will sound like a newb sorry please bear with me if you can.
From the start i was on 4.1.2 on SRx Mod i decided Hay i should encrypt my phone (bad idea i got stuck in a boot loop) so after searching for how to fix it i was told to use the unbrick then i wad told to use route 66 i choose route 66. I have since successfully flashed rooted 4.1.2 but i have a few questions.
First route 66 lets you choose which recovery you wish to use. now to install a recovery (my first root it came with CWM) Should i just download the app and install CWM with rom recovery or use Goo manager to install TWRP? or should i use odin to flash it? if i should flash it where should i get the correct files?
Second.
Say I would like to update to 4.3 and take advantage of roms again. What is the safest way to go about this. Depending on rls I have been able to update via recovery and a new rom and i have had to use odin. I believe (not sure) safest way to go from a major rls to another it should be done with odin. Like going from ICS to JB so should I use odin again to root to 4.3?
So to shorten my question
How do i install recovery on a freshly rooted (re rooted via route 66) Also i am currently runnning 4.12 to update to 4.3 do i need to use odin and a 4.3 image to be safe? or can i install a 4.3 rom and it will update.
In all now that my phone is working I am weary of just trying and want to do it the correct way and now i know trying to use encryption is dumb!
THANKS in ADVANCE i appreciate your help.

When it comes to Recoveries, choos if you want CWM or TWRP. Both are good. Based on that get either Rom Manager app for CWM or Goo Manager for TWRP. Let the app install the recovery for you.
If you want 4.3, then look for Stock Mod Rom in Android Development section. Flash that rom via CWM/TWRP. Make sure to follow the instructions in the Rom's thread. Particularly the part where it wants you to flash ATT insecure kernel. The Rom is Rooted. Do not flash 4.3 via Odin.

Thanks for the refresher
I have been away for a little while and i wanted to make sure. SO to get it straight
Right now I just got back from boot loop with route 66 via odin.
To go on i simply get CWM or TWRP with the respective program (rom manager or goo manager)
Then get the 4.3 rom from the rout66 thread and update to 4.3 via recovery.
If not which rom do i use.
Edit:
Ok now i think i understand your post you directed me to use a specific rom
http://forum.xda-developers.com/showthread.php?t=2501303
So from base 4.1.2 i can update to any 4.3 rom i choose? I just want to make sure as most major releases have some issues at the beginning maybe everything is sorted and their is no problems,
One thing i want to ask is can i choose another rom as sometimes i like to switch to and from touchwiz
So i guess my question now is once i install a recovery program of my choice (i always used CWM so ill probably stick with that)
Can I install any rom no problem? as far as changing versions only go up to 4.3 dont go back down with a recovery flash?
SO AFAIK right now that everything is all good and i wont mess my phone up again when loading a rom.
Is their anything i SHOULD NOT do, Beyond common sense i know not to flash a rom for another phone ETC
I appreciate your help I haven't been following the development for a couple months So i am Rusty also its been a while since i had to start from scratch with odin and at that time we did not have the GREAT list of Official Images so I got a rooted rom that had CWM already installed. I want to get to how i was before when i was enjoying the work of the devs and loving it. being in stock reminds me of how much work the devs do YOU GUYS ARE GREAT (if any even read this thread)

BeatnikBandit said:
Thanks for the refresher
I have been away for a little while and i wanted to make sure. SO to get it straight
Right now I just got back from boot loop with route 66 via odin.
To go on i simply get CWM or TWRP with the respective program (rom manager or goo manager)
Then get the 4.3 rom from the rout66 thread and update to 4.3 via recovery.
If not which rom do i use.
Click to expand...
Click to collapse
Do not do the Red Striked part. Search for Stock Mod Rom by @saranhai

Thank you to be safe i will use the ROM you suggested although this is the only thing that worries me as i never have or really want to flash modems
YOU MUST FLASH THE T999UVUEMJ4 MODEM OR T999UVUEMJC MODEM FOR T-MOBILE GALAXY S III IN ORDER FOR DATA TO WORK; OTHERWISE YOU WILL NOT HAVE DATA
AS USUAL, I'M NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE! ONE WRONG MOVE (Especially with the Modem) AND YOU COULD END UP WITH A VERY EXPENSIVE BRICK. PROCEED AT OWN RISK.
Click to expand...
Click to collapse
This is from the page for the
[ROM][3.9.14] .::StockMOD ROM::. | TouchWiz 4.3 | Galaxy S5 | UVUEMJC | RLS2
http://forum.xda-developers.com/showthread.php?t=2501303
I hope this is the ROM you are talking about and if so what do i do about the modem issue as I am coming from 4.1.2 IDK if i have the correct modem installed. All i have right now is Route 66 rooted 4.1.2 and CWM recovery I also created a Nandroid as soon as i got recovery so i can ave a pretty clean android to go back to if anything happens.
I am sorry i may be annoyed if i were you possibly so i hope you are hanging in there with me i really appreciate it once i do this ill be back in the game and wont need any more help. I just need to get this part sorted, THANK YOU
So other than the modem thing I think i got it, i just hope i dont have to mess with the modem IDK if I'm ready to try something that could hard brick my phone after just recovering it

Flashing the modem won't brick it. It's the exact same procedure as flashing the kernel, and the risk level is pretty much the same. As long as your device is the T999, you don't have anything to worry about. Just check the md5 on the download to make sure its not a corrupted/bad download. Even if you flash the T999L/T999V/I535 modem, it shouldn't brick. It just wouldn't get signal till you flash the correct one again. Many, many people have flashed the modems with no problems at all.
Sent from my SM-N900T using Tapatalk

THANKS DOC
I really didnt think you would answer my post!
Anyway so even though the warning says i can brick it with a modem change really all that will happen is that i will just not get Data until i install the correct one got it.
And unless anyone posts otherwise The first 4.3 rom i should install is Stock Mod Rom by @saranhai and also flash the modem T999UVUEMJC via recovery?
I tried the modem map but i had no success with getting to to work, first it said the link was not supported and i needed to revert to GMaps Classic so i did but i got the same results. Random places all over the world (some in the sea) some said city and modem some were simply city's so i think its out of date so i suppose that the worst that can happen is that i get no data i suppose i can try the other modem listed on the roms page?
If someone knows (as their are two maybe its east west cost or something of the like i live in southern California south of la but furthest from the border of Mexico in San Diego so north San Diego county but anyone that knows the area may know of the massive military base i live south east of Camp Pendleton
(off topic but if a war comes to our shores i pray i am dead already or something divine as i live very close to a large Marine Training base and camp/base in General and right next to it (on the coast) is a dual Nuclear Reactor Power plant and one reactor has been malfunctioning and AFAIK its just being maintained to keep anything catastrophic from happening (which i believe IDK for sure was the reason why it is still running but not producing power)

BeatnikBandit said:
THANKS DOC
I really didnt think you would answer my post!
Click to expand...
Click to collapse
No problem! If I am able and have something to add...
Anyway so even though the warning says i can brick it with a modem change really all that will happen is that i will just not get Data until i install the correct one got it.
Click to expand...
Click to collapse
Many people warn about that because on many devices it is true. just like a kernel or recovery though, if you flash the wrong thing to its partition, it can brick. I.e. If you flash a recovery to the modems partition.
A lot of times people bring habits from their old devices. In our case, while it is possible, it's highly unlikely you'd brick flashing the modem. We know it's not going to flash the wrong item/partition. Several people have tried flashing the I535, T999L, T999N modems and all that happened was they got no working signal. Flashed back to the correct modem and all was good again.
And unless anyone posts otherwise The first 4.3 rom i should install is Stock Mod Rom by @saranhai and also flash the modem T999UVUEMJC via recovery?
Click to expand...
Click to collapse
This would be my recommendation, yes. Just follow instructions in the OP.
I tried the modem map but i had no success with getting to to work, first it said the link was not supported and i needed to revert to GMaps Classic so i did but i got the same results. Random places all over the world (some in the sea) some said city and modem some were simply city's so i think its out of date so i suppose that the worst that can happen is that i get no data i suppose i can try the other modem listed on the roms page?
Click to expand...
Click to collapse
The map is definitely screwed up and I apologize for that! I meant to start a new one a while back but just never got around to it. Still on my to do list!
Good Luck!
Sent from my SM-N900T using Tapatalk

Well thank you guys both I appreciate you gave me the correct info fast Perseus71 and thank you for clarifying DocHoliday77 And an extra thank you for all the work you do for the S III community!

i was just about to do this althoug i downloaded the rom and the modem but now what about the "insecure Kernal" I dont want to mess my phone up again sorry for all the questions its just after you mess up your phone when yoyu come back to roms and its just like getting a traffic ticket for a little bit you drive like you just got a ticket REALLY SAFE with no nerve so sorry but thats my mindset i just messed up my phone and dont want to do it again (i just finished paying for it too so i donk want to break my just paid off 600 dollar car lol.
so yeah AFAIK the post sys all i need is the modem but do i need the kernal too as it may not be listed as it is know its needed at one point when updating versions?
THANKS AND SORRY this is probably the last thing i need as i was just about to flash but just got worried

If wifi doesnt turn on, then try the kernel. If everything boots and runs as you like, then its up to you.
Sent from my SM-N900T using Tapatalk

Going from CM11 To Stock? (Model: Sghi747)

Hey guys, I am new to this forum here but before anyone flames me, I did read the faqs and tried to uninstall from there but it did not work out. Apparently I dont think you can get rid of CM11 since you cant install any stock firmware older than it? Before I installed CM11, I was on jellybean. I had tried to find the latest kitkat update for the s3 (att) and there is no file of it found online (tried sammobile). When I tried flashing an older firmware with ODIN, it just fails at "NAND!". Any help would be appreciated. I am COMPELETELY new at this so specific directions would be appreciated!
I really do love cyanogenmod but there are simply too many glitches and not enough guidance on how to fix em. I am, however, currently using it on my HP touchpad, if anyone remembers what it is . Maybe ill go back to using it in the future.
thanks!

Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.

DocHoliday77 said:
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
Click to expand...
Click to collapse
..
I am on "I747UCUEMJB"
and i am not sure what build i am on but according to my "build number"this is what it says: "cm_d2att-userbug 4.4.2 KOT49H"
The main issue is, I cannot find 4.3 update anywhere on the internet

The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581

DocHoliday77 said:
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
Click to expand...
Click to collapse
i have no idea what MJB means (i google'd it) and i just found out what my bootloader version is via download mode (its at the very bottom) and i have version 2.0?
ok downloading the giant file now. will report details. just follow instructions in the first link?
[sorry, like i said, im a noob so i really apologize for the lack of terms here]

MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.

DocHoliday77 said:
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
Click to expand...
Click to collapse
Cool! Got it. I think that was my main problem. I could only find 4.0 (or 4.1) and have been trying to use that on ODIN. Perhaps that was the main issue....
Oh already ran it and got "I747UCUEMJB", sorry if didnt say it properly.
Really appreciate the help! Ive at this for days and no solutions. Sometimes the hacking/custom firmware isnt for everybody
Ill update what happens. Download is taking forever.
EDIT: BTW, for the first link, which poster am I gonna have to follow? im assuming "garbage guy"?

I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.

DocHoliday77 said:
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
Click to expand...
Click to collapse
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?

david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?

david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
david12795 said:
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
Click to expand...
Click to collapse
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.

DocHoliday77 said:
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
Click to expand...
Click to collapse
TIL that OTA arent as fast. Ill download KIES and give it a try.

Just installed KIES and it said my phone has the latest firmware?

david12795 said:
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
TIL that OTA arent as fast. Ill download KIES and give it a try.
Click to expand...
Click to collapse
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
david12795 said:
Just installed KIES and it said my phone has the latest firmware?
Click to expand...
Click to collapse
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!

DocHoliday77 said:
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
Click to expand...
Click to collapse
No no! Its fine, I wasnt planning using it or anything, I just wanted to get rid of it since I have no use for it, no need to apologize. , I was fully aware that I would lose all files, other than SD ext drive. I just wanted to make sure that all files are in the right place and none of the unnecessary files are taking up space (e.g. files from cyanogenmod)
As for the update, I talked to a samsung representative and they said one can go to Best Buy and get it updated there through a technician, so Ill try that later since I am close to it ATM. If it back fires, Ill try your suggestions.
I really do appreciate for the help , I have been completely lost for days but it turns out I was just using the wrong firmware. Thanks for pointing it out. Good karma is coming your way . Hopefully one day, I will be here again and trying out a new custom firmware.

Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.

DocHoliday77 said:
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
Click to expand...
Click to collapse
Ill hope for the best and prepare for the worst.
Of course, if the worst happens, I can just use one of your links you mentioned. :good::good:

Stuck on Samsung boot screen

I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.

cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!

General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.

cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.

Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.

cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.

Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.

GS3 model confusion

So my dad bought a GS3 and it shows that it's a t999 model in the settings. It's on UVDMD5 has the UVDMD5 radio as well. I was going to odin flash to the new 4.3 root 66 but it threw out an error. I looked at the phone and in download mode it shows it's a i-747 so I'm super confused right now. I also have an s3 myself and when I remove the battery and check my phone it shows model: sgh-t999 and also shows t999 in download mode as well. On the new phone my dad purchased it shows model: GT-T999 where the battery goes. So yeah I'm pretty confused. I managed to flash the tmo twrp and flashed superuser zip and rooted it sucessfully but I wanted to update it to 4.3 but now I'm not even sure what firmware to flash

Looks like yet another frankenphone. Wish I knew where these things were coming from!
Its hard to tell you what to do, but if it currently had MD5 on there, you probably need to stick with T999 firmware. Well, maybe....
Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you what the firmware is. You cant judge by the rom or baseband.
Anyway, almost every time ive seen these things, the recommendation is usually to see if you can return the device. Theres just too many questions and things that dont match up. If you plan on using it as is, and never care about updates and such, I guess it might be ok, but otherwise theres just too great a chance for future problems!
For starters, there's no such thing as a GT-T999. And If download mode says its an I747, id guess youre using the I747 base firmware/bootloader. However, your system and baseband are from the T999 firmware, so we can be pretty confident that flashing I747 firmware will not work. But you probably can only flash I747 firmware because thats what your bootloader appears to be! Very confusing, very messed up, I know! Its highly possible, judging by the GT-T999, that it might be a chinese knock-off.
It may or may not help, but install Phone Info - Samsung app. Then let me know what it tells you. I dont think theres going to be a lot we can do though, but ill be glad to take a look anyway.

DocHoliday77 said:
Looks like yet another frankenphone. Wish I knew where these things were coming from!
Its hard to tell you what to do, but if it currently had MD5 on there, you probably need to stick with T999 firmware. Well, maybe....
Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you what the firmware is. You cant judge by the rom or baseband.
Anyway, almost every time ive seen these things, the recommendation is usually to see if you can return the device. Theres just too many questions and things that dont match up. If you plan on using it as is, and never care about updates and such, I guess it might be ok, but otherwise theres just too great a chance for future problems!
For starters, there's no such thing as a GT-T999. And If download mode says its an I747, id guess youre using the I747 base firmware/bootloader. However, your system and baseband are from the T999 firmware, so we can be pretty confident that flashing I747 firmware will not work. But you probably can only flash I747 firmware because thats what your bootloader appears to be! Very confusing, very messed up, I know! Its highly possible, judging by the GT-T999, that it might be a chinese knock-off.
It may or may not help, but install Phone Info - Samsung app. Then let me know what it tells you. I dont think theres going to be a lot we can do though, but ill be glad to take a look anyway.
Click to expand...
Click to collapse
Yes it was super confusing! It's so weird. I did the getprop ro.bootloader and I got I747UCALI5. I'm kinda scared to odin anything since I really have no idea what model I actually have so I just ended up flashing the latest PA rom & so far everything seems fine

Yup, its exactly as I expected! I747 bootloader/base firmware with T999 system and modem. These are not things that should work together and it also means there is no safe way to update your firmware. LI5 sounds like its really old btw. But tbh, I dont know if its even a real build number! I can say you will not be able to run TW kk roms and might not be able to run 4.3 ones as well. CM/aosp, im not sure about, but I know they were known to be really buggy on older firmware.
If it is an option, I strongly suggest seeing if you can get a refund. May I ask where it was bought from? I think whenever we run into these we need to start letting people know not to purchase from those sellers. For one, to protect folks from having this happen to them, but also to try and discourage this type of business practice (if you even want to call it that!). Its almost as bad as people who sell devices and then report them lost!
---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------
Just checked and LI5 is a real build, but it is old. 4.1.1

DocHoliday77 said:
Yup, its exactly as I expected! I747 bootloader/base firmware with T999 system and modem. These are not things that should work together and it also means there is no safe way to update your firmware. LI5 sounds like its really old btw. But tbh, I dont know if its even a real build number! I can say you will not be able to run TW kk roms and might not be able to run 4.3 ones as well. CM/aosp, im not sure about, but I know they were known to be really buggy on older firmware.
If it is an option, I strongly suggest seeing if you can get a refund. May I ask where it was bought from? I think whenever we run into these we need to start letting people know not to purchase from those sellers. For one, to protect folks from having this happen to them, but also to try and discourage this type of business practice (if you even want to call it that!). Its almost as bad as people who sell devices and then report them lost!
---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------
Just checked and LI5 is a real build, but it is old. 4.1.1
Click to expand...
Click to collapse
Just asked my dad & he said he bought it from a pawnshop which isn't surprising why there is so much confusion about the model lol. Would having an old bootloader cause problems? I was able to flash the latest PA beta but I haven't encountered any issues as of yet

I dont use non touchwiz roms, but I do remember they all started requiring certain bootloaders nrcsuse they were encountering too many bugs on older ones. I dont know any details though.
Id imagine youll encounter issues flashing any rom thst has the assert check. It checks to make sure you have a certain bootloader, and most here will be checking for T999 builds. Since yours has the I747 bootloader, it may cause trouble flashing certain roms.
That and you wont be able to easily or safely update the firmware...
Not sure theres much that could be done since it came from a pawn shop though.

DocHoliday77 said:
I dont use non touchwiz roms, but I do remember they all started requiring certain bootloaders nrcsuse they were encountering too many bugs on older ones. I dont know any details though.
Id imagine youll encounter issues flashing any rom thst has the assert check. It checks to make sure you have a certain bootloader, and most here will be checking for T999 builds. Since yours has the I747 bootloader, it may cause trouble flashing certain roms.
That and you wont be able to easily or safely update the firmware...
Not sure theres much that could be done since it came from a pawn shop though.
Click to expand...
Click to collapse
Yeah this whole situation has been odd. I'll advise my dad to avoid pawnshops from now on lol. Whenever I was in download mode I noticed the flashcount had shown 3 and I ended up using triangle away to reset it when I was still on 4.1.2 for the moment. Before I rooted it or anything it already had supersu installed but I don't think the phone was actually rooted cause everytime I would open supersu it would tell me to update the binary and it would fail each time and any other root apps I installed were denied root. The phone still had stock recovery as well. I honestly thought it was a t-999 up until I was going to flash the nc2 update and it failed and that's when I realized hey this isn't really a t999. I ended up flashing twrp instead and flashed the supersu zip to get root. I flashed paranoid android afterwards and when I went to about phone i noticed everything changed from t-999 to I747 including the modem. It was weird. I ended up reflashing att twrp just to be safe, I flashed the latest modem from at&t, and I crossed my fingers & bravely flashed a zip that updated my bootloader to the latest one for the I747 and it actually worked which was a huge sigh of relief. I reflashed paranoid android afterwards and so far no issues. Now that I updated everything I might end up just flashing a touchwiz rom from the at&t forums. Thanks for your help though, I greatly appreciate it! :good: