Develop Bugs

"Bricked" A100

It appears my A100 decided that it wanted to nearly 100% brick itself last night.
I'm stuck with only recovery at the moment and it is reporting that /dev/block/mmcblk0p4 and /dev/block/mmcblk0p8 are not found. I've tried plugging it into usb while in recovery to see about using ADB shell to recover the partitions but I cannot seem to get the USB drivers to recognize the device.
Anyone have ideas on what I can do as a next step?
Thanks to pio_maski and linuxsociety for helping us all out. For those just joining the thread:
pio_masaki said:
For everyone having the missing partitions error in this thread, once it starts its done, it began when the first freeze occurred.
At this point you have 2 choices, neither is fun and both involve Acer.
1 send it now and get charged for repair, they'll know its modded.
2 try to trigger fail safe and just plug it in, turn it on and let it sit and try to boot into android. After a set amount of failed /system or /boot reads it'll go into fail safe mode. Sending it under warranty in this state will have it repaired at no code aside from shipping to Acer.
You'll know fail safe is happening when you turn it on, blue or orange light comes on but the screen is off and there is no vibration on power on.
Both ways:
Get onto the Acer site and start a chat with a rep, tell them what happened. They'll ask you to hard reset after verifying warranty is still in effect time wise. After it fails this, they'll give you the info on sending it in. For me it took 10 days to get it back from sending it out.
Edit: for anyone that can still boot but hangs up, recovery may still be possible but its a very small window.
Click to expand...
Click to collapse
linuxsociety said:
If you have the brick, then there isn't any options left except to send it in to Acer for repair. They won't say anything about your ROMS/Kernels, however you need to find out if the stock bootloader needs to be re-flashed, and this will pretty much lock them out of recovery and everything when you do. They'll just end up replacing the board in the tablet and sending it back. I'm not 100% sure if anyone has sent their tablet in to acer with the a200 bootloader still intact and received their repaired tablet without a hassle, really that's the main thing you may want to check into.
Click to expand...
Click to collapse

I had the same thing happen to me last night.

Curious to know if you all were using stock kernels or a custom one? if custom which one?

linuxsociety said:
Curious to know if you all were using stock kernels or a custom one? if custom which one?
Click to expand...
Click to collapse
I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.

kemonine96 said:
I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.
Click to expand...
Click to collapse
The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.

linuxsociety said:
The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.
Click to expand...
Click to collapse
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.

kemonine96 said:
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
Click to expand...
Click to collapse
The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.
I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.

linuxsociety said:
The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.
Click to expand...
Click to collapse
Do the more recent recoveries include a good way to re-write the GPT partition table via an adb shell? Seems like if you can re-write the GPT partition table you'd be able to recover the device from mostly dead. Also, does the bug affect data stored on the various partitions? If so, are there images of the various partitions floating around?
linuxsociety said:
I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.
Click to expand...
Click to collapse
Speaking for myself, I find that I can mash the hardware keys more efficiently via muscle memory than touch about a touch screen. Probably my old graybeard keyboard ways shining through...
I considered moving over to TWRP but the last I looked the information was a little lean (~1-2 months ago now probably). I planned on looking closer at it once the JB port is further along for the A100. Figured I'd jump to TWRP when I jump over to JB. I am aware the CM9 versions for the A100 are a bit out of date and I'm working on a build to address that (running repo sync while I'm at work).

kemonine96 said:
What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...
I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.
Click to expand...
Click to collapse
At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.
As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with
It works with all existing roms from ICS to JB, stock or modified or CM.
Tapatalked from my Galaxy S II.

pio_masaki said:
At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.
As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with
It works with all existing roms from ICS to JB, stock or modified or CM.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.
If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.

kemonine96 said:
You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.
If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.
Click to expand...
Click to collapse
That is actually different from normal for emmc bricks, though makes sense too. If the file system is corrupt or missing then it would hog CPU time trying to find the data or fix the damage, if it even could.
Tapatalked from my Galaxy S II.

i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?

icomar said:
i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?
Click to expand...
Click to collapse
You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks
Sent from my A100 using Tapatalk 2

linuxsociety said:
You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
you are right, so:
1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.
I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?

icomar said:
you are right, so:
1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.
I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?
Click to expand...
Click to collapse
That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)
Sent from my A100 using Tapatalk 2

hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.
still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.
It is worse than before, am i right?

linuxsociety said:
That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)
Sent from my A100 using Tapatalk 2
Click to expand...
Click to collapse
He's bricking. If he wipes cache then he will finish the job.
Edit: never mind I didn't see his update.
Tapatalked from my Galaxy S II.

pio_masaki said:
He's bricking. If he wipes cache then he will finish the job.
Edit: never mind I didn't see his update.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
now what? too late?

icomar said:
hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.
still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.
It is worse than before, am i right?
Click to expand...
Click to collapse
Well it definitely doesn't look good now. So the boot animation was appearing before you tried to do all the wipes and install from CWM? I just wanted to verify that this DID in fact take place while booted into recovery. You may want to discuss this with pio_masaki since he had a brick happen to him recently, and he is quiet knowledgeable with the procedures to try to recover from lost partitions or to verify that you are indeed bricked (lost GPT partition info ) .

stock rom
my tablet(a100)is doing much the same, its stock except for crosix swap-mod ,i plug into pc(win 7) and it says apx not installed..last nite it locked up while reading,..and well..i rebooted it and all i saw was the android..

Use TWRP to flash 8.1 update

I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!

WyldOne91 said:
I feel like I should know how to do this and I just can't think right now...
I have 8.0 and the latest TWRP installed. Root with Magisk as well. I want to update to 8.1 but I don't want to have to factory reset the phone by flashing 8.1 to it and then reflashing root & TWRP. There's a way to do this that I'm not thinking of, right?
I read another post about using FlashFire but regardless of where I put the factory image, the app doesn't see it. So I feel like I'm at a loss right now.
Am I missing something? Thanks in advance!
Click to expand...
Click to collapse
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:

Badger50 said:
This is how I upgraded to 8.1, my setup before I upgraded was the same as yours.
1. Bootloader and unlock_critical both unlocked?
2. Download and extract the factory image, and place all contents in your SDK platform tools folder.
3. Edit the flash-all.bat file and remove the -w in the last line of code. (This prevents your data from being wiped)
4. Double click the flash-all.bat file to start the process. It'll take a little while, so be patient.
5. Once it's done, get back to bootloader mode.
6. Flash the twrp.img file. This will take you to temporary twrp.
7. Once in twrp, flash the twrp.zip, then flash custom kernel.zip(optional) then flash your magisk.zip.
8. Reboot and done.
Couple of caveats, make sure your using a good USB transfer cable, and it's recommended to remove your finger print and/or password/pin, and uninstall any themes you have installed. Hope all goes well for you :good:
Click to expand...
Click to collapse
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.

WyldOne91 said:
Cool thank you I will give this a shot later tonight! One question, what is "unlock_critical?" I haven't seen that mentioned anywhere else before.
Click to expand...
Click to collapse
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.

Badger50 said:
The pic is from the Google factory image page. Unlock_critical must be performed on the P2XL to allow the bootloader to be updated with future monthly security or software updates. This does not apply to the standard P2. Be advised, this WILL wipe your phone. However, you really don't have much choice if you want to flash monthly factory images.
Click to expand...
Click to collapse
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.

WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:

WyldOne91 said:
Oh crap... I only ran the OEM unlock. Welp, looks like I'm going to end up wiping anyways. Thanks for the info though. This is definitely one of those situations where I assumed I knew what I was doing and ran with it without actually reading the process.
Click to expand...
Click to collapse
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.

Badger50 said:
No problem my friend. There's a lot to learn on these new pixel devices. There are plenty threads on these forum with tons of info on whatever topic you may have questions about. Just takes time, patience, lots of reading, and a willingness to learn :good:
Click to expand...
Click to collapse
Yeah for sure. I'm always willing to learn!
CyberpodS2 said:
Since you are rooted, and already have the mindset that all is or will be lost you have the opportunity to try a couple options that if fail nothing lost...
After doing away with screen security and any themes, do Full backup in TWRP and also use TiBu to back up all your apps and then move them off the phone until after you do your thing.
After you do the critical unlock and get 8.1 installed and rooted you could try restoring the TWRP data partition and see what happens. Worst case it's either not booting or just acting funky. Do a factory wipe and not much lost.
Or... Use TiBu to save some time restoring all your apps. While I have had pretty good luck with restoring data on most apps, a few either won't restore or are boned in some way. Some other folks had a really hard time with restoring data so maybe just restore the apps without data. I run over 100 apps and have been through some version of this many times while playing around. With my crappy internet out here in the boonies it took 4 hours for google to restore all my apps and that's with hardly no data. It took about 20 minutes to restore most everything through TiBu. I would not restore data in the big initial bulk restore but instead go back and cherry pick the data restore on the things you need.
Again worst case all lost but you assumed that anyway and maybe you can save some time and effort if either option works.
Click to expand...
Click to collapse
Yeah I actually already ran a backup with Titanium Backup and moved it to my PC last night just in case I did something stupid haha but I appreciate the tips!

I am unable to make any ROM, TWRP stick.

I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?

Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk

Soooperstar said:
Have you tried a factory image with the -w as in wipe everything?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes, I have done all of the typical things and I am having very, very bad luck. Out of the box, thinking is critical.

Fixed!

Scottay5150 said:
I have FB factory, flashed ROM's and nothing is sticking. Might be corrupt storage. I was wondering if there is a more thorough way to wipe/flash the phone so I can make a ROM/OS stick?
Click to expand...
Click to collapse
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.

Bryanx86 said:
Fastboot format system, fastboot erase userdata, fastboot format cache. There was a guide somewhere someone had about clean flashing. I had an issue once but after totally wiping and a clean install of stock, I haven't had any issues since. Use the flash-all.exe to flash, idk if you flash your images separately, but flashing the zip as a whole through fastboot yielded better results for me. Also being sure that my adb.exe files were up to par. Also be sure to wipe both slots, as it might be slot b giving you problems. Google search should find you the right fastboot commands, I've forgot them off the top of my head. Of course if you're going to wipe you would need to back everything you need up.
Click to expand...
Click to collapse
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?

Scottay5150 said:
Yes, my SDK is up to date, from Google site. Interesting about flash-all.exe.
Fastboot format system
fastboot erase userdata
fastboot format cache
These were the commands you have used?
Anyone have beta how to wipe both a and b??
Does anyone want to link me to clean flashing?
Click to expand...
Click to collapse
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...

stebomurkn420 said:
You need to go back to square one.. Asking questions like this lead me to believe you have absolutely no idea what you are doing and you need to leave things alone before further damaging your device...
Click to expand...
Click to collapse
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.

Scottay5150 said:
OK folks. I want to apologize for my flooding of the forums attempting to repair my situation last week. Yes, I have been flashing for a long time without real complications. I haven't been on my ADHD meds for a while and that did not help me with the drama last week. Unfortunately my world like most of you is in my phone, I was panicked. Sorry about that.
Needless to say I needed other eyes on what I was doing for perspective sake. I went to my PC tech, luckily had personal flashing experiences with Android, Pixel even. We worked on it for about 6 hours in total. He couldn't get RR to work.
The issue was this after following the OP instructions. Once in the system I couldn't get the WiFi to connect with the phone, not being able to download whatever the phone was looking for. Google play services kept FC'ing. Google TTS kept FC'ing as well. I don't know if there is a fix or a forthcoming fix for this abnormal issue. I deleted data from the apps that were FC'ing and other Google that might be related. PS: not a RR issue I had this same issue with Benzo)
Unfortunately, we didn't save anything from the old RR setup because I couldn't be without a phone for another day. Any constructive thoughts would be welcomed.
I shall attempt to reinstall RR at some point to see if it works, or to get data to help the devs understand what might have happened or might had happened.
I am back on stock, not loving it that is for sure.
Click to expand...
Click to collapse
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.

borxnx said:
Sounds to me like you used the wrong GApps. Or maybe used the wrong TWRP, or tried installing TWRP when you should have just booted it. Something like that.
Click to expand...
Click to collapse
I wish I could say the wrong GAPPS, the version from the OP was used (others had issues as well), TWRP 3.2.0 again from the OP was installed per instructions. They were not. Not letting system boot up might have been the bigger issue. I shall never know.

Question Has anyone been able to restore nand backup since Android 13?

I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?

Aserar said:
I tried backup and restore on POCO F3 and I think it was successful on A11 but I dont think restore ever worked since A12. Always had error 255 at the beginning of restoring data partition. Has anyone been successful restoring a backup of android 13?
Click to expand...
Click to collapse
Of course. Backup and restore work fine on OrangeFox.

Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.
Requires Root, but you can always uninstall Magisk Root

DarthJabba9 said:
Of course. Backup and restore work fine on OrangeFox.
Click to expand...
Click to collapse
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of

cyanGalaxy said:
Bit unrelated, but I always use Swift Backup for backing up apps+appdata. It can backup other things as well.
Requires Root, but you can always uninstall Magisk Root
Click to expand...
Click to collapse
Yeah I do a swift backup also messages call log all of it but setting up the rest of the phone, logging back into accounts, is a pain, plus I always find an app or something that I forgot to refresh its backup. Nothing is like nand backup if you're testing new rom and might just go back

Aserar said:
Both OFX and TW failed me at restore I can't think of any reason why if it's working with others. Do you remove screen lock before backing up? Never had to before but it's the only thing I could think of
Click to expand...
Click to collapse
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.
And you might want to read this wiki very carefully.

DarthJabba9 said:
Possibly a result of user error. If you explain the process that you went through in order to restore the backups, and provide logs of the restore process, then I might be able to comment.
And you might want to read this wiki very carefully.
Click to expand...
Click to collapse
Oh I've gone through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though

Aserar said:
Oh I've went through the ofx wiki before with no success. It could be the screen lock on EU A13 roms. I had the issue two times then I gave up on backing up roms. I didn't care to save a log sadly bc I was in a hurry to get the phone working again. The restore process was straight forward. Restore from OTG. It starts normally and as soon as it hits restoring /data it ends with error 255. It doesn't start restoring data then fails after a while. It fails instantly as soon as restore data partition appears. I'll try without screen lock if it still fails I'll send you the log. Thank you for your hard work though
Click to expand...
Click to collapse
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.
2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.
3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).
4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.

DarthJabba9 said:
1. Idk about EU. But I have backed up and restored stock MIUI 14 many times, with no problem.
2. "Error 255" is always accompanied by an explanatory message in the recovery logs, which will show what caused the error.
3. Firstly, ensure that your OrangeFox is actually up-to-date (ie, that you are using the latest release).
4. Whether or not you have a screenlock before making the backup should not affect anything (as long as there is no screenlock set up at the time of restoring the backup). The lockscreen PIN/password is not included in the backups.
Click to expand...
Click to collapse
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.

Aserar said:
Yeah screen lock was never an issue before but it is the only thing I could think of. It could be something with EU. And yes I keep recovery up to date even when I don't switch roms. I made a backup of AOSP rom that I will probably restore soon. I'll keep you updated if the issue persists.
Click to expand...
Click to collapse
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).

DarthJabba9 said:
Well, I have now made backups and restores of the latest EU ROM (14.0.6.0) - boot and data partitions - without any problem (both with and without screen locks - obviously there must be no lockscreen PIN/password when restoring).
Click to expand...
Click to collapse
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/

Aserar said:
And I restored my AOSP backup with no errors! I wish I hadn't deleted my EU backup that I got the error with. The EU rom I had was the latest weekly release V14.0.23 bc the official release had issues but I doubt its that. I'm at a loss :/
Click to expand...
Click to collapse
Do you have a link for that release?

Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.

DarthJabba9 said:
Do you have a link for that release?
Click to expand...
Click to collapse
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.23.4.10.DEV/xiaomi.eu_multi_HMK40_POCOF3_V14.0.23.4.10.DEV_v14-13.zip/download

johnr64 said:
Sorry for also deviating, just my two pennies worth,
I moved away from Migrate-GPE and Swift backup and have been using DataBackup.apk, this also requires root.
Click to expand...
Click to collapse
Is this on the Play Store?
johnr64 said:
As usual DB saves your Apps and there Data, you also have the option to save Media Folders, DCIM, Download, Music, Pictures, Folders, i also save these to my Usb Stick using a OTG adaptor, DataBackup can be found is my "Temporary Recovery" folder.
Click to expand...
Click to collapse
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.

Aserar said:
Honestly I can't be sure of the exact release since its weekly. I looked it up and I can narrow it down to like 3 or 4 releases but it could be this one
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-WEEKLY-RELEASES/V14.0.23.4.10.DEV/xiaomi.eu_multi_HMK40_POCOF3_V14.0.23.4.10.DEV_v14-13.zip/download
Click to expand...
Click to collapse
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.

DarthJabba9 said:
I have backed up and restored this release as well, with no problem. I have satisfied myself (again) that there is no problem with backup/restore in OrangeFox Recovery, so, for me, this investigation is concluded.
Click to expand...
Click to collapse
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.

DarthJabba9 said:
Is this on the Play Store?
Having an alternative backup plan is good. But I have always found nandroid backups sufficient - as long as you know what you're doing.
Click to expand...
Click to collapse
Sorry for not getting back sooner,
I found DataBackup while watching youtube videos "Like You Do",
the source is on GitHub

Aserar said:
Lol there was no need for investigating my friend! The point of the thread was to see if its generally working with others and so eliminate it as the reason for the fail.
Click to expand...
Click to collapse
It's no big deal. I always try to investigate problems, since they might possibly point to a problem in the recovery.

Same here. Since a12 that nandroid gives error on restoring. After that I don't count with that anymore. Ive been relying on Google to restore some apps, and on swift backup to restore the ones that are out of ps.
Before I was using migrate, but have put it aside, since the last time I've got error on zip file and so unable to restore my apps (a real pita). Swift have working flawlessly, and with the advantage of restore app settings too.

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!