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] Galaxy s5 sm-900A apperaing as sm-900F

Hello, well I will go straight to my question
I bought a galaxy s5 ( the 900F) module from CHINA and it is original. I checked everything and it was all OK ! In the "about device" section it shows my phone's model number as "SM-900F" . For some reason private mode did not work at all ! So I thought why not trying to install another rom, because the "Samsung Chinese keyboard" always bothered me for some reason even thou I did not use it . Anyway, I downloaded this rom "G900FXXU1ANE2_G900FOXE1ANE2_SER" from sammobile .As you can see it's for the 900F edition so I tried installing it using odin 3.09 but it always failed , so after paying good attention to the download mode screen I saw IT ! "PRODUCT NAME - SM-G900A"
and when I tried to install this rom using odin I got this message appearing in my screen under the UDC START
SECURE CHECK FAIL : aboot
So, what to do ? I figured out that I bought the at&t module , so what should I do ? I can not return the phone
How can I install an original rom ? and If I do that will my phone be "locked" ? You know because it's an at&t module after all .
How can I unlock it to install other roms ?
And by the way, for some reason root checker shows that my phone is "rooted" , even though everything is "official
Screenshots from my phone included .
Oooh and guys, sorry for the bad explanation , I do not know how to explain in other way :laugh:
Log from odin :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANE2_G900FOXE1ANE2_G900FXXU1ANE2_HOME.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> SingleDownload.
<ID:0/003> aboot.mbn
<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)

Bakr87 said:
to the download mode screen I saw IT ! "PRODUCT NAME - SM-G900A"
Click to expand...
Click to collapse
You said that the download screen reported an ATT model number, but you didn't include a screenshot or photo of that. The screenshots that you did include from the settings menu strongly suggest otherwise.
The 900A has a locked bootloader and it would be challenging to change an ATT baseband. Your screenshots show a 900F baseband. What model number is shown on the label under the battery?
All of the evidence so far indicates that you have a 900F and commonplace troubles using Odin. Odin is fussy with USB; try a different cable and USB port. Or a different PC if necessary. Disable your anti virus, malware, firewall, et cerera.
As to private mode, what is your Knox status as reported on the download page?
.

fffft said:
You said that the download screen reported an ATT model number, but you didn't include a screenshot or photo of that. The screenshots that you did include from the settings menu strongly suggest otherwise.
The 900A has a locked bootloader and it would be challenging to change an ATT baseband. Your screenshots show a 900F baseband. What model number is shown on the label under the battery?
All of the evidence so far indicates that you have a 900F and commonplace troubles using Odin. Odin is fussy with USB; try a different cable and USB port. Or a different PC if necessary. Disable your anti virus, malware, firewall, et cerera.
As to private mode, what is your Knox status as reported on the download page?
.
Click to expand...
Click to collapse
fffft said:
You said that the download screen reported an ATT model number, but you didn't include a screenshot or photo of that. The screenshots that you did include from the settings menu strongly suggest otherwise.
The 900A has a locked bootloader and it would be challenging to change an ATT baseband. Your screenshots show a 900F baseband. What model number is shown on the label under the battery?
All of the evidence so far indicates that you have a 900F and commonplace troubles using Odin. Odin is fussy with USB; try a different cable and USB port. Or a different PC if necessary. Disable your anti virus, malware, firewall, et cerera.
As to private mode, what is your Knox status as reported on the download page?
.
Click to expand...
Click to collapse
Well, I included screen shots BEFORE trying with ODIN and AFTER trying with ODIN to install the rom.
I tried using other USB port + other USB cable but I get the same result.
and another screen shot is for the back of my telephone under the battery
And by the I checked my IMEI code ( using this code : *#06# ) on this site : imei.info
and the result is the following : G900A Galaxy S5 (better if you check it yourself on the site )
SCREENSHOTS are included in a compressed file in the attachments

Thank you for the additional details.
It is a novel situation. But the evidence heavily argues that your phone is actually a 900F.
The 900A has a locked bootloader, so it's very implausible that someone would have been able to change that to the current 900F bootloader as reflected in the baseband. The label and frankly everything except the download screen suggests that it is an F variant. The 900A reported in the download screen appears to be spurious and is no doubt reflective of some small anomaly in the IMEI assignment scheme or some such causing incorrect information on that screen..
The difficulties with Odin do not suggest that you have a 900A. Odin is well known for being fussy and temperamental. Try flashing the exact same stock version of firmware that the phone currently has just to confirm that Odin works. Cables are a big issue and people sometimes have to try half a dozen different cables before seeing success. Move your computer to a different location or borrow a different computer if necessary.
You will succeed if you are persistent. Odin is simply stubborn.
.

fffft said:
Thank you for the additional details.
It is a novel situation. But the evidence heavily argues that your phone is actually a 900F.
The 900A has a locked bootloader, so it's very implausible that someone would have been able to change that to the current 900F bootloader as reflected in the baseband. The label and frankly everything except the download screen suggests that it is an F variant. The 900A reported in the download screen appears to be spurious and is no doubt reflective of some small anomaly in the IMEI assignment scheme or some such causing incorrect information on that screen..
The difficulties with Odin do not suggest that you have a 900A. Odin is well known for being fussy and temperamental. Try flashing the exact same stock version of firmware that the phone currently has just to confirm that Odin works. Cables are a big issue and people sometimes have to try half a dozen different cables before seeing success. Move your computer to a different location or borrow a different computer if necessary.
You will succeed if you are persistent. Odin is simply stubborn.
.
Click to expand...
Click to collapse
Thanks for replaying =)
Well, I will try to do so tomorrow , hope everything will go well :fingers-crossed: I will write to tell you the results .

fffft said:
Thank you for the additional details.
It is a novel situation. But the evidence heavily argues that your phone is actually a 900F.
The 900A has a locked bootloader, so it's very implausible that someone would have been able to change that to the current 900F bootloader as reflected in the baseband. The label and frankly everything except the download screen suggests that it is an F variant. The 900A reported in the download screen appears to be spurious and is no doubt reflective of some small anomaly in the IMEI assignment scheme or some such causing incorrect information on that screen..
The difficulties with Odin do not suggest that you have a 900A. Odin is well known for being fussy and temperamental. Try flashing the exact same stock version of firmware that the phone currently has just to confirm that Odin works. Cables are a big issue and people sometimes have to try half a dozen different cables before seeing success. Move your computer to a different location or borrow a different computer if necessary.
You will succeed if you are persistent. Odin is simply stubborn.
.
Click to expand...
Click to collapse
Well , first of all - sorry for the very late answer
Second - I tries other version of ODIN, other STOCK roms, other cables ,but no use. I get the same error. I am almost sute that I have the G900A that had been modified somehow by someone to make it look like a G900F

Bakr87 said:
Well , first of all - sorry for the very late answer
Second - I tries other version of ODIN, other STOCK roms, other cables ,but no use. I get the same error. I am almost sute that I have the G900A that had been modified somehow by someone to make it look like a G900F
Click to expand...
Click to collapse
One thing that should probably be cleared up: is your vendor a carrier or some back street 2x3 sqm phone booth type store? Is the vendor officially authorised by Samsung/AT&T/your carrier? It might have happened that you bought some weird clone, or just a G900A or F that someone modified?
You also mentioned that the phone is "rooted", which suggests this theory. See if you can get a look at the system files via root browser and if you can make changes to them.
What could also have happened, your seller might have reselled a broken phone that someone brought back to the shop.
If you could provide more infos on where you bought your phone, that might help us solve the case.

guetzli32 said:
One thing that should probably be cleared up: is your vendor a carrier or some back street 2x3 sqm phone booth type store? Is the vendor officially authorised by Samsung/AT&T/your carrier? It might have happened that you bought some weird clone, or just a G900A or F that someone modified?
You also mentioned that the phone is "rooted", which suggests this theory. See if you can get a look at the system files via root browser and if you can make changes to them.
What could also have happened, your seller might have reselled a broken phone that someone brought back to the shop.
If you could provide more infos on where you bought your phone, that might help us solve the case.
Click to expand...
Click to collapse
The sad answer is yes ! I installed root explorer and I can see system files and other prove is that I installed another root checking application "Simple root checker" and here is a screenshot to what I found .
So what can be done ? returning it is not an option =(
Well I am okay as long it's an original s5

Bakr87 said:
The sad answer is yes ! I installed root explorer and I can see system files and other prove is that I installed another root checking application "Simple root checker" and here is a screenshot to what I found .
So what can be done ? returning it is not an option =(
Well I am okay as long it's an original s5
Click to expand...
Click to collapse
Okay, I am now almost sure as of what happened.
Someone rooted your phone, went into /system/build.prop and changed the line ro.product.model from the AT&T(SM-G900A) to the international one(SM-G900F). Also, the Knox counter is still on 0x0, which can only be kept like that via towelroot. In addition, towelroot used to be one of the rare ways to root an AT&T or Verizon S5 model.
I am 99.9% sure your phone is actually an AT&T one.
This also explains why you can't flash anything: the AT&T bootloader is locked, which prevents you from flashing.
So, if you wanna get your SM-G900A back, just change the build prop line mentioned above back to SM-G900A.
Hope this cleared things up

guetzli32 said:
Okay, I am now almost sure as of what happened.
Someone rooted your phone, went into /system/build.prop and changed the line ro.product.model from the AT&T(SM-G900A) to the international one(SM-G900F). Also, the Knox counter is still on 0x0, which can only be kept like that via towelroot. In addition, towelroot used to be one of the rare ways to root an AT&T or Verizon S5 model.
I am 99.9% sure your phone is actually an AT&T one.
This also explains why you can't flash anything: the AT&T bootloader is locked, which prevents you from flashing.
So, if you wanna get your SM-G900A back, just change the build prop line mentioned above back to SM-G900A.
Hope this cleared things up
Click to expand...
Click to collapse
Thanks for helping me all the way =)
I have a few more questions to ask
How can I return the original firmware ? do I have to use the buil.prop line or can I just install the AT&T firmware using ODIN ? and how to do that if I need to change the build prop line ? And by installing the AT&T firmware, will I be getting a locked phone ? I mean a sim-locked telephone

Bakr87 said:
Thanks for helping me all the way =)
I have a few more questions to ask
How can I return the original firmware ? do I have to use the buil.prop line or can I just install the AT&T firmware using ODIN ? and how to do that if I need to change the build prop line ? And by installing the AT&T firmware, will I be getting a locked phone ? I mean a sim-locked telephone
Click to expand...
Click to collapse
You are on the stock firmware. You only have to change the build.prop line, and then it's completely stock AT&T firmware. And no, you won't get a sim locked phone

guetzli32 said:
You are on the stock firmware. You only have to change the build.prop line, and then it's completely stock AT&T firmware. And no, you won't get a sim locked phone
Click to expand...
Click to collapse
Thanks =)
I think I am going to wait and see if I need to change the the build.prop line ! and what application to use ?
( If I wont be getting the the next android update then it's a must do )
ooh, by the way, how can I remove the root ?

Bakr87 said:
Thanks =)
I think I am going to wait and see if I need to change the the build.prop line ! and what application to use ?
( If I wont be getting the the next android update then it's a must do )
ooh, by the way, how can I remove the root ?
Click to expand...
Click to collapse
I recommend "Root Explorer" to edit the build.prop. You can unroot by installing an app called "SuperSU" from Play store, in the settings of that app there is an option to unroot. You should change the build.prop before you unroot, it won't work afterwards

guetzli32 said:
I recommend "Root Explorer" to edit the build.prop. You can unroot by installing an app called "SuperSU" from Play store, in the settings of that app there is an option to unroot. You should change the build.prop before you unroot, it won't work afterwards
Click to expand...
Click to collapse
Okay I got that =)
Could you upload the build.prop file for the G900A ? I haven't been lucky finding it =(
I think I am going to install the original build prop and then unroot the phone like you said )
And can I just install the stock at&t firmware ( from sammobile) without risking getting a sim locked phone ?

ART?
Are you runing dalvik or ART? Private mode doesn't seem to work under ART!

DylanE1 said:
Are you runing dalvik or ART? Private mode doesn't seem to work under ART!
Click to expand...
Click to collapse
This question doesn't belong here!
---------- Post added at 07:56 AM ---------- Previous post was at 07:51 AM ----------
Bakr87 said:
Okay I got that =)
Could you upload the build.prop file for the G900A ? I haven't been lucky finding it =(
I think I am going to install the original build prop and then unroot the phone like you said )
And can I just install the stock at&t firmware ( from sammobile) without risking getting a sim locked phone ?
Click to expand...
Click to collapse
I can't upload you the file, since I have the G900F and when you can't find it, I can't either(probably).
Changing the one line should be enough. I repeat, ro.product.model is what you wanna change.
I don't know if that'll SIM lock you phone, since I don't have those problems(Swiss Carriers don't SIM lock phones maybe someone else with an AT&T model can tell you that...?

guetzli32 said:
This question doesn't belong here!
Click to expand...
Click to collapse
I bought a galaxy s5 ( the 900F) module from CHINA and it is original. I checked everything and it was all OK ! In the "about device" section it shows my phone's model number as "SM-900F" . For some reason private mode did not work at all !
seems that it does too me, aside from his other issues..

DylanE1 said:
I bought a galaxy s5 ( the 900F) module from CHINA and it is original. I checked everything and it was all OK ! In the "about device" section it shows my phone's model number as "SM-900F" . For some reason private mode did not work at all !
seems that it does too me, aside from his other issues..
Click to expand...
Click to collapse
well, you didn't say that stuff in your first post so i was assuming you were in the wrong thread.
what exactly happens when you want to start up Private mode?

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!

Odin "complete(write) operation failed" when rooting

I'm trying to use PartCyborgRom on my Galaxy S8 SM-G950U USA version. When I first clicked start in Odin, it said, "complete(write) operation failed". Following that I get a blue screen that says something along the lines of update failed. If I flash part 2 it will let me go back into download mode but the cycle repeats. So far I have used two different computers (with the Samsung drivers installed), at least 2 USB 2 and 3 ports (I know it says not to use 3 but I wanted to see if anything changed), and 2 different cables. I've seen other threads where people say to keep trying while leaving Odin open, etc but none of that has worked either. Does anyone know what the cause could be?

QuantumPie said:
I'm trying to use PartCyborgRom on my Galaxy S8 SM-G950U USA version. When I first clicked start in Odin, it said, "complete(write) operation failed". Following that I get a blue screen that says something along the lines of update failed. If I flash part 2 it will let me go back into download mode but the cycle repeats. So far I have used two different computers (with the Samsung drivers installed), at least 2 USB 2 and 3 ports (I know it says not to use 3 but I wanted to see if anything changed), and 2 different cables. I've seen other threads where people say to keep trying while leaving Odin open, etc but none of that has worked either. Does anyone know what the cause could be?
Click to expand...
Click to collapse
You need to read a bit better and you would see that most of the errors you received are normal
What bootloader revision is your device on. 5th number from end is bootloader revision
Try to read a bit better and search the thread. All is answered there. There will be failures but some are normal and needed for this root method to work

TheMadScientist said:
You need to read a bit better and you would see that most of the errors you received are normal
What bootloader revision is your device on. 5th number from end is bootloader revision
Try to read a bit better and search the thread. All is answered there. There will be failures but some are normal and needed for this root method to work
Click to expand...
Click to collapse
Just realized I could search for keywords in a thread a few minutes ago.
I'm no longer sure but I'm guessing it was past 2. If that is the case, is there any way I can root?

QuantumPie said:
Just realized I could search for keywords in a thread a few minutes ago.
I'm no longer sure but I'm guessing it was past 2. If that is the case, is there any way I can root?
Click to expand...
Click to collapse
I didn't mean to sound like a arse. This root method can be tricky is why I say read read read. A lot of people miss the section of upload mode errors and device software unauthorized screen
What is the current firmware on the device.
If you don't see like a secure check fail. Binary or something you should be good. Which would be displayed in download mode screen. And Odin would fail right off

I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.

TheMadScientist said:
I didn't mean to sound like a arse. This root method can be tricky is why I say read read read. A lot of people miss the section of upload mode errors and device software unauthorized screen
What is the current firmware on the device.
If you don't see like a secure check fail. Binary or something you should be good. Which would be displayed in download mode screen. And Odin would fail right off
Click to expand...
Click to collapse
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
(Sorry for double posting. I wasn't sure if you get a notification without me replying to you)

QuantumPie said:
I'm now back to stock with a v5 bootloader. I'm trying to follow this method but I am getting a "Re-Partition operation failed" error even though I don't have that option ticked. Do I need it ticked or have to use the pit file? I can't get a clear sense of what the pit file does from my googling.
(Sorry for double posting. I wasn't sure if you get a notification without me replying to you)
Click to expand...
Click to collapse
V5 is unrootsble and no downgrade. You might as well find a new device if you need root

bricked sm-t580

i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
could not do normal boot invalid kernel length
Click to expand...
Click to collapse
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....

Have you tried flashing TWRP using ODIN? (AP Slot)

i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options

ilovebytes said:
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
Click to expand...
Click to collapse
Wouldn't it simply fail if OEM unlocking was disabled? I don't know honestly. I'd try it if no other solutions come up.

ilovebytes said:
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Click to expand...
Click to collapse
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.

of course i tried to get into receovery mode but the problem is i can't - when i do home, vol up and power absolutely nothing happens, i only get into download mode
edit: i believe FRP is the Problem this prevents odin from writing the files to the tablet - as it allways times out with :
Complete(Write) operation failed.
Click to expand...
Click to collapse
what i do not really understand is why FRP does not let odin flash an original samsung firmware ?

[QUOTE what i do not really understand is why FRP does not let odin flash an original samsung firmware ?[/QUOTE]
This sounds more like a binary issue. I have reason to believe you are what's called an FRP Binary Lock. Recovery is usually inaccessable or re-routed and you cannot "seem" to use Odin3 but in fact you can. This issue you apparently are having sounds oddly like some issues I've had on these devices and is often a result of bad Rooting or invalid firmware being installed. This overloads the binaries and puts the device in a locked mode with symptoms of an inaccessible Recovery a difficult to use Odin3 or a bootloop. Most of the time I hear of a notification somewhere of an FRP lock. If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661

Casper Young said:
If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....

ilovebytes said:
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
Click to expand...
Click to collapse
The situation I was suspecting is a "Custom Binaries are Blocked by FRP Lock" to which you would have seen a notification of it in one of 4 ways. Your situation is somewhat similar because you cannot access Recovey and although Download Mode is accessable it appears useless. Your device is not Bricked. A bricked device is unusable in any way and these days most devices can be restored.
You do seem to be having some difficulties that are usually common with binary issues. You can in fact use Odin3 but how is the question. Usually one can flash in the Stock firmware and that returns the device to normal. When it becomes impossible to flash in stock firmware or anything else it seems, to my experiance has always been a Binary issue. I will provide a link to the 4File Official firmware. And instructions for you to properly use it for your needs.
SM-T580 Official Stock Firmware 4Files
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
I'll assume you know something about using Odin3. Unzip the file to your desktop. There are 4 files but you'll only use 3 of them. You can use the patched version of Odin3.13B or you can use Odin3.14. Place the files in their respective places. BL, and AP are easy enough to see where they go. Now there is a file labeled CSC and one labeled HOME CSC. You will only use one of them. The CSC file returns your app data to factory settings (it erases everything). The Home CSC file keeps the app data. So it's your choice which one you choose. These are Official Firmware Files so you should be able to flash them in. Should that not work for you my most likely answer would be that your binaries are the issue and that is why you can't as of yet use Odin sucessfully. Does Odin even try to initiate a flash then stalls or does it do nothing altogether?
There are two different Binary files for the SM-T580 that I have. I would suggest using the Binary 4 FRP first. f I recall correctly the Odin3.13B patched version was made for this. Place the file in the AP section and try flashing it. You should get a few gears on the screen turning if it applied, or maybe not. If that fails use the U4 Binary Unlock file. It is only after you flash in the binary files that you can then install the Stock Firmware. It is the overloaded binaries that prevent the use of Odin as you may be experiancing. I am also including the Knox cleaner in case you need to reset it.
SM-T580 Binary files:
Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
U4 Binaries. This is two files. Flash one at a time using the AP section. They are labeled 1rst or 2nd
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
Knox Cleaner: Also flashed in using the AP section of Odin3
https://drive.google.com/open?id=1EolYe9auY9jslYSpSgHoon_YB00D2noV
Good Luck and let me know if this helps or not.

lewmur said:
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
Click to expand...
Click to collapse
Only if they could get into Recovery they may be able to reset it.
I have never once needed to go to Recovery to do "anything" before using Odin3 to flash.
The only time I've had to go there (repetedly) and reset was when trying to get past FRP Google Account Protection. Sometimes it takes out the page I want to get to and I need to reset it to get to it again. This is "not" always neccesary before flashing a ROM which rewrites the device programing.

sorry for double post

@Casper Young
thanks for your help so far, i am gonna try your suggestions on weekend when i have a bit more spare time - hope i can get the tab running again