Some of my responses/follow up questions aren't necessarily related to the root exploit. Hopefully I'm not derailing the thread in trying to better understand this process...
No, you're not unless it is renamed within the binary itself. In your video it is showing titled Odin3 v3.11 but the one you link to download runs as Odin3 v3.12. There are also differences in the banner image. Either way, I don't think this matters as the ROMs still get written. But to confirm, I'm not changing the default options in Odin. The only ones checked are "Auto Reboot" and "F. Reset Time".
Understood, thank you. I just did some testing and confirmed that if you remove the MD5 as the file extension (or simply add .tar on the end) that Odin skips the MD5 check. Learned something new!
Still trying to figure this out. If I pull up the settings the same way you do and request a factory reset there is no prompt for a Samsung account... it just resets. Is there something that if a Samsung account was previously set up this is what causes the prompt? If I go through the wizard the normal way when I get prompted for a Samsung account I can just use the skip option. Prior to me owning the phone I'm testing with I'm unsure if a Samsung account was ever used on it. Not sure if this may have anything to do with making the exploit work.
I've done some testing to try and verify this. It sure seems to me that the USB debugging setting is something that survives flashes/resets. If I turn it off and install the engineering kernel the debugging is still off. So while turning it on was omitted in your video, I would advise you keep it in the instructions.
Not quite sure what you're asking for, or if it is even a question. (I'm guessing English isn't your first language. Not criticism, I only know the English language so if you know multiple languages then you are doing better than me.) The baseband version on my phone is G920VVRS4DQD1. If you need more let me know.
I'm still pounding on this trying to figure out what is different for you that is holding up the rest of us. One thing I did stumble on is that I finally got the ADB fingerprint confirmation that you mentioned in your first post, I hadn't seen that prior. Thought maybe that was going to lead to a breakthrough but unfortunately I'm still stuck on that mount command. Haven't done testing to see if the approved fingerprint gets saved through factory resets, my guess would be it doesn't. Probably wrapping this up for tonight but should have some time to try again tomorrow.
---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------
I'd suggest doing what
@faw_wal does. Have a command prompt open in the path where the root.bat file exists. Issue the command "adb devices" and confirm your device shows up. If it only says "List of devices attached" and nothing else then your phone isn't being seen. You either need to make sure USB debugging is turned on, make sure you've got working drivers installed, or there is something else you're missing. You may also need to acknowledge a message on your phone that allows your computer to connect.
---------- Post added at 05:49 PM ---------- Previous post was at 05:38 PM ----------
@faw_wal, prior to you doing this on your device had you ever run a later ROM than DQD1? I'm wondering if there might be anything that could block this (blown efuse, etc.) if a later ROM had ever been loaded. Not sure if such even exists on these phones, but it wouldn't surprise me.
