Related
I've posted several times about issues I've had with my mobile services (I get no bars, no service of any kind; wifi hotspot error) after I do backup and restores. This has happened to me doing manual backup/restore using CWM as well as TWRP. Mobile services also went out after allowing the built-in auto update feature for the nightlies. Note that everything worked fine up until these procedures.
I really like this ROM when its running fine but I cannot keep on with this. Currently, no form of re-install is restoring my mobile services.
Unless someone can address this issue and with a solid fix, I'm done with this ROM.
Running Sprint Note2 / SPH-L900. I do not claim to be advanced in these issues so, IF ANYONE NEEDS ANY FURTHER INFO FROM ME PLEASE ASK AND I WILL PROVIDE IT.
So much for the "even 1% of phones", OmniROM!!!
hammerchucker said:
I've posted several times about issues I've had with my mobile services (I get no bars, no service of any kind; wifi hotspot error) after I do backup and restores. This has happened to me doing manual backup/restore using CWM as well as TWRP. Mobile services also went out after allowing the built-in auto update feature for the nightlies. Note that everything worked fine up until these procedures.
I really like this ROM when its running fine but I cannot keep on with this. Currently, no form of re-install is restoring my mobile services.
Unless someone can address this issue and with a solid fix, I'm done with this ROM.
Running Sprint Note2 / SPH-L900. I do not claim to be advanced in these issues so, IF ANYONE NEEDS ANY FURTHER INFO FROM ME PLEASE ASK AND I WILL PROVIDE IT.
So much for the "even 1% of phones", OmniROM!!!
Click to expand...
Click to collapse
Sorry to hear that you have this issue. What happens when you install and update manually? Have you tried doing a full wipe, flashing an older version from like two days ago and update from OpenDelta. To see if the issue is still there. (Remember to make a Nandroid backup before doing this or you will lose your data)
Let me know,
hammerchucker said:
I've posted several times about issues I've had with my mobile services (I get no bars, no service of any kind; wifi hotspot error) after I do backup and restores. This has happened to me doing manual backup/restore using CWM as well as TWRP. Mobile services also went out after allowing the built-in auto update feature for the nightlies. Note that everything worked fine up until these procedures.
I really like this ROM when its running fine but I cannot keep on with this. Currently, no form of re-install is restoring my mobile services.
Unless someone can address this issue and with a solid fix, I'm done with this ROM.
Running Sprint Note2 / SPH-L900. I do not claim to be advanced in these issues so, IF ANYONE NEEDS ANY FURTHER INFO FROM ME PLEASE ASK AND I WILL PROVIDE IT.
So much for the "even 1% of phones", OmniROM!!!
Click to expand...
Click to collapse
You posted several times, well you probably posted in the wrong place. We have a bug report website at http://jira.omnirom.org and your issue has never been brought to my attention.
I doubt everyone with the Note 2 has no mobile services, so have you at least checked common locations like APN settings?
XpLoDWilD said:
You posted several times, well you probably posted in the wrong place. We have a bug report website at http://jira.omnirom.org and your issue has never been brought to my attention.
I doubt everyone with the Note 2 has no mobile services, so have you at least checked common locations like APN settings?
Click to expand...
Click to collapse
That's a Sprint device so it may suffer from "odd" issues other Note2 variants don't have... I need to look into it but Utkarsh may have been blind-supporting the L900 in which case we may need to pull that device until it gets a proper maintainer who actually owns the device.
Entropy512 said:
That's a Sprint device so it may suffer from "odd" issues other Note2 variants don't have... I need to look into it but Utkarsh may have been blind-supporting the L900 in which case we may need to pull that device until it gets a proper maintainer who actually owns the device.
Click to expand...
Click to collapse
I can only vouch for my L900 Note2, but it runs Omni nightlies swimmingly...on the L900 boards I've seen several reports of oddities with 4.4 ROMs, most commonly from people who did the rooted de-Knoxed 4.3 update with a "wifi fix".
It ain't a baseband thing...as I have the MK4 (latest) baseband....and I've never flashed a full 4.3 OTA ROM be it stock OTA or rooted with that "fix".
Skripka said:
I can only vouch for my L900 Note2, but it runs Omni nightlies swimmingly...on the L900 boards I've seen several reports of oddities with 4.4 ROMs, most commonly from people who did the rooted de-Knoxed 4.3 update with a "wifi fix".
It ain't a baseband thing...as I have the MK4 (latest) baseband....and I've never flashed a full 4.3 OTA ROM be it stock OTA or rooted with that "fix".
Click to expand...
Click to collapse
OK, so only some people are having these issues... Weird. If it's working for most people and there's someone actually fixing reproducible issues, then the device goes on.
SELinux Mode Changer is the answer
Entropy512 said:
OK, so only some people are having these issues... Weird. If it's working for most people and there's someone actually fixing reproducible issues, then the device goes on.
Click to expand...
Click to collapse
I had same issue with my n7105. After surfing through the web, I found the answer as "SELinux mode changer". If you had a 4.3 with Knox installed earlier, you might face this issue. Its because by default SELinux mode is 'Enforcing' and I had to change it to 'Permissive'. After that it works fine.
I also had trouble with SuperSU, so had to apply .zip from TWRP.
hope this helps
So I had my unrooted Moto X Pure for quite sometime now and I was looking to root it. I was wondering are there any feature filled ROMS. I can't seem to find any screenshots on the ROM releases and would love to root my phone as it seems to have lots of delay even though it is not full. Can anyone lead me to some guides and tutorials to some good ROMS for the Moto X Pure Edition?
Dirty Unicorns and Pure Nexus are pretty good. Plenty of options to go with - both come with the CM13 Theme engine and Pure nexus also comes with the layers version too. I've gone back to stock rooted with Xposed installed as I like the Moto Assist thingy and the only things I need are the Advanced reboot menu and the option to change the icons in Google Now which is my favourite launcher.
lmulli said:
Dirty Unicorns and Pure Nexus are pretty good. Plenty of options to go with - both come with the CM13 Theme engine and Pure nexus also comes with the layers version too. I've gone back to stock rooted with Xposed installed as I like the Moto Assist thingy and the only things I need are the Advanced reboot menu and the option to change the icons in Google Now which is my favourite launcher.
Click to expand...
Click to collapse
I was looking at Dirty Unicorns and it seems pretty nice. I was wondering is there a guide to root and backup my Moto X Pure? I wanted to root, but I don't want to lose all the data and other system information/settings like it used to happen on my HTC One M8. Could you recommend any guides? Thank you!
Rooting requires you to unlock your bootloader, which will wipe all system data with no way around it. It should leave user storage (photos, downloaded files, etc) untouched, but it will delete all installed apps and restore the phone to its factory state.
The only partial workaround for an unrooted phone is to backup your apps to Helium and restore them after you've unlocked the bootloader—once you're rooted, this will be possible with Titanium Backup to backup apps to your internal/external storage as opposed to a cloud.
Immediately after you've unlocked the bootloader, be sure to flash the latest build of TWRP and make a backup of your entire device so that you can restore to something functional if you mess up with rooting. I'm sorry I wasn't able to help with keeping all your system data intact, but to my knowledge, it's just not possible.
I'm positive there's a complete guide to rooting and unlocking the bootloader of this device (as well as a guide to using TWRP for backups and installing ROMs and whatnot) on these forums, and they should be very easy to find with a little browsing. Best of luck to you.
Sent from my XT1575 using XDA-Developers mobile app
DubstepWithPON3 said:
Rooting requires you to unlock your bootloader, which will wipe all system data with no way around it. It should leave user storage (photos, downloaded files, etc) untouched, but it will delete all installed apps and restore the phone to its factory state.
The only partial workaround for an unrooted phone is to backup your apps to Helium and restore them after you've unlocked the bootloader—once you're rooted, this will be possible with Titanium Backup to backup apps to your internal/external storage as opposed to a cloud.
Immediately after you've unlocked the bootloader, be sure to flash the latest build of TWRP and make a backup of your entire device so that you can restore to something functional if you mess up with rooting. I'm sorry I wasn't able to help with keeping all your system data intact, but to my knowledge, it's just not possible.
I'm positive there's a complete guide to rooting and unlocking the bootloader of this device (as well as a guide to using TWRP for backups and installing ROMs and whatnot) on these forums, and they should be very easy to find with a little browsing. Best of luck to you.
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for all the info! For some reason, after following all the steps, Helium does not work for me. I've downloaded the drivers and have enabled PTP mode and whatnot, and for some reason it still doesn't work :/
Also it seems my computer isn't recognizing the device, like I can't go to "My Computer" and find the device there, it used to work.
Tazz. said:
Thanks for all the info! For some reason, after following all the steps, Helium does not work for me. I've downloaded the drivers and have enabled PTP mode and whatnot, and for some reason it still doesn't work :/
Also it seems my computer isn't recognizing the device, like I can't go to "My Computer" and find the device there, it used to work.
Click to expand...
Click to collapse
Be sure you've enable developer options from within about phone. Tap build number repeatedly till says develop options unlocked or whatever. Then in developer options enable USB debugging
Also, in my experience, Dirty Unicorns was very laggy and I greatly prefer TruPureXMM (or OrionOS if you don't wanna get Xposed to tweak your phone—TruPure has very little customization if you don't get GravityBox. Either way, AOSP ROMs are much smoother).
Sent from my XT1575 using XDA-Developers mobile app
aaronpw0621 said:
Be sure you've enable developer options from within about phone. Tap build number repeatedly till says develop options unlocked or whatever. Then in developer options enable USB debugging
Click to expand...
Click to collapse
I've done that as well, but it still does not work at all. Even my computer doesn't recognize the device when I plug it in. It doesn't do the AutoPlay feature asking if I want to explore the contents and stuff.
DubstepWithPON3 said:
Also, in my experience, Dirty Unicorns was very laggy and I greatly prefer TruPureXMM (or OrionOS if you don't wanna get Xposed to tweak your phone—TruPure has very little customization if you don't get GravityBox. Either way, AOSP ROMs are much smoother).
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just wondering, are AOSP ROMS supposed to feel like how I am using my Moto X Pure currently? When I my HTC One M8 I love the ROMs since they were chock full of Xposed Mods as well as just mods from the maker itself(Viper/Venom ROM)
Tazz. said:
I've done that as well, but it still does not work at all. Even my computer doesn't recognize the device when I plug it in. It doesn't do the AutoPlay feature asking if I want to explore the contents and stuff.
Just wondering, are AOSP ROMS supposed to feel like how I am using my Moto X Pure currently? When I my HTC One M8 I love the ROMs since they were chock full of Xposed Mods as well as just mods from the maker itself(Viper/Venom ROM)
Click to expand...
Click to collapse
I suggest downloading the latest device drivers from Motorola support section of their website
Tazz. said:
Just wondering, are AOSP ROMS supposed to feel like how I am using my Moto X Pure currently? When I my HTC One M8 I love the ROMs since they were chock full of Xposed Mods as well as just mods from the maker itself(Viper/Venom ROM)
Click to expand...
Click to collapse
It depends. Some AOSP ROMs (like TruPure) are almost identical to the original firmware with very little customization available requiring you to install Xposed. Other AOSP ROMs (like Orion) have the capability of customization as well as extra features built-in while still providing the stability and smoothness of the original firmware. I'd advise you to browse around and see which AOSP ROM appeals to you the most (definitely take a look at the two I've mentioned, though, as they're currently the best ROMs available for this phone in my opinion).
My personal preference is staying away from CM-based ROMs due to performance, but it's entirely up to you. Dirty Unicorns definitely has a lot of very useful features and tons of customization without needing Xposed at all, I just personally couldn't get past the lag. I don't really need anything from Dirty Unicorns that I can't get with GravityBox on TruPure, but your needs may vary.
Sent from my XT1575 using XDA-Developers mobile app
Temasek's has the notification LED working (and customizable per app). That alone makes it worth the price of admission, the lack of a flashing LED for notifications was driving me nuts. I'm typically not a huge fan of CM since I usually run into bugs, but I do love the theme engine. I just flashed it yesterday & so far so good - everything works & I haven't noticed any lag either.
I have been using Resurrection remix and it is very stable with no lag, highly customizable, and I have been getting really good battery life. I suggest trying that one. I am really liking it.
aaronpw0621 said:
I suggest downloading the latest device drivers from Motorola support section of their website
Click to expand...
Click to collapse
I've tried that as well, no luck
DubstepWithPON3 said:
It depends. Some AOSP ROMs (like TruPure) are almost identical to the original firmware with very little customization available requiring you to install Xposed. Other AOSP ROMs (like Orion) have the capability of customization as well as extra features built-in while still providing the stability and smoothness of the original firmware. I'd advise you to browse around and see which AOSP ROM appeals to you the most (definitely take a look at the two I've mentioned, though, as they're currently the best ROMs available for this phone in my opinion).
My personal preference is staying away from CM-based ROMs due to performance, but it's entirely up to you. Dirty Unicorns definitely has a lot of very useful features and tons of customization without needing Xposed at all, I just personally couldn't get past the lag. I don't really need anything from Dirty Unicorns that I can't get with GravityBox on TruPure, but your needs may vary.
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've never used CM actually always used AOSP or other customizable ROMs actually. So far the most popular I know for the Moto X Pure is DirtyUnicorns and PureNexus(or whatever is called) are there any you have in mind that would be worth looking into?
Jlew7715 said:
I have been using Resurrection remix and it is very stable with no lag, highly customizable, and I have been getting really good battery life. I suggest trying that one. I am really liking it.
Click to expand...
Click to collapse
Thank you, I'll look into it after I unlock my phone and root it!
Dirty Unicorns or Resurrection Remix?
DubstepWithPON3 said:
It depends. Some AOSP ROMs (like TruPure) are almost identical to the original firmware with very little customization available requiring you to install Xposed. Other AOSP ROMs (like Orion) have the capability of customization as well as extra features built-in while still providing the stability and smoothness of the original firmware. I'd advise you to browse around and see which AOSP ROM appeals to you the most (definitely take a look at the two I've mentioned, though, as they're currently the best ROMs available for this phone in my opinion).
My personal preference is staying away from CM-based ROMs due to performance, but it's entirely up to you. Dirty Unicorns definitely has a lot of very useful features and tons of customization without needing Xposed at all, I just personally couldn't get past the lag. I don't really need anything from Dirty Unicorns that I can't get with GravityBox on TruPure, but your needs may vary.
Sent from my XT1575 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well put
Update: I've tried TruPureXMM, OrionOS, and most recently, Pure Nexus; Pure Nexus is definitely my favorite out of all I've tried. Just thought I'd share that with you.
The only problem I'm experiencing is relatively lesser cell reception than I was getting on other ROMs, which is probably only noticeable since I'm in a relatively remote area. I'm pretty sure I saw a flashable improved modem on this site somewhere, though. I'll let you know if I find it and if it helps.
Sent from my XT1575 using XDA-Developers mobile app
DubstepWithPON3 said:
Update: I've tried TruPureXMM, OrionOS, and most recently, Pure Nexus; Pure Nexus is definitely my favorite out of all I've tried. Just thought I'd share that with you.
The only problem I'm experiencing is relatively lesser cell reception than I was getting on other ROMs, which is probably only noticeable since I'm in a relatively remote area. I'm pretty sure I saw a flashable improved modem on this site somewhere, though. I'll let you know if I find it and if it helps.
Click to expand...
Click to collapse
I've got Pure Nexus on my Nexus 9 & love it, if you find that modem link please post it, the constant searching for a better signal is eating the hell outta my battery.
TXJim said:
I've got Pure Nexus on my Nexus 9 & love it, if you find that modem link please post it, the constant searching for a better signal is eating the hell outta my battery.
Click to expand...
Click to collapse
Sadly I don't think my memory was serving me correctly. I looked around for a long while and couldn't find anything like I was talking about, which sucks because I'm losing battery rapidly as well. I was fully charged at 7 this morning and I've been at school/work all day using my phone less since it seemed the battery was going faster. It's only 6:34 PM and I'm currently at 5%.
Sent from my XT1575 using XDA-Developers mobile app
I'm running DU now, which is pretty friggin awesome BTW, I'm actually a little surprised that just flashing PureNexus hosed your modem. Have you tried restoring a backup to get the stock one back again?
TXJim said:
I'm running DU now, which is pretty friggin awesome BTW, I'm actually a little surprised that just flashing PureNexus hosed your modem. Have you tried restoring a backup to get the stock one back again?
Click to expand...
Click to collapse
I received this phone with DU already installed (bought it in mint condition pre-rooted off of Swappa at $325 for the 32gb model—still can't believe I got such a good deal), so sadly, I don't have a backup of stock to restore to. I do, however, have a backup of TruPure which didn't give me reception issues. Although, I'd greatly prefer staying on Pure Nexus solely for the fact that it doesn't require Xposed for customization.
Sent from my XT1575 using XDA-Developers mobile app
The strange encryption misfire between TWRP & LOS-based OS's (questions/thoughts?)
Things we know:
TWRP and LOS-based systems with encryption either don't install correctly or boot correctly afterward. (2 different things perhaps).
Installing Magisk on non-encrypted partition gives boot loop
All LOS-based OS's must be installed on non-encrypted partitions
There is no easily found issue in the Jira issue tracker or TWRP bug tracker about this problem for the OnePlus 5.
I earlier posted this reply in the RR LOS ROM thread in response to another question about LOS-based OS's and encryption. I thought that rather than take a thread off topic, this is a better place for it. (where it can be totally ignored ). I shouldn't have attached this issue to a single ROM's thread since it affects a lot of LOS-based ROMs. There are other little offshoot pieces to this and some may deserve their own threads or questions at least.
TWRP: A number of people using TWRP (official or non) have problems restoring nandroid backups, which pretty much defeats much of the utility of TWRP if you can't do this. Does it have anything to do with Encryption? IT appears to, at least on the encrypted version when using the non-official version. There is a warning about it right in the thread title for non-official TWRP. I've had no problems restoring while encrypted using the official 3.1.1-1 version, but I'm beginning to feel kind of lucky in that regard.
LOS-based systems: These devices that are going to use LOS based systems require decryption of the data partition before installing whichever LOS-based ROM you're interested in. For some people, it's fine. They don't care so I don't see them as having a problem. I actually like encryption and want it, so this problem will keep me from using LOS-based ROMs until it's fixed. I've got a lot of years with Linux and Android experience, have helped with coding and customizing kernels, OSs and recoveries (mostly Philz) in the past, and would be glad to dig into the problem, at least for awhile to see if anything new can come to light but I'm not kidding myself or anyone that I can figure any of this out myself and I'm way out of practice.
Magisk: and non-encrypted partitions are also not happy together, but since I'm not too sure about the nature of that problem, I'll just call it a one-off for the moment.
Things to do: It'd be nice to figure out which area this "blob" of a problem is most likely to be in, and it'd be even nicer if one of the devs that I'll list below already knows where it is and could tell us. I can see some reason for suspecting TWRP and some reason for suspecting a combination of the OP5 FS in combination with the LOS-based ROM (or it's installer). It's not clear yet. I made a quick dirty list of some of the devs either involved with OP5 TWRP or OP5 LOS-based systems and will "mention" them in this thread in case they already know and/or are working on these things.
Another bit of this is that I signed onto Jira bug tracker (Lineage OS) to see if I could find even one sample issue that resembled this on an OP5. I couldn't but I can find some similar ones on other devices with dates only a month old. Part of this would be to try to get this either/both onto the Jira bug tracker or the TWRP bug tracker or both. Another part before that is really deciding whether this issue belongs in those places.
My question:
It's even be helpful to know whether the suspicion of LOS-based ROM and TWRP devs @apascual89, @DarkExistence, @Dees_Troy, @koenkk, @chenxingyu and @xdvs23 is that it is a problem due to TWRP or LOS ROMS or is it the combination of the two? It's be more useful to know what is most suspected to be the actual problem.
Thinking it over: It seems possible that encryption as it exists on the OP5 (in it's native OSs) is not yet available either as a blob or in an API (or in code of course) to LOS. If that's a decent premise, then LOS is just awaiting some nebulous release of either code or prebuilts from OP (not that that's any small thing or can even be counted on).
Personally I'm just curious to know what is thought to be the biggest factor preventing using LOS with encrypted partitions.
Many thanks in advance to anyone that can supply an answer(s). I'm going to do a git on Resurrection Remix to start looking into it. I've got TWRP already and am looking at that. My odds of finding anything are slim alone. If anyone is interested in this, it'd be useful for you to note your interest. If I can think of a unique way (or if you can) to describe this as a LOS-based bug or a TWRP one, then please feel free to either tell me or just open a bug report on Jira or TWRP.
Addition: May as well ask if there's already a link to an issue in Jira. I've scanned it but not found one: https://jira.lineageos.org/browse/BUGBASH-612?filter=-5
Click to expand...
Click to collapse
Clarifications of what I/others would like for the OP5 (TWRP/LOS/MAGISK) spoken of above & below:
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.
Click to expand...
Click to collapse
Updates regarding latest encryption fixes in a couple of LOS-based ROMS:
I got multiple reports that CRDROID (Los-based) and Unofficial RR (LOS-based) are both now patched to work with Encryption.
SO: It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.
More updates about ROMs and TWRP's:
Here's some updates:
1) ROMs: It's looking like the custom LOS based ROM world is headed for encryption in some cases within a few versions. You can look at the last couple pages of official and unofficial RR to see what's been discussed, but it sounds like a trend is forming that pretty much matches the trend of smartphones in general.
2) TWRP: Even though this discussion (it's about the most recent dozen replies that include me, katinatez and xdvs23) is , I think, in the official twrp thread, it's about some combination of a) official b) unofficial and c) katinatez (Damn, I know I spelled his name wrong , sorry).
Official : Good points: Can do working restores encrypted /// Bad: Can't work with OTG
UnOfficial : Good points : Work's with OTG // Bad :: Can't do working restores usually.
katinatez TWRP: Good points: OTG OK, Restores OK, Encryption/Decrytion OK; But: It's not an official nor has a thread for it and you have to self-mount /system before doing these things.
The idea is to combine the best points of unofficial and katinatez and it sounds like development is back on, and maybe a commit of both katinatez and xdvs23's code can be performed pretty soon.
Some progress seems possible!
Click to expand...
Click to collapse
Looks possible that TWRP (Unofficial) just took a leap forward and is doing a bunch of things right:
Things it's doing well (well via the few reports starting here: https://forum.xda-developers.com/showpost.php?p=73220260&postcount=910)
1) Backup / Restore nandroids (I just asked for some details on encryption states in that thread but I think the restore was to encrypted partition.
2) OTG working
3) TWRP Themes working.
4) I'll try it and check adb access and sideload as well and report back.
Click to expand...
Click to collapse
Thanks for carrying on the battle. So far it seems good to me, so nice work! -- I just installed, plugged in and mounted OTG device and did a full (all partitions) encrypted backup to the usb-stick, then restored it. I saw no red characters, and I may have forgot to save the log (doH!) but will look in the backup folder in a bit.
Currently I'm running noLimits with Elemental 1.06. No problems. Oh yeah, themes working fine as well. Unless something odd crops up, this could be a real recovery.
Good work to you guys for persevering.
Other things tested: Sideload mode OK; Adb shell OK. Installed xXx ROM latest version with another kernel: OK.
-- Probably this will be the last entry since a fully functional TWRP was a big thing on the wish list and it appears to be here. The thread is the "Unofficial TWRP" thread currently, but maybe it'll be renamed.
This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.
ArkAngel06 said:
This is the one thing killing me about this phone right now. I'm an avid ROM tester, and I jump from ROM to ROM especially in the early days of development trying to find the one that has the things that I need working.
At the moment, after trying a ROM, there is no way that I know of to get back to stock without flashing stock recovery and stock ROM and re-ecrypting with "fastboot oem lock" and thus wiping your SD card.
It's a crazy amount of work for something that has always been so easy.
Click to expand...
Click to collapse
Same with me. I can a step back and sort of see the long view where this thing gets somehow solved in a day or a month or whatever, and the moment it's solved, no one recalls it was such a pain in the butt. IT does keep me from testing LOS-based OS's because encryption won't work with them. It does keep me on my toes whenever I have to restore my phone from a nandroid backup and that stuff seems like where we should focus some energy.
The thing that bugs me as much as anything is that there's no visibility into anyone "doing anything" about this. I keep hearing people saying (devs too) "I don't know" and "Someone will fix it" and that could certainly happen, (or not). I'd feel much better about it if I could at least search up a bug tracker issue in one of the fairly obvious places (Lineage (Jira) bug tracker) or (TWRP bug tracker).
You're right. It's an insane amount of time to waste for something that should be a 10 minute restore from nandroid backup, but the problem is clearly bigger than that even.
Forgot to add this::
Please try to add any ideas you've got no matter how stupid you might think they are. I'm going to start when I return home.
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week.
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
@ArkAngel06
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585
snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
Click to expand...
Click to collapse
It's no problem, I thought the video might be like a week old or something, but i figured you wouldn't just now be posting the fix if it was done a week ago.
I hope some people give it a try and it works for them. You'd be a hero. :highfive:
There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
ArkAngel06 said:
This would be a partial fix, if true....maybe not for you, because you seem to want/need encryption. But...
https://forum.xda-developers.com/showpost.php?p=73130727&postcount=9
I don't necessarily trust a random person with a sub 100 post count posting a supposed fix for something that seems like a more serious problem, but you asked for it. It's a little sketchy, like Magisk 13.2 passing safety net, when it shouldn't. Unless his Google frameworks hadn't been updated since last week. (week old video)
I'm not sure of your needs, but personally, I would be happy if you could use OOS and LOS both on unencrypted or encrypted. His post shows OOS running on unencrypted, so presumedly you could go back and forth from unencrypted OOS to unencrypted LOS.
I certainly haven't tested it, and I am not really willing to. I have already spent too much time reformatting my phone and starting over from scratch. I'm gonna stay on stock with Magisk till this all gets sorted out.
Click to expand...
Click to collapse
Thanks. I think my "needs" are not very many, but that like a lot of people my wants are more. In the era of very quick processors / TPUs (like the SD835/K960/Exynos/etc) AND dedicated H/W aboard for encryption/decryption, that encryption isn't a speed drain unless benchmarks are your main thing. (even then, I'm not sure it matters). Since encryption is a really important step in keeping at least some portion of our personal data personal, I like the idea of being able to use whichever OS/ROM I can get ahold of that I like with it enabled. It's not a do or die thing. I've used more phones without it than with, but I prefer it.
That's not really my main thrust with this thread, but it's one of them. The main thrust is just a hope that this will be one of those phones (like certain Nex(i) of the past and many phones of the far past including old droids) that allows you to configure them the way you want without too many impediments. I only mentioned about 3-4 items in the original post. If we could get a solid TWRP that reliably does what really defines TWRP (make & restore nandroid backups regardless of encryption) AND allows OTG, of course that's a great starting point. We've kind of got some of that spread across two different versions right now and I expect to see it pretty soon across both. Commits are out there that need applying and debugging so that is headed in the right direction.
The other big thing for me and I see others too is to be able to use the really innovative ROMs that are lately LOS-based without having to use non-encrypted phones, certain file systems, etc. I'd like to just have the phone setup however I want, and install the damned ROMs and have them work about the same regardless. I'm not going to gripe about the usual problem LOS-based ROMs have at first like non-working cameras and other things they need either code or blobs for because that's just normal. Eventually those things will work. I guess that as a long time developer I'd really like to know what developers think is the primary cause of the inability to install and get working LOS-based ROMs on the OP5s that are encrypted. Even if I don't think of it as some huge problem, I think it's really interesting and it's some sort of problem.
Magisk and SuperSU: I guess I just accept that these "SuperUser" utilities are always going to be problematic and part of the forever struggle between manufacturers and users that like to be in control of their phones. These two groups will be leap-frogging one another forever. Until the day when no one can any longer get a bootloader unlocked and root a phone, I'm interested and after that barrier is crossed, XDA will be a lot less interesting place and so will smartphones. Yeah, I realize most users don't even know what rooted means or bootloader. We can keep trying to meet these basic "standards/desires" until then.
So all I want is a good solid TWRP and the ability to install whatever ROM I want to without doing stuff to my phone I don't want to. I'll put this in some hidden section in the OP by the way. ----- Thanks.
snowwolf725 said:
Because I upload the video at 2017/07/16, Magisk 13.2 can passing safety net.
This method also works for LOS on decrypted OP5.
I am so sorry for having low post count, because English is not my native language. :angel:
@ArkAngel06
I also post this method in following posts, however nobody cares about it.
Ref:
https://forum.xda-developers.com/showpost.php?p=73046308&postcount=163
https://forum.xda-developers.com/showpost.php?p=73043647&postcount=585
Click to expand...
Click to collapse
Thanks snowwolf;
I think I replied to some of this in my reply to @ArkAngel06 already and I appreciate it. For Magisk, it seems like we're in a race between Google and the Magisk/SuperSU developers that'll never end. They have to keep leap-frogging each other which I suspect they'll do for a long time yet. It's great to have work-a-rounds and with SuperUser utilities, maybe that's about all we can ever hope for. The emphasis has been thrown on "high security" devices by too many companies and even governments so that the security world will never again look like the beginning of the smartphone era when nearly every phone had an unlocked/able bootloader. I appreciate the reply.
dladz said:
There are some manual scripts you can run to keep the phone decrypted if needs be, personally I wouldn't bother, the stock Roms are superb.
Run the remain decrypted script after each flash and you'll be fine
I have a thread for this in the htc 10 threads
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.
hachamacha said:
I might just be too tired to do this right now, but is there a link to those scripts as well? Thanks for the reply. I think a lot of stock ROMs are really good lately too and most of the time, until really solid TWRP implementations and ROM implementations, I just Root, make backups and fine tune stock ROMs, but I love the idea of having freedom to use LOS-based ROMs in any encryption configuration I want, and to make working restorable nandroid backups which we're still working towards. I appreciate it.
Click to expand...
Click to collapse
This is my thread, never got round to making a script but shouldn't be too hard.
Haven't tried this on the OnePlus but the principle should be the same.
https://forum.xda-developers.com/showthread.php?t=3604856
Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
Another thing to take into account now that may be getting solved with some luck is that the RR official build has had this commit applied today to attempt to fix a LOS-based build to boot encrypted. No one has any idea (I think anyway) whether it works yet, but we should know pretty soon. RR is pretty popular.
Here is the commit(s) I found ::: https://github.com/apascual89/andro...mmit/a13eef258620e0726c6dcd9e83dacc1342080ed6
I'll update the OP if it worked.
Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!
MrWilsonxD said:
Subscribed to this thread, this was a fantastic, cohesive way of trying to get these issues fixed! Hope to see it succeed!
Click to expand...
Click to collapse
Thanks. That was my goal I thought maybe we're getting closer on some of these issues that all sort of whirl about one another in the encryption realm. The 'commit' in RR I noted above in some other reply was at least a brief ray of light but I've heard one report that it didn't work so far. I guess we'll see if anyone gets it to work. Cheers.
Quote of someone (and myself asking questions) from the RR Official thread where the commit to try to fix encryption+LOS happened earlier:
Hecke92 said:
Tried encrypted install, but cannot get past boot screen
Thanks anyway
Click to expand...
Click to collapse
Just curious if there's any details you could share about which version TWRP,
which version and type (SuperSU or Magisk) SU and what you had installed prior to this encrypted attempt.
Also which type of encrypted (ext4, f2fs, etc) would be the target?
many thanks for any information either way.
And the reply I got back::
I have the latest tarp by xdvd (as i saw it was newer than official twrp). I am always using magic, but that is of no relevance I think (because I clean flashed RR and no SU is integrated).
Partition is ext4 and before I had OOS (XXX)
so apparently over in the RR unofficial thread there are users reporting that they flashed and booted on an encrypted device.
success.
Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350
heisenberg33 said:
Solved https://forum.xda-developers.com/showpost.php?p=73143625&postcount=350
Click to expand...
Click to collapse
Hey cool! That's terrific. I don't have time to scan the source and see if it's any different than the changes I listed from official RR but really this at least halfway satisifies the premise of this thread. I guess I'll keep it going until we're sure that TWRP can backup/restore nandroids no sweat regardless of encryption state and also handle OTG devices. Then I think we're onto a more solid start.
I'll fix this thread up tomorrow in the OP and when it's served a purpose will stop updating it. Shouldn't be long
Thanks to you last two guys for shouting this out for people. I asked a question at the end of official about where their github is located. I don't see it in the OP where official RR lists theirs.
Updates from recent comments in RR ROM LOS-based Unofficial & Official versions::
Since I've not yet found the exact source used in the unofficial version which is now working encrypted on the OP5, I'll have to wait to put up a link to it. @Eliminater is the author so credits to him and whoever did the working commit. If @Eliminater can give us a link to the working github where the changes that made encryption work were committed, it'd be appreciated.
Comments from https://forum.xda-developers.com/oneplus-5/development/los-resurrection-remix-n-t3632856 (unofficial RR) seem to indicate that although they managed to get encryption working OK with RR unofficial that they "may" have lost the ability (at this point) to run non encrypted. I'm not certain of this but that's how the comments/replies look. I'm sure it'll settle out soon. I'm also pretty sure that every LOS-based developer for the OP5 knows where the source is where this change occurred and that's more important than me knowing where it is. (so good job!)
Comments from Official RR: https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578 where I found and posted the commit that was supposed to fix encryption, indicate that they're not yet quite there. Comments say that encrypted official RR is not yet working and still boot-loops. Shouldn't take long for them to get these two synced up, but that's just my take. On Official RR, decrypted works.
and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174
gershee said:
and now crdroid is also working on encrypted devices..
same Dev as unofficial rr.. (thanks eliminator!)
no word if it working on both encrypted and decrypted..
https://forum.xda-developers.com/oneplus-5/development/7-1-2-crdroidofficial-t3636441/post73146174
Click to expand...
Click to collapse
Thanks for the report. It looks good for LOS-based ROMs now. 2 out of ~9 or 10 of them are working so they'll all be working with encryption (and without) soon enough. I'll kill off that part of this thread and concentrate more on getting the full-featured TWRP we can all use:
TWRP should be able to:
1) Backup and restore nandroids whether in encrypted or decrypted mode.
2) Be able to access OTG devices
3) Be able to convert or at least create usable a) ext4, b) f2fs (is there more we care about?) filesystems for data and cache.
Click to expand...
Click to collapse
There's a few devs I'm aware of that work on it for OP5 but I'm not going to bug them just yet. I want to be more sure I know what each version of TWRP (off and non-off) can do and can't.
I just installed RR 6.2.1 last night and been having this issue since. Natwest bank's app crashes the moment I open it. I have magisk installed and hidden and also have NatWest bank app selected in the magisk hide list. I have tried resetting the app and clearing caches in TWRP. No luck.
For now I am using a version of this app released last year as a workaround.
I have a similar issue with Amex bank app as well. Where in I am able to setup the app and login but it crashes the moment I try to setup fingerprint login.
Can someone help please?
PS: I have had the same issue with Lineage is 15.1 (which is what RR is based off).
I have the same issue with RR and Linage 15.1, some of official apps that do root/jailbroken checks, tends to close or appear like its crashing.
But this is due to custom ROM's. This is sad truth for now that i found out that there is no way for custom ROM's to be certified official or tested working with Android on older phones.
Someone can correct me if i am wrong.
Fingerprint option missing in "Security" settings after flashing custom ROMs
Hello! I'm trying to install custom ROMs on my OnePlus 8 Pro (IN2020) and have the problem with fingerprint sensor: when I'm using stock firmwares (A10/11, MSM/fastboot) or GSI (kernel doesn't matter), I have an option in "Security" with ability of using fingerprints. But when I'm flashing any custom ROM, I have an option disappeared. I've tried restoring my persist partition, tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix), tried not using Magisk and so on. Nothing helps. I guess there can be different types of fingerprint sensor hardware on our phones, so drivers required. Dev's help will be appreciated, also I'm ready to test and send any info needed. Thanks in advance!
Very common issue, run through the fix persist img position problem thread, at least ask in there.
Bare in mind that custom ROMs like GSI's do not have fingerprint functionality, it allows you to create data but not to use it.
Easy Solution,
MSM to Android 11.
dladz said:
Very common issue, run through the fix persist img position problem thread, at least ask in there.
Bare in mind that custom ROMs like GSI's do not have fingerprint functionality, it allows you to create data but not to use it.
Click to expand...
Click to collapse
I don't think you've read it quite right. I tried fixing persist partition, also GSI ROMs have the fingerprint option for me.
IronSingh said:
Easy Solution,
MSM to Android 11.
Click to expand...
Click to collapse
How can I flash custom ROMs after flashing A11 MSM??? Sounds impossible for me.
Welld1s said:
I don't think you've read it quite right. I tried fixing persist partition, also GSI ROMs have the fingerprint option for me.
Click to expand...
Click to collapse
I've read that the option is there but after enrollment it fails to function.
So you've been through the persist fix?? Have you asked in that said thread?! There's a tonne of people who have had this issue and have got it fixed.
I'm sure they'll know what to do with it
dladz said:
I've read that the option is there but after enrollment it fails to function.
So you've been through the persist fix?? Have you asked in that said thread?! There's a tonne of people who have had this issue and have got it fixed.
I'm sure they'll know what to do with it
Click to expand...
Click to collapse
There is a difference in our situations: their enrollment is failed, but I don't see an option at all. Like the driver or device is not found, so Android thinks I don't have a fingerprint scanner. Tried the persist fix, yes. I'm not a total noob in here, been ROM addict from Samsung S3 stuff I think the problem is we have another fingerprint scanner hardware with different driver needed on some instantnoodlep devices.
Welld1s said:
There is a difference in our situations: their enrollment is failed, but I don't see an option at all. Like the driver or device is not found, so Android thinks I don't have a fingerprint scanner. Tried the persist fix, yes. I'm not a total noob in here, been ROM addict from Samsung S3 stuff I think the problem is we have another fingerprint scanner hardware with different driver needed on some instantnoodlep devices.
Click to expand...
Click to collapse
I know mate, but that's the only thing I could suggest, the GSI and the OOS issues were always different.
Have you changed firmwares, like from regional to global?
I think it would at least be with talking to the person who came up with the persist fix as they obviously know a lot more about this specific issue.
I highly doubt that the hardware is broken.
Not suggesting you're a noob either, just suggesting you've missed something potentially, that could happen to anyone.
Personally I don't know how to fix it as I've never had they issue.
Good luck with it.
dladz said:
I know mate, but that's the only thing I could suggest, the GSI and the OOS issues were always different.
Have you changed firmwares, like from regional to global?
I think it would at least be with talking to the person who came up with the persist fix as they obviously know a lot more about this specific issue.
I highly doubt that the hardware is broken.
Not suggesting you're a noob either, just suggesting you've missed something potentially, that could happen to anyone.
Personally I don't know how to fix it as I've never had they issue.
Good luck with it.
Click to expand...
Click to collapse
I'm not telling you that hardware is broken, I think that hardware is different, because I've read something similar from people who has newer devices.
Welld1s said:
I'm not telling you that hardware is broken, I think that hardware is different, because I've read something similar from people who has newer devices.
Click to expand...
Click to collapse
Right ok, well good luck with that pal.
v.is.for.vladdy said:
Hello! I'm trying to install custom ROMs on my OnePlus 8 Pro (IN2020) and have the problem with fingerprint sensor: when I'm using stock firmwares (A10/11, MSM/fastboot) or GSI (kernel doesn't matter), I have an option in "Security" with ability of using fingerprints. But when I'm flashing any custom ROM, I have an option disappeared. I've tried restoring my persist partition, tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix), tried not using Magisk and so on. Nothing helps. I guess there can be different types of fingerprint sensor hardware on our phones, so drivers required. Dev's help will be appreciated, also I'm ready to test and send any info needed. Thanks in advance!
Click to expand...
Click to collapse
Bro on my op 8 pro my fp option is also missing if u got anything thats works for you pls let me know I'm using my device without fp and it's been 25 days plus... I'm not happy with face unlock..
Bdw i tried fix persist img and msm tool nothing working for me if u got anything brother let me know ... I cant RDA my device no customer service in my city.
Just curious...you're both on 11 right?
The persist fix I believe was originally intended for Android 10 (I know that's when it came out)
My point being, would it be worth downgrading to 10 then running the through the fix?
dladz said:
Just curious...you're both on 11 right?
The persist fix I believe was originally intended for Android 10 (I know that's when it came out)
My point being, would it be worth downgrading to 10 then running the through the fix?
Click to expand...
Click to collapse
Sir, I don't have fingerprint option only on CUSTOM ROMS, which are currently running Android 10 only. I have it perfectly working on STOCK ROMS (A10/A11) and GSI.
Welld1s said:
Sir, I don't have fingerprint option only on CUSTOM ROMS, which are currently running Android 10 only. I have it perfectly working on STOCK ROMS (A10/A11) and GSI.
Click to expand...
Click to collapse
GSI ROMs don't have the fingerprint working mate. .
Thats pretty well known I believe
And a custom ROM would be a complete ROM a GSI is simply a system image, you almost always have to expect issues.. The title of this thread is misleading for that very reason, should have been called "No fingerprint on GSI ROMs"
What happens if you use lineage or Carbon both built for the 1+8pro, my guess is that it'll work.
You could try to flash an actual custom ROM, then wipe system and install the GSI, if that doesn't work then it won't work.
Nothing to do with your hardware, driver, persist or anything else its just a GSI limitation.
Also stop with the patronising attitude, there's no call for it, it doesn't help you, me or anyone else.
dladz said:
GSI ROMs don't have the fingerprint working mate. .
Thats pretty well known I believe
And a custom ROM would be a complete ROM a GSI is simply a system image, you almost always have to expect issues.. The title of this thread is misleading for that very reason, should have been called "No fingerprint on GSI ROMs"
What happens if you use lineage or Carbon both built for the 1+8pro, my guess is that it'll work.
You could try to flash an actual custom ROM, then wipe system and install the GSI, if that doesn't work then it won't work.
Nothing to do with your hardware, driver, persist or anything else its just a GSI limitation.
Also stop with the patronising attitude, there's no call for it, it doesn't help you, me or anyone else.
Click to expand...
Click to collapse
I guess we have a misunderstanding here. What I did and the result - no fingerprint in security options:
1. Flashed stock A10 firmware via MSM, updated to latest A10 version with zip-archive locally
2. Unlocked the bootloader
3. Rebooted to the system once
4. Booted to fastbootd and flashed any custom ROM for both slots (means Lineage OS, Pixel Experience and Carbon ROM) with data/metadata wipes
5. Rebooted to installed system, passed initial setup
6. Set the PIN, got no fingerprint option in settings.
I can repeat: I have it working on stock A10/11 AND GSI, only Lineage, Pixel and Carbon custom ROMs on A10 are affected. Not making something up, not trolling or "patronising", just trying to provide all the useful info that you, for some reason, don't want or can't accept. :/
Edit: my mistake, as I actually didn't try to add any fingerprint on GSI, so can't say that it works for 100% here. I'm just saying, that the option is in place in settings, but not when using custom ROMs like LOS and so on. No offense.
Welld1s said:
I guess we have a misunderstanding here. What I did and the result - no fingerprint in security options:
1. Flashed stock A10 firmware via MSM, updated to latest A10 version with zip-archive locally
2. Unlocked the bootloader
3. Rebooted to the system once
4. Booted to fastbootd and flashed any custom ROM for both slots (means Lineage OS, Pixel Experience and Carbon ROM) with data/metadata wipes
5. Rebooted to installed system, passed initial setup
6. Set the PIN, got no fingerprint option in settings.
I can repeat: I have it working on stock A10/11 AND GSI, only Lineage, Pixel and Carbon custom ROMs on A10 are affected. Not making something up, not trolling or "patronising", just trying to provide all the useful info that you, for some reason, don't want or can't accept. :/
Edit: my mistake, as I actually didn't try to add any fingerprint on GSI, so can't say that it works for 100% here. I'm just saying, that the option is in place in settings, but not when using custom ROMs like LOS and so on. No offense.
Click to expand...
Click to collapse
Then I'm not sure pal.
GSI I would expect it, lineage I haven't installed it but haven't heard anything to suggest it doesn't work.
Carbon ROM I'm pretty sure had the option for me, was a little flakey by it worked..
None taken, sorry I'd barely slept.
PS: seeing as you're on Android 10 why not use twrp? And is born slots necessary? I don't think I did that.
That's the only significant difference I can see between your method and mine.
Also that I set up the phone with a fingerprint each time, not sure if it did or not.
PPS: "don't want or can't accept" yes that's sarcasm pal just saying.
You have a new device. See this thread: https://forum.xda-developers.com/oneplus-8-pro/help/kernel-devs-fingerprint-scanner-t4163005
And this custom kernel fix: https://forum.xda-developers.com/showthread.php?p=83613489
Basically wait for Android 11 custom ROMs to com out.
dladz said:
Then I'm not sure pal.
GSI I would expect it, lineage I haven't installed it but haven't heard anything to suggest it doesn't work.
Carbon ROM I'm pretty sure had the option for me, was a little flakey by it worked..
None taken, sorry I'd barely slept.
PS: seeing as you're on Android 10 why not use twrp? And is born slots necessary? I don't think I did that.
That's the only significant difference I can see between your method and mine.
Also that I set up the phone with a fingerprint each time, not sure if it did or not.
PPS: "don't want or can't accept" yes that's sarcasm pal just saying.
Click to expand...
Click to collapse
Tried with TWRP too, makes no difference for me. Both slots aren't necessary for sure, but that won't hurt too.
I think I tried literally anything except flashing LOS right on A11 OOS, which is a total nonsense. :^(
Welld1s said:
Tried with TWRP too, makes no difference for me. Both slots aren't necessary for sure, but that won't hurt too.
I think I tried literally anything except flashing LOS right on A11 OOS, which is a total nonsense. :^(
Click to expand...
Click to collapse
I didn't suggest flashing Lineage on 11, that's a bad idea wherever said that.
The chap above has a decent idea there, maybe it is hardware.
Give that a shot.
@DJ said:
You have a new device. See this thread: https://forum.xda-developers.com/oneplus-8-pro/help/kernel-devs-fingerprint-scanner-t4163005
And this custom kernel fix: https://forum.xda-developers.com/showthread.php?p=83613489
Basically wait for Android 11 custom ROMs to com out.
Click to expand...
Click to collapse
As I said in the beginning (love quoting myself):
"tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix)"
Doesn't help + gives a distorted image after booting the system on custom ROMs (disappears after locking and unlocking the device again). Looks like the only way is to waaaait. :'c