Hello,
I've already rooted my note 4 n910f once and now is unrooted.
But now I want to root again and install a costum recovery with odin but fails!!!:\
"<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
And on the phone appears "SECURE CHECK FAIL : RECOVERY
and qualcomm secure boot enable
MarcosNK said:
Hello,
I've already rooted my note 4 n910f once and now is unrooted.
But now I want to root again and install a costum recovery with odin but fails!!!:\
"<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
And on the phone appears "SECURE CHECK FAIL : RECOVERY
and qualcomm secure boot enable
Click to expand...
Click to collapse
Might be a long shot, but do you have reactivation lock enabled? Someone else was having that problem and that was the cause.
Also double check your files of course and maybe try a different version of Odin
absinthesummer said:
Might be a long shot, but do you have reactivation lock enabled? Someone else was having that problem and that was the cause.
Also double check your files of course and maybe try a different version of Odin
Click to expand...
Click to collapse
Yes reactivation lock is enabled Is there a way to fix this?
I've tried everything else, different cables, odin versions...:\
MarcosNK said:
Yes reactivation lock is enabled Is there a way to fix this?
I've tried everything else, different cables, odin versions...:\
Click to expand...
Click to collapse
Turn off reactivation lock, root your device & do whatever you need to do, then if you want to you can turn it back on. It's a great function but it does prevent modifying devices (for obvious security reasons)
absinthesummer said:
Turn off reactivation lock, root your device & do whatever you need to do, then if you want to you can turn it back on. It's a great function but it does prevent modifying devices (for obvious security reasons) [/QUO
Sorry but I don't know to turn it off :\ lool
Ok It's done Thank you very much
Click to expand...
Click to collapse
MarcosNK said:
absinthesummer said:
Turn off reactivation lock, root your device & do whatever you need to do, then if you want to you can turn it back on. It's a great function but it does prevent modifying devices (for obvious security reasons) [/QUO
Sorry but I don't know to turn it off :\ lool
Ok It's done Thank you very much
Click to expand...
Click to collapse
Sorry I should have mentioned it's under security in settings, but I'm glad you found it
Click to expand...
Click to collapse
Related
Hi all
My I9505, has turned quite weird today... I tried flashing it with latest NEE firmware, but it failed:
<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)
And on the handset I get in red writing:
STAT: [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I can only flash it with:
I9505XXUAMDE_I9505OXXAMD8_NEE
When entering recovery I sometimes get:
"No command" instead of the windows where it sets CSC, sometimes it sets CSC normally
When I try to reset flash counter I get
could not find triangle and counter data
I have also tried flashing with PIT, but that didn't help either...
Any help??
Kind regards
Ratata82 said:
Hi all
My I9505, has turned quite weird today... I tried flashing it with latest NEE firmware, but it failed:
<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)
And on the handset I get in red writing:
STAT: [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I can only flash it with:
I9505XXUAMDE_I9505OXXAMD8_NEE
When entering recovery I sometimes get:
"No command" instead of the windows where it sets CSC, sometimes it sets CSC normally
When I try to reset flash counter I get
could not find triangle and counter data
I have also tried flashing with PIT, but that didn't help either...
Any help??
Kind regards
Click to expand...
Click to collapse
read this
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Click to expand...
Click to collapse
samersh72 said:
read this
Click to expand...
Click to collapse
I have already tried all the steps, many times... This is just driving me insane
Ratata82 said:
I have already tried all the steps, many times... This is just driving me insane
Click to expand...
Click to collapse
it is something to do with bootloader
read this http://teamuscellular.com/Forum/topic/4963-★☞-support-touchwizstock-deodexed-jflteuscr970vxuamf5-☜★/?p=77401 post #51
and this http://forum.xda-developers.com/showpost.php?p=43619724&postcount=479
samersh72 said:
it is something to do with bootloader
read this http://teamuscellular.com/Forum/topic/4963-★☞-support-touchwizstock-deodexed-jflteuscr970vxuamf5-☜★/?p=77401 post #51
and this http://forum.xda-developers.com/showpost.php?p=43619724&postcount=479
Click to expand...
Click to collapse
But then I should be able to upgrade it, it fails with every single rom except the oldest. But looks like you are right
Fixed:
The problem was infact the new KNOX secure bootloader. I just upgradet it to I9505XXUDMH8_I9505OXXDMHA_BTU, and that fixed it.
Hopefully we will soon see a bootloader downgrade for new KNOX security Samsung handsets, nothing is unbreakable
Best regards
Please Explain
Ratata82 said:
Fixed:
The problem was infact the new KNOX secure bootloader. I just upgradet it to I9505XXUDMH8_I9505OXXDMHA_BTU, and that fixed it.
Hopefully we will soon see a bootloader downgrade for new KNOX security Samsung handsets, nothing is unbreakable
Best regards
Click to expand...
Click to collapse
can you please explain, how did you fix it. I am facing the same problem :crying:
You can't downgrade which means flash a previous android version
So just flash the newest android version and you'll be ok
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Remove PIT file and try again.
From Edge of Galaxy Seven
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Not knowing WHAT you are flashing, makes it a little harder to determine what is going wrong.
Go HERE and flash this in Download Mode. This is the latest Stock 935A ROM, This will wipe Everything on the device, and it'll be like it came brand new
norbarb said:
Remove PIT file and try again.
From Edge of Galaxy Seven
Click to expand...
Click to collapse
which is the pit file, sorry for dumb question
Darkboss10 said:
which is the pit file, sorry for dumb question
Click to expand...
Click to collapse
If I remember correctly you need to uncheck PIT in odin and this should help. BTW. What are you trying to flash?
From Edge of Galaxy Seven
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Darkboss10 said:
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Click to expand...
Click to collapse
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
so i do better go with the v4 bootloader and i will check if the pit file is uncheck, what should i put on the re-partition case of odin active or inactive?
by the way thanks for your help
kangi26 said:
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hey i did exactly as you told me , and for first time i guess i have an advance, i still get an error but at least a new error , check it out maybe you know what it is
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
any idea what can be?
i try to flash the G935a...PI2 rom bot without the CSC which i guess is the pit file right?
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
kangi26 said:
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
Click to expand...
Click to collapse
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Darkboss10 said:
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Click to expand...
Click to collapse
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
kangi26 said:
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
if you watch the top corner blue letters it says recovery booting....
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
I'm at a loss man, I'm sorry. I haven't seen that before, I dont get the "Samsung" part when I enter Recovery
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
Can you post screen from download mode?
From Edge of Galaxy Seven
norbarb said:
Can you post screen from download mode?
From Edge of Galaxy Seven
Click to expand...
Click to collapse
There you go . By the way i should mention the phone only turns on download mode when plugged.
Darkboss10 said:
There you go . By the way i should mention the phone only turns on download mode when plugged.
Click to expand...
Click to collapse
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
You need to start by using the latest Odin, 3.12.3 for installing the original ROM. If you try to unlock, you need to go get the PrinceComsy version. PrinceComsy won't work for in-bricking a device, and if you have any of the stock versions of the ROM, you need the 3.12.3 version.
norbarb said:
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
Click to expand...
Click to collapse
I try that . Now i got this error but only on the phone screen and odin is stuck at initialization .. any idea what could be
i download the venom stock rom and the odin file he suggest but that odin is v 3.11.2 , so that was the one that trows me the odin protocol error, i try the same rom but with the v 3.12.3 odin , and it start working but it says fail at the on the recovery image, do that has to do something with my problem that the phone can boot into recovery mode?
here are the logs
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Erase)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
Hello friends please help me I tried to install lineage OS 15 on my note 4 SM N910P and it did not work and since I can not install a system in my phone odin me return the message <ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Removed!!
My phone show this red messages
Error sw rev check fail: [aboot] fused 5> binary 4
[1]eMMC write fail:ABOOT
Please help me
Are you on the QI5 bootloader? If you are, that's most likely the problem.
And are you trying to downgrade? If you are and you're on the QI5 bootloader, it won't work cos the QI5 bootloader is locked.
Samted69 said:
Are you on the QI5 bootloader? If you are, that's most likely the problem.
And are you trying to downgrade? If you are and you're on the QI5 bootloader, it won't work cos the QI5 bootloader is locked.
Click to expand...
Click to collapse
exactly what they said.
i have tried to downgrade and same error
i can still root my phone and run anything for 6.0 based but never going back to 5.1
i have tried to flash an 5.1 rom to a 6.0 baseband and it works fine
howeva you wont b able to use wifi or hotspot so i suggest only 6.0 rom here on out until next phone....
Capturing the bootloader of my phone
Samted69 said:
Are you on the QI5 bootloader? If you are, that's most likely the problem.
And are you trying to downgrade? If you are and you're on the QI5 bootloader, it won't work cos the QI5 bootloader is locked.
Click to expand...
Click to collapse
Hi sir the image attached to this message shows you the bootloader of my phone. Thank you for helping me I do not always have a solution to my problem
durvil1 said:
Hi sir the image attached to this message shows you the bootloader of my phone. Thank you for helping me I do not always have a solution to my problem
Click to expand...
Click to collapse
Screenshot the screen from Settings > About Device.
Screenshot the screen from Setting
Samted69 said:
Screenshot the screen from Settings > About Device.
Click to expand...
Click to collapse
Hi friends the only here are the captures of the properties of my phone it only works with this system since I installed but no network, too many bug and reboots. Please help me :crying:
Hello help me please
durvil1 said:
Hi friends the only here are the captures of the properties of my phone it only works with this system since I installed but no network, too many bug and reboots. Please help me :crying:
Click to expand...
Click to collapse
Hello help me please Hello help me please Hello help me please :crying::crying::crying::crying:
have have tried flashing soo many stocked firmware but it doesnt functions ... my Note 4 sm-n910p shows this error ... Help please
My galaxy s8 has the same message.I'm trying to use Odin to bypass FRP Lock
Samted69 said:
Are you on the QI5 bootloader? If you are, that's most likely the problem.
And are you trying to downgrade? If you are and you're on the QI5 bootloader, it won't work cos the QI5 bootloader is locked.
Click to expand...
Click to collapse
I have QI5 update and get the same error trying to flash older versions. Can I flash QI5 to get back to stock? I can't find a download for it.
Hello guys, first of all thanks for any consideration towards solving my problem. I'm at my first attempt of flashing/rooting a cellphone and I'm going to do so on a Samsung Galaxy S8 (SM-G950W).
Code:
Android version 7.0
Baseband : G950WVLS2ARA1
Build Number : NRD90M.G950WVLS2ARA1
Android security patch : January 1, 2018
So basicly I've been following THIS GUIDE to install TWRP, the steps were to download Odin (Ver 3.12.3), the TWRP .tar file for my phone which should be the SnapDragon one, Samsung Drivers and Samsung smart switch (I guess for a backup?). Developper Options are activated and Usb Debugging is as well. Once I put my cellphone on Download mode, I connect it to my PC, Open Odin and load my img.tar file on the AP slot (twrp-3.2.1-0-dreamqlte.img.tar).
Once I press start I get this error on Odin :
Code:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<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> recovery.img
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And I get a red message on the phone's console saying :
Code:
SECURE CHECK FAIL: recovery
I've been looking around for an answer on google, many and similar issues but I couldn't find the exact same thing so I thought why not ask the experts!
Sorry if it is too much information I'd rather make sure you guys have enough hints to see what I'm doing wrong.
Thanks in advance towards any solution.
You missed the part that says "You need to have an unlockable variant such as Chinese or HK to flash" your canadian s8 is locked, can't flash twrp on it.
peachpuff said:
You missed the part that says "You need to have an unlockable variant such as Chinese or HK to flash" your canadian s8 is locked, can't flash twrp on it.
Click to expand...
Click to collapse
Thanks Peachpuff, so what would be my next step? Is there a way for me to unlock this?
I have to unlock it from Telus (Carrier)?
Frenkz said:
Thanks Peachpuff, so what would be my next step? Is there a way for me to unlock this?
I have to unlock it from Telus (Carrier)?
Click to expand...
Click to collapse
No, there is no way to unlock the bootloader currently on the G950UW. Unlocking the bootloader and carrier unlocking are 2 separate things. This means TWRP / custom recovery is impossible at this moment.
Although root alone is possible, and the way it's done has awesome benefits.
Read here:
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
Slayde.K said:
No, there is no way to unlock the bootloader currently on the G950UW. Unlocking the bootloader and carrier unlocking are 2 separate things. This means TWRP / custom recovery is impossible at this moment.
Although root alone is possible, and the way it's done has awesome benefits.
Read here:
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
Click to expand...
Click to collapse
You just made my life way easier, it actually comes with SU pre-installed!
Thanks a lot for your input and have a great day!
I'll try to give as many details as I can.
Recently I did a root, which worked perfectly fine. Didn't know what I was doing, so I looked around and downloaded Xposed and did all the steps to get it on my phone. After opening it, it asked to download additional firmware or updates or something. I agreed, and the system rebooted once it downloaded what it needed to. Then, when it rebooted, it told me that it was unable to authorize or verify, or something. Essentially it wouldn't let me back into my phone and I didn't know what to do. So I downloaded the most current firmware for my model from Updato, but it didn't seem to work. I tried doing just the AP, then doing the BL-AP-CP-CSC, tried both Home and non home versions as well. After that, if I'm not in download mode, it tries to update software, and then runs a quick string, and then repeats, which I assume is just a textbook case of boot looping.
Information on Download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935U
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0x0
DUALCOMM SECUREBOOT: ENABLE
RP SWREV: B8(2, 1, 1, 1, 1)
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL: [boot] Fused 8 > Binary 1
Click to expand...
Click to collapse
The last line comes after trying to use the AP only
Odin log:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 4797 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Can't post links, but on Updato, under SM-G935U, the first one with 8.0.0 is the one I used.
I tried some suggestions I found looking around, like changing out the USB cable, but ultimately it didn't help and it was fine to use to flash the original root in the first place, and I have Samsung drivers installed.
I would really appreciate some insight. Appreciate it.
sounds like you took an OTA while rooted.
I think you're ODIN flash might be failing because you're OTA might've updated your bootloader.
You need to determine the build you're on from recovery if you can get there and make sure you're flashing a build with the same (preferably) or greater (bad if you want to go back) bootloader. The 5th digit from the right is the bootloader version.
First of all - are you sure the phone got rooted in the 1st place? As your KNOX seems still 0x0 you probably did not modify too much...
Anyway - something to try is to flash the stock with additional PIT file included which rewrites the partitioning from scratch. Try that one