Related
Hey guys, I'm a bit (and by bit I mean huge) noob since I just switched to Android about 20 days ago. I'm looking to flash a custom ROM on my phone, and I'm looking to keep the awesome battery life the phone brings. I was looking at OmniROM, and that one got my attention since it seems to be stable, clean and most battery efficient (correct me if wrong please!)
However, I have no clue how to proceed. My phone is rooted already, but some tutorials I was reading were for the D802 and required a MicroSD slot.
Can anyone lend me a hand? It'd be hugely appreciated
lunaandres said:
Hey guys, I'm a bit (and by bit I mean huge) noob since I just switched to Android about 20 days ago. I'm looking to flash a custom ROM on my phone, and I'm looking to keep the awesome battery life the phone brings. I was looking at OmniROM, and that one got my attention since it seems to be stable, clean and most battery efficient (correct me if wrong please!)
However, I have no clue how to proceed. My phone is rooted already, but some tutorials I was reading were for the D802 and required a MicroSD slot.
Can anyone lend me a hand? It'd be hugely appreciated
Click to expand...
Click to collapse
First off you need to install TWRP recovery or CM recovery. Once those are complete you can continue on. Which I can help once you get there.
Link: http://forum.xda-developers.com/showthread.php?t=2449670
magestic1995 said:
First off you need to install TWRP recovery or CM recovery. Once those are complete you can continue on. Which I can help once you get there.
Link: http://forum.xda-developers.com/showthread.php?t=2449670
Click to expand...
Click to collapse
Done. I have installed TWRP and went ahead and downloaded the OmniROM file. What is next?
Thanks, by the way
lunaandres said:
Done. I have installed TWRP and went ahead and downloaded the OmniROM file. What is next?
Thanks, by the way
Click to expand...
Click to collapse
This is a link to the second post of the omni rom thread http://forum.xda-developers.com/showpost.php?p=47236432&postcount=2 . It gives step by step instructions on how to install using TWRP. This method is usually the same for all ROMs
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 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
Hi all, is it worth waiting for the official Oreo update before unlocking?
Will it be a advantage to flash after taking the update, or doesn't it really matter?
I've been putting it off for a while but I'm starting to get board of waiting.
Have you read the forum regarding people who are having various issues, oreo is in beta stage at best, so if you want functionality of your phone as it is, then either wait as I am or consider a nougat rom.
Regards Ray
What is the rush? Is there a problem with your device as it is? Is there some feature of Oreo that can't live without?
Unless you understand the implications of rooting/romming this device, ALL of them including potential issues going back to stock and relocking the bootloader, just stay stock and wait... If you did understand all the implications than you probably wouldn't be asking this question.
Till Motorola releases the oreo update they won't release the kernel source for this device . And Kernel source would be important for stable rom.
I had this feeling too. I really, really, wanted to be on Oreo because of theming and the new features. I unlocked my phone, installed TWRP, failed, and bricked it. I was able to recover and, well, no more ROMing for me. I'd wait for the stable Oreo ROM. It's worth the wait.
reCoded said:
I had this feeling too. I really, really, wanted to be on Oreo because of theming and the new features. I unlocked my phone, installed TWRP, failed, and bricked it. I was able to recover and, well, no more ROMing for me. I'd wait for the stable Oreo ROM. It's worth the wait.
Click to expand...
Click to collapse
You are a senior member how you failed?
Flashing phones isn't a worry for me, I've done every phone I've had.
All I was asking is, is there any advantage in getting the new bootloader that will come with the stock Oreo.
ugupta100 said:
You are a senior member how you failed?
Click to expand...
Click to collapse
Just because I'm a senior member doesn't mean I know how to do everything. Jumping from 32-bit ROMs to 64-bit ROMs is much different than with a 32-bit ROM. I can easily install a 32-bit ROM but installing 64-bit TWRP requires extra stuff which I didn't do, which bricked my device.
reCoded said:
Just because I'm a senior member doesn't mean I know how to do everything. Jumping from 32-bit ROMs to 64-bit ROMs is much different than with a 32-bit ROM. I can easily install a 32-bit ROM but installing 64-bit TWRP requires extra stuff which I didn't do, which bricked my device.
Click to expand...
Click to collapse
Thanks for the warning, I'll keep that in mind.
reCoded said:
Just because I'm a senior member doesn't mean I know how to do everything. Jumping from 32-bit ROMs to 64-bit ROMs is much different than with a 32-bit ROM. I can easily install a 32-bit ROM but installing 64-bit TWRP requires extra stuff which I didn't do, which bricked my device.
Click to expand...
Click to collapse
Can you expand on this a little?
I thought it was just a matter of flashing the newest version of twrp with 64bit support and finding a 64bit ROM you liked?
eemgee said:
Can you expand on this a little?
I thought it was just a matter of flashing the newest version of twrp with 64bit support and finding a 64bit ROM you liked?
Click to expand...
Click to collapse
It doesn't work like that since the stock software is 32-bit and the TWRP version is 64-bit. You have to flash a modified boot.bin file (or something like that) to make the software compatible with 64-bit TWRP. I'm not too sure what to do since I couldn't find any tutorials.
reCoded said:
It doesn't work like that since the stock software is 32-bit and the TWRP version is 64-bit. You have to flash a modified boot.bin file (or something like that) to make the software compatible with 64-bit TWRP. I'm not too sure what to do since I couldn't find any tutorials.
Click to expand...
Click to collapse
Well they kept that quiet! I had a look around and wouldn't see anything either.
Hello again all!
So I've recently discovered the glory of GSI / Treble roms! Good stuff! But after much banter with Ressurection remix's 9.0 GSI rom, I have still yet to get it working, and wasn't sure if I'm just missing something.
So far, what I've tried is:
- Wiping everything (caches, system, data) as well as formatting my data partition
- then installing the rom. after a couple of routine-looking reboots, the system boots without gapps functioning great.
- quick settings states 'No SIM card', which is false
- reinstalled rom countless times
- restored to functioning rom, backed up EFS, reinstalled RRemix in the same fashion, restored EFS backup. No solve there.
And with that, I'm out of ideas and without much knowledge of GSI / Treble processes, I'm not even sure how to word searches for help. Any advice ya'll?
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Derbyy said:
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Click to expand...
Click to collapse
I'm interested in this for sure. I'm curious, are you guys using the A only IMG of treble ROMs?
jal3223 said:
I'm interested in this for sure. I'm curious, are you guys using the A only IMG of treble ROMs?
Click to expand...
Click to collapse
It’s funny you should reply to me on today of all days. This morning, after a month of testing, I finally succeeded in getting my RP2 to A/B boot RR 7, TWRP, AND have it rooted with Magisk. I couldn’t believe I finally got it. AMA
Are any of you on Verizon? I've tried multiple GSIs and have never gotten LTE to work properly.
Reznor7 said:
Are any of you on Verizon? I've tried multiple GSIs and have never gotten LTE to work properly.
Click to expand...
Click to collapse
Did you try an A only image? It should work as it doesn't touch the vendor image or CSC. At first I was trying AB images on my Note 9 and could never get signal. I found out that we are only supposed to use the A only images on that device and my problems were solved. I haven't tried anything on my Razer Phone 2 though as the stock ROM is pretty much exactly what I want. It's worth a try.
Need RR help.
Derbyy said:
Hey man, let me know if you still haven’t gotten this resolved and are still looking to do so. After days of research and experimentation I finally created a process to reliably flash a fully functional RR 7.X rom. I can provide my boot.img and instructions if you need them.
Click to expand...
Click to collapse
Hey, can I get that boot.img and instructions if you can still provide them? I want to install r.r 7.x please. Sorry for messaging you 4 months later.
jal3223 said:
Did you try an A only image? It should work as it doesn't touch the vendor image or CSC. At first I was trying AB images on my Note 9 and could never get signal. I found out that we are only supposed to use the A only images on that device and my problems were solved. I haven't tried anything on my Razer Phone 2 though as the stock ROM is pretty much exactly what I want. It's worth a try.
Click to expand...
Click to collapse
sorry to disturb you years later,but why not try to flash another gsi like crdroid,boot into it and flash you rr rom back?
this strange method worked on my redmi 10a