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.
Related
Model: SM-S902L I think?
Current ROM: Official and only ROM provided on Kitkat 4.4.2 Currently with residue files from being Rooted
Custom Recovery: TWRP
I have been battling with this phone for WEEKS. This is the first phone I rooted, but for the life of me I can't undo it. I had installed xposed at some point but I can't really remember why. I'm trying to flash the original stock rom on here to completely remove root access as everything else has failed me, but I can't even do that! I did the 'full unroot" option that was in SuperUser, and that's gone, all of the other root access apps have been removed, however I'd like to get the stock ROM, and recovery back on here.....
I have tried to load it via fastboot, but can't find a fastboot compatible driver for this phone and Windows 10 64bit, those I have tried windows states is incompatible with it.
I have tried using different types of ODIN to install the flash rom, (that I downloaded from sammobile.com) and every time they fail with:
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone it says:
SW REV CHECK FAIL:[aboot]Fused 3 < Binary 2
and the download stops.
I'm at my wits end here. I have tried so many different ways to get this to work, including doing a factory reset before the flash, removing the sd card, uninstalling and reinstalling the phones usb drivers, leaving "Auto Reboot" checked, then trying unchecked, Tried with Odin3 v1.85, Odin3.9 (I believe... about 3 weeks ago), and Odin3_v3.10.6. I can't find anything online about this model, aside from the zipped file of the original stock rom from samsung.
I have tried Kies, but it refuses to take the S/N for the phone, when I checked on the back of it, the S/N isn't listed, just an IMEI number (which I tried with no luck). Looking on the phone for the S/N just displays 00000000000, as well as when using a S/N finding application. Same issue with Smart Switch, can't verify S/N.
On top of that, the phone can't seem to decide what model it is. There is a sticker on the back casing that says SM-G900P(B), then on the one behind the battery it has an FCCID ends with G900V, but the model # just above that says SM-S902L that is displayed in the device settings. I've found that all of these can be used to determine the type of ROM that can be flashed, however mine are all different...
I have also tried installing it via TWRP from the sd card, it fails as well...
please someone more knowledgeable in this help me put this factory rom on my phone...
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<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)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Hello again:
Zero replies, did I omit important information in my first request -- or am I just rehashing previous inquiries about boot loop problems? (I have read through all posts relating to boot loops but found no answers that solved the to write to Nand failures). Forgive me if it's here and I simply didn't recognize it. . .
So (succinctly) why might Odin fail to write when attempting to reload the original firmware: . . . NAND Write Start!! . . . FAIL! (Auth) . . .Complete(Write) operation failed. . . .All threads completed. (succeed 0 / failed 1)
What might I be doing wrong, or what might I try instead?
Thanks again
flyyboyy said:
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<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)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Click to expand...
Click to collapse
Same thing with me.. patience gets you through it..
The same thing happened to me, same phone and same contract carrier (Sprint).
I bought my phone from a third party who apparently restores it to near-mint condition. The OS it had was one of the first releases of 6.0 /marshmallow. I tried downgradingit back to 5 / lollipop because i heard that call recording was still enabled with that OS.
I used Odin versions 3.7 thru 3.10 i believe and flashed every version of 5 that was listed on sam mobile and samsung 's site and all of them either failed to initiate- citing the same readings and failure reasons in odin that you mentioned - or they "succeeded" and resulted in boot loops.
I also failed to flash any of the earlier ROM versions of android 6 than the one my SM-G900P phone came with.
Finally, i succeeded in flashing 2 types of ROMS, the version of 6 my phone started with, then subsequently the most recent version released earlier in march 2017 (this month).
Conclusion: i believe the order that you flash these roms for our model phone with our carrier matters. Flash your phone with ROM images from the version that it came with, and continue sequentially and chronologically until your boot screen finally shows something other than that lovely little sprint logo
Good luck with your son's phone, and please let us k ow how it goes..... as i think this may be a recurring theme we may see more often in the future. I imagine the problem lies with either odin, samsung sm-g900p, or the sprint/cdma ROMa we're dealt.
-Rob
Have you tried samsung kies yet? Odin is for rooting your phone. Samsung kies will put updated firmware in your phone. I have used it several times in the past on a sam phone. It will work. Its from samsung company.
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...
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
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