Factory Reset Protection locked me out! Help! - Lenovo ZUK Z2 (Plus) Questions & Answers

Hello all,
I had a nightly build of Nougat RR on my Zuk Z2 and it was giving me problems. I decided to go to AOSP Extended Oreo. I had a really long randomly generated password for my Google account, and I also had 2FA. I changed the password to something I can easily type and disabled 2FA. I didn't realize this was a no-no and would trigger FRP.
I flashed TWRP 3.2.1 (for Oreo support) and flashed 1.7 Baseband Modem with ADB.
I booted into TWRP and wiped everything. I had backed up the important files; I wanted to start from scratch. I pushed the AEX ROM and GApps using ADB and flashed it using TWRP.
The first bootup took a while, which was expected. It began the initial setup; and told me: "This device was reset to continue, sign in with a Google account previously synced on this device". So I signed in, but it kicked me back out saying "Please sign in using one of the owners accounts for this device." But that is the account that was on the device!
I did a bit of googling, and discovered if I reset the password it would trigger a 24 (or 72) hour lockout for theft prevention. I waited over 72hours and it is giving me the same error, no luck.
On my Google devices page, it tells me an Android phone was last synced.
The phone seems to work beautifully, but I can't get in! Can someone please help?
Many thanks,

Don't flash gapps yet

raz0rev said:
Don't flash gapps yet
Click to expand...
Click to collapse
Thank you for the response! So I should do another wipe using TWRP and only flash AEX? That should let me through? Then when do I flash gapps? I'll give that a shot tonight. I really don't wanna buy a new phone, the Z2 is still so nice.

You Solved?
I'm in the same situation and don't know how to solve it!

paolomatador said:
You Solved?
I'm in the same situation and don't know how to solve it!
Click to expand...
Click to collapse
Flash only ROM then reboot device, once boot up use it for a while then reboot to recovery flash gapps reboot.
Hope it helps

Yes, I did it and it solved. Great!!
Thanks

Related

Installed Viper, Now Locked Out of Phone

I flashed Viper, now in the initial setup I am presented with this message:
"This device was reset. To continue, sign in with a Google Account that was previously synced on this device."
I enter my credentials, and it brings me back to the same prompt. It is in an endless loop and I can't get into my device. What do I do now?
Edit: Tried using the "Forgot password" link using the HTC 10, reset a new password, still having same issue.
Edit 2: I reset my Google account password last night. Today I flashed Viper, which is equivalent to a device reset. I just read this: "The moment your Google account password is changed, Device Protection starts a 72-hour timer on your protected device. For that 72 hours, if the device is wiped, the account in question cannot be used to sign into / unlock the phone." So am I on this 3-day lockout? Did the timer restart when I reset my password again today trying to get into the device? Really pissed right now.
If your bootloader is locked and you're S-ON then I don't think you have any recourse besides waiting the 3 days.
If you're unlocked / S-OFF then you should be able to wipe/format in TWRP, reinstall ViperROM and be good to go, but I've never run into this situation personally so I can't be sure.
The 72hr lock begins whenever you change your password so don't change it again.
drumz0rz said:
If your bootloader is locked and you're S-ON then I don't think you have any recourse besides waiting the 3 days.
If you're unlocked / S-OFF then you should be able to wipe/format in TWRP, reinstall ViperROM and be good to go, but I've never run into this situation personally so I can't be sure.
The 72hr lock begins whenever you change your password so don't change it again.
Click to expand...
Click to collapse
Thanks for the reply! From everything I've read, there's no way to clear out whatever identifying information is in the phone that ties it to a Google account. I'm unlocked and S-OFF, so I'll give it a shot if I get time tonight. Anyone else had any experience with this?
Flash RUU to get back to stock if one is available for your device.
yldlj said:
Flash RUU to get back to stock if one is available for your device.
Click to expand...
Click to collapse
Flashed stock RUU, was able to get back into device using my Google account. I think I might have done something wrong when flashing RUU, though, I'm getting lots of FCs. Anyway, I unlinked my Google account from the phone, should I be OK to go back to Viper now?
All is well after flashing stock RUU, removing Google account from the phone, reflashing TWRP and Viper. Thanks!
Glad you're back in business. Make sure you do a full wipe before flashing a RUU, that should clear out anything from the previous install. I think Viper's Aroma installer does it for you which could be why you don't have the same FC issues now. Just FYI.

Lineage/CyanogenMod requires password on boot

Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.

Factory reset problems

So my Swift was struggling to run and kept rebooting on me- I downloaded an app for pokemon go I probably should not have. What i decided after a week of frustration, was to do a factory reset of the phone. But now my phone wont let me finish the install- it lets me get as far as setting up a Cyanogen account, but whatever I do it tells me there is a 'communication error' with the server, suggests changing the WiFi connection and check my SIM us properly installed. It will not let me go past that screen. Ive tried rebooting in recovery, setting up a new cyanogen account and popping in an old sim. nothing but the same message.
I never did anything fancy with the phone. It has been running the stock ROM and was up to date with the software. Im out of ideas, and am looking for any other suggestions.
Anything at all would be awesome. I dont know what information I can give that might help you, but if you need something ask.
Thanks
First thoughts would be that cyanogen are history so setting up a cyanogen account sounds potentially problematic.
Are you not able to skip the account setup? I can't remember.
What version COS is installed?
M.A.K said:
First thoughts would be that cyanogen are history so setting up a cyanogen account sounds potentially problematic.
Are you not able to skip the account setup? I can't remember.
What version COS is installed?
Click to expand...
Click to collapse
Ya... That would explain some things. So now i cant even log into my old account?
Nope.... it does not give me that option.
And when check in fastboot mode, it says the LK version is : Crackling-13-ge86e772.
And both the OEM unlocked and security fuse is set to false.
As it's unlocked, you at least have the option of installing another rom. And we'll have a new rom coming from wileyfox soon, too.
So if i download a compatible rom and install that, it should be okay? Considering my device is unrooted, I didnt think that was an option. Sorry about this...
Yes. As you've already done a factory reset you don't have to worry about your data being compatible.
It may be worth trying to flash the latest COS first just in case something has somehow been corrupted. But failing that, install TWRP and try LineageOS or crDroid.
awesome!! I will give that a go. Thanks so much

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.

Resurrection Remix "Android setup" fails (RR8.1.0)

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

Categories

Resources