Database Users

[Q] Q: Un-rooting / flashing stock Note 3 - HELP

Hello there,
I have looked through the forums and have attempted various different tutorials on how to un-root and flash back to the stock firmware. I am with Rogers Wireless (Canada), and have downloaded Odin and N900W8VLUBMI5_N900W8OYABMI5_RWC which is the rogers firmware for my device. Every time I connect my device to Odin in download mode, select PDA / AP, I get an error log with the following:
Code:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLUBMI5_N900W8OYABMI5_N900W8VLUBMI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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)
On the phone itself, I see:
"SW REV CHECK FAIL: [sb1]Fused 2 > Binary 1"
I cannot seem to flash it, no matter what I do.
Any help is appreciated, I would really like to flash back to the stock firmware and remove root. Thank you.

bustin.droid said:
...
On the phone itself, I see:
"SW REV CHECK FAIL: [sb1]Fused 2 > Binary 1"
I cannot seem to flash it, no matter what I do.
Any help is appreciated, I would really like to flash back to the stock firmware and remove root. Thank you.
Click to expand...
Click to collapse
You are currently on a newer firmware (you can check it in Settings/About or with *#1234# ). You are on a new bootloader and you will not be able to return to an older firmware. Check your knox status - if that is 0x1 you will also never be able to make it back to 0x0. Read around for more info (but generally you should be able to write the latest ROM from your carrier, and that should also remove root).

xclub_101 said:
You are currently on a newer firmware (you can check it in Settings/About or with *#1234# ). You are on a new bootloader and you will not be able to return to an older firmware. Check your knox status - if that is 0x1 you will also never be able to make it back to 0x0. Read around for more info (but generally you should be able to write the latest ROM from your carrier, and that should also remove root).
Click to expand...
Click to collapse
Thank you for the reply,
I see that knox is set to 0x1, doh. Where would I be able to find / download the same / latest firmware for my Rogers Wireless Note 3?
Edit: Found it, thank you. So there will NEVER be a way to trip knox back to 0x0?

bustin.droid said:
Thank you for the reply,
I see that knox is set to 0x1, doh. Should I be able to download the latest firmware from the Rogers website?
Click to expand...
Click to collapse
I don't know about Rogers, but for instance you can look here:
http://www.sammobile.com/firmwares/1/?model=SM-N900W8&pcode=RWC#firmware
There is also another option that might also work - with Kies 3 using Tools -> Emergency firmware recovery - but I believe you might need the latest Kies version and even that one might not work. (I consider that one a little safer only in the fact that if something very bad happens you might get away with free service on it by saying Kies created the problem, while saying that you bricked the phone in Odin will guarantee that service will NOT be covered by warranty).

xclub_101 said:
You are currently on a newer firmware (you can check it in Settings/About or with *#1234# ). You are on a new bootloader and you will not be able to return to an older firmware. Check your knox status - if that is 0x1 you will also never be able to make it back to 0x0. Read around for more info (but generally you should be able to write the latest ROM from your carrier, and that should also remove root).
Click to expand...
Click to collapse
i had the same thing when i flashed the 4.4.2 into hongkong one, same happened and it is stuck,
i cant flash either 4.4.2 not hongkong,
any ideas with thanks.

xclub_101 said:
I don't know about Rogers, but for instance you can look here:
http://www.sammobile.com/firmwares/1/?model=SM-N900W8&pcode=RWC#firmware
There is also another option that might also work - with Kies 3 using Tools -> Emergency firmware recovery - but I believe you might need the latest Kies version and even that one might not work. (I consider that one a little safer only in the fact that if something very bad happens you might get away with free service on it by saying Kies created the problem, while saying that you bricked the phone in Odin will guarantee that service will NOT be covered by warranty).
Click to expand...
Click to collapse
your right, kies does helps, but was wondering can we blame kies for the 0x1 when flashing back to stock if we do a warrenty exchange through the carrier? haha

After I flashed Poland 4.4.2 rom I lost my warranty and Knox now 0×1. ANY ideas how to fix it.
Sent from my SM-N9005 using XDA Premium 4 mobile app

different region rom on indian s5

Hello friends
Have a question
I am using s5 sm g900h indian variant
I am on indian rom right now but i want to try latest 4.4.2 which is in indonesia so can i flash indonesian rom on my variant or should i wait for my update

No, you can't do that. This will brick your phone..
Wait for your regional update..

sharingan said:
I am using s5 sm g900h indian variant
I am on indian rom right now but i want to try latest 4.4.2 which is in indonesia so can i flash indonesian rom on my variant or should i wait for my update
Click to expand...
Click to collapse
You should probably wait for an update from your carrier.
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone as the poster above cited.
Another possibility is changing your CSC to another local carrier that is already rolling out the OTA update. That would likely be compatible but no one will guarantee it as that specific update may depend upon a carrier specific firmware base. Also if you change your CSC from the Android UI, it will insist on wiping your user data, so you'd need to use an app or manually change the CSC code if that matters to you.
.

fffft said:
You should probably wait for an update from your carrier.
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone as the poster above cited.
Another possibility is changing your CSC to another local carrier that is already rolling out the OTA update. That would likely be compatible but no one will guarantee it as that specific update may depend upon a carrier specific firmware base. Also if you change your CSC from the Android UI, it will insist on wiping your user data, so you'd need to use an app or manually change the CSC code if that matters to you.
.
Click to expand...
Click to collapse
Okk then
I will wait for my update

I have cross flashed from different regions without issues.
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H

fffft said:
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone
Click to expand...
Click to collapse
drakester09 said:
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
Click to expand...
Click to collapse
If you had read either of the two posts above yours, you would have found an answer to your question.
Having made a handful of working flashes does not equate to a guarantee that it will work in all situations and cases. You are encouraging people to put their phones at risk. Your statement that it should be good as long as it is for a 900H is demonstrably wrong.
It does not always work. You've merely been lucky so far.
.

fffft said:
If you had read either of the two posts above yours, you would have found an answer to your question.
Having made a handful of working flashes does not equate to a guarantee that it will work in all situations and cases. You are encouraging people to put their phones at risk. Your statement that it should be good as long as it is for a 900H is demonstrably wrong.
It does not always work. You've merely been lucky so far.
.
Click to expand...
Click to collapse
The condescending tone of yours is ill fitted to this conversation.
I read your post, now could you be so kind to actually read mine?
What issues did you guys have when flashing a different region firmware?
Click to expand...
Click to collapse
Can you please share some cases where this has happened?
Where it has been stated and proven that CSC differences can risk your phone?
If so then the CSC changer app is a risk and should be removed, but it isn't.
We are not talking about variants, of course T/L/S/F are not the same despite haviing Snapdragon and you might break something when cross flashing, basebands are different, etc etc.
All G900Hs are equal. The software that was built for one G900H will work in another.
The carrier/regional customizations COULD cause issues if there's a certain incompatibility between app data, but they are easily fixed by a wipe.
For once the PIT argument is useless, Odin pulls the current PIT from your phone to map partitions.
In old days the update was not as seamless and you might be forced to use a PIT file. That's not the case for current releases.

drakester09 said:
The condescending tone of yours is ill fitted to this conversation.
Click to expand...
Click to collapse
Uh huh. You give no rationale for encouraging people to do something very risky. One doesn't have to search very far in the forum to find people that have bricked phones doing what you suggest. Your last post at last offers an elaboration in which we find you relying upon several factual errors. Leaving me no choice but to disagree with you about about who is being condescending.
Firmware is installed as a set of partitioned images. In particular hidden.img contains carrier specific items in a partition that is known to vary in size amongst some carriers. There are numerable and repeatable cases of people flashing firmware from another carrier bricking their phones.
As you say, if you provide no explicit PIT file, Odin will map the partitions by drawing the current PIT from your phone. And that is exactly what corrupts partitions if the new firmware expects a larger partition for hidden.img. The existing PIT is not accurate for a new firmware image that requires a larger partition. And not surprisingly, corrupt partitions can amount to a bricked phone.
Anyone following your advice is playing Russian roulette with their phone. Sometimes it will work. And sometimes your advice will brick their phone.
.
.

fffft said:
Uh huh. You give no rationale for encouraging people to do something very risky. One doesn't have to search very far in the forum to find people that have bricked phones doing what you suggest. Your last post at last offers an elaboration in which we find you relying upon several factual errors. Leaving me no choice but to disagree with you about about who is being condescending.
Firmware is installed as a set of partitioned images. In particular hidden.img contains carrier specific items in a partition that is known to vary in size amongst some carriers. There are numerable and repeatable cases of people flashing firmware from another carrier bricking their phones.
As you say, if you provide no explicit PIT file, Odin will map the partitions by drawing the current PIT from your phone. And that is exactly what corrupts partitions if the new firmware expects a larger partition for hidden.img. The existing PIT is not accurate for a new firmware image that requires a larger partition. And not surprisingly, corrupt partitions can amount to a bricked phone.
Anyone following your advice is playing Russian roulette with their phone. Sometimes it will work. And sometimes your advice will brick their phone.
.
.
Click to expand...
Click to collapse
I crossflashed numerous factory roms with Odin on my S/S2/S3/S4/S5 and Note/2/3 from various (European) country`s and never had a issue with pit files ans csc files to be honest. Can`t imagine beeing luky like that all the time every time.

gee2012 said:
Can`t imagine beeing luky like that all the time every time.
Click to expand...
Click to collapse
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.

fffft said:
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
Click to expand...
Click to collapse
Lets agree to disagree. Imo you don`t have to flash a pit file if you flash a compatible rom for your model with the same partition layout (16 or 32GB) everytime you flash a stock rom.
PS saw earlier posts by you and i want to point out none of my my advices/posts ever lead to a bricked device

fffft said:
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
Click to expand...
Click to collapse
I'm sorry to be a bother but could you please share any case where the mentioned situation has happened?
There must be at least one or several.
I'm all in for factual data so I'd love to see real scenarios where this has happened. It will take you much less time than to post such a long winded post and will prove your point.
Thanks in advance.

gee2012 said:
I crossflashed numerous factory roms with Odin on my S/S2/S3/S4/S5 and Note/2/3 from various (European) country`s and never had a issue with pit files ans csc files to be honest. Can`t imagine beeing luky like that all the time every time.
Click to expand...
Click to collapse
Exactly. Even I've done it like number of times. No issues whatsoever. Although I take care it's the correct model, I don't really bother about region.
drakester09 said:
I have cross flashed from different regions without issues.
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
Click to expand...
Click to collapse
Sent from 5th Galaxy

How did you cross flash i got G900P i want to flash G900WD how ?

Hi . I have a S5 G900F. I had Alliance rom until recently I decided to bring it back to stock. So i downloaded the european firmware from sammobile.com and flashed it via mobile odin but now my phone is bricked. Another problem is that I cant flash any firmware or custom rom via pc odin it fails. when I press start these commands appear on the lower left corner
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXA1ANG3_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also cant flash anything from recovery beacause when I to go recovery mode these lines are wriiten in red colour
E: unable to mount /system
E; unable to mount /sd card.
Can anyone help me please.
One more thing I ordered the mobile from an online store so I dont know the region of my mobile. on the back, under the battery it says made in vietnam.

waleed794 said:
Hi . I have a S5 G900F. I had Alliance rom until recently I decided to bring it back to stock. So i downloaded the european firmware from sammobile.com and flashed it via mobile odin but now my phone is bricked. Another problem is that I cant flash any firmware or custom rom via pc odin it fails. when I press start these commands appear on the lower left corner
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXA1ANG3_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also cant flash anything from recovery beacause when I to go recovery mode these lines are wriiten in red colour
E: unable to mount /system
E; unable to mount /sd card.
Can anyone help me please.
One more thing I ordered the mobile from an online store so I dont know the region of my mobile. on the back, under the battery it says made in vietnam.
Click to expand...
Click to collapse
Im have the same problem!
Im have a S5 SM-G900M and try install G900F and have the same error.
Is possible install this?

Hello friends i have s5 4g vession G900I how can i enable 4g .i can see only WCDMA/GSMA i din't find LTE/4G in the settings
Sent from my SM-G900I using XDA Free mobile app

sandeep20064096 said:
Hello friends i have s5 4g vession G900I how can i enable 4g .i can see only WCDMA/GSMA i din't find LTE/4G in the settings
Sent from my SM-G900I using XDA Free mobile app
Click to expand...
Click to collapse
Hi.
Im think your phone have a different chip
For example the difference into g900m and the g900f is the bands avaible
The g900m have only 900Mhz / 1800Mhz
The g900f have all bands
But in try install the firmware g900f into g900m but dont work.

please help
walkermoon said:
Exactly. Even I've done it like number of times. No issues whatsoever. Although I take care it's the correct model, I don't really bother about region.
Sent from 5th Galaxy
Click to expand...
Click to collapse
i want to flash newest cambodia ROM to my S5 g900h ... so can i do it easily with odin or i want to change moedm firmware and bootloader first ?? and please help me ASAP
i rooted my S5 and i flash the recovery. but now it has error that it could not run cache partition ...
so i want to go back to stock ... tell me if i have to go to direct cambodia ROM or i have to flash india ROM first ??
please help me with this

[q] help quick and now

need help quick! im trying to flash stock through odin, did not have custom recovery and it gets near and and says FAIL! ext4 hidden image hellpppppp

MarkDyer1 said:
need help quick! im trying to flash stock through odin, did not have custom recovery and it gets near and and says FAIL! ext4 hidden image hellpppppp
Click to expand...
Click to collapse
Add some screenshots about in ODIN.

im really scared man. i downloaded stock from sam mobile note 3 sm n9005 LTE and followed everything!

Joku1981 said:
Add some screenshots about in ODIN.
Click to expand...
Click to collapse
and again using different odin, i really need help, i tried loads

MarkDyer1 said:
and again using different odin, i really need help, i tried loads
Click to expand...
Click to collapse
Did you have Lollipop before?

Joku1981 said:
Did you have Lollipop before?
Click to expand...
Click to collapse
no, im flashing kit kat which i had before, i only rooted it once and then wanted to unroot, no roms, im UK with EE so dont think i had lolipop

Joku1981 said:
Did you have Lollipop before?
Click to expand...
Click to collapse
do you know what it is? can i fix it??? i really scared, youve replied to one of my oither threads and im scared, i just want to fix this

Joku1981 said:
Did you have Lollipop before?
Click to expand...
Click to collapse
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005EVRGNH2_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> modem.bin
<ID:0/008> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> FAIL! (Ext4)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is what odin says

Calm down mate, I know its hard, but that's what you need to do.
Now for that error, its absolutely normal. I have had the exact same error! I mean I still don't know why! I downloaded the German LP ROM and tried to flash it, and it failed, then I downloaded the Polish LP ROM and it flashed successfully. I was certain that the German ROM is meant for 16 GB devices, and as mine is 32 GB it would not flash, but then someone came and said there are no 16 GB models of Note 3 in Europe! Well if that's true then I don't know what's wrong!
So I guess you need to download the Polish LP ROM, and flash it. It should not fail.

devilsdouble said:
Calm down mate, I know its hard, but that's what you need to do.
Now for that error, its absolutely normal. I have had the exact same error! I mean I still don't know why! I downloaded the German LP ROM and tried to flash it, and it failed, then I downloaded the Polish LP ROM and it flashed successfully. I was certain that the German ROM is meant for 16 GB devices, and as mine is 32 GB it would not flash, but then someone came and said there are no 16 GB models of Note 3 in Europe! Well if that's true then I don't know what's wrong!
So I guess you need to download the Polish LP ROM, and flash it. It should not fail.
Click to expand...
Click to collapse
I'm not polish though? I'm Uk on EE which I the stock I tried to flash ? But I can fix this right?

MarkDyer1 said:
I'm not polish though? I'm Uk on EE which I the stock I tried to flash ? But I can fix this right?
Click to expand...
Click to collapse
And I am an Indian :laugh:
No, seriously it doesn't matter what ROM you are flashing regardless of where you are. Yes, you should be able to fix that, at least that's what happened with me, so you shouldn't be any exception, I think.

MarkDyer1 said:
I'm not polish though? I'm Uk on EE which I the stock I tried to flash ? But I can fix this right?
Click to expand...
Click to collapse
This seems problem of the pc or the USB cable/port. Try others.

Joku1981 said:
This seems problem of the pc or the USB cable/port. Try others.
Click to expand...
Click to collapse
Um, I am inclined to say this is wrong mate.

devilsdouble said:
Um, I am inclined to say this is wrong mate.
Click to expand...
Click to collapse
Maybe you can give a better solution coz Im reading your posts in this thread and... anything :fingers-crossed:

devilsdouble said:
And I am an Indian :laugh:
No, seriously it doesn't matter what ROM you are flashing regardless of where you are. Yes, you should be able to fix that, at least that's what happened with me, so you shouldn't be any exception, I think.
Click to expand...
Click to collapse
But then it'll be in weird language? I won't understand any of it and apparently if you put wrong country or carrier on the sim can't tell the phone where to look for satellites to send texts and Internet ect

No it won't be in a weird language. I have flashed the Polish LP and the only way I can tell is that there were a couple of bloat ware apps in Polish.
And any carrier info about SMS etc us on the SIM (as you say and will not be affected by flashing the ROM.
I don't want to be nasty, but if you're this nervous about things then maybe you should stay away from experimenting in until you've read up a bit on it. I once this is fixed.
Sent from my SM-P605 using Tapatalk 4

Try also connecting the cable on a different usb port and also try a different cable if it still fails.
Also if your gonna flash polish lollipop once its finish the first screen will be the choose your language selection then once selected everything will be changed to that language.
Happened to me once but first it was the usb port not supplying enough power so changed it to the back usb port then got at least 50% then failed again and finally replaced my usb cable and was successful.

Check settings-- security...if theres a reactivion lock option..make sure its disabled...it is there on the note 4 and note edge...not sure if itsthere on note 3..but check anyway...if not, maybe something as simple as a different cable and diff USB port may help
Sent from my VZW LG G2

mrao said:
Check settings-- security...if theres a reactivion lock option..make sure its disabled...it is there on the note 4 and note edge...not sure if itsthere on note 3..but check anyway...if not, maybe something as simple as a different cable and diff USB port may help
Sent from my VZW LG G2
Click to expand...
Click to collapse
I can't get on my note 3,it only goes into download mode, why are people thinking its computer or cable?

Because computer usb ports and a busted cable are common reasons fir odin to fail....also make sure samsung kies, if installed, is not running...if you can only get to download mode...all you can do us try flashing stock firnware....or try flashing twrp with auto-reboot unchecked....and then manually reboot to twrp...push a rom and flash it
Sent from my VZW LG G2

My note 3 SM-N9005 is also a SM-N900A. NEED HELP

Okay, so i purchased a brand new samsung note 3 sm-n9005 from hong kong, and its been running perfectly,
here are some specs
android version= kitkat 4.2.2
baseband version = N9005ZHUENF1
kernel version = 3.4.0-722276
built number =KOT49H.N9005ZHUENF1
so far so good, everything seems legit, but then i wanted to upgrade to lollipop so i downloaded the necessary samsung drivers, kies software, odin 3.09,
and the hong kong version of the lollipop 5.0 firmware "N9005ZSUGOC3"
but soon as i click start
it shows fail
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005ZSUGOC3_N9005OZSGOC3_N9005ZSUGOC3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
and as i was inspecting the error on the oden on my phone, i noticed
the product name on my phone is SM-N900A which makes no sense.
to further examine i went to the recovery and it shows
android system recovery <3e>
KOT49H.N900AUCUCNC2
now i am really confused as to what phone i have, the box, documentations, and with in the phone settings everything points to n9005. where as oden and "volume down + power + home" menu shows n900a
and
"volume up + power + home" recovery menu also shows n900a.
what should i do to upgrade to lollipop, what phone do i really have?

What does it say under the battery?
Did you buy from a reliable seller or could it be a knock-off phone?
There's an app on Play you could use - Phone INFO Samsung. DL it and run and see what it tells you.

What is a BOUBOO Note ??? as under system menu .

same isse
i have same issues as yours. dont know what firmware to download

WhateverMan said:
It's a real device, just that the person probably flashed the N9005 firmware on it.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
It's not brand new then. It's a second hand device.

It's a real device, just that the person probably flashed the N9005 firmware on it.
Sent from my SM-N9005 using Tapatalk

So after a while of trying to flash different roms, turns out, it is a n900a
So after a while of trying to flash different roms, turns out, it is a n900a, it is authentic, its not a fake, everything checks out, but the retailer was from hong kong, and they buy the phones on bulk, so the guy distrubuting the phones, has flashed the n9005 rom on to it,
after flashing the n900a lollipop, the phone has been working as good as it should, i have had no problems whats so ever, it just amazes me as to what lengths people would go to deceive and cheat the customers.
anyways, thank you for your replys, hope you all have an amazing time,
sincerely,
Ali,
PS, boubou is what i called my ex girlfriend, its just an inside joke, and since this phone was just about equally two faced, i gave it a name that would make sense

hey, what ever it says on the recovery is true
kings555 said:
i have same issues as yours. dont know what firmware to download
Click to expand...
Click to collapse
hey, what ever it says on the recovery is true
N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar
just flash this,
it is the official android 5.0 lollipop for n900a (atnt). works like a charm, and if you have to, just disable all the atnt apps,
there is no difference other then the fact that it shows a atnt logo on boot.

its an inside joke
JJEgan said:
What is a BOUBOO Note ??? as under system menu .
Click to expand...
Click to collapse
PS, boubou is what i called my ex girlfriend, its just an inside joke, and since this phone was just about equally two faced, i gave it a name that would make sense

hi
​
urmother93 said:
hey, what ever it says on the recovery is true
N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar
just flash this,
it is the official android 5.0 lollipop for n900a (atnt). works like a charm, and if you have to, just disable all the atnt apps,
there is no difference other then the fact that it shows a atnt logo on boot.
Click to expand...
Click to collapse
where did you dload this firmware. im sorry im just noob with these techy stuffs

kings555 said:
​
where did you dload this firmware. im sorry im just noob with these techy stuffs
Click to expand...
Click to collapse
so i can send you the links, or i can send you a full tutorial i made for my friends to install a custom note 4 rom,
it is the best rom you can have on a n900a. ive been rocking that since.

urmother93 said:
so i can send you the links, or i can send you a full tutorial i made for my friends to install a custom note 4 rom,
it is the best rom you can have on a n900a. ive been rocking that since.
Click to expand...
Click to collapse
You can send me and a tutorial? Sorry ... Google translation

MrYuraB said:
You can send me and a tutorial? Sorry ... Google translation
Click to expand...
Click to collapse
I man... Google translation.... OK: P

MrYuraB said:
You can send me and a tutorial? Sorry ... Google translation
Click to expand...
Click to collapse
mate, i dont think i can attach files here, if you give me your email, id be more then happy to email it to you

kings555 said:
​
where did you dload this firmware. im sorry im just noob with these techy stuffs
Click to expand...
Click to collapse
no worries mate, my brother is the same,
http://www.sammobile.com/firmwares/database/SM-N900A/
all the official firmware can be found on this website, however lollipop hasnt been officially released for note 3 att (n900a),
i was using this
http://forum.xda-developers.com/not...-dompop-urv2-2-3-tekhd-edition-note4-t3074094
rom on my note 3, its a port from note edge, had amazing bettery life and little to not bugs.
i no longer have the note 3 i upgraded to a note 5.
hope it helps,
if you want, i made a tutorial for my brother, i can send it to you too

Bricked 900A or maybe N9005!!?? Help
I do hope someone can help me. I have a bricked note 3 which appears to have been bogus for reasons the same as the above. Recovery mode States SM-
Official
Samsung official
But the sticker on the back shows N9005 and the serial is not recognized by keis.
I rooted it using let it rain and tried to flash a recovery to it which then failed and gave me an att&t warning when turning on. I then tried again to flash stock and it now gets to the Samsung logo and no further. I have never been able to flash anything with Odin due to fail (auth) at various stages. Was trying N9005 stock but having read the above tried 900 A From sammobile which also failed at the same point. Running out of ideas and patience, can anyone help? The attached was taken prior to me doing anything.

What model does it say in download mode ??

I need the stock ROM for the Galaxy S4 SM-S975L from Tracfone.

Hello. I need the stock ROM for the Galaxy S4 SM-S975L. All other ROMs (from updato.com, ect) fail to flash. My phone is soft bricked so I need to flash a ROM onto it.
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S975LUDUANB1_S975LTFNANB1_S975LUDUANB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl2.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

sammobile.com has it. No, I can't provide a direct link to it due to site rules.

Strephon Alkhalikoi said:
sammobile.com has it. No, I can't provide a direct link to it due to site rules.
Click to expand...
Click to collapse
Code:
This firmware is only available for premium users.
Please click here to become premium.
That's what SamMobile says when I try to download it. I can't pay $16.77 just for one stock ROM, I don't know what to do.

Try samsung-updates.com. Otherwise pay the $17 as it's far less than purchasing a new phone.

Strephon Alkhalikoi said:
Try samsung-updates.com. Otherwise pay the $17 as it's far less than purchasing a new phone.
Click to expand...
Click to collapse
Samsung Updates has to legit be the WORST thing ever, it says 5 hours for a 1.3GB file (I have 100mpbs down.) I'll try this and If it doesn't work, *sgh* I'll just pay up

Strephon Alkhalikoi said:
Try samsung-updates.com. Otherwise pay the $17 as it's far less than purchasing a new phone.
Click to expand...
Click to collapse
Someone is saying that flash is failing because it's an older firmware. How would I check if it's up to date?

The Straight Talk S4 only ever had the one ROM, thus "someone" has guessed incorrectly.

Strephon Alkhalikoi said:
The Straight Talk S4 only ever had the one ROM, thus "someone" has guessed incorrectly.
Click to expand...
Click to collapse
Well ODIN fails on AUTH

Have you tried a different cable? Have you switched to a different USB port? Did you make certain your drivers were installed correctly before proceeding? Any of these or all of them could explain the error you are having. In the meantime, please provide the following information.
Model Number, located in the upper left corner of the download mode screen.
Android Version, found by going to Settings > More > About device.
Firmware Version (AP, CP, CSC), found by dialing *#1234# in the dialer or by installing Phone Info from the Play Store and running it.
Service Provider
Country
Is the phone rooted? (Yes/No)
Is a custom ROM installed? (Yes/No, and the name of the ROM)

Strephon Alkhalikoi said:
Have you tried a different cable? Have you switched to a different USB port? Did you make certain your drivers were installed correctly before proceeding? Any of these or all of them could explain the error you are having. In the meantime, please provide the following information.
Model Number, located in the upper left corner of the download mode screen.
Android Version, found by going to Settings > More > About device.
Firmware Version (AP, CP, CSC), found by dialing *#1234# in the dialer or by installing Phone Info from the Play Store and running it.
Service Provider
Country
Is the phone rooted? (Yes/No)
Is a custom ROM installed? (Yes/No, and the name of the ROM)
Click to expand...
Click to collapse
- SM-S975L
- Android 4.3
- I can't access the dialer; it's bricked
- Tracfone / Straight Talk
- USA
- Yes
- No

Unfortunately, the fact the stock ROM won't install leads me to think you have a hardware issue. On a working device Odin would not reject the firmware intended for the device. At worst it would simply not attempt to replace the bootloader.
Truth be told, with the S4 being over four years old now, it may be best to cut your losses here and work on getting a newer device. In fact, in your position I would look on Swappa for an unlocked device from T-Mobile, then get a hold of Straight Talk and request a BYOD SIM.

Strephon Alkhalikoi said:
Unfortunately, the fact the stock ROM won't install leads me to think you have a hardware issue. On a working device Odin would not reject the firmware intended for the device. At worst it would simply not attempt to replace the bootloader.
Truth be told, with the S4 being over four years old now, it may be best to cut your losses here and work on getting a newer device. In fact, in your position I would look on Swappa for an unlocked device from T-Mobile, then get a hold of Straight Talk and request a BYOD SIM.
Click to expand...
Click to collapse
I called Straight Talk, Tracfone, and Samsung and they didn't help me at all. Every USB cable, every port, every cable, every laptop, ODIN always fails. I guess I'm just gonna get a new phone, so RIP.

Straight Talk/Tracfone are noted for poor customer service when you call them. You get better results by initiating a chat session with them. Regardless, it's no surprise you got the brush-off from everyone. The phone is old, is no longer sold and is no longer supported by its manufacturer.
If you want to stick with getting Samsung devices from Straight Talk but the S7 on an installment plan is too rich for you, look to the Sky J7 as an alternative. Personally, I'd go the Swappa route and get a device that way.

The aboot.mbn file is the bootloader and will sometimes fail to flash if the OEM Samsung cable isn't used with Odin 3.07.