Database Users

Accidentally deleted my System folder SGH-M919

Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.

titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!

titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app

fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!

titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.

[Q]Flashing Lollipop help

i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything

Is your device unlocked or branded?

Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...

billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.

Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a

i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.

Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10

billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?

Have practically the same situation...
The furthest I've got is the following
Code:
<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> aboot.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.

Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.

Soft brick after official Nougat update

Hello, so I'm having a huge problem right now, that seemingly came out of nowhere.
My phone is stuck on "Samsung Galaxy S7 Edge" screen logo and can only enter download mode, nothing else.
All I did was download the firmware update that popped up OTA. Something must have failed and I was greeted with a permanent freeze on that part.
The update that I've downloaded was called - G935FXXU1DQB7/G935FSEB1DQB2/G935FXXU1DQB3 with the file size of 1224.14 MB
It has failed once before but it wasn't a brick. Said something about mounting data error in a recovery mode. A day later I've tried to re-download and install the update again and this is the place I'm in right now.
My phone is the European Exynos variant, not sim locked. I'm from Lithuania, but I somehow doubt my model had the Baltics firmware as I don't think the 7.0 is released there yet.
So far I've tried installing stock firmwares from UK, Poland, Baltics region. Both 6.0.1 and 7.0 yield the same results. Different Odin versions. I can confirm that the USB ports work and there is a connection, because flashing a single random .tar file passes and reboots the phone., but does nothing for me (like installing extracted hidden.img.tar). Ends up at the same splash screen.
Every attempt to flash anything has to be with the download mode rebooted or else it doesn't do anything. (Maybe this is normal)
All threads completed. (succeeded 0 / failed 0)
When I flash the AP, BL, CP, after a while (a minute or so) I get a fail without seemingly any progress.
Complete(Write) operation failed
Usually hangs on the recovery.img, depending on what I try to flash.
When I flash CSC, Pit file, or leave a ticked repartition box without including any of them, I instantly get
Re-Partition operation failed.
So naturally this always triggers if I flash all 4 of the items.
I have also tried Smart Switch. The only problem is I currently don't have my S/N number, because some internals and all of the outside of my phone was changed under the insurance, including the back where I believe the number is found, so I've tried S7 Edge S/N number of a friend of mine. I believe our phones are different, because his firmware is from Baltic region (SEB) which doesn't even have 7.0 out. I'll try getting my S/N number through the carrier I bought the phone in. Anyway, Smart Switch throws an error about "Failed to recognize software update mode" after downloading the (SEB region) firmware and stops there. I'm afraid even my own S/N number won't help.
This is what my download mode says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWAEV: B:1 K:0 S:0
I feel like all of this mess is caused mostly by the Factory reset prevention lock?
I don't want to trip Knox and void the warranty by installing a custom recovery, which would maybe help me? Does anyone have any ideas? I'm at this for like 10 hours already and desperate. Hope I don't need to give it in. No ability to even turn off the phone, what BS is this...
Can't post images yet, sadly.

same here. but for me now odin say:
<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> 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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

bassini said:
same here.
Click to expand...
Click to collapse
greenman from sammobile forums suggests
that "This is looking like you have a damaged emmc. The re-partition should have been successful."
I think we're out of luck on this one. The only strange thing is that we've probably installed the same piece of software that killed it. What are the odds?

Rakanoth said:
greenman from sammobile forums suggests
that "This is looking like you have a damaged emmc. The re-partition should have been successful."
I think we're out of luck on this one. The only strange thing is that we've probably installed the same piece of software that killed it. What are the odds?
Click to expand...
Click to collapse
For me it was a newest XEO firmaware.
And also its after trying re-pa...

[VIDEO GUIDE] How to root and install TWRP - Android 7.0- Galaxy S6 multiple variants

Hey everyone,
This guide should make it very easy for anyone to root and install a custom recovery (TWRP) on basically almost any S6 variant. You've got all the download links in the video description as well.
It works on all Android 7.0 stock versions, including the latest ones (with the most recent security patches).
Everything is very clearly explained, with step-by-step instructions in the video below. Just make sure you download the correct TWRP tar file for your S6 variant.
https://youtu.be/BV1ELmu8T0I
Enjoy!

Here is just the same but in really short (because that isn't so complicated) And here are also useful links to get latest drivers, stock firmware, ROOT, TWRP etc.
rifek4 said:
http://cdn.droidviews.com/wp-content/uploads/2015/03/Odin3_v3.12.7.zip Odin 3.12.7 (latest)
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 SamFirm 0.3.6 (latest)
http://samsung-usb-driver-for-mobile-phones.en.lo4d.com/download Samsung USB Drivers 1.5.63 (latest)
Install latest USB drivers, unpack lastest Odin3 and SamFirm. Use SamFirm to download latest firmware for your model, so put "SM-G920F" in "model" check "Auto" under that, put CSC code for your country in "Region", download it and then just flash it in Odin
Here you got full CSC codes list and also short guide how to use SamFirm
https://www.androidsage.com/2017/07...specific-product-code-csc-and-country-region/
How to root then? > CF-Auto-Root
How to get TWRP then? > latest TWRP
Customize? > Look my signature
Click to expand...
Click to collapse

rifek4 said:
Here is just the same but in really short (because that isn't so complicated) And here are also useful links to get latest drivers, stock firmware, ROOT, TWRP etc.
Click to expand...
Click to collapse
Thank you so much for responding, but unfortunately l it does not have my version which is the (SM-S906L/TFN) variant it works but straight talk but when I booted it up it said Tracfone so the region I put TFN and the model number (SM-S906L) and I can't find it. I have the firmware for my phone so as this is much not a problem. What is a problem is when I do flash the stock firmware in odin is that i run into sboot.fail and cm.bin fail, and the only way is to delete them from the .tar file and rezipping them into another .tar without the sboot/cm.bin, and NO matter what I flash either if is a successful rom flash in twrp or what I just said in odin I ALWAYS come back to a boot loop. I'm starting to think my phone is dead idk what to do.
Error: <ID:0/004> Odin engine v(ID:3.1101)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Odin engine v(ID:3.1101)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Halp

I hate to ask, but i've been going over every post i can find in the forums, including this one, and i think i am scared to ask this but.......Does this not work for the G920V Verizon variant? i keep looking everywhere online but it seems like none of these methods work for that Variant, but no one has said that it wont work on that one specifically, was hoping maybe you can confirm or deny if it works on the Verizon variant? thank you in advance.

KNOX
How about KNOX? Will it flip the flag?

rifek4 said:
Use search option or Google is your friend.
Click to expand...
Click to collapse
Looks like you're the one who can't read. He clearly stated that he read everything he could find and all he got was conflicting information. If you don't have the answer, don't post anything. If you have the answer and can set the record straight, then please do. Thanks.

rifek4 said:
I answered on same question for few times before, and I won't do it any more because I don't like to repeating my self. Answer on he's question is in thousends places on that forum, if he only would to like use "Search Option" here little bit above on right corner, and type there "ROOT S6 Verizon" or just "ROOT G920V" he will have answer for him question even confirmed not once! My first shoot in search engine, that thread : https://forum.xda-developers.com/ga...-auto-root-t3056630/post73993971#post73993971
For example here on few last pages is many posts with answer to him.
P.S.
Please don't let me starting next time.
Click to expand...
Click to collapse
Is this what you call an answer?
---------------------------
Quote:
Originally Posted by NizzoFoShizzo
I thought SM-G925V verizon model doesn't allow this method because it doesn't have the oem unlocking option in the developer options.
Just flash CF-Auto-Root for your model (is avaiable), then you can easy flash also TWRP without problems with OEM Unlocking. After that do all what you want
---------------------------
Because I'm quite sure you're wrong. Just because there's a CF-Auto-Root image for the device for a particular build number, it doesn't mean it's gonna get past the locked bootloader. I got CF-Auto-Root from here https://desktop.firmware.mobi/device:841/firmware:2970 for my G920V 6.0.1 build CPK2. Tried to flash with Odin, and it failed right away. On the device, on the downloading screen, it says "Secure Download : Enabled", and once I try to flash, it says "SECURE CHECK FAIL: (RECOVERY)".
Also, the CF-Auto-Root README.txt clearly says: "Your device must have: - An unlocked bootloader, - OEM unlock enabled (if present) in developer options, - Factory reset protection (if present) disabled".

I was going to write a long post about all the things I tried on the Verizon phone that din't work, including mihaixp and rifek4's suggestions (things that worked fine on G920F), so I'll just say: "No, there is no root for Verizon phones", and leave you with this: https://forum.xda-developers.com/verizon-galaxy-s6/help/current-root-method-verizon-s6-t3647371

rifek4 said:
Here is just the same but in really short (because that isn't so complicated) And here are also useful links to get latest drivers, stock firmware, ROOT, TWRP etc.
Click to expand...
Click to collapse
Plz Guyz Help!
I just installed twrp in my SM-G925l & directly boot into recovery , after that i did factory reset, advanced wipe(dalvik/ART cache, system, data, internal storage, cache) and than i was going copy the Rom Files via MTP but it says "can't copy files, the Device either disconnected or stopped responding" .
I don't have a external usb drive so can't try that.
Plz guyz, help. What to do now.

rifek4 said:
Yes... So true... For G920V with 6.0/7.0 I think isn't any avaiable way to ROOT. I never had Verizon and never looking for any post with informations about it, but from that what I know possible was S6 Verizon (G920V) ROOT but on Lollipop (5.1.1) ROM's only.
Click to expand...
Click to collapse
and yet here you just answered the simple question i asked in the first post you replied to, so thank you , but even though you say this, other posts seem to make me believe it is possible.
But just in case, here is what i have tried so far, maybe some other option i am not seeing in my searching has come up that you might know?
First i was trying to root via the method mentioned here....http://rootmygalaxy.net/root-samsung-galaxy-devices-using-cf-auto-root-odin-tool/
This method kept failing me however on the first box, not the green pass as is expected. I also in my searching found this thread about locked bootloaders... (crap my window crashed with the link and now i can't seem to find it, grr) anyways, there was talk of unlocking the bootloader to solve the problem....which lead me to this thread...https://forum.xda-developers.com/verizon-galaxy-s6/general/root-nougat-s6-verizon-t3710864
And i used that method, and everything went and worked as expected however i did not achieve the SuperSU that i expected to see int he app drawer in the end, so something didn;t work.
which lead me to this thread...https://forum.xda-developers.com/ve...20vvrs4dqd1-odin-nougat-7-0-firmware-t3597007 to get myself the firmware needed for this method here...https://forum.xda-developers.com/ga...-auto-root-t3056630/post73993971#post73993971 and this post ...https://androidmtk.com/root-samsung-galaxy-s6-sm-g920v which was again just the CF Auto Root that failed the first time around.
So i feel like a giant game of round robin here.
I really don't want to drop to a lower version of Android to root the unit (and i also feel it really wouldn't matter what version at this point) but if that is my only option i might just try it, but so i kindly ask again, after clearly using the search function on the forum to look for methods, has anyone had luck with the Verizon variant S6 920V on Nougat getting root to stick and if so, can you please point me to the method you used on the forums, because all the methods i keep finding circle back to the CF Auto method that keeps failing time and time again. Thank you in advance.

So will this be triggering KNOX or not?

Could anyone please tell me whether Knox will be triggered or not

Hello, I tried this method, everything was OK, i got pass in ODIN app, then tried to reboot and now nothing is happening, i think device is bricked, but I made everything as you have described in video. Now when I try to hold volume UP + home + lock buttons, galaxy s6 logo pops up, the side buttons just flash and nothing happens. Could you please, help me?
Edit: I can enter download mode
Edit2: false alarm, I just installed wrong TWRP

HELP - I just wanted to install a stock Samsung S7 OS downgrade...

Hey Everyone,
I've been reading up on the forums but I'm willing to admit I now need more direct help.
I have a Samsung Galaxy S7 andI wanted to downgrade the OS back to Nougat from Oreo so I could spoof on Pokemon go. I move all the files I'm interested in keeping to a new handset (so the handset being worked on is not my primary one, it's expendable, so I didn't bother backing up).
I started trying to learn to flash an older OS. I quickly came across TWRP and Odin. I tried several times to flash with Odin, but I gather that Odin doesn't allow downgrades, and I couldn't find an OS in the correct format anyway. I discovered that to downgrade you have to use TWRP. So I use odin to install TWRP and learn to use it (on a basic level)...
I found a stock OS post on this forum and downloaded it, and tried to flash it with TWRP as directed by the poster. Well that didn't work, it went through the flashing process, errored and then turned itself off, tried to turn itself back on and hangs at the samsung logo. It seems I managed to completely wipe the OS off my phone. Luckily it still talks to the computer so I stick TWRP back on it to try to flash an OS. I can't find a TWRP friendly file (has to be a zip file??). When I try with Odin to flash stock ROM from Sammobile it fails, here's the log contents:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4203 M
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When it goes through this failure, this is what the phone screen says on download mode.
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G930F
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FAP LOCK: OFF
Secure Download : Enabled
WARRANTY VOID: 1 (0x030c)
RP SWREV: B:3 K:1 S:2
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 3, BINARY:1
I'm pretty sure this means I'm trying to use the wrong image, but I can't find one that works.
I've tried looking for images I can flash in TWRP, and I found something online called Lineage, download that, and HAHAHA it works!! phone is alive again, but I can't install any aps. They say they are installed but they aren't visible anywhere.
I've tried several different stock OSes with Odin, but I always get the same error.
I think hey, maybe I downloaded the wrong version of the OS from Sammobile, so I try to check my IMEI number in the "about phone" section but it's blank! I've somehow deleted the IMEI. I do still have the box though (thank god) so the IMEI number is 359468 07 8490758. According to google you can use the 7th and 8th digits of the number to get the country of origin to make sure you're using the right image, however, My IMEI number 7th and 8th digits are 07, but according to multiple sources, the 07 source doesn't exist!!!
So several possible questions that I just can't work out in this whole situation.
-What the hell is my country of origin, and how do I find the OS that should work for this phone (UK unlocked) considering I have no idea of my country of origin??
-Is this error actually caused by an OS mismatch?
-If it's not, what the hell do I do now? I am at a total loss.
-Is there a stock nougat version I can flash with TWRP? because I'm pretty sure I know how to do that, whereas I can barely get Odin to do anything for me.
Other random bits of info that may be relevant:
It's Exynos, I had to look that up in the initial research stages
I've checked and re-installed the samsung drivers about 3 times at this point
I tried something called x3z samsung tools to try to repair the IMEI, but it just says "card not found" and won't open. Guessing that's something to do with the fact that the IMEI number is blank?

UPDATE - I have fixed it
After trying about 15 other things with little success, I finally found The Galaxy Project Nougat ROM by djb77 https://forum.xda-developers.com/galaxy-s7/development/rom-galaxy-project-t3440314.
I was only able to use Odin to flash the same OS I had all along, it wouldn't allow any downgrades despite the whole phone being formatted.
Once I found the Galaxy Project, I finally managed to flash that ROM using TWRP, which was enough of a downgrade which allowed me to downgrade Google Play Services to the level I needed.