Develop Bugs

[Q] Sprint Galaxy S3, Trying to flash Stock ROM, ODIN 3.07, Stuck on sbl2.mbn

I attempted to update my rooted Sprint Galaxy S3 via Kies to 4.3, although it did not finish. My phone was on during the initial running of Kies, the phone went into Download(ing... Do not turn off target) mode (Odin)
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warrenty Bit: 0
BOOTLOADER AP SWREV: 1
After sitting for a substantial amount of time Kies states that it needs to do a Emergency Firmware Recovery, I attempt, but isn't able to do so. Assuming it has a problem working with ODIN MODE, I run the alternative method of flashing the Stock ROM to my phone using ODIN 3.07 (in administrative mode/ Windows 8)
I download the ROM: KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5
I follow the guide for putting the ROM into the PDA spot,
when I select the ROM from my folder it shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
I then Start ODIN:
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
This is as far as it will go.
I've restarted the system and ran it again just as described.
I've reinstalled Samsung USB Drivers
I've looked for another Stock ROM, but the Sammobile.com/firmware downloads aren't available due to the hosting site.
Please, if anyone has had this problem and has fixed it, or anyone that knows why it is stopping at sbl2.mbn contact me here or at [email protected].

dcbstudios said:
I attempted to update my rooted Sprint Galaxy S3 via Kies to 4.3, although it did not finish. My phone was on during the initial running of Kies, the phone went into Download(ing... Do not turn off target) mode (Odin)
ODIN MODE
PRODUCT NAME: SPH-L710
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warrenty Bit: 0
BOOTLOADER AP SWREV: 1
After sitting for a substantial amount of time Kies states that it needs to do a Emergency Firmware Recovery, I attempt, but isn't able to do so. Assuming it has a problem working with ODIN MODE, I run the alternative method of flashing the Stock ROM to my phone using ODIN 3.07 (in administrative mode/ Windows 8)
I download the ROM: KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5
I follow the guide for putting the ROM into the PDA spot,
when I select the ROM from my folder it shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L710VPBLJ7_L710SPRBLJ7_329968_REV03_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
I then Start ODIN:
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
This is as far as it will go.
I've restarted the system and ran it again just as described.
I've reinstalled Samsung USB Drivers
I've looked for another Stock ROM, but the Sammobile.com/firmware downloads aren't available due to the hosting site.
Please, if anyone has had this problem and has fixed it, or anyone that knows why it is stopping at sbl2.mbn contact me here or at [email protected].
Click to expand...
Click to collapse
I would assume its because you're attempting to downgrade. Try this in Odin instead
http://rwilco12.com/Files/Devices/S...0VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.exe

At this point, DO NOT reboot the phone. If you had read the Knox faq, you would know that attempting to flash a < MK3 stock tar will while on the Knox bootloader will immediately brick your phone because the older firmware will not get written. Right now, you need to immediately flash an MK3 full stock tar if you don't want a fancy paperweight.

CNexus said:
At this point, DO NOT reboot the phone. If you had read the Knox faq, you would know that attempting to flash a < MK3 stock tar will while on the Knox bootloader will immediately brick your phone because the older firmware will not get written. Right now, you need to immediately flash an MK3 full stock tar if you don't want a fancy paperweight.
Click to expand...
Click to collapse
The previous gentleman sent me a link to the MK3 update. I tried to run it through ODIN but it just hangs at
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_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

Jessooca said:
Don't use a pit file and don't check repartition.
Use Odin 1.87 it hasn't given me an issue flashing the latest tar file
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Also use a download manager to download the stock tar, that way you won't have a wonky download which sounds like is your case possibly
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What would you recommend as a download manager? If you don't mind me asking.
After running the tar I got from a previous post, a MK3 tar, it gives me:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time passing sbl2.mbn.....but shouldn't it also load sbl1.mbn and sbl3.mbn....i've seen it listed in so many other posts.

Thank you for the tar file. I'm also curious on the the topic...are there more than one Odin? I have Odin3, (some sites refer to it as Odin3, ODIN, or just Odin) versions 1.87 (the one you told me to try), 3.07, and 3.09. I wasn't under the impression that certain versions of Odin worked better for some than others. Do they? And, is Odin and Odin3 different? I appreciate your help on this subject.

Uninstalled the USB drivers then reinstalled them with SGS3 tool kit, swapped to original cable from Samsung galaxy s4,, as well as USB port... It has a status bar on Odin first time .... Hold tight.

IT PASSED!
To be clear for people that have this same problem in the future...
Uninstall Kies, if you have it
Run a registry cleaner, I used CCleaner
Install Samsung Galaxy USB Drivers through SGS3 Toolkit
Use Odin 1.87 in Admin
Use MK3 tar in PDA section, leave auto reboot and reset time
Use original or I'm assuming Samsung USB cable
If one port doesnt work, try another USB port
Thank you everyone for your input and help, folks like you make this site worth using. :good:

Still having the same problem!!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_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> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Did you follow the instructions two posts before yours?
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.

FUNNY!!!!
someone tell me im using the wrong Soft because my phone is "BLUE"...??? i so i tried this one
L710VPUDND8_L710SPRDND8_SPR.zip
and it works...:laugh::laugh::laugh::laugh::laugh:

Trying to get to stock from CM 11 with no luck

Hello!
So i've been failing at getting this SGS4 SCH-M919 back to stock firmware. I have CM11 nightly installed. (This is my bosses phone that i'm trying to get back to stock) So far, I've downloaded two stock firmware images (just in case firs was corrupt) and they both haven't worked.
My process goes like:
-Download drivers (or Kies, i've tried both)
-Set into recovery mode
-Start Odin (i've tried in a few versions)
-Plug phone in
-Odin recognizes
-choose file to flash
-Start the flash then I'll always get this error
<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)
After that, i'm in a little brick mode that I can easily get out of my flashing CWM Recovery on there, and it'll boot me back into CM11.
So, any ideas? I've tried two computers, restarted...idk what to do anymore.
Thank you to anyone who tries to help me!

Looks like you're trying to flash older firmware which will never work if the device has been updated to 4.3 and up.. You need to flash either 4.3 or 4.4.2. 4.3 will work if that was the firmware they had before flashing cm11.. Otherwise you need to flash 4.4.2
Sent from my SGH-M919 using Tapatalk

[Q] Can't ODIN.. please help

Hi guys,
so I've got a Note 2 UK version, which had problems upgrading (had a stock rom).
I so decided to ODIN a new stock rom (4.4.2 UK from SamMobile), which I failed.
It was good until the very last bit - it failed on flashing modem.bin.
I've tried re-downloading the rom, re-booting the phone, and everything I could find to do, but they were all no good.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNE1_N7100BTUFNE1_N7100XXUFND3_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> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried flashing only modem.bin alone, which didn't work, so i guess it's the problem with flashing modem.bin.
Btw, I've tried both ODIN v1.85 and v3,04.
Not sure if this will have an effect, but the sim card doesn't read, so I was thinking that the sim card tray has a problem.
I ordered one to replace it - again, not sure if this makes any difference.
It's now stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.' screen.
I can go into download mode, but nothing else.
Please help!
Thanks

Miracle.vl63 said:
Hi guys,
so I've got a Note 2 UK version, which had problems upgrading (had a stock rom).
I so decided to ODIN a new stock rom (4.4.2 UK from SamMobile), which I failed.
It was good until the very last bit - it failed on flashing modem.bin.
I've tried re-downloading the rom, re-booting the phone, and everything I could find to do, but they were all no good.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNE1_N7100BTUFNE1_N7100XXUFND3_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> system.img
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> recovery.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried flashing only modem.bin alone, which didn't work, so i guess it's the problem with flashing modem.bin.
Btw, I've tried both ODIN v1.85 and v3,04.
Not sure if this will have an effect, but the sim card doesn't read, so I was thinking that the sim card tray has a problem.
I ordered one to replace it - again, not sure if this makes any difference.
It's now stuck on 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.' screen.
I can go into download mode, but nothing else.
Please help!
Thanks
Click to expand...
Click to collapse
Not.sure.if.it will make any difference but the latest roms are recommended to use.odin 3.09

[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.

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