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.
Related
The ROMs seem to have bugs so I intend to just use a custom kernel and remove bloat apps. Maybe when I find a ROM updated enough so there aren't any bugs, then I will shift to it.
Also, the updating process for ROMs in general seems very time consuming and frustrating. Plus you have to backup everything before an update to the ROM. This is why I wish to just stay with the stock, until I find something that is less time consuming.
Also - Is there a guide/FAQ for the whole root/rom/kernel/bootloader thing for noobs? If so can you please link it to me?
Thank you.
imda1 said:
The ROMs seem to have bugs so I intend to just use a custom kernel and remove bloat apps. Maybe when I find a ROM updated enough so there aren't any bugs, then I will shift to it.
Also, the updating process for ROMs in general seems very time consuming and frustrating. Plus you have to backup everything before an update to the ROM. This is why I wish to just stay with the stock, until I find something that is less time consuming.
Also - Is there a guide/FAQ for the whole root/rom/kernel/bootloader thing for noobs? If so can you please link it to me?
Thank you.
Click to expand...
Click to collapse
Well, I'll try to clarify some things here. I'm using the Lineage OS Unofficial ROM for this phone. I can't speak for all the other ROMs, but Lineage has been very stable, supports the fingerprint gestures, and if all goes well then we'll see official Lineage OS builds before long. Same thing happened happens with my Moto G3. As for bloat, Lineage doesn't really come with any besides their forked AOSP apps, some of which are replaced by the official Google versions depending on which Open GApps version you choose.
As for updating, Lineage is still unofficial so that means manual flashing, but honestly you can stay on a build for quite some time, there's not a lot of major changes from one nightly to another. Also you can dirty flash updates meaning you don't need to wipe everything, just flash the updates and clear the cache as TWRP suggests after flashing. Once it gets an official build you can update in the System Settings.
A quick look at the Guides forum for this phone would have shown you this collection of guides:
https://forum.xda-developers.com/g5-plus/how-to/howto-ultimate-g5-plus-guide-unlocking-t3593531
Please try to search the forum and look at top and stickied posts in the future. I hope this helped, custom ROMs can do a lot of great things.
Edit: I will say however there's nothing wrong with staying on stock if you choose. I happen to love ROMs but it's personal preference.
That thread and others in the guides section have a ton of useful support whether you're an avid ROM enthusiast or just trying to improve on stock.
To answer your question about updates when staying on stock but using a custom kernel, you won't be able to get them correctly because your /boot (kernel) and /recovery (TWRP) partitions aren't stock anymore which it'll detect and fail.
When updates come you can either return to stock using the tools/guides here, take the OTA then reinstall TWRP and custom kernel (which does take some work to get back where you were), or hopefully a benevolent Dev here will create a flashable zip from the update you can just do in TWRP, which is often the case but we'll have to wait & see. In either case it's still worth it imo for the control you get over the system compared to remaining fully stock.
Can someone make flashable zip of the recent update that fixes the 911 bug?
Hi,
Good question! :angel:
I explain it for another device (Moto G4):
http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
Simple explanation:
- You can update with OTAs if you never modify the SYSTEM partition.
- You can install the OTA using any custom recovery (for example TWRP) is you spoof the build thumbprint: you can edit the ZIP of the OTA, or change the data in the recovery.
- The OTA will install a new kernel (it fully overwrite the partition), so you will require to re-root.
That's all!
Use flashfire
zeft64 said:
Use flashfire
Click to expand...
Click to collapse
What's your experience with it so far with G5 Plus, or others using it with our device?
If none, maybe be careful about recommending it without giving further info.
Installed it and on first screen (Actions) it says:
"Motorola devices experimental
While some basic testing has been done for flashing this brand's firmwares, caution is still advised. Please consult with expert users for this brand before performing potentially dangerous actions."
It also says on the Playstore blurb and Chainfire's XDA thread for it that it works "without using a custom recovery", so if we have one is that a problem? I know it is for flashing OTAs otherwise, but does it get around having one if you do?
More generally it also says in both places:
"FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and the XDA discussion thread before doing anything potentially destructive"
Avoid flashfire... I tried to install something and let the device "dead"... I don't know how, but got back to life after some minutes...
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Dahenjo said:
What's your experience with it so far with G5 Plus, or others using it with our device?
If none, maybe be careful about recommending it without giving further info.
Installed it and on first screen (Actions) it says:
"Motorola devices experimental
While some basic testing has been done for flashing this brand's firmwares, caution is still advised. Please consult with expert users for this brand before performing potentially dangerous actions."
It also says on the Playstore blurb and Chainfire's XDA thread for it that it works "without using a custom recovery", so if we have one is that a problem? I know it is for flashing OTAs otherwise, but does it get around having one if you do?
More generally it also says in both places:
"FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and the XDA discussion thread before doing anything potentially destructive"
Click to expand...
Click to collapse
I'm sooooo glad someone else commented on this. I'm sorry man.
This is an effort to consolidate fixes, tweaks and mods specific to the rooted G955U/G955U1 SnapDragon S8+ via SamPWND.
The initial release of root for this version by the development, contributions and tireless efforts from elliwigy, Harry44, akiraO1, BotsOne, GSMCHEN and jrkruse are obviously being enjoyed by many, as is evident by the visits to elliwigy's release page.
Unfortunately, that thread is in dire need of clean-up because it has become a hodgepodge of redundant rooting questions, helpful answer posts (and complaints), all infused with a few mods and tweaks mentioned.
So let's share what can be done (and what cannot thus far) with this rooted version.
Please (!!!), already be aware of which device you have, and if SamPWND works on your device. "How do / Can I root my..." questions simply don't belong here!
Let's try to keep it clean in here by looking around the forum first before posting, but also by being helpful and not condescending to those of us enjoying root who are perhaps not as knowledgeable about such matters as others.
Some of the most common questions being asked, and their answers from that thread
Flashfire infinitely spinning for part 2 root steps
Turn on airplane mode
Is there a fix for the 80% battery max capacity?
No, and it seems unlikely at this stage. Make yourself happy and hide your battery percentage.
Green/glitchy screen
Most (including myself) have resolved or heavily mitigated this via the AQI1 fw posted recently.
S8+: https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673810
S8: https://forum.xda-developers.com/ga...ampwnd-green-screen-corruption-fixed-t3673782
Does Magisk work with this root?
No.
Does Xposed work on this root?
Unofficially yes, search for unofficial Xposed s8, it will be in the device forums. Edit-or use this link: https://forum.xda-developers.com/galaxy-s8+/how-to/unofficial-xposed-guide-snapdragon-s8-t3663728
Can I install custom roms?
No, the BL is still locked. The last I read is there are some ideas around how we might achieve an unlock, but nothing so far. There's is the modified stock rom available in the OP of the root thread that provides csc and superSU but beyond that, no.
Screen rotation is messed up / reversed
You downloaded the wrong step 1 files. Try again for your device (plus or non-plus)
I can't think of any other recurring questions, but I've been keeping up to date on that post for more of the 318-or-so pages, and there's a lot of other useful information held within them. Worth a read.
Awesome first response!
So can I start with this:
"Unofficial Xposed'...
Where are the where's & how's located for our specific device, along with the yeahs & no's about what Xposed can do? I've looked and read, but there really is no clear post (that I have found) saying that our model can (or can't) DL Xposed and make things work.
Out of level 8, I'm probably a level 2 coming from rooting back in the days of the first Droid LOL! So I figure if we can keep things down to a level 3 or 4 here, we can learn and teach about WHY certain things won't work.
I'm also very interested in the capabilities of our camera. I used to use chdk to hack Cannon P&S cameras, and despite all my hours doing so, the hardware could never deliver night shots like this phone!
AddictedToGlass said:
Awesome first response!
So can I start with this:
"Unofficial Xposed'...
Where are the where's & how's located for our specific device, along with the yeahs & no's about what Xposed can do? I've looked and read, but there really is no clear post (that I have found) saying that our model can (or can't) DL Xposed and make things work.
Out of level 8, I'm probably a level 2 coming from rooting back in the days of the first Droid LOL! So I figure if we can keep things down to a level 3 or 4 here, we can learn and teach about WHY certain things won't work.
I'm also very interested in the capabilities of our camera. I used to use chdk to hack Cannon P&S cameras, and despite all my hours doing so, the hardware could never deliver night shots like this phone!
Click to expand...
Click to collapse
You may have read my post just before I edited it to add the links. The link I posted for the s8 is where all if the Xposed info is held for our devices. I am currently running it with the latest fw I also linked to with no problems. That thread also contains a few modules the OP has verified working. I am currently only using it for a couple of tweaks from "all my.." and xVoice++. I also was utilizing this Xposed version before flashing the fw mentioned, and it's worked perfectly for both. I can't remember which fw I was on previously though.
regarding camera mods, I made an attempt the moment I got the phone to replace the stock camera with a ported pixel, before researching how to do it properly these days. Wound up with crashing camera warnings every 30 seconds and my backup wouldn't restore properly in titanium and had to reset completely and start fresh.
I used to root back in the Motorola Droid (original) days, when root required 30-or-so lines of commands, I'm sure you remember funny how we've come full circle. I swapped to iPhone for the iPhone 4, enjoyed a bootrom exploit for several iOS versions, and stuck with apple up until just last weekend so it's been a while since I've been on the root scene myself, much has changed indeed. It's the first Android device (S8+ here) that actually made me want to switch away from apple, and I don't yet regret it.
nice concept.. just a forewarning tho, these posts typically go in general discussion..
elliwigy said:
nice concept.. just a forewarning tho, these posts typically go in general discussion..
Click to expand...
Click to collapse
Thanks! And it's alright if it gets moved there so long as it still helps everyone out and you wizards walk through once in a while to bless us all with a bit of wisdom. LOL!
Meanwhile, for as long as it's allowed to stay here, it might serve well to keep distractions off your release thread.
elliwigy said:
nice concept.. just a forewarning tho, these posts typically go in general discussion..
Click to expand...
Click to collapse
Considering less than one hour after I replied with the common questions and answers, someone asked about flashfire on page like 318 again, I'm sure this post is pretty low on priority for the people who tend to ask the questions.
I just finished rooting my sprint s8+ with sampwned. I installed my 256gb micro sdcard and I get the kernel panic reboot to error screen. Am I unable to use the sdcard? I'm scouring xda for any info. Just looking for a little help if anyone knows anything I don't. Thanks.
Nice idea OP.
Some fixes may be had by using the @partcyborg ROM for S8. It is in the S8 ROMs, Kernels, ... Forum https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
For the S8+ @jrkruse has some good info in the S8+ Verizon, ROMs, Kernels, ... Forum. https://forum.xda-developers.com/verizon-galaxy-s8+/development
monroe0328 said:
I just finished rooting my sprint s8+ with sampwned. I installed my 256gb micro sdcard and I get the kernel panic reboot to error screen. Am I unable to use the sdcard? I'm scouring xda for any info. Just looking for a little help if anyone knows anything I don't. Thanks.
Click to expand...
Click to collapse
i think u pmd me but flashing a newer combo boot.img fixes it.. its a known issue with samsungs older combo firmwares, not related to root
elliwigy said:
i think u pmd me but flashing a newer combo boot.img fixes it.. its a known issue with samsungs older combo firmwares, not related to root
Click to expand...
Click to collapse
Yea thats what I did. Problem solved.
Just want to add that the Official xposed app and framework, work on this device
Sent from my SM-G955U using Tapatalk
I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194
Greetings to the following maintainers of current, or upcoming, Pie roms.
In no particular order...
@PixelBoot, @voidz777, @minidude2012, @calebcabob, @semdoc, @ggpew2, @AndyYan, and last, but certainly not least @razorloves
First, I applaud you all for the work you do in maintaining these roms and keeping the Nexus 6P relevant and thank you. I've been flashing roms since KK and y'all keep Android fun!
Now for my humble request.... As it seems most, if not all, Pie roms are trending away from FDE to FBE recovery, I am unable to use them with FBE apparently as I am with Total Wireless (in the SE United States) and it's "TRACFONE.VZWENTP" APN never survives the formatting of data or installing the FBE twrp recovery. To compound the issue, the roms also are missing the APN "+" sign to add an APN & the "EDIT APN" field is grayed out, not allowing me to manually install nor edit to get the correct APN.
Is it possible to begin baking in either the APN itself (I'm happy to provide the info if necessary) or at least the ability to add & edit please? I appreciate your consideration.
Either way, again, thank you for your efforts!
Best regards,
NatesLaw
"Most if not all pie ROMs are going to fbe"? This is a bit of stretch. There's 4 fde based pie ROMs, and six fbe, with three of those fbe ROMs put out by the same person.
If it was more of a wide spread issue I'd see it making sense to look but you look to be a very small minority, that's just my two cents though.
I'd honestly just stick to fde like I do, there's no reason to need access to and flash 30 different roms lol. We have aicp, aosip, ressurection remix, and a stock rom.
Lawlrus said:
"Most if not all pie ROMs are going to fbe"? This is a bit of stretch. There's 4 fde based pie ROMs, and six fbe, with three of those fbe ROMs put out by the same person.
If it was more of a wide spread issue I'd see it making sense to look but you look to be a very small minority, that's just my two cents though.
I'd honestly just stick to fde like I do, there's no reason to need access to and flash 30 different roms lol. We have aicp, aosip, ressurection remix, and a stock rom.
Click to expand...
Click to collapse
As I said, it's merely a humble request. This is a forum, so I'm just using the opportunity to ask. If they aren't interested, then that's fine. No hard feelings either way, but I don't think it hurts to ask. I hope you have a great day.
@Lawlrus
Good day. Not sure of your expertise level but since you're the only one to respond perhaps you can answer a question please.
Once I flash a rom (btw, even ACIP Pie doesn't have my APN or way to add it) do you think that's it's possible, after flashing a rom, that perhaps then flashing my stock EFS backup might add the correct APN?
If you, or nobody, knows that fine.... Just thought I'd ask, in case, so I'm not wasting effort should the answer be "negative ".
TIA
Regards.
NatesLaw said:
@Lawlrus
Good day. Not sure of your expertise level but since you're the only one to respond perhaps you can answer a question please.
Once I flash a rom (btw, even ACIP Pie doesn't have my APN or way to add it) do you think that's it's possible, after flashing a rom, that perhaps then flashing my stock EFS backup might add the correct APN?
If you, or nobody, knows that fine.... Just thought I'd ask, in case, so I'm not wasting effort should the answer be "negative ".
TIA
Regards.
Click to expand...
Click to collapse
I *think* I already asked in another thread where you posted about your issues about adding the APN manually, and it was stated that the option is greyed out. If that was the case I wouldn't know what the reason would be other than the service you have.
As far as flashing the efs, I have done it before, and I've seen other people do it. But when it comes to your efs, its something you definitely do not want to play with if you're not ready or able to deal with it if it goes poorly. Your efs contains your iemi number (this is the reason why everyone should back up their efs regardless but 90% don't) if playing around flashing your efs backup, then a ROM, flashing the backup etc etc, and something goes wrong, it can be very wrong. Without your iemi your phone is nothing more than a tablet at that point. If you lose it, or if you're messing around flashing and the backup gets corrupted, then you're Sol. There is no way to get it back without a working backup, aside from using illiegal programs that phone thieves use that i'm not going to get into.
Before trying to reflash the efs backup you have, I'd completely start from scratch. If there's no way to add your apn manually, reflash the DEC factory image, and the radio, reroot/recovery/all that bull**** and see what happens. If you still have the issue, try messing with your efs backup.
I'm an old user, I've been flashing phones since android 2.x so I'm not nearly as picky as most people, flashing a new ROM every couple days isn't as exciting as it used to be for me, I spent years flashing multiple ROMs weekly, sometimes daily. But now I just stick on winexusers stock ROM 98% of the time because it works, and I don't need 900 flashy features that end up ****ting up the experience for me if features go wrong. What this means, is consider sticking with what works. If only 2 9.0 ROMs work with your service, who gives a ****? Enjoy 9.0. If you're stuck using 8.1 then what's it matter? 9.0 battery is much worse than 8.1 and aside from security updates, 9.0 is 8.1 but flaky as fk because we don't get official 9.0. As far as security updates, when is the last time you saw a vulnerability that only a kernel update fixed, that wasn't caused by people installing the vulnerability, or being stupid themselves?
NatesLaw said:
@Lawlrus
Good day. Not sure of your expertise level but since you're the only one to respond perhaps you can answer a question please.
Once I flash a rom (btw, even ACIP Pie doesn't have my APN or way to add it) do you think that's it's possible, after flashing a rom, that perhaps then flashing my stock EFS backup might add the correct APN?
If you, or nobody, knows that fine.... Just thought I'd ask, in case, so I'm not wasting effort should the answer be "negative ".
TIA
Regards.
Click to expand...
Click to collapse
That's weird man, I've never had an issue not being able to edit my APN on any ROM, including Pie ones.. If its bcuz of your carrier, what happens when you remove your SIM card and set it up without it, then see if your APNs editable then?
Have you tried any of the apps in the PlayStore? I know there's quite a few in there, that try to enable the edits in different ways. Saw one that listed a ton of carriers and you can just select yours.
Good luck
Sent from my [device_name] using XDA-Developers Legacy app
Talysdaddy said:
That's weird man, I've never had an issue not being able to edit my APN on any ROM, including Pie ones.. If its bcuz of your carrier, what happens when you remove your SIM card and set it up without it, then see if your APNs editable then?
Have you tried any of the apps in the PlayStore? I know there's quite a few in there, that try to enable the edits in different ways. Saw one that listed a ton of carriers and you can just select yours.
Good luck
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hello & good evening.
Yes, it's probably because we're on Total Wireless, which uses Verizon's system but has it's own APN.
I may try the Sim card trick, thanks. Lately I've just been using stock (rooted) so the performance is fine. I just used to enjoy trying new roms back with my old LG G3. It was SO easy to root and flash back then.
God bless!!
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