Database Users

[Q] Galaxy S5 Bootloop

Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!

I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.

fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.

tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.

fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.

I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.

It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.

tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.

Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.

tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!

[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?

J510FN unable to flash firmware

I've had many phones in the past and never had a problem flashing stock and custom on any of them, but i've run into a issue with my sisters J5 2016 that i cant sort out.
As far as i understand she did an OTA update, but it failed halfway. The phone turned off, then wouldn't reboot......thats when she gave to me.
I first tried to access recovery mode, but this was not working.
If you just try to power up normally, then you get the samsung screen, but with the error message in corner.
View attachment 4231349
Only mode working is download mode, but this has an error in the first line that i have never seen before (it actually starts my worry that the internal memory is damaged somehow)
View attachment 4231345
I tried a firmware (single file in the AP box), but failed on pit.
So tried a version of firmware with the 4 separate files, but same error messages, so retried with the separate .pit file included in the flash.....still no joy, same error messages.
View attachment 4231346 View attachment 4231347
I have searched Internet and xda, but can not find this fail, so hoping someone might have a solution, or a way i can prove the internal memory is damaged (maybe theres another piece of software that i can use)

meerameer said:
I've had many phones in the past and never had a problem flashing stock and custom on any of them, but i've run into a issue with my sisters J5 2016 that i cant sort out.
As far as i understand she did an OTA update, but it failed halfway. The phone turned off, then wouldn't reboot......thats when she gave to me.
I first tried to access recovery mode, but this was not working.
If you just try to power up normally, then you get the samsung screen, but with the error message in corner.
Only mode working is download mode, but this has an error in the first line that i have never seen before (it actually starts my worry that the internal memory is damaged somehow)
I tried a firmware (single file in the AP box), but failed on pit.
So tried a version of firmware with the 4 separate files, but same error messages, so retried with the separate .pit file included in the flash.....still no joy, same error messages.
I have searched Internet and xda, but can not find this fail, so hoping someone might have a solution, or a way i can prove the internal memory is damaged (maybe theres another piece of software that i can use)
Click to expand...
Click to collapse
Use Smart Switch. It will automatically download and restore anything needed even if that means a pit file. Give it a try using thr Emergency Recovery option.

Amarius1 said:
Use Smart Switch. It will automatically download and restore anything needed even if that means a pit file. Give it a try using thr Emergency Recovery option.
Click to expand...
Click to collapse
Thank you for trying to help, that is much appreciate, but maybe i didn't make it clear.
The only working option is the Download mode, the Recovery mode doesn't work, so Smart Switch cant connect/see the phone

meerameer said:
Thank you for trying to help, that is much appreciate, but maybe i didn't make it clear.
The only working option is the Download mode, the Recovery mode doesn't work, so Smart Switch cant connect/see the phone
Click to expand...
Click to collapse
Doesn't matter. Just enter your s/n of the phone found behind the battery in the Smart Switch menu saying "Emergency Recovery"
It doesn't specifically need to recognise it or show as connected. Just make sure ur in download mode with cable in and enter the emergency data in the bokes so Smart Switch can force download the stock firmware for your phone

Amarius1 said:
Doesn't matter. Just enter your s/n of the phone found behind the battery in the Smart Switch menu saying "Emergency Recovery"
It doesn't specifically need to recognise it or show as connected. Just make sure ur in download mode with cable in and enter the emergency data in the bokes so Smart Switch can force download the stock firmware for your phone
Click to expand...
Click to collapse
Unfortuantly it was a fail.
Smart Switch downloaded the firmware, but could not install it and displayed a user friendly "Unknown Mode" message (i did check by plugging into odin without switching the phone off and odin showed it was in download mode).
The last message on phone screen reads "mmc: mmc_read fail" (this appeared when Switch came up with its fail message)
Just for clarity I tried all the above multiple times with different leads, and even different laptops and have upgraded my own phone without issues earlier .....so i am near admitting defeat with this J5 6
I do have to say again, thanks for suggesting and helping

meerameer said:
Unfortuantly it was a fail.
Smart Switch downloaded the firmware, but could not install it and displayed a user friendly "Unknown Mode" message (i did check by plugging into odin without switching the phone off and odin showed it was in download mode).
The last message on phone screen reads "mmc: mmc_read fail" (this appeared when Switch came up with its fail message)
Just for clarity I tried all the above multiple times with different leads, and even different laptops and have upgraded my own phone without issues earlier .....so i am near admitting defeat with this J5 6
I do have to say again, thanks for suggesting and helping
Click to expand...
Click to collapse
i dont know my answer will help or not. but i have met some older samsung phones with error in mmc. mmc is a hardware, so if you want to fix you have to change the mmc. maybe you can search for information about mmc on google to make sure.
by the way, why dont you go to service center? your waranty still 0x0

yea like mfmuam mentioned, take it to service centre and most likely they will change your motherboard. If your warranty is unexpired it will be totally free.

mfmuam said:
i dont know my answer will help or not. but i have met some older samsung phones with error in mmc. mmc is a hardware, so if you want to fix you have to change the mmc. maybe you can search for information about mmc on google to make sure.
by the way, why dont you go to service center? your waranty still 0x0
Click to expand...
Click to collapse
Unfortuantly her warrenty expired about 3 weeks ago (almost like the phone knew it had to break away that date ), but yes i have considered hitting ebay and getting her another board. Shes on holiday at moment, so will have to wait to see what she wants to do....... Thanks for advise though :good:

check your android security patch level ( im now in may 1 2017 region XID ) and than you download stok rom same like security patch level in your phone and than flash with odin put in pda.
---------- Post added at 11:44 PM ---------- Previous post was at 11:29 PM ----------
now i've 3 stok rom with different sec patch lvel,if i flash the first stokrom odin says fail like your ss,and then i flash the second stokrom odin says fail too,now im flash the third stokrom and tarraaa its work,because what?the third stokrom i have sec patch lvel in May 1 2017 same like im using my phone now.
pls correct if i wrong
check patch lvl - setting - about device - softwre info

Doni Artjoe said:
check patch lvl - setting - about device - softwre info
Click to expand...
Click to collapse
LOL, how could he check it when there is no system
installed on the phone and the phone cant boot up?
@meerameer
Hello,
please dont give up.
But also please dont be a fool and try repair change motherboard
by yourself.
You could try to re-flash with Heimdall program at Linux-System.
But before you can try to flash in Windows with Odin 3.12 program again.
download the very first firmware rom from samdownloads (they have 4-part rom with pit file)
make sure your battery is at 80% minimum
take out the battery
wait 30 sec
press and hold only power button for 10 sec
put back battery
start phone in download mode with no keys but only usb jig insert
start odin 3.12 and prepare all files but take CSC_(your-code) (do not use the csc_home!), take option with reboot, and also re-partition
connect phone with pc and start odin flash
Another idea would be to flash some custom recovery only and do full wipe
there, and then let Smart Switch emergency repair the phone.
You also have still a chance to get it repaired by the Samsung Service,
for maybe just a small fee. Just write them some short lovely email.

franticfreddy said:
LOL, how could he check it when there is no system
installed on the phone and the phone cant boot up?
@meerameer
Hello,
please dont give up.
But also please dont be a fool and try repair change motherboard
by yourself.
You could try to re-flash with Heimdall program at Linux-System.
But before you can try to flash in Windows with Odin 3.12 program again.
download the very first firmware rom from samdownloads (they have 4-part rom with pit file)
make sure your battery is at 80% minimum
take out the battery
wait 30 sec
press and hold only power button for 10 sec
put back battery
start phone in download mode with no keys but only usb jig insert
start odin 3.12 and prepare all files but take CSC_(your-code) (do not use the csc_home!), take option with reboot, and also re-partition
connect phone with pc and start odin flash
Another idea would be to flash some custom recovery only and do full wipe
there, and then let Smart Switch emergency repair the phone.
You also have still a chance to get it repaired by the Samsung Service,
for maybe just a small fee. Just write them some short lovely email.
Click to expand...
Click to collapse
Thank you Mr Frantic for the nice clear instructions :good:
I actually spend all day fixing hardware on phones and laptops, but thats hardly the rocket science of software like you developers get into. I have done flashing etc since the days of my beloved ACE.
I followed you so far down to 7, as i don't have a separate csc, apart from the csc_home file and for all my searching for a UK separated file firmware i had no luck, only got the combined one
I have tried what you suggested, but am going to try again following you to the letter :highfive:
PS Custom Recovery wouldn't go on, failed on odin at the .pit and theres no recovery (as far as i can tell) on the phone, just displays the J5 6 first screen, with the addition of the info text you get when in Download Mode.

@meerameer
Hello,
you could also try firmware for another country like germany, as the chance is good
that there it will be possible to choose english language in setup.
Maybe you can try this german firmware with csc_dbt.
But you need to be registered to samdownloads and firmware zip has password for encrypt
but its written on the download site (its mostly samdownloads.de)
The csc_home will not erase the internal storage since there is normally no pit file in it.
Because you need to re-pit and format the phone completely, you must use any
csc_(any country) but not csc_home.
Maybe thats why Odin fail for you so many times, because you never got any csc part
with the pit file in it?
You can check the csc part file if there is a pit file in it, you can open csc file with 7-zip.
EDIT:
Anyways, i have attach now the single pit-file for the j5-2016 european version.
So now you can try flash your 4 firmware in Odin with this additional pit file.
In Odin you got the menu for repit, where you can select the pit-file
manually (there is a warning that pit from csc will be used, but since you dont
have any csc file with pit in it, you can give a try.)
Else you still have the option to use SamFirm download program, where
you can download the newest firmware with option in binary nature (that means 4-parts)
and there will be csc file with the pit file already in it,
so you can flash like you already did.
I hope that helps..

franticfreddy said:
@meerameer
Hello,
you could also try firmware for another country like germany, as the chance is good
that there it will be possible to choose english language in setup.
Maybe you can try this german firmware with csc_dbt.
But you need to be registered to samdownloads and firmware zip has password for encrypt
but its written on the download site (its mostly samdownloads.de)
The csc_home will not erase the internal storage since there is normally no pit file in it.
Because you need to re-pit and format the phone completely, you must use any
csc_(any country) but not csc_home.
Maybe thats why Odin fail for you so many times, because you never got any csc part
with the pit file in it?
You can check the csc part file if there is a pit file in it, you can open csc file with 7-zip.
EDIT:
Anyways, i have attach now the single pit-file for the j5-2016 european version.
So now you can try flash your 4 firmware in Odin with this additional pit file.
In Odin you got the menu for repit, where you can select the pit-file
manually (there is a warning that pit from csc will be used, but since you dont
have any csc file with pit in it, you can give a try.)
Else you still have the option to use SamFirm download program, where
you can download the newest firmware with option in binary nature (that means 4-parts)
and there will be csc file with the pit file already in it,
so you can flash like you already did.
I hope that helps..
Click to expand...
Click to collapse
Seems I was having a dumb moment earlier. :silly:
Yes I checked before and the csc contained "J5XNLTE_EUR_OPEN_HIDDEN220M.pit". Thanks for the pit file also, I have checked on file size and they are exactly the same .
I have been questioning myself wondering if had right pit for my model, but screen and sticker (under battery) all say J510FN and all the .pit files i have found are all exactly same file size.
In total I've tried two 4 file firmwares, and 3 single file ones from different regions and release dates. All stop on that pit error before it even gets into the essence of the firmware.
Can you think of any software that can test the mmc , something that might give a bigger hint to whether its a hardware issue?

Hello,
well there is the option to test the mmc with special equipment for experts.
But its difficult and requires knowledge.
Did you try another Odin version?
Maybe Odin 3.09 or 3.10.7 can flash the firmware.
In older version of Odin, only check option for re-pit.
Do not make auto-reboot.
Only check re-partition and f.reset-time.
Do not use BL.
Only use AP+CP+CSC+pit file
When flash is finished, take out battery and put back in,
and restart manually into download mode and flash again the single firmware file
in AP.
I think you have flashed a different firmware version which is not suitable for your pit file
with the 220M addition.
It is very important to use the corresponding firmware files.
Maybe you only use the provided pit file for flash (do not select anything in BL, etc),
just select the pit file in re-pit menu.

franticfreddy said:
Hello,
well there is the option to test the mmc with special equipment for experts.
But its difficult and requires knowledge.
Did you try another Odin version?
Maybe Odin 3.09 or 3.10.7 can flash the firmware.
In older version of Odin, only check option for re-pit.
Do not make auto-reboot.
Only check re-partition and f.reset-time.
Do not use BL.
Only use AP+CP+CSC+pit file
When flash is finished, take out battery and put back in,
and restart manually into download mode and flash again the single firmware file
in AP.
I think you have flashed a different firmware version which is not suitable for your pit file
with the 220M addition.
It is very important to use the corresponding firmware files.
Maybe you only use the provided pit file for flash (do not select anything in BL, etc),
just select the pit file in re-pit menu.
Click to expand...
Click to collapse
Ok tried this, but still no joy.
I think you are certainly correct about what you were saying about the 220m pit file, as that one on the phone screen gives the message "ERROR There is no pit binary".
The pit file you posted gives the error "SECURE CHECK FAIL : PIT"
But the only time i have seen a SECURE CHECK FAIL message before is when i have accidentally in past tried putting completely wrong firmware on a phone , does that fit with what you know ?
ADDITIONAL INFO
My sister told me last night she had in fact taken it to her local indepentant phone shop to see if they could repair, they had no luck.
So i dont know what they did to it in their attempts. I do now have to wonder if they badly failed and now the phone is confused to what pit it should have, hence errors on software that should have fixed it
I've checked with the imei and the serial to make sure I'm defiantly looking for right files (J510FN), also my sister had from new and its never had a replacement board etc.......so im sort of hitting a brick wall.
Seems only option is to drive the 50 miles to the city, where i know there is an authentic Samsung repair store and hand over my life saving for them to look at it and tell me what we already know

Hello,
its really weird, its hard to find out what went wrong with your phone..
Maybe the guys at the generic repair center did the final brick of it.
As you said with the pit file i provided you got another kind of error.
I think there was some mix in bootloader and pit files which were used
at begin error stage 1.
I seen some kind similar problem when people was cross-mixing the 4-part
firmware files (they wanted use older bootloader but newer modem and system
or vice versa).
As there is still shown the samsung official binary but custom system, it is
possible the guys at generic repair center did use Odin and checked the
nand erase all option which is never, never, never a good idea.
Try to flash with this Odin v3.10.7 version
I strongly recommend you get your firmware file with
the SamFirm downloader ,
where you can search for your model SM-J510FN with countrycode BTU,
and check option to download in binary nature , so you will get the 4 parts.
The program requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
Here and here.
If you have the firmware there is no need to extra select the pit file for
flashing since its in csc_btu integrated. Just check option repartition, f.reset time.
These files also get checksum, then the secure fail *should* not happen...
If not fail then after finish flash take out battery, wait, put back,
goto recovery and do factory reset..
Im running out of ideas.. , anyways good Luck .

franticfreddy said:
Hello,
its really weird, its hard to find out what went wrong with your phone..
Maybe the guys at the generic repair center did the final brick of it.
As you said with the pit file i provided you got another kind of error.
I think there was some mix in bootloader and pit files which were used
at begin error stage 1.
I seen some kind similar problem when people was cross-mixing the 4-part
firmware files (they wanted use older bootloader but newer modem and system
or vice versa).
As there is still shown the samsung official binary but custom system, it is
possible the guys at generic repair center did use Odin and checked the
nand erase all option which is never, never, never a good idea.
Try to flash with this Odin v3.10.7 version
I strongly recommend you get your firmware file with
the SamFirm downloader ,
where you can search for your model SM-J510FN with countrycode BTU,
and check option to download in binary nature , so you will get the 4 parts.
The program requires .NET Framework 3.5 (Microsoft Visual C++ 2008 Redistributable Package (x86) and Microsoft Visual C++ 2010 Redistributable Package (x86) installed)
Hereand here.
If you have the firmware there is no need to extra select the pit file for
flashing since its in csc_btu integrated. Just check option repartition, f.reset time.
These files also get checksum, then the secure fail *should* not happen...
If not fail then after finish flash take out battery, wait, put back,
goto recovery and do factory reset..
Im running out of ideas.. , anyways good Luck .
Click to expand...
Click to collapse
OK, I have a couple of hours free now, so will try this.
Just like to say again, thanks for all your suggestions, you have been more than helpful :fingers-crossed:
UPDATE
Tried what you suggested, but still no joy.
Tomorrow i need to go near the city, so going to take a detour and take phone to the Samsung Shop. I'll update you on what they have to say about it .
Thanks again

Sad to hear it didnt work
I just was about to say, try what I said but also select the same separate pit file in the pit menu.
Im pretty sure the "right" mix of the right pit file and the corresponding firmware files could
help. But theres so many versions to try and its hard to find especially older firmwares..
Best regards.

franticfreddy said:
Sad to hear it didnt work
I just was about to say, try what I said but also select the same separate pit file in the pit menu.
Im pretty sure the "right" mix of the right pit file and the corresponding firmware files could
help. But theres so many versions to try and its hard to find especially older firmwares..
Best regards.
Click to expand...
Click to collapse
***Final Update***
I managed to get the logic board checked by Samsung and the emmc was corrupted. They wanted £124 to fix it.... Which I declined, as I can a replacement board on ebay for around. £60.
Chances are that the fault was caused by when my sister took it to a local generic repair shop, and might have been ok if she has gone to a more reputable repair shop.
So my note to all is research your repair stores when you have a fault, as the cheapest doesn't always mean the best.

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!

PIT file for S7 Edge Required

Hi all, I know somewhat about flashing but when it comes to PIT file I have absolutely no idea. Just read about what it is. Now the question, from where I would get my phone's PIT file. I cannot extract it from phone as only download screen is accessible on it. Details are phone are below,
S7 Edge - 32 GB
SM-G935F
Country : Pakistan
Current Binary: Samsung Official
System Status: Custom
FRP Lock: OFF
Warrant Void: 0 (0x0000)
RP SWREV: B:8 K:5 S:7
I remember that B:8 was actually 7 but I think I flashed (unsuccessful) next binary so it got updated.
I need the PIT file. Does it also holds internal storage capacity information ?

Can anyone help ?

Hy, Hope you have found the solution.
If you havent then here is a clue about PIT file. It is located in Firmware>csc*tar.md5>*.pit

Chaudhry69 said:
Hy, Hope you have found the solution.
If you havent then here is a clue about PIT file. It is located in Firmware>csc*tar.md5>*.pit
Click to expand...
Click to collapse
Nope, gave up flashing on that phone. It is still in my drawer, just sitting there

As a matter of fact pit (partition information table if memory serves me right) does hold the information for storage. But, I wonder how you ended up screwing it, it's like the most unbrickable thing. What is the error odin showing when you flash the firmware.
I would recommend xsg latest build from samfirm as it contains csc for Pakistan.

Chaudhry69 said:
As a matter of fact pit (partition information table if memory serves me right) does hold the information for storage. But, I wonder how you ended up screwing it, it's like the most unbrickable thing. What is the error odin showing when you flash the firmware.
I would recommend xsg latest build from samfirm as it contains csc for Pakistan.
Click to expand...
Click to collapse
Well I did nothing to start with. I tried to factory reset to phone from settings and ended up on boot loop. Have been trying flashing since then but of no use. Someone said its memory might be bad, dont know what other reason could be there. Strange if memory went bad of this phone, its too early for that. I have my HTC sensation which I started some time back and that was working fine .

It just starts flashing, progress bar starts and then file copy fails after a little while.

Chaudhry69 said:
As a matter of fact pit (partition information table if memory serves me right) does hold the information for storage. But, I wonder how you ended up screwing it, it's like the most unbrickable thing. What is the error odin showing when you flash the firmware.
I would recommend xsg latest build from samfirm as it contains csc for Pakistan.
Click to expand...
Click to collapse
message <ID:0/003> Complete(Write) operation failed. is the message i get while flashing. I have another thread https://forum.xda-developers.com/t/...ery-stock-rom-unrooted.4157363/#post-84324697 in which someone helped me but in the end i was still not able to flash. It starts copying, progress bar starts and then fails after a while. Can you please share the link you mnetioned on sam firmware xsg ? Maybe I can try one more time.

lazers378 said:
message <ID:0/003> Complete(Write) operation failed. is the message i get while flashing. I have another thread https://forum.xda-developers.com/t/...ery-stock-rom-unrooted.4157363/#post-84324697 in which someone helped me but in the end i was still not able to flash. It starts copying, progress bar starts and then fails after a while. Can you please share the link you mnetioned on sam firmware xsg ? Maybe I can try one more time.
Click to expand...
Click to collapse
Well, as the nice folks over there said, region doesn't matter. It is true somewhat if you are not after some very specefic feature like vowifi, volte etc. For your peace of mind, here is a link to XSG Firmware, pick the latest. How to flash;
Download the firmware greater than or equal to your current bl, k and S ver.
Extract the zip.
Extract pit from csc.
Deselect auto reboot. Select all other options.
Attach pit and flash all except home_csc.
Why it happened?
Either the flash is damaged, Can be Million reasons other than age.
OR Some how bootloader or modem is messed up.
Latter will be fixed by an odin flash. If nothing works give twrp a try. Knox will trip but better than having a dead phone. If twrp works, install stock debloated rom and enjoy the company of a legendary deveice while it lasts.