Develop Bugs

Odin wont install stock rom

I tried rooting my Galaxy sIII and it failed, and wont boot.
So per recomendations I found here, I downloaded a stock image for the phone, and every one I try to flash, ends in an error in odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And on the phone it reads:
SW REV CHECK FAIL : FUSED 2 > BINARY 0
HELP!

Bump!
Can anyone help?

BlakDrgn said:
Bump!
Can anyone help?
Click to expand...
Click to collapse
What is your firmware on phone? Did you take last OTA to 4.3?

norbarb said:
What is your firmware on phone? Did you take last OTA to 4.3?
Click to expand...
Click to collapse
Yeah it ota'ed to 4.3 I believe.

BlakDrgn said:
Yeah it ota'ed to 4.3 I believe.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2537910 Read this and some more about 4.3 OTA
http://forum.xda-developers.com/showthread.php?t=2526698

norbarb said:
http://forum.xda-developers.com/showthread.php?t=2537910 Read this and some more about 4.3 OTA
http://forum.xda-developers.com/showthread.php?t=2526698
Click to expand...
Click to collapse
Thanks! reflashed Clockwork mod and the phone booted right up!

Bricked when rolling back from 4.3 to 4.1.2
I got the OTA update 4.3 and it has been draining the battern significantly. So i resorted to revert to 4.1.2 and i think bricked the phone.
This is the error i get from odin when trying to flash 4.1.2
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I see this error in the phone
s3 sw rev check fail: Fused 2 > Binary 0
Now phone does not boot up either. I'm not a android geek - was just trying to get to a older stable version where battery easily lasted for a day...
Saw this thread after i tried to flash 4.1.2 I still don't see a solution posted on how to get the phone to work again...
Please help!!!!!!!!!!!!!!!!!
---------- Post added at 06:41 AM ---------- Previous post was at 06:35 AM ----------
BlakDrgn said:
Thanks! reflashed Clockwork mod and the phone booted right up!
Click to expand...
Click to collapse
Can you please help on how to get this clockwork mod reflashed?

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/

[Q&A] [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/
Q&A for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HOWTO][TAR][OUDHS] THE ODIN THREAD :: Return to stock, fix soft brick :: 5/7/13 MDL. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

i did all this to my s4 but now when i boot it, says Kernel Is Not Seandroid Enforcing, Set Warranty Bit
also when i booted the phone the wifi does not work. could you help with this problem?

Samsung Galaxy S4
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?

Ayaz Gill said:
Is This ''UVUAMDL Official TAR'' for Samsung Galaxy S4?
Click to expand...
Click to collapse
Yes

UPDATE: I fixed the issue while posting this, the solution is included. I am hoping by posting this it may help someone having the same problem, because I spent hours and days trying to solve the issue. Sorry the post is so long.
This is my first post.. I am in desperate need of help!
I have searched everywhere, and cannot find any answers really.
I rooted my M919 at one point, and I could not receive OTA updates.
I do not know if it was rooted when I tried to update it with Odin though.
I was in a hurry (I know BIG mistake) and I never wiped my phone or anything before trying to flash the phone.
I think the phone may not be working because I may have not used triangle away before, but I am not sure if I ever used it. I did the root a long time ago.
I have tried changing USB cords, computers, drivers, md5 files, different Odin versions, flashing PIT file, you name it, I have probably tried it
When I boot the phone the currupt recovery screen shows up. Kies will not recognize the phone.
In the left corner it says:
ODIN MODE
...SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
I can still access "downloading" mode, and it says the same as above.
Odin gives me different errors depending on the file I am attempting to flash
The reason I tried flashing the PIT file is because it would sometimes say
I am not completely sure what update I was using before this all happened, but I think it may have been this one, unrooted?:
CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5
Error codes are as follows:
While flashing 4.4.4 (Odin 3.10)
M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
JFLTE_USA_TMO_16G.pit
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Recovery File I found (Odin 3.09)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/006> Added!!
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
One time I tried using this and it passed!!!
This ONLY works on 3.07 to my knowledge though. It fails on every other Odin
Recovery File I found (Odin 3.07)
JFLTE_USA_TMO_16G.pit
openrecovery-twrp-2.8.0.1-jfltetmo.tar
<ID:0/005> Added!!
<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> 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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The screen is now frozen on the "Samsung Galaxy S4" screen and just shuts off if trying to boot into recovery mode.
If plugged into USB while trying to boot into recovery it launches the recovery file I just flashed!
I went back into download mode, and plugged the phone back in.
I opened Odin 3.07 again, since I had success with the recovery file.
I tried flashing 4.4.4 again M919UVUFNH7_M919TMBFNH7_M919UVUFNH7_HOME.tar.md5
and it failed while only having Auto Reboot checked. I tried launching it with Auto Reboot AND F Reset Time, and it worked!! Hope this helps someone!!

Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks

shaqto said:
Hi DarkMenace - would it be possible for you to send me signed M919 PIT file as well? Thanks
Click to expand...
Click to collapse
Replied to your email. Not sure if I still have it but I may be able to find it if you say it's not there.

alright i did a no no... I tried flashing back to stock odin when my phone was encrypted .. now its softbricked.
everytime i try to flash the stock odin, it always fails at system.img ext4. Need some help guys, its been softbricked for a week. I flashed philz touch twrp on it so I do recovery on it. any ideas?

doesnt work
Bricked my s4/but i had twrp installed to fix it

I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

asmth00 said:
I'm getting a Fail message in Odin over and over. I've downloaded the .zip twice so I don't think it's an issue with a corrupt file... The .dll is in my Odin folder and everything. Pretty confused and today is my last day to send my phone back into T-Mobile before they charge me.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What version Bootloader/Modems do you have now on the phone? If the version you have now has Knox, then you can't downgrade to MDL.
If you are not sure, you can use this free app: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
If the version is MK2 or newer, you can't downgrade to MDL.
You can find newer firmwares either on the SamMobile.com site, or on this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Rob

<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!

In odin, it says 0:[COM4] on the top left
You have 0:[COM3] in your screenshot
Is there a problem or something?Or is it fine?

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me

AziNoapte said:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGH-M919-UVUAMDB-k0nane.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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I get this when i click start
i have a gt-1905 softbricked
please help me
Click to expand...
Click to collapse
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: http://www.sammobile.com/firmwares/
Rob

rlichtefeld said:
If you have a GT-1905 (which I can't find), you shouldn't be trying to flash FIRMWARE for a T-Mobile phone (SGH-M919). That will brick your phone.
If it is an S4, you should be able to take off the back and look under the battery for the model number.
You can flash ROMs, but not firmware between different S4 models. Try finding the FIRMWARE for your phone, and flash that. Also, verify your model, because GT-1905 isn't a Samsung model number.
You can find firmwares here: ------------To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links--------------
Rob
Click to expand...
Click to collapse
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?

AziNoapte said:
i messed up the writing cuz i was scared
I have 19505
I managed to get to 4.2.2 with konane`s guide,got the stock tar but wifi doesnt work on my S4
Can you help me fix it?
Or if it is impossible, can i upgrade to KitKat?
Click to expand...
Click to collapse
Since this forum is for the T-Mobile variant of the S4, and I'm not familiar with the GT-I9505, I would suggest you try the forum for that model:
http://forum.xda-developers.com/galaxy-s4
If you flashed a T-Mobile tar to your I9505, it is probably because of the radio/modem which was designed for the T-Mo model. There should be links in that forum about no WiFi, etc.
Rob

Hello gang. Got a new circuit board installed two weeks ago. Got the phone back, started setting it up, and after about an hour the touchscreen quit working. >8\
I emailed the shop and they said "could be because you're rooted."
Smelled like bull**** to me, but giving them the benefit of the doubt I figured I'd try to flash back to stock. (Which I WAS actually stock, I had the 4.4.4 OTA update, and then rooted and de-bloated.)
Anyway, I downloaded the "Stock firmware" (SGH-M919-UVUAMDB-k0nane.tar.md5) from post 1 in the title thread and flashed it with Odin.
SEEMS to be working, but oddly enough I have a M919UVUFNH7 baseband and bootloader, but Android 4.4.2, which based on my reading, should be impossible?
Also, like several other posters, I have no wifi.
In any event, I am currently downloading the NH7 firmware from sammobile. Says 2 hours to go.
Will try to flash that with Odin and we'll see what happens. Anyone have suggestions in the meantime?

OK - follow-up. I downloaded M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar and flashed it with Odin. Even though Odin said "Boot" and "Modem" in the flashing process, I still seem to have NH7 bootloaders and baseband.
Help?

Well, never mind. I don't care anymore. Tried to replace my glass and cracked the digitizer. Dunno if I'm down to drop another $120 on this thing now.
$300 purchase price
$100 circuit board replacement
$12 glass
Now $120 for a display? I might just call knock it off with this thing.

[2015] ODIN failed flashes reflashing STOCK 4.4.2 - Please HELP :'(

Hi there!
I recently bought a N3N (N7505) :good: for mobile drawing. Since I bought it used, I found KNOX at 0x1 and the 4.4.2 it came with was already annoyingly buggy (lags everywhere, packed RAM & phone app FCs). I did manage to root it through CF-Autoroot (I think?) and even put a custom recovery (TWRP touch v2.8.7.0)
The problem is, everytime I download a ROM from Sammobile (md5 checks confirm undamaged downloads), it fails to flash via ODIN (flashes ALL THE WAY till the end and says FAILED - phone reboots perfectly to previous OS like nothing happened) and I'm wondering if I downloaded the wrong ODIN files, or is there something I'm missing?
So, i'm currently on N7505XXUCNL1 and wondering how I can reflash it (or a similar one) to refresh the phone anew :angel:
ROMz, Y U NO FLASH???
Any advice on what ROM would best suit me to refresh my N3N with???
:victory::victory::victory:Thanks in advance!!:victory::victory::victory:
UPDATE:
When i'm in Download mode, this is the information displayed
ODIN MODE
PRODUCT NAME: SM-N7505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Secure Download : Enabled
KNOX WARRANTY VOID: 1
AP SWREV: (2)
The ODIN log for when I try to flash N7505XXUCNL1_N7505OXXCNL1_TPH is here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The ODIN log for N7505XXUCOE1_N7505SWCCOF1_SWC is here:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now I'm stuck on the Firmware update encountered an issue. Please select recovery mode in Kies and try again

can you provide us the log?

damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
The ODIN failed flash log??
Where do I find that?

damadikaz said:
can you provide us the log?
Click to expand...
Click to collapse
Greetings damadikaz,
I have posted my ODIN logs as an UPDATE on the main post for two separate flashes that both failed.
Any help is greatly appreciated:highfive::highfive::highfive:

Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.

audit13 said:
Try flashing the latest stock ROM from here: http://www.sammobile.com/firmwares/database/SM-N7505/
Looks to me like the flash is failing because the bootloader currently on the phone is newer than the bootloader in the ROM you are flashing.
Click to expand...
Click to collapse
Oh WOW!!! It could be!
Thank you very much:laugh:
Going to download tonight and flash :good::good::good:
Will return with feedback!
Thanks again good sir! :highfive::highfive::highfive:

Verizon Note 4 Will not flash in Odin

Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it

pfcland said:
Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it
Click to expand...
Click to collapse
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?

SirLaughsalot said:
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?
Click to expand...
Click to collapse
Were can i find this post at

ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?

pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting

Bren123 said:
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting
Click to expand...
Click to collapse
Yea it shows it on first boot shows a lock that is unlocked

pfcland said:
Yea it shows it on first boot shows a lock that is unlocked
Click to expand...
Click to collapse
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk

Bren123 said:
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Ok it is gone thanks alot man

Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.

Bren123 said:
Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.
Click to expand...
Click to collapse
it shows Ox1 but i am not worried about it because my phone is paid off

pfcland said:
it shows Ox1 but i am not worried about it because my phone is paid off
Click to expand...
Click to collapse
Oh OK cool.
Sent from my SM-N910V using Tapatalk
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
pfcland said:
Ok it is gone thanks alot man
Click to expand...
Click to collapse
Your Welcome. [emoji3]
Sent from my SM-N910V using Tapatalk

pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sbl1.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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!

droiddude414 said:
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> sbl1.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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!
Click to expand...
Click to collapse
Do this
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
1. Extract odin into a desktop folder
2. Extract the tar from the zip and place it in the odin folder .
3. Place the PIT file inside the odin folder
4. Open odin folder
5. Run odin
6. In the left you should see some menues click on the one that says PIT
7. Now browse for thr PIT file and select it
8. Now Click on the AP button and select the TAR file in the odin folder .
9. Wait for it to load
10. Now make sure the re partition is not check marked .
11. Now click start and it should flash succesfully.
It will reboot and show the lock screen but one you reboot again it should be gone
Hope this helps

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
lugnuttz said:
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!
Click to expand...
Click to collapse
I tried again with the never version of odin and it still does not work for me. This is what I get:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help me get my phone back to kitkat???
I can only flash marshmallow, or now lollipop v5.11, after following the instructions above. I still can't get the kitkat firmware to work.
Please help!

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
thank you, this helped me out when my odin got stuck for 30+ minutes.

I use to have a Note 4 Verizon good cell, but I then change it to a T-Mobile N910T unlock easer to flash them no boot-loaders are blocked, but thats just my saying.

I went through the process ... i have root and i can only install a 5.1.1 rom for the life of me i am unable to flash any 6 or 7 roms ... ideas?

Get write failure
I know this has been a couple years but I am in the same boat . I went through the steps and I get a flash write failure?
It happens after about 40 seconds into
system.img.ext4
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> sbl1.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> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Reverting Note 4 Back to Stock Firmare

I've searched high, and I've search low for firmware for my phone (only to be led to sites whose download speed is atrocious).
My phone model is: SM-N910P
I've been searching for the .tar files for the firmware updates. The MD5 is either not valid by Odin's standard or something else.
Can someone point me along to a link of the latest Note 4 Stock Firmware update from a site that doesn't take all day to download from? Thanks Kindly.
P.s. Yes, I have gone through website and threads posting link to the correct firmware but all of them have not been MD5 correct or worked at all.
I'm also experiancing frequent crashes/restarts on the phone.
I got this phone from a family friend and its been acting weird in ways that are outside my comphrenension. It's rooted and they need it to factory state but all theses errors, problems, slow downloads, are making it near impossible.

Try downloading stock tar from this thread with your PC. You can and should verify the md5 before flashing in Odin when md5 is provided.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N930P using Tapatalk

I flashed the file you linked to and this is what i got in Odin
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1101)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> sbl1.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Write)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

gordonfrohman said:
I flashed the file you linked to and this is what i got in Odin
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
tz.mbn
sdi.mbn
NON-HLOS.bin
boot.img
recovery.img
system.img.ext4
FAIL! (Write)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Questions:
Which stock tar did you flash? (see end of this post)
Does the phone frequently reboot or boot to download mode (reporting) failure to normal boot? Any eMMC failures reported?
Things to check or try if non applicable:
Factory reset in stock recovery if no OS is installed. If you can boot OS, make sure that Settings/Security/reactivation lock is disabled and enable developer mode and enable USB debugging.
Verify correct Samsung driver installed on PC or uninstall and reinstall from Samsung support for Note 4.
Use original Samsung Note 4 cable or replace. A good quality USB data cable should work but if replacing, use OEM replacement.
Run Odin in administrative mode. Try the suggested Odin version (3.10.7 or 3.10.6) or latest version from here: http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
(Odd reported issues sometimes result in one of these reported as successful where various others weren't).
Try another USB port, cable or PC
Edit: All KIES and Smart Switch sessions should be killed prior to starting Odin session.
Do not Odin older stock tars; usable stock tars start at OG5 and up.
Sent from my SM-N930P using Tapatalk