Database Users

[Q] Last Resort! - Restoring to Stock on S4!

Hi. Before you read all that mess below, just answer this simple question first: Is it possible to restore to stock (as in with all bloatware and pre-loaded apps intact) on an AT&T Samsung Galaxy S4 SGH-I337 Baseband Version I337UCUAMF3 on Android Version 4.2.2? If not, just say so and disregard reading the rest lol. (If it's any help, the Kernel Version is 3.4.0-812098 and Build # is JDQ39.I337UCUAMF3).
So I have been messing around with my S4, specifically with NoBloat and rooting, trying to delete bloatware and such. And with that line, you should already know by now what has happened. Though I did backup most of the things I deleted, I think I've deleted some important things and now want my phone returned to stock. It has been rooted so I also want to get rid of the binary counter as well. Before you send me to another thread however, I want to tell you guys what I have already tried and researched, yet always encounter an obstacle in:
I have tried using Odin (3.07 AND Odin3 v1.85) and flashing (correct term?) to my phone with I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 as the PDA, but when I pressed start, Odin would get to the first box then say FAIL!. My phone then has START [224, 1440] then under it SW REV. CHECK FAIL : fused :2, Binary : 1. I think it may be because in the ID: COM space, my phone recognizes as a 0:[COM:3], 4, or 5, but not a 6, which in a video tutorial I've watched, says it must be a COM:6 for it to work. I have tried many of the troubleshooting tips such as removing and putting the battery back in, changing usb ports, and reinstalling drivers, all of them leading to the same FAIL! screen. I know the file and the version of my phone doesn't match (wishful thinking I guess xP ), but is there any other way pr a tar.md5 file for my version to restore using Odin?
Another thing I've tried is using ADB to reupdate (?) my phone. I downloaded the adt files and put the tar.md5 file in the platform-tools folder. Then I opened a command prompt but when I type in adb sideload <filename.tar.md5>, it says it could not be read or could not start. Backtracking, I tried downloading sdk properly but got lost in that and jumped off this method completely.
Finally, giving up all hope of reverting back to complete stock, I simply wanted to reset the binary counter, and even here I had issues. I found out that AT&T is one of the carriers that locks their bootloader, so I searched and found djrbliss' LOKI method to get around it. I tried downloading at the github link, but didn't know how to download it (maybe I somehow just didn't see the download button), so sadly, I couldn't do this either.
I have reset and restored using past backups but the applications, lock screen, and a few other things did not restore properly (while the rest of it did fine, strangely).
Sooo...yeah. I think I may have exhausted almost every method possible, so this thread is really my last resort. Please help me find a way or just tell me it can't be done, so I can put this to rest.
Sorry for the long-winded message, haha, but thanks to all who'll help me find a solution to this dilemma

Go to a best buy Samsung experience. They can flash the stock mf3 firmware.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
Go to a best buy Samsung experience. They can flash the stock mf3 firmware.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
But because I rooted before, won't that void my warranty? Or will they just restore to mf3 stock firmware no questions asked anyway?
Also, double checking, doing this will restore all stock apps and reset binary yes?
Thanks for responding quickly. I will try this out asap. :laugh:

AquaYan said:
But because I rooted before, won't that void my warranty? Or will they just restore to mf3 stock firmware no questions asked anyway?
Also, double checking, doing this will restore all stock apps and reset binary yes?
Thanks for responding quickly. I will try this out asap. :laugh:
Click to expand...
Click to collapse
It is void, but multiple people have taken in rooted phones and gotten them flashed. Just say it isn't, and they should. I don't know about binary but the system will be factory fresh
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

There is a thread on how to remove the 'custom' boot screen, but I am not sure if it works on mf3. Sorry, but can't find the link right now

Flashed custom recovery, WiFi broken

I have an SGH-I337 with Android version 4.4. I have the Knox bootloader (sadface). I attempted to root this phone previously using Saferoot but this caused problems (relevant thread).
I can connect to the data network but I can't get the wifi to work. It won't even turn on. As soon as I tap the switch it goes back off.
Please help.

You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app

DeadlySin9 said:
You'll probably have to use the NB1 full ODIN to fix it. Make sure to back up your internal storage and anything that doesn't sync to your Google or Samsung account.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.

goose90proof said:
Ok, I'll try that.
While I have your attention, I have a couple other questions...
- Do you know if this phone is actively being worked on by developers? As in, are exploits being researched to unlock the bootloader?
- Can the phone be rooted with an update? What is the preferred method to do this? Recovery (I have teamwin) or ADB?
EDIT: Is it safe to flash just the modem or would you recommend the full phone firmware. I found a thread here with firmware.
Click to expand...
Click to collapse
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).

DeadlySin9 said:
The phone is actively being worked on, most progress is kept between PM's or in a thread in the Verizon S4 section (they're in the same boat as us and chances are an exploit for one will work on both).
The phone can not be rooted with an update because we can't sign it once we add the su binary.
You can't flash the modem as those are recovery flashable zips and if you're on NB1 you can't get root or recovery without a more involved method first (no simple one click).
Click to expand...
Click to collapse
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:

WiFi issues with OTA firmware too
Just thought I'd add that the OFW has WiFi issues as well, at least for a few if us. When I updated OTA to 4.4 the WiFi worked for a couple of weeks then stopped working (reboot will allow it to work for a while until the unit sleeps, then it won't toggle). I tried the Odin tar.md5 image and the same thing crops up. This thread is relevant: [Q] OFW 4.4.2 WiFi Not Turning On. I like KitKat, hopefully we can figure out what the problem is.

goose90proof said:
Thanks much for verifying that for me. I'm content to wait until a solution is found. Just relieved to hear that the smarties are still tinkering with it. :good:
I guess I don't have TeamWin then? That's odd because after my failed root attempt, it was after I tried flashing teamwin that the phone booted back on after being softbricked. I guess that was coincidence then. At any rate, I will try to flash the NB1 firmware to fix the wifi. At least I have data. :silly:
Click to expand...
Click to collapse
You likely overwrote the stock recovery. Here is the NB! stock recovery. Flash in PDA slot in Odin:https://mega.co.nz/#!M9EQBT5A!ri4QeMYpgi-JjmUGZ3FY2gtogDBWPEL7zRCjASIcVe8
If you need the NB1 stock modem here it is. Also flash in PDA slot in odin: https://mega.co.nz/#!sstkFRiJ!d9zTRte0KcVFv7o-bjKFuFMM1Q9ivzDlqJKy2OlP_7o

Excellent thank you.

goose90proof said:
Excellent thank you.
Click to expand...
Click to collapse
did it work for you?

I haven't gotten around to trying it. The phone is working now so I'm a bit reluctant to do anything to it until future developments bear fruit.

[Q] no wifi rooted at&t S4 4.4.2 NB1

greetings!
I've been searching for hours and bashing my brains trying to get wifi working. It originally broke after an OTA update
tried all the tips and still nothing works permanently. The things I have tried are too numerous to remember or list.
It's not a hardware issue as wifi can work for periods of time but it always breaks - I assume because of an update that downloads and breaks it.
i see talk of reflashing "modules" with safestrap but safestrap has never worked properly and now does not work at all ("unfortunately safestrap has stopped") Can modules be flashed from Odin?
TIA !

Sorry to hear about your troubles man. Been there, done that...
IMHO, if you don't have hardware issues, this what you should do:
ODIN to stock http://forum.xda-developers.com/show....php?t=2616221 (post 1, the Returning to Stock / ODIN section)
After that root
Root with towel root (https://towelroot.com/)
Install SuperSU (PlayStore) and let it disable Knox.
Install BusyBox (PlayStore) and let it cook
Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
Install Safestrap (http://forum.xda-developers.com/show...php?p=45693712)
Now it's time to flash you favorite rom (Safestrap has the list). Copy the following to your SD card:
Your favority ROM
SuperSU.zip file. (http://download.chainfire.eu/451/Sup...erSU-v2.01.zip)
Your modem zip file (http://forum.xda-developers.com/show...96&postcount=1).
I337 Build.prop/APN (http://forum.xda-developers.com/show...81&postcount=9)

Same boat as well I believe, need help please.
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.

Few screens to help out
Here are a few screen shots that I hope help someone out. Please let me know what I can do if anything.

ONLY DRAGONMIKE said:
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.
Click to expand...
Click to collapse
You won't be able to put cwm on it or cm. See index, all things at&t......in the general forum
Sent from my Nexus 5 using XDA Free mobile app

Ummmm a tiny bit more help please lol
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.

ONLY DRAGONMIKE said:
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.
Click to expand...
Click to collapse
Just click on the spoiler for nb1 need users. The step by step is there. It's in the first post
Sent from my Nexus 5 using XDA Free mobile app

So this one
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.

ONLY DRAGONMIKE said:
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.
Click to expand...
Click to collapse
You're on nb1 and rooted. The next step is to install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app

So Safestrap 3 it is
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.

ONLY DRAGONMIKE said:
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.
Click to expand...
Click to collapse
What's mdf?
Sent from my Nexus 5 using XDA Free mobile app

MDF Reply
Security software Version
MDF v1.0 Release 2

MDF Reply
Here is a screenshot of where I'm talking about. Oh and Safe strap 3.72 is installed perfectly thank you so very much for that. Your awesome. And a lot of people are saying when you reboot and it shows the "Safestrap is disabled" screen you can't get back into it. I did just fine.

ONLY DRAGONMIKE said:
Here is a screenshot of where I'm talking about.
Click to expand...
Click to collapse
You're on nb1 firmware, safestrap is ok
Sent from my Nexus 5 using XDA Free mobile app

NB1 discussion
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.

ONLY DRAGONMIKE said:
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.
Click to expand...
Click to collapse
You can not install any roms. The i337 on any firmware higher than mdl can only flash touch wiz based roms. See the index, all things at&t.... for roms that are compatible.
Sent from my Nexus 5 using XDA Free mobile app

This mini-guide should work!
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks! :good:

[Q] How to unlock rooted i9505 from EE network

Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!

intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
I don't think so if you had android 4.4.2 before flash the custom ROM. You will have to buy a unlock code.

How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!

intacto said:
How is that even legal, it wouldn't be in any other country this phone belongs to me, how the company can ask me to pay for unlocking something that belongs in 100% to me!
Click to expand...
Click to collapse
I don't know if is legal or no. All depends of the little letter of the contract. Did you read the contract when you signed it?

intacto said:
Hi my contact run to its end and EE has an audacity to ask me for £20 quid to unlock a phone that they locked, that now belongs to me. As I have absolutely no intention to pay for it or upgrade, nor conduct any further business I would like to remove the lock, I am on new cyanogenmod 12 and rooted with CWM recovery. It shouldn't be that difficult, anyone is willing to help?
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.

Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.

intacto said:
So you think hat will work, I will definitely try it, anything to prevent this blood sucking supplier getting any more money off me! One question tho, when I do the backup of my current lollipop via cwm, do I have to wipe all the cache and after restoring it I wont have any issue with all the applications/customisation I currently have? It would kill me to set up everything again
and one more question, my lollipop version is like a week old, if I was to download the latest nightly can I upgrade my lollipop without loosing any apps/settings?
Thanks a lot for your help, I really appreciate it.
Click to expand...
Click to collapse
I hope he explain you too the PROS and CONS about that process :highfive:

I know the pross, what are the cons?

The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.

Strephon Alkhalikoi said:
The con with the service menu method is that it's possible to really screw up the phone. The RegionLock Away method is far better, but its cons are that there's no guarantee that the unlock will stick if the modem is upgraded, plus the app was never intended to unlock phones but simply remove region locking.
For a price of free though, neither can be beat and I didn't encounter any problems when I did it myself. The foolproof method however is to pay for the unlock. Why your carrier charges is unknown. As to whether it's legal for them to do so, unfortunately it probably is. Otherwise they would have stopped long ago.
Click to expand...
Click to collapse
Well I have tried that service menu trick while on kitkat, but that didnt go pass step 2, it didnt even show me the menu, but I am fine with downgrading to 4.2.2 and giving it a try....I also tried ragionaway app 2 days ago, that was a no-go

Because the exploits that allowed both to work were patched in versions later than 4.2.2. Downgrading the modem at minimum is a requirement for either to work.

Strephon Alkhalikoi said:
http://forum.xda-developers.com/showthread.php?t=2282683
You'll need to install the 4.2.2 stock ROM here in order for either method discussed to work. Once done, then you can reinstall CyanogenMod. So, before starting, take a nandroid backup through CWM.
Click to expand...
Click to collapse
Well it didnt go well with this 4.2.2 rom i must said, i got this in Odin:
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
I then tried to do the stock of 4.4.2, that resorted fine but it wiped my IMEI and now phone doesnt connect to mobile network...help...:crying:

What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.

Strephon Alkhalikoi said:
What version of Odin are you using? If it's not 3.09 or 3.10, download either of those and try again. Also, make sure you're using the original cable, are connected directly to the computer and not through a hub, have the drivers properly installed, and don't have Kies running.
EDIT: Lastly, try changing the USB port.
Click to expand...
Click to collapse
I have managed to revert back to lollipop from hte backup and it works fine but I am still in the square one. I do use the original cable, direct to my PC drivers are there, kies isnt running. It did a proper flashing to 4.4.2 but it refuses to have that 4.2.2, is there anyway to downgrade the modem only from 4.4.2 to see if that will work for me? also my phone is i9505xxugni2, the rome u gave me the link to has a different PDA, would that prevent the flashing of my handset?
Cheers!

Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.

Strephon Alkhalikoi said:
Absolutely. Go here and take a look around. You should be able to find a 4.2.2 modem from there. But, unless you deleted the download, you also have it in the 4.2.2 ROM download. the .tar.md5 files can be opened in WinRAR on the PC.
Click to expand...
Click to collapse
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:

intacto said:
So I did manage to flash this rom and that was successful, that revert me to 4.2.2, it didn't wipe my IMEI. Then I tried any method of unlocking I could find, even the regionaway, galaxy unlock app and with no luck, when i try to bring up the service menu by typing 1 after *#0011# it never brigs it up, I followed instructions to the letter I think I would have to pay for the code:crying:
Click to expand...
Click to collapse
:good:

RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.

Strephon Alkhalikoi said:
RegionLock Away requires root for it to function, as it rewrites system files. I believe the app itself mentions this. The service menu exploit may have been removed by EE.
Paying for the code is your only alternative if the free options don't.
Click to expand...
Click to collapse
Yes region away always ask for root so I have to re-do it every time after the flash. But seriously EE is the worst provider and one of the most hated companies in UK. I would rather pay someone on the street with z3x box than them

in our country we can get unlock code for free, but only till one month from end of contract. later they ask money.
i hate them too for asking money, but on other hand: why they should do anything for free if phone is yours and not their.

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.

Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.

So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app

rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.

JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app

http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app

I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient

Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.

Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.

JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.

Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)

Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks

Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.

JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far

Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.

joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf