Please is there any way to downgrade or root the sph-720t on android 5.0.1 OH1 Update. I swear I hate this update, and I'm urged to downgrade back to 4.4
maurs4216 said:
Please is there any way to downgrade or root the sph-720t on android 5.0.1 OH1 Update. I swear I hate this update, and I'm urged to downgrade back to 4.4
Click to expand...
Click to collapse
Copy latest SuperSU zip to SD card
Flash TWRP through Odin(uncheck reboot in Odin), disconnect USB, pull battery.
Reboot directly to TWRP
Flash SuperSU zip in TWRP
Boot phone and open SuperSU app to complete rooting process.
mattzeller said:
Copy latest SuperSU zip to SD card
Flash TWRP through Odin(uncheck reboot in Odin), disconnect USB, pull battery.
Reboot directly to TWRP
Flash SuperSU zip in TWRP
Boot phone and open SuperSU app to complete rooting process.
Click to expand...
Click to collapse
I've tried flashing twrp through doing several times with no success. Could it be because I flashed the full update (recovery, bootloader and rom)? I got the update straight from sam mobile
maurs4216 said:
I've tried flashing twrp through doing several times with no success. Could it be because I flashed the full update (recovery, bootloader and rom)? I got the update straight from sam mobile
Click to expand...
Click to collapse
No, that wouldn't stop you from flashing TWRP, what error did you get? Which version of TWRP did you try? Did you try different USB ports and/or cables?
mattzeller said:
No, that wouldn't stop you from flashing TWRP, what error did you get? Which version of TWRP did you try? Did you try different USB ports and/or cables?
Click to expand...
Click to collapse
Yes I've tried different usb ports/cables. Im on windows 8.1 and using odin v3.10. So far I've tried flashing twrp 2.8.4.0 and 2.8.0.0 both this error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried cwm/philz touch and got errors:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltespr.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
maurs4216 said:
Yes I've tried different usb ports/cables. Im on windows 8.1 and using odin v3.10. So far I've tried flashing twrp 2.8.4.0 and 2.8.0.0 both this error:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also tried cwm/philz touch and got errors:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.15.4-jfltespr.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had problems flashing stock using Odin 3.10, give Odin 3.09 a try
mattzeller said:
I had problems flashing stock using Odin 3.10, give Odin 3.09 a try
Click to expand...
Click to collapse
Nah still got the same error on Odin 3.09
maurs4216 said:
Nah still got the same error on Odin 3.09
Click to expand...
Click to collapse
Hmmm, maybe the drivers? I have gone as far as formatted my computer reinstall windows and then reinstalled Samsung drivers just to make sure the computer wasn't the issue, turned out it was. Do you have another computer you could cleanly install the Samsung drivers and try flashing on that one?
King root probably works...
You can try King root and then replace King root with supersu. Check this out... https://www.youtube.com/watch?v=BVvmGs_q6n8
mattzeller said:
Hmmm, maybe the drivers? I have gone as far as formatted my computer reinstall windows and then reinstalled Samsung drivers just to make sure the computer wasn't the issue, turned out it was. Do you have another computer you could cleanly install the Samsung drivers and try flashing on that one?
Click to expand...
Click to collapse
K94U said:
You can try King root and then replace King root with supersu. Check this out...
Click to expand...
Click to collapse
Solved my issue today, and everything is working now! I used odin 1.85 with a samsung usb cable, flash twrp and supersu, thanks for you guys' help tho:good:
Related
Hey guys...
I need a little help from professionnals...I wanted to try a Cyanogen rom, the 10.1.3, a stable one, on my S4. So I downloaded it, I rooted my phone with cf-autoroot with Odin, intalled CWM Recovery. Then I did all the wipes and flashed the cyanogenmod.
Guess what, it didn't work The flash worked well but next infinite bootloop on the boot animation of cyanogen...So I tryied to go back to recovery, mount USB and flash an another rom of cyanogen. And the results was worse, the flash did'nt work at all, if I remember "failed to mount /system" or something similar. And when I tried to restard the phone, nothing happened.
So I wanted to go back to the stock rom to repair this mess. => Download mode then under PDA, my tar.md5 files. Didn't work. I also tried with a PIT file, same result.
I changed my usb cable, the version of Odin, the usb port.
Here's what Odin give :
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I don't know what to do, I tried a lot of things beside all of this. Any ideas ?
THX
Try install STOCK ROM with older ODIN (click here), no the newest version
What stock rom are you trying to flash?
Thanks, but no change...
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Lennyz1988 said:
What stock rom are you trying to flash?
Click to expand...
Click to collapse
This is I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME, official for Europe, 4.3
BeamGG said:
This is I9505XXUBMGA_I9505OXXBMG3_I9505XXUBMGA_HOME, official for Europe, 4.3
Click to expand...
Click to collapse
if you have the secured bootloader (knox warranty void 0x0 in download mode) that means you can not flash old firmware such as MGA. you can flash firmwares MH?, MI? or MJ?.
I9505XXUBMGA = 4.2.2.
Thats probably why the flashing fails.
Lennyz1988 said:
I9505XXUBMGA = 4.2.2.
Thats probably why the flashing fails.
Click to expand...
Click to collapse
I'm such an idiot...I hasd chosen the wrong file...I'm trying with the MJ5 now, I'll let you know
EDIT : Indeed it goes further, but not at the end :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT : I changed the usb port and re-installed the drivers, worked...finally, thx guys !
BeamGG said:
I'm such an idiot...I hasd chosen the wrong file...I'm trying with the MJ5 now, I'll let you know
EDIT : Indeed it goes further, but not at the end :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT : I changed the usb port and re-installed the drivers, worked...finally, thx guys !
Click to expand...
Click to collapse
Only changing usb port and reinstalling solved it?
I have the same issue with ODIN3 3.07.
need4steer said:
Only changing usb port and reinstalling solved it?
I have the same issue with ODIN3 3.07.
Click to expand...
Click to collapse
Hey man,
Sorry for this late answer. Yes, as I said, I only changed the usb port et reinstalling drivers...did it work for you ?
BeamGG said:
Hey man,
Sorry for this late answer. Yes, as I said, I only changed the usb port et reinstalling drivers...did it work for you ?
Click to expand...
Click to collapse
Unfortunately no. Apparently the tar.md5 file I was trying to flash was the problem. The developer released a newer version of it which was flashed okay. Thanks a lot anyway!
need4steer said:
Unfortunately no. Apparently the tar.md5 file I was trying to flash was the problem. The developer released a newer version of it which was flashed okay. Thanks a lot anyway!
Click to expand...
Click to collapse
Cool, you are welcome ! :good:
Hey guys,
I've been having some issues with an international rom on my W8 and i decided to go back to stock with odin. As i was flashing i realized that everytime i would reboot, even after a factory reset, or data/system/cache wipe, all my file and folders were not erased. So i booted into TWRP and wiped internal SD and all the other stuff, then flashed back stock rom with odin and now i keep getting this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910W8VLU1ANJ3_N910W8OYA1ANJ3_N910W8VLU1ANJ3_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<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> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Basically i start flash process and about 30 seconds in i hear the phone disconnect and i get the fail. I know it's not a bad firmware download as i've lready flahsed it 5 times today, i know it's not cable, or USB port because until i wiped internal SD i did not have any issues. Now, i can still access download mode, but i cannot access recovery because it tells me "firmware upgrade encountered an issue. Please select recovery mode in kies and try again." When i connect it to kies, it simply says phone not supported and doesnt show up under emergency recovery.
Anybody know how to get me out of this mess??
weird, my note 4 cable was causing the issue. I took my old S2 cable and it worked. Thanks anyways
I've tried flashing the original Samsung roms on both Windows 7 & 8.1, on Odin 3.07, 3.09, 3.10.7 all failed in the same manner.
Flashing fails as soon as the system tries to flash cache.img.
Code:
<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/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone is the SM-N900 Exynos variant.
h3llb3nd4 said:
I've tried flashing the original Samsung roms on both Windows 7 & 8.1, on Odin 3.07, 3.09, 3.10.7 all failed in the same manner.
Flashing fails as soon as the system tries to flash cache.img.
Code:
<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/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone is the SM-N900 Exynos variant.
Click to expand...
Click to collapse
Udpate your Samsung drivers or simply install Kies 3. Try again then.
Joku1981 said:
Udpate your Samsung drivers or simply install Kies 3. Try again then.
Click to expand...
Click to collapse
I did install both Kies and Kies3, also made sure they weren't running. No avail. :/
h3llb3nd4 said:
I did install both Kies and Kies3, also made sure they weren't running. No avail. :/
Click to expand...
Click to collapse
Maybe is for that. Uninstall both. Only install now Kies 3 and try flash the firmware again.
* Are you sure that is the correct firmware for your device?
Your cache partition is most likely corrupted, just use the correct pit file for your n900 whilst flashing the rom.
Sent from my SM-N9005
Right, the issue was that I didn't flash the correct Pit file. But that's for another time.
NEW ISSUE!
In trying to solve the bad flash, during one of the flashes I checked NAND erase all. Now I just got the phone and have no EFS backups. is there any chance of fixing this? I don't have custom recoveries. Or do I have to send it in to Samsung?
The device boots fine, but I seemed to have wiped the phone's IMEI and baseband. The device can't register sims.
Ok so i was running unofficial cyanogen mod 13 alpha on my s4 9515, and after a while apps started randomly crashing and there were some other problems, so I decided to go back to stock touchwiz rom. I wiped cache and dalvik cache, put the .tar file into PDA in Odin, and Odin sad FAILED, missing pit partition, and after this I can't turn on my phone or go to recovery mode, it just says "there was a problem upgrading your firmware, connect your phone to Kies", which I also did but no luck. I can still go into download mode though...
So can anybody provide me with such .pit file? Or is there something else that I could do? Any help would be greatly appreciated
http://www.sammobile.com/forum/showthread.php?t=27308
In 99% of the cases you won't need the pit file. You just need to use a different usb port / different usb cable.
Lennyz1988 said:
In 99% of the cases you won't need the pit file. You just need to use a different usb port / different usb cable.
Click to expand...
Click to collapse
I tried that pit file already it doesn't work unfortunately. Also tried different usb ports and cables..
srdzenda said:
I tried that pit file already it doesn't work unfortunately. Also tried different usb ports and cables..
Click to expand...
Click to collapse
Can you flash a custom recovery? If so try that, perform a full wipe and flash the custom rom again.
Lennyz1988 said:
Can you flash a custom recovery? If so try that, perform a full wipe and flash the custom rom again.
Click to expand...
Click to collapse
No I can't unfortunately, also tried that already, fails in Odin like everything else...
The closest thing to success was flashing the pit file in the link that you gave me with a kitkat stock rom, it gets almost to the end and then fails
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9515XXU1AND3_I9515ITV1AND2_I9515XXU1AND3_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
srdzenda said:
No I can't unfortunately, also tried that already, fails in Odin like everything else...
The closest thing to success was flashing the pit file in the link that you gave me with a kitkat stock rom, it gets almost to the end and then fails
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9515XXU1AND3_I9515ITV1AND2_I9515XXU1AND3_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
You tried all the usb ports in your pc when flashing with .pit and this rom? The Odin log shows nothing strange so my guess would still be usb cable or usb port.
hi please help me
i have a big problem in my Note 4 Samsung SM-N910C
i was rooting my phone by twrp... after some time i wanna delete root so i enter mY twrp then suddenly
wipe all
1-cach
2- Dalvik cach
3- System
4- Data
5-Internal storgae
6-Micro Sdcard
so i delete the phone system so it is not work again stuck only on twrp and when i try to install N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.zip from sdcard it failed
and when i tried to install from Odin 10 N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_HOME.tar.MD5
give me failed
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
so please how to fix it
My phone stuck only on Samsung note 4
Not sure if this will solve the issue, but read what I put here: http://forum.xda-developers.com/note-4/help/soft-bricked-note-4-n910f-t3306402
Thought I bricked my n910f, and all is good now!
But i do not have any stock frimaware on my phone i already delete the system
webby93
my odin log data
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910CXXU1COH4_N910COXA1COH4_N910CXXU1COH4_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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I didn't either, I completely wiped it.
What i think happened with me is that odin did put the stock firmware on even when it said it failed after like 5 mins. Then the allsamsungrecovery fixed the rest to let it boot up.
The only issue could be that your odin doesn't seem to have got quite as far as mine did. Can you only enter download mode and that's it?
i can enter download mod
but when i select the frimeware stock
The odin data appear log failed
and on the phone appeared : “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
I'm really sorry, I don't think I'll be able to help any further. My knowledge is just from problem solving the few cases I've had to solve my self. Hopefully someone else can help you here.
Just Flash Lollipop 5.1.1 via odin which have coj5 or upgrade bootloader
you can't downgrade from coj5 bootloader you flash coh4 rom therefore you get error
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
flash this rom through odin complete stock and debloted firmware
download from here
https://docs.google.com/uc?id=0B8-hfA9ycQNoazRkV2xjNThWNWc&export=download
Best Regards,