will this keep the phone rooted like it does ever.
to flash the full image and root again is not very easy for me
It seems that no one is gonna take a try, I will and revert.
Just finished upgrading via flash fire. It worked
What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?
V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
sliding_billy said:
What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?
Click to expand...
Click to collapse
bush911 said:
V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
Click to expand...
Click to collapse
Thanks for investigating. I would have thought you would flash the OTA. Doesn't seem to improve the process if recovery is removed but root isn't.
I did. Didn't work. Downloaded OTA. Flashfire kicked in (I'm using FlashFire Pro v0.55.1). It appeared to process the OTA. I flashed. OTA was not successful. I re-flashed SuperSU to restore root.
Flashfire works great
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.
I just retook the 7.1.2 OTA but did not restart after download. Opened FlashFire it autodetected the OTA, offered to install and I accepted. Everything went fine. Still have Su and on Sharkey kernal
josephpalozzi said:
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.
Click to expand...
Click to collapse
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
edit: I was able to update to the Feb security patch, but lost twrp in the process. I tried the steps above again, this time I was presented with the ota available pop up screen which I didnt get the first time around. Even with the "preserve recovery" option ticked, it didnt preserve it. I get "no command" when I try to boot into recovery.
Just used TWRP sideload, TWRP IMG, TWRP install and SuperSU install to update XL to February. About to do Pixel. I've got FashFire installed and waiting until it is working in a more stable fashion. No point in fixing what ain't broke for me right now.
llong31 said:
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
Click to expand...
Click to collapse
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today
mac796 said:
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today
Click to expand...
Click to collapse
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse
mac796 said:
llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse
llong31 said:
mac796 said:
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse
Maybe I'll try the auto detect see if that helps, in not sure if L speed does. I think most stuff for pixel is systemless
Click to expand...
Click to collapse
Sorry to bump this old thread...how long were ya'll phones 'black' during Flashfire? Mine has been black (but still connected to storage via PC so it's not dead) for like 25 min.
EDIT: After almost an hour, I gave up. I force rebooted the phone hoping Flashfire didn't do anything and it looks like it didn't. Phone booted fine. Going to use the old method and sideload the OTA.
I've used the OTA file from the typical update with FlashFire the past couple months, and I used a file downloaded from Google once before (I don't remember if it was on the phone or a flash drive). The screen didn't stay black very long the times I've used it, I'd guess less than a minute, so apparently something didn't work correctly. Looking through the app and documentation, I'm not sure what you meant by "still connected to storage via PC".
Related
Hi, I rooted my a9 back in May right around when 6.0.1 came out. Long story short, my device just gave up the ghost after a nasty interaction between the screen and concrete, so now I have a new device being shipped tomorrow. I figured the first thing I'll do is let it run any updates / OTAs it might have to get it up to date then attempt to root again.
I've been looking around for the past several hours trying to determine what the correct rooting method might be now given Nougat's rollout, but I haven't come across anything truly definitive yet. If anyone could enlighten me on what I'll need to do now to root this new version I'd be very appreciative.
Thanks in advance guys!
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
txag2011 said:
Just got the phone today and updated to 7.0 (software version 2.18.651.2) Still searching around and not seeing a definitive answer on whether or not the old method for rooting works for this or not. I'm hesitant to attempt it without knowing, so any advice would be greatly appreciated.
Last time I rooted, I used Windroid toolkid to unlock the bootloader, flash TWRP and apply SU. I'm wondering, would the same program work if I replaced the recovery.img file in the Data folder with the TWRP 3.0.3 unofficial recovery I saw floating around in here for nougat?
Click to expand...
Click to collapse
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
JohnRogers23 said:
You can unlock it on the HTCDEV website, although if you've already got it unlocked I doubt you need to do it again. To root I just ADB fastboot flashed TWRP 3.0.3-4, then used that to flash Magisk, mounting system read only. I'm fairly sure some people are using Su on Nougat, so it'll probably work.
Never used the Windroid toolkit so I can't comment on that, but I've also never minded typing commands to the prompt. I'd imagine if you gave it the right TWRP it'd flash it OK..
Click to expand...
Click to collapse
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
I'm about to start the process trying to root using the above methods.. I'll post again when I have results.
txag2011 said:
That actually doesn't sound too bad; From that it seems like the process is still more or less the same. Why is the system mounted as read only though? After looking through most of the older step by step guides it doesn't mention anything about doing that. From what I see, after i run the command "fastboot flash recovery recovery.img" i boot into TWRP and then proceed to do a factory reset and wipe the cache, presumably to remove the encryption iirc, then install the supersu.zip is that still the correct procedure, or does this require mounting the system as read only now?
If you don't mind me asking, what steps exactly did you take to root yours? from what I've found all I need to do is get the bootloader unlocked with the steps from HTCDev, drop into download more, fastboot flash recovery recovery.img to get TWRP, boot into TWRP, run a format to get rid of the encryption, then install supersu.zip and that should be it. IS this correct or am I missing something?
Click to expand...
Click to collapse
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
JohnRogers23 said:
It wasn't bad at all. The reason I mounted R/O is because I'm using Magisk and not disabling dm-verity. I'm not sure if it works the same on 7, but SuperSu should disable dm-verity, so if you're using it you might not need to mount R/O, I haven't been keeping up on that at all. Benefits of Magisk include Android Pay and being able to take an OTA.
That all sounds like exactly what you need to do, except I believe it's fastboot mode (the one with the black screen?) to flash TWRP. I also didn't have to format anything, but I believe you do if you're using Su and disabling forced encryption. You may want to take a system image backup before you change anything, so you can go back to stock and get an OTA, or in case something goes wrong, but other than that it sounds correct to me.
Click to expand...
Click to collapse
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
txag2011 said:
huh... Magisk can utilize android pay and OTA's? I'm a little bit intrigued.. I just might have to give that a quick look now. Was it difficult to get up and running, and is there a fairly decent guide for doing it?
Click to expand...
Click to collapse
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
JohnRogers23 said:
Magisk is a framework for systemlessly modifying /system, so safety net works and you can take an OTA (with stock recovery), and also includes root. It's brilliant, but not quite as powerful as Xposed. Not difficult at all to get running, all it needs is to flash the magisk installer zip in TWRP (system mounted R/O of course) and then install the Magisk Manager app from the play store.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
txag2011 said:
I might give this a shot then, thank you for that. I'm about to try flashing TWRP 3.0.3-0. From the looks of it this is the most current one available. I'll update when it's done
Click to expand...
Click to collapse
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
JohnRogers23 said:
Go to the TWRP thread, hit the download tab, pick one of the newer ones there. I went with 3.0.3.-4.
Click to expand...
Click to collapse
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
txag2011 said:
Did just that. Got TWRP installed successfully. I PM'ed you a second ago but I might as well ask this here for everyone else to see in case someone else is wondering this too.... So if I'm understanding Magisk correctly, all I do now is hit install and choose Magisk v11.1?
Edit: I did just that, but it doesnt seem to have done anything.. I dont see and magisk apps, and root checker says i'm not rooted.. Did I miss something?
edit 2: scratch that... I just installed the magisk manager app from the playstore.. according to it, the latest version of magisk is in fact, installed, and it's rooted with magisksu (despite not showing so in rootchecker).. Little confused now. Is that everything that needs to be done?
edit 3: I went back in after seeing something mentioning installing phh's superuser via TWRP and installing the app after installing magisk. Did both, but noticed safety net wasn't passing. found an option in settings to hide magisk, which seems to fix that. I also ran root checker again and it shows I have root.
unless I missed anything you can think of I think that about finishes things. If thats it thank you for all the help @JohnRogers23
Click to expand...
Click to collapse
I'm glad you got it working. Strange you had to flash phh's Su separately though. Anyway, glad I could help.
Well Working !
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Dr.Anshuman said:
1.Backup your all imp data from internal memory
2.Flash TWRP 3.0.3-4.. Do not reboot into system and enter into Recovery TWRP..
3.Do a factory Reset via TWRP.. Do not reboot into system
4.Now flash SuperSU 2.79 SR3 via TWRP.. Finally Reboot into system..
*2 bootloops are common, do not give up for at least 3 bootloops..
*It will take a long time to boot as you have done a factory reset.. So be patient and wait for at least half hour..
Click to expand...
Click to collapse
Thanks! I got it more or less and went with magisk. Couldn't pass up a chance to have root and still get OTAs and use android pay. I'm still monkeying around trying to figure out how to use it to get liveboot back up and running.
Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what
Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.
I always get Failed to udate, try again when installing the ota via settings.
Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't flash it. I just want root.
kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha
I'm at my wit's end here. I know I'm probably missing some critical step, but I haven't been able to install any OTAs since installing TWRP and Magisk. Fortunately, I was able to update to the latest TWRP before trying (the one that has working decryption) and backup Boot, the two Systems, and Data. I cannot stress enough how important this is!.
The OTA installer detects the device is rooted (or unlocked, if magisk isn't installed) and downloads the OTA. It then asks to install (which is does while booted to system, presumably to the side (A or B) that isn't updated), and asks to reboot. After reboot, the system fails to boot, then goes to the original OnePlus recovery (with the Chinese characters).
I seem to remember reading somewhere that I needed to shut the phone down instead of rebooting, but that doesn't seem to help. I want to know the correct procedure for updating, but I also want to better understand what is actually going on. I'm guessing the boot image on the other side gets overwritten by the OTA, which then flips you to that side, but I don't understand why it doesn't boot. Non-patched boot.img, I suppose?
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
RocketGeeezer said:
These steps worked for me:
1 install ota
2 flash TWRP_A_B_Retention_Script-Magisk.zip via magisk
3 install magisk on inactive slot
4 reboot
Click to expand...
Click to collapse
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Flapjack said:
Awesome. I had not even heard of the retention script, but it sounds like exactly what I'm missing.
As for step 3, how do you install Magisk on the inactive slot?
Click to expand...
Click to collapse
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
whatthekj said:
Open magisk, click the first install option and download that zip. Then a box with four options should appear. Click the last option to install on another slot.
Click to expand...
Click to collapse
Thanks! Trying now!
Flapjack said:
Thanks! Trying now!
Click to expand...
Click to collapse
No problem. Let me know if you have any issues.
Well, it's different (booting to TWRP instead of stock recovery), but it still didn't work. It booted through the "warning...unlocked bootloader" screen twice, then went to TWRP, though without encryption. I was able to switch the boot slot and get into system again (just as it was before the flash), but I don't know what I did wrong.
The only thing different I did was use the tools under EX Kernel Manager to flash the TWRP retention script, as I couldn't find where Magisk could do that.
**EDIT**
Now when I try to do the OTA, I get a "System update installation failed".
I cleared the cache and tried it again, this time doing the retention zip from inside Magisk > Modules > Add (+ sign) option, which is what I'm assuming you did.
It did the exact same thing. After step four, I rebooted, and it went straight into recovery (without the option to decrypt).
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
RocketGeeezer said:
I think you have to root your phone again If you have the chinese twrp you can do it via twrp. Otherwise put tj magisk installer on a USB stick
Click to expand...
Click to collapse
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Flapjack said:
I can install/uninstall Magisk all day long, now that I've put TWRP 3.3.1-30 on. Even after a failed update, where it fails to ask to decrypt, I can still sideload via USB and install it (even though I can't see the internal storage).
Click to expand...
Click to collapse
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Maybe do some research first. There is also a unbrick thread
RocketGeeezer said:
Can you lflash the ota image again? And after that twrp and after that magisk again. After that reboot to system again. This worked on my pixel. Not shure if this works on the 7 pro...
Click to expand...
Click to collapse
I've tried that... several times. I wish it worked.
Maybe do some research first. There is also a unbrick thread
Click to expand...
Click to collapse
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Flapjack said:
I've tried that... several times. I wish it worked.
I've been doing a lot of research. There are some pretty in-depth threads on reddit how the A/B treble system works. Nothing I didn't already know. It's certainly different than pre-treble, but not rocket science... something is wrong with the phone. I would just like to know what I did wrong in the first place so I don't do it again.
Fortunately, I still have a bootable system with root on my B partition, so I was able to run TB and backup everything, along with all my pictures and such. I'll be restoring it to stock and just going from there. Looks like I don't have any other choice.
Click to expand...
Click to collapse
Okay I updated just like we do with our pixels when we flash a custom ROM. TW RP flash your ota.zip,TWRP zip, reboot to recovery that will switch slots , because your update just flashed to the other slot, then flash magisk then reboot. That's how I did this last update. Oh and it's got to be the full ota from what I read anyways.
*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This work for the Verizon Pixel 4 XL???
SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC
eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol
So for some reason the February update doesn't show up for my in system updates.
To update manually, is it better to download the ota from Google's site and flash that or the newest firmware and flash system?
G5-User7080 said:
So for some reason the February update doesn't show up for my in system updates.
To update manually, is it better to download the ota from Google's site and flash that or the newest firmware and flash system?
Click to expand...
Click to collapse
The safest way to update is by sideloading the OTA.
I assume your bootloader is not unlocked; if I am correct, flashing the factory image is not an option.
V0latyle said:
The safest way to update is by sideloading the OTA.
I assume your bootloader is not unlocked; if I am correct, flashing the factory image is not an option.
Click to expand...
Click to collapse
Ah sorry for the lack of details.
I'm unlocked and rooted and pass safetynet / play attestation with safetynet-fix-mod by DisplaX
I found your guide about updating etc in the Pixel 6 forum, and since I didn't know if I could just take feb 06 OTA or if I had to flash all previous ones too I just went with the factory image method.
I updated with the same version as I'm running to see if it would offer me to OTA then et voila it does
After I finished updating and did fastboot boot magisk-patched-boot-image.img it did offer me to OTA even tho I failed safety-net / play attestation (probably since I didnt do magisk direct install yet and was just booting the rooted image)
Which made me wonder,.. are you supposed to uninstall magisk before you even click on "system update"?
I thought you just check for updates first and when it shows one you then uninstall magisk.
G5-User7080 said:
Ah sorry for the lack of details.
I'm unlocked and rooted and pass safetynet / play attestation with safetynet-fix-mod by DisplaX
I found your guide about updating etc in the Pixel 6 forum, and since I didn't know if I could just take feb 06 OTA or if I had to flash all previous ones too I just went with the factory image method.
Click to expand...
Click to collapse
Current updates have all the updates and fixes from previous releases
G5-User7080 said:
I updated with the same version as I'm running to see if it would offer me to OTA then et voila it does
After I finished updating and did fastboot boot magisk-patched-boot-image.img it did offer me to OTA even tho I failed safety-net / play attestation (probably since I didnt do magisk direct install yet and was just booting the rooted image)
Which made me wonder,.. are you supposed to uninstall magisk before you even click on "system update"?
I thought you just check for updates first and when it shows one you then uninstall magisk.
Click to expand...
Click to collapse
Automatic OTA is troublesome when rooted. You don't need to perform a complete uninstall in Magisk; just restore images before you take the update, and make sure that you go back into Magisk and patch the inactive slot before you reboot.
V0latyle said:
Current updates have all the updates and fixes from previous releases
Automatic OTA is troublesome when rooted. You don't need to perform a complete uninstall in Magisk; just restore images before you take the update, and make sure that you go back into Magisk and patch the inactive slot before you reboot.
Click to expand...
Click to collapse
yes, that restore original images thing is what I meant, I'm just sticking to the OTA guide from Magisk, thats why I booted the patched boot img and then direct installed through magisk too instead of just flashing it.
Just since I've never done an OTA update before Idk if it shows that updates are available with magisk installed.
Like, if the "restore images" before OTA refers to before I even click on Settings -> System update to check if theres an upate available or if I can like let it download first and then restore it before installation or smth.
It did show it for me now but that was directly after rebooting from updating with factory images, booting rooted boot image but it was before I even direct installed root through magisk.
@V0latyle
mhh alright... I'm never doing OTA's again.
restored original boot.img through magisk, let the ota do its thine, instead of restart I went to magisk again and did "install to inactive slot" then reboot from magisk.
Except that it just showed "This device is corrupted" and when I pressed continue I was staring at a google logo and nothing happened.
So in the end I had to use android flash tool and wipe my phone cause normal fastboot firmware install didn't work.
Now its working and rooted again but the "This device is corrupted" message doesn't go away.
I even relocked the bootloader through android flash tool before I unlocked it and rooted like normal, but it's still there.
Is that like an addition from the last update? Now whenever I reboot there are 2 screens I have to click away,.. the normal unlocked warning and the corrupted screen.
G5-User7080 said:
@V0latyle
mhh alright... I'm never doing OTA's again.
restored original boot.img through magisk, let the ota do its thine, instead of restart I went to magisk again and did "install to inactive slot" then reboot from magisk.
Except that it just showed "This device is corrupted" and when I pressed continue I was staring at a google logo and nothing happened.
So in the end I had to use android flash tool and wipe my phone cause normal fastboot firmware install didn't work.
Click to expand...
Click to collapse
Shouldn't have had to do that. If this happens just reflash the boot image using ADB. If that doesn't work...
G5-User7080 said:
Now its working and rooted again but the "This device is corrupted" message doesn't go away.
Click to expand...
Click to collapse
Try sideloading the OTA. It appears that the "patch inactive slot" method in Magisk isn't working for everyone. Nothing is actually corrupt, the OTA update engine just isn't happy about something. Either way, wiping data shouldn't be necessary.
G5-User7080 said:
I even relocked the bootloader through android flash tool before I unlocked it and rooted like normal, but it's still there.
Click to expand...
Click to collapse
Don't EVER do this unless everything is 100% stock and the device has been fully wiped.
G5-User7080 said:
Is that like an addition from the last update? Now whenever I reboot there are 2 screens I have to click away,.. the normal unlocked warning and the corrupted screen.
Click to expand...
Click to collapse
Nope, both screens are part of the Android Boot Flow.
Since the inactive slot method didn't work, I suggest sideloading the OTA in the future. Do not interrupt the process or attempt to flash anything. Let the update complete normally and boot; you won't have root. Assuming you already have a Magisk patched boot image handy (it doesn't have to be current), you can then reboot to bootloader and live boot the patched image, then perform Direct Install in Magisk.
V0latyle said:
Shouldn't have had to do that. If this happens just reflash the boot image using ADB. If that doesn't work...
Click to expand...
Click to collapse
welp.. I tried flashing matching (so newest) boot, didnt work
V0latyle said:
Try sideloading the OTA. It appears that the "patch inactive slot" method in Magisk isn't working for everyone. Nothing is actually corrupt, the OTA update engine just isn't happy about something. Either way, wiping data shouldn't be necessary.
Click to expand...
Click to collapse
you mean now? like after im factory reset & rooted I should sideload the same OTA again which I'm on right now?
V0latyle said:
Don't EVER do this unless everything is 100% stock and the device has been fully wiped.
Click to expand...
Click to collapse
Isn't that what android flash tool does?
wiping my device and install stock?
either way I wasnt running a custom rom and of course I don't relock it after I'm rooted.
V0latyle said:
Since the inactive slot method didn't work, I suggest sideloading the OTA in the future. Do not interrupt the process or attempt to flash anything. Let the update complete normally and boot; you won't have root. Assuming you already have a Magisk patched boot image handy (it doesn't have to be current), you can then reboot to bootloader and live boot the patched image, then perform Direct Install in Magisk.
Click to expand...
Click to collapse
So right now I should leave everything as is including the corrupted message, right?
Then when the next OTA comes I do nothing, keep root, no uninstall or restore through magisk, and I just download the newest OTA from google, and do the fastboot sideload thing?
It'll work even though my boot.img is rooted?
And then the OTA will remove root, I live boot my existing (eventually outdated) magisk patchet boot.img, then direct install as usual?
V0latyle said:
Nothing is actually corrupt, the OTA update engine just isn't happy about something.
Click to expand...
Click to collapse
This is slightly frustrating,... thanks for telling my my device is corrupted and making me think its actually bricked... nice going google.
I'm gonna have so much fun doing all the device settings again, cause for some reason restoring google backup doesn't do that.
How would I not hate OTA's after this lol
G5-User7080 said:
welp.. I tried flashing matching (so newest) boot, didnt work
you mean now? like after im factory reset & rooted I should sideload the same OTA again which I'm on right now?
Click to expand...
Click to collapse
Yes. Sorry if it's confusing. The OTA update process can be a bit...sensitive.
G5-User7080 said:
Isn't that what android flash tool does?
wiping my device and install stock?
Click to expand...
Click to collapse
Yes, but only if Wipe device is checked
G5-User7080 said:
So right now I should leave everything as is including the corrupted message, right?
Click to expand...
Click to collapse
Just sideload the OTA. It won't wipe anything and it can't possibly hurt anything.
G5-User7080 said:
Then when the next OTA comes I do nothing, keep root, no uninstall or restore through magisk, and I just download the newest OTA from google, and do the fastboot sideload thing?
It'll work even though my boot.img is rooted?
Click to expand...
Click to collapse
Yes - when you update via system, it checks images for integrity before updating. Sideloading the OTA skips this and just overwrites the images. Doesn't affect user data.
G5-User7080 said:
And then the OTA will remove root, I live boot my existing (eventually outdated) magisk patchet boot.img, then direct install as usual?
Click to expand...
Click to collapse
Yep.
G5-User7080 said:
This is slightly frustrating,... thanks for telling my my device is corrupted and making me think its actually bricked... nice going google.
I'm gonna have so much fun doing all the device settings again, cause for some reason restoring google backup doesn't do that.
How would I not hate OTA's after this lol
Click to expand...
Click to collapse
I can definitely understand the frustration. Suggestion: before you go nuclear next time and wipe your data, post here and see if someone might have a solution. I have a strong suspicion that simply sideloading the OTA would have cleared the corrupted message, you wouldn't have had to wipe data, and you could have just re-rooted. As the great Hitchhiker's Guide to the Galaxy tells us, "Don't Panic!"
Sideloading went without issue, message still there though, but at this point idec anymore, thanks for the help!
V0latyle said:
Just sideload the OTA. It won't wipe anything and it can't possibly hurt anything.
Click to expand...
Click to collapse
G5-User7080 said:
Sideloading went without issue, message still there though, but at this point idec anymore, thanks for the help!
Click to expand...
Click to collapse
The corrupt message is?
Hmm. Sideload again. Reason being is the OTA always installs to the inactive slot, then switches to that slot. If you install the OTA twice, it installs to both slots. Example: you're on slot A. Install OTA -> slot B becomes active, Slot A hasn't been updated. Install OTA again, -> Slot A becomes active.
Just to make sure - you're using Magisk 25.2, yes?
Latest release, yes.
No worky, was on slot a before, so it did ota and switched to b, b wasnt rooted, I rooted it through magisk, did the ota again, so it switched back to a, rebooted, a wasnt rooted as expected and the message was still there.
just to confirm that it actually switched and didnt like ota 2 times without switching, I switched back to b and it was rooted.
Can only guess it only works if the ota actually installs anything, i mean im already on february 5th on both slots.
So I'll try again next month.
G5-User7080 said:
Latest release, yes.
No worky, was on slot a before, so it did ota and switched to b, b wasnt rooted, I rooted it through magisk, did the ota again, so it switched back to a, rebooted, a wasnt rooted as expected and the message was still there.
just to confirm that it actually switched and didnt like ota 2 times without switching, I switched back to b and it was rooted.
Can only guess it only works if the ota actually installs anything, i mean im already on february 5th on both slots.
So I'll try again next month.
Click to expand...
Click to collapse
The message should disappear when you update the OS next month.
G5-User7080 said:
So for some reason the February update doesn't show up for my in system updates.
To update manually, is it better to download the ota from Google's site and flash that or the newest firmware and flash system?
Click to expand...
Click to collapse
what works best for me (!) is downloading the whole factory image, extracting boot.img, patching it using magisk, transferring it back to the pc, and there editing flash-all.bat so it doesn’t wipe data (!) and adding one line to flash the new boot.img directly at the end. reboot to bootloader, run flash-all, done.
Just use PixelFlasher. It will take care of everything, including Magisk patching the boot image. Makes updates using the factory images painless, takes about 5 minutes total.
G5-User7080 said:
hi, umm so this isn't really something for any thread, I just have some questions.
Is it possible to force a full factory flash?
Cause I assume running flash-all.bat from the factory image or using android flash tool does not do that, as it only uses the fastboot update command.
Well, Idk what exactly fastboot update does, but from my old phone I remember that the script to flash stock contains a lot of flash commands for every partition, e.g. fastboot flash boot, fastboot flash system, etc.
So maybe that warning would go away after actually flashing the entire rom over it.
Also while data was wiped at least 2 times, there are three apps that I accidentally disabled a few days ago, and or some reason I couldnt re-enable them, and the weird thing is they are still disabled..
Then for some reason when I restored the google backup after the wipe it didn't apply my settings and only downloaded my apps.
And now I found another thing, sometimes my screen doesnt turn off after the set timeout, only when charging tho, but stay awake in dev settings isnt on..
Additionally the battery level is inconsistent and suddenly jumps up or down a few percent, but the kernel reported level (measured with ACCA) stays consistent, so its not really an issue.
I'll try resetting all app permissions and if that doesnt work all settings i guess, but I really have no clue what mightve caused this.
Especially since none of those happened before wipe / OTA and I only re-installed my apps, loaded their settings from backups and clicked through the settings app.
No new modules or any root quirks.
I'm glad its just my phone, I only really use it for social media and and umm music ig so its not really that much work to set up again, only really annoying thing is to click through everything in settings cause theres no way to back that up meh.
Click to expand...
Click to collapse
@G5-User7080 I'm bringing this to public as discussed in PM.
Yes, you can force a full factory flash. Yes, the flash-all script and the Android Flash Tool both do this - they flash bootloader, radio, and all OS partitions. If you want to be really thorough, you can check the "Force flash all partitions" checkbox, this also requires a data wipe.
I'm not sure why system apps would remain disabled following a data wipe.
The Google One backup isn't able to back up everything. It cannot back up application data, and it does not back up all system settings.
Regarding the screen, I've noticed the opposite with my Pixel 5. I have "Stay Awake" turned off, but despite having my screen timeout set for 1 minute, it turns off and locks after about 15 seconds.
Battery...Not sure what to tell you.
Consumer electronics are cantankerous beasts indeed and fraught with gremlins.
V0latyle said:
@G5-User7080 I'm bringing this to public as discussed in PM.
Yes, you can force a full factory flash. Yes, the flash-all script and the Android Flash Tool both do this - they flash bootloader, radio, and all OS partitions. If you want to be really thorough, you can check the "Force flash all partitions" checkbox, this also requires a data wipe.
I'm not sure why system apps would remain disabled following a data wipe.
The Google One backup isn't able to back up everything. It cannot back up application data, and it does not back up all system settings.
Regarding the screen, I've noticed the opposite with my Pixel 5. I have "Stay Awake" turned off, but despite having my screen timeout set for 1 minute, it turns off and locks after about 15 seconds.
Battery...Not sure what to tell you.
Consumer electronics are cantankerous beasts indeed and fraught with gremlins.
Click to expand...
Click to collapse
I couldnt think of any other way that some apps retain their disabled state, as well as why would the corrupted message stay even after full stock / full OTA on both slots.
Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.
Do you think enforcing all partitions flash would get rid of the corrupted warning as well?
As for the google one backup,.. it said it would restore settings, even if its not all of them,.. i dont think it restored any.
sound, display, permissions, gestures, gboard, etc, was all different.
G5-User7080 said:
I couldnt think of any other way that some apps retain their disabled state, as well as why would the corrupted message stay even after full stock / full OTA on both slots.
Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.
Click to expand...
Click to collapse
Pretty sure it does. I could be wrong.
G5-User7080 said:
Do you think enforcing all partitions flash would get rid of the corrupted warning as well?
Click to expand...
Click to collapse
In theory, yes. Google hasn't exactly released any in depth documentation for the Android Flash Tool. Note that force flashing all partitions will include a data wipe but it's worth a try
G5-User7080 said:
As for the google one backup,.. it said it would restore settings, even if its not all of them,.. i dont think it restored any.
sound, display, permissions, gestures, gboard, etc, was all different.
Click to expand...
Click to collapse
Only thing I can think of is you might have selected a backup that was incomplete or something. Google One takes "snapshots" every once in a while, including after you've signed into Google on your device.
Otherwise, the backup just didn't restore completely?
G5-User7080 said:
Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.
Click to expand...
Click to collapse
Fastboot does but I don't think Android Flash Tool does unless you select "Force Flash Partitions".
I'm pretty sure the information part of "Force Flash Partitions" says "Flash all partitions that are part of the build even if they are up to date (e.g. bootloader, radio) as well as force a wipe".
At least this language leaves me to believe that that Android Flash Tool won't overwrite partitions that are already up-to-date unless you select "Force Flash Partitions".