Database Users

[Q] Help unroot GT-I9505. I am unable to flash stock ROM using ODIN.

Help plss. I was caught in a boot loop and unable to enter TWRP recovery mode. I tried to flash the stock ROM but got an error
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)[/B]
<ID:0/003> Removed!!
<ID:0/003> Added!!
Please help!

Mee1122 said:
Help plss. I was caught in a boot loop and unable to enter TWRP recovery mode. I tried to flash the stock ROM but got an error
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)[/B]
<ID:0/003> Removed!!
<ID:0/003> Added!!
Please help!
Click to expand...
Click to collapse
Hi,
Post your problem HERE
Why were you trying to re-partition?

malybru said:
Hi,
Post your problem HERE
Why were you trying to re-partition?
Click to expand...
Click to collapse
I just saw it in an article saying I should do that when unrooting or unbricking my phone. Is it not the proper procedure? im kinda new with android.

Mee1122 said:
I just saw it in an article saying I should do that when unrooting or unbricking my phone. Is it not the proper procedure? im kinda new with android.
Click to expand...
Click to collapse
Hi,
Post in the thread I gave you.
They will tell you what to do.

malybru said:
Hi,
Post in the thread I gave you.
They will tell you what to do.
Click to expand...
Click to collapse
Thanks for taking time to reply. I actually solved my problem with reading a lot here. I just plugged the usb cable at the back of my computer and it worked! now i have a new question and i justed posted it in the link you gave me. Thanks again!

[Q] Having issues booting up my N9005 after a failed 5.0 Official Lollipop Update

Hello, I have tried updating my N9005 to the latest firmware 5.0 provided on Sammobile. After attempting to flash it via ODIN, the following error occurs:
<ID:0/003> Added!!
<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> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Retried this step several times, but i have received the same error.
Following a few instructions found on the XDA forums, I tried using PIT file in order to re-partition.
The phone now reboots but will not go past the first boot screen "Samsung Galaxy Note3 N9005".
I tried pulling out the battery and performing a factory reset (along with wiping caches), but the situation is still the same after rebooting the device.
Also I have noticed that upon accessing "recovery mode", a error stating " Failed to mount /system (Invalid argument)" error is displayed.
I'm pretty new at upgrading phones and I've bought this phone recently and was unaware of the consequences of flashing ROMS via Odin.
The initial fw. on the device was 4.4.2 Official Samsung. Is there any way that I can make the phone reboot normally with fw. 4.4.2? Or any other firmware for that matter?
Thanks in advance.

AndreiRonaldo said:
Thanks in advance.
Click to expand...
Click to collapse
Reflash the firmware again now via ODIN without the .pit file.

Joku1981 said:
Reflash the firmware again now via ODIN without the .pit file.
Click to expand...
Click to collapse
I've tried that several times without success. But the issue was fixed. Apparently the PIT file I was using did not match the ROM i was flashing. I just had to find a matching pair of both ROM and PIT and now I've successfully booted my device. Hope that this thread might help others in need for answers to similar questions.

Alright, this is taking alot more than i had expected, after finally managing to boot my device, I've noticed that flashed rom behaves awfully, my phone is stuttering, and i have no sound. Also, my IMEI is displayed as "Unknown" in the "Status'" section of the device's Settings. Any suggestion on how to fix this issue?

flash the stock the rom you have before

Stuck in bootloop from trying to downgrade from 5.0 to 4.2

As the title says, I tried to downgrade from lollipop 5.0 to 4.2 because I've had several issues and I also wanted to get root. I think part of my mistake was I wiped data/factory reset before I flashed AP. Any help would be much appreciated, as I have been at this for the past five hours. I added some info below that might help below. Thanks
- I cannot boot into recovery and get the message (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again)
- CP is the only thing that will flash and CSC also fails
- model number is g900a AT&T
- I have used Odin 3.10.7 and 3.09, but no luck
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persist.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk

Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies

VoltexYT said:
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
Click to expand...
Click to collapse
Kies and kies3 are both not recognizing my device. I heard it could be because of usb debugging, but I can't boot into my phone to check.

Allek84 said:
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Both kies and kies3 are not recognizing my device.

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!!

Back to stock from Beta One UI on the GS8

Having a difficult time here.... I've got a Galaxy s8 Sprint variant.. I downloaded the Beta one UI firmware, not official just used ODIN. I'd like to go back to stock and update to newest official release, or just go straight to the latest release. I don't care if it's rooted/unlocked or whatever just stock Sprint software. I've tried a couple of stock firmwares but I keep getting errors in Odin. Currently I"m on PDA G950U1UEU5ZSAB CSCG950U1OYM5ZSAB .
Any pointers would be greatly appreciated.

tri0xinn said:
Having a difficult time here.... I've got a Galaxy s8 Sprint variant.. I downloaded the Beta one UI firmware, not official just used ODIN. I'd like to go back to stock and update to newest official release, or just go straight to the latest release. I don't care if it's rooted/unlocked or whatever just stock Sprint software. I've tried a couple of stock firmwares but I keep getting errors in Odin. Currently I"m on PDA G950U1UEU5ZSAB CSCG950U1OYM5ZSAB .
Any pointers would be greatly appreciated.
Click to expand...
Click to collapse
What errors are you getting with Odin?
What firmware are you trying to flash?

spawnlives said:
What errors are you getting with Odin?
What firmware are you trying to flash?
Click to expand...
Click to collapse
I'll cut and paste it.. but the phone says SW REV CHECK FAIL : {ab}{FUSED 5 > Binary 2
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

tri0xinn said:
I'll cut and paste it.. but the phone says SW REV CHECK FAIL : {ab}{FUSED 5 > Binary 2
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
2 things I can see
1. Use Odin version 3.13.1 it supports the new compression format of newer firmware.
2. The software check fail is due to trying to flash older firmware than what is on your phone. You will need to download firmware with a bootloader version 5 ( 5th number from right of firmware(PDA) name ).

OP can you confirm if it worked?

Hey, THanks a ton.. worked! I don't think I woulda figured that out unless I would have happened to tried a rom with the correct bootloader version. Really appreciate it. One more thing.. which should I use normally.. the home_csc or the csc. I've been using the home one since that's what I see a majority of people using but I don't see any explanation.
thanks again!

tri0xinn said:
Hey, THanks a ton.. worked! I don't think I woulda figured that out unless I would have happened to tried a rom with the correct bootloader version. Really appreciate it. One more thing.. which should I use normally.. the home_csc or the csc. I've been using the home one since that's what I see a majority of people using but I don't see any explanation.
thanks again!
Click to expand...
Click to collapse
Glad you got it sorted
Home_CSC - will keep your apps and data.
CSC - clean install same as a factory reset.