Related
I have TWRP and root. When the security update from Google downloads it this and then TWRP starts and I don't know what to do next, help please.
peejayw said:
I have TWRP and root. When the security update from Google downloads it this and then TWRP starts and I don't know what to do next, help please.
Click to expand...
Click to collapse
You can go to the factory image page, download the newest factory image and install that via adb fastboot as described above. Be sure to download the correct factory image in the list.
The correct download qould be: Android 6.0.0 (MRA58N).
Unfortunately I am not allowed to post outsite links right now, as I am new in this forum. But here is a good internal link about How to flash a factory image.
Take care! Flashing a factory image wipes all user data!
But anyhow. Is there a method to install the security update without wipeing all data?
DerBoym said:
You can go to the factory image page, download the newest factory image and install that via adb fastboot as described above. Be sure to download the correct factory image in the list.
The correct download qould be: Android 6.0.0 (MRA58N).
Unfortunately I am not allowed to post outsite links right now, as I am new in this forum. But here is a good internal link about How to flash a factory image.
Take care! Flashing a factory image wipes all user data!
But anyhow. Is there a method to install the security update without wipeing all data?
Click to expand...
Click to collapse
Just flashing system.img over should be good.
I was enrolled in the Android O Beta Program and followed these steps but can't get TWRP to boot:
• Un-enroll from O beta
• Take OTA to downgrade to 7.1.2 N2G470
• Set up system (dev. options, enable USB debugging, etc.)
• fastboot boot twrp-3.0.2-0-RC1.img
• Boots in to TWRP but doesn't go passed splash screen (after waiting more than 30 minutes)
Not sure if I have to re-flash nougat bootloader, radio and img. Any help is appreciated, thanks!
It's a known issue with TWRP with way O repartitions your phone even after downgrade. You'll have to wait for an update to be released to accommodate the changes in partition structure.
You'll have to flash the factory images from April or May to both slot before it will work again properly
S8ntsHaz3 said:
You'll have to flash the factory images from April or May to both slot before it will work again properly
Click to expand...
Click to collapse
Gotcha, I'll give it a shot tonight.
No problem
S8ntsHaz3 said:
You'll have to flash the factory images from April or May to both slot before it will work again properly
Click to expand...
Click to collapse
This is correct.. all you need to do is flash the factory images to BOTH slots and you'll be good to go.. I went through this issue myself and once I did this, everything is back to normal
pahlerc1 said:
This is correct.. all you need to do is flash the factory images to BOTH slots and you'll be good to go.. I went through this issue myself and once I did this, everything is back to normal
Click to expand...
Click to collapse
Perfect. Thanks for looking out dudes.
That's what this place is for!!!
S8ntsHaz3 said:
You'll have to flash the factory images from April or May to both slot before it will work again properly
Click to expand...
Click to collapse
I've tried multiple times to get this booted to both slots and can't seem to get it right. Can you provide steps how to flash to both slots?
I use the unified android toolkit. I'm just learning all of this myself but I know there's a guide on here somewhere that can explain it better than my self. I believe it involved getting the factory image and removing the -w from the flashall file. I'm sorry I cant be of more help!!
S8ntsHaz3 said:
I use the unified android toolkit. I'm just learning all of this myself but I know there's a guide on here somewhere that can explain it better than my self. I believe it involved getting the factory image and removing the -w from the flashall file. I'm sorry I cant be of more help!!
Click to expand...
Click to collapse
Thanks, I'll look around, but if anyone has a link I'd appreciate it
In my experience if you flash the factory images twice it's flashes to both slots
Finally got the image flashed to both slots. Now for some reason I always get a bootloop after flashing the twrp installer. fml
chesstopher said:
Finally got the image flashed to both slots. Now for some reason I always get a bootloop after flashing the twrp installer. fml
Click to expand...
Click to collapse
On the May update?
You need to install the zip from inside twrp that is in the first post of the thread below. Need to do that when you root, twrp or change kernels.
So fastboot boot to twrp again and adb push the zip to the phone and install it.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
TonikJDK said:
On the May update?
You need to install the zip from inside twrp that is in the first post of the thread below. Need to do that when you root, twrp or change kernels.
So fastboot boot to twrp again and adb push the zip to the phone and install it.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yup, I was on the may update, had no idea they changed anything up in May. What I did was reboot the system, download the twrp zip, fast boot back to twrp and flash the zip, resulted in boot loop. I'll try flashing the verified bootsigner later and if that doesn't work, I'll try rolling back to April.
Flashing the bootsigner did the trick. Thanks for all the help!
enrolled android beta program for almost a day, battery consumes very much.
Now flashing the full May image, but after finishing flash, the phone can't boot into system.
It persisted in four turning dots for almost half an hour.
Tried to re-flash the may image, it did no help.
What should I do, mate?
chesstopher said:
Flashing the bootsigner did the trick. Thanks for all the help!
Click to expand...
Click to collapse
bush911 said:
enrolled android beta program for almost a day, battery consumes very much.
Now flashing the full May image, but after finishing flash, the phone can't boot into system.
It persisted in four turning dots for almost half an hour.
Tried to re-flash the may image, it did no help.
What should I do, mate?
Click to expand...
Click to collapse
Sorry man, I've been away from my computer for a couple days. Glad to see you got it figured out. What worked for me was booting into twrp from fastboot, flashing the twrp zip, flashing the latest bootsigner zip from CF, reboot recovery then following the steps to flash PA + gapps that I had downloaded previously.:good:
how can i downgrade from oos 9.04 to 9.03?
Flash full OOS zip.
Kollachi said:
Flash full OOS zip.
Click to expand...
Click to collapse
Where can that be found. Cant find it on oneplus website
WillowTree said:
Where can that be found. Cant find it on oneplus website
Click to expand...
Click to collapse
Try a search in this thread, maybe somebody posted it :
https://forum.xda-developers.com/on...-6-mirrors-official-oxygen-os-t3792244/page55
Totone56 said:
Try a search in this thread, maybe somebody posted it :
https://forum.xda-developers.com/on...-6-mirrors-official-oxygen-os-t3792244/page55
Click to expand...
Click to collapse
Found it, thank you.
Will something break if i downgrade?
WillowTree said:
Found it, thank you.
Will something break if i downgrade?
Click to expand...
Click to collapse
If you use the stock "Local Upgrade" option, it won't let you.
If you use TWRP or blu_spark TWRP, just remember to wipe Data.
There is a chance the security patch level is lower on the old bulid. If it's the case, you'll have to Format Data (Not wipe, really format) to remove all encryption, or it won't boot :/
This will erase all of your storage, including folders, downloads, everything.
Totone56 said:
If you use the stock "Local Upgrade" option, it won't let you.
If you use TWRP or blu_spark TWRP, just remember to wipe Data.
There is a chance the security patch level is lower on the old bulid. If it's the case, you'll have to Format Data (Not wipe, really format) to remove all encryption, or it won't boot :/
This will erase all of your storage, including folders, downloads, everything.
Click to expand...
Click to collapse
Sorry for being ignorant but how do i "format data"?
So I have to boot into TWRP > flash 9.0.3 OOS > wipe data > reboot to system and that it?
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
[/COLOR]
WillowTree said:
Sorry for being ignorant but how do i "format data"?
So I have to boot into TWRP > flash 9.0.3 OOS > wipe data > reboot to system and that it?
Click to expand...
Click to collapse
One advice : Be near a computer with the 9.0.3 and TWRP zips near you.
You should flash 9.0.3, then TWRP (or it will erase it).
This will install it on one slot.
Reboot recovery, and do this a second time, 9.0.3 and TWRP, to fill the other system slot
Reboot recovery a second time to go back to the first slot, and to format data, go into the wipe menu, and you'll see (if i remember correctly) two buttons, Format Data, and Advanced Wipe. It's above the "Factory Reset" slider.
You'll have to touch Format Data, and confirm by typing "yes", there will be a warning.
- > If when you reboot the recovery, it doesn't ask for your password, it means it's busted by the security patch, and you have to format haha !
This is why it's good to have a PC nearby, to copy the zips again if you have to format during the process.
Totone56 said:
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
[/COLOR]
One advice : Be near a computer with the 9.0.3 and TWRP zips near you.
You should flash 9.0.3, then TWRP (or it will erase it).
This will install it on one slot.
Reboot recovery, and do this a second time, 9.0.3 and TWRP, to fill the other system slot
Reboot recovery a second time to go back to the first slot, and to format data, go into the wipe menu, and you'll see (if i remember correctly) two buttons, Format Data, and Advanced Wipe. It's above the "Factory Reset" slider.
You'll have to touch Format Data, and confirm by typing "yes", there will be a warning.
- > If when you reboot the recovery, it doesn't ask for your password, it means it's busted by the security patch, and you have to format haha !
This is why it's good to have a PC nearby, to copy the zips again if you have to format during the process.
Click to expand...
Click to collapse
I greatly appreciate your help.
Just to clarify the last part, what if i don't have a password in the first place. Will it still "not ask for it" if. The security patch is messed up?
Edit : what if i want to re-flash the current stock OOS (9.0.4) do i only flash it in twrp and reboot. Nothing else?
WillowTree said:
I greatly appreciate your help.
Just to clarify the last part, what if i don't have a password in the first place. Will it still "not ask for it" if. Tje security patch is messed up?
Click to expand...
Click to collapse
Mmmmh. When you normally boot into TWRP, does it ask anything to decrypt the data ?
Mine asks for my password, if I don't enter it, all folders are unreadable and empty.
I never used it without a password.
Maybe it will enter TRWP without asking for anything, but all the folders and files will be encrypted and unusable. This is the case where you have to format everything.
If you want to go from 9.0.3 to 9.0.4 later on, you just have to flash it yes.
It's advised to still flash it on both slots like described above, just to be sure though, but you will not have to wipe anything
Totone56 said:
Mmmmh. When you normally boot into TWRP, does it ask anything to decrypt the data ?
Mine asks for my password, if I don't enter it, all folders are unreadable and empty.
I never used it without a password.
Maybe it will enter TRWP without asking for anything, but all the folders and files will be encrypted and unusable. This is the case where you have to format everything.
If you want to go from 9.0.3 to 9.0.4 later on, you just have to flash it yes.
It's advised to still flash it on both slots like described above, just to be sure though, but you will not have to wipe anything
Click to expand...
Click to collapse
Yes, you are correct. It does ask for a password if you have that enabled. But i always disabled it, just in case.
I think i got it now. When i see that the files are unattainable, i will format. And reboot after that.
What i meant was that. I want to re-flash the same stock version that i now havd (9.0.4) just to see if that solves my (connect-disconnect wifi/data issue). If not then i will proceed to downgrade to 9.0.3
WillowTree said:
Yes, you are correct. It does ask for a password if you have that enabled. But i always disabled it, just in case.
I think i got it now. When i see that the files are unattainable, i will format. And reboot after that.
What i meant was that. I want to re-flash the same stock version that i now havd (9.0.4) just to see if that solves my (connect-disconnect wifi/data issue). If not then i will proceed to downgrade to 9.0.3
Click to expand...
Click to collapse
You should do a simple factory reset at the same time if you re-flash your current version. I had bad WiFi issues too on this one after a dirty flash from 9.0.3. With a clean 9.0.4 flash, it was fine.
To be sure, you could re-flash 9.0.4 on both slots (It has been said to resolve issues sometimes), and do a simple factory reset (Without formatting, a classic "Clean Flash"). The ROM itself is fine, so it would eliminate issues you could have with your particular setup
Totone56 said:
You should do a simple factory reset at the same time if you re-flash your current version. I had bad WiFi issues too on this one after a dirty flash from 9.0.3. With a clean 9.0.4 flash, it was fine.
To be sure, you could re-flash 9.0.4 on both slots (It has been said to resolve issues sometimes), and do a simple factory reset (Without formatting, a classic "Clean Flash"). The ROM itself is fine, so it would eliminate issues you could have with your particular setup
Click to expand...
Click to collapse
That's exactly what i thought. A factory reset might solve the problem so i went and googled it and people were having issues when doing a simple factory reset in twrp > https://forum.xda-developers.com/oneplus-6/how-to/factory-reset-os-patched-boot-img-t3795998/amp/
But yet again i were to re-flash stock on both slots it would bring back "stock boot.img" i suppose, if I'm not wrong.
---------- Post added at 12:40 PM ---------- Previous post was at 12:04 PM ----------
It all went fine. Wifi issue seems to be fixed, need further look in to.
My guess was right, after flashing stock OOS second time on the other slot it must've stocked the boot.img so the factory reset went fine and booted into system as it should.
Thanks again for your help @Totone56
WillowTree said:
That's exactly what i thought. A factory reset might solve the problem so i went and googled it and people were having issues when doing a simple factory reset in twrp > https://forum.xda-developers.com/oneplus-6/how-to/factory-reset-os-patched-boot-img-t3795998/amp/
But yet again i were to re-flash stock on both slots it would bring back "stock boot.img" i suppose, if I'm not wrong.
---------- Post added at 12:40 PM ---------- Previous post was at 12:04 PM ----------
It all went fine. Wifi issue seems to be fixed, need further look in to.
My guess was right, after flashing stock OOS second time on the other slot it must've stocked the boot.img so the factory reset went fine and booted into system as it should.
Thanks again for your help @Totone56
Click to expand...
Click to collapse
Nice, enjoy !
And yes, flashing the ROM also switches slots. So if you were booting slot _a before, now you're on slot _b. So the kernel is the stock one, that went with the zip you just flashed
I've always wanted to post one of these
https://developers.google.com/android/images
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
I was looking thru that post and didnt wanna risk wiping the device. I just had to wipe a few days ago due to Edxposed bootloop issue lol
Ha, yeah, I feel your pain there, wiping is way too much of a pain to do that frequently
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
You can also flash the OTA file in stock recovery and not lose data.
spotmark said:
You can also flash the OTA file in stock recovery and not lose data.
Click to expand...
Click to collapse
Will it retain root or do you mean - https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Androider4Life said:
Retain root or have to re-root
Click to expand...
Click to collapse
Have to re-root using the Magisk method. Put stock boot on phone, patch boot with Magisk, put modded boot back on computer, and flash in fastboot. AFAIK, there is no way to retain root. Every time you flash the latest monthly patch, it flashes a new stock boot. Therefore, no root.
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
There's a way with taking the ota through settings I found out how from a user on here which is:
Once received the ota , go to magisk first uninstall/restore images then download/install ota then DONT REBOOT, go back to magisk install magisk to inactive slot from the app then reboot and all should work with new ota update and have root still.
What is this update 4.3mb
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
gettinwicked said:
Once again, my phone got bricked. I wanted to sideload, so I tried to get it into recovery, it wouldn't, so I tried a few times, and decided screw it. Now my phone bootloops. So, download the image and try flashing, it won't go into fastboot and fails. No matter what I do, I can't seem to save it. Can anyone help me with this? I'm trying a different computer in a sec, but, not sure if that will work either.
Edit: The different computer doesn't see it... FML
Click to expand...
Click to collapse
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
gm007 said:
What is this update 4.3mb
Click to expand...
Click to collapse
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Jiggs82 said:
Just flash the factory image or ota thru flash.all bat file after you do/did the necessary steps like extract the images etc to platform tools folder on ur pc
Or visit here for more help/steps
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
You missed the part where I did try flashing the image. I've done this a hundred times, so, I did it right.
Anyway, I got it. I didn't realize my work computer had a USB-C port, so, I grabbed one and tried flashing the image with that. Worked! Thank God... I guess sdk tools doesn't like a USB 1 to C cable, and my phone doesn't like going into recovery...
Androider4Life said:
How do we flash the update and not lose data and root? All the guides are still for 9.0 for updates
Click to expand...
Click to collapse
kerobrat said:
There's a link to a how-to for 10 in the stickied how-to for 9 - https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117.
But without twrp I don't think there's a way to retain root, I think you'll need to go the route of patching the boot image with Magisk. But for data just remove the -w switch from flash-all, that should be the same.
Click to expand...
Click to collapse
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Homeboy76 said:
If you are rooted flash the boot.img of the factory image you are currently on to both slots:
Code:
fastboot flash boot --slot all boot.img
Then Do #4 'keep Data'
Click to expand...
Click to collapse
I am starting to feel more and more like a lot of the bootloop issues are being caused by OTAs swapping slots on install. Besides the --slot all patched boot, it might help to run the OTA twice to get it to install to both slots completely. Preferably though, quit using OTAs and work with -w removed flash-all installer (and even then possibly installing to both slots with an active slot swap in between and before rooting). The double install is common when installing custom ROMs, and the process for OTA sideloads is pretty similar.
Performance improvement, feels smooth and responsive. Glad i dont need to root this phone, ppl are having so many problems.
boe323 said:
Its just a security patch, we already had the updated rom in september, this just adds the latest security patch. Even though its only 4.3mb, its taking ages to patch, 10 mins still installing.
Click to expand...
Click to collapse
My download was 1.3 gb and took forever to install. That's more than just the security patch.. Build number is different too.
Sent from my Pixel 3 XL using Tapatalk
Worked exactly the same as the 10 and .C3 builds for me. Flash-all (minus -w) and patched boot in Magisk. No issues. It was not just security this month. See the functional patches in the bulletin.
https://source.android.com/security/bulletin/pixel/2019-10-01
is there new platform tools too?
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".