I’m finally getting a more complete idea of what to do. More complete yes!.. but still not complete…
The SM-G960F was never released in the US and so I don’t see it available here:
Since I will be going from stock pretty much immediately to /e/ via the method you thoughtfully put together… does it even matter what stock firmware I use?
I may be misremembering something I read either here or at XDA over the last week but… If I use the wrong baseband for my device when transitioning to /e/ won’t I have other weird issues (like streaming service issues). I hope the answer is that I’m wrong about it.
In my current 8.1.0 build I do see my baseband version is G960FXXBETH2. This is the reason why I asked if I needed to use the french version that has a matching field.
I’m getting an error when side-chaining the no-verity-encrypt-samsung zip file. The vendors file ran ok. The directions didn’t say to reboot after that but I did after no-verity failed with Error Code:1
Nothing is encrypted. Do I need to run this magic patch?
Thank you for taking the time to reply with helpful comments.
Very well. I’m going to ignore the temptation of asking what the vendor patch did. FWIW the vendor patch did install/complete. It was the other (no verify encryption??) patch that failed.
I can’t forget what I never knew. Now that I know (thank you) I’ll try not to forget.
Where is this instruction outlined? Can you provide a link or clarify what fs to change the /data partition to? Why not ext4?
Do you mean:
-wipe (then reboot to recovery)
-Advanced wipe (reboot to recovery again)
-manually edit partition (create fs, format, then mount to /data, reboot to recovery again because why not)
-THEN sidechain /e/Q?
Most importantly… do I need to start all over by refreshing the stock rom using odin? Or can I just wipe and try again?
I admit that I dont understand what the purpose of flashing a stock rom is since it’s pretty much immediately blown away/formatted/wiped in TWRP. If that is NOT what’s happening with that step… I could benefit from knowing what is really going on.
Can you address this question please? Your statement wasn’t clear.
I was able to get Stock 10 installed, and then side loaded /e/Q BUT I got an encryption error and I’m not able to get the no-verity dm disabler to run via sideload because I get a generic “Error 1”. I did locate the developers site and ran the latest version.
If I can’t get these questions answered then I’m afraid anyone else out there that wants to upgrade to 10 from a samsung s9 is doomed to run into at least some of the same issues. I’m like 99% there. Just can’t figure out this encryption sh!t.
You are not responsible for the wrong documentation.
We are claiming to Manoj for month about those non accurate documentations, but he has not the direct control over it. I hope one of the new /e/team members will take his hand on this important component.
From what I see I believe you are over thinking it. You have an unlocked bootloader and TWRP installed, this is the hardest part. Now all you have to do is flash a stock Android 10 ROM and then follow THIS. If you follow it everything will be wiped (*DM Verity/Root files you have flashed) and then after you get /e/Q installed you can tackle the encryption through Trust in the settings (if the phone isn’t already encrypted, it will tell you, see below)
You are not responsible for the wrong documentation.
I am responsible for everything I encounter. Even moreso when I’m negitively impacted by something that isn’t my fault. Opportunity lurks where responsibility has been abdicated
Whoever is responsible for maintaining this documentation is also doing 17+ other things and this probably isn’t the only company they work for. If their efforts are spread as thin as they probably are… At some point the reality is that trying to do one more** thing means choosing to do a whole bunch of sh!t badly or incomplete haha.
I say once we (the oppressed Samsung users in the community) know what works we co-create a thread that would have been the thing I wish I had when I started.
You must now re-flash only the android Q Samsung’s /vendor partition (extract it from the downloaded firmware), or re-flash the antire Q Samsung firmware, and TWRP, and finally /e/OS
What’s one more time at this point.
Did factory reset from stock Q recovery
booted it up. Wifi and Cellular Work.
Enabled Dev mode
I can see oem unlocked,
flashed twrp 220.127.116.11 using odin
booted into twrp recovery
FYI I’m not going to sidechain vendor file or use dm-verity (this time). I’ll update once I do the rest of the things.
The hardest thing to get anyone asking for help to do is anything at all. Without being critical I’m sure that if I can pick apart a set of instructions and not find ambiguity… then you’ve got 99% of the people you’d probably want to reach anyway. I struggle. Thanks again.
Im having also trouble with Disney+. It doesn’t play video. I am not very intrested to modify system like above is told. Is this something /e/team could do in upcoming updates? I heard also that HBOmax didn’t work either.
I think this problem is something that many users are facing, so it would be nice if it would be fixed by the /e/team, not everyone individually