Related
I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
Edit: A solution which can pass Safetynet is HIGHLY preferred
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
xdafan15 said:
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
Click to expand...
Click to collapse
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
I tried stock 7.0 for a few days but went back to Lineage OS. I missed the long press on icons to get actions menu that isn't in 7.0 (among other things).
Spencervb256 said:
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
Click to expand...
Click to collapse
ptn107 said:
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
Click to expand...
Click to collapse
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
xdafan15 said:
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
Click to expand...
Click to collapse
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Spencervb256 said:
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Click to expand...
Click to collapse
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
xdafan15 said:
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
Click to expand...
Click to collapse
No haha it's hard to explain. But until about a month ago, no custom roms could be flashed if users were running stock 7.0 from Moto. Now there are a couple builds of roms which can be flashed over stock 7.0, with no bootloops. This is because Motorola upgraded the modem firmware in stock 7.0, so the custom roms did not work with it.
You can 100% mix the two, so if you are in stock 6.0, you can install any rom you like, as they are made to work with the 6.0 firmware. Even though they are nougat roms.
When stock 7.0 was released, people had issues with installing custom roms over that, because of the modem upgrade, but now there are a couple builds that will install over this firmware and not result in a bootloop.
I will try and find a few links for you which can explain some things, this is all from my mediocre memory haha
If that confused you even more then just stay tuned, I'll send you a pm soon with links to some reading in different threads which explain it much better than I can!
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
Pretty much...
xantanion said:
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
Click to expand...
Click to collapse
aybarrap1 said:
Pretty much...
Click to expand...
Click to collapse
My rule of thumb is simply wait for the official supported OS version. This means everything (including modem) will work - the community will then hack and modify from there.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
That's exactly it! You nailed it. Explained it better than I could, so yeah, you got it!!
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
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
keval3492 said:
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
Click to expand...
Click to collapse
64bit recoveries can handle 32bit roms too. Use a 64bit recovery and everything is fine.
You cannot downgrade your bootloader from stock Oreo to stock nougat(your current Rom). Custom roms won't flash bootloaders,only stock roms.
Your whole flash storage of your device is divided into several partitions like system, data, boot, recovery, internal storage. That's why you have to deal with less memory in your internal storage(10 out of 16 for example).
You cannot(yeah, but don't do it) modify the partition size cause it's used to met some requirements.
The rom will be flashed into system/data partition, not internal storage but also uses ram of course
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
keval3492 said:
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
Click to expand...
Click to collapse
Yes you can get official Oreo update if you are on Pie custom rom. You just need to go back to stock rom or flash the stock Oreo rom manually like the soak test.
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
keval3492 said:
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
Click to expand...
Click to collapse
Here's a link for the 64 bit TWRP https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 for flashing both 32 bit and 64 bit custom ROMs and TWRP flashables.
Of course, unlocking your bootloader and flashing a custom ROM via TWRP will unavoidably erase your device, so back up as necessary. Be also aware that flashing a custom ROM may necessitate flashing magisk as well, to get your device Google certified again.
As for a particular ROM, your best bet is to have a look at each custom ROM's page and particularly the first page and the last few pages. Both of those should give you information on how suitable the ROM is from other user's reports for your usage and also give you an idea how often the ROM is updated.
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
keval3492 said:
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
Click to expand...
Click to collapse
For some apps, like banking apps for example, these apps may not function properly if they detect an unlocked bootloader, or if your device does not pass Google Play Store certification. If you're wanting to flash a custom ROM or a TWRP flashable, then you may have to consider flashing magisk for magisk hide. Magisk hide helps to hide your unlocked bootloader status and thus may get your device certified to use these apps. Up to you - depends on if you use apps that won't work if they detect your device has an unlocked bootloader.
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
keval3492 said:
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
Click to expand...
Click to collapse
I'm guessing by Athens you mean athene? If so, athene is the device codename for the Moto G4/plus (2016). Custom ROMs and software designed for athene should work on our services, though please check the release dates of such software. That also means software built for another device codename may not work.
A kernel is part of the software communicating between the hardware and the software. Custom ROMs will come with one usually. If you choose to flash another kernel, ensure you flash the correct type of kernel - there are kernels for stock 7.0/6.0 (Motorola), 7.1 (custom) and kernels for custom 8.1/9.0 ROMs. These may not be cross compatible and as such if you flash the incorrect kernel to your device your device may fail to boot (buy then that's what TWRP backups are for). Due to the lack of source code for stock 8.1, I've not seen custom kernels built for the stock Motorola 8.1 stock ROM yet.
Thank you sir for guide me about athene and kernel ,so i choose custom rom only made for athene and kernel is also built in with custom rom.
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
keval3492 said:
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
Click to expand...
Click to collapse
Please search within the correct rom thread https://forum.xda-developers.com/mo...4-oreo-soak-test-update-t3871136/post78966322
I did not get proper answer from link you send ,please help for this..
keval3492 said:
I did not get proper answer from link you send ,please help for this..
Click to expand...
Click to collapse
Should be the same process to unlock your bootloader, provided your motherboard is the same and you've still got your IMEI and software channel.
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
keval3492 said:
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
Click to expand...
Click to collapse
When you unlock your bootloader, you need the unlock key. The unlock key is likely generated from and linked to your motherboard; if your motherboard had been changed, then you'd have to get a new unlock key.
If your IMEI is still present in your device and working, the unlock key should work. Some users with existing IMEI issues may not be able to unlock their bootloaders.
Basically, if your device is the same when you requested the unlock key, and everything is working okay, then unlocking should be the same as Nougat without any further steps. Back up, boot to fastboot and connect your device to your computer, then enter the unlock key command - with your key - on your computer in the minimal ADB terminal.
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
keval3492 said:
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
Click to expand...
Click to collapse
Should be - use the same key as you used to unlock your bootloader before (after you had your motherboard changed). Be aware you will not be able to re-lock your bootloader if you unlock your bootloader at the moment. We do not have the Oreo firmware to lock stock Oreo devices or devices previously updated to stock Oreo firmware.
Oreo firmware means coding in CMD ??
I know this is a mostly dead platform, but figured it was worth a shot to ask. My Trek 2 stopped auto-rotating the screen awhile back while it was stock. I had not updated in awhile, so I tossed in an AT&T sim to get it up to date. I did not notice it at first (I use the tablet intermittently) but I am almost certain that update coincided with the screen no longer rotating.
After several months and being tired of manually rotating the screen I took the time to put AOKP on it. Part of my desire was hoping to resolve the screen rotation. It did not. But, I did see a comment in one of the ROM threads where it looked liked someone had the identical issue and it might be related to the software or a minor difference in hardware. Does anyone have any ideas?
Some K88 tablets' auto-rotating only works with MM, not Nougat. Check your current firmware. It will be 7.0.1 or something above 7.0.0, not 6.X.X
The only solution is by flashing K88 back to MM. Sometimes, directly flashing B33 still may not work. So I recommend to flash B31, and then upgrade to B33, but not again to Nougat. Once update to Nougat, then the auto-rotating will not work again. I tried all custom firmware(nougat + oreo), but my K88 auto-rotating is not working with them.
To flash back to B31, you need to install TWRP using jasminetool. And then directly flash B31 stock firmware.
seungbaekm said:
Some K88 tablets' auto-rotating only works with MM, not Nougat. Check your current firmware. It will be 7.0.1 or something above 7.0.0, not 6.X.X
The only solution is by flashing K88 back to MM. Sometimes, directly flashing B33 still may not work. So I recommend to flash B31, and then upgrade to B33, but not again to Nougat. Once update to Nougat, then the auto-rotating will not work again. I tried all custom firmware(nougat + oreo), but my K88 auto-rotating is not working with them.
To flash back to B31, you need to install TWRP using jasminetool. And then directly flash B31 stock firmware.
Click to expand...
Click to collapse
Thanks for chiming in! Any idea what the limitation is? I have LineageOS installed right now, it runs great other than the rotation issue. It looks like all of the custom ROMs are Nougat based, is my only option to go back to stock to get auto-rotation back?