Develop Bugs

Unable to access root

I'm using asus zenfone 2 ze551ml
it's running latest build 21/9/17 of lineage os 14.1
im unable to get root access
i have checked my system folder in root directory through TWRP
Su file is present but although after allowing apps and ADB to get root access in developer setting
the ui which apparently ask for root access is not popping up
and root checker suggests that your device is not properly rooted at all
This problem came up when is switched rom lineage os 14.1 (nougat 7.1.1)
to lineage os 14.1(nougat 7.1.2)
recently updated su addons dated 25/06/2017 are having such a problem for me
plz update the su addon for X86(or firmware) or atleast give me the reason to stay on this rom
Thanks A Lot

andy9970 said:
I'm using asus zenfone 2 ze551ml
it's running latest build 21/9/17 of lineage os 14.1
im unable to get root access
i have checked my system folder in root directory through TWRP
Su file is present but although after allowing apps and ADB to get root access in developer setting
the ui which apparently ask for root access is not popping up
and root checker suggests that your device is not properly rooted at all
This problem came up when is switched rom lineage os 14.1 (nougat 7.1.1)
to lineage os 14.1(nougat 7.1.2)
recently updated su addons dated 25/06/2017 are having such a problem for me
plz update the su addon for X86(or firmware) or atleast give me the reason to stay on this rom
Thanks A Lot
Click to expand...
Click to collapse
Did you upgrade or do a full wipe?
Some stuff that I read indicated that uninstalling old su before installing the new su build was a good idea. It was released for those that had issue with the old one and not really a upgrade.
I recently did a full wipe on my phone (moto z) and used latest su on 7.1.2 without problems.
I suggest checking out what the local forum thread of your device says. If this is a device and build specific issue I'm sure some other people noticed it too.
Sent from my XT1650-03 using Tapatalk

i am facing the very similar issue on my zenfone 2 as well. I updated from rooted stock ROM to latest lineage 14.1 . kindly help

swejuggalo said:
Did you upgrade or do a full wipe?
Some stuff that I read indicated that uninstalling old su before installing the new su build was a good idea. It was released for those that had issue with the old one and not really a upgrade.
I recently did a full wipe on my phone (moto z) and used latest su on 7.1.2 without problems.
I suggest checking out what the local forum thread of your device says. If this is a device and build specific issue I'm sure some other people noticed it too.
Click to expand...
Click to collapse
I know what are you trying to say
That many device uses same su so check you my phones specific
But tbh what is know is there are only 5 devices running x86 cpu zenfone 2,4,5,6
And only one of them is running lineage os 14.1 other dont support officially so they use 13.0 's addon zip
That means only zenfone 2 can flash 14.1's addon su
And FYI I did wiped first
And xiomi's phine are having same problem with this popup

Finally a solution........ That after long desperate efforts worked for me. You can flash the Magisk 13.0 zip. Mind you an upgraded version will lead you to a loop to your custom recovery. Magisk 13.0 is zenfone 2 x86 architecture compatible. Good luck. Just got this solution last night. Tell me if this helped you and also if you found a better way.

Ayushman Tiwari said:
Finally a solution........ That after long desperate efforts worked for me. You can flash the Magisk 13.0 zip. Mind you an upgraded version will lead you to a loop to your custom recovery. Magisk 13.0 is zenfone 2 x86 architecture compatible. Good luck. Just got this solution last night. Tell me if this helped you and also if you found a better way.
Click to expand...
Click to collapse
Did i have to wipe my lineage os?

Ayushman Tiwari said:
Finally a solution........ That after long desperate efforts worked for me. You can flash the Magisk 13.0 zip. Mind you an upgraded version will lead you to a loop to your custom recovery. Magisk 13.0 is zenfone 2 x86 architecture compatible. Good luck. Just got this solution last night. Tell me if this helped you and also if you found a better way.
Click to expand...
Click to collapse
Wherr can i find magisk 13.0 ?

Samsung Galaxy A5 2017 Custom ROM and Issues with Fixes

So, I own a Samsung Galaxy A5 2017 and I became interested in Custom ROMs. So without any knowledge about flashing custom ROMs I tried it on my other Samsung Galaxy S5 and it worked flawlessly.
Thinking it would be same for my own A5 2017, I went ahead and installed TWRP Recovery and flashed a custom ROM. Little did I know that doing so will trip my KNOX and I won't be able to use secure folder and most of the Samsung apps. Thinking it would be best to switch to a custom ROM, I went ahead and flashed Lineage OS 14.1.
The flashing process completed without any error, but the device did not detect my sim cards even though I had 2 sim cards installed in it. Turns out my baseband version was displayed as 'unknown' and my IMEI was also 'unknown'. This issue took me 2 whole days to resolve and I found a fix for you guys.
To fix the baseband issue, I realized that my official stock ROM was android 8.0 and I flashed a custom ROM of android version 7.1.2 since a custom ROM with 8.0 is not yet available for this device ATM(none that IK of). So, after 2 whole days it hit me that I had to flash the stock ROM of 7.0 on my device to fix the baseband of the device.
After flashing the stock ROM 7.0 on the device, I installed TWRP again and flashed the custom ROM once again and it fixed the baseband 'unknown' issue and my IMEI was back to normal again.
Now for the Samsung apps issue, after installing the custom ROM the S Health app, Gear app did not work. So to fix this issue I had to root my phone using Magisk and then change my build.prop file to bypass the issue.
This fixed my issue and made my apps works properly and now my Gear S3 also connects properly and functions very well.
For Resurrection Remix OS Custom ROM A5 2017 (a5y17lte): https:// androidfilehost.com/?fid= 818070582850504876 (remove the spaces)
For GApps (choose arm64) (7.1): google OpenGapps ( I can't post outside links yet )
Root through Magisk or SuperSU (both work)
For changing the build.prop file:
To fix this, open build.prop in /system and change ro.product.name=samsung and ro.product.manufacturer=samsung to another brand like lg or htc (in lowercase).
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-31
For anymore issue feel free leave them in the comments and I will try and help you guys out.

I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks

Sorry for the Late Reply
drajithkv said:
I also installed custom ROM lineage 14.1 on my galaxy a5 2017....after booting sim is not detected nor is IMEI is being showed...I havnt done a backup ......tried all possible ways....not working.....pls do help
Thanks
Click to expand...
Click to collapse
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.

MZainKh said:
Its almost too late now, hopefully you have fixed this issue. If not could you let me know which stock OS version did you come from and what OS version did you flash.
For example my stock ROM was on Oreo 8.0 and I flashed a Custom ROM that was based on Nougat 7.1.2, So to fix this:
1. First Download the stock ROM of the same version as that of the Custom ROM (i.e. custom ROM is 7.1.2 Nougat so download Nougat stock ROM) flash this stock ROM.
2. You can now proceed to install the custom recovery and a flash the custom ROM now.
This should fix your issue as your CSC will be updated to match your custom ROM and will let your phone detect the sim cards.
Click to expand...
Click to collapse
That doesn't work on the latest updates as downgrading is blocked.

i need help!!!

Greetings developers, someone of you can help me with the following problem, I can not install the rom AOSP the TWRP does not mark me any problem simply installs but when starting it restarts constantly without going through the restart, like the rom AOEX rom Validus, however I can install the rom Xperience, DotOs, RRemix and the Stock without any problem, you know why that happens, my device is a Moto Z Play XT1635-02.

You should use treble twrp to install rom

JR Bautista said:
You should use treble twrp to install rom
Click to expand...
Click to collapse
If I am using a TWRP of treble, however as i say that if installing an AOSP ROM with Android 9 or 8.1 does not pass from the logo and restarts, but if you install the Rom Xperience. 8.1 If run without problems, but the same Rom Xperience. 13 (Android P) does not run, I have tried with the DPI images and do not correrily

MirandaEduardo said:
If I am using a TWRP of treble, however as i say that if installing an AOSP ROM with Android 9 or 8.1 does not pass from the logo and restarts, but if you install the Rom Xperience. 8.1 If run without problems, but the same Rom Xperience. 13 (Android P) does not run, I have tried with the DPI images and do not correrily
Click to expand...
Click to collapse
update your bootloader to oreo?

JR Bautista said:
update your bootloader to oreo?
Click to expand...
Click to collapse
Yes, 0xC182

MirandaEduardo said:
If I am using a TWRP of treble, however as i say that if installing an AOSP ROM with Android 9 or 8.1 does not pass from the logo and restarts, but if you install the Rom Xperience. 8.1 If run without problems, but the same Rom Xperience. 13 (Android P) does not run, I have tried with the DPI images and do not correrily
Click to expand...
Click to collapse
do a backup of your files (if you are installing xpe you need a Treble supported TWRP) in xpe 13 maybe you need to do a format data (idk why but some users have a weird bug and only can be fixed if you do a format data
so do a format data from TWRP wipe-->format data-> write yes do a swipe reboot to recovery
copy all your files the rom , install it and enjoy!
if you are installing AOSP you should use twrp from alberto

TeamMex said:
do a backup of your files (if you are installing xpe you need a Treble supported TWRP) in xpe 13 maybe you need to do a format data (idk why but some users have a weird bug and only can be fixed if you do a format data
so do a format data from TWRP wipe-->format data-> write yes do a swipe reboot to recovery
copy all your files the rom , install it and enjoy!
if you are installing AOSP you should use twrp from alberto
Click to expand...
Click to collapse
Ok, thanks, friend, I'm going to try it like that

MirandaEduardo said:
Greetings developers, someone of you can help me with the following problem, I can not install the rom AOSP the TWRP does not mark me any problem simply installs but when starting it restarts constantly without going through the restart, like the rom AOEX rom Validus, however I can install the rom Xperience, DotOs, RRemix and the Stock without any problem, you know why that happens, my device is a Moto Z Play XT1635-02.
Click to expand...
Click to collapse
Hello brother i think you have a stock rom for xt 1635 02 addison single sim. Bro can you upload it for me or some kind of link? Appreciate your kind help

khanpatriot said:
Hello brother i think you have a stock rom for xt 1635 02 addison single sim. Bro can you upload it for me or some kind of link? Appreciate your kind help
Click to expand...
Click to collapse
Yes, this Is a link
https://drive.google.com/file/d/1W-DXW1qm0g6GaALjKuA1pvM-_RHqlZ4j/view

Thanks alot

Oooppss one more query does software channel matter? I'm currently running lineage os 14.1 and i can't find the exact software channel of my device I'm little confused is it retus retail or some other channel. Can u plz help?

Treble bootloop on G960F

Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .

itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
Click to expand...
Click to collapse
What's your phone's specifications?

Lanreallenjay said:
What's your phone's specifications?
Click to expand...
Click to collapse
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!

itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
Ask for help here
https://t.me/phhtreble/283195 <---
Read before any question ^^^

After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?

itShouldWork said:
Hello everyone,
I'm getting really frustrated hree as I can't flash any android 10 GSI. I either get bootloop, stuck on samsung logo or stuck on restarting on samsung logo.
Flashing different kernels seem to change the above behavior (instead of bootloop I get samsung logo and vice-versa).
I tried everything:
Doing the no-verity thingie...
Flashing stock files then GSI - nothing.
Flashing soldiers oreo kernel - nothing
Flashing endurance kernel - nothing
I can't find a vendor image that's compatible with any GSI on my phone. I also can't find any kernel that's compatible either.
So please, end my misery... if anyone managed to install android 10 GSI on this TREBLE COMPATIBLE DEVICE, please guide me through or provide any useful file (vendor img/kernel) that I might have been missed.
I wrote this because I couldn't find anything that could help... Thanks in advance!
EDIT:
I solved the problem with the kind help from phhusson and the guidance from Lanreallenjay (thanks, both of you!), so I'm trying to provide the solution for anyone that might be having the same problem as I had. So here it is:
For PIE GSI: use stock kernel/vendor (anything stock), flash the GSI, then flash Magisk -> it should boot fine now (only tested with phhusson's GSI. I had vibrating restart loops before, I wasn't installing magisk, that was my mistake)
For Android 10 GSI: same as above, but install the modded Magisk from phhusson's git (located @ v200 android 10 gsi post) instead of the normal one .
Click to expand...
Click to collapse
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?

rupert3k said:
So from stock you flashed AOSP 10 GSI to system partition then phh's magisk (in TWRP) then it works for you?
Click to expand...
Click to collapse
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).

rupert3k said:
After flashing G960FXXS7CSJ3 November stock firmware I can no longer flash anything.
(can't mount data partition)
When I try downgrading to G960FXXU5CSF2 June firmware Odin fails and the screen says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 7 BINARY: 5
November G960FXXS7CSJ3 seems to have upgraded the bootloader security, does anyone know a fix?
Click to expand...
Click to collapse
Have you tried formatting data with TWRP (to the part when it asks you to write "yes") then flash no-verity?
You should at least be able to flash TWRP. If you can't, just download the proper USB drivers for your device, it might be the culprit.
Cheers!

itShouldWork said:
Yep, it does. Buuut the rom is not stable at all, I've got random reboots/ crashes when opening settings and such, not usable at all. I'm on ONE UI 2.0 beta now which is much more stable (daily driver stable actually).
Click to expand...
Click to collapse
Phh just hinted it's likely Pie vendor causing panics:
"First you need to flash stock rom. Then install magisk and then this gsi.
Though please note that on Pie vendor, S9 kernel panics and reboot every few minutes, so it is highly unusable."

itShouldWork said:
Hey, thanks for the interest!
I've got the S9 Exynos variant (SM-G960F, Europe), I unlocked the bootloader several days ago.
It's on android 9 right now, I flashed the stock firmware after I've tried everything to get android 10 treble to work and failed.
Current kernel version: 4.9.59-16947752 (stock)
Build number: PPR1.180610.011.G960FXXS7CSJ3
I can flash any rom available besides GSI (I've used lineage OS 16 for a couple of days).
If you need anything else more specific just ask, I don't really know what exactly can help with this situation.
Cheers!
Click to expand...
Click to collapse
I have tried Android 10 GSI , using latest Q update

ZoiraP said:
I have tried Android 10 GSI , using latest Q update
Click to expand...
Click to collapse
Is it usable? any random reboots/ annoying instability?

itShouldWork said:
Is it usable? any random reboots/ annoying instability?
Click to expand...
Click to collapse
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.

ZoiraP said:
I have tried it partly , nfc isnt working , camera quality is bad , Bluetooth working , audio working , magisk working . I'll use it a bit more and tell you.
Click to expand...
Click to collapse
Camera quality might be fixed with Google cam, if you find a good port.

Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?

rupert3k said:
Not to derail the thread but I just noticed after installing Android 10 beta 2 Treble Info now reports my S9 supports Treble A/B, curious no?
Click to expand...
Click to collapse
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?

A\B
itShouldWork said:
Wait what? That's interesting...
Can someone with more experience enlighten us about the differences between the A only and A/B?
Click to expand...
Click to collapse
No real experience but A\B devices have two slots ie double the partitions (OnePlus has 67) .
This allows updates to be installed while running from slot A while the updated system is copied to B.
Apparently Q requires A\B so now we're on Q may as well try that next time we're curious
Phh just released:
AOSP 10.0 v208
Fix suspend/dt2w for Samsung Q vendor
Fix backlight for Samsung Q vendor
Samsung Q's fine, love gestures but the bloat is killing me.
You can tell Q's going to be so much leaner without bixby & friends.
Glad we installed it to get compatible but I think now we probably stand a better chance with 10 GSI's, hopefully LOS17 & Pixel Experience get updated again soon.
Wondering whether to following the rooting instructions yet?
Phh did say "flash stock rom then magisk and then gsi"
https://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961
ZoiraP's wondering why we sooo slow lol!

Wow this looks good: https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t4020939

Replacing google play with microg Note 10

Hello guys,
I have looked all over the xda developing threads for note 10 and note 10 + , can someone tell me if i unlock the bootloader, twrp , and flash a custom rom, if i would be able to replace / delete google play services and use micro g instead? With magisk or nanodroid methods?
Does anyone know which rom is good for that? For example dr.ketans ? I am using a dual sim note 10 , N970F
Thank you :fingers-crossed:

papari999 said:
Hello guys,
I have looked all over the xda developing threads for note 10 and note 10 + , can someone tell me if i unlock the bootloader, twrp , and flash a custom rom, if i would be able to replace / delete google play services and use micro g instead? With magisk or nanodroid methods?
Does anyone know which rom is good for that? For example dr.ketans ? I am using a dual sim note 10 , N970F
Thank you :fingers-crossed:
Click to expand...
Click to collapse
You would have to use a GSI or non touchwiz base ROM as touchwiz ROMs come with gapps

minidude2012 said:
You would have to use a GSI or non touchwiz base ROM as touchwiz ROMs come with gapps
Click to expand...
Click to collapse
Since long time ago there is One ui 2 /2.1 in samsung note 9 and 10 and s9 -s10/s20 series, correct me if i am wrong, the question is if i root a normall rom like dr.ketan's rom, and use nanodroid for example to remove the gapps and install the microg or magisk to flash the microg, will it work ?

papari999 said:
Since long time ago there is One ui 2 /2.1 in samsung note 9 and 10 and s9 -s10/s20 series, correct me if i am wrong, the question is if i root a normall rom like dr.ketan's rom, and use nanodroid for example to remove the gapps and install the microg or magisk to flash the microg, will it work ?
Click to expand...
Click to collapse
That should work but I can't say if it will or not

papari999 said:
Since long time ago there is One ui 2 /2.1 in samsung note 9 and 10 and s9 -s10/s20 series, correct me if i am wrong, the question is if i root a normall rom like dr.ketan's rom, and use nanodroid for example to remove the gapps and install the microg or magisk to flash the microg, will it work ?
Click to expand...
Click to collapse
There is a MicroG thread on XDA whch explains more in details how it works. As I understood from there, in order to have a functional MicroG environment on your phone, the prerequisite is to have a ROM with spoofing signature enabled. It doesn't matter if the ROM is OneUI based or AOSP or GSI, they need to have this cooked in.
Better have a look on the MicroG thread before you try it. And take back-up all the time, if you install TWRP.
It's gonna be tricky tho, since the phone doesn't have micro SD slot, so that you will need a PC to install via adb (so it seems).