[Q] sm-900k update the bootloader of 4.4.2 Fail - Galaxy Note 3 Q&A, Help & Troubleshooting

My phone is SM-N900K, I want to upate to 4.4.2 ,but update bootloader Fail.
odin says:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
the phone show me:
secure check fail :aboot
Anyone have any ideas?
Thanks!

unplugged138 said:
My phone is SM-N900K, I want to upate to 4.4.2 ,but update bootloader Fail.
odin says:
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
the phone show me:
secure check fail :aboot
Anyone have any ideas?
Thanks!
Click to expand...
Click to collapse
While your device has the SnapDragon CPU, I don't think 4.4.2 is compatible with the K yet, your bootloader on the N900K will be different to the N9005 and you risk hard bricking if you try and force it.

radicalisto said:
While your device has the SnapDragon CPU, I don't think 4.4.2 is compatible with the K yet, your bootloader on the N900K will be different to the N9005 and you risk hard bricking if you try and force it.
Click to expand...
Click to collapse
My device's CPU is SnapDragon same with N9005. I just want to upate to kitkat.

unplugged138 said:
My device's CPU is SnapDragon same with N9005. I just want to upate to kitkat.
Click to expand...
Click to collapse
It's not whether the CPU is the same, it's about the bootloader. Your bootloader will be different to the N9005 version. SO may not (but from your 1st post it doesn't!!) work. It's not as simple as "has same CPU"

radicalisto said:
It's not whether the CPU is the same, it's about the bootloader. Your bootloader will be different to the N9005 version. SO may not (but from your 1st post it doesn't!!) work. It's not as simple as "has same CPU"
Click to expand...
Click to collapse
It is still working at 4.3 now.
Thanks mate.

Related

[Q] cannot unroot with odin :(

good day ,
anyone can help me with installing stock version of android 4.3 version on my GS4 ?! i have problem while using odin v3.09 to flash my Galaxy s4 i9505 to stock firmware version 4.3 with the md5 file downloaded from sammobile.com , here is some info about my phone :
having CWM recovery installed
running on custom ROM CM11 4.4.4
error message in odin is as below :
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
micphone7 said:
good day ,
anyone can help me with installing stock version of android 4.3 version on my GS4 ?! i have problem while using odin v3.09 to flash my Galaxy s4 i9505 to stock firmware version 4.3 with the md5 file downloaded from sammobile.com , here is some info about my phone :
having CWM recovery installed
running on custom ROM CM11 4.4.4
error message in odin is as below :
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Download the official firmware of your country and carrier from samobile.Com and flash with odin
This will flash stock firmware and stock recovery
Sent from my GT-I9505 using Tapatalk
1eyedmonster said:
Download the official firmware of your country and carrier from samobile.Com and flash with odin
This will flash stock firmware and stock recovery
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I just bought it from thailand !
micphone7 said:
I just bought it from thailand !
Click to expand...
Click to collapse
You wont be able to flash 4.3 if youre on 4.4.2
"If someone helps, never forget to hit thanks ? "

[Q] Note 4 SM-N910S Rom to N910U Rom

Excuse Me, I have a Note 4, and want to change the Rom from N910S (Korea) to N910U (HK).
I tried to use Odin to directly install N910U Rom but fail, with follows error message:
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help, thousand Thanks!
kwok_h said:
Excuse Me, I have a Note 4, and want to change the Rom from N910S (Korea) to N910U (HK).
I tried to use Odin to directly install N910U Rom but fail, with follows error message:
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help, thousand Thanks!
Click to expand...
Click to collapse
Hi mate
just have finded out what was giving the error.
I've unchecked the reactivation lock under security tab on the android Kitkat... Now can flash whatever I wanted with odin.
Sent From Out of Nowhere
N910s
Do you mean you can flash over 910s an 910u rom ? ....

Flashing stock ROM on rooted phone

I was flashing root(was already rooted) and because i had an bad USB cable it failed midway and now the phone is stuck in "Firmware upgrade encountered an issue. please select Recovery mode in Kies & try again." I learned that i have to flash stock ROM to restore my phone but i dont know what was my latest update (I know its either G900FXXS1CPK1 or G900FXXS1CPLV) before i rooted the phone. Can I just flash the newest version?
peeaarrll said:
I was flashing root(was already rooted) and because i had an bad USB cable it failed midway and now the phone is stuck in "Firmware upgrade encountered an issue. please select Recovery mode in Kies & try again." I learned that i have to flash stock ROM to restore my phone but i dont know what was my latest update (I know its either G900FXXS1CPK1 or G900FXXS1CPLV) before i rooted the phone. Can I just flash the newest version?
Click to expand...
Click to collapse
yes, but sometimes samsung sneaks some stuf fin that you dont want, so you could try the older version first and all that would happen if it doesnt like that one is fail in odin, then youd just go to the most recent one
youdoofus said:
yes, but sometimes samsung sneaks some stuf fin that you dont want, so you could try the older version first and all that would happen if it doesnt like that one is fail in odin, then youd just go to the most recent one
Click to expand...
Click to collapse
hii, really sorry for not replying faster i have just been down in the dumps because of this.I tried doing that but it said no PIT partition so i got that and tried it with that but then it says
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Now im stuck here and i dont know what to do. Please help.
peeaarrll said:
hii, really sorry for not replying faster i have just been down in the dumps because of this.I tried doing that but it said no PIT partition so i got that and tried it with that but then it says
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Now im stuck here and i dont know what to do. Please help.
Click to expand...
Click to collapse
If its failing, youre probably just trying to flash the wrong tar.md5. What version of android were you on before this issue? 6.0.1?
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
try this tar.md5
https://www.sammobile.com/firmwares/download/71369/G900FXXU1CPE1_G900FOXA1CPE1_BTU/
youdoofus said:
If its failing, youre probably just trying to flash the wrong tar.md5. What version of android were you on before this issue? 6.0.1?
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
try this tar.md5
Click to expand...
Click to collapse
yeah i was on 6.0.1. Will the UK version work if im in another country?
peeaarrll said:
yeah i was on 6.0.1. Will the UK version work if im in another country?
Click to expand...
Click to collapse
i only grabbed the uk version because you mentioned the baseband in your post which was a UK version. Its the g900f, so it should be able to accept that version. I think the only difference is the radios and default language. But if you go to www.sammobile.com/firmwares, you can select whichever version you actually need
there is a dropbox above the tar download links thatll allow you to choose whiever one you actually need
https://www.sammobile.com/firmwares/database/SM-G900F/BTU/
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
downloading from this site is always super slow, but its directly from the source. I always keep a copy of the one i need on my hdd for safety
youdoofus said:
i only grabbed the uk version because you mentioned the baseband in your post which was a UK version. Its the g900f, so it should be able to accept that version. I think the only difference is the radios and default language. But if you go to www.sammobile.com/firmwares, you can select whichever version you actually need
there is a dropbox above the tar download links thatll allow you to choose whiever one you actually need
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
[/COLOR]downloading from this site is always super slow, but its directly from the source. I always keep a copy of the one i need on my hdd for safety
Click to expand...
Click to collapse
i tried flashing in now but i still get the same error could it happen because of the USB cable or something else?I got this the first time
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
aand this the second time:
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
should i just continue trying until it succeds, im hesitant to do that because thats how i got it broken(i went fine until about half way through the process it just disconnected from the PC. and when i tried to boot it had the error i stated in the post.)
peeaarrll said:
i tried flashing in now but i still get the same error could it happen because of the USB cable or something else?I got this the first time
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
aand this the second time:
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
should i just continue trying until it succeds, im hesitant to do that because thats how i got it broken(i went fine until about half way through the process it just disconnected from the PC. and when i tried to boot it had the error i stated in the post.)
Click to expand...
Click to collapse
id definitely try a different cable and make sure that you dont touch the cable, phone or computer while its doing its thing. Since its borked anyways and wont boot, its not likely that youll make it any worse by trying odin again or even repeatedly. Also, did you download the oldest baseband of the same android version you were running? Thats also pretty important
youdoofus said:
id definitely try a different cable and make sure that you dont touch the cable, phone or computer while its doing its thing. Since its borked anyways and wont boot, its not likely that youll make it any worse by trying odin again or even repeatedly. Also, did you download the oldest baseband of the same android version you were running? Thats also pretty important
Click to expand...
Click to collapse
I have now downloaded the latest baseband version and tried to flash it but it says that it fail because of size, here is the log of the code;
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.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> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
peeaarrll said:
I have now downloaded the latest baseband version and tried to flash it but it says that it fail because of size, here is the log of the code;
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.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> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
no, not the latest, the oldest. The first one in the same android version you were on
youdoofus said:
no, not the latest, the oldest. The first one in the same android version you were on
Click to expand...
Click to collapse
i downloaded the first one in the same android version i am and tried flashing it but it shows the same error
<ID:0/004> FAIL! (Size)
peeaarrll said:
i downloaded the first one in the same android version i am and tried flashing it but it shows the same error
<ID:0/004> FAIL! (Size)
Click to expand...
Click to collapse
how big is the file? and you might need a different version of odin if its giving you that error
youdoofus said:
no, not the latest, the oldest. The first one in the same android version you were on
Click to expand...
Click to collapse
youdoofus said:
how big is the file? and you might need a different version of odin if its giving you that error
Click to expand...
Click to collapse
well in the end i got tired and remembered what i read somewhere to try to flash PIT and ROM individualy and i did. In the end i only flashed PIT and I booted the phone it and updated it.Everthing seems to work fine.
sorry for causing you so much trouble.
peeaarrll said:
well in the end i got tired and remembered what i read somewhere to try to flash PIT and ROM individualy and i did. In the end i only flashed PIT and I booted the phone it and updated it.Everthing seems to work fine.
sorry for causing you so much trouble.
Click to expand...
Click to collapse
Oh, no trouble at all! I'm just glad that you got it working man!!

Failed when flashing in combination firmware

I was trying to fix my IEMI problem by flashing in COMBINATION_FA60_G935FXXU1AQI2_CL7964511_QB14932435_REV00
and here is the log from odin:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1203)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can someone plz tell me the problem?
What bootloader version do you have now?
I'm not sure how you would fix IMEI issues with combination firmware as most you can do is wipe EFS (Which should never be done) which means you lose your IMEI until it gets reprogrammed.
The only thing you can try is reflashing stock samsung Firmware, other than that IMEI would need to be reprogrammed by flashing box.
I got the same exact log with Samsung J3 Pro... I'm trying to bypass/remove FRP because I can't use that talkback trick... Anybody know?

Downgrade G950FXXU2CRED to Nougat

Hey, i tried to downgrade from G950FXXU2CRED (latest oreo build) to nougat with odin but it shows this:
"<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5617 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Is this the new bootloader stuff problem? Can't i downgrade to nougat?
I think because the latest OREO is bootloader V2 and you can't downgrade to V1.
cannot downgrade to nougat..you must install xxu2 only version
Does any nougat firmware have bootloader v2?
otongniee82 said:
cannot downgrade to nougat..you must install xxu2 only version
Click to expand...
Click to collapse
picaadi said:
Does any nougat firmware have bootloader v2?
Click to expand...
Click to collapse
I think the only other solution is to install the custom roms.
What if we try wih the oem unlock?
ryaneu said:
I think the only other solution is to install the custom roms.
Click to expand...
Click to collapse
ryaneu said:
I think the only other solution is to install the custom roms.
Click to expand...
Click to collapse
Hello,
Ive got the same problem. And I couldn't find a U2 release of nougat...
Could you suggest me some custom rom witch have U2 compatible ?
Thanks a lot

Categories

Resources