Develop Bugs

error when flashing ROM via Odin

hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Mashari_F said:
hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Have you tried to use an other usb port?
2) do you use the original usb cable?
3) do you have all the samsung drivers installed?
4) make eure that samsung kies is not running in the background
Hope it helps you
Gesendet von meinem SM-P600 mit Tapatalk

Got the same problem, so recovered it from kies
Skickat från min SM-P605 via Tapatalk

Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.

ronaldphl said:
Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.
Click to expand...
Click to collapse
Is it giving you a FAIL after flashing , or doesn`t show up after a successful flash.
If it doesn`t show up after flashing , re-flash but untick "Auto-Reboot" within odin before flashing & restart manually after flashing.

I have a "Fail after flashing" - complete (Write) - operation failed in Odin

Which odin
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck

FSkyman said:
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck
Click to expand...
Click to collapse
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well

Recovery Flashing
ronaldphl said:
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well
Click to expand...
Click to collapse
Now I am confused are you talking about recovery or rom ?
The only recovery I could get to work was the TWRP - this Zip file comes with a Odin that works.
Cwm philz are not working.
But keep in mind as soon you installed twrp your knox counter is tripped.
For rom flashing you have to wipe your tablet and then follow these instructions xxxx://www.droidgator.com/update-galaxy-note-101-sm-p605-android-43-xxubmj9-firmware/.
Before starting backup your tab then everything should be fine.

Thanks for your effort in helping me out...
Before I sent my tablet for servicing... I restored the tablet with Kies to the original factory setting and rom as I HAD rooted my P605 and flashed a custom rom before. [Although the Know count is 0*1 anyway.... but the service centre was kind enough to fix my tablet as it's a hardware failure instead of anything to do with the ROM ]
When I got my tablet back and tried to flash the TWRP into it, this problem surfaced. And I read from another post that some say flashing a Samsung original rom could help I tried but to no avail. Still I am waiting and looking for a solution.
I tried Odin 3.04 3.07 and 1.85 with the two versions of TWRP but still none of them work.

Cant flash Stock firmmware
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3

aelaan said:
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?
Click to expand...
Click to collapse
Although it failed, I was able to recover using kies and use tablet as normal without data loss. It might be because at that point I had not rooted my tab and system state was still original in odin.
By the way I was on MJ4 xsa(AUSTRALIA) trying to install NC2 TGY(HONG KONG).
Now I have rooted it and have I installed NC2. I am still not sure what the issue was. But the only thing I did different was, first was using a virtual machine, but now did in an actual windows machine.
Can you please try this? If you can, install back NC2 using odin. Boot it once, then try recovering using kies. Kies recover mode gets your latest firmware based on your serial number. Not what firmware you are running.
Please post back the result. Interested to know the outcome.
Sent from my SM-P605 using XDA Premium 4 mobile app
---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------
Khazaad said:
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3
Click to expand...
Click to collapse
I don't think it is. Although the specs are the same, read somewhere that the internal partition structure for carrier branded firmware are different to generic. Don't remember where I read that. But can't confirm that either.
Sent from my SM-P605 using XDA Premium 4 mobile app

can't flash stock rom on Odin, stacked !! help!!!

Hi all, so I installed the cyanogenmod's new update, I used its in the system update, thought it will be pretty safe just like a stock android update, but then my phone stuck at boot screen. and I really don't have time to mingle with the system right now. I need the phone like 3 hours ago!! i downloaded the stock rom and try to use odin to flash it. then it gives me this error message.
I tried, change the cable, change usb port, change odin version, but nothing works so far. (((
Please help !!
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.

audit13 said:
You have the 4.3 bootloader on your phone? If you do, you can't use Odin to flash a stock ROM because it may brick your phone. You can only use Odin to flash a 4.3 stock ROM that had specifically been compiled for use with Odin.
Click to expand...
Click to collapse
Is there a 4.3 rom we can flash with odin? I attempted (stupidly) to flash stock after a CM11 nightly caused a bootloop and would not allow me to enter recovery. All I can do for the moment is enter download mode. Every rom I try to flash I get the same error along with the error on my phone reading:
SW REV CHECK FAIL : Fused 2 > Binary 0
Is there anything I can do?
EDIT: Finally found a fix. I flashed a rom from this thread.
http://forum.xda-developers.com/showthread.php?t=1980683
Just go to their website and download the file for your specific model. After flashing my phone booted up in CM11 (what I previously had installed) but it crashed upon loading the lockscreen. Luckily I could enter recovery mode and do a factory reset. This fixed everything!

[Q] Internal Storage 0MB. Can't flash anything via Odin

Hey everyone.
I'm helping fix my friend's GS3 (SGH-i747). He said that he ran out of battery, and then went into a bootloop. He's running on one of the CM Nightlies from a while back.
We've tried to wipe cache, dalvik cache, factory reset, etc, but nothing works because internal storage fails to mount. I've tried flashing stock via Odin, but with no success. When I flash a recovery however, it says it was successful but when I boot into the phone, I still have the old recovery.
The phone is on TWRP. When I go into "mount", internal storage is shown having 0mb. I cannot click on anything else (data, cache, etc) except system and external sd card (when it is present).
I've tried flashing the CM zip that was on the external SD card but had no success either.
No idea what to do from here. Any help would be appreciated. Thanks!

What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?

!
audit13 said:
What error did you get when you tried to flash back to stock in Odin? Did you try flashing CWM?
Click to expand...
Click to collapse
I get "NAND WRITE START!!" and then FAIL. It shows that the phone is connected to my PC. I've tried flashing CWM. It says it's successful, but when I boot into recovery, the recovery is still TWRP.

I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097

audit13 said:
I wonder if the partitions are all messed up. Do you have the PIT file for the phone?
Some information about PIT files: http://forum.xda-developers.com/showthread.php?t=999097
Click to expand...
Click to collapse
I kinda figured that too. I tried flashing a pit file for the sgh-i747 16gb alongside a stock ROM but nothing happened. How should I go about finding one for the phone?
Btw, the internal storage was already at 0mb before I tried flashing a pit file.

Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068

audit13 said:
Maybe try booting the phone using the debrick method.
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I'd try it but I don't have access to a 16GB or higher SD card. How do I go about getting a pit file for the phone?

Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2

audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Thanks for the link. To be sure, I flash this along with a stock rom right? Is there a specific stock rom that I have to use? I got one from Sam Mobile.

audit13 said:
Try here: http://forum.xda-developers.com/showthread.php?t=1848264&page=2
Click to expand...
Click to collapse
Here's the log in Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> 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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
That's what I usually get.

Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.

audit13 said:
Do not use that file. You are getting the error because you are trying to flash an older bootloader and it stops after trying to install about.mbn.
Click to expand...
Click to collapse
Should I flash stock 4.3 then? Unless this phone has Kit Kat (I think the CM version my friend was using is Kit Kat)

The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.

audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Pretty sure that I had put Stock 4.3 at one point. Thanks for the info, I'll try finding a stock 4.3 for Odin and report back.

audit13 said:
The cm version doesn't matter, it is the bootloader version that matters.
What was the last stock rom on the phone? If it never had stock kk on the phone, you can try stock 4.3.
Click to expand...
Click to collapse
Okay so I tried flashing stock 4.3 and Odin fails at system.img.ext4
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
I got the stock 4.3 from here: http://www.androidayos.com/samsung-galaxy-s3-stock-firmware/
I tried the .pit file included in that as well as the .pit file from the other thread you linked.
Also, the phone was on CM11 4.4.2 before all of this happened. No idea if that makes a difference, but if I recall correctly, the phone did have stock 4.3 at one point.

If you manage to get the thing booted then you might want to run a memory test to see if all the nand is still good

Did you check re-partition?

audit13 said:
Did you check re-partition?
Click to expand...
Click to collapse
Yep

I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660

audit13 said:
I don't think there was a stock ATT 4.3 ROM which is why a thread was made to create a 4.3 ROM that could be flashed. ATT released their 4.1.2 and 4.3 ROM as OTA update.s There is no 4.1.2 or 4.3 ATT ROM available on sammobile.com.
This thread was started for the purpose of restoring a stock 4.3 ATT ROM: http://forum.xda-developers.com/showthread.php?t=2722660
Click to expand...
Click to collapse
Yep, I downloaded that exact one and I get the error. What should I do now?

[Q] Phone SoftBricked in the middle of the night, help!

I haven't done any ROM updates for a couple of weeks, and I was sound asleep when the phone rebooted. It sat 'rebooting' for two hours before I woke up.
I'm able to reboot into Download Mode, but have been unable to install anything that has worked. I tried flashing both TWRP2.7.0.0 and the stock ROM, but neither have worked. TWRP is still showing as 2.6.3.1 on my phone, and I get a failure when loading the Stock rom that looks like this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUFNH2_I747MOYBFNH2_I747MVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm also able to boot into Recovery mode, but it appears that the phone is encrypted (it asks for a password, even though I've never encrypted it!) and when I try to factory reset or wipe dalvik or anything else, I get: E: Unable to mount '/cache'
Can you help? Phone is a rooted SGS-I7474M on Telus, and was running Slim 4.4.4 build 7.0 Official 5979. I'm using TWRP as my recovery.

Maybe try loading a stock from image using Odin? You can download the stock images from sammobile

Tony_YYZ said:
Maybe try loading a stock from image using Odin? You can download the stock images from sammobile
Click to expand...
Click to collapse
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!

hardidu said:
I think that's what I've been doing? I've downloaded this stock firmware: sammobile.com/firmwares/download/34793/I747MVLUFNH2_I747MOYBFNH2_TLS.zip/ and then tried loading it via ODIN?
Perhaps I'm missing something... Appreciate your thoughts!
Click to expand...
Click to collapse
Oh, my mistake. That's what I was suggesting. Sorry...I don't know what else to try.

What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.

audit13 said:
What bootloader is on your phone?
You're trying to alter the bootloader which is causing the error after trying to flash aboot.mbn.
Click to expand...
Click to collapse
You've lost me... I have no idea. I don't think I've ever touched the bootloader unless that's packaged with Slimkat or TWRP,
How do I find out and what's my next step?

<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.

audit13 said:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
The aboot.mbn file is a bootloader that Odin is trying to load onto your phone. but the current bootloader is preventing this because the bootloader your are trying to load is not compatible with your phone or the current bootloader is newer than the bootloader Odin wants to flash.
Does your phone still boot into download mode? You're sure your phone is an i747m (Canadian version of s3)?
If your phone can boot into download mode, I recommend you flash the latest version of Philz Touch for the d2lte, copy a custom ROM to your external SD card, boot into Philz, and flash the custom ROM so you can at least get your phone booted. Once booted, install the Samsung Phone info app. This app will tell you the baseband and bootloader on your phone.
Click to expand...
Click to collapse
I tried loading I747MVLDLK4_aio.tar.md5 and here's the log from the fail I ended up with:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLDLK4_aio.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Loading Philz also failed.

Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.

audit13 said:
Are you flashing the latest Philz tar.md5 file? You can't flash the zip in Odin. You should be able to flash the Philz zip in TWRP.
Click to expand...
Click to collapse
I was using Skips Toolkit to try and load Philz... I'll try using TWRP

Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.

audit13 said:
Flash Philz tar.md5 in Odin or the zip in TWRP. I prefer not to using any tool kits.
Click to expand...
Click to collapse
The process all looks good, log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-d2att.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
But still boots with TWRP... despite a PASS in Odin.

Samsung S4 restarting and not going to main screen

i have a Samsung S4 that i bought from a friend of mine couple weeks ago. It was working fine until recently it starting doing this:
https://www.youtube.com/watch?v=ZjJH...=youtu.be&hd=1
As you can see it boots up but doesnt go to the main screen and then restarts. I hard resetted it. I tried to install stock rom using odin but i get an error and it fails. Its a Samsung M919 from tmobile. I have no idea how to fix it. I tried different battery but same problem. I would really appreciate some help.
i downloaded the rom here: http://galaxys4root.com/galaxy-s4-stock-firmware/
this is the error i get with Odin. I tried different usb cables and computers but same error
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNB4_M919TMBFNB4_M919UVUFNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> aboot.mbn
<ID:0/017> NAND Write Start!!
<ID:0/017>
<ID:0/017> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/017> Removed!!
Thanks

can somebody please help

You trying to flash an old firmware, you need current stock kitkat 4.4.4 and updated Odin 3.07 with a factory reset before flashing.
Look in general section for ShinySide stock firmware.
Pp.

PanchoPlanet said:
You trying to flash an old firmware, you need current stock kitkat 4.4.4 and updated Odin 3.07 with a factory reset before flashing.
Look in general section for ShinySide stock firmware.
Pp.
Click to expand...
Click to collapse
thx for your reply. So i got Odin 3.07. Is this stock rom u talking about: http://samsung-updates.com/device/?id=SGH-M919. So all i have to do open ODA and put this into PDA and start?
i thought stock meant going back to the origal firmware wht the phone came with which would be androind 4.2?
also is there a better download link where i dont have to wait 6 hours?
thx

You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.

PanchoPlanet said:
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
Click to expand...
Click to collapse
whts the difference between NK2 and NH7?
thx for all your help so far

PanchoPlanet said:
You can download from here http://forum.xda-developers.com/showthread.php?p=54155517 using your laptop.
The latest stock nk2 firmware and return to stock, this will fix whatever is borked.
Using latest Odin in pda slot.
Run phone for a couple of days and make sure everything works properly.
Then take chances with custom roms after making a proper backup in case something goes wrong.
Pp.
Click to expand...
Click to collapse
it failed again.
i followed all your steps:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Where you able to do a factory reset?
Can you access recovery stock /custom?
What rom was running on phone before first flash attempt?
Was phone running properly when you got it?
You sure it's a t-mobile version M -919?
What color is the phone?
Pp.

PanchoPlanet said:
Where you able to do a factory reset?
YES
Can you access recovery stock /custom?
Not sure what you mean?
What rom was running on phone before first flash attempt?
I have no idea as i am not into flashing or installing "roms"
Was phone running properly when you got it?
Yes
You sure it's a t-mobile version M -919?
Yes as it says on the back of the phone
What color is the phone?
Black
Pp.
Click to expand...
Click to collapse
....

If you can start phone by holding volume up and power do you get a custom recovery or a stock recovery?
If you have a custom recovery , look for "back up and restore" check restore for nandroid and try installing nandroid.
If a stock recovery try wipe data/factory reset from recovery.
First image is custom recovery
Second image is stock recovery.
Pp.

PanchoPlanet said:
If you can start phone by holding volume up and power do you get a custom recovery or a stock recovery?
If you have a custom recovery , look for "back up and restore" check restore for nandroid and try installing nandroid.
If a stock recovery try wipe data/factory reset from recovery.
First image is custom recovery
Second image is stock recovery.
Pp.
Click to expand...
Click to collapse
I see stock recovery and i already tried wipe data/factory reset many times but same problem