Related
Hello,
I am totally new to android hacking, so thanks in advance for replying with as much details as possible.
I have an HTC One and wanted to root and install ARHD 70.0.
I rooted unlocked the bootloader, then rooted the phone. All went well.
Default install of ARHD 70.0 (with all checkboxes by default: sense6 tool box, google packages). I also checked the first 2 checkboxes for performances: ext4 setting and nosql setting. Before installing i did a wipe as recommended.
Then i installed ARHD 70.0. Installation went well too.
Upon reboot im in Sense 6 and i'm loving it.
As soon as I reboot, after about 1min, my battery level jumps to a fixed value (77% on that case) and goes down really slowly. Im 100% sure there is not tat much left because the indicator was at 50% just before i rebooted and also right after the phone restarted. After about 1min, it gets to 77% and sticks there.
I reinstalled multiple times (always with wiping first). I tried without Xposed framework and Sense 6 tool box... The issue reappeared after the first restart (from Sense, not from installation of ARHD).
I am pretty sure it's not hardware related because when i was on my unmodified HTC Once with Sense 5.5, it never happened.
I have not (afaik) modified/installed a kernel.
Do you guys know what could be the problem ?
Is there a way to see whats happening once i reboot into a log file so i can see which process affects this ? It always happens after reboot when i'm about 1min in.
Thanks for your help. Tried searching the forums, but i couldnt find anything helpful
EDIT1: AFAIK i must be S-ON since i havent changed anything regarding that
EDIT2: I also tried to update Xposed framework (because it was reporting that it was runnign an old version) through recovery (because im S-On) and then i updated Sense 6 toolbox (cause it needed an update) and it didnt fix my issue.
I
Coming from the simplicity of a Nexus 7 and a Moto G, I am a little confused by how the Z3TC handles recovery and flashing. After a two hour session last night I finally got CM12 20150217 running but not matter what I try, I can't seem to get Xposed 2.7 alpha1 to run (it works just fine on Cm12 on my Nexus so it ought to work, somehow).
In the god awful CM12 recovery, flashing xposed fails with an error message I remain unable to read. Flashing it with the twrp that someone integrated into the stock kernel succeeds according to the twrp status but then the xposed installer still does not see the app_process (it sees the bridge however, which I find weird and have not seen like this before).
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
In principle, I am open to going to AOSP if someone can point me to a scorpion_windy image (all I can find on FXP is scorpion for AOSP, which is another weirdness that confuses me) and feels I have better chances of getting it to work there....
Hi,
what you need to do is to install twrp recovery to the FOTA partition.
(This will also allow you update cm12 through cyanDelta, which is not possibe with the crappy cm12 recovery)
It's all decribed here: http://forum.xda-developers.com/z3-tablet-compact/development/daily-cm12-unofficial-builds-t2983400
The twrp img is actually a modified Z2 twrp, but it seems to work.
(i am writing "it seems" because i have a SGP621 myself, for this one I can say "it works").
Please note:
- It is no problem if app_process displays only ---, that is a known bug of the alpha
- not all xposed modules are working. XGELS is working for sure, if you want to test.
- You need to invoke soft reboot from within the xposed app after each flashing of the xposed zip (which you need to flash after each ROM update). Otherwise xposed will not work currently.
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Edit: Or not, a 10 s power & vol + action followed by power on lets me boot both TWRP and CM12, very strange.
Now lets see if I can get Xprivacy to do its job (for starters, the boot.img contents are different than on the GOogle/Moto devices so we shall see)
nupi said:
That seems to have resulted in a (soft?) bricked SGP611. At least now it sits at the Sony logo showing a solid yellow LED and doesn't even turn off anymore (meaning I can't even try to boot it to bootloader to flash a known working kernel anymore)
Click to expand...
Click to collapse
wow, I'm really sorry to hear that ... I have no idea what might have gone wrong.
You can turn off the device by holding the power button for 7-10 seconds.
If ou want to remove twrp from the FOTA partition, simply reinstall (ONLY) FOTA from the current ftf (SGP621_23.0.1.A.0.167_CE.ftf) through flashtools.
Never mind, I got it back and TWRP flashed xposed cleanly but I can't get it to work - soft reboot does not help, either
However, the kernel seems to have the wrong WiFi drivers for the SGP611 (at the very least, I don't get WiFi anymore). Back to flashing the CM12 kernel for now... I am thinking I should go back to KitKat until someone with a little more clue figures this one out
nupi said:
So did anyone already manage to cleanly install xposed on a Z3TC? Also, is there any way to get TWRP 2.8.X with CM instead of their awful CM recovery?
Click to expand...
Click to collapse
Cyanogen has made the worst mistake every with CM12 and CM Recovery Testing at the same Time.
As long as Cyanogen does not develop a real Recoveryfunction to CM Recovery this crap will block much more then Xposed.
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
neocortex08 said:
I asked a few questions in the official thread and did not resolve my issue. From replies to others in the thread I should probably try asking in the 'Discussion' thread(?) but I thought I would ask other HAM2 users here first.
Short version:
On my Ascend Mate 2 and I cannot boot after using romracer's version of xposed for sdk22 (http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979). I flash the latest version, wipe the cache, and press "reboot". It shows the boot logo, then the boot animation, then stays on the slightly animated Huawei logo indefinitely. I left it for an hour once just to see if it would change/finish.
Longer version:
(Started by making everything factory reset/stock.)
1. Got the B321 update
2. Got TWRP 2.8.7
3. Rooted with the latest SuperSU
4. Installed Viper4Android FX
5. Restored all my apps and settings with the stock backup tool
6. Flashed xposed-v71-sdk22-arm-by-romracer-20150816.zip
7. Would no longer boot. (First logo screen stays on for much longer than normal, then the Huawei animation plays, but without sound, and finally the animated Huawei logo just sits there.)
Nothing else was changed or added or modded before trying to flask xposed.
• The APK is not yet installed (not sure if that matters)
• I’ve tried the current version, as well as 70, 69, 68, and 67 for good measure
• I attempted to flash the 64 and 86 versions just in case
• I even tried a version for sdk22 posted by C3C076. This version did not even get to the animation screen and could not be removed with romracer's uninstaller (just thought I would try)
• I’ve tried waiting 10, 20 and even 60+ minutes for the boot to complete… it just sits there
• I’ve checked and rechecked and redownloaded the zip from the official (“unofficial”) first page
• I wipe the dalvik cache each and every time I flash
• After a few minutes, if connected to my computer, the initial Huawei folder window will appear (the one with Docs, drivers, and “autorun”), and my phone will show up in adb devices list in command prompt. I can even use adb commands at this point. I really believe this means something.
• To get back into my phone, each time, I have to restore the system backup or flash the uninstaller zip.
I really want a number of xposed modules! My phone works 'fine' without them, but who roots their phone for merely 'fine'. Any suggestions are appreciated.
Click to expand...
Click to collapse
He is correct. You have to be on CM. EMUI will NOT allow closed to work. Flash the uninstaller zip.
icyboyice said:
Haven't heard of xposed working on stock lollipop EMUI . It does work on CM tho .
Click to expand...
Click to collapse
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
neocortex08 said:
Thanks. I was worried that might be the case, a few days into my efforts, when I saw the "Xposed for CyanogenMod" guide posted a few days ago.
If that is the case, I suppose I have two additional questions:
1. Will installing CM mean another wipe and restore? (I'm certain I know the answer, which is of course "yes", but I thought I would ask all the same.)
I only ask because I hate having to re-do all my settings (3 email accounts in the google app, general device settings, etc), which neither the stock restore app or non-pro Titanium backup ever seems to put back.
Read through the "preview-cyanogenmod-mate-2 thread". Guess I'd have to bite the bullet.
2. Is CM worth it on its own? (And by worth it, I mean worth it for the HAM2... I can see CM's features with a quick search.)
I know I'll like being able to finally get Xposed, but I wonder if this will be an issue for getting updates like the recent B322. Or perhaps CM fixes that concern? I don't know much about it. My experience is limited to learning to root my phone for slightly more functionality on a few root apps.
Read through the "preview-cyanogenmod-mate-2 thread". Still not sure after reading about random restarts and battery issues (possibly from wake locks and/or google apps?).
Guess I'll just have to decide whether to try it after reading more comments in other threads about it.
Thanks for the help both of you!
Click to expand...
Click to collapse
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Moody66 said:
For someone like you that doesn't have a lot of experience with custom Roms I would say wait till things are better.
Click to expand...
Click to collapse
Thanks! As excited as I am to have Xposed, I really like my EMUI (and don't want to pay for the play store one you suggested to others), I like B321s stability, and I like not changing settings often. So for now I'll wait and deal with not having trivialities like AdAway or playing Youtube in the background.
@neocortex08
You only need root on your phone to be able to install adaway. You don't need xposed.
For background playback of YouTube videos you may want to check this out
http://forum.xda-developers.com/showthread.php?t=2213945
They have a install method for those who are rooted and have xposed and those who don't .
Here's a Stockish ROM for your N915P. This ROM has Knox, Sprint ItsOn, and secure storage removed. Nothing else was done to this ROM. I'm new to the Note Edge so I may upload patches to remove any other traces of Knox or ItsOn or optimizations I happen to find while making my own ROM.
Prereq: OG1 Baseband. Download it below.
Modified stock kernel (BeastMode Stock): Kernel modified to allow root by disabling "Root Restriction in defconfig"
Download
MD5: 75bd507e3b4296a128f1c0c48fd2359c
Version 1.1: Enabled many TCP Congestion options via defconfig. Added init.d ability via ramdisk.
Odex:
Download
MD5: 59d544ef6a4bc12d969f4efd9577d36d
DeOdex DEBLOATED:
Download
MD5: 00b5246b9c2074e7ff04f6af2bad1ec2
OG1 Baseband:
Download
MD5: 3bc88209d60117fb573e0f5a2e50f4e9
Patches and fixes:
None yet.
[size=+3]DeOdex note:[/size]
The first boot time for this DeOdex ROM is very long. Approximately 5-8 minutes. Your phone will get hot as the splash screen remains on the yellow Sprint boot animation. I recommend keeping your phone in a cool environment while this is happening. The heat, if not properly checked, can make boot times even longer as the system throttles speed in order to deal with the heat. This doesn't happen on the Odex version.
[size=+3]Install instructions:[/size]
-Are you currently on the OC8 bootloader and would like to stay on it?
--Simply flash the baseband with Odin, and the ROM.
-Are you on the update from OTA or flashed the OG1 TAR?
--Flash kernel only.
-Are you one of the unlucky ones to take the OTA and hose your system trying to root and are now on another ROM?
--Flash ROM only.
-Are you on any build after OC8 but not the current OG1?
--Flash the baseband and ROM. Bootloader is optional and not available in this thread as of yet.
Wiping is only necessary if you are coming from a different base, such as AOSP/CM. If you are coming from a touchwiz ROM, wiping isn't needed, but won't hurt.
Changelog:
9/5/15: Initial Release.
Kernel source code: Download
Thanks, will flash tomorrow.
Thank you so much freeza!! Patiently waiting for the deodexed version and for the baseband.
Added modified stock kernel v1.1 and baseband.
Freeza if I'm on 5.0.1 still just flashing the baseband may give me better service ? Technically...
Downloading now still waiting on the deodex will play with the stock to see how it is thanks
Ok, flashed rom, kernel, and modem. Took a while to boot but all is running well at the moment. Thanks for supporting our device!!
DeOdex uploading....
What What!!! By far the best developer on a Samsung!! Thank you so much for your hard work brother!! Real Talk, i still have your rom on my Note 3! It runs flawlessly!! XD
Get your DeOdex on, guys! ;D
Thanks so much for this!!! I love the separate edge screen and have no reason to "upgrade" to the Note 5
Thank you freeza NICE WORK WITH THE KERNEL
When I saw you had been requested to come help this phone achieve root I knew great things were going to come to those who waited. I've had other devices where you were there to help gain root and again you came through. I purposely didn't take the OG1 update because I knew in time this device wasn't going to be ignored. IMO it is the best NOTE device out there and it will be mine until they make a NOTE EDGE 2 (With SD card and removable battery). Thank you for the quick response and the hard work you do to make this happen.
Cant get either one of them to boot. Both the odex and the deodex wont boot, they both flash fine and then after the phone reboots it stays on the yellow sprint screen Maybe for up to a minute then reboots and it cycles that way. Never boots. I've tried not wiping/Factory restarting as well as wiping/Factory resetting. Have also tried formatting through TWRP to no avail. Have also tried flashing the kernel and wiping caches after flashing but Nothing is working. Have also flashed the baseband.
Im currently on OF6 if that should matter.
Edit: md5 Sums have also match up. Have downloaded both from my phone and a pc to no avail.
Edit 2: tried both TWRP 2.8.6.0 and 2.8.7.0. Also tried clockworkmod recovery and that didn't work either.
I had success but it took some time. I downloaded the deodexed debloated rom, the kernel, and the baseband. I had a method to how I wanted to do this and here is how i got there.
I was running OC8 rom rooted.
1. I odened the baseband tar file and rebooted. But unfortunately it bootlooped on the initial splash screen (note edge) so
2. I ran TWRP recovery and installed the kernel file. Rebooted phone and it ran fine. I looked at the settings about phone and saw that the baseband and the rom all said OG1 but i had not installed the rom yet. So i figure it was a trick to get the baseband to install. So
3. I went back into recovery. Wiped dalvik cache and regular cache and installed the new rom. It installed fine and i waited the length of time for the initial boot up. But this time as it was "Android is starting" it rebooted and got stuck on the sprint splash screen and kept randomally vibrating. Having the ability to remove the battery
4. Rebooted back into recovery, wiped everything including internal storage, and reinstalled the deodexed rom. It installed fine and went to the initial startup screen where it tries to initialize and it rebooted one time, back to the initialize screen but continued without a hitch.
I currently am running OG1 5.1.1. With root.
At times during setting up the phone it would randomally vibrate for no reason...short bursts...but it hasn't yet again rebooted, restarted, or crashed. It is faster from what i see. Probably because there are almost no google apps installed. I've had to install chrome, youtube, and maps. But all seems fine. My signal and speeds are the same so the baseband didn't do much to change that. But so far so good.
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
I did try to install over my odexed OC8 with this new rom but because there is so much different about the files that are installed IMO formatting the phone was the only way to get this to work.
---------- Post added at 12:16 PM ---------- Previous post was at 11:30 AM ----------
One final thing just in case it isn't known: when you wipe everything in TWRP, excluding external storage, you have to restart the recovery before trying to install a rom. It will say you have no OS installed, but you are restarting the recovery not booting a rom, so that's fine, but you do lose root status when wiping. So the next screen gives you the ability to gain root again, but you have to restart TWRP to do that. In the past i tried to figure out why installing after wiping didn't work, and 99% of the time it was because of that. I also don't like installing new roms over older roms (even if they are the same base (touchwiz to touchwiz)) because i feel I would spend more time troubleshooting why something isn't working instead of just starting over. I find less hassle doing it this way.
I odin baseband .tar file, than reboot it to recovery, and flash kernal and odex room at the same time, saw some red messages when kernel was flashing, than odex rom was next but it was successful when it was done. (I did not know if kernel falsh ok so i reflash kernel again) reboot to system and after the android system updated all its ok. No problems so far.
Oh and i inclided the supersu at the same time i flash kernel, odex rom and supersu.
1. Odin baseband tar file.
2. Flash kernel, odex rom and supersu.
3. Re-flash kernel.
4. Reboot to system and profit.
(Maybe i did un necessary steps, but its working. )
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Johnny Halo III said:
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Click to expand...
Click to collapse
Just starting to have random freezing. And not able to select my apps froms the edge screen, i can only scroll through it. Will remove all the app shorcuts and re-add tham again.
**update 1.
I removed all shorcuts from the edge screen and added them back, all work but some i have to select them a few times before they open.
Maybe i have to reflash, reset, clean and wipe.
**update 2.
Clean install of odex rom, and kernal 1.1.
No more lagg but the edge screen does not work properly. Not able to select and open some of the favorite app shorcuts.
**update 3.
Factory reset, cleaned and wype, odin sprint lollipop update (uf something), downloaded OG1 update. Installed all apps from scratch. And the edge screen does not work. I can scroll, side to side, up and down, but when i select an app it does not open it.
** update (last one)
Foud the code to test the phone hardware.
*#0*# on dial screen. Tested all and it came out good. But i notice that some how the edge screen its not as whide as it used to be ( like its more to the right of the phone) so where i use to touch to select an app its now more to the right emd of the edge, thats why i was able to scroll but not select the app.
Its all good now. Now second round of flashing.
Will give it another try at the room.
Thanks Freeza and sorry about the problems i had and hopefully did not cause anyone from not trying this great work pr yours.
I left all the problems i had so tje next person trying this room does not get discureged from trying. But allways fallow direction.
:thumbup:
** last update
After setting and resetting, flashing and un-flashing, rooting and un-rooting. I can finally wrote that all is good. Running latest lollipop 5.1.1 and freeza's new 1.1 kernel, I can reprt that all is smooth as butter.
Thanks for the hard work.
Thank you so much for your hard work Freeza! So glad I'm finally running 5.1.1 on this beast :]
The ROM is working pretty well, but I have noticed that every now and then, the phone will be rather laggy. Turning the screen off and on again seems to fix the issue, making me think that the processor is being throttled while the screen is off (good) but isn't being sped back up when the screen is turned on..sometimes.
It's not a huge deal, but I was wondering if anyone was experiencing the same thing.
No issues here.
Starting on OG1 had to flash bootloader, kernel, deodex rom and supersu to make it stick. Two days now and battery, signal and speed seem improved.
Thanks freeza!
Hi,
last week I bought myself a Huawei P20 Lite as this one seems to be good comprise between size, speed and price and all together I find this device quite nice.
However I'm not a big fan of this ROMs, it's bloated and you have to confirm on each and everyhting, so I tried to reduce this dramatically and I began a long journey....
Unlock the bootloader
When I bought the device I wasn't aware about the issues that I may face (Downgrad, additional 4 Euro to spend) but OK, I thought it would be worth....
Installing Recovery
..but I couldn't be more wrong. It seems that there's no working TWRP for this device out there. I tried a lot, both on 8.0 and 9.1 but each time I tried to
wipe cache/dalvik the whole system got stucked and wasn't able to show the boot animation. So, assuming that there's really no working recovery out there, I continued to
directly flash different ROMs and try out my luck.
Rooting
This wasn't as hard as I though first, at least, as long as the ROM I've used had an advanced Reboot-Menu with the possibilty to boot to recovery, otherwise you end up somewhere in the desert and
may not be able to restart with boot.
The problem is, that this device required to patch the RECOVERY_RAMDISK partition, so in order to have Magisk booted, you required to use the Recovery. No big deal: just Power up
using VolUp and Power until the Huawei logo appears... normally.. It didnt work in more than 50% of the times...
Gapps (or Magisk)
OK, as I already indicated, I tried lots of them, but to be honest, none of them really convinced me (all was done on EMUI9.1 "AB" and not EMUI8 "A only")
GSI Phh Treble: nice, but this is one of thinks I did not checked in depth, as almost all (?) are based on this one...
OmniRom from OpenKirin: works perfectly out of the box, SafeteNet is working, Magisk can be installed, but no advanced boot menu and I find it a little bit overloaded...
MicroG ufOffical: I would go with it, everyhting worked, it's slim BUT I couldn't get my Banking-App working, not even after appliying multiple MagiskHide Prop-Settings...
Descendant: This one was by far my favorite... Really slim, advanced reboot-menu, but I couldn't flash Gapps. OK, so I tried MicroG: this can be installed using Magisk. After some trouble (e.g. you have to install DroidGuardHelper so that the OS recognizes an "Update") I got MicroG working, but I coulnd't get it with my Banking-App. In this ROM I couldn't even apply any MagiskProp Hide-Settings. Only Post-FS worked. OK, as I'Ve failed using this approach, I thought: maybe I can use Gapps with this image.... but as I stated at the beginning: I do not have any working Recovery.
So my questions:
Is there any working Recovery out there? TWRP 3.3.x supports to be flashed in RECOVERY_RAMDISK (and there's also offical support for P20 Pro) As of now I wouldn't even care about decrypted data, but at least be able to wipe and do a factory reset....
Or: Is it possible to install Gapps from a running (rooted) system?
Or: can I patch system.img with Gapps before flashing it to the phone?
But perfectly: did anyone get Descendant running with MagiskHideProp? Maybe even got MicroG running on it?
I'm currently out of ideas, did someone else had such a trouble with that device?
Best regards,
Peter
Well, yes. Kinda the same as you but I didn't try that many roms. I tried a fair bunch of twrp versions though. And I managed to use twrp to flash roms and if I remember well even do a dalvik/cache wipe with one of them - but I might be imagining that one. It is worth noting that you can actually use some twrp versions for other huawei devices on the p20 lite. Try at your own risk. There is a lot more development going on for the p8 lite (2017) for example. I tried the lineageos version that was posted herefor that device and it worked quite well.