Database Users

[Resolved via warranty] Phone bricked overnight and Re-Partition operation failed

Hello everyone,
Upon waking up this morning, I found that my phone was stuck on the (very first) Samsung logo. Before going to sleep, I was already booted and everything was stable.
I attempted to enter CWM recovery, but it would not work. It would continue to show the Samsung logo.
Entering download mode, I see the following -
Product name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
This is strange, and pretty wrong. My product name is empty, custom binary download is "No" instead of at least "3" (I never have used TriangleAway), and I wasn't using an official Samsung ROM before the problem.
The very first thing I tried was flashing the Siyah .tar file. I get this:
"<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed."
If I attempt to flash a full, multi-part .tar.md5 file in PDA, ODIN v3.04 shows a "There is no PIT partition." error and fails. Re-partition is not ticked.
Therefore, I've tried to flash each of the following, with re-partition ticked:
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
Each of them fail with a "Re-Partition operation failed." error.
If I try to flash a .pit file and the full .tar.md5, I get the same "Re-Partition operation failed." error. The same happens when I try to flash the .pit and Siyah at the same time.
Once a flash fails, I need to turn my phone off and on into download mode again, or else ODIN will stop on "<ID:0/004> SetupConnection.." and not continue for every type of flashing attempt.
The same thing happens for both ODIN v1.85 and v3.04, I've taken my battery in and out, I've tried this on two different computers, I've used every USB port, my Samsung drivers are up to date and Kies it not running in the background.
I've searched Google and XDA for hours, and I'm pretty sure the the problem I need to resolve is the "Re-Partition operation failed." error. However, almost no one on the internet has ever had this error.
The absolute very last abnormal thing I did with my phone was use the app "GetRIL" app as recommended on page 857 of the Siyah thread. The process said it succeeded, but the RIL didn't match the Baseband in the end. My phone was completely functional after, and I don't think the app even asked for root privileges at any point, so I'm not sure if it could have been capable of causing an issue this dire.
Is there anything I can do? I just can't imagine how my phone could have broken itself overnight while charging...
Any help would be greatly appreciated.

Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.

Kangburra said:
Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.
Click to expand...
Click to collapse
CWM is completely inaccessible!
I'll try a service centre after I've tried absolutely everything with this phone... I don't think I'm covered by warranty after rooting (Although they maybe won't be able to tell given how messed up the download mode seems to be right now)

Same problem here!
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:

nicoroldan1 said:
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:
Click to expand...
Click to collapse
If you can't get to recovery then you must return to Samsung.

Kangburra said:
If you can't get to recovery then you must return to Samsung.
Click to expand...
Click to collapse
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?

nicoroldan1 said:
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?
Click to expand...
Click to collapse
I don't know, it would depend on your terms of warranty.
If you are stuck you could try to unbrick it yourself.

Mine woke up to the exact same thing. Sadly I don't have a solution for you, this happened 1 week after being bought so I just had it replaced. I had not modified it in any way nor I tried any repair on my own (no reason to).
Sorry for your phone bro... id still try sending it to Samsung, if it's that screwed maybe they won't try to figure what happened.
Sent from my GT-I9300 using XDA Premium App

I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps

kart_y_26 said:
I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps
Click to expand...
Click to collapse
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:

I would suppose the nand chips are damaged for whatever reasons, which makes a trip to the service center inevitable.

aegixnova said:
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:
Click to expand...
Click to collapse
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app

kart_y_26 said:
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It's a stock ICS taken from sammobile.
I've tried running ODIN v3.07 on my 32bit Windows 8 tablet, and my 64bit Windows 8 notebook across both 1.5.4 as well as 1.5.5 Samsung drivers, in both XP compatibility mode and default. Nothing.
Windows updates the drivers after my phone enters download mode, so I've tried flashing both before and after the driver download and installation. Same result.
I haven't tried running ODIN v3.07 on my Windows 7 computer (But I have for v3.04), so I'll give it a go later. I think I know what the result will be

I've given up, and will contact Samsung to get the phone repaired by them. I'll edit this post or bump the thread later with details of how the warranty was handled. I'm hoping that the end result will be favorable for me.
Thanks for the help, everyone. :good:

Same thing happend to me :/ Tried to flash PIT partition via odin again and it failed! Official service center voided my warranty. My phone is now at the unofficial service and i am waiting if it can be unbricked! He said if the phone gets to DL mode it should be OK!

Good luck buddy
Sent from my GT-I9300 using xda premium

I took my phone to an unofficial phone repair shop, 'Fonebiz'.
They replaced the entire phone circuit board within the hour, and Samsung was billed due to my phone still being under warranty. I don't know whether they were unknowledgeable of warranty checking procedures, uncaring of warranty procedures, or simply could not tell due to the extent of the phone's brokenness. Needless to say, I lost the contents of my internal SD, but thankfully most things were backed up.
Either way, I recommend unofficial repair centres which can be funded by Samsung, and my few days without the phone really let me appreciate the quality of the product and service I received.
I'm guessing that the problem was either a pure hardware fault, or Siyah kernel's dual-booting functionality messing up how partitions can be flashed to the phone. I'm not placing blame on anything, however.
I'm very pleased with both Samsung and the end result. :good:
I wish the very best of luck to everyone. This seems to be one of the few ways these solid phones can be bricked, and it's heartening to see that it can be resolved under warranty.

hey,
thanks for making this thread.
it is indeed devastating to find that other people experience my same problem and how they needed to replace the phone
i did nothing to my phone, no root, original firmware.
maybe dropped it once or twice but it worked fine afterwards for plenty of time.
last night i went to bed after putting it to charge as i usually do, while it was on and perfectly working.
this morning it was showing the s3 logo (weird thing is that the led was flashing as if the phone was still on and notifying about new emails)
then everything happens as in the OP
- no stock recovery abailable - reboot loop showing only the logo and nothing else
- normal boot stuck only showing the logo
- people haven't been mentioning this but: with the phone completely off, if i connect the charger it shows the battery empty with just the "in progress" circle and nothing else happens..
- download mode accessible but no "product name", and the unseen before "system status: custom"?
- what does that mean? anybod with a working s3 can tell us what they have in download mode? much appreciated
- all the while firmware is "samsung official" and custom binary is "no"
1. are people certain i cannot bring this back to life?
2. can anybody suggest a way to maybe retrieve at least some of my data?
3. warranty is a little tricky - bought on ebay.... anybody claim warranty in this situation? or have any pointers how to go about it?
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair

DorinAlex said:
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair
Click to expand...
Click to collapse
http://www.freesamsungrepairs.com/

[Q] My Note 3 is stuck after trying Odin

thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-

I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...

I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:

K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...

amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.

You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers

Hi there,
This is what I get in Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?

In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.

One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed

Are you trying to Root ur phone or Flash Stock ROM?

Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.

Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?

Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?

Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.

amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.

OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!

Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.

OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...

Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?

[Q] Bricked my note 3

i just picked up my Note 3 the other day from verizon (SM-N900V) and i attempted to root it using Root_de_la_vega. It was my fault for not doing more research, but i thought since i wasn't going to do anything fancy other than remove all the bloat ware that it should be simple enough. Now when i use Odin (3.09) it keeps failing and now my phone is bricked and now it says i need to use the software repair assistant.I have tried downloading Kies 3 as one site suggested, but for some reason it does not recognize the device What is the quickest way to repair this? I don't care if it goes back to default. I really need to fix it ASAP! Please help!
Below is the script that shows up in odin when i try to root it:
ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> cache.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07

droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
ok, im new to this, and its my fault for jumping in the deep end without doing my proper due diligence. I dont have a good clue what you mean my MJE odin file? Are you refering to the AP file that i drop into odin?

droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
i also tried using different versions of odin. Can you link to a good root file for SM-N900V?

When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.

theicro was
bftb0 said:
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
Click to expand...
Click to collapse
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?

Just to Add Here Are 2 Other Good Places To Look
http://forum.xda-developers.com/showthread.php?t=2576104
How To Flash in ODIN
http://forum.xda-developers.com/showthread.php?t=2543386
Root Recovery Roms
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
Download root checker from play store

thanks all for the help, and thanks for not chastising me much for my ignorance. Ill def make sure to do much much much more research before i try to do something like this again lol.

Your all back up and running with root I take it then ?

Root checker says that my device was not correctly rooted.....ill look into i more, not sure why it did not take.....it seems like verizon makes it more difficult than any other carrier to root their devices

deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
The Odin factory image stuff returns everything back to 100% factory, so you shouldn't be rooted if that's all you did.
And since you didn't mention anything else, I suppose that's exactly what we should presume.
Normally when you use that Odin procedure, you are returning to square one - you need to root. Probably with kingo.

As btfb0 said.... root with KingoApp (dot) com.

drag&fly said:
As btfb0 said.... root with KingoApp (dot) com.
Click to expand...
Click to collapse
As you seem to have figured out, the more research you do, the more likely you are to succeed at stuff like this. At least you were able to recover it.
That being said, KingoApp is definitely the best/easiest way to root this phone.

[Q] Stuck while "fixing" my SGH-I337

Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.

What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk

seedeh said:
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I used ODIN to flash (What I'm very confident is) 4.3 Stock in the same manner I flashed the custom ROM.
I feel like that isn't specific enough for you though. I used Odin3 v3.09 first and then after several failures switched to Odin3 v1.85 as demonstrated in a few tutorials I've seen.

Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

seedeh said:
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Let me attempt this thread's instructions before I make more of a fool of myself. Thank you for the assistance so far. I really appreciate it.

No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk

seedeh said:
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Seedeh,
The errors still continued as usual even with the explicit following of the linked directions. It appears that during the process:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that the "NAND Write Start" step isn't really even trying to write before it fails.
Kies "Emergency Firmware Recovery" also yields no success due to "Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.", which does persist each time I attempt to do so.
If you have any more suggestions, I'd be more than happy to attempt them.
Thank you.

AmpGuitarChase said:
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
Click to expand...
Click to collapse
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.

John The Rhino said:
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
Click to expand...
Click to collapse
John The Rhino,
Thank you for you assistance. I will surely give credit where credit is due
I've attempted the XDA Full Odin Tar MK2 link's instructions three times on two separate computers (one w8 and one w7) to no avail. I've triple-checked the instructions, but my Odin always fails when attempting to Complete(Write).
NAND Write Start!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
Complete(Write) Operation Failed
All threads completed. (succeed 0 / failed 1)
Odin settings: Auto Reboot checked, F. Reset Time checked, PDA = I337MK2_Full_Odin_Tar.tar file, nothing else is checked.
Device: Dev mode activated, USB debugging active, this is all verified after a recovery-initiated factory reset, device is in download mode.
Computer(s): Samsung Android ADB Interface drivers are installed, Odin does show a yellow bar upon device connection. MicroUSB cable is the default one that came with the device, all USB ports have been tried with the same results.
I tried to be as thorough as possible with my setup. I'll see if my process is correct now just in case that will help.
[Fixing Device to Working Status w/o wifi/data permissions] Flashed AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 via Odin
Automatic Reboot via Odin
[Device is back to working status w/o data/wifi permissions (No reset has been done)]
Power off
Reboot in Recovery Mode (Volume up + Home + Power)
Wipe data/factory reset command
Wipe cache (just in case)
Reboot
[Phone is now factory reset 4.3 MK2 (WiFi/Data permissions denied still]
Enable developer options
Enable USB debugging and Screen Stay Awake during charging
Power off
Boot into download mode (Volume down + Home + Power)
Open Odin3 v1.85
Bar in Odin for COM Port is yellow
Auto reboot & F. Reset Time are both checked
Load I337MK2_Combined_Odin_Tar\I337MK2_Full_Odin_Tar.tar.md5 in PDA slot
Screenshot of Odin before "START" http://i.imgur.com/oXufVNQ.png
Odin START
Wait for Odin to check .md5 compatibility
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Back to where these points began
Apologies for the length, but again I wanted to be as thorough as possible. My WiFi still won't turn on due to permissions issues and Data is on, but no 3g/4g/LTE comes through.
Surely I'm just missing an essential step or two.
Can you offer any further advice on this matter?

Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5

The bootloader on MK2 and later is encrypted and without the key it will always fail. ODIN sees the ABOOT is locked and cannot flash the complete image. AT&T and Verizon have chosen this method to keep you off their cheaper competitors. I had to take my I337 to Best Buy Samsung experience to have it re flashed so that it would boot after a refused OTA from MDL and now it is a paperweight.

jd1639 said:
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
Click to expand...
Click to collapse
I don't think Odin is the issue as it flashes what I like to call "The cure-firmware" .md5 AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5) file just fine every time with no issues with Odin. Only when I try to flash that file, it works. I wish there was a way to tell what exactly is going wrong with the other files. I also can't seem to find where I located this file, but whatever it's doing works on my S4. I'd like to find either a 4.2.2 or 4.4.2 version of this stock OS that would work.
I'm beginning to wonder if it'd be more worthwhile to reroot, reset the flag binary counter, reset, and drive an hour and a half away to the closest AT&T store and see if they can fix my device. Does this sound like it may be my best course of action?
Again, thanks for all the help guys. I means a lot.

There is no way to downgrade to 4.2.2 from MK2. The bootloader is locked. Read the guide for MK2 it will help you.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Check your APN settings re enter according to correct settings posted on XDA.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.

AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Loki does not work with MF3 and up

Congrats!
Sent from my SAMSUNG-SGH-I337 using Tapatalk

AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!

John The Rhino said:
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
Click to expand...
Click to collapse
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase

AmpGuitarChase said:
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
Click to expand...
Click to collapse
You're welcome. I'm glad it all worked out for you. As they say in the construction business, measure twice, cut once. Well same here, except I'd recommend as do others to read thrice (3x) FLASH once. Then you'll rarely have issues. Enjoy.

i337 same issue as original post
i have done the same research as posted in this link and read exhaustively every means google XDA and all the other pages dealing with rooting and flashing my AT&T s4 i337. I have ended up in the same boat as this guy with:
Baseband version - I337UCUFNB1
Build Number - JSS15J.I337UCUEMK2
i have attempted Kingo Loki, Motochopper, Odin(4 or 5 versions) adb flash in Linux(2 builds) and Winblows 7. My original desire was to have this build
https://www.youtube.com/watch?v=mJLKX_QWSpc
which got my hopes up immensely, as having wasted days upon days several times over the course of the last 9 months rooting this i337. The guy in the vid says he was able to get UT up and running following guidance from XDA. I want to be able to flash a twrp-like dual boot recovery to my device maintaining Andy functionality using UT as a daily driver.
I have read, as reading saves phones, everything I can glean from the aforementioned posts and forms, researched this thing to death and neded up with a phone with the knox-? security message listed in the original post. I have no Idea where to go from here, but know you guys do, as like a myriad of others, I worship this site like a god.
Please help an old retired disabled veteran of most of the sandy wars in the past 25 years. All I have now are my devices which bring me some comfort to my days.
I really need your help, as I've tried seemingly all and have a semi-dead i337.
buxtor, aka, Chief

FRP Lock, unable to be flashed onto, and no SIM card

I seem to be stuck in a pickle, and at this rate this phone is seeing a swift throw to the curb by my friend who had given me this phone after getting his new one.
So, he had given me the phone and I was glad to finally move on from my issue-ridden HTC One M8, which was essentially on it's last legs. Even this low quality phone was more usable than the piece of junk I have. I got to work, and I installed the RebornROM, and I had went ahead to delete some of the bloatware.
However, it seems that my dumb self removed a Samsung app, and it seems to have triggered the FRP lock. I didn't think it was a big deal, seeing as how reverting back to stock was apparently most people's fix. I saw the Realterm fix, however I have 0 access to the home at all, and no SIM card. I downloaded the firmware, and I started up Odin to flash the stock firmware on. I was met with an error that I can only find scarce info on, and on YouTube it seems to be from Indian tech channels who are telling me to buy z3x-tools, and I'm not here to go ahead and try to do that.
To be more specific, my particular error is: SW REV. CHECK FAIL. DEVICE: 2. BINARY: 1. I could not find info on this error from xda, and I'm confused really. What's going on here?
As per promise to my friend, if I fail to find anything on this issue by tomorrow, the phone meets it's doom by the curb. After all, I'd really like to not use this janky phone anymore, as I'm quite tired of being unable to do nothing (to be more specific, it's using an older version of Cyanogen because I can't afford to use Sunshine to upgrade my bootloader and S-OFF, and everything on the phone is slowly stopping to work, in particular my camera app crashes instantly, flashlight does not work, a good chunk of the left side of my touch screen has stopped responding and I've had to use one-handed mode to text, along with flipping the screen, and it is a gigantic mess of issues.)
Please help out, xda. I've got nothing else I can really do for this phone, and here I was figuring this would just be an easy night of fixing the damn thing.

After some fiddling, I have now gotten an error on startup that isn't even the FRP lock anymore; it's a notice telling me to use the Smart Switch app's emergency backup. Attempted to install it, and after jumping through multiple hoops and several fixes, I am stumped at "Error 1152: Temporary files failed to copy" upon attempting to open it's installer.
Pushing on, I have received a new error. I instead am just attempting to install the AP file, and I now receive another error: KERNEL REV. CHECK FAIL. DEVICE:1, BINARY:0. Even more fun, because there's even less information on this one. In fact, I have only found others crying for help as I am. Regardless, I am now trying the other 3 files. BL outright fails to download, CP has replaced the screen I saw originally, instead putting the kernel error up top instead of the old FRP lock error I'd get. CSC seems to have put the FRP lock error back though. Afterward, I had a feeling that maybe BL will work now? I simply got my usual old SW REV error I mentioned already.
From here, I learned of an issue here. I think I need a different AP file. My phone is the MetroPCS version. The only reason I say this is because I realized the AP file caused the Smart Switch error, then CP -> CSC brought me back to the failure. The KERNEL REV issue occurs when trying to use my AP, with these logs:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?

Can you get into recovery and see which firmware you are on? Does your phone boot into the os? I've been through a lot of these issues. I just recently didn't have a sim, so no real term, and had the Google lock, but there is a way out of it.
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?[/QUOTE]

Drunkpilot said:
Can you get into recovery and see which firmware you are on? Does your phone boot into the os? I've been through a lot of these issues. I just recently didn't have a sim, so no real term, and had the Google lock, but there is a way out of it.
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?
Click to expand...
Click to collapse
[/QUOTE]
Cannot get into the OS, recovery, anything. All I can do is enter download mode. The FRP lock prevents anything else.

Cannot get into the OS, recovery, anything. All I can do is enter download mode. The FRP lock prevents anything else.[/QUOTE]
I ran into the same issue on another on5 when I had unlocked it for a friend, rooted it, then stupidly took off oem unlock and and rebooted to give back to him. I had to Odin the exact firmware I was running in order for it to work and fix the phone. I was running a t mobile older version ( an APF1) while trying to flash an (APL1) which wouldn't allow me to flash the AP partition in Odin. Once I flashed the full APF1 firmware with a factory reset, it booted normally, but unrooted, of course. Finding the correct firmware should hopefully fix your problem if your circumstances were like mine.

Check out these links. There are also other links and other threads to check out as well. Also check out sammobile.com as they have the the stock firmware for this phone.
whodisname said:
Have you tried this?
https://9to5google.com/2015/11/03/how-to-to-bypass-factory-reset-protection-samsung-phone-hack/
Sent from my SM-G550T1 using XDA-Developers mobile app
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
http://visihow.com/ADB_commands_to_bypass_Google_Account_Verification
Click to expand...
Click to collapse
You can also pm me for link to my drive account as I have both of the baseband versions of this firmware. Hope this helps
----edit-----
Here's another thread to check out as well. Make sure to use the latest version of odin as well. Oh and one more thing it you're gonna use any custom Rom on this device I suggest only using the one by @SuperStars as all the others are for the Indian variant and will cause sound yo not work at all on any other Varian even though they claim to work for the metro/tmobile variants. Superstars can be found here:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919

hatchet13rydin69 said:
Check out these links. There are also other links and other threads to check out as well. Also check out sammobile.com as they have the the stock firmware for this phone.
You can also pm me for link to my drive account as I have both of the baseband versions of this firmware. Hope this helps
----edit-----
Here's another thread to check out as well. Make sure to use the latest version of odin as well. Oh and one more thing it you're gonna use any custom Rom on this device I suggest only using the one by @SuperStars as all the others are for the Indian variant and will cause sound yo not work at all on any other Varian even though they claim to work for the metro/tmobile variants. Superstars can be found here:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
Click to expand...
Click to collapse
Unfortunately, all of these are not the solutions to my issues. I require the AP, CP, CSC, etc. versions of the firmware that can be sent through Odin. I have no access to my recovery or OS due to the lock already being on.

All the links I sent you were to the odin flashable .tar files which is all the files needed to get your phone up and going again. Most of the links will show the download as a zip file which you would extract after downloading then use odin to flash the extracted files to your phone

hatchet13rydin69 said:
All the links I sent you were to the odin flashable .tar files which is all the files needed to get your phone up and going again. Most of the links will show the download as a zip file which you would extract after downloading then use odin to flash the extracted files to your phone
Click to expand...
Click to collapse
Are you sure? I downloaded from every link and it seemed to be a standard recovery .zip file from each one; that or the link was expired, deleted, etc.

Hi, my device is Moto g4 plus. I have removed frp and flashed stock rom and flashed hw network. Got my network back but if i open camera, it says"camera is busy" even if I install third-party camera application also not working. Even flashlight also not working and missing option from quick pull option. Even if i install flashlight application also it says no flashlight detected. Plz help me with some solution for this issue...

Aashakmeeran said:
Hi, my device is Moto g4 plus. I have removed frp and flashed stock rom and flashed hw network. Got my network back but if i open camera, it says"camera is busy" even if I install third-party camera application also not working. Even flashlight also not working and missing option from quick pull option. Even if i install flashlight application also it says no flashlight detected. Plz help me with some solution for this issue...
Click to expand...
Click to collapse
wrong forum

Sorry to bump this, but I need a response to this now. I have no files to flash and my old phone just bricked, so...
Can anyone help me out? I need an Odin flash in order to do anything, in which nobody has provided me any reliable file. The last guy in the thread earlier from a couple months ago gave me broken links instead of anything, and then didn't respond after I made him aware of this. Someone please.

Drunkpilot said:
Can you get into recovery and see which firmware you are on? Does your phone boot into the os? I've been through a lot of these issues. I just recently didn't have a sim, so no real term, and had the Google lock, but there is a way out of it.
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?
Click to expand...
Click to collapse
[/QUOTE]
How did you get past the FRP lock?

F0rZ3r0 said:
Sorry to bump this, but I need a response to this now. I have no files to flash and my old phone just bricked, so...
Can anyone help me out? I need an Odin flash in order to do anything, in which nobody has provided me any reliable file. The last guy in the thread earlier from a couple months ago gave me broken links instead of anything, and then didn't respond after I made him aware of this. Someone please.
Click to expand...
Click to collapse
Hi there. Did you ever get an Odin link that worked? Is that the best/only way to unlock a Galaxy on5 Metro PCS?

davizzyus said:
Hi there. Did you ever get an Odin link that worked? Is that the best/only way to unlock a Galaxy on5 Metro PCS?
Click to expand...
Click to collapse
I have no clue. I never got a Odin link that worked. I need it to make my phone work, which is why I'm asking, since nobody seems to have what I'm asking for.

https://drive.google.com/file/d/0B7K3zIeKabE8aHo5NlVMLXpNdUU/view
Use the PL1 firmware. The most spread around one is the PF1, these should work. If not, I'm not sure what to say. Browse a bit more until you can find a solution. This fixed my phone finally.

F0rZ3r0 said:
https://drive.google.com/file/d/0B7K3zIeKabE8aHo5NlVMLXpNdUU/view
Use the PL1 firmware. The most spread around one is the PF1, these should work. If not, I'm not sure what to say. Browse a bit more until you can find a solution. This fixed my phone finally.
Click to expand...
Click to collapse
What kind of phone? How did you load the firmware? Did it bypass the Google lock?

davizzyus said:
What kind of phone? How did you load the firmware? Did it bypass the Google lock?
Click to expand...
Click to collapse
1. Umm... MetroPCS On5. :b
2. ODIN.
3. I didn't have a Google lock, I had a FRP lock triggered by custom binaries.

F0rZ3r0 said:
1. Umm... MetroPCS On5. :b
2. ODIN.
3. I didn't have a Google lock, I had a FRP lock triggered by custom binaries.
Click to expand...
Click to collapse
okay so i had this very same problem a few months back then got a new phone(on moto g5 plus now). the only way i could find to defeat FRP was flashing the "home csc" in odin. i HAD it but idk what happened must have deleted it when i got rid of the phone but im looking for it again also because i am fixing a friends On5. when i find it ill upload it!