Related
HD8 2018 6.3.1.5 (and 6.3.1.4) issues
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.5 (6.3.1.4) on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
HD10 2017 40.6.5.0_user_650601220 issues
Well, what do you know ... I finally took the plunge to do the unlock and install TWRP on my Kingoroot rooted HD10 2017 (thanks @k4y0z !). I backed up all the apps via Titanium Backup, and then backed up the internal sdcard via Total Commander to a zip, which later nicely restores things back with the proper timestamps (yay!). It's very difficult to restore timestamps, but Total Commander with root can do it.
In my optimism, after getting TWRP, I immediately installed the latest FireOS, 40.6.5.0_user_650601220, with Magisk, and Xposed installed into system (xposed-v89-sdk22-arm64.zip). And, just like HD8 2018, the moment I activated Xposed modules, the tablet started rebooting when WiFi was on. If I managed to hit WiFi off button before it did so, it seemed stable. So both HD10 2017 and HD8 2018 appear to have the same Xposed bug in the latest FireOS versions!!! I wonder if it's related to the fix of MTK-SU issue.
I also ran into Google Play & battery drain issues. Tired of several attempts of troubleshooting, I actually ended up backtracking all the way to 40.6.2.6_user_626533320, which is the version I started with. Once Google Play went south after my 1st restore, I could not fix it over multiple tries, and I had to do a Factory reset again and restore apps via Titanium Backup a bit more carefully, starting with the latest versions of Google Play apps without data (rather than just all at once). Now everything appears to be working as before, with TWRP, and the same old FireOS version that I already had
The battery drain issue was an interesting one, apparently, Vanced Youtube helper app, microg_YouTube_Vanced_0.2.6.17455, creates a lot of battery drain via needless Wakelocks, which can be fixed by running the following commands:
Code:
adb shell
su
pm disable com.mgoogle.android.gms/org.microg.gms.people.ContactSyncService
P.S. A week ago I unlocked HD8 2017 (OS version 50.6.3.6_user_636558520), and successfully cloned HD8 2016 to this 2017 via TiBa & Total Commander. That attempt went without a glitch, and that's why I thought I could also do HD10 in no time, but HD10 gave me all kinds of issues.
bibikalka said:
HD8 2018 OS continues to present never ending issues (seems like a poorly supported product compared to the earlier Fires ...)
I flashed 6.3.1.4 on top of 6.3.1.2 via TWRP (+Magisk/systemless Xposed), and, ended up with a weird WiFi crashloop that took a few tries to understand. Essentially, the moment it connects to a WiFi network, it reboots. If I set WiFi to off, it's stable (have to do it quick before it connects after a reboot!). If I disable Xposed module, it's stable. Neither Xposed 89.3 or 90beta work correctly.
On 6.3.1.2 Xposed worked more or less OK.
I tried to downgrade back to OS 6.3.1.2 or 6.3.0.1, but apparently the settings are not compatible once you load 6.3.1.4 on it. It never reaches the launcher, and keeps sitting at Fire screen. I could not even boot 6.3.1.2 or 6.3.0.1 without Magisk. Doing a factory reset was not in my plan yet. So I had to go to 6.3.1.4 again where it booted fine. I now run 6.3.1.4 with Xposed disabled.
Anybody has 6.3.1.4 with Xposed & WiFi working properly out there? I wonder if this is also a similar issue with Fire 7 2019 (mustang) - @Michajin
Click to expand...
Click to collapse
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Michajin said:
you will have to refresh me where i had on the mustang. I am using los 16.0 on the hd8, dont really have a need for xposed. Seems like i had this on the mustang right after root when on stock? i will look into it and try and refresh myself if you cant point me into the thread...
Click to expand...
Click to collapse
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
bibikalka said:
It was here :
https://forum.xda-developers.com/showpost.php?p=79841222&postcount=21
Click to expand...
Click to collapse
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Michajin said:
I am trying to remember but it seems i had to flash full xposed from TWRP. I think i had issues with the systemless version from magisk. I didn't know people would chose to run FIRE-OS once anything else was available (no offense) with 14.1 and 16, both being decent... lol
Click to expand...
Click to collapse
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
The camera works on both 16.0 and 14.1. But 14.1 is by far more stable at this time. Bluetooth and headphones (plus more- see thread) issues on 16.0. The only issue on 14.1 is the headphone jack doesn't work (but i think someone has found a fix for it but it hasnt been updated in the rom). Backup in TWRP and install 14.1 and give it a shot, i am on 16.0. 14.1 was working really smooth. I have not tested skype on either. 14.1 seemed smoother and less buggy than fireOS right at Beta.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
Observation regarding custom ROMs is one reason I typically hang with 'stock' and tune to my liking. LOS 14.1 for this device/gen (and a few others) is an exception; worth considering. LOS 16.1 is less refined ATM with no meaningful advantage over 14.1.
bibikalka said:
You have a point here regarding LoS I thought I was gaining stability by sticking to FireOS, but this version has been anything but stable!
I need Skype to work - is the camera working in either LoS 14.1 or 16? The issue is that some of these ROMs seem to be in eternal beta, once the low hanging fruit is done, the polish is not applied further.
Click to expand...
Click to collapse
I needed to have headphones working, so I didn't try LOS 14 until recently. I'm extremely happy with it. It's so much snappier than stock for me, and videos load so much faster, like in Netflix, for example. I'm also using Magisk and Xposed with no issues.
I didn't realize the new build is up with fixes... Going back to 14.1, I think he is working on 17.0 (Kaijones23) 17.0 was updated last night....
https://github.com/mt8163/android_device_amazon_karnak/branches
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
xantiux said:
Noob question - how do you flash lineage-16 or cm-14.1 onto the device? I downloaded the zip files from the link above, but they are way to small to be a complete rom. Is there a different location where I can download the roms?
Click to expand...
Click to collapse
Have you unlocked the bootloader (prerequisite):
https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
xantiux said:
I have unlocked the bootloader, for which I had to open the tablet up in order to short a pin. I was able to load the FireOS 6.0.0.0 and 6.0.0.1, and was looking if there is a way to load 6.0.1.2 or 6.0.1.4, when I came upon this thread, and saw that it may be possible to load lineage or cm, but I don't know how to get my hands on the ROMs. The downloads from the links above are way too small.
Click to expand...
Click to collapse
This help?
https://forum.xda-developers.com/hd8-hd10/general/lineageos-14-1-fire-hd8-2018-t3936242
https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
xantiux said:
This is great, thank you!
Somewhat related question - is it hard to get a zip of fireOS 6.3.1.2, so it can be flashed via TWRP?
Click to expand...
Click to collapse
Supposedly renaming .bin to .zip allows flashing from twrp. I'd be wary of other partitions such as recovery and aboot which could trigger a bad day.
Headphone fix for LOS 14 has been applied in the latest version of the ROM. If you don't feel like reflashing entire ROM, there is a flashable zip containing only the headphone fix (module). I don't have the links handy but it's all available on this forum.
Updated post #1 and described HD10 '17 Xposed WiFi crashloop as well.
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
bibikalka said:
Updated with the same HD8 2018 6.3.1.5 WiFi/Xposed issue.
Click to expand...
Click to collapse
Welcome back!
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
atharvvvg said:
So I had installed the latest lineageOS version ( 17.1, android 10, osprey moto g3) from the official website and flashed it correctly, but after some time, I noticed that the torch icon was greyed out in the status bar and any camera app won't work.
The app showed- "Camera stopped working"
Cleared cache, app info, rebooted the phone but nothing seemed to work.
I thought that flashing the ROM again would fix it, I redownloaded the latest lineageOS version, new GApps, and flashed it in the correct way( first wipe then flash), but the issue came back after a few reboots.
So I rebooted again and it got fixed, but I think the issue might spring back.
Is there any fix for this?
Click to expand...
Click to collapse
Hello members,
Last week i'v also installed the latest lineageOS version ( 17.1, android 10) Gapps nano, on my Samsung A3 2017. With the TWRP tool., Nice ROM!
Unfortionally with the same issue as above, Samsung and other camera app's very often not working, need to reboot to fix that.
The flashlight does not work either then, and much more irritating BlueTooth not working anymore, my A3 always had perfect connection with my Parrot carkit CK3100.
I'v found in several forum some workarounds for this but these do not solve the issues long enough.
But the issues are also found in older releases from LineageOS.
Will there be a update for these mentioned 3 issues?
If not, i need to install another ROM which is not based on LineageOS.
The Cam and BT must work without any problems.
Thank you very much.
Frank.
Hello everyone. Long time since I had an android device and I'm cutting the chains of my iPhone wanting to be de-Googled and de-Appled. I was running Lineage 17.1 from Microg and thought I had everything working on it until I started updating some software on my phone over the air. I rebooted and it went to bootloop. Since then I re-installed 17.1 and got things working again. I just upgraded to 18.1 and want to make sure it's all set up properly and won't have any errors.
Magisk says SafetyNet has an "SafetyNet API Error." "Basicintegrity, ctsProfile, evalType N/A." all in red when I check if it's working. I've done some digging, but want to make sure I do this right. I need to get the boot.img file from the original firmware. Should I get this from the oneplus website, or should I be looking for something else since I have Lineage? Can anyone provide the raw boot.img file for the OnePlus 7 Pro that I should use? I'm a little overwhelmed with all of the steps to extract it from the original firmware. Please and thanks for any help getting this phone set up the way I need it to work!
That error show when safety net API download was incomplete/corrupt, you can try to erase data from magisk manager and check safetynet again but with a better internet connection or use another magisk version like canary
And if you end in a bootloop for any magisk module just turn off your device and in your computer in a CMD/powershell/terminal window enter this command
adb wait-for-device shell magisk --remove-modules
Then connect and turn on your phone and automatically your phone will reboot with all your magisk modules disabled
Use magisk canary bro,,,
I sideloaded Canary and still get the red SafetyNet API error screen after opening it. Can someone direct me to a full tutorial on how Magisk works and what the modules do? I'm thinking I might need to do a full uninstall of Magisk and start over. If I do this will I lose all the data on the phone and have to start from scratch? Thanks for your help so far!
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Lear31pilot said:
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Click to expand...
Click to collapse
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Lossyx said:
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Click to expand...
Click to collapse
Got it! I'll go back to 17.1 Thanks!
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Lear31pilot said:
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Click to expand...
Click to collapse
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
RokCruz said:
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
Click to expand...
Click to collapse
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Lear31pilot said:
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Click to expand...
Click to collapse
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
RokCruz said:
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
Click to expand...
Click to collapse
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Lear31pilot said:
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Click to expand...
Click to collapse
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
RokCruz said:
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
Click to expand...
Click to collapse
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Lear31pilot said:
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Click to expand...
Click to collapse
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
RokCruz said:
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
Click to expand...
Click to collapse
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
So
Lear31pilot said:
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
Click to expand...
Click to collapse
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Lear31pilot said:
So
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Click to expand...
Click to collapse
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
And remember you need to install magisk in order to pass safetynet.
RokCruz said:
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
Click to expand...
Click to collapse
Looks like I'm denied the ability to disable the Market App.
Photo's attached for the Google settings I have available on HOS 11.
Also unable to make the microphone work in the keyboard for voice to text, but I have a feeling I won't be able to make that work without logging in to Google. Currently looking for some workarounds.
What will passing Safetynet allow me to do that I'm not already able to do now? Use banking apps and "tap to pay" type apps? I haven't found my bank app on the Aurora Store just yet. "US Bank" if it makes a difference.
I'll continue to play with this OS, but so far, it seems the easiest to get working right from the get-go.
Hello,
Is there any OnePlus 7 Pro custom ROM with no GApps , and the bootloader can be re-locked after the ROM flashed?
Why re-lock the bootloader?
- I don't give a way phones, in case i lost the phone.
Try LinageOS?
- I did, can't re-lock the bootloader, because they don't load the signing keys into the verified boot as GrapheneOS and CalyxOS do.
If there's a ROM out there, please tell me where, if not, I'm sorry for any inconvenience.
Thank You
Did you find anything since this post? I've been playing with LOS 17.1 and 18.1 on my OP7Pro but can't get Safetynet to pass when I have Magisk on, and have issues trying to put TWRP on with LOS, as LOS hijacks the recovery. I'd like to get my banking apps and some other apps like Lyft to work without having google know my every keystroke and geolocation. I'm close with LOS 18.1, but am missing those 2 apps ability to work. I might try 17.1 again if that's going to make things easier.
From your post it looks like GrapheneOS and CalyxOS might be options. What's wrong with those OS? Will those not work with MicroG?
Lear31pilot said:
Did you find anything since this post? I've been playing with LOS 17.1 and 18.1 on my OP7Pro but can't get Safetynet to pass when I have Magisk on, and have issues trying to put TWRP on with LOS, as LOS hijacks the recovery. I'd like to get my banking apps and some other apps like Lyft to work without having google know my every keystroke and geolocation. I'm close with LOS 18.1, but am missing those 2 apps ability to work. I might try 17.1 again if that's going to make things easier.
From your post it looks like GrapheneOS and CalyxOS might be options. What's wrong with those OS? Will those not work with MicroG?
Click to expand...
Click to collapse
Hello,
First, Now I'm sure 100% that OnePlus 7 Pro is supporting verified boot and bootloader relock, but to achieve that, you have to load the signing public key used to sign the ROM during its build and it should be user build not debug mode build (ex. for debug mode build is the offecial LineageOS) to the phone verified boot partition.
I found this divestos [dot] org, but still not tested nor working on Oneplus 7 Pro. I tried but my phone never load the OS.
Now, I'm trying to go through the build steps from official LineageOS website to do my own build and do it user build, sure using my own signing keys, I hope it will work.
For GraphenOS and CalyxOS, unfortunately they work only with Google Pixel phones, ironic, isn't?, Lyft might work with you if you decided to go that way, because i tried Uber and it worked just fine with MicroG, but my banking app did not work, not because of microG or the OS, but because the app itself design to detect google play store and if you login or not, and if the app downloaded from the play store itself or not.
I hope my answer gave you some help.
ahmed.elsersi said:
Hello,
First, Now I'm sure 100% that OnePlus 7 Pro is supporting verified boot and bootloader relock, but to achieve that, you have to load the signing public key used to sign the ROM during its build and it should be user build not debug mode build (ex. for debug mode build is the offecial LineageOS) to the phone verified boot partition.
I found this divestos [dot] org, but still not tested nor working on Oneplus 7 Pro. I tried but my phone never load the OS.
Now, I'm trying to go through the build steps from official LineageOS website to do my own build and do it user build, sure using my own signing keys, I hope it will work.
For GraphenOS and CalyxOS, unfortunately they work only with Google Pixel phones, ironic, isn't?, Lyft might work with you if you decided to go that way, because i tried Uber and it worked just fine with MicroG, but my banking app did not work, not because of microG or the OS, but because the app itself design to detect google play store and if you login or not, and if the app downloaded from the play store itself or not.
I hope my answer gave you some help.
Click to expand...
Click to collapse
I actually took a senior member's' advice to just use Hydrogen (the Chinese (de-googled) version of Andriod) on my OP7Pro. So far it's working well and I just have to get things set up, but I'm rooted and Magisk works using the boot.img patch and hiding the app in settings. No need for Microg as it is a signed OS (or something like that). At the end of the day, I just needed something that worked right and didn't have big G tracking my moves. Some small tweaks and I'll at least have Hydrogen 10 working right. I might play with HOS11 after I get the backup functionality working correctly. I'm tired of downloading a ton of apps and getting all of my logins done and email accounts set up, only to make a tweak on the system and have to start over again.
Hope the custom LOS you're working on works for you. Thanks for getting back. This is a learning process for me. Take care.
Lear31pilot said:
I actually took a senior member's' advice to just use Hydrogen (the Chinese (de-googled) version of Andriod) on my OP7Pro. So far it's working well and I just have to get things set up, but I'm rooted and Magisk works using the boot.img patch and hiding the app in settings. No need for Microg as it is a signed OS (or something like that). At the end of the day, I just needed something that worked right and didn't have big G tracking my moves. Some small tweaks and I'll at least have Hydrogen 10 working right. I might play with HOS11 after I get the backup functionality working correctly. I'm tired of downloading a ton of apps and getting all of my logins done and email accounts set up, only to make a tweak on the system and have to start over again.
Hope the custom LOS you're working on works for you. Thanks for getting back. This is a learning process for me. Take care.
Click to expand...
Click to collapse
The same here, I hate this tracking and the feel that there is someone always looking over my shoulder .
Could you please tell me, where did you get HydrogenOS, I might give it a try.
Thank You, have a blessed life.
Best bet would be to run a debloat script. Universal Debloater (found here or on gitlab I believe) has the options for Google and OnePlus. Since you can use USB Debugging without unlocking bootloader, this might be the best option for you.
They will show the apps that are getting removed and a little description if you open up the list files in a text editor (notepad or whatever).
ahmed.elsersi said:
The same here, I hate this tracking and the feel that there is someone always looking over my shoulder .
Could you please tell me, where did you get HydrogenOS, I might give it a try.
Thank You, have a blessed life.
Click to expand...
Click to collapse
I just did an internet search (duckduckgo) and found a website with the complete zip file. Not sure if this is the one, but they offer the download for 10. (Mods can remove this link if I'm not allowed to share links with downloads) In any case, you can dig and find something if you chose to go this route. There are probably more HOS 11 downloads as of late since it's newer. I just wasn't able to get the Magisk app to work right on the 11 verison. That may have changed with the most recent update of Magisk. A de-bloat tool may work on OOS too. I just haven't tried it on OOS yet.
download HydrogenOS 10.0.10 Archives - RM Update News
Tech News
www.rmupdate.com
Hi,
kinda new to custom ROMs and running into my first real problems.
I installed TWRP, LineageOS 20.0, BitGApps Basic and Magisk 26.1 on my Samsung Galaxy S10e Exynos.
After setup everything works extremely well and fast. I installed Universal SafetyNet Fix, Viper4Android (programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer. (github.com)) and Universal GMS Doze (gloeyisk/universal-gms-doze: Patches Google Play services app and its background processes to be able using battery optimization (github.com)). The phone still works fine and Viper4Android works too. SafetyNet also passes.
Now the problems arise. A few hours later and some reboots later, the phone won't boot anymore (maybe 20 reboots). I didn't even change any settings before the reboots. The boot animation plays and the phone is getting reset by a watchdog maybe. Also cannot use ADB during boot and the safe mode button combination doesn't work. I'm not experienced enough to understand the log files correctly. I already flashed the phone twice and the same problem occurred.
I attached some logs I could get from TWRP, but the main data partition is encrypted.
Full log files are here: logs.zip
Otherwise I'm extremely impressed with Lineage and would love to use it as my daily.
Thanks a lot for helping.
loriZyy said:
Hi,
kinda new to custom ROMs and running into my first real problems.
I installed TWRP, LineageOS 20.0, BitGApps Basic and Magisk 26.1 on my Samsung Galaxy S10e Exynos.
After setup everything works extremely well and fast. I installed Universal SafetyNet Fix, Viper4Android (programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer. (github.com)) and Universal GMS Doze (gloeyisk/universal-gms-doze: Patches Google Play services app and its background processes to be able using battery optimization (github.com)). The phone still works fine and Viper4Android works too. SafetyNet also passes.
Now the problems arise. A few hours later and some reboots later, the phone won't boot anymore (maybe 20 reboots). I didn't even change any settings before the reboots. The boot animation plays and the phone is getting reset by a watchdog maybe. Also cannot use ADB during boot and the safe mode button combination doesn't work. I'm not experienced enough to understand the log files correctly. I already flashed the phone twice and the same problem occurred.
I attached some logs I could get from TWRP, but the main data partition is encrypted.
Full log files are here: logs.zip
Otherwise I'm extremely impressed with Lineage and would love to use it as my daily.
Thanks a lot for helping.
Click to expand...
Click to collapse
If it is an issue with the ROM itself, you will need to post your issue in the ROM thread where you got your ROM and see if there is something in the ROM that the developer of the ROM needs to fix in the ROM itself.
Hi, kinda new to custom ROMs and tried out Lineage and later Crdroid on my Galaxy S10e Exynos.
The OS works fine but after a few restarts the phone randomly bootloops and I can't find any way to fix it.
Currently installed is Crdroid recovery, Crdroid latest (the same problem happens with Lineage) with Android 13, MindTheGapps, Magisk 25.2
Magisk modules are Zygisk, Viper4Android and Universal SafetyNet Fix.
I attached some logs but I'm too inexperienced too read them correctly. It looks like the file
Code:
/data/misc_de/0/apexdata/com.android.permission/runtime-permissions.xml
is corrupted after a few restarts?? The bootlogo just repeats and nothing is happening. The logs say that the zygote process has crashed.
Does anyone know what to do? Thanks a lot!
Logs: log.txt
This used to happen on my Galaxy A50 on another ROM too, and since it's not an S10e problem it's probably a Magisk module