Hello,
I live in the Netherlands the 7.7 is nowhere to be found here. So I've imported the 7.7 from Belgium but it seems that the CSC was set to LUX.
After looking around on XDA I managed to change the CSC
(need root, root explorer. Edit "/system/csc/sales_code.dat")
And also the customer.xml (on the same directory) has information about carriers/providers and Samsung bookmarks locked to Luxemburg.
Now I have changed the CSC, I can't update with Kies. It's saying that the device is not supported trough Kies.
How do I fix this?
Zero Masamune said:
Hello,
I live in the Netherlands the 7.7 is nowhere to be found here. So I've imported the 7.7 from Belgium but it seems that the CSC was set to LUX.
After looking around on XDA I managed to change the CSC
(need root, root explorer. Edit "/system/csc/sales_code.dat")
And also the customer.xml (on the same directory) has information about carriers/providers and Samsung bookmarks locked to Luxemburg.
Now I have changed the CSC, I can't update with Kies. It's saying that the device is not supported trough Kies.
How do I fix this?
Click to expand...
Click to collapse
1st and basic thing: If u root your device you will not be able to get OTA/KIES updates... well now you know it anyway cause you did it Well no problem there is a way to go back to Stock
OK 2nd maybe you read this little History
If you read it you know now however you dont need any root to change CSC, if you got the right Firmware for your 7.7 Device (GT-6800 or GT6810).
Actually i can say this for SGS II I9100 and SGT 7.7 GT-6800 & GT6810!
How to install via Odin the right Firmware -->PUSH HERE [email protected][ROM&GUIDE] Official Firmwares SGT 7.7 P6800 + P6810 Download<--
Click to expand...
Click to collapse
As i see your from NL. Actually i cant offer you Firmware with NL CSC
Netherlands
-->BEN, KPN, MMO, ONL, QIC, TFT, TNL, VDF, VDP, XEN
Click to expand...
Click to collapse
I can show you now 2 ways how u manage this.
You wait untill a Firmware comes out for your Country.
or
You install the P6800XXLA3 wich CSC is ATO(Austria) it contains Multilanguage(inclueded NL) + Kies updates work again ;D
Cheers
- people have had upates to their rooted tabs via kies.
after update you lose root & then re-root.
you get updates if you dont change "version" from what your kernel is running.
look out for multi-csc roms, i think you can change the csc through the phone system settings.
ezynow said:
- people have had upates to their rooted tabs via kies.
after update you lose root & then re-root.
you get updates if you dont change "version" from what your kernel is running.
look out for multi-csc roms, i think you can change the csc through the phone system settings.
Click to expand...
Click to collapse
True mate i know that too ^^
but i tried it to change over the preconfigcode *#272*IMEI# but it didnt work ... maybe cause we got honeycomb? .. i dont know
On my sgs2 it works yes ^^ but there is GB
xenix96 said:
True mate i know that too ^^
but i tried it to change over the preconfigcode *#272*IMEI# but it didnt work ... maybe cause we got honeycomb? .. i dont know
On my sgs2 it works yes ^^ but there is GB
Click to expand...
Click to collapse
i need to change mine too !
ezynow said:
i need to change mine too !
Click to expand...
Click to collapse
Well i managed to change my CSC if you did read what i post u would know how u can change it too
I installed the Austrian ROM (P6800XXLA3), but my CSC did not change when I went into stock recovery. It was still trying to put TYG (Hong Kong) CSC back, which it no longer found in the CSC folder. Then I used the following tool to change the CSC to ATO:
https://market.android.com/details?id=com.manniakk.cscselector&hl=en
Warning though, this clears your tab, ie. you need to set it up again and reinstall apps (recommend backing up with titanium backup). Root is not required, but if you were rooted, you need to re-apply root again.
But it works and Kies recognises the tab for future updates.
If you change the CSC to other than ATO in the list (the ROM has several), Kies will not recognise the tab for future updates.
Can't Modify CSC on Chinese P6800
morkli said:
I installed the Austrian ROM (P6800XXLA3), but my CSC did not change when I went into stock recovery. It was still trying to put TYG (Hong Kong) CSC back, which it no longer found in the CSC folder. Then I used the following tool to change the CSC to ATO:
https://market.android.com/details?id=com.manniakk.cscselector&hl=en
Warning though, this clears your tab, ie. you need to set it up again and reinstall apps (recommend backing up with titanium backup). Root is not required, but if you were rooted, you need to re-apply root again.
But it works and Kies recognises the tab for future updates.
If you change the CSC to other than ATO in the list (the ROM has several), Kies will not recognise the tab for future updates.
Click to expand...
Click to collapse
I got a Chinese P6800 were i attempted to set CSC with SGS Toolbox, but when I go under CSC Selection, I do not get any choises, only two lines:
Using workdir: /sdcard/SGSToolbox/work_20120215_2152559
Copied imei file...
kevinsfar said:
I got a Chinese P6800 were i attempted to set CSC with SGS Toolbox, but when I go under CSC Selection, I do not get any choises, only two lines:
Using workdir: /sdcard/SGSToolbox/work_20120215_2152559
Copied imei file...
Click to expand...
Click to collapse
I've not used the SGS Toolbox, but using the app I linked above worked for me. I'm now using the Portugese (TPH) stock ROM and was able to change the CSC to TPH. Kies now recognises the tab properly for future firmware update. There is not much point changing the CSC unless you've installed a new stock ROM using Odin (see official firmware thread in the development section). Warning, changing the CSC wipes your tab, so backup beforehand (to external sdcard or your PC).
morkli said:
I've not used the SGS Toolbox, but using the app I linked above worked for me. I'm now using the Portugese (TPH) stock ROM and was able to change the CSC to TPH. Kies now recognises the tab properly for future firmware update. There is not much point changing the CSC unless you've installed a new stock ROM using Odin (see official firmware thread in the development section). Warning, changing the CSC wipes your tab, so backup beforehand (to external sdcard or your PC).
Click to expand...
Click to collapse
The reason why I would like to change CSC is to get non-chinese firmware on my p6800, the chinese version does not have google account or android market, so I can not install the CSC tool from https://market.android.com/details?id=com.manniakk.cscselector&hl=en
kevinsfar said:
The reason why I would like to change CSC is to get non-chinese firmware on my p6800, the chinese version does not have google account or android market, so I can not install the CSC tool from https://market.android.com/details?id=com.manniakk.cscselector&hl=en
Click to expand...
Click to collapse
Okay, I understand. I've attached the CSC tool for you below.
View attachment com.manniakk.cscselector-1.apk
I had to reflash twice in order to get a different CSC on my device. Both times I wiped the device in recovery mode. I didn't use any 3rd party tools apart from Odin.
morkli said:
Okay, I understand. I've attached the CSC tool for you below.
View attachment 907495
Click to expand...
Click to collapse
Thank you, I do appreciate it when people are helping out.
Now I got the tool running ... but it seems that I only are able to choose between 2 different CSC codes , I can onlychoose between CHN and CHZ
I now have Android Market from a .apk, but is still missing Google account, and so far all attempts of reflashing with non-chinese firmware after the instructions on http://forum.xda-developers.com/showthread.php?t=1469635 has failed.
It seems that this chinese variant does not play along very well, but I am sure some day some clever xda person will come up with the right solution for me, so I'll keep on reading
What error do you get when attempting to flash firmware using Odin?
morkli said:
What error do you get when attempting to flash firmware using Odin?
Click to expand...
Click to collapse
First I use task manager to kill any kies* processes
Then set the P6800 to odin mode, select the file I want to flash and start the same way as I successfully have used for P1000 & P7510.
But all odin does is :
<ID:0/023> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6800OXALA3_P6800XXLA3_P6800XXLA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/023> Odin v.3 engine (ID:23)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> boot.bin
<ID:0/023> NAND Write Start!!
<ID:0/023>
<ID:0/023> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)when I try to flash P6800OXALA3_P6800XXLA3_P6800XXLA3_HOME.tar.md5
kevinsfar said:
The reason why I would like to change CSC is to get non-chinese firmware on my p6800, the chinese version does not have google account or android market, so I can not install the CSC tool from https://market.android.com/details?id=com.manniakk.cscselector&hl=en
Click to expand...
Click to collapse
Dood, just push vending.apk and google accounts, maybe google services framework. I did it with my (China) P6800 and I have full market, google account setup, the works.
Chinese p6800 change ROM
kevinsfar said:
Thank you, I do appreciate it when people are helping out.
Now I got the tool running ... but it seems that I only are able to choose between 2 different CSC codes , I can onlychoose between CHN and CHZ
I now have Android Market from a .apk, but is still missing Google account, and so far all attempts of reflashing with non-chinese firmware after the instructions on http://forum.xda-developers.com/showthread.php?t=1469635 has failed.
It seems that this chinese variant does not play along very well, but I am sure some day some clever xda person will come up with the right solution for me, so I'll keep on reading
Click to expand...
Click to collapse
Hey guys, the solution to change the ROM to a chinese p6800 is in this post http://forum.xda-developers.com/showthread.php?t=1479082&page=4
Got mine to change singapore sourced model after loads of attempts loaded the latest XEF firmware then CWM with ODIN and wiped the caches with CWM . Please note you loose all your data . Kies now sees my tab as an XEF region now all I need is a UK 3G rom and will be set.
cannow said:
Got mine to change singapore sourced model after loads of attempts loaded the latest XEF firmware then CWM with ODIN and wiped the caches with CWM . Please note you loose all your data . Kies now sees my tab as an XEF region now all I need is a UK 3G rom and will be set.
Click to expand...
Click to collapse
Are you not getting 3g data as is? And im guessing samsung has stopped pushing this device due to the superbrick bug?
I went with the Austrian stock firmware although i'm in the US. Using a straight talk (no-contract gsm carrier) sim card. It took me 2 weeks to get mms working--as i initially bought my tab from an importer who did NOT tell me the device had been rooted, debloated etc--through amazon btw. I knew i was buying a "demo" model... anyway, firmware version/rom mismatch was the mms issue. Once the version number and baseband version matched, mms worked. Mobile odin is superior to the comp version, but the firmware list upped to filefactory (SUCKS) only has windows self extractors...doesnt anybody know? Windows is dead!
Sent from my GT-P6800 using XDA Premium HD app
(Note: I edited this post, thanks.)
Ok, the ICS P6810 (wifi only) for UK is out ... Now I have a question and please correct me if I'm wrong...
I have the Hong Kong model, whould installing the UK Stock (P6810XXLB3_P6810OXALB3_XEU.zip) with Odin do the trick?
after that use the CSC app from Manniakk to change the CSC to UK and then just use kies to update to ICS?
Is this correct?
Or do I have to change something else?
Please let me know..
Thanks in advance.
Related
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?
I flashed a rom and it wasn't working , I could boot but screen was black . I flashed another rom and pulled a cable by accident.I think my phone is soft bricked. Kies can't recognize it, I can only boot into Download mode. My phone doesn't charge at wall outlet. Rom i used was stock firmware for galaxy s4 (5.0.1) , my model is GT-I9505 (4g version). When i go into odin mode to flash a new rom it fails "Complete(write) operation failed. Please help me!
try flashing with .pit file and tick re-partition.
.pit file is somewhere here on forum - hard to search on mobile.
it is either that or try different cable / USB port / computer
Sent from my TF300T using XDA Free mobile app
th3cr0w said:
try flashing with .pit file and tick re-partition.
.pit file is somewhere here on forum - hard to search on mobile.
it is either that or try different cable / USB port / computer
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
I tried that pit file can be extracted using heimdall, but odin says complete (write) operation failed like it has no access.
https://www.youtube.com/watch?v=Th2Jy9QXhxo
Vokrava said:
I flashed a rom and it wasn't working , I could boot but screen was black . I flashed another rom and pulled a cable by accident.I think my phone is soft bricked. Kies can't recognize it, I can only boot into Download mode. My phone doesn't charge at wall outlet. Rom i used was stock firmware for galaxy s4 (5.0.1) , my model is GT-I9505 (4g version). When i go into odin mode to flash a new rom it fails "Complete(write) operation failed. Please help me!
Click to expand...
Click to collapse
Just let Kies repair it,you have to enter the model and serial nr witch is under the battery.
In Kies go to help or something(in Dutch it's Hulpmiddelen ) then select in drop down Firmware ugrade and inisialate ,then enter model and serial nr
Put phone in download mode and go. The firmware will be downloaded and installed automaticly
Sorry for my bad English
I think Kies doesn't work on rooted phones that is why it can't connect?
@Vokrava: You'd be correct. While I posted the link to the video already, you should be able to resolve this by flashing your firmware via Odin. Just be certain to put the firmware in the Bootloader/BL section of Odin, rather than the PDA/AP section.
Odin : Complete (Write) operation failed
Download mode : SW REV. CHECK FAIL : fused : 4 , Binary : 2
Who is your service provider, and what country is yours?
I got the phone from my friend , I don't know where did he buy it. My provider is mt:s , country is Serbia
Having gotten the phone from a friend changes things. Find out where he got it from and what carrier it was originally using.
Someone told me you can install firmware from any country. I will find that out in 2-3 days or sooner I only remember I had some vodafone bloatware on it. Thanks for helping me I hope we will solve this.
If the phone is unlocked you can install any firmware you wish. However, this particular error seems to be one where you need the original firmware. For example, my I9505 was originally an O2 UK phone, but it's been unlocked. If I encountered this issue I may not be able to use the BTU firmware I have on my hard drive. I'd have to go to sammobile and download O2 firmware.
Ah ok I had cyanogen mod on it before.
Any other way to find out while I wait ?
Not unless you can decipher the IMEI. The carrier the phone was intended for is embedded in it.
It came from Europe (Vodafone) , he doesn't remember the country. I think it is Italy. What do you think ?
Try this firmware.
Patched it with spanish rom , everything is working! Thanks for everything have a nice week!
Store that ROM on your hard drive in case you need it in the future.
How to get rid of "Ramadan" and Hijri on calendar? SM-G950FD Dual Sim version
EDIT- See last post on page 3 by me. Solution found, and samsung pay also working.
Hello, I got my new S8 dual sim version from ebay today, was shipped from texas, but is the dual sim "DUOS" international version. The calendar app has the orange Ramadan line through it and "Hijri" in the settings. Is there any way at all to get rid of this?
I'm not sure if there is a different OEM rom I can flash in ODIN that would get rid of this. I definitely don't want it in my calendar, along with some different dates I'm not aware of that also show up. I googled it and looks like muslim dates.
I've read that SM-G950F roms are compatible, but what about odin flashing F roms and not FD? Would this solve the problem somehow if there is no other work around?
Screenshot_20170619-221511 by Daniel Rivera, on Flickr
Screenshot_20170619-221539 by Daniel Rivera, on Flickr
Just press on it and then delete
NeedleGames said:
Just press on it and then delete
Click to expand...
Click to collapse
That doesn't work though. You can press on it, shows the date individually, event is there but clicking on it does nothing. Also as far I can tell no way to get rid of the muslim calendar dates also. I want to keep it OEM for now, no root, is there any other international variant OEM rom to flash?
danman132x said:
That doesn't work though. You can press on it, shows the date individually, event is there but clicking on it does nothing. Also as far I can tell no way to get rid of the muslim calendar dates also. I want to keep it OEM for now, no root, is there any other international variant OEM rom to flash?
Click to expand...
Click to collapse
You can choose what calendar sources you want (google, celebrations, facebook etc.) All of them are on by default. You just have to find it in the calendar app and disable that calendar. It is celebrations calendar for sure.
I don't know. I'm thinking it's baked into the ROM for real now. I googled this also and it seems the S7 had the issue also on international variants. But there were some work arounds I think. I tried unselecting all the different calendars. There is none that states celebrations on here.
Screenshot_20170620-090119 by Daniel Rivera, on Flickr
You can flash any firmware (using Odin) from the F version to the FD one with absolutely no issue.
Edit: If you are scared to flash an F firmware, you can flash the Russian one (from the FD) and it wont have any of that "bloatware"
t-shock said:
You can flash any firmware (using Odin) from the F version to the FD one with absolutely no issue.
Edit: If you are scared to flash an F firmware, you can flash the Russian one (from the FD) and it wont have any of that "bloatware"
Click to expand...
Click to collapse
Cool, so would this one work? https://www.sammobile.com/firmwares/galaxy-s8/SM-G950FD/SER/download/G950FXXU1AQF7/172614/
It's an updated version also it seems, as I'm on AQDG and security patch April 1, 2017 and this one is 6-1-17. This won't put the russian alphabet on my phone will it? lol
Mine has the Egypt firmware apparently.
danman132x said:
Cool, so would this one work? https://www.sammobile.com/firmwares/galaxy-s8/SM-G950FD/SER/download/G950FXXU1AQF7/172614/
It's an updated version also it seems, as I'm on AQDG and security patch April 1, 2017 and this one is 6-1-17. This won't put the russian alphabet on my phone will it? lol
Mine has the Egypt firmware apparently.
Click to expand...
Click to collapse
That should do
You can remove the russian keyboard very easily (it is like if you flash a Greek or Italian OS, no big deal)
But be aware. In order to avoid the EGY CSC, you shouldnt have a SIM card while booting for the first time and you should probably use a .pit file
Last but not least, use SamFirm to download the whole firmware (Here) and make sure that you tick the Binary Nature selection on the app (that way, you will get 5 files instead of one and you can completely remove the EGY csc)
t-shock said:
That should do
But be aware. In order to avoid the EGY CSC, you shouldnt have a SIM card while booting for the first time and you should probably use a .pit file
Last but not least, use SamFirm to download the whole firmware (Here) and make sure that you tick the Binary Nature selection on the app (that way, you will get 5 files instead of one and you can completely remove the EGY csc)
Click to expand...
Click to collapse
I'm not exactly sure what you mean by the EGY CSC. What is this exactly? Under software information I see under service provider is EGY/EGY/EGY. I do have straight talk up and running just fine on my S8 using the ATT network, everything works as it should right now.
I'll be sure to have my SIM card removed when flashing in odin and rebooting the 1st time. As of right now, I'm downloading the file from sammobile, the zip file which they say to extract and flash in odin.
I checked that link you sent and found the russian one with the SER region selected and clicked binary nature. So should I not flash the file from Sammobile with odin and use the the link you sent instead?
The tool downloaded the 5 files you said, I have a HOME_CSC file, CSS_OXM... , CP, BL, and AP files. They are all md5 files. So you're saying I should flash these in odin instead of the single file from Sammobile?
Im good at rooting phones and stuff, but only when following guides. The "behind the scenes" stuff I'm not good at since I don't program. This one I'm not rooting right away, just want to do this to try and get rid of the egypt stuff and muslim calendar things.
Heres what I have. It shows 4 places to flash though. The AP, BL, and CP seem straightforward using the files downloaded, but which one of the top 2 files goes in the CSC part?
odintest by Daniel Rivera, on Flickr
danman132x said:
I'm not exactly sure what you mean by the EGY CSC. What is this exactly? Under software information I see under service provider is EGY/EGY/EGY. I do have straight talk up and running just fine on my S8 using the ATT network, everything works as it should right now.
I'll be sure to have my SIM card removed when flashing in odin and rebooting the 1st time. As of right now, I'm downloading the file from sammobile, the zip file which they say to extract and flash in odin.
I checked that link you sent and found the russian one with the SER region selected and clicked binary nature. So should I not flash the file from Sammobile with odin and use the the link you sent instead?
The tool downloaded the 5 files you said, I have a HOME_CSC file, CSS_OXM... , CP, BL, and AP files. They are all md5 files. So you're saying I should flash these in odin instead of the single file from Sammobile?
Im good at rooting phones and stuff, but only when following guides. The "behind the scenes" stuff I'm not good at since I don't program. This one I'm not rooting right away, just want to do this to try and get rid of the egypt stuff and muslim calendar things.
Heres what I have. It shows 4 places to flash though. The AP, BL, and CP seem straightforward using the files downloaded, but which one of the top 2 files goes in the CSC part?
odintest by Daniel Rivera, on Flickr
Click to expand...
Click to collapse
The single file from Sammobile wont help you to remove all the muslim stuff from your phone. On the other hand, a 5-"pack" firmware will debloat your phone completely.
Just put the BL file to the BL option in Odin
AP file to AP option
CP file to CP option
and CSC (NOT HOME_CSC) at the CSC file
Also make sure that you have "extracted" from the CSC .tar.md5 the pit (Just open it with WinRaR and extract the .pit file)
After doing that, open the pit section on the Odin and selete the pit file that you just extracted
t-shock said:
The single file from Sammobile wont help you to remove all the muslim stuff from your phone. On the other hand, a 5-"pack" firmware will debloat your phone completely.
Just put the BL file to the BL option in Odin
AP file to AP option
CP file to CP option
and CSC (NOT HOME_CSC) at the CSC file
Also make sure that you have "extracted" from the CSC .tar.md5 the pit (Just open it with WinRaR and extract the .pit file)
After doing that, open the pit section on the Odin and selete the pit file that you just extracted
Click to expand...
Click to collapse
Thank you. This all worked perfectly. Did every option. Phone is back up and running just fine, Latest software and security patches are installed.
Sadly, the ramadan and muslim dates are still there, still shows EGY under service provider SW version. I guess I'll just have to accept this and can't get rid of it.
danman132x said:
Thank you. This all worked perfectly. Did every option. Phone is back up and running just fine, Latest software and security patches are installed.
Sadly, the ramadan and muslim dates are still there, still shows EGY under service provider SW version. I guess I'll just have to accept this and can't get rid of it.
Click to expand...
Click to collapse
I'm glad that your phone works but I still cannot understand why it didnt change
If you get your hands on a european sim, then you will be able to get rid of the muslim dates etc
t-shock said:
I'm glad that your phone works but I still cannot understand why it didnt change
If you get your hands on a european sim, then you will be able to get rid of the muslim dates etc
Click to expand...
Click to collapse
Hello t-shock I'm hoping you'll see this, but I ordered me a Russian Sim card on ebay so I can change to the SER hopefully. Would I follow the same steps again? You did say make sure not to have my Sim card in when booting for the first time, but wouldn't I want to have it in so it can read it and hopefully change? Since when I did it with no Sim cars inserted, it didn't change. Now I'm trying to change my csc to get Samsung pay to work, and it looks like it should on Russian phones since its been released there.
I've tried everything else and I can't even pull up the multi csc menu, even though it shows EGY should be part of the multi csc pack.
danman132x said:
Hello t-shock I'm hoping you'll see this, but I ordered me a Russian Sim card on ebay so I can change to the SER hopefully. Would I follow the same steps again? You did say make sure not to have my Sim card in when booting for the first time, but wouldn't I want to have it in so it can read it and hopefully change? Since when I did it with no Sim cars inserted, it didn't change. Now I'm trying to change my csc to get Samsung pay to work, and it looks like it should on Russian phones since its been released there.
I've tried everything else and I can't even pull up the multi csc menu, even though it shows EGY should be part of the multi csc pack.
Click to expand...
Click to collapse
Hi
Put the Sim on the phone and repeat the step that I have said.
But make sure that you use the pit file and also the csc (not home_csc)
Were you able to get rid of EGY? I'm in the same boat.
I think you should flash multi-CSC firmware that contains CSC you want to get. I have NEE/NEE/XSG, no muslim stuff. OXM firmware.
As I have had same satuition. EGY is included in Multi-CSC OXM, you can't change CSC by odin flashing another Multi-CSC OXM firmware.
I tried flash VD2(Germany Vodafone) then it became VD2/VD2/EGY but if I flash other CSC included in Multi-CSC OXM, it go back to EGY/EGY/EGY. I'm gonna just root my phone now.
I got my phone from Dubai, inserted finnish SIM card and turned on the phone. It automatically changed CSCs to NEE, which is correct for me.
zerosource said:
Were you able to get rid of EGY? I'm in the same boat.
Click to expand...
Click to collapse
Presterin said:
I think you should flash multi-CSC firmware that contains CSC you want to get. I have NEE/NEE/XSG, no muslim stuff. OXM firmware.
Click to expand...
Click to collapse
I'm waiting on my Russian Sim card to come in the mail, then I will try to change to the SER csc, which Samsung pay should work for. Hoping it changes. Apparently from reading above, if you have a multi csc like the EGY I have, you can't flash another one. That's why when I initially flashed the SER csc through Odin, in a multi part file, it didn't change. HOPING it will change when I get my Russian Sim card.
P1226R said:
As I have had same satuition. EGY is included in Multi-CSC OXM, you can't change CSC by odin flashing another Multi-CSC OXM firmware.
I tried flash VD2(Germany Vodafone) then it became VD2/VD2/EGY but if I flash other CSC included in Multi-CSC OXM, it go back to EGY/EGY/EGY. I'm gonna just root my phone now.
Click to expand...
Click to collapse
Can you clarify please? I'm assuming you had EGY csc also. Is that why when I flash SER csc (Russian) it didn't change anything? But VD2 is not multi csc package and that's why it changed? I don't really care what firmware I'm on now as long Samsung pay will work and it doesn't have all the bloat ware. I was told Russian software has some of the least bloat. Will changing my Sim card change the csc?
Hi guys,
As the title suggest i'm having trouble updating my phone & can't find threads directly relating to the issue i seem to be having.
When i try to update through the phone i get a message that states "The operating system on your device has been modified in an unauthorized way."
I do as the message suggest which asks me to update through kies but then kies makes me download the new app which says my phone is up to date even though i'm on 4.4.4.
As for the state of my phone, i bought it about a month ago sealed new, it's still stock & I've done nothing to it & tested to see if it's routed just in case & it seems not to be.
i'll list all the details to help any kind soul who wishes to help:
Model number - SM-G900f
Baseband version - G900FXXU1ANK3
Kernel version - 3.10.0-2413392 - [email protected] #1 - Fri Nov 14 22:19:34 KST 2014
Build number - KTU84P.G900FXXU1ANK3
Thanks for any help in adavance, if you need more information from me please let me know!
Drakmon said:
Hi guys,
As the title suggest i'm having trouble updating my phone & can't find threads directly relating to the issue i seem to be having.
When i try to update through the phone i get a message that states "The operating system on your device has been modified in an unauthorized way."
I do as the message suggest which asks me to update through kies but then kies makes me download the new app which says my phone is up to date even though i'm on 4.4.4.
As for the state of my phone, i bought it about a month ago sealed new, it's still stock & I've done nothing to it & tested to see if it's routed just in case & it seems not to be.
i'll list all the details to help any kind soul who wishes to help:
Model number - SM-G900f
Baseband version - G900FXXU1ANK3
Kernel version - 3.10.0-2413392 - [email protected] #1 - Fri Nov 14 22:19:34 KST 2014
Build number - KTU84P.G900FXXU1ANK3
Thanks for any help in adavance, if you need more information from me please let me know!
Click to expand...
Click to collapse
Download the latest version of the firmware for your device
Here's the UK version
https://rapidgator.net/file/2220550....galaxys5update.com/galaxy-s5-stock-firmware/
Download odin
https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Download and install the Samsung USB drivers if you haven't already done so
Put your phone into download mode (hold power button Vol down & home button)
Connect phone to PC via USB
Press Vol up to start connection
Open odin
In the AP section add the firmware tar (Unzip download to get tar image)
Press start
Once it's flashed & your phone has restarted (it may not fully boot but it doesn't matter) go to recovery mode (hold power button Vol up & home button) and do a data wipe/factory reset
Now your phone will fully boot
TheFixItMan said:
Download the latest version of the firmware for your device
Here's the UK version
https://rapidgator.net/file/2220550....galaxys5update.com/galaxy-s5-stock-firmware/
Download odin
https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Download and install the Samsung USB drivers if you haven't already done so
Put your phone into download mode (hold power button Vol down & home button)
Connect phone to PC via USB
Press Vol up to start connection
Open odin
In the AP section add the firmware tar (Unzip download to get tar image)
Press start
Once it's flashed & your phone has restarted (it may not fully boot but it doesn't matter) go to recovery mode (hold power button Vol up & home button) and do a data wipe/factory reset
Now your phone will fully boot
Click to expand...
Click to collapse
Thanks for the help!
do you know why it has to be done through Odin & it won't download by itself?
also do you have another link, this one is supremely slow & is there any way to keep the data that's currently on my phone?
Thanks again btw!
Drakmon said:
Thanks for the help!
do you know why it has to be done through Odin & it won't download by itself?
also do you have another link, this one is supremely slow & is there any way to keep the data that's currently on my phone?
Thanks again btw!
Click to expand...
Click to collapse
Most of the links you will find are really slow unless someone has uploaded it to their personal file storage & shared link
I would always advise to factory reset/wipe data after flashing firmware through odin
If you are rooted you can use titanium backup to backup app data but really most apps you don't need to
Things like contacts should be synced to your Gmail account but you can use an app to backup contacts & sms messages - just make sure you save the file to your pc or first & transfer it back & restore it after wipe
WhatsApp has its own backup via Google drive if you enable it
Anything else on internal storage (pictures music documents etc) just copy to pc
TheFixItMan said:
Most of the links you will find are really slow unless someone has uploaded it to their personal file storage & shared link
I would always advise to factory reset/wipe data after flashing firmware through odin
If you are rooted you can use titanium backup to backup app data but really most apps you don't need to
Things like contacts should be synced to your Gmail account but you can use an app to backup contacts & sms messages - just make sure you save the file to your pc or first & transfer it back & restore it after wipe
WhatsApp has its own backup via Google drive if you enable it
Anything else on internal storage (pictures music documents etc) just copy to pc
Click to expand...
Click to collapse
Hey there, quick update!
When i try & parse the update through Odin the process fails?
I noticed in download mode the "system status" is set to "custom" & when i checked into this, when my phone is on in the settings option in about phone my system status is "official".
could this be why it's failing? if so, any ideas how to fix this?
other maybe useful info is when it fails it says "system check fail : aboot" not sure if that gives any more info?
Also in download mode my phone thinks it's a SM-G901F?
Thanks in advance!
Drakmon said:
Hey there, quick update!
When i try & parse the update through Odin the process fails?
I noticed in download mode the "system status" is set to "custom" & when i checked into this, when my phone is on in the settings option in about phone my system status is "official".
could this be why it's failing? if so, any ideas how to fix this?
other maybe useful info is when it fails it says "system check fail : aboot" not sure if that gives any more info?
Also in download mode my phone thinks it's a SM-G901F?
Thanks in advance!
Click to expand...
Click to collapse
The system check will fail if you are trying to flash the wrong firmware
The sm g901f is the galaxy s5 plus so get that firmware for your country
If your device is actually something different get the correct firmware & the correct corresponding pit file & flash both with reparation device ticked
TheFixItMan said:
The system check will fail if you are trying to flash the wrong firmware
The sm g901f is the galaxy s5 plus so get that firmware for your country
If your device is actually something different get the correct firmware & the correct corresponding pit file & flash both with reparation device ticked
Click to expand...
Click to collapse
on my phone it's listed as a SM-G900F, this is the first reference I've ever seen to SM-G901F.
Is this not rather odd that my phone thinks it's an SM-G900F?
Drakmon said:
on my phone it's listed as a SM-G900F, this is the first reference I've ever seen to SM-G901F.
Is this not rather odd that my phone thinks it's an SM-G900F?
Click to expand...
Click to collapse
Not if you flashed a custom rom for a different variant
Anything displayed in about phone is mainly just displaying what is written in the build.prop of the rom/kernel/baseband you are using
Look in the area under where the battery sits - it will tell you what your device is
My guess is that if download mode displays your device as a g901f then that is what it is
TheFixItMan said:
Not if you flashed a custom rom for a different variant
Anything displayed in about phone is mainly just displaying what is written in the build.prop of the rom/kernel/baseband you are using
Look in the area under where the battery sits - it will tell you what your device is
My guess is that if download mode displays your device as a g901f then that is what it is
Click to expand...
Click to collapse
Sticker under the battery lists it as a SM-G900F, mobile is stock new & i bought it about a month or two ago. Not rooted or modified in anyway (at least by me).
I bought it thinking it was an SM-G900f, interesting that it may not be....
Drakmon said:
Sticker under the battery lists it as a SM-G900F, mobile is stock new & i bought it about a month or two ago. Not rooted or modified in anyway (at least by me).
I bought it thinking it was an SM-G900f, interesting that it may not be....
Click to expand...
Click to collapse
It's more likely then that incorrect firmware was flashed on it in the past
Find the correct 900f firmware with pit file & flash it with reparation ticked
TheFixItMan said:
It's more likely then that incorrect firmware was flashed on it in the past
Find the correct 900f firmware with pit file & flash it with reparation ticked
Click to expand...
Click to collapse
so is the sticker on the back the correct Model i should be targeting or is the download mode version my actual model?
Drakmon said:
so is the sticker on the back the correct Model i should be targeting or is the download mode version my actual model?
Click to expand...
Click to collapse
Highly unlikely the sticker has been altered
More likely someone flashed incorrect firmware on device
Find correct firmware (what the device actually is) and pit file (pit file must correspond to firmware) & tick reparation device
TheFixItMan said:
Highly unlikely the sticker has been altered
More likely someone flashed incorrect firmware on device
Find correct firmware (what the device actually is) and pit file (pit file must correspond to firmware) & tick reparation device
Click to expand...
Click to collapse
Thanks for all the help you're giving,
Is there any diagnostic programs that can tell me 100% what model my phone is actually supposed to be?
Half the stuff online says the download mode version is correct but there is this whole thread dedicated to someone in a very similar issue to that i'd like to avoid as it looks like it takes ages to fix: https://forum.xda-developers.com/galaxy-s5/help/samsung-galaxy-s5-sm-g900f-sm-g901f-t3400692/page4
Drakmon said:
Thanks for all the help you're giving,
Is there any diagnostic programs that can tell me 100% what model my phone is actually supposed to be?
Half the stuff online says the download mode version is correct but there is this whole thread dedicated to someone in a very similar issue to that i'd like to avoid as it looks like it takes ages to fix: https://forum.xda-developers.com/galaxy-s5/help/samsung-galaxy-s5-sm-g900f-sm-g901f-t3400692/page4
Click to expand...
Click to collapse
What country is the device from
Is it network locked? And what network is it on
I can give you a quick suggestion of firmware to try
TheFixItMan said:
What country is the device from
Is it network locked? And what network is it on
I can give you a quick suggestion of firmware to try
Click to expand...
Click to collapse
Here is a link to where i bought it from, just as an extra reference as they may have more info than what just i can tell you https://www.ebay.co.uk/itm/New-Factory-Unlocked-SAMSUNG-Galaxy-S5-G900F-Black-White-Blue-16GB-Android-Phone/253356954657?_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20160727114228%26meid%3D6f58bd4f7d0347f1b86e571ca200abc0%26pid%3D100290%26rk%3D1%26rkt%3D2%26mehot%3Dpp%26sd%3D253356954657%26itm%3D253356954657&_trksid=p2060778.c100290.m3507
It's an unlocked phone for us within the UK but it was shipped from Hong Kong if i remember correctly.
on a side note, i was looking into firmware versions, my phone is currently on 4.4.4 but there seems to be no version listed for that on SM-900F PDA lists but there is on SM-901F & one of the firmware updates is listed as G901FXXU1ANK3 & my PDA is G900FXXU1ANK3
Drakmon said:
Here is a link to where i bought it from, just as an extra reference as they may have more info than what just i can tell you https://www.ebay.co.uk/itm/New-Factory-Unlocked-SAMSUNG-Galaxy-S5-G900F-Black-White-Blue-16GB-Android-Phone/253356954657?_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20160727114228%26meid%3D6f58bd4f7d0347f1b86e571ca200abc0%26pid%3D100290%26rk%3D1%26rkt%3D2%26mehot%3Dpp%26sd%3D253356954657%26itm%3D253356954657&_trksid=p2060778.c100290.m3507
It's an unlocked phone for us within the UK but it was shipped from Hong Kong if i remember correctly.
on a side note, i was looking into firmware versions, my phone is currently on 4.4.4 but there seems to be no version listed for that on SM-900F PDA lists but there is on SM-901F & one of the firmware updates is listed as G901FXXU1ANK3 & my PDA is G900FXXU1ANK3
Click to expand...
Click to collapse
After g900f on the sticker does it have three letters after it?
---------- Post added at 06:15 PM ---------- Previous post was at 05:59 PM ----------
Drakmon said:
Here is a link to where i bought it from, just as an extra reference as they may have more info than what just i can tell you https://www.ebay.co.uk/itm/New-Factory-Unlocked-SAMSUNG-Galaxy-S5-G900F-Black-White-Blue-16GB-Android-Phone/253356954657?_trkparms=aid%3D111001%26algo%3DREC.SEED%26ao%3D1%26asc%3D20160727114228%26meid%3D6f58bd4f7d0347f1b86e571ca200abc0%26pid%3D100290%26rk%3D1%26rkt%3D2%26mehot%3Dpp%26sd%3D253356954657%26itm%3D253356954657&_trksid=p2060778.c100290.m3507
It's an unlocked phone for us within the UK but it was shipped from Hong Kong if i remember correctly.
on a side note, i was looking into firmware versions, my phone is currently on 4.4.4 but there seems to be no version listed for that on SM-900F PDA lists but there is on SM-901F & one of the firmware updates is listed as G901FXXU1ANK3 & my PDA is G900FXXU1ANK3
Click to expand...
Click to collapse
Try this firmware
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/BTU/download/G900FXXU1CRA2/206701/
With this pit file tick reparation
https://drive.google.com/file/d/0BzyeAt2hy6XeM3g4SWhUaWtoVWM/view
TheFixItMan said:
After g900f on the sticker does it have three letters after it?
---------- Post added at 06:15 PM ---------- Previous post was at 05:59 PM ----------
Try this firmware
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/BTU/download/G900FXXU1CRA2/206701/
With this pit file tick reparation
https://drive.google.com/file/d/0BzyeAt2hy6XeM3g4SWhUaWtoVWM/view
Click to expand...
Click to collapse
I'll write out the whole thing:
Model: SM-G900F
SSN: -G900FGSMH
FCC ID: A3LSMG900F
Also on the case of the pit file - is that kind of interaction super advance? Odin gives me a warning when i go into that setting lol
Drakmon said:
I'll write out the whole thing:
Model: SM-G900F
SSN: -G900FGSMH
FCC ID: A3LSMG900F
Also on the case of the pit file - is that kind of interaction super advance? Odin gives me a warning when i go into that setting lol
Click to expand...
Click to collapse
Flashing pit files will reparation your device - although odin shouldn't do if it is the wrong files as with anything there's always a risk
Usually you wouldn't flash pit files as there's no need but as your phone isn't accepting firmware you may have to
If the above firmware doesn't work you can always try the 901f firmware (without the pit & don't tick repartition) it will only flash it if it passes verification test so no harm in trying
TheFixItMan said:
Flashing pit files will reparation your device - although odin shouldn't do if it is the wrong files as with anything there's always a risk
Usually you wouldn't flash pit files as there's no need but as your phone isn't accepting firmware you may have to
If the above firmware doesn't work you can always try the 901f firmware (without the pit & don't tick repartition) it will only flash it if it passes verification test so no harm in trying
Click to expand...
Click to collapse
The firmware listed above is the same as the original one we downloaded, i'll try it again with the pit file in place & let you know how it goes this time.
Drakmon said:
The firmware listed above is the same as the original one we downloaded, i'll try it again with the pit file in place & let you know how it goes this time.
Click to expand...
Click to collapse
it failed again.
Just for good measure, here are the odin logs:
<ID:0/004> Added!!
<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.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2484 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thought they don't seem to say much
Though on the phone it listed the reason for failure due to PIT
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.