Database Users

[Q] Trying to find stock rom for SM-N9005, note 3, don't know original network

I have this note 3 SM-N9005 stuck at Samsung logo screen. I am trying to put stock rom in it but my problem is i don't know original network of this phone, because i bought it from ebay. i checked it on internet but so many European countries are using this model number
I am attaching download mode screen in attachment if that can help in finding original network of this phone
Other information about this phone got from its box
Serial Number : RF1DA741A8E
Model Number : SM-N9005
SSN : N9005GSMH
FCC ID : A3LSMN9005
MPN: N9005ZKEBTU
Please help me finding original network of this phone so i can find suitable ROM for this phone.
Thanks in advance

U r from UK? U may find it on sammobile.com

Brownpanda said:
I have this note 3 SM-N9005 stuck at Samsung logo screen. I am trying to put stock rom in it but my problem is i don't know original network of this phone, because i bought it from ebay. i checked it on internet but so many European countries are using this model number
I am attaching download mode screen in attachment if that can help in finding original network of this phone
Other information about this phone got from its box
Serial Number : RF1DA741A8E
Model Number : SM-N9005
SSN : N9005GSMH
FCC ID : A3LSMN9005
MPN: N9005ZKEBTU
Please help me finding original network of this phone so i can find suitable ROM for this phone.
Thanks in advance
Click to expand...
Click to collapse
BTU for U.K.

jdomadia said:
BTU for U.K.
Click to expand...
Click to collapse
Thanks a lot guys , I am downloading it so I will let you know soon , plz let me know how you figured it out , just for future reference

Thanks for your help so far , so as you suggested, i downloaded file for BTU UK and using odin 3.07. But I am getting these messages
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
lot of people suggested to get PIT file for this. I dont know from where i can get that.
lof of people suggested for hard reset. but on hard reset screen it stuck at error message, kies update error so go to download mode
Please suggest what i can do about it now ??

The device was running Kitkat 4.4.2 can tell by Odin mode where it says
Udc start.
Grab the stock Polish ROM XEO and flash it or the newer Polish one.
Edit: failing on bootloader also, another give away.
Sent from my Moto G via Tapatalk

radicalisto said:
The device was running Kitkat 4.4.2 can tell by Odin mode where it says
Udc start.
Grab the stock Polish ROM XEO and flash it or the newer Polish one.
Edit: failing on bootloader also, another give away.
Sent from my Moto G via Tapatalk
Click to expand...
Click to collapse
Thanks for your reply, is XEO and BTU are compatible with each other ? what about downgrade option ? can we go to Jelly bean now or is it not possible now ?

Brownpanda said:
Thanks for your reply, is XEO and BTU are compatible with each other ?
Click to expand...
Click to collapse
Yup XEO works on BTU devices, have a BTU device myself

radicalisto said:
Yup XEO works on BTU devices, have a BTU device myself
Click to expand...
Click to collapse
I am downloading right now , I will let you know how it will go, Thanks for this information

Thanks Thanks Big Thanks for this help, in my case i guess i was using all jelly beans files 4.3. I guess my friend tried to flash 4.4.2 kitkat when it got damaged. I guess right now its not possible to downgrade from kitkat to jelly beans.
Thanks a lot jdomadia for your big help, I am still waiting for your reply how did you figure out it was from BTU UK ? we do see lot of phones with same problem. please let me know
Thanks a lot Radicalisto for sharing your experience , yes you were right XEO and BTU were compatible
If anybody need any help on this thread please do not hesitate to contact me, i will be very happy to share my experience

uogard my note 3 SM-N9005 form 4.4 to 5.0 wifi stop working
please I need help about my Note 3 SM-N9005
I bought from the ebay before 2 months ago it was good but I did upgrade to Android 5.0 using Odin ( 5 files PIT, BL, AP, CP, CSC ) finish SUCCESSFUL but after rebooting I find the WiFi is not working at all
I have try for more than ten different firmware but nothing the WiFi still not working
Model: SM-N9005
FCC ID : A3LSMN9005
SSN : N9005GSMH
SN : MAM2C88YT14
please any body can help me

Brownpanda said:
Thanks Thanks Big Thanks for this help, in my case i guess i was using all jelly beans files 4.3. I guess my friend tried to flash 4.4.2 kitkat when it got damaged. I guess right now its not possible to downgrade from kitkat to jelly beans.
Thanks a lot jdomadia for your big help, I am still waiting for your reply how did you figure out it was from BTU UK ? we do see lot of phones with same problem. please let me know
Thanks a lot Radicalisto for sharing your experience , yes you were right XEO and BTU were compatible
If anybody need any help on this thread please do not hesitate to contact me, i will be very happy to share my experience
Click to expand...
Click to collapse
They knew it was BTU because all phones from the UK, regardless of operator, are BTU (AFAIK), with the exception of Three.

I have a SM-N9005
SERIAL NUMBER RF1DA9A6R1Z
FCC ID : A3LSMN9005
SSN : N9005GSMH
Anyone knows the original firmware, can you help me please?

Im using Note3 N9005 and im on 4.4.2 kitkat.
I want to upgrade my firmware to lollipop.
My AP: N9005DXUFNG2
CP: N9005DXUFNG1
CSC: N9005OLCFNG1
my question is Which contry firmware should i flash?

Don't need any help.
I flash lollipop rom N9005 by myself.
Waste of time...........
Sent from my SM-N9005 using XDA Free mobile app

<ID:0/018> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOK6_N9005BTUGBOJ1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
<ID:0/018> SetupConnection..
<ID:0/018> Initialzation..
<ID:0/018> Get PIT for mapping..
<ID:0/018> Firmware update start..
<ID:0/018> SingleDownload.
<ID:0/018> aboot.mbn
<ID:0/018> NAND Write Start!!
<ID:0/018> FAIL! (Auth)
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
my phone info is
model:sm-n9005
fcc id:a3lsmn9005
ssn:-n9005gsmh
---------- Post added at 02:19 AM ---------- Previous post was at 02:12 AM ----------
shamim shambu said:
Don't need any help.
I flash lollipop rom N9005 by myself.
Waste of time...........
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
what country did you choose please help me

styphon said:
They knew it was BTU because all phones from the UK, regardless of operator, are BTU (AFAIK), with the exception of Three.
Click to expand...
Click to collapse
Plus exception of O2 EE VOdA etc etc .

Hi there, i lost my stock rom can any one help me find i cant find it for my model
Model SM-N9005
FCCID A3LSMN9005
SSN N9005GSMH
Made in Vietnam by Samsung

faisalmemon said:
Hi there, i lost my stock rom can any one help me find i cant find it for my model
Model SM-N9005
#
READ this thread .
See stock rom posts in General section see sammobile or samsung-updates .
Hundreds of roms for N9005 .
https://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-sticky-roll-t3237249
Click to expand...
Click to collapse

[Q] Grand 2 Duos in Brazil: model number SM-G7102T (not G7102)

Hello from Brazil to Grand 2 owners and developers!
I've just bought a Grand 2 Duos smartphone, to replace my Grand Duos (GT-I9082L) because of a broken screen. After reading many XDA posts on this phone, I found out that my model number is not the same mentioned here: mine is SM-G7102T, not SM-G7102. I guess "T" stands for "TV", as it has a digital TV receiver, with antenna and builtin app (see photo/screenshots attached).
I would like to try rooting my phone, but it seems dangerous to install @balliboxer's prerooted ROM, because of the different model number. Is there any safe way to test it? TV is not important, root access would be much more useful. But I'm afraid of bricking my phone with the custom ROM.
As it's a newly released phone, I couldn't even find its stock ROM on samfirmware.com or samsung-updates.com. Is there any way to backup my current firmware, so that I can restore if needed?
Can I help XDA members to find out some technical details about this specific model, so that balliboxer and other developers can assure if the custom ROMs can work with it?
-> UPDATED - April 1st (not April Fools!!): CF-ROOT file made for SM-G7102 works with SM-G7102T! Check this thread (thanks, chainfire!):
http://forum.xda-developers.com/galaxy-grand-2/development/-t2698428
Thanks a lot!
Francisco Mogadouro da Cunha
Campinas - Sao Paulo - Brazil

Francisco,
I think it will be hard to get root access because appearantely this model have just release only here in Brazil

Friend. I bought SM-G7102T but it is impossible to use. Lock too. It is very difficult to make and receive calls. Until changed by another but the default continues. Your gran 2 also came with this defect?

gerardojunior said:
Friend. I bought SM-G7102T but it is impossible to use. Lock too. It is very difficult to make and receive calls. Until changed by another but the default continues. Your gran 2 also came with this defect?
Click to expand...
Click to collapse
Have you this problem yet? I have the same problem and I'm trying to solve this, but no success

Root and call problems
I cant do the root and Im having trouble with calls (very slow with the contacts). Any solution?

rlfmeneses_ i have the same problem ;(

DELETED

Re:
rspaulo said:
DELETED
Click to expand...
Click to collapse
1) Install KIES on your desktop;
2) Plug your Grand 2 Duos (SM-G7102T) via USB cable;
3) When KIES recognizes device and it's version (SM-G7102T), it will automatically update with new firmware version that fix this problem. (Problem: Very slow to answer calls and to made new calls also to view contact list).
Thanks;
Jussa.

JussaSP said:
1) Install KIES on your desktop;
2) Plug your Grand 2 Duos (SM-G7102T) via USB cable;
3) When KIES recognizes device and it's version (SM-G7102T), it will automatically update with new firmware version that fix this problem. (Problem: Very slow to answer calls and to made new calls also to view contact list).
Thanks;
Jussa.
Click to expand...
Click to collapse
Just want a 4.4 rom, but thanks

chicao said:
Hello from Brazil to Grand 2 owners and developers!
I've just bought a Grand 2 Duos smartphone, to replace my Grand Duos (GT-I9082L) because of a broken screen. After reading many XDA posts on this phone, I found out that my model number is not the same mentioned here: mine is SM-G7102T, not SM-G7102. I guess "T" stands for "TV", as it has a digital TV receiver, with antenna and builtin app (see photo/screenshots attached).
I would like to try rooting my phone, but it seems dangerous to install @balliboxer's prerooted ROM, because of the different model number. Is there any safe way to test it? TV is not important, root access would be much more useful. But I'm afraid of bricking my phone with the custom ROM.
As it's a newly released phone, I couldn't even find its stock ROM on samfirmware.com or samsung-updates.com. Is there any way to backup my current firmware, so that I can restore if needed?
Can I help XDA members to find out some technical details about this specific model, so that balliboxer and other developers can assure if the custom ROMs can work with it?
-> UPDATED - April 1st (not April Fools!!): CF-ROOT file made for SM-G7102 works with SM-G7102T! Check this thread (thanks, chainfire!):
http://forum.xda-developers.com/galaxy-grand-2/development/-t2698428
Thanks a lot!
Francisco Mogadouro da Cunha
Campinas - Sao Paulo - Brazil
Click to expand...
Click to collapse
Hi friend... I´m from Brazil too and I have a g7102t. When you rooted the phone, the TV stay works?
I have some issues on my smartphone. The battery is very hot and terminate so fast. The GPS is very slow to connect.
I need to upgrade to 4.4.4 or 5.0 (CM12). But I can´t lose TV function.
Can you help me?

thiago.augusto.souza said:
Hi friend... I´m from Brazil too and I have a g7102t. When you rooted the phone, the TV stay works?
I have some issues on my smartphone. The battery is very hot and terminate so fast. The GPS is very slow to connect.
I need to upgrade to 4.4.4 or 5.0 (CM12). But I can´t lose TV function.
Can you help me?
Click to expand...
Click to collapse
Hi Thiago! I'll write in English, as the answer may be useful to people from other countries. I really don't know if there is GM-7102T in any other country, or if it's a Brazil-only version.
Everything works fine after rooting, including embedded TV. Unfortunately my phone broke some months ago, and I've changed to other model. So I think I can't help you with the other issues.
Francisco

Hi Francisco! Tks for response! I'll try to root too. But do you know if cm12 still works built in TV?

thiago.augusto.souza said:
Hi Francisco! Tks for response! I'll try to root too. But do you know if cm12 still works built in TV?
Click to expand...
Click to collapse
I don't know anything about CM12 on G7102T. I've used only a rooted stock ROM.
I guess TV won't work, as it requires specific software. But you can try it and reinstall original ROM back if it doesn't work.

chicao said:
I don't know anything about CM12 on G7102T. I've used only a rooted stock ROM.
I guess TV won't work, as it requires specific software. But you can try it and reinstall original ROM back if it doesn't work.
Click to expand...
Click to collapse
Dear Chicao,
Do you think that it´s possible do a backup of TV´s software (with Titanium Backup) and restore on CM12?
Regards,
Thiago.

thiago.augusto.souza said:
Dear Chicao,
Do you think that it´s possible do a backup of TV´s software (with Titanium Backup) and restore on CM12?
Regards,
Thiago.
Click to expand...
Click to collapse
The tv app uses a lot of libs and system files tb won't backup. I already did it.
We already lost the hope on getting an official update for the g7102, didn't we?
Sent from my Note3

I am have problem in Odin write failed... Can you help?
<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> Added!!
<ID:0/004> Odin engine v(ID:3.1210)..
<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> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Erase)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I dont have permission for post picture or URL
Enviado de meu MI 5 usando Tapatalk

[Q] Software Update for my S5 (SM-G900F)

Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.

gevensa said:
Hello there!
I need your help to be sure about some things.
(Oh! Sorry for my bad English, not my native language)
I have a Galaxy S5, I bought this with my country operator. The latest software for the SM-G900F model released by my operator is G900FXXU1ANCE.
I read that Samsung has updated the software with some better and this update is G900FXXU1ANE2.
My questions are:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Thanks in advance for your answers.
Click to expand...
Click to collapse
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.

gevensa said:
1) If I download the G900FXXU1ANE2 version and install via ODIN, you modify a 0x1 Knox void warranty? Or is maintained in 0x0?
2) If I install G900FXXU1ANE2 and sometime I go to claim warranty, could reinstall the G900FXXU1ANCE version? Ie make downgrade. Or this could change me knox void warranty?
Click to expand...
Click to collapse
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).

Thanks for your answers.
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in Spain?
Sent from my SM-G900F using XDA Free mobile app

gee2012 said:
First of all flashing official firmware with Odin will NEVER trip KNOX. Don`t know if you can flash an older rom, if the bootloader is the same it should be possible, just try it mate and if it should fail you reflash the rom you have now. You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
fffft said:
Installing this update should not change the Knox bit. It should remain at 0x0 in this situation. Flashing stock firmware will not normally change Knox, although if you try installing a pre KitKat firmware e.g. 4.2.1, may corrupt the bootloader and increment the Knox counter. A power interruption during the flash process may also trip Knox. More commonly, installing a custom kernel or recovery will also trip the Knox counter.
You should be able to revert or downgrade to the earlier firmware in your example. And that won't affect your warranty (or be necessary for warranty purposes). Note though that you cannot downgrade all firmware versions. For example, Samsung introduced the Knox DRM in 4.3 and don't want you downgrading to remove it, consequently you cannot downgrade from 4.3 to 4.2.x (or earlier).
Click to expand...
Click to collapse
Thanks for your answers!!
Sent from my SM-G900F using XDA
Free mobile app

gee2012 said:
...
You can flash any compatible rom with Odin, also the ones that are not for your region.
Click to expand...
Click to collapse
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
my stock firmware said:
Model: SM-G900F
Model name: GALAXY S5
Country: Czech Republic
Version: Android 4.4.2
Changelist: 1539356
Build date: Thu, 08 May 2014 03:44:41 +0000
Product Code: ETL
PDA: G900FXXU1ANE2
CSC: G900FETL1AND3
MODEM: G900FXXU1ANE2
Click to expand...
Click to collapse

born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
Where is your device from, if i may ask? Is it a Dutch device or imported?

I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.

born4trance said:
I ordered mine from a dutch webshop (i'm also dutch btw) who import their devices from EU countries.
Click to expand...
Click to collapse
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?

gee2012 said:
Yup, saw that. So you can`t flash a Dutch PHN rom to your device? Strange as it its a EU device as you say Have you tried a German DBT rom?
Click to expand...
Click to collapse
Everything flashes fine, until it encounters hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the mentioned file's filesize differed from the PHN .tar one.
Its a shame that there are so many differences amongst the same model.

born4trance said:
Correct > FAIL! (Size) @ hidden.img.ext4
I haven't looked at other firmwares yet but i did notice that the file in question differed from the one inside the PHN .tar
Click to expand...
Click to collapse
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.

gee2012 said:
What software version do you have now annd what is your CSC file? In the dialpad type *#1234#.
Click to expand...
Click to collapse
I already quoted the firmware i (currently) have, a few posts back

born4trance said:
I already quoted the firmware i (currently) have, a few posts back
Click to expand...
Click to collapse
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.

gee2012 said:
Sorry for not reading that Usualy it shouldn`t be a problem to flash a different European rom. I got my phone with a TNL (T-Mobile) rom and flashed a PHN rom and it wasn`t a problem for me. I`ll try flashing a DBT rom just to see if it works.
Click to expand...
Click to collapse
Perhaps it will work for you but not for me Í'm not sure if or when i'll flash another FW, i don't really want to lose/give up towelroot :angel:

gevensa said:
Another question: I have csc CRM What if I install the csc PHE, I will receive in the future the OTAs to release in SpaIn?
Click to expand...
Click to collapse
An OTA update will check your CSC to see if the update should be applied to your system. If you change your CSC from AAA to BBB, you can't expect to receive OTA's for AAA any longer. If your intent in doing this is wanting to receive BBB updates, the CSC change will usually suffice. It's a carrier implementation though and a more conservative carrier could also do secondary checks such as matching the baseband CSC as well.
Also you shouldn't change a CSC unless you are confident that the BBB OTA is compatible with your current firmware.
.
---------- Post added at 11:06 PM ---------- Previous post was at 10:17 PM ----------
born4trance said:
Well, i tried to flash a PHN firmware once but it failed at hidden.img.ext4 with "FAIL! (size)".
So there are some exceptions =/
Click to expand...
Click to collapse
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care aout Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
.

fffft said:
That doesn't surprise me at all. As I said earlier, you cannot expect to flash any firmware with Odin. It is dismaying how many people state that you can do so when they don't really know that to be true. Or to be more precise, they think they know and want to help someone. But in fact, they don't understand the subject in any depth, have no reasonable basis to believe that they do and good intentions notwithstanding, do a real disservice by spreading dangerously inaccurate information.
To reiterate, you cannot flash any file with Odin. Someone who tells you that you can flash any carrier's S5 firmware onto your S5 is demonstrably wrong. It will work in some cases and they are making a bad assumption that because it worked in one case that it can be universally done. As you found out firsthand, that is not true. Someone who assumes it is universally true and further presents that unfounded assertion as fact isn't exercising sound judgement.
This is an oversimplification, but to give you a rough idea of what is going on.. hidden.img.ext4 contains carrier specific information. And it is partitioned. So if you flash a firmware from another carrier and it happens to be formatted as a larger partition, the flash will corrupt the partition structure, leading to the Odin error writing to hidden.img.ex4 and soft brick your phone.
Long story short, don't blindly believe everyone that makes authoratative statements about what you can safely do. Try to understand the process as much as possible yourself, so that you can spot the worst inconsistencies. And look for a sense of how deep and consistent someone's knowledge of a subject is before taking their advice.
To recover after flashing an incompatible flash from another carrier, you would ideally flash a stock copy of hidden.img.ext4 and the PIT from the original carrier. If you don't care out Knox, flashing CWM will typically resolve the issue as well. Also if you understand partitioning structures, better informed users can discern in advance if a carrier x firmware can be safely flashed or not.
Click to expand...
Click to collapse
Wow.. and wow (+thanks )
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 (of the same model) that comes with a PHN firmware, and then flash the PHN firmware itself and retain 0x0

born4trance said:
So (long story short): besides flashing CWM/TWRP/Philz i could flash a .pit from a 16GB S5 that has a PHN firmware on it (and retain 0x0)
Click to expand...
Click to collapse
Flashing a custom recovery would increment Knox to 0x1. But it should remain 0x0 if you use the proper PIT corresponding to the new stock firmware. I haven't tested that (as I don't really care about Knox personally) but I don't see any logical reason that Knox would be concerned with that scenario, nor heard of any reports of it happening to anyone.
PHN.. is Netherlands? So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Theoretically the write could still fail on an aboot auth failure but I haven't seen any evidence that carriers are locking down their bootloaders that tightly and don't think that would be a likely impediment.
.

fffft said:
PHN.. is Netherands?
Click to expand...
Click to collapse
Correct: For non branded / SIM-lock free
fffft said:
So assuming that you have say, a 16 GB SM-G900F, you should be able to flash a 900F PHN firmware successfully and safely if you do so in conjunction with a PIT file for a 16 GB PHN 900F. I presume that the flash won't trip Knox either but I have not actually done so personally.
Click to expand...
Click to collapse
I indeed own a SM-G900F and its also important to mention that the partition layout differs between 16GB/32GB models
Now to get ahold of the correct .pit (still looking)

install lollipop 5.0 FAIL! (Auth)

Hello every body here :
i have an S5 G900f have an old lollipop 5.0 which i dosn't like
so i went to choose an earliest firmware 5.0 from sammobile
when i try to install it using ODIN i get the error message below
<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)
searching for this in google say that the solution is to uncheck reactivation lock under security setting
the problem i can nnot find it in my s5
no reactivation lock under security setting
any help thank's

Are you sure you are running stock Lollipop?
And are you sure it is a G900F?
Check in download mode what it says the model is

*Detection* said:
Are you sure you are running stock Lollipop?
And are you sure it is a G900F?
Check in download mode what it says the model is
Click to expand...
Click to collapse
strange my download mode says it is G900P
but under about my device or when i remove the battery it says G900F

jamel-o said:
strange my download mode says it is G900P
but under about my device or when i remove the battery it says G900F
Click to expand...
Click to collapse
A lot of S5s are mislabelled - your device is the G900P

*Detection* said:
A lot of S5s are mislabelled - your device is the G900P
Click to expand...
Click to collapse
So i should download the firmware version for G900P andtry again

Yep, can't remember if Lollipop locks the bootloader on the G900P or not, but you should be able to 'upgrade' at least if it does

You must ALWAYS believe your phone's download screen model name
Enviado desde mi SM-G900F mediante Tapatalk

can i upgrade my firmware using samsung kies !!? which model i put ?
it says that it can not verify my model S/N

What ROM version is running on the phone at the minute?
Post a screenshot of Phone INFO Samsung
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
Firmware section

Baseband version :
G900FXXU1BOD3

Try the latest for the G900P with ODIN, see how you get on
Looks like whoever you bought it from, has either modded the build.prop to display G900F info, or manage to flash enough of a G900F ROM to show that info
I can flash a G900T ROM without the bootloader and modem, and it shows G900T on my phone, but the phone is G900F
Either way, if download mode says G900P, that's your model

*Detection* said:
Try the latest for the G900P with ODIN, see how you get on
Looks like whoever you bought it from, has either modded the build.prop to display G900F info, or manage to flash enough of a G900F ROM to show that info
I can flash a G900T ROM without the bootloader and modem, and it shows G900T on my phone, but the phone is G900F
Either way, if download mode says G900P, that's your model
Click to expand...
Click to collapse
thank's man i will try the latest firmware for G900P and see

the update work now when i use a G900P Firmware
but seems that he IMEI has changed !!
and the Hands free activation appear !!!
my phone became not activated !!?
what happen i don't know

jamel-o said:
the update work now when i use a G900P Firmware
but seems that he IMEI has changed !!
and the Hands free activation appear !!!
my phone became not activated !!?
what happen i don't know
Click to expand...
Click to collapse
If you flashed a stock Samsung ROM, whatever was done to your phone prior to flashing this ROM is the problem - if it says G900P in download mode, and G900F in About and on the sticker, someone had changed something in order to make it look like a G900F (Likely because they are more popular)
Google how to disable hands free activation, there are youtube videos and forum posts about it

i can not find the hotspot future !!!
under more network or anywhere else

*Detection* said:
Google how to disable hands free activation, there are youtube videos and forum posts about it
Click to expand...
Click to collapse
do you have any idea why i can't find the hotspot future
thank's

Maybe it's not available for that ROM, the G900T firmware doesn't have Mobile Data toggle, but the G900F firmware does (Same phone)

*Detection* said:
Maybe it's not available for that ROM, the G900T firmware doesn't have Mobile Data toggle, but the G900F firmware does (Same phone)
Click to expand...
Click to collapse
i need to use a costum rom from the forum for that ?

jamel-o said:
i need to use a costum rom from the forum for that ?
Click to expand...
Click to collapse
Or find an app, check the play store, might find one that can make a hotspot

s4 i9507 help

Ok I don't even know where to start. The s4 i9507 model is a specific model of the s4 released in Australia on optus network. From what I understand, it is the exact same phone as the s4 i9505. What I am trying to do is flash an unbranded ROM (xsa) for the i9505 onto the i9507. I downloaded the firmware from sammsmobile, but while trying to flash the phone it keeps coming up <ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth).
I don't understand why this may be happening. I have rooted the phone, I have read other forums that suggest to wipe the phone altogether?
P.S please only helpful suggestions, I don't need anyone telling me it's not a good idea to flash a ROM that's meant for another version because the i9505 and i9507 are the exact same phone/specs.

Anyone?

Flash i9507 stock firmware.
Sent from my ASUS_Z00AD using XDA Labs

steveracer said:
Ok I don't even know where to start. The s4 i9507 model is a specific model of the s4 released in Australia on optus network. From what I understand, it is the exact same phone as the s4 i9505. What I am trying to do is flash an unbranded ROM (xsa) for the i9505 onto the i9507. I downloaded the firmware from sammsmobile, but while trying to flash the phone it keeps coming up <ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth).
I don't understand why this may be happening. I have rooted the phone, I have read other forums that suggest to wipe the phone altogether?
P.S please only helpful suggestions, I don't need anyone telling me it's not a good idea to flash a ROM that's meant for another version because the i9505 and i9507 are the exact same phone/specs.
Click to expand...
Click to collapse
So is the GT-I9515, yet ROMs from GT-I9505 don't work on it.
Anyway, your problem may be a result of a faulty USB connection or cable. In other words, father USB wants to try another woman's hole

krasCGQ said:
Flash i9507 stock firmware.
Sent from my ASUS_Z00AD using XDA Labs
Click to expand...
Click to collapse
There is no unbranded stock rom for the i9507. It was released specifically for optus australia and asia. So the only stock rom i can get still has the telco's logos on boot up and shut down, I did see if i could find the file to delete them but couldn't see it anywhere

steveracer said:
Ok I don't even know where to start. The s4 i9507 model is a specific model of the s4 released in Australia on optus network. From what I understand, it is the exact same phone as the s4 i9505. What I am trying to do is flash an unbranded ROM (xsa) for the i9505 onto the i9507. I downloaded the firmware from sammsmobile, but while trying to flash the phone it keeps coming up <ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth).
I don't understand why this may be happening. I have rooted the phone, I have read other forums that suggest to wipe the phone altogether?
P.S please only helpful suggestions, I don't need anyone telling me it's not a good idea to flash a ROM that's meant for another version because the i9505 and i9507 are the exact same phone/specs.
Click to expand...
Click to collapse
The only helpful solution here is to flash a custom ROM. Attempting to install I9505 firmware on the I9507 will always fail as Odin compares the firmware to the device. Odin will refuse to install the firmware if there is a mismatch.

Strephon Alkhalikoi said:
The only helpful solution here is to flash a custom ROM. Attempting to install I9505 firmware on the I9507 will always fail as Odin compares the firmware to the device. Odin will refuse to install the firmware if there is a mismatch.
Click to expand...
Click to collapse
Funny you say that because odin recognizes the device as an i9505 not what it actually is (i9507)

steveracer said:
Funny you say that because odin recognizes the device as an i9505 not what it actually is (i9507)
Click to expand...
Click to collapse
And yet, Odin rejects it, meaning a mismatch. Ergo, Odin is doing its job and rejecting the ROM you're attempting to install. Therefore the only viable solution is to install a custom ROM.

Could u recomend one thats not full of bloatware? I tried cyanogenmod 13 and it was terrible

steveracer said:
Could u recomend one thats not full of bloatware? I tried cyanogenmod 13 and it was terrible
Click to expand...
Click to collapse
Well, I'd consider the entirety of Cyanogenmod to be bloatware since very little testing is done to the source code. However, if you believe Cyanogenmod to be bloatware, then you clearly want to install an AOSP ROM, as that's about as bloatware free as it gets.

If you want unbranded gt-i9507 the only available is the hk version. You can find the firmware here:
http://updato.com/firmware-archive-select-model?record=38777983479C11E6A0500CC47A44B7B2