Develop Bugs

(A Type of) Random Reboot Problem Solved?

Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.

Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.

Factory reset on a corrupted Android OS?

So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.

I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again

Auto rotate doesn't work

Hi All, my redmi 5a auto rotate doesn't work, I don't know why but I've experienced a tragedy that maybe connected with this problem.
I use AOSP Extended ROM for Rolex in my Redmi 5A Device, as long as I use it I don't have any problem, but yesterday I've tried to restore my kernel into this ROM Stock Kernel ( I Use Direwolf Unified Before, Many Times I Try Other Kernel Also But And Never Had Such A Tragedy) After I Restored the original kernel, then I wipe my dalvik and cache as usual, BUT, Suddenly The Boot animation Stucked before it show's the AEX Logo, So I Think It Was A Bootloop Simple Problem, Than I Reinstalled My AOSP Extended OS, Than Something Happened, Even Since The First Boot It's Stucked At The Same Point, Than I Tried To Re-flash it again, and after that it still like that, so I was thinking that my External Memory Data Was Corrupted, So I Tried To Copy The File Directly From My PC To My USB OTG (I copied same AOSP ROM) than I reflash it but it still like before, than i start thinking if this ROM file (in my PC and SD card) is corrupted, so I tried to install PE ROM, But The Result Is Still Same As Before, Stucked At Boot Animation Than Forced Shutdown.
Well after that I think my device is get a serious problem such as hard brick or soft brick, than I tried to do clean flash to MIUI 10 Fastboot ROM With My PC, BUT the time elapsed is more long than usually (About 20 minute) waiting for booting and finally my device is normal, so I immediately install TWRP Custom Recovery (3.2.3-1 by FenFern) And Installing AOSP ROM Again (I Swear I Love This ROM) Everything seems normal no problem, restoring app, rooting, personalization, and etc.
Well the problem with auto rotate is coming when I see some funny videos on YouTube, my devices ONLY CAN ROTATE TO THE LEFT, AND CAN'T ROTATE AUTOMATICALLY AND CAN'T ROTATE TO THE RIGHT SIDE, I tried many game's app and watching some anime's in video player, Even If I Switch to auto rotate mode.

hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?

SandipS said:
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
Click to expand...
Click to collapse
Well yeah it's working, except the auto rotate

Question Pixel 6 Soft Brick with OTA

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

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.