http://www.mediafire.com/file/bjxvu....651.1-4.24.651.1_release2dk2r14ngv5s3bvl.zip Here you are untouched best of all it fixes voice recognition.
I'm anxiously waiting for someone to post a deodexed version. =)
That wouldn't do much the biggest update when you pull it apart is to the firmware.
Update? for?
Rooted?
snarf
Not rooted yet.
yeah. I've been waiting for this voice issue update for a while. however, I'd rather just have unlimited power and freedom to do what I want with the hardware HTC gave us. Filtered Sprint crap.
Looks like theres a new radio here? Since this is only a patch OTA it'll have to be flashed over the top of a stock. Working on a flashable right now, any testers?
It is fully rootable btw via revolutionary.
squidlymandingo said:
It is fully rootable btw via revolutionary.
Click to expand...
Click to collapse
That would be because its not really a full OTA, just an OTA containing patches to already existing files in order to fix small bugs. In fact it doesnt even add new files, just patches pre existent ones which is why it is being a ***** and a half. You have to deodex the patches lol.
I had thought it was supposed to be in January and I am still not even seeing rumors for it, has anyone heard anything?
If you are a rooter, Mandatory mode for SELinux (Android 4.4) is only likely to make your life more difficult.
So I would say - be careful what you wish for.
bftb0 said:
If you are a rooter, Mandatory mode for SELinux (Android 4.4) is only likely to make your life more difficult.
So I would say - be careful what you wish for.
Click to expand...
Click to collapse
Is it already confirmed in the release? Or just a rumor? Also would that block root? or just recovery and roms?
Morkai Almandragon said:
Is it already confirmed in the release? Or just a rumor? Also would that block root? or just recovery and roms?
Click to expand...
Click to collapse
It isn't a rumor - SELinux has been present in Android since 4.2, but operating in "permissive" mode (which basically blocks no violations, but logs the violations which occur). This was done to give an opportunity to app/framework developers to modify their apps so that they will not fault once SELinux changes over to enforcing in KitKat (4.4). This has been in the Google road map for a long time.
Of course, it can be turned back to permissive mode in a full custom ROM, so my comment applies to stock or near-stock situations. In particular, the initial rooting operations may get more technically difficult to acheive.
(With SELinux enforcing mode, a root user identity obtained by an exploit can have very limited capabilities, depending on the process context of the attack vector)
For instance if you were to accept an OTA on lightly-rooted stock, and then lose root during an OTA upgrade, it might be quite difficult to re-attain root.
Recovery and ROMs are already quite limited (for retail VZW N3 devices) because of the trusted boot enforcement.
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.
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 a xt1602 with may security patch.
If I flash the earlier stock ROM would it hurt?
Will the bootloader will face any problems?
Whatever you do, just skip the bootloader part when downgrading! Other than that, there is no risk.
ProudlyTM said:
Whatever you do, just skip the bootloader part when downgrading! Other than that, there is no risk.
Click to expand...
Click to collapse
Thank you very much! Being a noob that I am, can you please tell me how can I skip it? Or point me to a tutorial that does it.
manasn said:
Thank you very much! Being a noob that I am, can you please tell me how can I skip it? Or point me to a tutorial that does it.
Click to expand...
Click to collapse
No problem! When you are flashing the stock ROM files with fastboot, just skip the fastboot flash bootloader command.
ProudlyTM said:
No problem! When you are flashing the stock ROM files with fastboot, just skip the fastboot flash bootloader command.
Click to expand...
Click to collapse
Thank you, I am just preparing myself towards rooting and having a safe way back when official nougat gets released.
manasn said:
Thank you, I am just preparing myself towards rooting and having a safe way back when official nougat gets released.
Click to expand...
Click to collapse
Just be careful if you've downgraded that you don't install an OTA update, especially if your bootloader and your system are not at the same patch level. We've seen many instances of downgraded devices being bricked as the OTA patches their newer bootloader (as the OTA appears to assume that your system is the same patch level as your bootloader), which corrupts to the point of requiring a blank flash or a motherboard replacement.
If you've downgraded, the safest way to update would be to wait for the fastboot 7.1.1 stock ROM rather than chance it with the OTA.
echo92 said:
Just be careful if you've downgraded that you don't install an OTA update, especially if your bootloader and your system are not at the same patch level. We've seen many instances of downgraded devices being bricked as the OTA patches their newer bootloader (as the OTA appears to assume that your system is the same patch level as your bootloader), which corrupts to the point of requiring a blank flash or a motherboard replacement.
If you've downgraded, the safest way to update would be to wait for the fastboot 7.1.1 stock ROM rather than chance it with the OTA.
Click to expand...
Click to collapse
Oh, thank you! You just saved a noob's device (mine) from getting bricked in future.
I went ahead yesterday and rooted my device.
Things have happened in the following manner
I purchase a moto g play xt1602 retin
I get may security patch OTA, I install it. All stock.
I unlock bootloader and flash TWRP
Take a backup of new rootless pristine system using TWRP
Root using supersufixer.zip and supersu.zip in TWRP, take another backup.
Now, my plan was as following
Stay on rooted stock, reap AdAway benefits and lower brightness below minimum(didn't happen)
Wait for Nougat OTA
When it arrives, follow https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797 this guide but just skip flashing bootloader
Boot into newly flashed stock and proceed with updates
But reading your reply makes me sure that this process will possibly brick my beloved moto g4 play. So I should either wait for may stock build or Nougat stock build zip and not apply OTA when it arrives. Am I correct?
Apologies for being so verbose but I'm sweating. I don't like sweating.
manasn said:
Oh, thank you! You just saved a noob's device (mine) from getting bricked in future.
I went ahead yesterday and rooted my device.
Things have happened in the following manner
I purchase a moto g play xt1602 retin
I unlock bootloader and flash TWRP
Root using supersufixer.zip and supersu.zip in TWRP, take another backup.
Now, my plan was as following
Stay on rooted stock, reap AdAway benefits and lower brightness below minimum(didn't happen)
When it arrives, follow https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797 this guide but just skip flashing bootloader
Boot into newly flashed stock and proceed with updates
But reading your reply makes me sure that this process will possibly brick my beloved moto g4 play. So I should either wait for may stock build or Nougat stock build zip and not apply OTA when it arrives. Am I correct?
Apologies for being so verbose but I'm sweating. I don't like sweating.
Click to expand...
Click to collapse
I followed a similar path - happily remaining on stock MM with July 2016 patch level for the last 8 months. I block OTA updates by disabling/freezing Motorola Update Service (com.motorola.ccc.ota). Simple, effective, works.
Device (XT1607) is fully unlocked, rooted and rocking Xposed with a small but potent suite of modules that brings out the best in this phone. I'm in no hurry for stock Nougat. Will update in time once migration path is clear and benefits outweigh effort/risk. I lack nothing Android 7.x brings to the table.
Don't forget to take an occasional nandroid in TWRP; store it on the SD card or off-device. Can be a life saver.
Wait - what about that ancient xxx patch level? OMG!! I'll be pwned by evilness everywhere. Relax, surf responsibly....everything will be fine.
I don't like to sweat about mundane things either. There is no reason to. Many sweaty soles are self inflicted. Don't become one of them.
Davey126 said:
I followed a similar path - happily remaining on stock MM with July 2016 patch level for the last 8 months. I block OTA updates by disabling/freezing Motorola Update Service (com.motorola.ccc.ota). Simple, effective, works.
Device (XT1607) is fully unlocked, rooted and rocking Xposed with a small but potent suite of modules that brings out the best in this phone. I'm in no hurry for stock Nougat. Will update in time once migration path is clear and benefits outweigh effort/risk. I lack nothing Android 7.x brings to the table.
Don't forget to take an occasional nandroid in TWRP; store it on the SD card or off-device. Can be a life saver.
Wait - what about that ancient 716 patch level? OMG!! I'll be pwned by evilness everywhere. Relax, surf responsibly....everything will be fine.
I don't like to sweat about mundane things either. There is no reason to. Many sweaty soles are self inflicted. Don't become one of them.
Click to expand...
Click to collapse
Okay! Haha I feel much better now, lets see what happens
manasn said:
Okay! Haha I feel much better now, lets see what happens
Click to expand...
Click to collapse
As Davey126 has mentioned, you might as well enjoy your ad-free device and treat your eyesight and not worry too much about getting the Nougat OTA. Besides, you'll want to wait to see if there are any pertinent issues with the 7.1.1 update (even with the soak test, some bugs might still emerge in wider deployment), which you may avoid if you don't need to upgrade to the newest patch
Furthermore, mods like xposed don't work fully on Nougat (rovo89 hasn't released an official xposed, and the unofficial builds are still hit and miss), so Marshmallow might be more for you if you really like to customise. As for being behind on security patches, I concur with Davey126 that as long as you're sensible about where you download and install APKs from, you should be in good stead. Security patches are nice, due diligence and being aware about what you're putting on your device is crucial to staying safe.
In other words, enjoy the flexibility of your rooted device and when the fastboot Nougat ROM comes out, then you can think about whether you wish to update or wait for any bugs to be ironed out. Alternatively, I'm sure someone will release a TWRP flashable build of the stock 7.1.1 (which shouldn't touch your bootloader/GPT anyway, so should be safe to use). Either way, waiting will mean you don't risk your bootloader or GPT and still have a device you can enjoy