The Oneplus 7T (hotdogb) and 7T Pro (hotdog) belong to the same device family, but are different devices, requiring different ROMs to flash. This thread is about the 7T Pro (hotdog). DO NOT flash this ROM to a 7T (hotdogb)
ErrorCode::kInstallDeviceOpenError (7)and sideloading aborted.
New build with August 2022 ASB patches available
a new build with the August 2022 ASB patches is available for download and also offered by the Updater app:
- Security string 2022-08-05
- Bromite Browser and Webview updated to 103.0.5060.140
- Some kernel patches
Thanks for the feedback - just a comment: I expect that the OTA updates simply work, my post about the 'error 7' may have been misunderstood.
I don't know as a matter of fact, but I am pretty sure that the answer is no.
I know that with LineageOS it is possible to make GPay work, but I am not educated enough to know how they do it. Also, I wish I didn't need to use GPay, but most of the time the only thing I have on me is my phone. Also, if GPay isn't working, I can't use my banking app due to the same check they do behind the hood.I don't know as a matter of fact, but I am pretty sure that the answer is no.
However, I am currently working on a 2nd build variant with the ported "sandbox jail" for Google Play from GrapheneOS and I am looking for volunteers to test that for me (more to follow later today), as I can't do that on my own device, which is my daily driver (and there is no working TWRP for our device being able to decrypt the /data partition on A11), as this would screw up my setup... That thing could be your solution, I think...
EDIT: AFAIK, G*Pay requires passed safety net attestation, which is not the case for this device with this ROM. I have no idea, whether it's possible to pass SN with this device and LineageOS. Maybe others can step in here?
EDIT2: Apart from the technical answers given by me before: distancing from G* on the one hand side, whilst still using G*Pay on a daily basis, is a significant and unsolvable contradiction, so you may want to think about this topic, too...?
G*Pay is deeply integrated with the Google Play services, and this ROM uses microG and not the genuine Google Spy services. Further, G*Pay needs the 'SafetyNet' attestation to pass, and on this device using this ROM, this check fails. There are LineageOS devices (especially with older hardware) still passing 'SafetyNet', as the checks are more relaxed on older hardware, due to compatibility reasons. That is why.
Of course, you decide about your life and what is important to you. And everybody has different priorities. I for myself have decided, that I prefer not to use my phone to pay in shops or restaurants. Cash and/or plastic cards work quite well, too. For sure, I don't want "big G*" to spy on all my finance transactions, analyze and profile them and report "suspicious activities" to any US authority.
Most probably "SafetyNet", as explained above. That depends of course on each bank, and how they implement two-factor authentication (2FA) etc. - My bank e.g. lets me still use their app for read access, which is fair enough. Using 2FA on the same device voids the whole concept and unfortunately, many banking apps are mainly designed to make it very difficult for security researchers to find and publish all the loopholes rather than implementing proper security, but that is another story.
Thanks for your feedback - I see you have started to think about "big G*", which is good. As said, all up to you and your preferences. Just a general non-technical advice from my side: Maybe somehow consider it similar to fast food vs. healthy nutrition. There is no 'magic pill' to convert fast food into healthy food - if you e.g. understand that too much fast food is not good for you, you have to actively change your diet. This is work, requires to to get familiar with nutrition and alternatives, but at the end, you'll see that you won't really miss the fast food...I am new to this whole custom ROM community, but due to recent things, I really want to distance myself from Google services. Although this build isn't for me, I really love what you are doing, and I appreciate your work. I hope that one day I will be able to use this on my daily driver OP 7T pro.
Volunteers wanted - Test build for 'sandboxed play services'
I have created (and also briefly tested myself on a different device) a test build of this ROM with an Android 11/LineageOS 18.1 port of GrapheneOS's Sandboxed Play services .
I would be interested to see, to what extent this approach is usable and whether this would be interesting for you as an offered 2nd build variant or not.
Your feedback is appreciated.
Thanks & regards - M.
Me neither for now, as I have already mentioned (major reason is that I don't want to wipe my device) - so this is not for everyone, but it may be interesting for some people.
https://microg.org/ and https://calyxos.org/docs/guide/microg/ might give you more insight on that.
When I was playing around with AA (scroll back in this thread), I wasn't too impressed either - wasn't e.g. too much amused about the requirement to install G*Maps and have it actively spying your location, while using AA, even if you weren't using it or even had a different GPS app...
fastboot flash recovery_a lineage-18.1-recovery-20210903.img fastboot flash recovery_b lineage-18.1-recovery-20210903.img
Partition product_b dd: /dev/block/dm-1: write error: No space left on device Partition vendor_b dd: /dev/block/dm-2: write error: No space left on device
Don't "update" Google Play Services! This ROM comes with microG, which spoofs the existence of G* play services, but you can't "update" those, and in fact you don't really want to (if you understand the technical background).thanks dev for the great work... all working fine.
often when performing aurora updates, one gets google play services install errror 'conflicting package exists', wondering if anyone has seen this and how to get round it?
looking at apkmirror, the one in aurora is already the latest non-beta version of gps, presumably this is an aurora issue, but just wanted to see if there is quick solution given this error happens on this rom on this phone for me...