Database Users

[Q] I need I337UCUAMF3 official firmware

I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]

chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
I might be wrong here as im not the sharpest tool in the shed, but i do believe there is a new post like this every single day and all get the same response. There is no MF3 image available for flash through odin or otherwise. Search = Friend.

If you repeat three times "owaa tagoo siam" it might magically appear.

Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)

agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
It seems useless

So did you try it or just say its useless? There are a couple other methods that have been shown to work as well.
Sent from my GT-I9505G using XDA Premium HD app

You are going to have to wait for Samsung to release the MF3 on kies or a leak of the tar to happen.
Sent from my GT-I9505G using Tapatalk 2

chentongxin said:
I accidentally deleted a few important documents led to the current system fails to boot, whenever I boot it always stays in the interface of a white background, and now I can get into odin mode but not in the recovery
My mail is [email protected]
Click to expand...
Click to collapse
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT

salwansk said:
hey buddy, im not familiar with Samsung restoring things cuz im an HTC person. but i was talking with a samsung rep and played dumb, i told him i did OTA and my phone died on me. now it booting up with emergency mode, and i told him i tried to hook it up to kies with emergency mode but no luck....
he gave me this like to remove custom OS ROM, i know its stupid but it kinda a different way to re-install the stock OS...
im sorry if being a NOOB here, cuz i said before im an HTC guy and love RUU ....
anyway if you already know that, then ignore it. otherwise try this link and let me know if this restore MF3 for you.
thanks
http://www.samsung.com/us/support/faq/FAQ00052690/61265/SGH-I337ZRAATT
Click to expand...
Click to collapse
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.

scott14719 said:
Its been stated 1000 times, this will not work with MF3 at this time. Using Kies to try and restore Firmware if you are on MF3 or using ODIN at best will not work and could possibly make things worse. There are a couple of exceptions using modified files (you can find them in the forum) but other than those exceptions absolutely KIES and ODIN will not help to restore Firmware if a phone is already on MF3.
Click to expand...
Click to collapse
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ

salwansk said:
LOL... i think i might upset u right ? sorry bro...
i hope some one can modify the stock MF3 soon...
i had similar problem with Sprint note2 L900 4.1.2, it won't downgrade to 4.1.1 in order to get the SPC and flash it with different carrier. but one of the genius guys modify the stock 4.1.1 to let note2 accepted without error ....
its here
https://www.youtube.com/watch?v=f0d2B9lfouQ
Click to expand...
Click to collapse
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.

scott14719 said:
No, definitely didn't upset me. My phone works and i know what I am doing. However, you probably would have upset the OP if he would have tried your suggestion and screwed his phone up worse. It would have been his own fault because there is always risk when it comes to doing anything to our phones, but being a bit more cautious when making suggestions to people would be a good thing also. Especially when there is already so much information about this in the AT&T S4 forums.
The video you linked to, once again, will do no good. ODIN will not work for restoring firmware on an MF3 phone at this time period.
Click to expand...
Click to collapse
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.

salwansk said:
i know ODIN will not work for restoring firmware on an MF3 phone at this time, but this link was just an example. maybe in the future someone can do something work with MF3....cuz at my work now we can't sim unlock or fix imei with this bulid MF3, i have tried octopus box, nspro, and setool3. non of them was able to sim unlock MF3, even the secret menu not exist in MF3....
i asked the riff jtag rep, if i can resurrection I337 MF3 and unlock the bootloader with riff box. he hasn't responded yet.
Click to expand...
Click to collapse
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.

scott14719 said:
Many things have been tried with this already.
Look up a poster called "Aou". His posts will help shed light on the subject. Adam Outler also has worked a lot on the issue. The entire MF3 OTA was torn down and part by part tried. Once the MF3 bootloaders are applied, it simply can not be rolled back. There are software and hardware reasons for this, but it has all been tried. The result every time is Hard brick that JTAG can not fix at this time.
Once the full MF3 firmware has been released, maybe this will change, but it is doubtful. The MF3 bootloaders will still be the same. Without Samsung's signing key, the bootloader cannot be modified.
Once Samsung releases the full MF3 firmware (for ODIN and Kies) it will hopefully enable people to flash or restore back to a factory MF3 state, but we will still not be able to roll-back to AMDL. Maybe the full MF3 firmware release will include more files to work with...but again, it is doubtful.
As of now, the only way to sim unlock a phone on MF3 is to use a code (from AT&T or other). Hopefully someone will find a method that will work with MF3...but it hasn't happened yet.
You have good ideas about what should be done but it is important that you look and see what has already been tried and what is known at this point. Hopefully, people will still try to modify and work with MF3 (maybe something that hasn't been tried yet), but it will be building on what has been tried so far.
So, basically, at this time ODIN and KIES will not work with MF3, except for the modified files used without the bootloader. Neither will restore the phone to stock or can be used to roll back the firmware.
Hopefully, when Samsung releases the MF3 firmware, people will be able to restore their phones through ODIN and KIES, but will still be stuck on MF3.
In order to do any more, another work-around (such as the LOKI exploit) will need to be found or someone at Samsung is going to have to release or leak the encryption key.
That is pretty much all for now.
Click to expand...
Click to collapse
thanks bud, and yes i started read about this issue just today.
i know samsung is way easier than HTC when it comes to unlocking and flashing, thats why i didn't care at first. but what freaked me out when i tried to sim unlock galaxy s4 yesterday. today i found out about the MF3 and how is it pain in the axx :laugh: .... thanks for the info bro :good:

add myself to the thread for future fixes...

Scott that was probably the best explanation I have seen yet. You should have it pinned lol
Sent from my GT-I9505G using XDA Premium HD app

agent929 said:
Not happening my friend. Try going into download mode and then press down to cancel. It might boot normally then. (worked for me at one point with a similar issue)
Click to expand...
Click to collapse
Well Thank YOU ALOT.. you saved me TONS OF WORRIES. That trick got me out of a boot -> recovery -> odin mode loop. I thought I was going to have to confess to ATT and beg for them to fix my phone. I wont be touching my recovery again for a while. Not until a confirmed method and hugely tested recovery/custom rom method comes out.

Thank you! I knew that little bit of advice would help somebody one day.

[Q] Can't unlock rooted sgh-i337 on 4.4.4

I have a stock SGH-i337 running android 4.4.4 that is rooted.
I've rolled back to NC1 without success. I'm currently at NJ4.
I need to go from AT&T to T-Mobile.
I cannot access the hidden menus to remove the carrier lock.
None of the methods mentioned here seem to work - *#0011#, *#9090#, etc.
Any ideas?

Install safestrap, then flash the mf3 modem. Then try regionlockaway.
Sent from my Nexus 9 using XDA Free mobile app

Did that work? I'm going to be trying this for a phone my daughter bought a couple of days ago. It's an AT&T S4 that she wants to use on Tmobile.
The phone is on 4.4.4 and using I337ucuFNJ4. She used Ebay unlocking service and said they couldn't do it because of money owed on the previous owners account. She gave me the IMEI and it looks clean (as she did check this online and with AT&T before buying).
How can the phone essentially have a clean IMEI if money is still owed on the account? I'll get it from her on Friday and see what I can do.

Ok so I have the s4 rooted with towelroot and flashed the modem back to NJ4. Everything works fine.
Installed busybox then safestrap 3.72 and all of it installed fine. I have SuperSu and did a check root all is fine.
Now do I flash in safestrap the MF3 modem files and install regionlockaway then flash back to NJ4 with Odin? Man I have been searching around for hours to try and get this done. I hate asking for help, but if someone could give a little more detail it would be greatly appreciated. I don't want to brick this thing and was trying to get this down to give it to her in a couple of hours. Thanks guys.

I have a new paper weight.
I've fallen back to my original Galaxy S.
I hope the GS6 arrives soon.

Is unlocking this at&t phone even possible? And what did you do to brick your phone dude? I get the feeling I'm wasting my time with this, that it's not possible and people in the know are having a laugh. I hope that is not the case here.
There is just too much BS on the internet and feel like I'm searching for a needle in a haystack at this point.

Battery failure / short circuit / smoke / bad luck. I have to obtain a battery before I can tell if the damage is permanent.

Got it to work!
Ok I first off sorry for your trouble and hope the phone is not damaged buddy.
I used this technique here http://forum.xda-developers.com/gal...aranteed-free-sim-unlock-mk2-nb1-nc1-t2852979
Odin 3.10 was no longer working for me to flash baseband modem so did it all using safestrap. The files that safestrap uses are zip files and use them like they are (don't unzip them to use) and they are about 22 mb's in size.
The trick for me is it didn't work right away. I had to reflash with safestrap my NJ4 modem and reboot.... and put in the correct APN settings for T-Mobile.
So it does work and hope I can help others that fall into the same problem. If you need help just leave a message in this thread and I've subscribed to it so will get an email letting me know.
APN settings - https://support.t-mobile.com/docs/DOC-17581
This page came in helpful for grabbing need modem/baseband firmware - http://forum.xda-developers.com/showthread.php?t=2496517
Good luck! Do a backup in Safestrap if you're nervous. You can always start over.

The good news - only the battery was burnt.
What boot loader do I have? getprop ro.bootloader returns I337UCUFNJ4 and getprop ro.boot.baseband returns MDM. I presume that MDM is the bootloader version and I337UCUFNJ4 is the modem version.
I'm concerned that the guides and tips are for older versions of the GS4 that don't work on 4.4.4 and may actually do damage.

Ok glad to hear the good news man. The I337UCUFNJ4 is your modem right now.
A nice little free google play store program to use to get info on your phone is called Phone INFO, download it now please.
This will show you all kinds of information on your phone and what you need is to know is Device Type to know which Safestrap to install. Mine or my daughters was klteatt.
Keep in mind I don't have the phone in hand anymore, gave it back to her last night.
What you'll need to download from the modem page link is the I337UCUFNJ4 and the MF3 modems and keep them in their zip format to use. Create a folder on your external sd card ( mine was EXT SD Downloads ) and put both modem zip files in there.
Another program that needs to be installed is called BusyBox and I just used the free version https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
You will need this busybox installed for safestrap to work properly. And also have developer Options activated and check install from unknown sources etc etc (you can do a quick search on this one) it's key to have this done and very quick to do.
Now if you follow the instructions here http://forum.xda-developers.com/gal...aranteed-free-sim-unlock-mk2-nb1-nc1-t2852979
the only thing I did different was flash back the modem MF3 firmware back to the NJ4 that you currently have. APN T-Mobile settings might have auto populated once the card was recognized (I had manually put it in earlier when it didn't work before flashing to NJ4) so not sure.
When safestrap is installed properly it will say so at the top of screen and nothing is greyed out. Do a backup so you can start over if you screw it up. Take like ten minutes or so, no worries.
I've had very little coffee this morning and sorry for being a bit all over the place with this. Let me know how it goes and if you need more help. Good Luck! At least you know it will work, I didn't.
I used Safestrap-JFLTE-3.72-kk-B01 (sorry for confusion forget the klteatt, sorry)------- phone INFO - https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en

I followed the instructions very carefully. The problem is that I no longer have cellular service on any network.
I've rebooted, tried to reflash each of the modems. NJ4 flash fails while the MF3 flash seems to work, but I still have no cellular service.
Phone info shows bootloader NJ4 and baseband MF3

hmmm makes it a bit harder not having the phone with me anymore. You did the developers options correctly?
Perhaps use Play Store and download 'SELinux Mode Changer' to see if it will allow you to install through Safestrap the NJ4 modem firmware?

nicetucu said:
hmmm makes it a bit harder not having the phone with me anymore. You did the developers options correctly?
Perhaps use Play Store and download 'SELinux Mode Changer' to see if it will allow you to install through Safestrap the NJ4 modem firmware?
Click to expand...
Click to collapse
Been there. Did that. No joy.
There is an NJ4.tar.md5 file. How do I use it?

ua549 said:
Been there. Did that. No joy.
There is an NJ4.tar.md5 file. How do I use it?
Click to expand...
Click to collapse
Flash it in Odin
Sent from my Nexus 5 using XDA Free mobile app

I used ODIN to flash the file. Baseband is still MF3. Still no joy. I'll try going back to NC1.

ua549 said:
I used ODIN to flash the file. Baseband is still MF3. Still no joy. I'll try going back to NC1.
Click to expand...
Click to collapse
Try the nb1 tar file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try the nb1 tar file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! The phone is now working but I have to download, install and configure all (~150) of my apps again.
It will take a couple of days to pair all the Bluetooth devices (plus travel). I wish I'd known that this was a complete reset. I could have captured many of the apps, network locations and configurations. That said, I don't have to buy a new phone.

ua549 said:
Thanks! The phone is now working but I have to download, install and configure all (~150) of my apps again.
It will take a couple of days to pair all the Bluetooth devices (plus travel). I wish I'd known that this was a complete reset. I could have captured many of the apps, network locations and configurations. That said, I don't have to buy a new phone.
Click to expand...
Click to collapse
Sorry man, I thought if you've used Odin before you knew it would wipe your phone.
Sent from my Nexus 9 using XDA Free mobile app

yikes..... well good thing is the phone works. Glad it worked out, well kinda lol.

I'm happy I don't have to buy a new phone before the GS6 arrives. I'll just stick with AT&T until then.
I appreciate everyone's help!

Need help flashing stock S5 G900R4

Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.

First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces

*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.

Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e

*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.

nice one

*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?

I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe

*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.

Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case

*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?

Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc

I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely

Phone bricked due to FRP?

Hello guys,please make sure you activate OEM UNLOCK in the developer options before you root your Android device with FRP installed. otherwise you risk to get into a bootloop after trying to boot into recovery due to FRP blocks custom binaries

have u tried using kies and using tools/firmware upgrade and putting your model number in and flashing with stock ? have you tried using odin and doin the same ?

jo01 said:
have u tried using kies and using tools/firmware upgrade and putting your model number in and flashing with stock ? have you tried using odin and doin the same ?
Click to expand...
Click to collapse
I am downloading the stock ROM now it takes a while. But how the hell can google tell me what i have to install and wehat not when i paid the phone? I am so pissed, its unbelievable. **** google and **** Samsung for letting this assholes do this.
Ok KIES does not even recognize my phone. The mworse is, it would start if it would not try to start into recovery. is there any option to remove the "recovery bit" or something like that and make the phone start normal and not into the recovery? That is my problem.
k now it is definately bricked, after i triedto flash a stock rom it says an error ocurred while recovery an i shall use smart switch but smart switch says unsupported device, i can not believe thishappened because of a google feature which no one asked for and they brick a device i bought for 800 bucks

OK FIXED, i had to flash via ODIN the Origin ROM, in my case the phone came from Italy and the Provider was TIM, it took me 7 Euro to download at Sammobile full speed and got it in 5 minutes.
Can be closed

I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.

this is quite concerning as i purchased my phone from Amazon Italy as it was cheaper than anywhere else but i was unable to root despite following the steps but i discovered it was because of the FRP, but i don't want a situation like this to happen, any more tips would be good, preferably without having to spend money from sam mobile too.

Brunkhorse said:
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
Click to expand...
Click to collapse
Im having the same problem. I can only access the download menu on the phone and all of my many attempts to flash or recover it failing with the phone saying "custom binary (recovery) blocked by FRP lock". I only know a limited amount about the rooting scene but if anyone could post a rom or something that would fix this or a method to remove the lock even with the smallest chance of success I definitately would give it a try(maybe a step by step as well please ) . Again there is no way i can see how to access anything on the device. My phone is the SM-G928W8 from Canada with Telus. Anything is worth a shot so if you have any ideas id love to hear them, thank you everyone :fingers-crossed:

ibstickboy said:
Im having the same problem. I can only access the download menu on the phone and all of my many attempts to flash or recover it failing with the phone saying "custom binary (recovery) blocked by FRP lock". I only know a limited amount about the rooting scene but if anyone could post a rom or something that would fix this or a method to remove the lock even with the smallest chance of success I definitately would give it a try(maybe a step by step as well please ) . Again there is no way i can see how to access anything on the device. My phone is the SM-G928W8 from Canada with Telus. Anything is worth a shot so if you have any ideas id love to hear them, thank you everyone :fingers-crossed:
Click to expand...
Click to collapse
YOu need to find a stock ROM, this will be the hardest part. AFter you have it, flash via ODin and the problem will be solved, i had the same problem. But you have to hurry because FRP also locks the charging of the battery so once you run out of battery you need to bring it to a technician.
jonny68 said:
this is quite concerning as i purchased my phone from Amazon Italy as it was cheaper than anywhere else but i was unable to root despite following the steps but i discovered it was because of the FRP, but i don't want a situation like this to happen, any more tips would be good, preferably without having to spend money from sam mobile too.
Click to expand...
Click to collapse
I spent the money because i needed it quick, if you download a stock ROM and have it left you can go ahead. YOu can download at SLOW MODE for free at sam
Brunkhorse said:
I am in the same situation. I tried using the Recovery method with smart switcher or ODIN to flash the stock firmware but I am still stuck in a boot loop. I cannot access recovery at all and cannot install as the lock protection is on. Any other suggestions? I wasn't trying to root my phone it just decided to shut off and not boot up again.
Click to expand...
Click to collapse
Check if you have the right stock ROm, it needs to be exactly the same country and provider. There is unfortunally no other way to remove FRP but booting the phone and remove the google account

can be deleted, i thought it works like on other subforums that new posting willl be added

please delete

Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?

thismonk said:
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
Click to expand...
Click to collapse
The battery is not locked (as far as I can tell), my phone got the lock when it was fully dead and while I was charging it and it seemed to have a charged battery after I unplugged from charging for awhile but there was no actual way to check. As for the firmware you will just have to wait for it my friend, that is the same firmware I needed and as of just now they still don't have it available on sammobile. Sorry man and best of luck

Needed? Did you end up getting the phone fixed by someone or send it back in to Samsung?

No I didn't get it fixed I sent it back to the phone company and paid a small fee rather than waiting for the firmware to be released.

Who was your phone company? I'm wondering because I can't seem to find anyone to help. I even contacted the local Samsung service center who deals with Telus and they told me that they could replace the mainboard but woudlnt flash the firmware or otherwise fix it. So that was rather useless I'm essentially buying a new phone.

thismonk said:
Is it true that the battery doesn't charge after it's FRP locked? So the missing W8 firmware even if it comes eventually when the battery is dead the phone is dead? How in the hell are we supposed to fix this with no firmware available on sammobile?! Is there really no other way? Who has the firmware? Do the carriers have it?
Click to expand...
Click to collapse
Absolutely right, if the battery runs out, you are lost. Then you have to bring it to the Samsung Service, they will fix it for you, if you pay of course..because KNOX will be void. The only way to avoid this is to remove your google account from the phone or enable under Developer Settings the OEM UNLOCK. Then FRP is disabled. But if you forgot and are now in a bootloop you have a real problem because as i have seen the W8 Firmware is not available on sammobile.

deepphrozen said:
Absolutely right, if the battery runs out, you are lost. Then you have to bring it to the Samsung Service, they will fix it for you, if you pay of course..because KNOX will be void. The only way to avoid this is to remove your google account from the phone or enable under Developer Settings the OEM UNLOCK. Then FRP is disabled. But if you forgot and are now in a bootloop you have a real problem because as i have seen the W8 Firmware is not available on sammobile.
Click to expand...
Click to collapse
My battery ran out but the phone is actually still working. When I plug it in via USB it powers up. It doesnt' actually charge the battery, but this will work for Odin. Now I just need to find someone to dump the stock firmware for me...

Any updates on a firmware?

If you need to go to stock then have you tried to boot I to download mode and use smartswitch reinstall feature?

thismonk said:
My battery ran out but the phone is actually still working. When I plug it in via USB it powers up. It doesnt' actually charge the battery, but this will work for Odin. Now I just need to find someone to dump the stock firmware for me...
Click to expand...
Click to collapse
I have same Problem as all of you but haven't fixed it yet because I still haven't found right ROM but if you have wireless charger it will force charge!! ??

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