Develop Bugs

[Q] Root Issues - Are these known? Are there fixes?

I purchased my Pixel 2 XL from the Google store. I had just upgraded to the 8.1 OTA a few days before when i came across this video and used it to root my phone:
https://youtu.be/nFD9sa-WdUM
Here's the basic steps i took:
Unlock dev options and turn on OEM Unlocking
Boot to stock recovery
Go to his highonandroid site and download TWRP 3.1.1 beta2 (img and zip), an outdated fastboot.zip, magisk 14.5, and the USB drivers which i didnt download because my computer is already recognizing my device just fine.
Extract the fastboot files to a new folder and copy the twrp img file to the fastboot folder.
In CMD, unlock the bootloader with fastboot and reboot phone.
Connect phone as storage device, copy over twrp zip file and magisk 14.5 zip files to root folder on the phone, reboot into recovery
Use fastboot to boot the twrp image that we copied to fastboot folder to get into twrp
Unhook the USB cable, set TWRP to read only, install TWRP, hit home button, then install Magisk and reboot
Once booted up, get into Magisk, download proprietary software, run checks and done.
Once this was done, my fingerprint scanner and wifi no longer worked. I could turn wifi on but it would never find anything. I also received the error when rebooting the phone that says "There's an internal problem with your device. Contact your manufacturer for details." When this message is on the screen, if i dont touch the phone and the screen times out, it flickers really bad and never actually shuts off until i unlock it and hit the OK button.
So i decided to give it another go and ran into some big issues. I figured that i used 8.0 instructions on 8.1 and there was enough things different that it caused problems, so i used this link to reroot:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
I went through the first 10-15 pages and the last 10-15 pages and did some searches on the thread and never found any of my issues, but found that a lot of people used different sets of steps and pretty much everything was successful as long as you didnt miss anything and used the most updated stuff. So i did, i went to googles website and downloaded the newest SDK with fastboot, adb, and all that good stuff, as well as the newest 8.1 image (there was a newer version but it had a carrier label on it so i didnt get that one), and the newest magisk and twrp.
I flashed 8.1 and the phone wouldnt boot, nor would it get into TWRP anymore, so i had to use fastboot to boot the twrp image and reinstall the recovery and magisk but it still wouldnt boot. I ran through several different steps and eventually got it to boot up with recovery working. Its the newest 8.1 image, the newest magisk, and the newest twrp, and since then magisk has updated a couple times.
Now on to my issues!
I still get the "Internal problem" popup when booting
I get a lot more random reboots
Sometimes random things just wont work, like streaming plex to my tv or loading an app or something on an app and i have to reboot and it works fine
I've seen numerous times that the "Internal problem" thing is just a mismatch between the system and vendor build.prop files. I dont know what exactly is mismatching between the two but i've tried reflashing them and all sorts of things and nothing ever fixes it.
Does anyone know if there's a fix to any of these three issues, or if maybe looking at my steps i clearly did something wrong? I'm willing to do the whole thing over again if there's a good suggestion, but once i flashed the 8.1 image and went that route, i rerooted successfully 4 times total before i quit doing it again just because of that internal problem popup, i kept figuring something went wrong or i did something wrong. I had no security or anything set before rooting or flashing or anything, and each time i reflashed the operating system, but when i flashed the OS, i had to extract the system file because i would constantly get an error that it was too big and it failed to truncate it, so i've always had to manually install it by first copying it to my phone and installing it through TWRP. Its been an adventure, but these problems suck!

PMad said:
...Its been an adventure, but these problems suck!
Click to expand...
Click to collapse
It's called training. For the error, you just need to fastboot flash the stock dtbo.img. This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore. I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate. Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image. (and try to distill your posts down a little, ffs)

v12xke said:
It's called training.
Click to expand...
Click to collapse
Every new phone is a new adventure, they are all the same but unique at the same time!
v12xke said:
For the error, you just need to fastboot flash the stock dtbo.img.
Click to expand...
Click to collapse
I'll give this a shot! Thank you!
v12xke said:
This was fixed on the 15.1 version of Magisk so you shouldn't have that problem anymore.
Click to expand...
Click to collapse
15.1 is the version i'm on now but nothing has changed. Which issue was this supposed to fix?
v12xke said:
I can tell you that rooted, kernel and a few root apps and I have never had ANY random reboots, so one of your apps is causing it or you didn't start from a completely blank slate.
Click to expand...
Click to collapse
My concern here is that my settings and apps are literally exactly the same as before root, except for magisk, its my only new app, which would lead me to believe that something Magisk is changing is causing the problem, or something else is happening that i'm not realizing yet.
v12xke said:
Run your phone in Safe Mode for a while to see if you stop the reboots 100%. If so, one of your apps is the cause. If you still get reboots in Safe Mode, you're gonna need to re-install. I suggest using the instructions on the Google web page where you got the full image.
Click to expand...
Click to collapse
The reboots are typically 1 reboot every 1 to 3 days, so its not a terrible issue but its happening and it shouldnt. For flashing the OS, after the first failure when trying to install it, those are the only instructions i've used, but i get that error when trying to install the OS that says something about how it failed to truncate the system.img file and so it wasnt installed, so my work around was to copy the file to the phones root folder, install the 8.1 image then immediately go and manually install the system.img file in twrp since its the only thing that fails, but i still have issues. What is this truncate issue?
v12xke said:
(and try to distill your posts down a little, ffs)
Click to expand...
Click to collapse
I agree! hahaha i just wanted to be clear and include all the details, otherwise everyone would have asked me question after question that i could have just included. It ends up being long, a lot happened!
I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)

PMad said:
...I'll give that dtbo.img a shot and see what that clears up, then if there's issues with rebooting still i'll try safe mode for a few days and see what that does.
Thank you v12xke! (how do you pronounce that? haha)
Click to expand...
Click to collapse
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.

v12xke said:
Your dtbo.img got patched by Magisk somewhere along the line and that is why the OS is throwing the error. Extract that img file from the full Google image and fastboot flash it, and the error will go away. There is a long thread around HERE on random reboots you should read. The v12xke is a car (Jaguar E-Type) I once owned.
Click to expand...
Click to collapse
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?

PMad said:
So i just tried to do this and ran into one of the issues i had when originally trying to root it... I get into TWRP and it will not take any button presses, like the touch screen has become a screen (minus the touch). Is there a fix for this or do i just need to install TWRP before i use it each time it does this?
Click to expand...
Click to collapse
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).

v12xke said:
1. You don't use TWRP to flash dtbo.img, you fastboot it while the phone is in bootloader mode.
2. TWRP works just fine if you install it and leave it installed. Make sure you are using 3.2.1-0 (img and zip).
Click to expand...
Click to collapse
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.

PMad said:
I was getting into TWRP to create a backup of everything and it popped up asking for my password, and i remembered reading that we have to get rid of all of our security before making a backup, so i tried to hit buttons to cancel it and nothing worked, i had to hold the power button. So i eliminated all of my security and went back thinking it was a 1 time issue but it happened again, it took me straight to the main menu but nothing would work. I'm using 3.2.1-0 like you mentioned and i cant press any buttons. I'd like to back everything up before flashing this or anything else.
Click to expand...
Click to collapse
You don't need a backup before re-flashing the STOCK dtbo (or boot) partitions, haha. READ UP.

Crosshatch Issue With ROMs & TWRP. Strange Occurrences

Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo

Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!

Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol

Android 10 - Factory reset needed?

Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?

I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good

razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.

is it worth factory resetting device with this latest update?

Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.

Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.

bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit

animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.

For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.

jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.

v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.

bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now

animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.

v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?

animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.

General December update woes...

The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 4 (and A9 for a/b slots), hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. I always thought corruption must have been there before, but now I'm not so sure.
update: flashed the last build from November using flash.android.com and was able to get my system back. 2nd flash for that build worked.

Alekos said:
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 9, hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. Corruption must have been there before, but now I'm not so sure.
If anyone has any fastboot tricks - I'd try anything at this point.
Click to expand...
Click to collapse
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back

mac796 said:
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
Click to expand...
Click to collapse
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message.
I tried flashing 4 different Factory Image builds (flashing manually the Factory Image not ota). The android flash tool (webiste) completes but same message appears after it restarts.

Alekos said:
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
I tried flashing 4 different Factory Image builds. The android flash tool completes but same message appears after it restarts.
Click to expand...
Click to collapse
You're trying to flash with fastboot right? Use that Android flash tool. You'll see a link to it in the factory image page. I went through the same thing you did, I got the corrupt device. at the very end It'll ask you to Lock the bootloader just don't do it if you want to stay unlocked.

Oh maybe I misunderstood you tried that and it's not recognizing it

mac796 said:
Oh maybe I misunderstood you tried that and it's not recognizing it
Click to expand...
Click to collapse
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.

Alekos said:
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Click to expand...
Click to collapse
That's no good. Hope it works out. I had a hell of a time getting mine back too

mac796 said:
That's no good. Hope it works out. I had a hell of a time getting mine back too
Click to expand...
Click to collapse
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
a few reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.

Alekos said:
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
Lots of reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Click to expand...
Click to collapse
I'm glad you got out of it

I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section

victoraran said:
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
Click to expand...
Click to collapse
so if I didn't have "OEM unlocking" enabled - I'd have a brick right now. just actually trying to help someone else that also got the corruption message and can't get back into Android to enable oem unlock. Recovery doesn't work (like my situation).
What a mess...

That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.

Battery life is awesome, still on 44% at half 10 at night from half 6 this morning

prohibido_por_la_ley said:
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Click to expand...
Click to collapse
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.

Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Well in the 4 years of me being on Android I've never had it happen.

I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.

JodyBreeze901 said:
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
Click to expand...
Click to collapse
same

Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Why not just adb sideload the OTA image, rather then flashing on both slots the factory image? It just sounds a bit of a hassle to me.
I know, I used to fastboot flash without -w my nexuses as well, but that was before the OTA images were available.

prohibido_por_la_ley said:
Well in the 4 years of me being on Android I've never had it happen.
Click to expand...
Click to collapse
yeah it's super rare. been flashing images and ota's since Nexus 4. But it happens.
I usually get the updates right away but sometimes I'll update the ota. I usually reflash the factory image every year after the beta. just seems odd how it corrupted the device. couldn't get into the system at all (or recovery/rescue modes).

yolandabecool said:
same
Click to expand...
Click to collapse
apparantly it has something to do with Bluetooth? I don't know how, but if you can get into safe mode and disable Bluetooth, clear cache/data for it and update all your google service apps, it can fix it (keeping Bluetooth off while restarting phone in regular mode) - but I couldn't load Android.
The trick to getting into Safe Mode is this: Turn off the device. Hold down power and and as soon as you see the "G" Logo, hold volume down. it will directly boot you to Safe mode. cool little trick. you'll have to manually enable wifi because it gets turned off.
At this point, if you can, enable OEM Unlocking. at least you'll be able to save the device if anything serious happens (like what I went through). the pixel repair website also works but I couldn't get into "Rescue Mode"

Question [HELP] Pixel 6 Pro freezing shortly after booting [SOLVED]

Hey guys,
Need some help troubleshooting what's going on with my Pixel 6 Pro.
Short version:
It's freezing up ~30-60s after booting and unlocking the phone, and then soft-rebooting some time after. If i don't unlock the phone it doesn't reboot. Safe mode also works but with lots of scary errors in logcat.
ROM: Stock, May 2023
Magisk: Yes
Kernel: Kirisakura Ravianth 1.0.5_6
Long version:
I rebooted manually to check something and then shortly after the screen froze up. It rebooted on its own and then it froze again. I then rebooted into safe mode and although it doesn't freeze up in safe mode, there are a lot of errors in the logcat (maybe these are normal for safe mode). Rebooting normally again, it freezes up every time 30-60s after unlocking, but is fine if I don't unlock. I then flashed the stock May 2023 image, without -w, so data was not wiped. I assume this means that Magisk and Kirisakura kernel is gone. The problem is still happening! Yikes!
What should I try? Can I clear data of the system without actually clearing all data on the phone (factory reset)?
We'll get to speculations on what could have caused this after I recover it...
I'm attaching two error level logcats:
1) During regular boot:
--------- beginning of kernel--------- beginning of system2023-06-06 22:35:2 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
2) During safe mode boot: Freeze_safe_mode_boot.txt
--------- beginning of main--------- beginning of kernel--------- beginning - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com

I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...

simplepinoi177 said:
I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...
Click to expand...
Click to collapse
Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.

Flyview said:
Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.
Click to expand...
Click to collapse
My apologies...I didn't see/overlooked that you had loaded up in safe mode...
One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.
FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....

simplepinoi177 said:
My apologies...I didn't see/overlooked that you had loaded up in safe mode...
One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.
FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....
Click to expand...
Click to collapse
Thanks! The files must have been too big. I edited the post with external links to the logs.
I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?

Flyview said:
Thanks! The files must have been too big. I edited the post with external links to the logs.
I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?
Click to expand...
Click to collapse
Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).

Your whole system has been broken. I would recommend you reflash all new system.

Kris Chen said:
Your whole system has been broken. I would recommend you reflash all new system.
Click to expand...
Click to collapse
How can you tell?
simplepinoi177 said:
Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).
Click to expand...
Click to collapse
Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

Flyview said:
Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
If you wish to do what Kris Chen suggests (he may have gotten to his conclusion by reading your logs), you could simply flash the Full Factory image that you linked -- you could do it manually or there are multiple tools that can do it for you; you were able to root, so I imagine you already have a method. Try to back up as much as you can.
If you wish to completely unroot, there are guides and methods I imagine.
If I found myself in your situation, this is what I would do...
update every module
a bug may be what's causing glitching and corrected in newer version
disable every module
update/establish Magisk stable version -- this may mean downgrading if on canary or delta
unhide Magisk if hidden
reboot
enable one module and reboot and see if the system loads up correctly
see if can't narrow down if it is a specific module
if that does result in a stable loading system,
it was a buggy module
if that doesn't result in a stable loading of system,
take a photo of installed modules
I would remove/delete the Magisk subdirectory from the root directory
flash the stock init_boot
*I'm sure there are more official, better ways to "remove root"
if that does result in a stable loading of system
install Magisk stable version
patch stock init_boot; flash it
install single module -- rebooting right after each one & confirm system stability before installing next one
maybe Magisk just needed to be intensively re-initialized
if that does not result in a stable loading system
remove Magisk
flash stock init_boot
flash stock kernel
if that does result in stable loading of system
it's your kernel, not Magisk
if that does not result in stable loading of system
lost cause
back everything up
flash Full Factory image with wipe included
Those are just things I, personally, would do -- take it as much as a suggestion as you will (as you probably did many of them already anyways). Good luck to you!

Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.
I am seeing some scary things in the logs:
"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."
and there are a lot of com.google.android.gms errors as if it doesn't even exist:
"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"

Flyview said:
Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.
I am seeing some scary things in the logs:
"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."
and there are a lot of com.google.android.gms errors as if it doesn't even exist:
"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"
Click to expand...
Click to collapse
I'm unsure, I don't know too much about "safe mode", but I just assume that if it all works in safe mode, it usually means it's a module -- in my experience, rooted users only enter that mode when there's an issue with Magisk and/or its modules.
And in the quintessential rooting guide in the P7P forum (and all his other guides), roirraW "edor" ehT suggests to disable modules before flashing the update (even if you are losing root) -- which I infer that modules can still mess with the system even if you don't have root access....
I'm unsure what else safe-mode disables -- if you research and figure that out, maybe you can narrow down what safe-mode is disabling that is causing your issue. Maybe uninstall the last 5-10 apps/modules you installed (if it's not Magisk related)? I doubt running in safe-mode reverts the kernel as well (so I can't imagine that's proving it), but maybe its the custom kernel (like something the custom kernel is interacting with it doesn't like and causing a glitch)?

I think the best thing would be to backup all your data and do a clean flash.

Rachid.Ala said:
I think the best thing would be to backup all your data and do a clean flash.
Click to expand...
Click to collapse
Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:
1) Disabled Digital Wellbeing with SwiftBackup last night.
2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.
[TEST MOD]Thermal-Throttling-Modifier[Pixel 6/Pro]
/* * Your warranty is now void. * I am not responsible for bricked devices thermonuclear war, or you getting fired because the alarm app failed * Please do some research if you have any concerns about what this MOD does before flashing it *...
forum.xda-developers.com
I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?

Flyview said:
Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:
1) Disabled Digital Wellbeing with SwiftBackup last night.
2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.
[TEST MOD]Thermal-Throttling-Modifier[Pixel 6/Pro]
/* * Your warranty is now void. * I am not responsible for bricked devices thermonuclear war, or you getting fired because the alarm app failed * Please do some research if you have any concerns about what this MOD does before flashing it *...
forum.xda-developers.com
I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?
Click to expand...
Click to collapse
Have you spent time on studying the log what's going on ?
I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.
- Reflash all system to check whether it's ok.
- Then disable digital wellbeing to check whether it's ok.
- If NG,how about enable it ?
- Next flash magisk module to check whether it's ok.
- If NG,how about removing it ?
I think it's not so hard to find out which one to result in so much error, right ?

Kris Chen said:
Have you spent time on studying the log what's going on ?
I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.
- Reflash all system to check whether it's ok.
- Then disable digital wellbeing to check whether it's ok.
- If NG,how about enable it ?
- Next flash magisk module to check whether it's ok.
- If NG,how about removing it ?
I think it's not so hard to find out which one to result in so much error, right ?
Click to expand...
Click to collapse
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.
I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?

Flyview said:
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.
I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?
Click to expand...
Click to collapse
I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.
But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....

Flyview said:
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.
I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?
Click to expand...
Click to collapse
Well, it seems that you live in the past... Until now, no twrp support for A13.
So you cannot manage to wipe specific partition.
simplepinoi177 said:
I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.
But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....
Click to expand...
Click to collapse
Yes!
Until now, no TWRP support for A13.

I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....
Google Pixel - Update and Software Repair
With this or anything else, good luck!

simplepinoi177 said:
I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....
Google Pixel - Update and Software Repair
With this or anything else, good luck!
Click to expand...
Click to collapse
Interesting! I might give that a shot but I have an
UPDATE:
I was up until 4AMtrying different things and somehow got it working again!?
Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?
After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.
Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?
So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.

Flyview said:
Interesting! I might give that a shot but I have an
UPDATE:
I was up until 4AMtrying different things and somehow got it working again!?
Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?
After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.
Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?
So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.
Click to expand...
Click to collapse
Curious/Interesting.... I always assumed clicking on the trash icon and rebooting simply but effectively uninstalled the module. But it's also why I stated that you should remove each module and reboot after each time....*very important the rebooting
I imagine somewhere between this
so I went back into safe mode. After some more time trying different things in safe mode
Click to expand...
Click to collapse
may be what corrected what was causing it to glitch...? That or, again, getting the module properly/completely removed or re-initialized properly corrected it -- we told you that it was most likely the modules; when things run smoothly in safe-mode, it's usually the culprit...
Tweaking with frequencies & thermal often end up with random glitches -- from my very limited experience of overclocking my CPU and GPU, the way to go about it is to tweak those things until just riiight about the system doing random reboots....It's easy to imagine this all being a symptom of such things...it's why I suggested even going back to stock kernel after removing all Magisk & modules....
Glad you stabilized your device though!