I've owned and rooted quite a few android phones from various companies (SONY, HTC, Nokia, Motorolla, Samsung) but the I find the whole process most confusing with the LG.
I bought my device 2nd hand and it was already on LP (some nameless custom rom) rooted, with recovery. It didn't even list baseband... it said unknown. So I flashed CLoudy 2.2, used it for a few hours, than flashed CM12.1.
Now, about my confusion. I read everywhere that you need the JB bootloader for CM/AOSP, because the loki exploit was patched with kk/LP, however, as per the instructions in the rom's OP, prior to flashing CM12.1 I flashed an LP bootstack, and according to my understanding, a bootstack is a collection of partitions that include basebend, bootloader etc.
So then... If CM/AOSP need the JB bootloader, how is it that the OP recommends an LP bootstack, and everything works perfectly fine with it.
What am I missing?
Are there any apps, or any way I can see what bootloader, what baseband I have installed on my device?
shy_bump.png
Not sure about "how to know which one are you using". You flashed it, so you should've remembered it. Anyways, if you need a specific bootstack for a specific rom, just flash the one you need (stated in the op). Doing that before every Rom flash assures you don't end up with the wrong one, mess up your partitions and brick your phone. I like doing it manually so I know exactly what I have, but you can use apps like autorec.
I am not into aosp so I don't follow it as much, but some of the recent builds are using lp bootstacks because they use CAF sources which allow/require use of lp bootstack.
Hello there,
Is there any custom kernel available that can work on lineage and pass safetynet? I would like to run lineage nonrooted and be able to use Android pay.
koftheworld said:
Hello there,
Is there any custom kernel available that can work on lineage and pass safetynet? I would like to run lineage nonrooted and be able to use Android pay.
Click to expand...
Click to collapse
Lineage without root does pass Safetynet. At least it does on the Samsung Galaxy S5.
Not sure why it would be any different on Axon 7 (but happy to be corrected).
Lineage on Axon 7 with magisk and hide applied to Play Store definitely passes Safetynet. You may need to clear Play Store cache and reboot but it definitely works.
I can't get it to pass here. I've never rooted, but obviously have unlocked my bootloader and am running a custom kernel. Anyone have any success in this circumstance?
check if the selinux state is enforcing, if it is permissive safetynet will fail
koftheworld said:
I can't get it to pass here. I've never rooted, but obviously have unlocked my bootloader and am running a custom kernel. Anyone have any success in this circumstance?
Click to expand...
Click to collapse
I passed safetynet on RR, NucleaROM (w/ radioactive kernel), and LOS (The most recent one was Nuclea with Magisk 13.2). I can't verify if Android Pay works because we're just one step ahead of trading stuff here But I think I've seen some people who have been able to use it. Just a friendly reminder:
DO NOT LOCK THE BOOTLOADER IF NOT EVERYTHING IS STOCK (recovery, system, BL)
Choose an username... said:
I passed safetynet on RR, NucleaROM (w/ radioactive kernel), and LOS (The most recent one was Nuclea with Magisk 13.2). I can't verify if Android Pay works because we're just one step ahead of trading stuff here But I think I've seen some people who have been able to use it. Just a friendly reminder:
DO NOT LOCK THE BOOTLOADER IF NOT EVERYTHING IS STOCK (recovery, system, BL)
Click to expand...
Click to collapse
Everything (including Pokemon) works for me except pay. Selinux is set to enforcing, but cts profile match fails soi fail safetynet. Play store shows me as uncertified.
Los Dark rom has the kernal patch so it passes Safety Net
Hello, could someone explain me why magisk is necessary for custom roms for our device? When bootloader boots custom kernel it should boot rest of the system without any problems but it bootloops even before bootanimation
I also need custom ROM without Magisk. Is any Oreo custom ROM supports SuperSU?
RR-O ROM+Gapps goes to bootloop without Magisk and RR-O ROM+(Gapps)+SuperSU goes to Bootloader mode.
RR-O ROM+Gapps+Velocity Kernel boots & works, but RR-O ROM+Gapps+Velocity Kernel+SuperSU goes to Bootloader mode.
So anyone can please help for any Oreo custom ROM + Gapps + any rooting app (SuperSU, Lineage addonSU, phh's SuperUser).
mjnck said:
Hello, could someone explain me why magisk is necessary for custom roms for our device? When bootloader boots custom kernel it should boot rest of the system without any problems but it bootloops even before bootanimation
Click to expand...
Click to collapse
Have you figured it out yet? If not here, we go...
A Custom ROM is to give you 100% control, it's the point, and to have 100% control, the phone needs to be rooted to access the system.
In Linux, 'Root' means, what the Admin is in Windows...
Kind of pointless to install a custom rom, with limited control, of course you can root a stock rom too.
DoR3M3 said:
Have you figured it out yet? If not here, we go...
A Custom ROM is to give you 100% control, it's the point, and to have 100% control, the phone needs to be rooted to access the system.
In Linux, 'Root' means, what the Admin is in Windows...
Kind of pointless to install a custom rom, with limited control, of course you can root a stock rom too.
Click to expand...
Click to collapse
Not necessarily. Custom roms may have up to date security patches vs out of date stock roms on older phones. And custom roms may have extra functionality especially on bare bones stock rom like the MiA1.
barrack1 said:
Not necessarily. Custom roms may have up to date security patches vs out of date stock roms on older phones. And custom roms may have extra functionality especially on bare bones stock rom like the MiA1.
Click to expand...
Click to collapse
Yes of course all the 'Bells & Whistles' I didn't mention... But that's not the reason for rooting, which is what the OP asked...
Anyhow Custom ROMS give us many things, but it's about being in Control...
Cheers
I seem to remember reading something some weeks ago that Samsung did something in their latest few updates for the S8+ that made it impossible to root them... is that true?
I'm running a SM-G955F - DTM here... and I'd rather keep it rooted. I'm using magisk to root my devices.
Any insights for me?
AFAIK, as long as if you have twrp installed, you can update to whatever you want.
you then can:
make a full backup with TWRP, and Samsung can't do anything against you just restoring the full backup (with the old update and root)
just flash whatever (custom)ROM you want.
You already are rooted, so OTAs aren't a thing for you. I don't know if there even exists a twrp flashable stock ROM, but why don't you just switch to a custom rom (with the newest updates installed)?
Honestly, the only custom rom i know of is lineage (nee cyanogenmod), and at least on my old S5 I found that the fingerprint reader does not work on cyanogenmod. also, anything that checks safetynet does not work either.
[Lemmy] said:
Honestly, the only custom rom i know of is lineage (nee cyanogenmod), and at least on my old S5 I found that the fingerprint reader does not work on cyanogenmod. also, anything that checks safetynet does not work either.
Click to expand...
Click to collapse
LieangeOS isn't even available for our device (infact it is, but unusable).
The custom roms available right now are all stock touchwiz roms with slight modifications (most of them aren't even necessary, thx to aroma).
Look over to a thread like the one from Renovate ICE, most of the time roms like these are based on the newest sources from Samsung with the newest security patch level. It has root (Magisk or SuperSu) included and also passes safetyNet.
As I said in the post above, you always can make a full twrp Backup, try a ROM like Renovate Ice and if you don't like it, just go back to your stock ROM in minutes. :fingers-crossed:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
+1
ajeteja said:
The fingerprint was working fine on stock rom. Unlocked the bootloader and flashed twrp image. Somehow I formatted the internal storage erasing everything. After that, I flashed Pixel Experience custom rom and the fingerprint scanner isn't working. Getting "fingerprint enrollment issue". The enrollment happens only when I try pressing it very hard and I didn't face the issue on stock rom. I tried every custom rom available my bad. Somehow registered the edge of the finger and its working for now. What is the issue, I don't think it is hardware issue Any fixes for the same?
Click to expand...
Click to collapse
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
NZedPred said:
By any chance were you on the Oreo soak test when last on Stock rom? If so, the blobs wouldn't be compatible. Confirm whether or not that was the case, and if it is, then I'll point you in the right direction.
Click to expand...
Click to collapse
Yes I was on soak test. Pls help Moto g5s plus
@NZedPred Can you pls help? I am also facing the same issue.
#shubham Bane/- said:
Yes I was on soak test. Pls help Moto g5s plus
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Yes I was on soak test. Pls help Moto g5s plus
Click to expand...
Click to collapse
kiranbala003 said:
@NZedPred Can you pls help? I am also facing the same issue.
Click to expand...
Click to collapse
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
@NZedPred thanks man. It worked
kiranbala003 said:
@NZedPred thanks man. It worked
Click to expand...
Click to collapse
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
ugander1989 said:
hi, i am also facing the same issue. fingerprint lock disappeared after i flash a AEX custom rom from stock oreo soak test in my moto g5 plus (potter).
could you please provide the setp by step procedure to fix my issue thanks a lot
Click to expand...
Click to collapse
Step by step instructions are in my post above... Do you have a more specific question?
Does this work with moto G5s plus [sanders]
Will the above method work with moto g5s plus sanders
sarath6622 said:
Will the above method work with moto g5s plus sanders
Click to expand...
Click to collapse
Yes, if you did the same thing, i.e. flashed stock Oreo and then went to an Oreo custom rom, then yes the same approach will work. I have a flashable build and persist fix for sanders here:
https://www.androidfilehost.com/?w=files&flid=280579
Clean flash/Dirty flash?
@NZedPred I am facing the same problem. I own the Indian Moto G5 Plus (retin)
Here's what I did -
1. I unlocked my bootloader
2. I updated to Oreo (soak test) using the OTA capture.
2. I somehow rooted my phone after flashing TWRP.
3. Just after I flashed TWRP i.e. before rooting, I took a complete backup including the persist and EFS partitions.
4. After rooting, I clean installed MSM-Xtended ROM (8.1.0)
5. Everything is fine, but the fingerprint feature doesn't work/appear anywhere. Even the gesture support is gone.
What do I need to do?
If I follow your steps mentioned above i.e. flashing the persist-fix first, flashing the Nougat ROM you provided and then flashing any custom ROM, how should I proceed?
I am really confused whether I should clean flash (Wipe Data, System, Cache) after every step or dirty flash everything.
Please guide me.
Before you go back to custom ROM from stock Oreo ROM you have to flash stock nouget ROM if not fingerprint , NFC will not work.
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
@sinchan_nohara
navinsingh said:
I was also in the same problem of fingerprint not working. Tried your method i.e. flashed persist zip and nougat rom (after wiping dalvik, system ,data, cache) and now when I try to clean flash custom Oreo rom . Gapps is not getting flashed . Its detecting the rom as 7.1.2. any solution for this
Click to expand...
Click to collapse
U wrongly flashed firmware, try Oreo custom rom
NZedPred said:
Taken from the Oreo thread:
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc. To ensure they run correctly, it is MANDATORY to install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
So flash the persist fix from the first link, and flash the latest Nougat stock rom from the second. Reboot and make sure all is working OK in stock. Then flash whichever custom rom you want.
Click to expand...
Click to collapse
dhinesh_cool said:
U wrongly flashed firmware, try Oreo custom rom
Click to expand...
Click to collapse
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
navinsingh said:
can you please guide me to install a custom oreo rom. because when i try to flash custom oreo rom (franken rom i used) , the rom gets flashed but the gapps (arm64 mini 8.1.x) fails everytime and shows error code 20 (incompatible rom). but i had flashed both the rom and the gapps successfully before the fingerprint issue bcoz of which i had to flash the stock 7.0 with the persist fix. and one more thing the rom is getting flashed succesfully (as twrp shows me) but when i try to boot into system without the gapps installed( i.e. only with the rom) it gets stuck on the bootloader page so i think the rom itself is not getting flashed. please help......
Click to expand...
Click to collapse
ask in telegram grp