Develop Bugs

[GUIDE] Unlock your MK2 Knox Galaxy S4

After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck
Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).
Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.
Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.
If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.
The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.
If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.
Better guide by kali323:
kali323 said:
1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"
http://www.hunterspad.com/Domains/S...ir=Xda/Galaxy+S4/T-Mobile+S4/Return+To+stock/
2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.
3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.
4. Now youre in MDB 4.2.2 with MK2 modem.
5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
https://mega.co.nz/#!S9AjUAYA!GOOIp2B4z5dIZy2RFxwQBsMz_v7nRJiOypoAjkuAwtc
6. Now you have MDB Rom with MDL modem
7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer
http://forum.xda-developers.com/showthread.php?t=2470551
9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.
10. Odin 4.3 or 4.4 and youre done
Click to expand...
Click to collapse
Some additional info:
blu422 said:
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
Click to expand...
Click to collapse

hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!

ionutul said:
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Click to expand...
Click to collapse
I'm not too sure actually, I didn't run into that error, and I don't have other S4s I can try it out on.
There were several things I did do before trying to flash back though, that may have had an effect. The first is rooting through motochopper's method. The second was installing and running regionlock away. Try rooting first and then flashing. Otherwise, I might have to chalk it up as something unique with my phone I'm not aware of.

Tsumi said:
After several hours of trial and error, I found a way that worked for me. It will trip the Knox counter though. Also, what worked for me may not work for everyone else. If you brick your device that's not my fault in any way, so good luck
Using this guide, flash back to the stock TAR (not the UVUAMDL TAR). This restores 4.2.2, which allows access to the menu. However, this alone is not enough, as it won't give you access to the perso functions. Attempting to flash the UVUAMDL TAR will result in an error (at least, it did for me).
Second, extract the modem.bin from the UVUAMDL file, and flashed it to the phone using Odin. It's similar to the guide above, but instead of using PDA, you use phone. This gives you access to the perso functions, as it forces the baseband back to UVUAMDL from UVUEMK2. It may be possible to flash the UVUAMDL.tar modem files found in other threads, I haven't tried this out myself though.
Now, at this point you can follow the instructions in this thread, as every option should now be available. If they're not, make sure your Android version is 4.2.2 and that the baseband is UVUAMDL.
If it works at this point, great, go on to the next step (you may have noticed by now that your sound is not working). If not, use RegionLock Away to fully unlock the phone. At this point, your phone should be fully unlocked and you can see it connected to the network. However, dialing/calling lags significantly, and there is no sound.
The next step is to use Odin to fully restore UVUEMK2, which would restore full functionality. You can download the file from here, and flash using the same steps above. This will restore full sound and phone functionality, while your device remains unlocked. If it gets stuck during the boot animation, you simply need to do a factory wipe from recovery (not sure if this works, haven't tested it myself), or just install your recovery of choice from Odin and install whatever ROM you want to use (what I did, which still required a full factory reset from recovery). Skipping restoring UVUEMK2 and installing your ROM of choice does not work, however. You will still have no sound and the phone function will lag considerably.
If everything goes well, you should have a fully unlocked T-mobile Galaxy S4.
Click to expand...
Click to collapse
HELP...!
Ok, I've been reading many many articles for the past few days and finally have mustered enough energy to attempt the unlock my T-Mobile SGH-M919 running MK2 firmware. Since I was unable to get into the service menu and input keys using the many directions on this site.... I attempt to flash to old older firmware, following this guide.
I followed each direction 1 step at and time and followed it to the "T". Anyway, long story short... I tried and it soft bricked my phone. I get the warning screen that the firmware was unsuccessful and that I need to run recovery using Samsung Kies. I download the software and attempt recovery. It got to roughly 90% and then it failed too. I reverted back to Odin and reflash using MK2. It too got to about 90% and fails. What is going on?
Any more tips to get this thing working again?? Help.

Got to only 93% via Kies... two times!

Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
If your rooted you can try region Loa away by chain fire see if it works.
Sent from my SGH-M919 using xda app-developers app

egren58 said:
Um I'm almost sure once you are on mk2 your not able to go back to mdl. Do to the boot loader...
Sent from my SGH-M919 using xda app-developers app
---------- Post added at 08:52 PM ---------- Previous post was at 08:51 PM ----------
If your rooted you can try region Loa away by chain fire see if it works.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!

dyangster said:
wwwhheeew.... finally got it to unbrick. Took 4 hours to get this thing operational again. I thought the guide specifically says it can downgrade from MK2 to MDL? I already ran the Regionlock app and it appears to be done right, but it's still not sim unlocked.!
Click to expand...
Click to collapse
same problem, RLA does not work on MK2, flashing MDL modem and going through the motions also does NOT sim unlock...cant seem to get this thing working.
funny thing is it wont even register on the network with a GoSmart sim, GoSmart being a TMO MVNO.
i hate sammy...

I flashed to the stock firmware first, which I believe is the MDB firmware. It doesn't work attempting to go to MDL. Going to MDB gets you 4.2.2, but you would still be locked because it keeps the MK2 modem.
The second step was to extract the MDL modem.bin from the TAR, and then flash that on Odin via the phone method. That was how I was able to downgrade the modem from MK2 to MDL, but that screws up sound, but allows you access to the unlock functions.

Odin MDB and factrory reset in recovery. I was stuck at "Kernel is not seandroid enforcing set warranty bit: Kernel" at the boot up screen. I thought it didnt work and wasnt going to boot up and was looking MK2 tar and then out of nowhere after 5 mins I hear the tmobile boot up sound and this **** actually boot it. Im in MDB 4.2.2 with mk2 baseband. Just need to downgrade baseband and Ill let you know if it works guys. Ill post all files as well that I use
---------- Post added at 10:34 PM ---------- Previous post was at 10:07 PM ----------
I have successfully unlocked and I was at 4.3. Huge props to Tsumi. Ill post an updated guide of Tsumi unlocked method of all the files I used
---------- Post added at 10:58 PM ---------- Previous post was at 10:34 PM ----------
How to Unlocked M919 on MK2 4.3. This method has no been tested on the new MB4 4.4.2 update
Huge Props to Tsumi. Is his method and thank/donate to him. i use his guide but it wasnt clear enough so I went searching to internet for links for all the correct files.
Im not responsible for any bricks but if you follow carefully then you shouldn't
This method will trip KNOX
1. Download MDB Tar. Extract from 7zip file and then rename the file (remove the .md5) so the filename should be "SGH-M919-UVUAMDB-k0nane.tar"
http://www.hunterspad.com/Domains/S...ir=Xda/Galaxy+S4/T-Mobile+S4/Return+To+stock/
2. Odin the MDB Tar in the PDA slot and once it finish go to recovery and factory reset.
3. It will take forever to reboot and it will be stuck at the boot up screen for awhile with this error "Kernel is not seandroid enforcing set warranty bit: Kernel". In about to 5-10 mins it will boot up.
4. Now youre in MDB 4.2.2 with MK2 modem.
5. Odin the .bin file below. Use the PHONE slot in odin and not PDA. Again it will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
https://mega.co.nz/#!S9AjUAYA!GOOIp2B4z5dIZy2RFxwQBsMz_v7nRJiOypoAjkuAwtc
6. Now you have MDB Rom with MDL modem
7.Odin CF AutoRoot with the link below in the PDA Slot. It will take 5-10 mins to boot up with the error "Kernel is not seandroid enforcing set warranty bit: Kernel"
http://download.chainfire.eu/328/CF-Root/CF-Auto-Root/CF-Auto-Root-jfltetmo-jfltetmo-sghm919.zip
8.Download RegionLock Away 1.3 App either in the thread below or buy it at the google play store to support the developer
http://forum.xda-developers.com/showthread.php?t=2470551
9. Run RegionLock Away and click reboot now. It will take another 5-10 mins to boot up and if you dont ask you for an unlock code with a non tmobile or non tmobile mnvo sim then youre are unlocked.
10. Odin 4.3 or 4.4 and youre done

ionutul said:
hello,
i tried to flash the stock tar as you said, but i get an error.
it says:
write protection: enable
secure magiccode check fail : boot
what can i do in this case?
thank you!
Click to expand...
Click to collapse
I'm curious, how come you didn't trip the Knox counter?

Help
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.

JerkLife said:
Hey I Have A Tmobile Galaxy s4 and it says my sim isn't registered on the network i was just wondering if there was anyway to get this running, i tried the above method and it completed but i still can't use a tmobile sim on my phone.
Click to expand...
Click to collapse
If you have a T-mobile S4 and a T-mobile sim, and it says sim is not valid, then you need to contact T-mobile about your sim card. Either that, or your phone has a bad IMEI (not sure what error message would pop up if you have a bad IMEI). Either way, it's not an unlocking problem. Either your sim or your phone is invalid on the T-mobile network.

This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!

blu422 said:
This method works the only problem I encountered is while flashing the modem i couldn't make it flash, i would flash it but then in settings my baseband would stay mk2 so the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
edit: just kidding this method did not work for me, the unlock prompt no longer shows up, but an at&t sim card still will not work, although it does tell me i have five voicemails that i cannot listen to. no texts no calls no data, where it should say at&t in the notification panel it says no service... :/ any ideas? I havent yet updated back to 4.3/4.4 yet could that be the problem?
when I try to call it just says "not registered on network"
turns out that it is just because i havent updated back yet, not even a t-mobile sim works. turns out I have a blacklisted imei! but i think I am unlocked hopefully this (at least the first part) answers a few questions aroused during this process, may be the op could get updated with a couple key peices in this post. also huge kudos for this!
Click to expand...
Click to collapse
As I have only done this on one phone, I am not sure what issues you were encountering. Also, like I said in my post, YMMV, different phones may behave differently.
What do you want to see updated?

wrong
the 2nd link is not a link to the files. it's a link to internet browsers..

BoloVon said:
the 2nd link is not a link to the files. it's a link to internet browsers..
Click to expand...
Click to collapse
All links are working for me...

Tsumi said:
As I have only done this on one phone, I am not sure what issues you were encountering. Also, like I said in my post, YMMV, different phones may behave differently.
What do you want to see updated?
Click to expand...
Click to collapse
That message pops up when its blacklisted so it won't work regardless if you unlock it
Sent from my SGH-M919 using Tapatalk

No wifi
i was able to flash stock tar to my s4. now i cannot get wifi to work.. i tried turning it on but the signal comes back off.
help please..

Tsumi said:
What do you want to see updated?
Click to expand...
Click to collapse
That \/ maybe just add a link to my post saying if you have problems with the .bin part then see here or not its whatever you see fit
blu422 said:
the way to fix this is to flash in odin with auto reboot off. then when its done flashing unplug the phone then pull the battery and boot straight into download mode and flash the modem.bin once again same drill, auto reboot off then pull the battery then reboot and it should work.
Click to expand...
Click to collapse
---------- Post added at 10:17 PM ---------- Previous post was at 09:52 PM ----------
BoloVon said:
i was able to flash stock tar to my s4. now i cannot get wifi to work.. i tried turning it on but the signal comes back off.
help please..
Click to expand...
Click to collapse
Which stock are you referring to? The 4.4.2 one?

Am I in Trouble - MM update

I tried to sideload the update a few days ago and set my phone into a boot loop.i was able to use Odin and flash it back to 5.1.1 but now I am unable to install the security update that is available. I've tried to install it 3-4 times so far but after my phone restarts and says it is installing it quits once it gets to 25% and boots as normal. Then it comes up with a message that the install was interrupted. So I don't know what's going on with this update as I'm on a good wifi connection.
I tried again on a different network and when it got to installing 25% it gave me an install failed error once again.
Am I going to have the same issue when AT&T pushes out MM?

Mickeylittle said:
I tried to sideload the update a few days ago and set my phone into a boot loop.i was able to use Odin and flash it back to 5.1.1 but now I am unable to install the security update that is available. I've tried to install it 3-4 times so far but after my phone restarts and says it is installing it quits once it gets to 25% and boots as normal. Then it comes up with a message that the install was interrupted. So I don't know what's going on with this update as I'm on a good wifi connection.BL
I tried again on a different network and when it got to installing 25% it gave me an install failed error once again.
Am I going to have the same issue when AT&T pushes out MM?
Click to expand...
Click to collapse
If I recall correctly from the Android Central thread, you had to odin reflash after an unsuccessful adb sideload attempt, like myself. The instructions in the firmware thread were to use only the AP file in odin. That's not correct, you have to use the AP,BL,CP, and CSC files to completely restore the official ATT firmware.
The same thing happened to me. The OTA failed at 25% many times. After reflashing using all the correct files,
I successfully received the OTA. I also had discrepancies in my settings which were resolved by this.
I'm not sure if that's what you did also, but if so reflashing as indicated above should have you back on track. Hope that helps!

Thanks, I'll try that because I only used the AP file in Odin.

I can't find a firmware any longer.
Never mind I got it.

Mickeylittle said:
I can't find a firmware any longer.
Click to expand...
Click to collapse
I think I don't have enough posts to put a link here, but look at the thread on Android Central where you posted about
reflashing. The post from Golfdriver 97 has the link to the firmware thread on here. Just download and extract the four files and then load in Odin.
---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------
dakini03 said:
I think I don't have enough posts to put a link here, but look at the thread on Android Central where you posted about
reflashing. The post from Golfdriver 97 has the link to the firmware thread on here. Just download and extract the four files and then load in Odin.
Click to expand...
Click to collapse
I'll try anyway to post the link. http://forum.xda-developers.com/att-galaxy-note5/general/note-5-marshmallow-odin-package-t3331843 that's the correct firmware that you used. Skip the word "marshmallow" in the title , it's lollipop.

Thanks that's exactly where I found it and you were exactly correct. I pointed all 4 of the blocks to those files and it worked like a charm. The patch update from AT&T just finished downloading so I feel good about my phone being back in working order and ready for whenever MM if finally released.
Thanks Again!

Mickeylittle said:
Thanks that's exactly where I found it and you were exactly correct. I pointed all 4 of the blocks to those files and it worked like a charm. The patch update from AT&T just finished downloading so I feel good about my phone being back in working order and ready for whenever MM if finally released.
Thanks Again!
Click to expand...
Click to collapse
Very happy to hear that it worked for you!

Mickeylittle said:
Thanks that's exactly where I found it and you were exactly correct. I pointed all 4 of the blocks to those files and it worked like a charm. The patch update from AT&T just finished downloading so I feel good about my phone being back in working order and ready for whenever MM if finally released.
Thanks Again!
Click to expand...
Click to collapse
Have fun waiting on that release lmao...
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

e1ement08 said:
Have fun waiting on that release lmao...
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
Oh yeah I'm holding my breath on this.

Mickeylittle said:
Oh yeah I'm holding my breath on this.
Click to expand...
Click to collapse
Well, i decided since my firmware was no longer seen as modified, giving a system 7 error, I would try to sideload again.
I sideloaded the PE6 firmware from linux, and this time it worked like a charm! Marshmallow at last.

dakini03 said:
Well, i decided since my firmware was no longer seen as modified, giving a system 7 error, I would try to sideload again.
I sideloaded the PE6 firmware from linux, and this time it worked like a charm! Marshmallow at last.
Click to expand...
Click to collapse
I'm not skilled at Linux whatsoever so I'll just try to wait AT&T out.

Having trouble with the service.

My problem started some months ago, when a friend tried to root my phone, he told me that he rooted it but every app that checks for root told me that it wasn't rooted and i couldn't use apps that needed root also, the downside to all this is that i couldn't use apps that do not allow root, like the banking app, or Pokemon Go, but i used the phone like that for some months until last week when i decided to try and fix it. I thought that if i flash a stock firmware everything should be fine and the phone should be as new. On the phone, it says that the model is SM-N910F(behind the battery), in the settings it also said SM-N910F, so i tried flashing a rom for this model at first and it kept failing with me not knowing why. After trying different thing and googleing some time, i finally noticed that in "Fast Download", it says that the phone's model is SM-N910P, so i started searching about this, i didn;t understand why there were 2 different models on my phone, then i found out about searching my IMEI on imei.info, so i tried it and here it was SM-N910C, i had no idea what all this meant, but at this time i already got stuck into bootloop. Eventually, i found this thread: https://forum.xda-developers.com/note-4/help/help-sm-n910f-sm-n910p-bootloader-t3299285 and did what cam_bob22 said, it worked, i finally flashed the firmware on my phone and it worked, i could use the bank app, pokemon go, everything was fine except the fact that i couldn't select or change my mobile operator, when going to mobile networks, the mobile operators options was greyed out and couldn't be pressed(i want to mention that i did have service and that data worked but the internet would work only in roaming and i couldn't get 4G). So i tried updating the software from 5.1.1 to 6.0.1 like it was said in the instructions and hopping that this update would fix the issue, but unfortunately for me after the update i somehow lost service completely, the signal sign was in the shape of a triangle with no bars, and the mobile operators setting was exactly as before.
So far i tried going back to 5.1.1 but besides the Hands Free activation that i can't make to go away, i still can't use the mobile operators setting and my data only works with roaming activated and doesn't get 4g. One thing that i forgot to mention is that the IMEI with the 5.1.1 firmware was of a samasung Galaxy S5 not a note 4, i checked it on imei.info.
I was wondering if there is any way for me to go back to the OS i had before my friend tried to root my phone, when it said in the settings that it was SM-N910F and everything worked as it should have.
Thank you for reading and i really hope someone can help me.

@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.

aaron74 said:
@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.
Click to expand...
Click to collapse
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.

robert11arad said:
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.
Click to expand...
Click to collapse
Oh ok. So do you have service?

aaron74 said:
Oh ok. So do you have service?
Click to expand...
Click to collapse
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)

robert11arad said:
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)
Click to expand...
Click to collapse
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?

aaron74 said:
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?
Click to expand...
Click to collapse
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Ok. About the best advice i can give is, because your on pure Sprint Rom, something is messing up with csc or something.
All i can suggest, is maybe try updating to QC1 with Odin and then try flashing my gsm Rom. Which is essentially just a tmobile rom.
And if that don't give you the function you you need. Then maybe try an international Rom.
It's hard to say what the last person did to the phone.

robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?

aaron74 said:
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?
Click to expand...
Click to collapse
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.

robert11arad said:
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.
Click to expand...
Click to collapse
Well, first, let me state,about bricking device. I have to state that it's not impossible to brick. But after hundreds of flashes never had problem. These devices are hard to brick. What hard bricks a device is messing with boot loader and partitions that shouldn't be messed with, like trying to unlock lte bands. But just flashing roms is fine unless you flash a Rom not for your phone and it over writes wrong partition.
All snap Dragon note 4s have the same layout so all you need is correct kernel, csc, and some ril lib files to get data working.
Now, mine main worry is that the phone is still unlocked,because I don't know what possible changes were made to it.
But with all that being said,I'll move on. With another post.
---------- Post added at 05:52 PM ---------- Previous post was at 05:13 PM ----------
@robert11arad
Before we go too deep into this and upgrade and stuff. I'd like to just test a custom Rom on your phone and see what works.
So what firmware are you on right now?
5.01, 5.1.1, or 6.0.1?
I'm gonna take a guess and move on. You last stated you were on OG5 which it's 5.1.1. So if that's true, let's try the following.
First I'm gonna assume you already used Odin to flash that firmware. So now we need to flash Twrp. So download this on pc https://eu.dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar
1 . Put phone in download mode. Open Odin and plug in phone.
2. In Odin options make sure everything is unticked except Reset Flash Counter.
3. Now click on AP and select the Twrp file.
4. Flash it. Let it flash until it states it's completed. Once done. Unplug phone. Pull out battery. Put back in and boot to recovery by holding power+home+vol.up
5. Now you should have Twrp. Just reboot phone so we can continue to next post.

PM sent

@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.

aaron74 said:
@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.
Click to expand...
Click to collapse
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...

robert11arad said:
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...
Click to expand...
Click to collapse
Ok. I must have forgot something in csc. Sorry. I'll get back with you.

N910P - Please Help - Tried to root and failed No Bootloader found?

I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.

JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!

Once you get phone back on stock. I'll show how to root!

Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.

SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse

Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!

I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.

JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.

Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.

meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light

Got Night mode on camera today!

I just received OTA on my 975U ASF6, includes night mode in the stock camera app!!!! New Charging animation. Only had it for 5 minutes. Anybody else get it? If so post what changes you've noticed it was 522.5 Mb

iteam said:
I just received OTA on my 975U ASF6, includes night mode in the stock camera app!!!! New Charging animation. Only had it for 5 minutes. Anybody else get it? If so post what changes you've noticed it was 522.5 Mb
Click to expand...
Click to collapse
What carrier do you have? Nothing showing up anywhere for Sprint yet.

There was an article about it. ATT is the only US carrier to get the night mode feature (ASF6)
The rest of us will have to wait.

innocentone1 said:
There was an article about it. ATT is the only US carrier to get the night mode feature (ASF6)
The rest of us will have to wait.
Click to expand...
Click to collapse
Well that sucks ass....

I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.

Atomicmuffin said:
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Click to expand...
Click to collapse
Usually I'd be in the same boat as you, but since I'm on Sprint it wouldn't even let me sideload the firmware science update

mistermidas said:
What carrier do you have? Nothing showing up anywhere for Sprint yet.
Click to expand...
Click to collapse
AT&T
I saw it on firmware science and set my clock to July 4th as it wouldn't update at first. Said it was up to date. Set my date to July 4th and it updated! Camera is sweet! Fingerprint works way better for me and battery is better as well. Phone feels "smoother" all around as well. After a cache wipe and a reboot

mistermidas said:
Usually I'd be in the same boat as you, but since I'm on Sprint it wouldn't even let me sideload the firmware science update
Click to expand...
Click to collapse
I've been recovering from Samsung/Odin modding addiction for about 3-4 years now. My first relapse and this happens
I'll give it a few hours, and if an Odin file for ASF6 doesn't show up somewhere, I'll just suck it up and Factory reset.

On a side note does anyone see their signatures or others???? I have had one for ages, it's in my control panel but not showing and I don't see anybody elses....

iteam said:
On a side note does anyone see their signatures or others???? I have had one for ages, it's in my control panel but not showing and I don't see anybody elses....
Click to expand...
Click to collapse
Seems fine to me. Your sig is:
S10+ Ceramic White 512 GB
PIE 9.0 / ONE UI
Samsung EVO 128GB Class 10 / UHS-I 100MB/sec
Click to expand...
Click to collapse

mistermidas said:
What carrier do you have? Nothing showing up anywhere for Sprint yet.
Click to expand...
Click to collapse
innocentone1 said:
There was an article about it. ATT is the only US carrier to get the night mode feature (ASF6)
The rest of us will have to wait.
Click to expand...
Click to collapse
mistermidas said:
Well that sucks ass....
Click to expand...
Click to collapse
Atomicmuffin said:
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Click to expand...
Click to collapse
mistermidas said:
Usually I'd be in the same boat as you, but since I'm on Sprint it wouldn't even let me sideload the firmware science update
Click to expand...
Click to collapse
iteam said:
AT&T
I saw it on firmware science and set my clock to July 4th as it wouldn't update at first. Said it was up to date. Set my date to July 4th and it updated! Camera is sweet! Fingerprint works way better for me and battery is better as well. Phone feels "smoother" all around as well. After a cache wipe and a reboot
Click to expand...
Click to collapse
Atomicmuffin said:
I've been recovering from Samsung/Odin modding addiction for about 3-4 years now. My first relapse and this happens
I'll give it a few hours, and if an Odin file for ASF6 doesn't show up somewhere, I'll just suck it up and Factory reset.
Click to expand...
Click to collapse
Atomicmuffin said:
Seems fine to me. Your sig is:
Click to expand...
Click to collapse
Ugh, why don't I see mine or anybody elses? I logged out and logged back in, checked my control panel settings and nothing... Not a huge deal but I don't know why

The new update has also dropped for Verizon. So Verizon and AT&T are the only ones with the new night mode for the camera.

Atomicmuffin said:
I'm on AT&T and I got impatient. I haven't done any phone-related poweruser activities in a few years so I said screw it and went to firmware.science. Grabbed the update zip. Sideloaded it. Went well...but hangs at "Starting Android". And they rolled over the bootloader version so I can't Odin back. ****.
Anyone have any thoughts? I can't seem to find a full Odin ASF6 download yet, which is expected considering it dropped yesterday.
My fault for getting impatient.
Click to expand...
Click to collapse
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.

innocentone1 said:
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
Click to expand...
Click to collapse
Regardless of using HOME_CSC? Well that's a shame.
Damn. Back when I was flashing stuff daily I was on USC & VZW, so this is my first rodeo with an ATT phone. Thanks for the heads up.

innocentone1 said:
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
Click to expand...
Click to collapse
You sure about that? Last 2 phones I've had were purchased directly from Samsung, but ATT model, and I never received a single OTA update from ATT. So I've resorted to upgrading via Odin. Haven't had to do a factory reset once.

Lavman72 said:
You sure about that? Last 2 phones I've had were purchased directly from Samsung, but ATT model, and I never received a single OTA update from ATT. So I've resorted to upgrading via Odin. Haven't had to do a factory reset once.
Click to expand...
Click to collapse
Hmm. Now I just don't know what to think

waiting for U1 firmware

innocentone1 said:
Usually when flashing an Att upgrade via odin 99% of the time a factory reset is required.
Click to expand...
Click to collapse
You would be wrong. I Odin'd numerous times on the S9+ and twice on the 10+. As long as you use Home CSC, it doesn't wipe. The 10+ says it's wiping but doesn't (or is only wiping cache).
Using an update.zip on the other hand wipes an ATT device.
---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------
Atomicmuffin said:
Hmm. Now I just don't know what to think
Click to expand...
Click to collapse
As long as you use a HOME CSC, Odin does NOT wipe an ATT device. Only if you use an update.zip

todd3835 said:
You would be wrong. I Odin'd numerous times on the S9+ and twice on the 10+. As long as you use Home CSC, it doesn't wipe. The 10+ says it's wiping but doesn't (or is only wiping cache).
Using an update.zip on the other hand wipes an ATT device.
---------- Post added at 04:46 AM ---------- Previous post was at 04:44 AM ----------
As long as you use a HOME CSC, Odin does NOT wipe an ATT device. Only if you use an update.zip
Click to expand...
Click to collapse
That's what I thought (about HOME_CSC, I mean).
Are you referring to sideloading a FOTA update ZIP via ADB? Maybe i'm missing something, but before I sideload anything I always comb through the updater-script. Old habit from CWM-Zip flashing. Nothing seemed out of the ordinary, nor do I recall seeing the userdata partition even mentioned in it, let alone any kind of factory reset initiation.
I DO recall seeing "Failed to update vendor image." towards the end of the sideload. When checking the last.log, looked pretty messed up. Almost like a kind of corruption of some kind. The log is gone now though, because first thing I did was Wipe Cache when it hung at "Starting Android"

May be too early to know for sure but I think I'm finally getting good reception and the signal strenth is now displaying in settings/connections/mobile networks.
On Verizon with the ASD9 firmware it would display not available now its giving me actually numbers.