Develop Bugs

Galaxy S4 M919 need some advice/help.

Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat

Den Den said:
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Click to expand...
Click to collapse
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.

To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.

lordcheeto03 said:
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
Click to expand...
Click to collapse
Should i keep the 4.4.2 kitkat thats not working with my usa sim card atm? Or should i flash it to 4.2.2. ADL? If having 4.2.2 is better doing that guide i put link to above, then give me a good tut on doing it, need to do it today xD THanks in Advance!

HampTheToker said:
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
Click to expand...
Click to collapse
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!

Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.

Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.

lordcheeto03 said:
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Click to expand...
Click to collapse
That Makes sense...just trying to grasp info. on everything so it's more clearer ;p and thanks for correcting me, yea it was data lol.

HampTheToker said:
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
Click to expand...
Click to collapse
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)

Den Den said:
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Click to expand...
Click to collapse
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!

lordcheeto03 said:
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
Click to expand...
Click to collapse
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/

Den Den said:
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Click to expand...
Click to collapse
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker

lordcheeto03 said:
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
Click to expand...
Click to collapse
Flashed ADL using odin, somehow got the menu to work(couldnt budge for some reason to umts), went thru all the steps, it rebooted, put it back to download mode, and flashed it back to nb4. Put my simplemobile simcard in, still nothing, am I supposed to put a different sim card in like ATT or something for it to work? Confused why it didnt work, yet it still detects the MTC european version simcard(not in service, but it had a pin set on it, so it always asks you to unlock the sim with the sim pin u put on it to view ur files on it, etc). Am i doing something wrong? I could give you more info on the phone...
Edit: Just checked on Swappa.com of my imei and got this =/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nvm, Looks like i think its blocked on Tmobiles network, but i put in the H2O sim and it worked.(under ATT) phew....

Seriously need some help. At the end of my patience with trying to update this thing

I'm really frustrated. I've been trying to update this Galaxy S3 for days now with no success. Currently I am running on Slimkat 7.0. It's sometimes slow and buggy and needs some updating.
For reference, this is the phone at its current state:
- Bootloader: i747ucalh9 (literally taken from the fail message when trying to update to any other bootloader)
- Modem/firmware (?): I747UCLH9
Here's what has happened, greatly summarized (note I'm using CM6.0.4.7 for all of these operations, and when I say "update", I mean "flash"):
- I tried updating to Slimkat 9 but received no signal. I gave up on it entirely for a while
- I tried installing various LP ROMs, including CM12.1.
- I had 12.1 running for a bit, but I had no connectivity. LTE, 3G,H+ nothing.
- I tried installing a newer modem (this thread. Finally at MJB, I could actually get connectivity in some of the newer ROMs (including Slimkat 9)... but it was very erratic. It would just randomly oscillate between LTE and 3G and H+. This also broke CM12.1 entirely.
- Again, the above problem was always present. Most of the LP ROMs would just bootloop me, though. The only one that worked was Cyanide L... which I didn't really like.
- I thought maybe the issue was the bootloader. My bootloader is still i747ucalh9. So I tried updating it to various bootloaders from here, but none of the updates will work. Literally, they give me error 6 or 7 and pretty much essentially tell me that I can't do it.
- So after repeating the cycle of "let me try to update this" several times and having the update fail on me, I'm still stuck at Slimkat 7 as the only thing that worked on LTE (note the past tense). Worse yet, I tried simply downgrading my modem to match my current bootloader version, but that made things worse than better. I am now stuck at 3G... which just recently went back to LTE. Talk about erratic.
- I also tried going full stock by flashing this: http://forum.xda-developers.com/showthread.php?t=2363882 But it expects 5 arguments for format, and got 3... or something. Failed hard.
So, I'm pretty much at the end of my rope here. I really might just go and grab a new phone at this point. I just really don't want to because this thing still works fine.... I guess I got unlucky and am at a version of the bootloader that is difficult to update from. I can't seem to go anywhere with this thing. Anyone have any ideas? Do I need to use a different recovery?
Thanks...

First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.

jason2678 said:
First and foremost, verify your bootloader. Install the Samsung phone info app, or in a terminal app or adb shell enter:
Code:
getprop ro.bootloader
If you're on any of the older bootloaders (the ones that do not end in MJB, NE4, or NJ1) there are two ways you can go (you probably will be given the age of your modem). If you're on any of the ones that end in MJB, NE4, or NJ1 you've got to be a lot more careful because downgrading them will hard brick your phone (Odin back to stock is not an option anymore).
Option 1: If you're on the older bootloaders, you can go to sammobile.com, grab the 4.1.1 firmware from there and flash it with Odin. Do not do this if your bootloader ends in MJB, NE4, or NJ1 (can't stress that enough). This will reset your phone completely to stock. You should now start getting OTA updates. They will be incremental updates, you'll have to take at least three or four to get up to date on bootloader and modem and they're big downloads. They will come every 24 hours, but you can cheat that by setting your system time forward 1 day to make them a little more rapid fire. This is a nice, safe way to get your firmware current. Once you're up to NJ1 firmware you can use Odin to flash a custom recovery and get back to custom ROMs; I'd recommend TWRP 2.8.6 if you're going to be flashing newer ROMs as CWM and Philz aren't as up to date and sometimes give problems with newer ROMs.
Option 2: I'm pretty sure your version of CWM is a big part of your problem. If you're going to be flashing lollipop you ought to update your recovery to TWRP 2.8.6; easiest way to get it is just use the Flashify app. I'd get that recovery up to date before messing with bootloaders too. Next get your firmware up to date. If your bootloader version is before MJB, then you have to start with MJB. Then update to NE4. Then update to NJ1. It has to be done incrementally, and the bootloader and modem must match on the newer firmwares, or you'll hard brick. This thread has recovery flashable MJB and NE4 bootloaders/modems; the bootloader and modem are packaged together in the same zip so you can't get out of sync. This thread has recovery flashable NJ1 bootloader/modem. This will get your firmware all up to date, and data should start behaving on newer kitkat and lollipop ROMs. This route is a lot more risky than the OTA route described above because of all the manual steps you have to take, but you could get it done quite a bit faster if you're confident in your abilities. Just read those linked threads very, very carefully and make certain you understand.
Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help! I actually did/tried a majority of this an hour or two before you posted that, except the latest firmware update link you supplied. I knew it existed and I had seen that thread before, but I couldn't dig up the link again before I had to go to work. Thing is I kind of wanted to avoid Odin for some reason but I finally gave up and used it. And yeah I already knew my bootloader version. The phone told me when it failed to update the bootloader lol.
Here's what happened thus far:
- I used Odin to flash the sammobile 4.1.1. The flashing worked just fine, but booting into it did not. It hung on the Samsung logo. So, OTA updates were out the window.
- I have no idea why, so I just used Odin to flash TWRP onto it afterwards (from here)
- I tried one of the ROMS. Data still didn't work.
- I used the thread you linked to update to MJB bootloader and whatnot. The update went fine.
- Tried another few ROMs. Data worked, but LTE was still erratic.
- Updated to NE4 and then grabbed the deoxed stock ROM.
- The deoxed stock rom failed to boot (stuck at ATT globe logo). For some reason my phone can't use stock ROMs.
- So again used Odin to put TWRP onto the phone
- Installed various LP ROMS. Again the data was erratic and plus the battery life was horrid.
- Tried getting the ktoonsez kernel. My service was murdered.
- Gave up on LP. Tried Slim 9.0. Erratic data.
- Tried Liquidsmooth 4.4.4 instead.
Currently that's kind of where I'm at. The LTE data works fine (takes a bit to get up and running after reboot though) and thus far everything is okay (though that can quickly change considering I haven't done much of anything), so I don't even know if I want to mess with it anymore. It looks like this specific ROM includes a custom kernel. So I'm guessing it's an incompatibility between the kernel and the firmware version on the other ROMs. It seems like most of the LP roms have horrible battery life (back of my phone feels like a furnace on them), so I'm not even sure if I want to do that last firmware update to use them.
It'd be kind of nice to use the OTA but apparently my ability to go stock in any form or fashion is just totally borked.
Thanks for the post though, that's pretty gold. I'm sure someone in a situation like me where they have a super old firmware will find this thread of some use as it has actual instructions and links to what you need to do to get up and running. Before you posted that, I had to go digging around pretty much everywhere figuring out what and where was going wrong.

Glad you've got it mostly working.
You might have been able to get that stock ROM to boot if you had booted into the stock recovery and run a full wipe. Touchwiz ROMs can be tough to get running after being on AOSP. As a general progression try to format internal storage with TWRP (the wipe where you have to type "yes" to confirm), if that doesn't work try a wipe with Philz, and if that doesn't work nothing, not even Odin, is effective as a wipe in the stock recovery.

Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app

mrkhigh said:
Thanks for typing all this out I believe it will help me put cm12.1 official on a friends phone.
Are these the steps?
1) verify latest software
2) twrp via Odin
Alt 2) root via apk then use rashr or similar to flash twrp
3)wipe
4)In twrp install official d2att from cm website
5) install current gapps
6) profit
I'm not new to this at all but I've never even touched an att gs3 and I know most devices have their quirks and I don't want to brick.
Also does towel root work on this? I don't mind Odin but I can do this on the fly I think if I can attain root.
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yep. You've got it. If you're on the latest and greatest firmware I think the towelroot exploit has been patched, unless geohot has retaken the lead in that arms race.
Easiest way to root on this phone since the bootloaders are unlocked is to just use Odin to flash a custom recovery then use the custom recovery to flash SuperSU. There's just a little trick to it. Store SuperSU.zip somewhere on your phone before flashing the custom recovery. Uncheck everything but f.reset time when you use Odin; don't let it auto reboot. Upon success pull battery. Replace battery and boot straight into recovery with vol up + home + power. If you mess up and boot into unrooted stock ROM with a custom recovery it will get overwritten with a stock recovery and you'll have to Odin custom recovery back onto it and try again.
I would do this to root your stock ROM just to execute this command in a terminal app or adb shell before any more serious flashing:
Code:
su
reboot nvbackup
That fixes a derp and gives you a working efs backup on a few backup partitions built into your phone instead of a blank one. Highly recommended before doing any ROM flashing. This will just look like a pretty normal reboot. You might see a quick flash of tiny blue text if you're watching for it.
Then you're ready to make a nandroid backup (just in case), wipe, and flash away. Take a look at LiquidSmooth if you're looking for a good lollipop ROM.

Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Thanks for the suggestion on the ROM but I think I'll stick to official cm12.1 it's not my phone and that should be a nice readily updatable bland flavor of lollipop.
Sent from my DROID RAZR M using XDA Free mobile app

mrkhigh said:
Nice... So the recovery partition gets rewritten every boot up until a custom ROM is installed and the efs can disappear... This is why you always ask questions.
Click to expand...
Click to collapse
At the Android 4.3 update it was noticed that flashing a custom recovery would be overwritten by the stock recovery on the initial reboot unless following the method Jason described. Another solution was to delete two lib or .so files. On devices still on stock recovery, stock recovery does not overwrite itself.
There is a blank EFS partition on the device intended for a backup. The nvbackup command populates that partition with an image which will rebuild your EFS if it is lost during a modem update or ROM flash. The loss of EFS does happen. I believe wanam, of the xposed module fame, created an EFS backup tool for Samsung devices. I don't believe he updates it any longer because he rolled the functionality into a partition backup tool, the later is in the PlayStore listed under a different creator name, yet it's still him.

So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..

coolwhipp420 said:
So I'm finally going to take the plunge, and update my boot loader/modem.. I never messed with it because all the Roms I used always worked.. I want to try lollipop, but due to old bootloader my phone won't boot with those Roms..
I'm on UCDLK3 bootloader/modem.. I know I have to upgrade to MJB, NE4, then NJ1 in that order in increments..
So my question: can I upgrade from LK3 straight to MJB with out any problems?? Or is there something I need to flash before I can get to MJB?? I think I can go straight to MJB, but better safe then sorry..
I know downgrading after upgrade most likely will brick.. Any information is appreciated... Oh, its an ATT I747..
Click to expand...
Click to collapse
Since you are on LK3 you may want to considr applying the free sim/carrier unlock method before upgrading; that is if you are on stock LK3 and you have not previously carrier unlocked your device.
There was an OTA release for the MG2 stock ROM, I believe that was 4.1.2. You may want to go to that before MJB. Did you make the nvbackup suggested by Jason?

Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..

coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
There is a command to manually trigger the restore routine. I think it's
Code:
reboot nvrestore
but don't hold me to that. I'd never execute that command except if in dire need. The problem with this phone is there is an automatic routine that can be triggered in the event of a bad flash that will overwrite your nvram with the backup, even if the backup is blank. I don't think the backup stores anything modem specific, but I've never been able to confirm that. So I've always done it again after updating modems (only had to once).
Having the phone sim unlocked can be nice if you plan on traveling internationally. Otherwise, potential future carrier hopping or added resale value are the only reasons to do it.

coolwhipp420 said:
Why would I do a carrier unlock, if I'm not switching carriers?? And if I do it, will I be able to use the same carrier?? Just seems like a waisted step for me.. But idk..
Jason's first post, option 2 is how I was planing to update.. And no, I haven't done the nvbackup yet.. How would I apply that backup if things go wrong? Not really sure what a nvbackup is..
Any information is appreciated..
Click to expand...
Click to collapse
If you will never be switching carriers, nor ever sell/give/trade the phone to someone who will switch, then it is an unecessary step to do the carrier unlock.
I see Jason beat me to answering both of your questions.

I already regret trying to add custom ROM.

Hello,
I tried to flash custom ROM, but something somewhere went terribly wrong.
I did read some guides on flashing before attempting this and did make some precutions as well.
Such as creating ROM backup with CWM and copying efs folder with Root browser.
Unfortunately I didn't succeed with the flash. Now the phone can turn on, but there is no network service, and IMEI number is missing.
I tried to go back to my original ROM, but that didn't fix the problem.
I tried to gather as much information as possible, but it seems that information on this device is a bit outdated. For example, I wanted to try to flash back to stock ROM with odin, but most links with stock ROM are down. The one that isn't down only provides .7z file instead of md5,tar file that is required by odin.
The device works, just can't connect to mobile network.
Is there something I could do?

Before flashing anything else, what baseband and bootloader is on the phone? The imei may be missing because the ROM is too new for the phone's current bootloader/modem combination.

Bootloader version is T999UVDLJA
Baseband version is UKNKOWN
I have finally found stock ROM in tar.md5 format, which is compatible with ODIN.

The t999 is the aws version of the s3 according to this: http://www.gsmarena.com/samsung_galaxy_s_iii_t999-4804.php
This forum is for the i747 and i747m (the AT&T and Rogers) version of the s3.
If the t999 is like the i747, do not flash any ROM via Odin that tries to downgrade the bootloader as this may brick the phone.

This makes just even more complicated.
When I go to settings -> About device, under model number I have SGH-I747.
When I double check this with Samsung phone info app, under model number I have SGH-I747.
In the same Samsung phone info app under PDA version I have I747UCDLK3 and under CSC version I have I747ATTDLK3
t999 only appears when I enter Download mode via volume down + home button + power button.

What does the label under the battery say about the model #?

Label under the phone is SGHT999.
Wow, this phone is weird...
I read on the forums that there is chance to restore firmware of the phone with KIES, so I tried that. At first I entered SGH-I747 model number and serial number of the phone and it failed. But after that I entered SGH-T999 model number and serial number of the phone and KIES started to update the phone.
At the moment I have android V4.3
Bootloader T999UVUENC2
Baseband T999UVUENC2
PDA version T999UVUENC2
CSC version T999MBENC2
Phone seems to be unrooted, IMEI number is visible, I can call again, but the phone's factory mode is on.
It seems that I had a SGH-T999 which somehow was tricked int thinking that it is SGH-I747.
At the moment I would just like to have a stock ROM for this phone without all the T-Mobile apps, would that be possible?

Does everything see to work?
The easiest way to root and remove apps would be to flash a custom recovery, install supersu and titanium backup. Then use titanium backup to remove the apps.

Yes, at the moment everything works.
I can call, receive sms, use wi-fi as well as mobile data.
The only problem is that phone has factory mode on Yellow text on black background. And it is heavily loaded with T-Mobile applications.
So I guess this phone is T999 then, right? How could it be that everywhere it had I747?
By custom recovery you mean custom ROM?

You need a custom recovery such as TWRP: http://forum.xda-developers.com/showthread.php?t=1809313
Download the tar version that can be flashed via Odin.
Download supersu and copy it to the phone. Flash recovery, boot directly into recovery without letting the phone boot the ROM, flash supersu, reboot. Install Titanium Backup from the Play store, remove the apps.

Thank you for sticking with me in this thread!
Could you please explain a little bit more what is TWRP? From the link provided I understand that is is a application that helps with custom rom flashing and backing up roms?
Shouldn't I do this at first - http://forum.xda-developers.com/showthread.php?t=1771687

Boot into download mode. Do you see anything about warranty bit 1? If you do, that means you have already tripped the counter.
Root is not required to flash a custom recovery.
If you are only interested in root, follow the other thread. If you want to be able to flash custom ROMs and backup the rom, you need a custom recovery which will definitely trip the counter.
Do you have any warranty left on the phone?

Yes, there is 1 next to warranty bit. What does it mean for me that I have tripped the counter?
At the moment I would just like to get rid of factory mode and remove those unwanted T-mobile APPS. I think I will be done with Flashing for quite some time
I don't have any warranty on the phone, It has been in the family for quite some time.

It would be 0 if the counter wasn't tripped.
To bring it right back to stock, you could flash one of the prerooted ROMs from the other thread. Just make sure you are flashing a rom that has the same bootloader that is currently on your phone. Hopefully, the stock rom will remove the factory mode.

I understand that the counter is only important if you need warranty, yes?
I actually just found a way how to remove the factory so that is one more thing less to worry about
And I rooted the phone with odin using the link few posts back.
Now for the final question, I understand that this rom is something along the lines that I'm looking for? http://forum.xda-developers.com/showthread.php?t=2501303

The ROM looks nice as long as you are running the correct bootloader and modem.
Installing a custom ROM only requires a custom recovery. There is no need to root or remove apps from the existing ROM since you are going to wipe the existing ROM before installing the new ROM.

I read through the thread and I understand that I have to flash T999UVUEMJC modem before flashing the ROM.
I'm not sure where the bootlaoder of this rom is mentioned. Only place where boot loader of my device T999UVUENC2 is mentioned is in change log "-Rebased to T999UVUENC2".

The official T-mobile firmware is here: http://www.sammobile.com/firmwares/database/SGH-T999/
Notice the last few letters in the firmware PDA?

Based on your post on the first page (post #7) you are on the NC2 bootloader and modem, which are compatible with the rom you are wanting to flash. (See the second line under the Disclaimer banner.) NC2 is the most current firmware for the T999 listed on the page Audit linked to.
(one explanation for how your device was reporting i747)
Is it possible that someone else flashed the i747 rom to this phone? Either someone doing you a favor or a previous owner? I747 roms will work on the T999, I frequently see people commenting on doing so successfully. You just need to have comparable bootloaders and modems. That and if the rom dev didn't accommodate the device in the updater-script the user must edit the script himself. In the unofficial cm12.1 thread for the i747 people were doing this often.

So the bootloader version is always the same as the modem version?
I understand that in my case I don't need to flash T999UVUEMJC modem, since the one I have at the moment is newer?
That is definitely possible, although, how it came to be I will never know, since I personally didn't buy the phone. But this would explain a lot.
Could you please take a look at this thread, I created steps I plan to do in order to flash the above mentioned ROM. It would really put my heart at ease http://forum.xda-developers.com/galaxy-s3-t-mobile/help/one-rom-flashes-please-double-check-t3111443

Re-Partitioning Developer Edition

Can someone please explain to me how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!

doubleplay648 said:
Can someone please explain to me
how i re-partition my developer edition. I just received my phone back from samsung and updated from BOG5 to N910VVRU2BPA1_StockRestore_Incremented.tar.md5
Now i can cannot downgrade back to BOG5 with a |tz|Fused 2 > Binary 1 error. I also cannot root my phone with TWRP using odin. Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1). On my phone it says secure check fail : recovery
My reactivation lock is off and USB debugging is enabled
Here is what my recovery mode says:
ODIN MODE: HIGH SPEED
PRODUCT NAME: SM-N910V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS OFFICIAL
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD: ENABLE
Any ideas where i go from here? I have only flashed stock_restores so there is no chance that i locked my bootloader.
I reference page 3 of this for reference: http://forum.xda-developers.com/note...t3313224/page3
I really don't want to lock my developer edition so please provide me with as detailed step-by-step instruction as possible.
***Re-partitioning a developer edition seems extremely risky so i would like to know exactly what I'm doing considering i cannot root yet to backup my aboot partition***
-Thank you!
Click to expand...
Click to collapse
I replied to you on PM, but this may be helpful for others.
Repartitioning has nothing to do with downgrade-ability. The Safe Upgrade won't work for you either, since it includes older TrustZone. N910VVRU2BPA1_StockRestore_Incremented.tar.md5 didn't change any of the critical partitions. You'll need a similar tar for OG5 to be able to downgrade, which isn't available unfortunately.
Click to expand...
Click to collapse
However, you could flash OG5 ROM via TWRP, if you wish.

Cannot install TWRP
hsbadr said:
I replied to you on PM, but this may be helpful for others.
However, you could flash OG5 ROM via TWRP, if you wish.
Click to expand...
Click to collapse
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?

doubleplay648 said:
I'd love to but I cannot figure out why I cannot install twrp. It always give me a fail on odin (see previous post). Any suggestions?
Click to expand...
Click to collapse
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.

hsbadr said:
If you've the Developer Mode, you should be able to flash TWRP tar from here via Odin. Otherwise, you should have flashed a retail bootloader.
Click to expand...
Click to collapse
So i have the developer edition. I sent it into samsung for repair and i mentioned several times about the bootloader being unlocked. I tried flashing the twrp tar you gave me and it gave me a odin fail and my phone says SECURE CHECK FAIL: recovery
The only thing i did when i got my phone back was upgrade the 5.0.1 to your 5.1.1 incremented stockrestore.
Did i do this right?
1. put phone into download mode (power + volume down+ home)
2. plug into pc and open odin.
3. flash the tar via ap, without checking re-partition
So any idea why this isn't working? Samsung had to replaced the motherboard in my phone. Is it possible that when they sent back my phone they updated the SW to a locked bootloader?

Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!

doubleplay648 said:
Okay so hear me out. Since I obtain the |tz|Fused 2 > Binary 1 error when attempting to flash back to STOCK BOG5 or simply STOCK 2BPA1. Couldn't I theoretically flash back from the incremented 5.1.1 stockrestore to stockrestore of either BOG5 or 2BPA1 using the stockrestore.tar and the TRLTE_USA_VZW.pit file to repartition the developer edition. shouldn't this work since i technically have the BOG5 incremented bootloader? Then I wouldn't run into the secure check fail : recovery error when flashing TWRP via odin and I would be able to achieve root again. However, if I re-partition the developer edition what would happen to my bootloader? Since i'm using a stockrestore.tar it shouldn't affect the bootloader correct? I would like some input from the developers on here before proceeding. Thanks!
Click to expand...
Click to collapse
Your phone is retail. If you want DevEd you will need to talk to one of the few folks at Samsung that know what a Deved is. Convince them that they retailed your phone when they replaced the main board. They should fix this. The only number you should call is the 800 number on your DevEd receipt. If the CSR doesn't know what your talking about, ask for a supervisor, escalate until they know what you have. They need to be clear what you have, or it will return retail again. The good news is they will flash your fuse 2 retail to DevEd.
The number is 800-757-0280
Click on image,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From Odin Download screen it should say "Mode: Developer"

From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
---------- Post added at 02:22 PM ---------- Previous post was at 02:02 PM ----------
anticloud said:
From Experience - no real convincing needed. Samsung will be happy to reflash the phone for you. They will also perform an end-to-end diagnostic of the phone, and like in my case, where the screen had burn in, replace the screen for free (a $271.00 value).
Samsung service - IMO, is great. It's the rest of Samsung I concern myself with. While this statement semi-contradicts what I stated above, it's not really... The actual tech / service end is second to none all about customer service... It's just getting to them without hassle - when I say this, I mean, sometimes the left hand does not know what the right hand is doing - and it'd appear that the (1st) person you are on the phone with won't have any clue what a developer version is etc... pay that no mind, and be persistent. The second hurdle you may encounter, when you mention developer version, they may want to take you down the road of factory reset and then tap the version number to open up developer options - and that we know is NOT what is meant by developer version.
Eventually, once you get to the actual tech department - they will see by your serial number that you have an actual developer version. and they will create an RMA version.
What you can expect -
You will be restored to a completely 100% working phone - but note, you will most likely be on the latest edition firmware Samsung has, as a developer edition, incremented to the latest version - @radionerd will tell you, I had my phone returned with 5.0.1 installed on it, the SWREV contained T2 / A2 partitions (totally incremented) and they actual BOG5 firmware revision was different than any leaked or OTA image - this really did not hurt any, and I was still able to flash 5.0.1 Jasmine ROMS etc... root, the whole 9 yards...
And they will fix items on the phone, if broken, that should always work - like the screen. Samsung claims burn in should not happen EVER, yet it does
I, personally, am having issues with a 5.1.1. upgrade (from 5.0.1.) using the safe stock LPA1 restore - and hsbadr knows about this - and has posted suggested fixes - but, I'll tell you, it ain't purdy. I had to roll back to a 5.0.1 Jasmine ROM after receiving a Binary Fused set of messages even with the safe upgrade... I managed to recover the phone back to 5.0.1 BOG5 / Jasmine 3.1 etc...
Click to expand...
Click to collapse
and I can't help but mention - if you happened to use one of the safe upgrades to move forward, there is rollback.

Booted up M919VWXUGOL1 (Lollipop for M919V) on TMO M919

Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hi there, I'm interested in your repackaged M919V Firmware. Can you upload it? Thanks ill be waiting. Cheers

MysticBlueDragon said:
Hi there, I'm interested in your repackaged M919V Firmware. Can you upload it? Thanks ill be waiting. Cheers
Click to expand...
Click to collapse
https://androidfilehost.com/?a=show&w=files&flid=239650
I've also tried repackaging the latest i9505G (S4 GPe) firmware and flashing and the experience is also good, though I haven't extensively tested either. They are both in the folder.

it's the wifi calling that's the main problem running a lollipop ROM on SGH-M919

found a solution wifi

kalan1988 said:
found a solution wifi
Click to expand...
Click to collapse
Just install this kernel
https://androidfilehost.com/?w=file...2674a1a5ca61e20aa2c0b1cf1f6c99f1a46298b244ca6
heres is the xda link:
https://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729

AndyYan said:
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
Click to expand...
Click to collapse
Can you flash this thru recovery mode?

I found that the LP kernel needed to get WiFi breaks Widevine L1 (gets set to L3), which would partially defeat the purpose of using a Touchwiz stock rom anyway. I am trying a few other kernels and will see if one works. GPE edition 5.1 flashes fine including WiFi but Widevine L1 does not actually work despite showing up in DRMINFO.

AndyYan said:
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
Click to expand...
Click to collapse
Does this mean you're going to Dev for the s4? We would love to have you!

I installed your repackaged tar successfully and also flashed the kernel you suggested. Wifi worked after flashing the kernel but if I reset the phone, the saved wifi info is lost so I have to re-enter wifi info all over again. Any advice on this? Should I be looking for a different kernel or any advice you guys can give? Greatly appreciated.

AndyYan said:
https://androidfilehost.com/?a=show&w=files&flid=239650
I've also tried repackaging the latest i9505G (S4 GPe) firmware and flashing and the experience is also good, though I haven't extensively tested either. They are both in the folder.
Click to expand...
Click to collapse
Hey man, can't thank you enough for this. In the process of updating the device (GT-I9505G), I managed to screw up somewhere and now the cell phone data does not work. This is the screenshot of my firmware(s). Everything else, like calling, wifi etc works. Before I realized I tried to update install ROM, as it has happened in the past, but still things are the way they are, no cell phone data. APN is correct. I made that sure.
The screenshots of the firmware are below. CSC and PDA version are missing.
Screenshots taken using https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en_US
I was wondering if I flash your I9505GUEUDPF1_Boot+Rec+Sys.tar.md5 to this device, will it address the issue and put back PDA and CSC version?
If yes, how do I flash it in Odin, as what do I choose or extract the file and flash everything separately?
Thanks a million again. You saved my rear end a big time.
Edit: I have realized you can not flash the file as is. So I have extracted the image in *.ext4 format. I need guidance which folders to extract and how to proceed thereon. Thank you very much.

fuzzychicken said:
I was wondering if I flash your I9505GUEUDPF1_Boot+Rec+Sys.tar.md5 to this device, will it address the issue and put back PDA and CSC version?
Click to expand...
Click to collapse
I don't get it - what's stopping you from flashing the *full* firmware available around the web? That's the surefire way to fully recover.

AndyYan said:
I don't get it - what's stopping you from flashing the *full* firmware available around the web? That's the surefire way to fully recover.
Click to expand...
Click to collapse
There is another thread where all ROMs are listed. I have tried flashing those stock ROMs but I have not been successful.
So I went back to 5.0.1 stock ROM and let the phone update by itself, still I have not been successful. I am super confused why repeated updates could not fix this problem.
I have EFS backups from 5.0.1 stock (before I started flashing business). Do you think I can use that? I am not too sure of CSC and PDA are in the efs partition, hence the question.
Thanks again.

fuzzychicken said:
There is another thread where all ROMs are listed. I have tried flashing those stock ROMs but I have not been successful.
So I went back to 5.0.1 stock ROM and let the phone update by itself, still I have not been successful. I am super confused why repeated updates could not fix this problem.
I have EFS backups from 5.0.1 stock (before I started flashing business). Do you think I can use that? I am not too sure of CSC and PDA are in the efs partition, hence the question.
Thanks again.
Click to expand...
Click to collapse
For what I know you *have* to use the full firmware for those partitions...

AndyYan said:
For what I know you *have* to use the full firmware for those partitions...
Click to expand...
Click to collapse
Yes, I totally understand that. Since I9505G firmware is hard to come by and att Galaxy S4 is similar in hardware as that of S4 Play Edition, Is it worth giving a shot to that. I am on att MVNO so, in theory, it should work.
---------- Post added at 11:49 AM ---------- Previous post was at 11:20 AM ----------
AndyYan said:
For what I know you *have* to use the full firmware for those partitions...
Click to expand...
Click to collapse
I found these files. Do they constitute *full* firmware with approx correct file sizes?
These are not the newest files so I will not be able to update the bootloader but assuming that I update after flashing these, it *should*fix it.
Thanks again for help.

fuzzychicken said:
I found these files. Do they constitute *full* firmware with approx correct file sizes?
These are not the newest files so I will not be able to update the bootloader but assuming that I update after flashing these, it *should*fix it.
Thanks again for help.
Click to expand...
Click to collapse
Looks "full" to me, though you don't need that PIT file unless the device is actually bricked.

AndyYan said:
Looks "full" to me, though you don't need that PIT file unless the device is actually bricked.
Click to expand...
Click to collapse
Thanks mate.
My Bootloader and baseband is 2 versions updated to this one. So I don't want to flash those. In that case, there is a mismatch. What troubles should I expect?
At the moment, the phone is working just fine except the cellular data. Worth the risk of going ahead?

ninjamuffinBV said:
Just install this kernel
https://androidfilehost.com/?w=file...2674a1a5ca61e20aa2c0b1cf1f6c99f1a46298b244ca6
heres is the xda link:
https://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729
Click to expand...
Click to collapse
how would I install this kernel?

I just started having problems with wifi in the stock SGH-M919 and custom roms. (Not sure what I did, radio problem, I think) This rom installed fine and the kernel fixed the wifi. Its connected and downloading updates now. The only thing I see so far (I just installed it), is that the camera crashes. I flashed twrp right off the bat. I will reinstall it all to check when I get a chance. Thanks
Update:
Odin 3.12,
flash the full (sammobile) M919UVUFOK3, wipe data, and the wifi doesnt work but camera does
flash the M919VWXUGOL1_Boot+Rec+Sys.tar.md5, wipe data, and wifi doesnt work but camera does
flash twrp-3.2.3-0-jfltexx.img.tar, still no wifi
TWRP,
install Lolli-Test-TW-07.02.2015.zip, and now wifi works but camera crashes
M919UVUFOK3 and Lolli-Test-TW-07.02.2015.zip dont work (just thought i would check)
I dont have an active sim card for this phone so I cant really test it completely. That kernel does fix wifi though.

Im not sure what is going on. I just did Odin the stock firmware (samsung-firmware) three times as well. I can get wifi to turn on like normal now but it will not connect to 2.4Ghz wifi. It seems like its in a loop. It works fine with 5Ghz though. I tried 3 different custom ROMs too. I have 3 other Samsung phones (and 3 printers) that work fine on my 2.4Ghz. I see that both stock firmwares flash modem, aboot, boot, recovery, system, sbl1, sbl2, sbl3, cache, hidden, rpm, tz and hlos. I dont know what Im missing here.
It works fine with 5Ghz so it has to be something in my software, right? I am really bummed that i didnt dd this phone before I started messing with this one. I wont ever skip that step again, lol.