This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Twitter - http://twitter.com/mtthwlx
Downloads:
https://drive.google.com/drive/folders/1zwaS15e4zXiSWuEU_ZOjTLBqtdzP86dL?usp=sharing
Source:
Github – https://github.com/DespairFactor/
Credits:
Essential
Google
Star Wars
Finally...
Good to see the development..
Special thanks to the members who donated f&f codes.
And @DespairFactor for quick release..
Hype.
Oof
indian84 said:
Finally...
Good to see the development..
Special thanks to the members who donated f&f codes.
And @DespairFactor for quick release..
Click to expand...
Click to collapse
ghostENVY said:
Hype.
Click to expand...
Click to collapse
LeTurntRice said:
Oof
Click to expand...
Click to collapse
There are no features yet, I am working on EAS tweaks for stock at the moment and will likely also do an HMP kernel
n00b question... What does this kernel have? Also would you be able to dive into the camera apk to help solve compression issue and color saturation since you have the phone now?
xterminater07 said:
n00b question... What does this kernel have? Also would you be able to dive into the camera apk to help solve compression issue and color saturation since you have the phone now?
Click to expand...
Click to collapse
I am about to push my changes to github, I am unaware of what the issue is or if I can help. but I can try when I have free time
Oh nice, we get to be named after Rei? Curious as to whether you intend for this to work on AOSP, LOS or stock ROMs?
ChronoReverse said:
Oh nice, we get to be named after Rei? Curious as to whether you intend for this to work on AOSP, LOS or stock ROMs?
Click to expand...
Click to collapse
Right now this is for stock oreo beta 2, will work on other stuff as I have time, but I am hoping they release stock oreo soon
OH! Does it include patches to pass Safetynet despite the unlocked bootloader as well? Would like to avoid Magisk if possible.
ChronoReverse said:
OH! Does it include patches to pass Safetynet despite the unlocked bootloader as well? Would like to avoid Magisk if possible.
Click to expand...
Click to collapse
I am adding that right now, I am testing some boot issues with one of my commits, R1 will be up for all when it is resolved
Hi,
What is the correct way to flash, boot.img then magisk. I cant remember. Blame the booze.
Thanks
R1 good to go? As its uploaded i see
Edit: Guess so as flash and passed safety net
DaveHTC200 said:
R1 good to go? As its uploaded i see
Edit: Guess so as flash and passed safety net
Click to expand...
Click to collapse
NZnewbie said:
Hi,
What is the correct way to flash, boot.img then magisk. I cant remember. Blame the booze.
Thanks
Click to expand...
Click to collapse
R2 is up now, I am working on getting AnyKernel to work and keep recovery on device if possible when flashing.
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Tried Rey2.zip nd booted back to twrp and the touch didnt work. Using the latest twrp as well
DespairFactor said:
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Click to expand...
Click to collapse
DespairFactor said:
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Click to expand...
Click to collapse
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
NZnewbie said:
Tried Rey2.zip nd booted back to twrp and the touch didnt work. Using the latest twrp as well
Click to expand...
Click to collapse
Looking into it, I think flashing magisk makes touch work, will see if I can fix it within the kernel side.
gk1984 said:
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
Click to expand...
Click to collapse
Yes it is, I have it on my device right now
Ive heard theres a fix coming for that as well(hope so)
gk1984 said:
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
Click to expand...
Click to collapse
DespairFactor said:
I am about to push my changes to github, I am unaware of what the issue is or if I can help. but I can try when I have free time
Click to expand...
Click to collapse
The problem with the stock camera app was that it compresses images too much, they have lower the compression ratio but it is still not good enough. You can try it yourself to see what I mean. In broad day light outdoor, the images appears to be great but if you zoomed in, you will see it it just doesn't look right. The color is washed out as well, and you don't see any details. Looks like everything is smoothed out. File size is about 6 to 7mb or so. The low light shots are worst, it's about 3mb and there's more fuzzy stuff and lack of details/sharpness.
If you can dive deep into the apk to see what they set the compression to, and change that to possibly 0, and see what else needs to be changed. I spoke to Arnova8g2, who helped ported the gcam hdr+ to oneplus3/3t and he helped fixed the compression a bit on the older apk but I can't overwrite it no matter what. Let me know if you need any more info.
Related
COMPLETELY BASED OFF OF @Dmitry KERNEL WITH PATCHED SUPOLICY
DISCLAIMER: Blah blah blah I didn't break your phone don"t blame me.
Background
Well It actually wasn't too hard to achieve even though I know nothing of the boot.img. Just followed @Chainfire guide on installing SuperSu for Android 6.0 Marshmallow. Booted my nexus into a lollipop rom and flashed SuperSu beta 2.51, did some adb commands to patch the selinux policy and recompiled and flashed boot.img
SELINUX IS ENFORCING
Steps to Root your new Nexus 4 running the latest Marshmallow
1) FLASH YOUR PREFFERED 6.0 ROM.
2) FLASH MODIFIED BOOT
BOOT.IMG V2
MEGA MIRROR
3) FINALLY FLASH SUPERSU BETA 2.51
4) PROFIT
CREDITS:
@Chainfire for his amazing SU work and great guide on noob patching selinux
@Dmitry Grinberg for his awesome 6.0 rom I'm running and for providing a boot.img with dmverity already disabled
Leave a thanks if you felt like I helped
Video Proof https://goo.gl/photos/ZWNNNRiMQzRwuZXP8
CHANGE LOG
V1: First boot image throw together for root.
V2: Data Fix merged from @Dmitry
Selinux is permissive in the modded boot.img right?
sd3993 said:
Selinux is permissive in the modded boot.img right?
Click to expand...
Click to collapse
How can I easily check this? Looking for an app now.
Looks like its enforcing according to SElinuxModeChanger apk. Asks if I want to put it into permissive at least.
It works.. Thank you..
ktetreault14 said:
Looks like its enforcing according to SElinuxModeChanger apk. Asks if I want to put it into permissive at least.
Click to expand...
Click to collapse
It's enforcing then. root on L at first needed selinux to be in permissive. That's why i needed to ask. Thanks for boot.img!!
ktetreault14 said:
How can I easily check this? Looking for an app now.
Click to expand...
Click to collapse
What Gapps and how you are using them? Instructions?
Awesome thanks guy glad i could help sorry about the permissive thing. Ill look into it
Thanks very much for your work
I've uploaded your modified boot image to my AFH host, hope you don't mind, if you do let me know and I'll take it off, just thought it might save your Google Drive getting hammered
https://www.androidfilehost.com/?fid=24052804347833281
ktetreault14 said:
Awesome thanks guy glad i could help sorry about the permissive thing. Ill look into it
Click to expand...
Click to collapse
There is nothing to look into about that. Enforcing is what it should be.
---------- Post added at 02:11 PM ---------- Previous post was at 02:08 PM ----------
sd3993 said:
There is nothing to look into about that. Enforcing is what it should be.
Click to expand...
Click to collapse
Also a google engineer on aosp on m live thread is making a boot.img that's going to enable data. He'll be adding selinux policies to it after a bit of experinentation. When that's working do integrate those changes into your boot.img so we can have root and data together(in enforcing mode) which is the way it's all supposed to work
EDIT:- here you go :3
http://forum.xda-developers.com/showpost.php?p=63211817&postcount=278
OK Dmitry has fixed the data issue and uploaded a new boot image, hopefully @ktetreault14 can fix that (after a well earned sleep session ) so we can root also, thanks again.
http://forum.xda-developers.com/showpost.php?p=63211817&postcount=278
I will get around to looking at it in roughly 12 hours. About to be going to work
EDIT: going to attempt real quick
Done!!! Redownload from Op. Going to post in other threads. Tell me if all works @djsubterrain
Don't feel pressured to do it, people can wait
djsubterrain said:
Don't feel pressured to do it, people can wait
Click to expand...
Click to collapse
Thanks man I can't test as my S6 has a tiny sim lol. But it booted
Very nice of you, have a good time at work
How do I get it work guys as I tried through wugs toolkit no success could anyone help me.
Sent from my AOSP on Mako using Tapatalk
insigma28 said:
How do I get to it guys tried through wugs toolkit no success could anyone help me.
Sent from my AOSP on Mako using Tapatalk
Click to expand...
Click to collapse
Get to what?
It's a boot.img replacement so you need to use fastboot to flash it, just reboot your phone to the bootloader and use fastboot.exe to flash it using "fastboot flash boot <filename>" (Obviously replacing <filename> with whichever file you want to flash.
djsubterrain said:
Get to what?
It's a boot.img replacement so you need to use fastboot to flash it, just reboot your phone to the bootloader and use fastboot.exe to flash it using "fastboot flash boot <filename>" (Obviously replacing <filename> with whichever file you want to flash.
Click to expand...
Click to collapse
Did not mean to put get to lmao thank you for the reply dude appreciate it.
Tapped from my N4
Mirror please
ktetreault14 said:
I will get around to looking at it in roughly 12 hours. About to be going to work
EDIT: going to attempt real quick
Done!!! Redownload from Op. Going to post in other threads. Tell me if all works @djsubterrain
Click to expand...
Click to collapse
I'm sorry if I missed to notice. GDrive throws me 404 error when i try to download the latest boot.img. Could someone be kind enough to provide a mirror?
Thanks in advance.
Hello everyone,
After seeing the news that Treble images were properly working on the S9, I decided to give it a go and see for myself how good/bad was it working.
The from my findings, the only thing that is NOT working is the auto-brightness.
Here are the installation steps :
Make sure you got TWRP installed properly, with DM-Verity and Encryption disabled.
Download this : https://www.androidfilehost.com/?fid=817906626617958348
Place it in the root of your device, then navigate to TWRP, click install, click install Image, select the transfered system.img, and select system image.
Make sure to full wipe after that, and reboot, and you are good to go.
This is awesome. As soon as I'm able to get my hands on an Exynos variant S9, I'm buying one for Treble support alone.
Auto-brightness doesn't work because the framework doesn't define any brightness levels for each lux level. You can make an overlay to fix that or modify the framework at source.
MishaalRahman said:
Auto-brightness doesn't work because the framework doesn't define any brightness levels for each lux level. You can make an overlay to fix that or modify the framework at source.
Click to expand...
Click to collapse
I'll pass onto phh, see if he can include a fix in his builds.
Works Samsung câmera app?
how about camera's aperture (switch between 1.5 and 2.4) , slow motion too ?
Paradoxxx said:
Hello everyone,
After seeing the news that Treble images were properly working on the S9, I decided to give it a go and see for myself how good/bad was it working.
The from my findings, the only thing that is NOT working is the auto-brightness.
Here are the installation steps :
Make sure you got TWRP installed properly, with DM-Verity and Encryption disabled.
Download this : https://www.androidfilehost.com/?fid=817906626617958348
Place it in the root of your device, then navigate to TWRP, click install, click install Image, select the transfered system.img, and select system image.
Make sure to full wipe after that, and reboot, and you are good to go.
Click to expand...
Click to collapse
Any idea how to build a treble image?
I know how to build for a specific device but treble... bohh. Maybe you can help me.
Astrubale said:
Any idea how to build a treble image?
I know how to build for a specific device but treble... bohh. Maybe you can help me.
Click to expand...
Click to collapse
phh is sharing his build script : https://github.com/phhusson/treble_experimentations/blob/master/build.sh
That should get you started
Paradoxxx said:
Hello everyone,
After seeing the news that Treble images were properly working on the S9, I decided to give it a go and see for myself how good/bad was it working.
The from my findings, the only thing that is NOT working is the auto-brightness.
Here are the installation steps :
Make sure you got TWRP installed properly, with DM-Verity and Encryption disabled.
Download this : https://www.androidfilehost.com/?fid=817906626617958348
Place it in the root of your device, then navigate to TWRP, click install, click install Image, select the transfered system.img, and select system image.
Make sure to full wipe after that, and reboot, and you are good to go.
Click to expand...
Click to collapse
owsome guide thanks
---------- Post added at 11:23 AM ---------- Previous post was at 11:22 AM ----------
hoangtu2410 said:
how about camera's aperture (switch between 1.5 and 2.4) , slow motion too ?
Click to expand...
Click to collapse
on aosp u loose some tw features
matheus_sc said:
Works Samsung câmera app?
Click to expand...
Click to collapse
Nope
hoangtu2410 said:
how about camera's aperture (switch between 1.5 and 2.4) , slow motion too ?
Click to expand...
Click to collapse
Stays at 1.5, and not sure about slow motion.
Paradoxxx said:
Nope
Stays at 1.5, and not sure about slow motion.
Click to expand...
Click to collapse
damn... maybe it is possible to collect the camera.apk and all needed libs to get the samsung app to work on aosp rom ??
inteks said:
damn... maybe it is possible to collect the camera.apk and all needed libs to get the samsung app to work on aosp rom ??
Click to expand...
Click to collapse
It's also framework related so very much unlikely to happen.
have you guys also tested if the telephoto lens activates when you zoom in?
iamnotkurtcobain said:
It's also framework related so very much unlikely to happen.
Click to expand...
Click to collapse
Porting the frameworks has recently happened for Huawei and Sony. Unless Samsung are deliberately obfuscating things, it should be possible to do the same for the Exynos versions of the S9 and S9+.
Can someone post screenshots
Im so excited .. this is one of the biggest reasons why I will switch to s9+
Hi sorry for a noob question I am new here, after flashing the image will I get stock android ? Like lineage os ?
Thanks
pavneet10174 said:
Hi sorry for a noob question I am new here, after flashing the image will I get stock android ? Like lineage os ?
Thanks
Click to expand...
Click to collapse
Yes
Griffiths_Anna said:
Yes
Click to expand...
Click to collapse
Hey thanks a lot for helping,
I have one more question, when I flashed aosp ROM it worked fine but with the brightness glitch, however when I flashed lineage os it just bootlooped so any suggestions ?
Thanks
26th builds of 8.1 are okay for brightness but fingerprint is broken for some and causes touch to stop but reboot, unlock then a few lock/unlock cycles it's good temp fix til next reboot
Hello guys and girls,
As some of you already know Android 8.1 suffers from a severe Multi-Touch Issue. This issues makes the smartphone randomly jumping between the two touching points on the screen when touching with two or more fingers.
The issue is known to google since the preview of 8.1. It isn´t only affecting pixel but most probably all devices running 8.1. The issue is also present on P.
An issue got created here: https://issuetracker.google.com/issues/70344455
There is a fix since mid march in review on google gerrit. But that didn´t make it into the april release, obviously.
To visualize the issue refer to the following videos:
https://youtu.be/wgYN5GwIgIc
https://youtu.be/2Vv584tvVyg
https://www.youtube.com/watch?v=4dnIk_5qdK8&feature=youtu.be
This is especially bad for gamers. With the recent release of PUBG this issues seems dramatic to some, less to others.
I´m no gamer but I noticed the issue on the google foto app.
This issue has nothing to do with the corners badly reacting to touches, or touch sensitivity etc.
So but now to the fix. It seems the issues is only related to resampling but not to touching specific points of the screen ( not related to crossing x and y axis).
That also explains why the issue wasn´t happening when using the touch tracking tool in dev settings but on various multi touch test apps.
The fix is on google gerrit currently under review here:
https://android-review.googlesource.com/c/platform/frameworks/native/+/640605
https://android-review.googlesource.com/c/platform/frameworks/native/+/640606
Last week I compiled myself a DU build with the changes included and I couldn´t trigger the issue at all. I found no other side effects caused by the two patches.
For now I decided to provide a Magisk Module which replaces the changed libs that fixes the issue.
I compiled the libs while doing my april build of DU. The magisk module can be found on the link a little bit down.
The download is here:
https://www.androidfilehost.com/?fid=890129502657595755
A few disclaimers here.
1. That fix should in theory work for most 8.1 devices, including the likes of pixel 1st gen, pixel 2nd gen, one plus, xiaomi which suffer from this severe issue.
1a. It works only for AOSP/LOS based roms on the essential phone. It seems like stock isn´t close enough to aosp.
2. I didn´t fix this, I just compiled the libs with the fix found on google gerrit.
3. Rom devs you are very welcome to include this fix. I found no ill consequences as of yet but I can understand google taking it slow and reviewing it longer. Maybe they will find a better fix, but as of now this is the best thing we have.
Donations:
Donations are not mandatory but very welcome.
If you like my work: http://paypal.me/freak07
this was confirmed working on the xda portal post by @crixley for the essential phone running a custom aosp/los based rom.
Big thanks to you!
Freak07 said:
this was confirmed working on the xda portal post by @crixley for the essential phone.
Big thanks to you!
Click to expand...
Click to collapse
Huge difference, including touch latency! I'm super pumped about it.
Work perfectly!!! Thank you so much!
Guys, does it work? For me I ended up in bootloop
xorwin said:
Guys, does it work? For me I ended up in bootloop
Click to expand...
Click to collapse
Omg you're right it actually causes my phone to not boot. I wiped my entire phone thinking it was some kind of module conflict and now it still wont boot.
xorwin said:
Guys, does it work? For me I ended up in bootloop
Click to expand...
Click to collapse
wind711 said:
Omg you're right it actually causes my phone to not boot. I wiped my entire phone thinking it was some kind of module conflict and now it still wont boot.
Click to expand...
Click to collapse
I bootlooped too. Flashing the stock boot image fixed it and my phone booted right to Android.
Jank4AU said:
I bootlooped too. Flashing the stock boot image fixed it and my phone booted right to Android.
Click to expand...
Click to collapse
Once I flashed the stock boot image I lost magisk so that wouldn't work.
wind711 said:
Once I flashed the stock boot image I lost magisk so that wouldn't work.
Click to expand...
Click to collapse
I wasn't worried about losing Magisk. I was trying to get my phone to boot.
@crixley what did you do to get it to work? For three of us it results in a bootloop.
Jank4AU said:
I wasn't worried about losing Magisk. I was trying to get my phone to boot.
@crixley what did you do to get it to work? For three of us it results in a bootloop.
Click to expand...
Click to collapse
I'm not on stock rom, that might be it. Should have been clear on that
crixley said:
I'm not on stock rom, that might be it. Should have been clear on that
Click to expand...
Click to collapse
Yeah, I'm on stock so you're probably right, that might be it.
Thank you soo much @Freak07 !
I installed with with magisk app as a module. Booted perfect
tomzefi said:
I installed with with magisk app as a module. Booted perfect
Click to expand...
Click to collapse
Are you on stock or custom ROM?
Jank4AU said:
Are you on stock or custom ROM?
Click to expand...
Click to collapse
Should have mentioned that. I am on resurrection remix and rooted.
Confirmed that it also bootloops on stock ROM, if you have ElementalX Kernel installed.
It seems that the stock rom isn’t close enough to aosp so this fix will only work on custom roms!
I edited the OP accordingly to the stock rom issue.
In the meantime can one of you guys on the stock rom do me a favour and check if you have libinputflinger.so and libinput.so located in system/lib and system/lib64 or if the libs are somewhere in vendor for you?
They exist both files.
hypnz said:
They exist both files.
Click to expand...
Click to collapse
It should be 4 files overall. libinput.so and libinputflinger.so have to be in system/lib and additionally in system/lib64.
but if they are in system and not in system/vendor then I have no way of fixing it atm I fear.
This kernel fixes continuesly reboots when you install magisk v17 or higher on lastest oreo stock rom.
Requirements
A2017U_V2.1.0B20 Firmware
TWRP
Instructions
Install a fresh Stock ROM.
Boot it once.
Install TWRP.
Install the boot image over TWRP by choosing install image option.
Flash Magisk v17 or higher.
Flash custom signed kernel modules magisk module over TWRP.
Reboot phone.
Download
BOOT_A2017U_V2.1.0B20_for_magisk_signed.img
Custom_Signed_Modules_A2017U_V2.1.0B20.zip
XDA:DevDB Information
[KERNEL][SOLUTION] Magisk 17 and higher for Stock ROMs, Kernel for the ZTE Axon 7
Contributors
asderdd
Source Code: https://github.com/Asderdd/android_kernel_zte_axon7/tree/zte-8.0.0
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: A2017U_V2.1.0B20
Created 2018-10-21
Last Updated 2018-10-21
Thanks ihsan awesoma work :good: :highfive:
Any idea if this can also be used on nougat roms? Or perhaps the same modification used to boot those with Magisk?
Dodgexander said:
Any idea if this can also be used on nougat roms? Or perhaps the same modification used to boot those with Magisk?
Click to expand...
Click to collapse
I can do it again for nougat but I recommend you to use oreo b20. It's better than all others about sound quality, camera and more stuff.
asderdd said:
I can do it again for nougat but I recommend you to use oreo b20. It's better than all others about sound quality, camera and more stuff.
Click to expand...
Click to collapse
It is possible doing this for the A2017V3.0.0B17 ?
for all axon 7 phones running oreo b20 stock?
Thanks for your job, I've seen your source under github, can you confirm that to avoid bootloops on Magkisk > 17 is enough to set to "n" the SeLinux policy?
Teşekkürler.
foggydew88 said:
Thanks for your job, I've seen your source under github, can you confirm that to avoid bootloops on Magkisk > 17 is enough to set to "n" the SeLinux policy?
Teşekkürler.
Click to expand...
Click to collapse
Yes, if you want use a custom init binary you need to disable zte's policyproc.
Aviver said:
It is possible doing this for the A2017V3.0.0B17 ?
Click to expand...
Click to collapse
If you send me pm that includes the stock boot.img and /system/lib/modules /system/vendor/lib modules folders it's possible.
Predatorhaze said:
for all axon 7 phones running oreo b20 stock?
Click to expand...
Click to collapse
Absolutely.
great work!
Hi, thanks for your work but after this i have no wifi on G model.
ppllpp said:
Hi, thanks for your work but after this i have no wifi on G model.
Click to expand...
Click to collapse
Don't forget to install Magisk module that I gave.
asderdd said:
Don't forget to install Magisk module that I gave.
Click to expand...
Click to collapse
Ok, solved using directly Magisk to flash custom module. Thanks.
Thanks for this @asderdd works well. Do you know if it will still work with v17.2 or v17.3? I tried but it doesn't seem too although I know they are beta and dev versions.
ppllpp said:
Hi, thanks for your work but after this i have no wifi on G model.
Click to expand...
Click to collapse
This is probably because you didn't boot first. I had this too. Make sure you install stock rom first, install recovery and then after the first boot make sure to restart, go to recovery and then flash it according to the steps.
Dodgexander said:
Thanks for this @asderdd works well. Do you know if it will still work with v17.2 or v17.3? I tried but it doesn't seem too although I know they are beta and dev versions.
Click to expand...
Click to collapse
Sure, it works with all sub versions of magisk 17. I'm using magisk 17.4 canary build at this moment.
Dodgexander said:
Thanks for this @asderdd works well. Do you know if it will still work with v17.2 or v17.3? I tried but it doesn't seem too although I know they are beta and dev versions.
This is probably because you didn't boot first. I had this too. Make sure you install stock rom first, install recovery and then after the first boot make sure to restart, go to recovery and then flash it according to the steps.
Click to expand...
Click to collapse
Yes i know i should have followed exactly the instruction but i flashed recovery and modem with miflash all at once then twrp and encryption is not the best...anyway problem solved. Even if custom module in twrp give me error and i don t know why, maybe encryption.
I have tried Oreo yet, but I'm very eager to do so. I've seen some comments that system is now only ro, does this fix this? And can i assume safetynet passes on this? Thank you!
Sent from my ZTE A2017U using Tapatalk
@asderdd On stock latest nougat A2017U Magisk 17.x also bootloops to recovery, is this a separate problem? I'm interested in reporting whatever you had to do to topjohnwu so he can make a fix in Magisk if possible. Or better yet if you're not to busy maybe you can advise him?
thanks
bluenote73 said:
I have tried Oreo yet, but I'm very eager to do so. I've seen some comments that system is now only ro, does this fix this? And can i assume safetynet passes on this? Thank you!
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Nope it doesn't effect mount status of system. I recommend you to make a magisk module that can adds, modifies or removes files systemlessly. Unfortunately b20 rom can't pass safetynet.
bluenote73 said:
@asderdd On stock latest nougat A2017U Magisk 17.x also bootloops to recovery, is this a separate problem? I'm interested in reporting whatever you had to do to topjohnwu so he can make a fix in Magisk if possible. Or better yet if you're not to busy maybe you can advise him?
thanks
Click to expand...
Click to collapse
The solution is disabling zte's selinux policyproc feature. Lookup the commits at github for details. I don't know what had changed on magisk v17 to cause conflict with our policyproc.
asderdd said:
Unfortunately b20 rom can't pass safetynet
Click to expand...
Click to collapse
I am pretty sure I had safetynet passing fine with your solution before + MagiskHide props config module but I kept losing it after some time. I thought it was something I did wrong but today after a fresh reinstall I still can't pass safetynet with the MagiskHide props config module spoofing the Nougat ZTE Axon fingerprint.
Have google done something which means we can't pass safetynet on b20?
only twrp from nfound works on this rom?
---------- Post added at 12:24 PM ---------- Previous post was at 12:00 PM ----------
doesnt work for me,G version.Magisk is shown in app list,but not in drawer and no root is detected
---------- Post added at 12:29 PM ---------- Previous post was at 12:24 PM ----------
i rebooted again,works now.Magisk 17.3
So after Trying different PIE GSIs, I Found a less buggy GSI rom. It's "RR-P-v7.0.3-20191112-A64-A.img" that i found on @turbolukex5 thread on this link. https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
basically i tested camera, BT,in call audio, Fingerprint and Mobile Hotspot. So far they work pretty nice. The only thing that doesn't work as of now is the MTP. So you need to reboot to TWRP to transfer files on storage.
If this thread is prohibited, kindly remove it. I just want to share what i found today. Thank you.
Curcepogi said:
So after Trying different PIE GSIs, I Found a less buggy GSI rom. It's "RR-P-v7.0.3-20191112-A64-A.img" that i found on @turbolukex5 thread on this link. https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
basically i tested camera, BT,in call audio, Fingerprint and Mobile Hotspot. So far they work pretty nice. The only thing that doesn't work as of now is the MTP. So you need to reboot to TWRP to transfer files on storage.
If this thread is prohibited, kindly remove it. I just want to share what i found today. Thank you.
Click to expand...
Click to collapse
You can use kraken kernel for fixing MTP.
heni87 said:
You can use kraken kernel for fixing MTP.
Click to expand...
Click to collapse
Thanks bro. I will try it later if you can give me the link. I cant rly find it on internet.
Curcepogi said:
Thanks bro. I will try it later if you can give me the link. I cant rly find it on internet.
Click to expand...
Click to collapse
https://github.com/SPART4NICUS/DOWN...Kernel-V3.0-universal7870-Treble-20200108.zip
Working. On. A6+ gsi
elokuba said:
Working. On. A6+ gsi
Click to expand...
Click to collapse
Yes. It will definitely work on any Device that is treble Enabled. You just need to find the Correct vendor for your device. :highfive:
heni87 said:
https://github.com/SPART4NICUS/DOWN...Kernel-V3.0-universal7870-Treble-20200108.zip
Click to expand...
Click to collapse
Thanks. I will try and report here later. As of now the only bug i got is the Camera when using flash. The shutter is not synced with the flash. You will get a dark photo when taking at night.
Curcepogi said:
Thanks. I will try and report here later. As of now the only bug i got is the Camera when using flash. The shutter is not synced with the flash. You will get a dark photo when taking at night.
Click to expand...
Click to collapse
That's basically a bug which is present in almost every GSI. Use footej/open camera from play store instead. Those will also give you back some of the manual controls if you are into that sorta thing.
heni87 said:
That's basically a bug which is present in almost every GSI. Use footej/open camera from play store instead. Those will also give you back some of the manual controls if you are into that sorta thing.
Click to expand...
Click to collapse
I already tried the kernel. I got a working MTP after reboot(bare bones, no GApps). But when i install GApps(Aroma) the rom is very sluggish and FP was broken during setup. So i did not finish the setup and i quickly reverted to stock. ?
wats bether version on a6+
Curcepogi said:
I already tried the kernel. I got a working MTP after reboot(bare bones, no GApps). But when i install GApps(Aroma) the rom is very sluggish and FP was broken during setup. So i did not finish the setup and i quickly reverted to stock. ?
Click to expand...
Click to collapse
Not sure but the guy who compiled that kernel said not to use magisk it breaks too many stuff.
heni87 said:
Not sure but the guy who compiled that kernel said not to use magisk it breaks too many stuff.
Click to expand...
Click to collapse
I did not used magisk on setup. This are my steps:
-Flashed GSI
-Flashed Kraken kernel
-rebooted and did factory reset
-Resized the system to flash GApps.
-flashed GApps aroma.
And the phone is already sluggish. Any thoughts bro?
elokuba said:
wats bether version on a6+
Click to expand...
Click to collapse
I don't have that device. But u can use CPU info or CPU Z and Treble check to know what variant is for you.
Curcepogi said:
I don't have that device. But u can use CPU info or CPU Z and Treble check to know what variant is for you.
Click to expand...
Click to collapse
Which version should i use? Arm64? Or a64 only?
tutul2336 said:
Which version should i use? Arm64? Or a64 only?
Click to expand...
Click to collapse
Same as mine. A64_a only
Curcepogi said:
I did not used magisk on setup. This are my steps:
-Flashed GSI
-Flashed Kraken kernel
-rebooted and did factory reset
-Resized the system to flash GApps.
-flashed GApps aroma.
And the phone is already sluggish. Any thoughts bro?
Click to expand...
Click to collapse
Would help you out much better if you could come at our telegram. But for now try doing everything first and reserve flashing kraken as last step also factory reset is unnecessary.
heni87 said:
Would help you out much better if you could come at our telegram. But for now try doing everything first and reserve flashing kraken as last step also factory reset is unnecessary.
Click to expand...
Click to collapse
I appreciate your efforts on this query. I will try your suggestions as soon as im available again. Thank you bro.
Curcepogi said:
I appreciate your efforts on this query. I will try your suggestions as soon as im available again. Thank you bro.
Click to expand...
Click to collapse
Anytime bud. Search us on telegram by @SM_A600X don't wanna post the invite link since a mod will eventually come and take it down.
heni87 said:
https://github.com/SPART4NICUS/DOWN...Kernel-V3.0-universal7870-Treble-20200108.zip
Click to expand...
Click to collapse
There is newer version https://github.com/SPART4NICUS/DOWNLOADS/releases/tag/RC11
any good GSI on A6+? Have you tried Havoc OS?