Resurrection Remix "Android setup" fails (RR8.1.0) - OnePlus 5T Questions & Answers

Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat

wahlmat said:
Hi!
Since the official OxygenOS Android 10 update left me less than happy, I decided to try and give a custom ROM a chance again. Had RR on my OPO a few years back so that felt like a good thing to default back to, but for OP5t. Unlocked the bootloader, got TWRP 3.3.1 installed. All good. Got RR8.1.0 for dumpling downloaded, also downloaded gApps and magisk. Transferred them over, installed the .zip's. So far so good. Booting into RR seems fine at first, but when I get to the point of backing up my data from a previous device/or skipping it, the installer freezes/loops/fails.
I assume I have the correct firmware since OxygenOS 10 works "just fine". When I try to recover stuff from an old device, I choose my old backup from yesterday, then it goes into a screen where it says "Wait a few secs..." or something of that nature. The circle around it just keeps looping. This takes only a few seconds to find the data if I'm installing OOS. So this is a dead end. If I try to pass through without anything, accounts, face unlock and all that, I get to a point of where I am supposed to setup the assistant. Whether I choose "Skip" or "Next" (as in set it up) I keep looping back 2 steps to enter pin, then set up the assistant again.
I have re-installed RR a bunch of times as it didn't work, first I had problems with "Enter device pin" which I had no clue what it was in the android setup. Cleaned it all up, installed OOS10, that worked to setup and install just fine. Cleared it all out again, tried to install RR, got past the "Enter device pin", but then it failed as mentioned above.
TL;DR: RR8.1.0 Dumpling Android setup fails when backing up from account/can't get past assistant. OOS10 works as it should.
Any clue on what the problem might be? Tried installing at least 10 times, but it didn't work. Any help is appreciated If there's just some general flaw in RR for this device/version, any other custom ROM that is to be recommended?
/Wahlmat
Click to expand...
Click to collapse
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?

ireaper4592 said:
Maybe it's because u trying to install 8.1 ROM on pie firmware just a thought?
Click to expand...
Click to collapse
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?

wahlmat said:
Could be. Tried to search for A10 firmware, but came up short (had this issue with my OPO and firmware for A7). Got AICP installed now and that seems to work.
Out of curiosity, does OnePlus release the firmware openly, or do you have to find some guy's "homemade" firmware in a future case like this?
Click to expand...
Click to collapse
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it

ireaper4592 said:
They have all firmwares on there sight go there and click three lines,go to support,look for device and find latest firmware download that's it
Click to expand...
Click to collapse
I actually can't seem to find it on their site.

wahlmat said:
I actually can't seem to find it on their site.
Click to expand...
Click to collapse
https://www.oneplus.com/uk/support/softwareupgrade

Related

sw3 on Lollipop pairs with phone but does not connect with wear

I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
baronimus said:
I fixed (to a certain degree) a bootlooped watch by installing a stock Lollipop Rom. It does not work though, because watch cannot connect with Android wear and therefore not complete installation. (It does pair up with the phone and says wait a minute) Any suggestions?
Click to expand...
Click to collapse
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
golfnut22 said:
Our watches must be brothers as I have had the exact same scenario. I did however get it back going to LP, paired, etc to the smartphone. What I had to do was fastboot format cache, then userdata, then fastboot reboot. I then fastboot flash the .simg file, the recovery.img file and the boot.img file, then fastboot reboot. I then connected to XC which did not work all the way through, but gave me access to be able to use twrp.img (for some reason, twrp would not boot in LP). Then in twrp I adb pushed the LP rom that is signed and after pushed, installed it. Then, I had to leave it alone for the battery drain as it was locked up or something. After it drained, which was evident because it was not warm, I charged it and it is now working again...but only in LP. I cannot get MM installed.
IF you happen to get MM installed and working, please advise your steps.
Click to expand...
Click to collapse
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
baronimus said:
Thank you for your reply. I will certainly let you know of any progress. The procedure I followed was somewhat more simple. I flashed the twrp with fastboot, booted twrp up, transferred the downloaded rom image from the pc to the watch and booted the rom from twrp. It then starts up but fails to play with wear.
Click to expand...
Click to collapse
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
golfnut22 said:
Regarding the pairing with phone, I had to go in the phone settings, application manager, open android wear, and clear the data and cache in order for it to recognize my watch. I had previously had it linked to another phone and had the phone connected to a different watch so I think it was getting confused.
Regarding getting past the 5.0.1 update, I have found this post http://forum.xda-developers.com/smartwatch-3/orig-development/tut-how-to-fix-swr50-fastboot-t3258918 and am currently getting OTA updates as I write. I don't know how far I will get, but so far I have had two updates. I did not flash the updates, only the original rom. Then I went into the watch settings, about, and pressed the software or system update (I've been doing it manually each time).
Edit: It allowed me to update all the way to MM, however I got the 4 dots /symbols again when it was rebooted. Up to that point, which the last update was the LCA43, the watch appeared to be working fine. I did not test it much as I was just trying to get all the updates I could. So, while it did not go all the way thru to MM, I still was very happy that I got up to that update.
Click to expand...
Click to collapse
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
baronimus said:
I now succeeded in pairing up with the phone. What I did was to flash another Rom which I found in the forum. It's called ROM_SW3_5.1.1.2_LCA43. Now the watch works just fine on Lollipop and updates automaticly. I am going to try and upgrade to MM but I fear its going to get stuck on the infamous four symbols when I do. I am happy though to have the watch up and running again, it was deemed paperweight for a while
Ok stuck again. Still at Lollipop version 5.1.1.2
Click to expand...
Click to collapse
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
golfnut22 said:
Does yours actually have 5.1.1.2 in the about section? Mine says 5.1.1 with the build as LCA43.
Click to expand...
Click to collapse
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
baronimus said:
Indeed it does. The Rom comes from here: http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
Since the problem occurs only when updating to MM I am led to think that we have a kernel issue?
Click to expand...
Click to collapse
I may have stopped updating one to early. Anyway, my watch updated by itself last night all the way to MM, now it is stuck again. I'll have to search and see if there is a way to stop the automatic OTA updates.
I have seen where people have flashed only the kernel. I have not. At this point, it would be nice just to keep it at the last LP. I'll let you know if I find anything. Thanks.

Lineage Update Installation Issues

As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
It will probably be the same as for my L900 with CM13 were I have to download the update, reboot into TWRP and update manually.
Sent from my SM-G900T using Tapatalk
nezlek said:
As more Lineage OS builds come on line and multiple "nightly" update builds for devices start to appear, one of the issues users may face is the how and why of installing them. The Lineage UPDATER states that it will reboot to the device's recovery to install the update, but that doesn't guarantee anything. If that recovery happens to be, for example, TWRP 3.0.2.0 on an LG v410 tablet, all that might happen is you might find yourself, as I did, staring at a TWRP screen with NOTHING happening. The goal of this thread is to give Lineage users a place to consolidate their experience-based knowledge of how to handle this - other than re-flashing the whole thing -for whatever device(s) they may have.
Click to expand...
Click to collapse
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
nezlek said:
This is far from the worst thing that has ever happened, but WHAT, for instance WOULD be the recoveries that DO allow for automated updates? In my case, I downloaded the new nightly to the root directory my SD Card and let fly, and everything worked, but that seems rather not elegant.
Click to expand...
Click to collapse
Automated updates work fine for me. It automatically boots onto TWRP, applies the update, and reboots.
Might be a device-specific issue. I am on the OnePlus One, and the same TWRP version (of course made for my device).
I am guessing that perhaps there is an issue reading or writing the recovery script.
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
nezlek said:
Interesting. Sure didn't work for me this a.m. but as I said, far from the end of the world. I also think the "nightly" is going to morph into the "weekly" and that will be fine, too. I have yet to find anything that doesn't work to my satisfaction aside from not automatically picking up my Wi-Fi at boot - not exactly a deal breaker
Click to expand...
Click to collapse
BTW, are you able to navigate to that directory in TWRP?
Oops. Right after I clicked on send I realized I didn't answer your question!!
Yes, and the zip file is there, but nothing happened. As I said, far from fatal.
I updated my opo (Bacon) with the nightly ota download and most recent twrp, after reboot I had lost my home screen (2 of 3 pages remained) and several of the apps that I had dragged to those screens.. didn't work well for me. I let the ota reboot into twrp and it seemed to proceed without troubles until the opo came back to life. (finished booting)
Galaxy S5 SM-G900T here. Wiped my phone and installed lineage-14.1-20170131-nightly-klte-signed.zip with open_gapps-arm-7.1-stock-20170131 the day it came out and it has been good so far, no crashes or freezes and all apps work good except FolderMount, no biggie. Tried to install lineage-14.1-20170207-nightly-signed.zip and is giving me an "error 7 can't install this package on top of incompatible data". Any way to fix this without factory reset? Doesn't make sense to factory reset every week for an update.
Update: Tried to reflash lineage-14.1-20170131-nightly-klte-signed.zip and got the same error. So something must have changed. The only thing I can think of is I have SU 2.79 installed.
Update 2: Removed root, restored boot and same continues. I dont want to wipe on every update.
Sent from my SM-G900T using Tapatalk
Well, now semi-automatic at any rate.
Are you able to navigate to the download directory in TWRP?
/data/data/org.lineageos.updater/app_updates
First, sincere THANKS to jhedfors for this priceless bit of wisdom
Getting better. Still no "automatic update" but the latest "nightly" build did fire up TWRP, and put the update zip file into the aforementioned folder, and after that, installing it was the proverbial snap. I can't speak for everyone, but I would find no horror in the folks at Lineage giving in to reality and calling the "WEEKLY" as opposed to "NIGHTLY" builds.
Hey, since the only device I happen to have running Nougat at the moment also happens to be the OLDEST device I use on a regular basis, the Complaint Department shall remain CLOSED on this one. :angel:
I have an LG G3 (d855) with working LineageOS. The updater downloads OK and the zip is indeed in /data/data/org.lineageos.updater/app_updates, but TWRP refuses to do anything about it on reboot. I can browse to the folder manually, but it does feel that something isn't firing to get TWRP to perform the install automatically.
What is the trigger for TWRP to install a specific Zip on reboot?
D
For me, One Plus 3, automatic updates don't work. Also manually installing the latest
https://mirrorbits.lineageos.org/full/oneplus3/20170214/lineage-14.1-20170214-nightly-oneplus3-signed.zip gives me an error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Zip file is corrupt!
Updating partition details...
...done
Any idea?
I did a migration via experimental build coming from cm13 then updated to lineage 14, which worked OK.
But since then I cannot update the daily builds.
I have the "same" issue on a Nexus 6.
The updater tells me I have an update, I ok it to download. Once done, I click install, gets into recovery and stops.
Still in the recovery, if I try to manually install from the downloaded location (data/data/...), it says zip failed.
I reboot and try opening that zip on a PC and sure enough, Windows thinks it is corrupt also.
If I re-download manually from "https://download.lineageos.org/shamu" that copy opens fine on the PC and when moved to the phone (data/data/...) installs fine.
There is something corrupting the zip when the updater does its thing. ;-(
Note: This isn't a migration, I have just been updating "nightlies".
Stuck in the TWRP...
Hi everyone, in trouble :/...I have got an LG d802 and updated TWRP from 2.8.7 to 3.0.2-1, then did a boot/system backup of the current cm 13.0 and after that the "experimental" update (as described in the recent update & builds post on lineageos) from cm 13.0 to lineage 14.1 which worked.
I decided to use lineage updater to go to the latest nightly as described which must have failed (booted in TWRP an did nothing...). When installing the 14.1 nightly manually, TWRP 3.0.2-1 showed two error lines with "unknown command".
Since then I'm stuck in TWRP.
Restore of cm 13.0 backup was not possible with neither TWRP 3.0.2-1 nor 2.8.7, no errors, just wouldn't boot. I can't even find any cm 13 build... to try to back which would be an option of course.
I did wipe the system then, lineage expermental + nightly or just nightly can be installed "successfully" with TWRP 3.0.2-1 and 2.8.7 with no errors there anymore, but also the system won't boot.
Please, please help (and/or redirect me to the right thread), what can I do? Thank you!
First, you can ignore the two errors in TWRP
I've gotten them with each update I've installed, but in my case - an LG v410 tablet - I have successfully, if manually, installed three updates so far, with a few peculiarities. "Automatic" is just a nine-letter word concerning updates at this point. I can live with that.
One - it is going to download it to /data/data in the tablet's storage no matter WHAT I do. I can live with that.
Two - I seem to have to download the update at least two times before the Lineage updater accepts the fact that it is there. I can live with that, too.
Three - a "getting there and almost what I want with no major glitches" Nougat build is much preferred to a KitKat build that LG couldn't give a rat's rear end about supporting, and I can DEFINITELY live with that.
But, back to YOUR problem with being stuck in TWRP. Worst case disaster recovery scenario - ANY chance you have a non-Lineage ROM you can revert to and start over from THERE? Realize what a pain that is going to be, but... When I still had CM 12.1 on it, I once did that out of desperation when nothing else seemed to be able to get it to boot. WHY such a laborious process fixed it I have NO IDEA, but better to have a working mystery than a well understood paperweight.
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
nezlek said:
I ASSUME you have respectable backups of your data, etc.. so that loss of TIME is your major issue ?? Also assume you've wiped the caches, etc..?? You COULD try offloading your data, wiping data, and reloading.
It also seems to take a LONG time to reboot after an update. Can I assume you are at least getting to the Lineage animated LOGO screen or are you hanging in TWRP itself?
Click to expand...
Click to collapse
I'm hanging in TWRP, also did wipe data before. I found a full 13.0 backup, selected all but Data because of storage space..."successful"...still system won't boot...
(Power Off in TWRP doesn't even work, just reboots, if that is of any help...)...A wild guess...file system issue maybe?
Yikes
As reasonable a guess as any, I suppose. I admit I've never had TWRP refuse to power off if nothing else, no matter how badly I had screwed things up (often spectacularly) elsewhere.
ASSUME you've tried the hold the power button until it shuts off, after which it should have booted to Android when powered on trick. Or, assuming you can do so, pull the battery?
Perhaps your bootloader is the culprit. Can you just re-flash that?
I got stuck in TWRP Recovery Boot-Loop. Already had the issue before with cm14.1 beginning of december. Didn't they fix the bug or is it another one?
For the specs: I got a Nexus 4 - mako.
I did this FIX and it booted up again as it was before: https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
What's now correct update? Download and dirty install manually in TWRP?
Thanks for the post
:good:
I've NEVER encountered that issue so glad to see someone has figured out a more elegant solution. I suspect your CM 14.1 problem is / was device (build for it) specific, as NONE of my CM / Lineage devices has ever done any such thing and they've all been updated several times in the last month.
In every case, however, I 've had to MANUALLY install the update zip file from within TWRP. Far worse things have happened and since I drive a stick shift car anyway, what the problem?

XT1710-01 Root Guide?

New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
StATicxTW0T said:
New to the Moto Z2 play, moved to this from a Z2 force on Verizon after the shattershield started peeling. Anyway, there seems to be a lot of conflicting information here, and i'm struggling to actually nail down the process for root. My bootloader is already unlocked, however between several different versions of TWRP, Retus based phones vs Albus, ability to unroot and update if the system is modified, rooting with or without disabling encryption, countless different variants with different procedures, etc. i'm a little overwhelmed. Can anyone point me in the right direction of rooting my device (hopefully) WITHOUT losing all my data?
Click to expand...
Click to collapse
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
allstar21369 said:
I'm about to buy the unlocked Moto Z2 Play from the Moto site (64GB variant... not sure of the model number) but have you checked out these threads?...
https://forum.xda-developers.com/showpost.php?p=75098899&postcount=40
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615/page3
Click to expand...
Click to collapse
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I have a rooted XT1710-01, also. If you are going to install Xposed and Gravity Box, I recommend not updating Magisk, above v14. After v15 and now v16, I have had issues with Automate It app and Tasker rules not working, until I uninstalled Xposed.
Downgrading Magisk versions requires flashing your stock ROM and basically starting over.
Motorola has not posted firmware for this model.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
So glad to see someone have it working and with a clear guide. I'm going to buy the phone this week.
StATicxTW0T said:
I did but they involve disabling encryption, which means having to wipe data everytime an update rolls around.
For those that see this in the future, I followed this guide, but used Magisk 13.3 and have working root, without having to wipe my data (bootloader already unlocked) https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792
Click to expand...
Click to collapse
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Johmama said:
I just wanted to let everyone know that the guide posted in that post worked for me perfectly. I had an XT1710-01 that I had unlocked the bootloader before but stopped there. Then I finally wanted to root it, and ran into everything the OP ran into - just so many different guides and versions of TWRP/Magisk not working with the Z2 Play, it was hard to nail down the exact versions of everything I needed and make sure I didn't flash an incompatible version or something. I found that same guide a few days ago as well but never did it until today, and can confirm it works. I already had my bootloader unlocked and just did the rooting portion and all my data was saved (but I wasn't too worried about my data honestly, it's all backed up anyway).
And a special thanks to OP for coming back and posting his solution. Nothing is more frustrating than searching for a problem online, finding a hit on your exact problem in a thread that was posted years ago, and then no solution is ever posted in that thread. So good job. :good:
Click to expand...
Click to collapse
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
allstar21369 said:
I just received my Z2 Play, unlocked the bootloader, and am about to flash the custom TWRP (albus_twrp.img) posted in the guide linked above... but the guide never says to "flash" TWRP, it just says to "boot" with TWRP and also "Enter your FBE password: it must work! (turn off screen and turn it back on if not responsive)"...
I'm not 100% sure what to do here. Should I boot TWRP first, do a full backup and then flash TWRP? I don't want to wipe it.
And what is this FBE (File-Based Encryption) password? I've never set one and don't want everything encrypted.
Click to expand...
Click to collapse
I didn't flash TWRP on my phone. I think I tried it once and it failed for some reason, so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup. Flashing it is up to you, I've always flashed a custom recovery but on this phone I'm keeping the original recovery so I can get an OTA. On my Nexus devices I don't care about OTA because I just flash ROMs all the time so it's no big deal.
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked. As far as turning off encryption, I'm not sure if there's a way to do that. There could be, but to turn it off, it wipes your data as a security measure.
Johmama said:
so I just followed the guide of booting into TWRP, backing up my phone, and pulling the backup. Should be okay for what I need, in case of a failure I will have a backup somewhere and can recover the device. But yes, I'd at least boot into TWRP, then backup your device like in that guide so you have a backup.
Click to expand...
Click to collapse
Yeah, I can't backup my ROM most likely because I don't have an FBE password. When I go to backup my ROM in TWRP it fails.
Johmama said:
The FBE password as far as I can tell is the 4 or 5 digit PIN number you are asked to input upon a fresh wipe of your device to set as a password. I have my phone set up to use my fingerprint to unlock the phone, and if that fails it will ask for my PIN, which is the same as the FBE of mine. I used that same number in TWRP when it asks for a password to unencrypt the data and it worked.
Click to expand...
Click to collapse
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
allstar21369 said:
I tried entering my unlock code and the pin I created but neither worked for my FBE password. I don't ever remember being asked to enter a password when setting up my device. I suppose this means I'll have to wipe data and then setup an FBE password.
Click to expand...
Click to collapse
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Johmama said:
If it helps at all, the first time I tried it also didn't work for me and I did end up wiping my phone for other reasons before I came back and tried that guide again and it worked. I thought I set up the PIN they're talking about the first time around but I did have troubles in TWRP before the first wipe of my data. I would just boot up the phone regularly, plug it in to your computer, and try to grab any files you need and wipe it. I know that isn't the answer you're looking for, but it's all I can give I guess. Once you reset, hopefully they'll prompt you to make a PIN during the setup process and that should be the FBE password. Then follow the guide. I hope you get it man.
Oh, and to a note to you and everyone reading this, I booted to TWRP 3.2.1-0-albus and Magisk-v14.0. Dunno if it's just rumors or not but I heard the newer versions of Magisk might not work with the Z2 Play past version 14. Dunno if that's true but v14.0 worked for me.
Click to expand...
Click to collapse
Okay. I just wiped and re-set up everything and still no FBE password was asked for OR works when I go into TWRP. I'm using TWRP 3.1.1-0... I suppose I'll try it all again using TWRP 3.2.1-0-albus after deleting data.
*Edit: I did exactly what I just said I was doing booted TWRP 3.2.1-0-albus instead of 3.1.1-0 and when I it booted up and asked me for a decryption password I entered the pin I set up previously and it has been stuck at the "Mount, Trying Decryption" screen for a long time... but it's not frozen. It says "Updating partition details... ...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block device: '/dev
/block/dm-0'
Updating partition details...
...done"
And the progress bar/thing at the bottom is still animated like it's working... no forward or back buttons or anything and turning off/on the screen hasn't done anything... not really sure what to do here... I don't want to unplug it and brick my phone or force it off...
*Edit 2:
I now have it all sorted out.
TWRP never finished trying to decrypt data so I long pressed the power button and eventually went here -> https://forum.xda-developers.com/z2-play/development/twrp-moto-z2-play-t3729531 , downloaded "twrp_albus_3.1.2_r18_64.img" and in adb used the command:
fastboot boot twrp_albus_3.1.2_r18_64.img
This TWRP looks a bit different than all of the others but it let me boot up and use my recently created PIN code to actually decrypt my data and make a full backup. After that I just installed Magisk (the latest one, 16.4) as indicated in this guide -> https://gist.github.com/eexit/e6d5fc0984e1c7f25376d3dafa819792 and everything is fine. I never even flashed TWRP, just booted it.
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
joefuf said:
Just curious what you guys have done about getting OTA updates since you've rooted and installed Magisk.
Have @allstar21369 or @pizza_pablo had the chance to figure out the update process?
I'm currently trying to navigate the Magisk uninstall --> OTA update process and could use some insight if either of you guys have any to share.
Click to expand...
Click to collapse
I didn't want updates, especially the oreo "upgrade".
pizza_pablo said:
I didn't want updates, especially the oreo "upgrade".
Click to expand...
Click to collapse
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
joefuf said:
Hmm, didn't even think about just sticking on what works... Did Oreo give people some issues?
Since this was Day 1 with the new phone, I was just trying to get up to speed and probably sit on one version until I had compatibility issues with something, but everything just works.
Click to expand...
Click to collapse
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Double - double \_0_/
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
pizza_pablo said:
Oreo hasn't come to the phone, when I decided I didn't want it, mostly because of the white background in the Quick Settings and I didn't want any of the other "improvements".
With this setup, I accept the risks of not having the security updates.
Click to expand...
Click to collapse
Yeah, very understandable. It really is superfluous to the general experience.
allstar21369 said:
I feel exactly the same way. No benefits for me. I don't want the bright white interface and I would never use the "Picture in Picture" (or floating video) feature (and if I did want that there are a couple apps for Nougat that do it).
But If I do decide I want it and give upgrading a shot I'll definitely post it here.
Click to expand...
Click to collapse
Thank you sir! Keep me posted. I'm posting everywhere right now to learn the new methods so I know if there ever comes a time. This is my first phone since my Motorola Droid 4. Back then it was one click root, install and run Safestrap apk to get custom recovery, boot into custom recovery and flash zips to your heart's content. I'm sure this will be as "simple" once I learn, but it's pretty daunting in prospect.

[Q] Fingerprint not working on mate se after feb update

I have a mate SE (BND-L34) that was on 8.0. Back in September of 2018, I unlocked it and rooted using another thread in this forum. All was working fine until a few days ago when I tried to install xposed using magisk. That bricked the phone. TWRP came up but boot looped. Finally got to the point where my only option was to let it download a stock image through wifi. I did, and then it had a couple updates available, and I let it update to build number BND-L34 8.0.0.352(C567). It also shows android security patch of February 1, 2019. That took the phone back to completely stock. All data wiped, no unlocked warning at bootup.
correction: At bootup, it does still give me the unlocked warning.
So anyway, All seemed to be working and I could add fingers to the list and they will unlock the phone fine. Then I installed an app that could use the fingerprint to unlock it, and I found that it did not work at all. The app waits for the fingerprint to be detected and it never happens. So I tried a different app, and same thing, just waits for the detect to happen. Again, the finger print unlocks the phone without hesitation, every time.
This makes me think that one of the updates is causing a problem. I've done some searching both on xda and google, and come up with nothing. Like no one else has seen this problem.
So I have a few questions:
1) Has anyone else seen this problem?
2) Can I use firmware finder to install a previous build, like the one from January or even the one from September? I don't have TWRP or root, just the stock image.
3) If I can't use firmware finder to downgrade, is there another way? Like through adb or something.
update:
Here's the answer to questions 2 & 3 above:
I was able to use firmware finder to download the January build .351. I couldn't get firmware finder to flash it. I then installed twrp into recovery using the image I found here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500. I followed the steps in this post https://forum.xda-developers.com/honor-7x/how-to/tested-unbrick-bnd-l24-t3811645 to flash the .351 image. I just used the files I downloaded from firmware finder instead of the ones list there.
And since no one has replied, I'm guessing that this problem is mine alone. Also, going back to 8.0.0.351 did not solve the problem.
I finally rolled all the way back to 8.0.0.344(C567) (first Oreo, I think, from September) and now the fingerprint sensor works for applications. I have no idea why. Maybe there was a security update in the Jan build that disabled the fingerprint if the phone was unlocked. But it seems unlikely since no one else saw the same problem. I can't be the only person with an unlocked BND-L34 that let the phone update to the latest ota.
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Delete
electric bill said:
So I have another question: is there any way to stop the phone from looking for ota updates? It's damn annoying to have that "update available" thing pop up every day.
Click to expand...
Click to collapse
Yeah, I posted the same thing a month or so ago and ended up figuring it out. Since you are rooted, the same solution I used will work for you. Froze the EMUI System Update process with Titanium Backup.
https://forum.xda-developers.com/hon...ation-t3897144
Welp
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
electric bill said:
It was working, then I tried to install magisk, but it wouldn't install with twrpimgmount_ramdisk.img so I flashed twrp_p10_lite_0.4.img and then magisk 18.1. After that, fingerprint stopped working for apps . I tried re-flashing 344 build, factory resets, different twrp versions, running the magisk uninstall zip, I even re-locked the bootloader. No dice. This phone is back to stock now just the way I got it, no mods, no twrp, no root, and it still has a problem. I just can't figure it out. I think I'm done.
I really liked the phone. It has great features for a $200 phone. I could still use it without the fingerprint password feature, but I really liked that... alot. I certainly have the root procedure down.... I might buy another one and try again, or I might look for something else in that price range and say fu huawei.
Click to expand...
Click to collapse
it's a problem with the app. If I restore an older version with titanium, it works fine.
Hi, I unlocked my mate SE boot-loader and rooted it. After upgrading to BND-L34 8.0.0.352, My TWRP disappeared and lost root. I tried used fastboot to reflash TWRP and failed. Could you confirm if your TWRP worked on version 352? Even I reverted my rom back to 344 using "Firmware finder", I still could not install custom any recovery. Could you help?

[HELP] WiFi keeps disconnecting and reconnecting

My XT1795 is on stock 8.1 with unlocked BL, TWRP and magisk (I haven't installed any modules though). I am facing this weird issue since an year, the WiFi randomly keeps disconnecting and reconnecting automatically every 10 to 15 mins. I am sure that it has nothing to do with my WiFi router as I face the same issue when I am connected to mobile hotspots or any public or private network. I tried resetting the wifi and network settings, restored the device quite a few times, and also reflashed the stock rom but the problem still exists. The most recently that I reflashed the stock rom was a month ago, i didn't face any issue for the first 15 days but now it's back again.
Can someone please help me?
Try using a different kernel. But make sure that stock 8.1 is supported
Some random said:
Try using a different kernel. But make sure that stock 8.1 is supported
Click to expand...
Click to collapse
Yeah but I don't understand the reason behind this problem..
rizwan.mahai said:
Yeah but I don't understand the reason behind this problem..
Click to expand...
Click to collapse
You have root right? Try taking some logs until WiFi crashes. Then wait a couple of seconds before stopping log recording. I will try to look into it.
Some random said:
You have root right? Try taking some logs until WiFi crashes. Then wait a couple of seconds before stopping log recording. I will try to look into it.
Click to expand...
Click to collapse
View attachment alogcat.2020-03-30-11-09-20+0530.txt
Please have a look at the logcat, this morning while generating this log the wifi network ([email protected]) disconnected and reconnected atleast 3 times. Even after the reconnection, most of times I am not able to access the internet, I have enable airplane mode, then enable the wifi again or reboot the device. I am sure there is no problem with my router because, I face the same issue when ever I connect to any network be it a mobile hotspot or railway public network.
 @lohanbarth @vaserbanix @kalyansundhar
As far as I have seen this is what's concerning:
1
E/WifiVendorHal( 2001): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = }
Some vendor realted stuff is just gone.
2
W/WifiConfigManager( 2001): Looking up network with invalid networkId -1
The NetworkID (probably which decides which network it tries to connect to) is ****ed
3
E/wpa_supplicant( 3589): wpa_driver_nl80211_driver_cmd: failed to set RXFILTER option I/QCNEJ/CndHalConnector( 2569): -> SND notifyRatConnectionStatusChanged(rat = 1, DISCONNECTED)
Yeah I think drivers are just ****ed
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Some random said:
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Click to expand...
Click to collapse
This problem started after I unbricked my phone few months ago. I flashed an older version of bootloader on my XT1795 which lead to a complete breakdown, the phone was unable to boot, I had to flash mmcblk0.tar and this rom on a 32GB sd card and booted from it so as to flash a new stock rom on the int storage. After all those efforts the phone booted up but I started having this WiFi issue.
I'll try installing lineage OS because , I have tried reinstalling stock 2 times and even factory reset-ed the device. Thanks alot for responding.
Edit : I have flashed the LineageOS 15.1, will update if the problem persists.
rizwan.mahai said:
This problem started after I unbricked my phone few months ago. I flashed an older version of bootloader on my XT1795 which lead to a complete breakdown, the phone was unable to boot, I had to flash mmcblk0.tar and this rom on a 32GB sd card and booted from it so as to flash a new stock rom on the int storage. After all those efforts the phone booted up but I started having this WiFi issue.
I'll try installing lineage OS because , I have tried reinstalling stock 2 times and even factory reset-ed the device. Thanks alot for responding.
Edit : I have flashed the LineageOS 15.1, will update if the problem persists.
Click to expand...
Click to collapse
The problem is still there on Lineage 15.1.
Lineage 15.1 Logcat
Some random said:
As far as I have seen this is what's concerning:
1
E/WifiVendorHal( 2001): stopRssiMonitoring(l.2156) failed {.code = ERROR_NOT_AVAILABLE, .description = }
Some vendor realted stuff is just gone.
2
W/WifiConfigManager( 2001): Looking up network with invalid networkId -1
The NetworkID (probably which decides which network it tries to connect to) is ****ed
3
E/wpa_supplicant( 3589): wpa_driver_nl80211_driver_cmd: failed to set RXFILTER option I/QCNEJ/CndHalConnector( 2569): -> SND notifyRatConnectionStatusChanged(rat = 1, DISCONNECTED)
Yeah I think drivers are just ****ed
I would personally suggest 2 things
1. Install lineage 15.1
2. Re-install stock
Alternatively to 2:
Factory reset, could fail though due to magisk and force-encrypt
Click to expand...
Click to collapse
The wifi drops are more severe on lineage 15.1. Most of the times there's no internet access even while wifi is connected. Please have a look at the new logcat file.
View attachment logcat_lineage.04-01-2020_10-57-24.rar
I am being forced now to roll back to the stock rom from twrp backup.
When it is like that even on lineage, try downgrading to nougat and see if the error persists, I also have this problem now btw... I'm on Android 9 though
If the error doesn't persist, upgrade back to Oreo. And see if it's fixed, if not, then I'll have to try around a little bit by myself
Also, me being on Android P with Radium, it isn't really a kernel issue.
I just cant decide what it is,
Also, don't use the "stable" build advertised pretty recently in jarl's lineage 16 thread, it isn't stable
(Bruh)
I will try downgrading to Oreo and see if the error persists for me.
Some random said:
When it is like that even on lineage, try downgrading to nougat and see if the error persists, I also have this problem now btw... I'm on Android 9 though
If the error doesn't persist, upgrade back to Oreo. And see if it's fixed, if not, then I'll have to try around a little bit by myself
Also, me being on Android P with Radium, it isn't really a kernel issue.
I just cant decide what it is,
Also, don't use the "stable" build advertised pretty recently in jarl's lineage 16 thread, it isn't stable
(Bruh)
I will try downgrading to Oreo and see if the error persists for me.
Click to expand...
Click to collapse
1.
Now I flashed stock 8.1 (fresh flash) on the lineage 15.1. The wifi problem is still there. Like you said, the last way could be downgrading to Android Nougat but I am scared it could hard brick the device. Why I am saying this is I did a downgrade 7-8 months ago, which bricked the phone and led me to Blank Flash 7.1 srock rom to finally make it boot, it was then this wifi issues started. It was a disaster, later I came to know that downgrading bootloader from from a new version of rom to an older version will mostly end up in dead devices. :highfive:
2.
So do you still think I need try downgrading once again ?
3.
I am fed of this phone now, I was planning to get a new one but everything in India is locked down till 15th April. I only have this flashing time till that date, from 16th (could be even 10th) I have to attend office.
rizwan.mahai said:
1.
Now I flashed stock 8.1 (fresh flash) on the lineage 15.1. The wifi problem is still there. Like you said, the last way could be downgrading to Android Nougat but I am scared it could hard brick the device. Why I am saying this is I did a downgrade 7-8 months ago, which bricked the phone and led me to Blank Flash 7.1 srock rom to finally make it boot, it was then this wifi issues started. It was a disaster, later I came to know that downgrading bootloader from from a new version of rom to an older version will mostly end up in dead devices. :highfive:
2.
So do you still think I need try downgrading once again ?
3.
I am fed of this phone now, I was planning to get a new one but everything in India is locked down till 15th April. I only have this flashing time till that date, from 16th (could be even 10th) I have to attend office.
Click to expand...
Click to collapse
We have one last resort,
G. S. I
If that doesn't work, then it's due to isp's being overloaded from all the streaming which is happening.
For me, it started when testing an "stable" (*cough cough* it isn't *cough cough*)
Lineage update
Install latest , non wiktor build of lineage 16.0 builddate
20200208
Or the gsi "optimized" 2019070X build
And then installing a pie (or Q) GSI of choice
Some random said:
We have one last resort,
G. S. I
If that doesn't work, then it's due to isp's being overloaded from all the streaming which is happening.
For me, it started when testing an "stable" (*cough cough* it isn't *cough cough*)
Lineage update
Install latest , non wiktor build of lineage 16.0 builddate
20200208
Or the gsi "optimized" 2019070X build
And then installing a pie (or Q) GSI of choice
Click to expand...
Click to collapse
What is GSI ?
rizwan.mahai said:
What is GSI ?
Click to expand...
Click to collapse
Generic system image,
An effort by Google to streamline system updates, the project itself is called
Project Treble
Jarlpenguins lineage 16 (and only those)
Support android pie gsi .IMG files for installation
Some random said:
Generic system image,
An effort by Google to streamline system updates, the project itself is called
Project Treble
Jarlpenguins lineage 16 (and only those)
Support android pie gsi .IMG files for installation
Click to expand...
Click to collapse
Please try to run this command in terminal emulator, while wifi is on.
Code:
su
killall wpa_supplicant
This will kill all the active connections and reconnect to current network, I read on linux foums that this fixed the wifi issue at least temporarily.
rizwan.mahai said:
Please try to run this command in terminal emulator, while wifi is on.
This will kill all the active connections and reconnect to current network, I read on linux foums that this fixed the wifi issue at least temporarily.
Click to expand...
Click to collapse
Okay okay. I got the.. ahem... "Fix" for the issue.
Basically, when reinstalling almost everything (except firmware)
It just fixed itself? I dont know how it just did.
Try reinstalling Lineage 15.1 or 16 (jarl's builds, wiktors cause more problems aka Lineage 16.0 v0.16 instead of 0.17)
And then installing a GSI of choice. If you didnt look that up yet, basically, you know how on a PC, no matter the hardware, you can install windows on it without device specific ****? Yeah that's project treble, allowing installation of updates and ROMs using .img files.
Luckily, our Lineage 16.0 builds (and only those) have full support for treble, so, just download a rom of choice, RR for example, extract it using an application like RAR and then wipe ONLY
/System & /Data NOT FORMAT
Wipe>advanced wipe> select system and data
This won't erase Internal storage just uninstall all apps and stuff
And then head to where you extracted the .img file and select "flash zip" in the bottom right corner
It should now switch to: "install Image"
And the extracted file should show up.
Select it, select "system image" and flash
Don't worry about it saying: " NO OS INSTALLED" And blah blah blah. The phone will take care of it, unless it crashes, then the rom isn't compatible with our specific device.
Some random said:
Okay okay. I got the.. ahem... "Fix" for the issue.
Basically, when reinstalling almost everything (except firmware)
It just fixed itself? I dont know how it just did.
Try reinstalling Lineage 15.1 or 16 (jarl's builds, wiktors cause more problems aka Lineage 16.0 v0.16 instead of 0.17)
And then installing a GSI of choice. If you didnt look that up yet, basically, you know how on a PC, no matter the hardware, you can install windows on it without device specific ****? Yeah that's project treble, allowing installation of updates and ROMs using .img files.
Luckily, our Lineage 16.0 builds (and only those) have full support for treble, so, just download a rom of choice, RR for example, extract it using an application like RAR and then wipe ONLY
/System & /Data NOT FORMAT
Wipe>advanced wipe> select system and data
This won't erase Internal storage just uninstall all apps and stuff
And then head to where you extracted the .img file and select "flash zip" in the bottom right corner
It should now switch to: "install Image"
And the extracted file should show up.
Select it, select "system image" and flash
Don't worry about it saying: " NO OS INSTALLED" And blah blah blah. The phone will take care of it, unless it crashes, then the rom isn't compatible with our specific device.
Click to expand...
Click to collapse
Thanks. I'll give it a try.
rizwan.mahai said:
Thanks. I'll give it a try.
Click to expand...
Click to collapse
If the launcher for example is lagging, try adding this line
Sys.use.fifo_ui=1
Into build.prop and rebooting, maybe that makes it better

Categories

Resources