Related
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.
Hi guys,
I'm having trouble with my A2 Lite. Right after unboxing the phone I installed Magisk as described in the guide (https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-device-t3825626), which worked like a charm. Today, I wanted to install a OTA security update. After the update was downloaded I got an error and I remembered that I had to "uninstall" Magisk, as described in "step a" of the guide. So I did exactly as described in the guide. After Magisk was "uninstalled" I closed the app and tried again to install the OTA security ("step b") update. Unfortunately I got the same error message again ("Can't install update"). So I thought f*** it - I skipped "step b" and proceeded to "step c" and installed Magisk into an empty slot. After that I hit "reboot" and now my phone's in a bootloop :-/
bootloader is unlocked, oem unlock and debug usb are activated. I'm able to enter fastboot, but no recovery, whatsoever.
Is there any way to fix this?
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
lunatikk said:
just letting you guys know that "fastboot set_active b" did the trick. I don't know what the hell went wrong though. I did everything according to the guide, except for trying to update the ota update (and failing) before uninstalling Magisk.
Now, the phone is booting correctly, but I still can't install the ota update. it says "Couldn't update" and "Installation problem". What the heck...
Click to expand...
Click to collapse
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
fake__knv said:
This is probably due to the root as it modified the system partition. Check the thread regarding on how to update without losing root.
Click to expand...
Click to collapse
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
lunatikk said:
Could you explain further? Will flashing the stock boot.img fix the issue and will I lose all data on the phone after flashing the boot.img?
thanks
Click to expand...
Click to collapse
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
lunatikk said:
Hi BubuXP
I followed your troubleshooting guide and flashed the boot.img as instructed. Flashing the boot.img didn't do the trick so I continued with flashing the system.img. I checked for the correct build no. of course and for both boot.img and system.img the active slot "b" was chosen. After flashing the system.img I got stuck at a bootloop. I tried to set the active slot to "a", but that didn't help either: Now it wasn't in a bootloop anymore, but it was stuck at the boot animation (horizontal beam) loading forever. After 10 minutes I tried to restart - still the same problem.
What's going on here??
edit:
I flashed daisy_global_images_V9.6.4.0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2 using MiFlash and the "Save user data" option. It was flashed successfully. However, when I start the phone it askes for a password and won't boot up into android if not entered. What the hell...? I deactivated my screenlock pin before I started all this. Is there a default password or what's the problem here?
regards
Click to expand...
Click to collapse
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
BubuXP said:
Sorry, but I don't know anything about that. It's an encryption problem, and that's why I hate data encryption on the phone: my data is not so important to be protected when some hackers physically stole my phone, it's only a nuisance when things like this happens.
I can only suggest to change the active slot, maybe with this you can resolve.
I will also update my troubleshooting section of the rooting guide to make the data backup as the first option to be safe.
If you can sacrifice the data, you can simply format the data partition via fastboot or reflash using the flash_all.bat script.
Click to expand...
Click to collapse
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
lunatikk said:
I also thought that it had something to do with encryption. In the security menu, where I turned off the display lock, it said that the phone is encrypted. However neither pin nor fingerprint could unlock the phone.
I had to go for ultima ratio and flash my device with the newest fastboot image and miflash (save user data option didn't work either, btw.).
I lost all data on the device, but now everything works fine and the OTA update also ran through without any issues.
Now, I'm not sure if I will fiddle with magisk again. I really don't have no clue about what went wrong at all...
Thanks
Click to expand...
Click to collapse
Thanks for sharing.
Maybe something to try for next time to restore data, I don't know.
I haven't tested yet but I did make a backup using the method explained here
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I have yet to try (or need) the restore function but running that backup created a 6gb file. My understanding is this is the majority of your apps, data, messages, etc
Without twrp I was hesitant to root but with the bit of knowledge and files shared here so far I have moved forward and glad I did. I haven't had to flash the stock image yet but hopefully this backup helps ease the pain. It is nice to be able to modify at will
BubuXP said:
Please go see my guide, I just added a troubleshooting section that you should check:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Your feedback could improve it further.
No, flashing boot.img will not erase any data on the phone. But you must remove any PIN, password or screenlock before proceeding, or you could not access your data anymore (because of encryption).
Click to expand...
Click to collapse
Had the same problem. I tried to install the OTA of March, followed the guide to install OTA with Magisk, but after unistalling Magisk, i tried to install the OTA but it gave me this message "installazione riprenderà automaticamente quanto il dispositivo non sarà attivo";
I looked for some help online, but didn't find anything, so skipped to the point c, and i got this bootloop now.
I tried the "set_active b" command, but I'm still in bootloop. I tried to flash the stock rom but apparentrly it's impossible to do it without recovery (which I'm unable to open), so... Help?
EDIT: By using miFlash and using the flash_all command I flashed the most updated ROM I found on MIUI.en, which is the january's one. It worked, even if the build version (10.0.3) is different from the one I had previously (10.0.4). The system says that there's an available update, but i'm too afraid to try it. Suggestion are accepted!
Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.
is it worth factory resetting device with this latest update?
Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.
jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.
bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?
animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
fil3s said:
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Directly through the phone's regular system update.
WHOneedsSOX said:
Directly through the phone's regular system update.
Click to expand...
Click to collapse
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
fil3s said:
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
Click to expand...
Click to collapse
That's correct, it isn't unlocked.
RetroTech07 said:
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
Click to expand...
Click to collapse
I have done absolutely no modifications other than typical downloading of apps and modifying through there but even that is just theming. By "try again," just wipe and then reinstall the update?
WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Morgrain said:
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
Click to expand...
Click to collapse
I'd be happy with 2 random reboots per day. Not even kidding, I must be at 100 a day. It's super random too. None from 9 am until around 1pm and then all of a sudden 10 in a row.
I'm pretty sure it's a software issue, had no random reboots before I installed the February update. Will probably try reformatting the entire phone first and see how that goes.
DanielF50 said:
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Click to expand...
Click to collapse
Thanks, will try this out if a reformat doesn't work.
Try safe mode and see if it still happens.
neyes said:
Try safe mode and see if it still happens.
Click to expand...
Click to collapse
Still happened in safe mode.
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
RetroTech07 said:
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
Click to expand...
Click to collapse
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
WHOneedsSOX said:
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
Click to expand...
Click to collapse
Official Google Android Flash Tool
roirraW edor ehT said:
Official Google Android Flash Tool
Click to expand...
Click to collapse
Thanks!
Successfully updated to F.15 (without loosing data or root). Only thing that's not working properly is fingerprint reader; gets it right around 1/10 tries... obviously already tried deleting prints and re-enrolling. Any suggestions?
ystokar said:
Successfully updated to F.15 (without loosing data or root). Only thing that's not working properly is fingerprint reader; gets it right around 1/10 tries... obviously already tried deleting prints and re-enrolling. Any suggestions?
Click to expand...
Click to collapse
Back up data then reset phone
HueyT said:
Back up data then reset phone
Click to expand...
Click to collapse
Thanks. What's the easiest way to backup data? I don't have a custom recovery
HueyT said:
Back up data then reset phone
Click to expand...
Click to collapse
it seems to be solved after flashing latest safetynet-fix