Question Pixel 6 Soft Brick with OTA - Google Pixel 6 Pro

Anybody else with this problem? My 6 Pro gets soft bricked with the
SD1A.210817.036.
It loses the signal (Tmobile) then restarts to recovery saying
“Cannot Load Android System. Your Data May Be Corrupt” It gives me the option to "Try again." or to "Factory data reset."
Device Completely stock
This is what I have done
1
Try Again (Same behavior)
2
Factory Reset (Multiple times), would let me finish the setup but as soon restores my data and apps happens all over again.
3
Sideload Rescue OTA (SD1A.210817.036.) same ****
4 now with heavy weapons
Unlocked bootloader, manually flashed factory images (Unlocked) the factory image it's an older version but seems to work perfectly (I'm able to set up and restore my data, but the phone automatically downloads the OTA update and the same thing all over.
5
Got a device replacement (Hella lucky they had my device in stock)
6
Different new Pixel 6 Pro Same behavior as soon the OTA hits and finishes to restore my apps.
7
Tried Manually flash, use the online google tool with different builds (tried the Tmobile stock)
Always the same problem.
There's any way to wipe/repartition only the System portion? I remember having something similar back in the days with an S2 and was able to fix it with a Reflashing of the PIT partition through Odin
Any suggestions?

Only thing I see consistent is the data being restored. That data could be corrupted. Not sure if that's possible. Try setting up as new device or from a different backup.

I think"new device" is the way to go. Over the years I've found some apps don't work with a new update.

Points 5 and 6 suggest that it's something to do with your data and app restore causing the issue.
How modified was your previous device?

Just got my Pixel 6 Pro yesterday. I have had to restore 3 times. The first two were from a back up and the third time, from scratch and the same thing is happening. It took a while for the third time to happen (over night and a few hours into the day) and I thought I was safe and put a screen protector on and then bam! Just before it happens I get a lot of the Google apps like phone app and some heat app crashing, then it reboots and says Android is corrupt.

Corrupted data error message after December update
Hi! Is everyone else here struggling with Corrupted data error message after December update? Pixel asks to wipe data, but even if you do, it still do the same on the next reboot. There's Reddit thread about that going on:
forum.xda-developers.com

Related

[Q] Updated to 4.3, now GApps continuously force closes

I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.

[Q] Android 4.4.2 Issues

Issue resolved.
MiasmicTaco said:
This morning my Razr M received the latest OTA update. I was previously rooted with a locked bootloader (I know, bad choice).
I proceeded with the update but my phone massively screwed up: lost wireless, contacts malfunctioned, several apps failed.
I went through all the steps to clear cache, soft reset, hard reset, etc. Ever sense my phone has been stuck on the setup wizard screen stating "Please wait, this may take a few minutes". I left this morning at noon returned home at 7 and it is still on that screen.
Click to expand...
Click to collapse
Try using RSD to restore to the same version (4.4.2). I've gotten that wireless issue before, and I just had to format userdata and reinstall the update to get it working.
just roll back to orginal firmware by using RDS and after that,use OTA update

HTC One M8 Memory/Nand Corruption?

Had this M8 for a few months now after bringing it back from a bad software install by another user (here http://forum.xda-developers.com/htc-one-m8/help/m8-qhsusbbulk-rebooting-t3437240), was on a stock rom up until 2 weeks ago (restored from a nandroid backup provided by user on xda) until all apps seemed to force close constantly, I also could not connect to any mobile network, kept complaining of no sim card, no imei and unknown baseband. Tried a reset and a restore from the nandroid backup, neither of these worked, the phone would turn on and would get to the HTC boot screen then black screen continually, no amount of restore or reset fixed it, I also formatted and repaired the file system a few times, again made no difference.
Ended up going on to a custom rom which has worked for about 2 weeks up until today, again being presented with force closes in apps and the mobile network again will not work, complains of no sim card as before.
I'm thinking the nand (where the actual system and data partitions are) is basically dying and is not working correctly, anyone experienced similar?
Reflash of firmware via fastboot oem rebootRUU and another restore of a stock rom via twrp has fixed it once again, still clueless on why this randomly continues to happen

Question Soft Reboots After Every Reboot [SOLVED]

EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.

Android 12 disaster

My phone recently updated to Android 12. Ever since I have a few problems.
1. Signal says 4g instead of LTE and sometimes doesn't load webpages giving that error with a gray screen.
2. Android auto crashes after being on for 30 seconds.
3. The whole phone crashes and reboots if I use Chromecast
Do a clean load... after a factory reset and see what you got. Be sure all critical data is redundantly backed up... now.
Was hoping not to do a clean wipe but it that's what it takes
One reason I never upgrade firmware that is fast, stable and fulfilling its mission. It's not worth the trouble and wasted time it will cause.
After a major firmware upgrade a factory reset is best practice. Clearing the system cache from boot menu may help.
i always do factory resets after any major OS update on any device. that way you have a fresh out of the box experience .

Categories

Resources