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?
Related
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!
:crying::crying::crying: I can`t flash my S4 SGH-M919V with odin, i try to flash any firmware lollipop 5.0.1 of GT-I9505 that is the same thing and others firmwares of 4.4.4 of the same model but always send me FAIL abort the operation.
I don`t know why when I put my s4 in odin mode show this information in small letters:
ODIN MODE
PRODUCT NAME: SGH-M919V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
MMC BURTS MODE: Enabled
One question the last lines maybe is the problem write protection enabled or not? if is yes the problem how i can fix it for flash any firmware on my s4 thanks for your time (if this post is in the wrong section please change thanks again) i hope solutions XDA-Developers
http://forum.xda-developers.com/galaxy-s4-tmobile is where you need to go for issues with your device, as that forum has far more people familiar with your S4. This is the international S4 forum.
Now, regarding Odin, you should be using a recent version of Odin (current is 3.10), the original cable connected directly to the computer, not using a hub, and not have Kies running. You may also need Samsung's drivers if you haven't installed Kies or downloaded them from Samsung, so if you haven't already downloaded them, do so. That said, attempting to flash an I9505 ROM to your device is automatically going to fail. Odin verifies the model number and other parameters in the S4 before it allows a flash to proceed. Naturally, the model numbers don't match and thus flashing the ROM will not work.
Write protection and MMC bursts modes are supposed to be enabled, so you can eliminate that as a concern.
Thanks for your anwer bro but so to try install a firmware of the same model of mine and the same error
Post your Odin log, so we can see where it fails.
This is mi phone information: i have install Albe95 rom
AP:I9505XXUHOA7
CP:M919VVLUFNH3
CSC:I9505OXAHOA7
This is the Error with any versión of odin and any firmware stock forma this model or :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUHOB7_I9505YXYHOB5_I9505XXUHOB7_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:17)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Any solution? Thank s
I read some post and say it that write protection is enable never can't flash any firm help
Seriously? After telling you that you cannot install an I9505 ROM on your device and explaining why you can't, you're still trying?
YOU CANNOT INSTALL AN I9505 ROM ON A T-MOBILE S4! All attempts to do so will automatically fail. The only stock ROMs that will work on your device are T-Mobile ROMs.
What part of the above do you not understand? Tell me now so I can dumb things down.
i m understand all above OK
this log show with any firmware for the phone or t-mobile firmware men i triying to install stock firmwares for my mobile ok and don`t work of any way but thanks for your time and help :good::good::good: i waiting for more solutions or i read the link than you put above
@LE_17: I apologize for snapping. However I thought I had made it reasonably clear that you could not install an I9505 ROM on your device. Apparently this wasn't the case. In any event, your ROM is here.
that s ok bro no problem
thank s for your time but the link of the firmware that you post i have in my PC downloaded and when i flash it send the same error i dont know why :crying::crying::crying:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Strephon Alkhalikoi said:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Click to expand...
Click to collapse
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Try to flash the latest version from here.
http://www.sammobile.com/firmwares/database/SGH-M919V/#firmware
if it fails, try different usb port and different usb cable.
Try using the latest version of Odin (v3.10.6) and see if you can flash the correct firmware for your rom.
http://forum.xda-developers.com/showthread.php?t=2711451
Try using a different USB port if its failing again and make sure your USB drivers are up to date
Ok man i try it thanks for your time and answer post the result
Lennyz1988 said:
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Click to expand...
Click to collapse
Well color me silly. I did miss that, and I'm sure the OP did too as he mentioned already having that ROM.
LE_17 said:
Ok man i try it thanks for your time and answer post the result
Click to expand...
Click to collapse
If you're trying to flash the official Lollipop update for the S4, use the Canadian version. I tried using the Rogers version (as Videotron uses Rogers' network) from SamMobile and it worked perfectly well. I was even able to change my CSC to Rogers and get the update through Kies.
Disclaimer: If you choose to try this, it is at your own risks. I cannot be held responsible if your phone gets damaged in any way nor can I guarantee the results.
No need for this anymore! The SGHM919V has gotten the Lollipop update this morning.
Hi guys, looking for a little help / advice.
I have a UK Galaxy S4 (I9505) which is rooted and running CM12.01 ROM.
I am trying to Unroot and restore a stock rom via Odin, but it always fails.
<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.1101)..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different versions of the firmware, different versions of Odin. Changed USB cables and ports, but always the same error. Any advice greatly appreciated.
Thanks
Are you flashing the newest firmware available?
GDReaper said:
Are you flashing the newest firmware available?
Click to expand...
Click to collapse
I think so....
the file is: I9505XXUHOD7_I9505EVRHOD1_I9505XXUHOD7_HOME.tar.md5
flashing original rom for samobile.
johnfree98 said:
flashing original rom for samobile.
Click to expand...
Click to collapse
that is originlal ROM from sammobile as far as I know.
the version bootloader and modem to be the same that gives you the cm
johnfree98 said:
the version bootloader and modem to be the same that gives you the cm
Click to expand...
Click to collapse
not quite sure what u mean, could you explain please...
mrmcox said:
not quite sure what u mean, could you explain please...
Click to expand...
Click to collapse
I think he wants to say that you should try and flash a ROM with the same baseband you currently have.
You could also try another windows. Windows 7 always worked for me, but Windows 10 gave me some problems.
GDReaper said:
I think he wants to say that you should try and flash a ROM with the same baseband you currently have.
You could also try another windows. Windows 7 always worked for me, but Windows 10 gave me some problems.
Click to expand...
Click to collapse
So the baseband from the custom ROM that is installed is L720TVPUCOH1. Which official stock ROM should I try ?
Thanks in advance...
mrmcox said:
So the baseband from the custom ROM that is installed is L720TVPUCOH1. Which official stock ROM should I try ?
Thanks in advance...
Click to expand...
Click to collapse
The one with the same baseband. It's worth a try.
GDReaper said:
The one with the same baseband. It's worth a try.
Click to expand...
Click to collapse
Ok, I've found a Stock ROM with the same baseband, but its a US Sprint based ROM, and I have a UK based phone....Will this be ok ?
No. Odin does version checking to confirm that the firmware actually is for the device it is being flashed upon and will fail on a mismatch.
It sounds to me however that you might possibly have a Frankenphone, since you should not be able to install a Sprint bootloader on an international device. Would you please enter Download Mode and read off the model number posted on the screen? This is just to confirm that you really do have an I9505, and not another device masquerading as one.
Strephon Alkhalikoi said:
No. Odin does version checking to confirm that the firmware actually is for the device it is being flashed upon and will fail on a mismatch.
It sounds to me however that you might possibly have a Frankenphone, since you should not be able to install a Sprint bootloader on an international device. Would you please enter Download Mode and read off the model number posted on the screen? This is just to confirm that you really do have an I9505, and not another device masquerading as one.
Click to expand...
Click to collapse
Thanks for the reply..... I had already attempted to install the stock ROM I mentioned above, and It actually worked...
I just went into the Download mode, and checked the product number which now says SPH-L720T.. I also checked this in the "about device" section on the phone, which now gives the same info..... But I'm almost certain it said I9505 last time..
Is this going to be a problem, or should the phone just carry on as normal now ?
Thanks again
mrmcox said:
Thanks for the reply..... I had already attempted to install the stock ROM I mentioned above, and It actually worked...
I just went into the Download mode, and checked the product number which now says SPH-L720T.. I also checked this in the "about device" section on the phone, which now gives the same info..... But I'm almost certain it said I9505 last time..
Is this going to be a problem, or should the phone just carry on as normal now ?
Thanks again
Click to expand...
Click to collapse
The "about device" info can be changed very easily. You could make it show that your device is a S7 and is running iOS.
Download mode info is hard-coded.
So your device always was, and will be, a SPH-L720T
And since it's a Sprint phone, there is one major thing to keep in mind. In the UK and on the European continent, that phone will not get LTE service. The radio in the phone expects to see American channels and won't pick up the European ones. This is like my S4, but only in reverse. In my case, my S4 expects European channels as it's an I9505 and doesn't see American channels.
The only exception to the above is if the original owner managed to rewrite the Qualcomm chip to enable European bands.
GDReaper said:
Download mode info is hard-coded.
So your device always was, and will be, a SPH-L720T
Click to expand...
Click to collapse
This is what I don't understand....As I said, I am almost certain, that this used to say GT I9505, and was definitely an LTE version. I have used this phone on 4G networks. The phone was purchased in the UK direct from EE as a network upgrade. Could something I have done have messed this up ? and anyway to restore it ?
mrmcox said:
This is what I don't understand....As I said, I am almost certain, that this used to say GT I9505, and was definitely an LTE version. I have used this phone on 4G networks. The phone was purchased in the UK direct from EE as a network upgrade. Could something I have done have messed this up ? and anyway to restore it ?
Click to expand...
Click to collapse
It used to say GT-I9505 in download mode?
GDReaper said:
It used to say GT-I9505 in download mode?
Click to expand...
Click to collapse
I'm almost certain it did...not 100% sure, but 80-90% positive it did.... is that possible ? or am I just probably mistaken ?
mrmcox said:
I'm almost certain it did...not 100% sure, but 80-90% positive it did.... is that possible ? or am I just probably mistaken ?
Click to expand...
Click to collapse
I highly doubt it did.
I don't think the info displayed in download mode can be modified. Even if it can, I doubt it is an easy process to do. And flashing different ROMs is 100% not going to change it.
Download mode is similar to the bios of a PC, as I believe it's installed on the phone's motherboard itself, just like a PC's bios.
GDReaper said:
I highly doubt it did.
I don't think the info displayed in download mode can be modified. Even if it can, I doubt it is an easy process to do. And flashing different ROMs is 100% not going to change it.
Download mode is similar to the bios of a PC, as I believe it's installed on the phone's motherboard itself, just like a PC's bios.
Click to expand...
Click to collapse
Is there any way to try and convert it to I9505 baseband, as now it wont receive any data signal in uk, which it always did before. if so how can I do this, and what files should I be looking for ?
thanks
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!
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