Database Develop

[HELP] Moto X won't boot to OS after strange happenings...

Rooted, Bootloader unlocked, TWRP installed, Xposed Running. 5.0 - I did not yet update or press update ever, If I have ever accidentally allowed it to begin downloading I kill the download by deleting the file using SDMaid.
I got home, had problems with other devices, phone was on about 40% at this point. I remember hearing the phone reboot, I noticed it went into TWRP, which was strange, I restarted system > powered up > lockscreen > restart to twrp with no interaction. Phone is now getting low 21%ish. Fix permissions - because used to be the all out fix on my other devices.
Same thing again > straight into twrp.
I notice that some scripts have been ran in the twrp console. Something along the lines of Victara_en_US.zip Some red scripts I assume saying failed to update.
I assume the phone is now too low to power up.
It shows no sign of charging since leaving the last twrp reboot.
Green light in top speaker shows when attempting to power up with usb charger plugged in > nothing else happens.
With charger unplugged from phone I see my modified logo screen and the moto planet spinning before phone turns off completely. This process now repeats.
Anyone have any idea what the hell is wrong with my phone?
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...

THE-M1GHTY-BUKO said:
EDIT UPDATE:
Managed to get into the fastboot menu:
Battery Low (RED)
Device is UNLOCKED status code 3 (YELLOW)
Software status modified (YELLOW)
As normal aside from Battery...
Click to expand...
Click to collapse
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.

mikeoswego said:
Get your phone into TWRP and connect it to your charger and let it charge to at least 70% Use Advanced Wipe in TWRP, select Cache and wipe that. Then see if your phone will start normally. Somehow you have downloaded the update file and it is trying to run automatically. Since your phone is modified, the update fails (and nothing is updated or changed.) The update file is in /cache so wiping that should correct the problem. You should go ahead and update to the Stagefright patched version of your ROM so you aren't having to deny the factory update all the time.
Click to expand...
Click to collapse
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.

This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.

TyNote3Krill said:
This happened to me a couple times but wiping the cache AND the dalvik cache fixed it. If it still doesn't work, I hope you have a backup because you are going to have to wipe the system and data next. Sometimes these updates like to link themselves to all the phone's partitions, and in that case you should wipe everything and restore your full system and data backup in recovery.
Click to expand...
Click to collapse
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?

THE-M1GHTY-BUKO said:
I wiped both the first time I tried it :-/
I don't have a system backup as a far as I am aware, need to check main pc for something like that. I had a lot of trouble with no signal after changing my phone to x1095 so I could root it etc. Just hope I don't have the same trouble again. Can i reinstall the system through twrp? Or do I need to flash via fastboot?
Whats my best option, system files wise, for fixing this?
Click to expand...
Click to collapse
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.

TyNote3Krill said:
If you dont have a backup, at this point, I don't see any other options besides formatting your data or flashing the stock firmware. Of course, don't just take my word for it, but in the future just make sure you have a working backup available.
Click to expand...
Click to collapse
Am I able to flash anything other than the stock 5.0? Last I checked I had converted whatever I had to the x1095. I remember everything being easier on other phones...

Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.

THE-M1GHTY-BUKO said:
Attempting this now....
Phone still boots to a black screen. I don't understand why it would download the update let alone attempt to install it, I religiously deny the update. Also why would it have booted up normally then forced itself into TWRP? :S
What can I next? I dont mind wiping using fastboot as I managed to take all my files off the phone via twrp.
Click to expand...
Click to collapse
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.

TyNote3Krill said:
Yes, you can, just make sure you have the right file for the job. They are usually about 2 gigs, and they take forever to flash. Note that once you flash the file, your phone will be as if you just bought it from the store, but it always will boot if you have the corresponding build.
Click to expand...
Click to collapse
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.

mikeoswego said:
In TWRP, make a backup now even though it may not be useful depending on what the problem is. Then, use advanced wipe in TWRP and wipe data. If the phone will boot now, something got corrupted in data and you'll just need to set your phone up again. If the problem continues, you'll have to flash your system image. How to do this varies with the model of your phone; some models have TWRP images, others need to use fastboot files. After you flash the new system image, you can either just continue to clean setup the phone, or you can try to restore only data from the backup you made previously.
Click to expand...
Click to collapse
I tried wiping data to no avail.
Im trying to download stock 5.0 for now but the download is taking decades for some reason. Do you, or anyone else, recommend any roms which I can easily flash without having to worry about modem files?

THE-M1GHTY-BUKO said:
Does that include 5.1 roms? I can never seem to find x1095 5.1 roms, or anything for that matter, they are all titled with every other version.
Click to expand...
Click to collapse
Hopefully this could provide more information for your situation?
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945

Thank you for your help, as well as anyone else who helped me. I now have a running phone on 5.1.
How do I gain root from here? My superuser app updated and now tells me I have no binary, despite telling me to flash something only 5 minutes prior.
Sent from my XT1095 using XDA Free mobile app

So you don't have root? I would suggest rooting using towelroot. Go online and search "towelroot" click on the first result, click on the lambda to download the apk, and install it. You can then open the app, and press "make it ra1n" to root your device without any reboot needed.

I had root prior to wiping and installing the 5.1 update that was linked to me. Towelroot gives me the phone not supported message.
Sent from my XT1095 using XDA Free mobile app

Towel root does not work in 5.1.
To root just flash TWRP. Start TWRP. When you exit TWRP it will ask you if you want to root it. Simple.
Sent from my XT1095 using Tapatalk

I'm still in the "phone not responding" phase.. how did you manage to get in the bootloader from there? Tnx!

I found a chainfire autoroot IMG that rooted my phone. Found xposed too. I'm back at a fully working phone now, thank you to all who helped me.
Gotta say, the battery life on 5.1 is a hell of a lot better.
Sent from my XT1095 using XDA Free mobile app

As in you can't get it to fastboot?
I left it to charge for a while, then took about 5 minutes attempting the power button volume button combo to restart and get it into fastboot.
I believe that it's something like:
Power + vol down until the phone screen flashes/green light goes off
Then
Still holding the power and volume down
Hold the vol up too
Then release the power still holding the vol up and down.
That's what worked for me. It's literally the most awkward phone I've had go button combos.
I think vol up from powered off works too.
If you mess up just hold the power and vol down again.
Sent from my XT1095 using XDA Free mobile app

Help !! - bootloader suddenly got locked, no more recovery

I have had an unlocked Nexus 6 running TWRP and custom rom with no problems at all. Today when I tried to boot into recovery I got the stock screen instead of TWRP. At bottom it says 'Device is locked status code 0'. When I go into barcodes I see a date of 1-1-1970. Also see a 'unable to load partition table error'.
Rebooting into my current rom (Pure Nexus) works fine if I power off and restart. So how did this happen and what do I do next? I did absolutely nothing recently, had no errors in phone usage. Just wanted to update the rom and now this.

Is it a secondhand phone? Did someone remote lock it with Android device manager or W/e?
Sent from my Nexus 6 using Tapatalk

ECrispy said:
I have had an unlocked Nexus 6 running TWRP and custom rom with no problems at all. Today when I tried to boot into recovery I got the stock screen instead of TWRP. At bottom it says 'Device is locked status code 0'. When I go into barcodes I see a date of 1-1-1970. Also see a 'unable to load partition table error'.
Rebooting into my current rom (Pure Nexus) works fine if I power off and restart. So how did this happen and what do I do next? I did absolutely nothing recently, had no errors in phone usage. Just wanted to update the rom and now this.
Click to expand...
Click to collapse
I think you have a hardware problem, and the date being set to the beginning of the Unix clock is a dead giveaway. Where you still have a ROM, you have something you can try. I assume you have OEM Unlock enabled, so connect your Nexus to the PC and try unlocking the bootloader. If it unlocks, then try flashing TWRP. If it doesn't work, pray you still have a warranty. If you do, contact Motorola and set up a RMA through them.
As to how this happened, there's no way to tell from here. But it's not the first time it's happened to someone on this forum. The last time it happened, they had no OS and no recovery to work with, meaning a brick.

EeyoreSyndrome said:
Is it a secondhand phone? Did someone remote lock it with Android device manager or W/e?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No it is a new phone I bought in Oct, no one else has access to it.

How did you try booting into recovery? Through an app or roms power menu? Or by pressing power and volume down from a powered down state to get into bootloader and then go into recovery?
I've seen something similar a couple of times when I've tried booting into recovery from an app. Scared the **** out of me the first time, but I just needed to power off and boot up with the button combination instead.

[SOLVED] December-Update Softbrick

Hi,
My P4XL is/was rooted with Magisk. Then today i tried to install the december update exactly like written here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
After clicking on reboot in magisk, booting up took ages. After 20min. i forced another reboot and waited another 20min. At this point i quit waiting and decided something went wrong.
I tried to go back to the november update by flashing the full factory image 10.0.0 (QD1A.190821.014, Nov 2019) from the google download page.
Now when i try to boot or go to recovery or rescue mode i alwas get to the fastboot screen with the following information:
Code:
Bootloader version: c2f2-0.2-5799621
Baseband version: g8150-00014-190826-B-5830341
Device state: Unlocked
Boot slot: a
Enter reason: error booting boot.img
Is it, cause i already made the update and cant go back to november?
Any ideas how i get my device fixed?

How about your slot-b system ?
Try to switch into slot-b and boot it !
Kris

Kris Chen said:
How about your slot-b system ?
Try to switch into slot-b and boot it !
Click to expand...
Click to collapse
That seems like a good idea. Thanks. I will try that later when i get home from work. Will report back.

Update: Switching slots did nothing, sadly.
I tried to flash the November Factory Image and December Factory Image. I always end up stuck in bootloader mode: "Waiting for device".
So, for everyone with the same issues finding this thread, here is the solution:
Now (not with a lot of confidence) i sideloaded the full ota image for december (bootloader mode, select corresponding option), that is thankfully now available from the google page, aaaaaaaaaaaand its booting again. Yay.
Just to be sure that everything is alright, i flashed the whole factory image again, this time it was working fine.
Now all is ok again and im on the december update. Thank god. That was a stressful day haha.
Still weird that i couldnt flash the factory image, but the ota was fine... Any idea why?

Aiakio said:
Update: Switching slots did nothing, sadly.
I tried to flash the November Factory Image and December Factory Image. I always end up stuck in bootloader mode: "Waiting for device".
So, for everyone with the same issues finding this thread, here is the solution:
Now (not with a lot of confidence) i sideloaded the full ota image for december (bootloader mode, select corresponding option), that is thankfully now available from the google page, aaaaaaaaaaaand its booting again. Yay.
Just to be sure that everything is alright, i flashed the whole factory image again, this time it was working fine.
Now all is ok again and im on the december update. Thank god. That was a stressful day haha.
Still weird that i couldnt flash the factory image, but the ota was fine... Any idea why?
Click to expand...
Click to collapse
Just a couple of ideas as to why the factory image failed. Were platform-tools up to date? How long did you wait when the output screen said "waiting for device"? I had to wait a couple of minutes for mine to kick in. Could've been a cable issue as well

Badger50 said:
Just a couple of ideas as to why the factory image failed. Were platform-tools up to date? How long did you wait when the output screen said "waiting for device"? I had to wait a couple of minutes for mine to kick in. Could've been a cable issue as well
Click to expand...
Click to collapse
Platform tools is always up to date. First thing i check before i use adb/fastboot.
Ok well, i didnt give it much time. Maybe i was to impatient.
Cable is original google. Everything worked fine so far with it.

At least, sideload saves your phone. But I cannot understand why factory full image cannot be flashed? I never have this problem.
Try to get into recovery mode and wipe every thing and try it may have help.( Ofc, you will lose every thing after doing that. Be carefully.
Aiakio said:
Update: Switching slots did nothing, sadly.
I tried to flash the November Factory Image and December Factory Image. I always end up stuck in bootloader mode: "Waiting for device".
So, for everyone with the same issues finding this thread, here is the solution:
Now (not with a lot of confidence) i sideloaded the full ota image for december (bootloader mode, select corresponding option), that is thankfully now available from the google page, aaaaaaaaaaaand its booting again. Yay.
Just to be sure that everything is alright, i flashed the whole factory image again, this time it was working fine.
Now all is ok again and im on the december update. Thank god. That was a stressful day haha.
Still weird that i couldnt flash the factory image, but the ota was fine... Any idea why?
Click to expand...
Click to collapse

Did you boot after flash magisked boot.img of december?
I got december update by fastboot & flash.bat file, and flash magisked boot.img,
but my Pixel4 gets bootloop. (after boot, it goes to the 'Google' boot screen, and repeat on and on.)

dev311k said:
Did you boot after flash magisked boot.img of december?
I got december update by fastboot & flash.bat file, and flash magisked boo.img,
but my Pixel4 gets bootloop. (after boot, it goes to the 'Google' boot screen, and repeat on and on.)
Click to expand...
Click to collapse
I tried to. But didn't work. I was stuck at the G-Logo. No bootloops though.
Maybe try to flash and boot with original boot.img? Can flash magisk still after that.

Aiakio said:
I tried to. But didn't work. I was stuck at the G-Logo. No bootloops though.
Maybe try to flash and boot with original boot.img? Can flash magisk still after that.
Click to expand...
Click to collapse
Maybe we have to wait next Magisk

I'm using Magisk Canary. Running great so far on December update. GPay is working too.

Aiakio said:
Hi,
My P4XL is/was rooted with Magisk. Then today i tried to install the december update exactly like written here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
After clicking on reboot in magisk, booting up took ages. After 20min. i forced another reboot and waited another 20min. At this point i quit waiting and decided something went wrong.
I tried to go back to the november update by flashing the full factory image 10.0.0 (QD1A.190821.014, Nov 2019) from the google download page.
Now when i try to boot or go to recovery or rescue mode i alwas get to the fastboot screen with the following information:
Code:
Bootloader version: c2f2-0.2-5799621
Baseband version: g8150-00014-190826-B-5830341
Device state: Unlocked
Boot slot: a
Enter reason: error booting boot.img
Is it, cause i already made the update and cant go back to november?
Any ideas how i get my device fixed?
Click to expand...
Click to collapse
Don't bother trying to preserve root -- I often find it causes more problems then anything. This may take a little longer, but it has always worked for me:
- download and extract the factory stock image from Google and place into your adb folder
- extract the boot.img file and copy it to your phone (I place mine into the download folder)
- edit the flash-all.bat file and remove the "-w" from the script. '-w' is the command that wipes your phone's personal data
- reboot phone into bootloader
- run the flash-all.bat and let it do it's thing. When it gets to <waiting for device>, don't touch the phone and be patient. After 2-3 mins, it will run through the update gauntlet
- let the phone reboot and wait for the updates to finish
Proceed with re-rooting using the Magisk Manager method, but a quick summary:
- Open Magisk Manager and patch the boot file
- copy magisk_patched file to your adb folder
- boot into bootloader and flash the patched image
A little slower than the OTA, but definitely will be rooted without any issues. I just updated to Dec and re-rooted without any issues.

patched dezember boot.img please

hanschke said:
patched dezember boot.img please
Click to expand...
Click to collapse
This is the stock, and patched December boot images. Your welcome :silly:
https://drive.google.com/file/d/18FqwDgmCE6zsiENxNTlrUqlEa35X64E7/view?usp=drivesdk

An FYI, yeah, you can flash almost anything with the cable in the box, what you'll have problems flashing is the full factory image. You need a USB A to C to reliably flash the full image. Yeah, I know it's crazy that the cable in the box doesn't work and it sounds stupid and I must be wrong. I'm not asking for trust, just have an A to C on hand and try it after you fail with the C to C from the box. Don't get all jiggy, do nothing else other than try flashing again but with the A to C. You should be ok and just need to flash the boot afterwards.

krabman said:
An FYI, yeah, you can flash almost anything with the cable in the box, what you'll have problems flashing is the full factory image. You need a USB A to C to reliably flash the full image. Yeah, I know it's crazy that the cable in the box doesn't work and it sounds stupid and I must be wrong. I'm not asking for trust, just have an A to C on hand and try it after you fail with the C to C from the box. Don't get all jiggy, do nothing else other than try flashing again but with the A to C. You should be ok and just need to flash the boot afterwards.
Click to expand...
Click to collapse
Welcome to the Wonderful World of Pixel Craziness... Been this way since the 2XL. Lol Just keep preaching the word whenever you can. Folks are hard to convince until they experience it themselves. ?

Yeah, I've had most of the Nexus and following them Pixel devices among many others, there has been some real headscratchers along the way. I've read the conspiracy theory that they do it on purpose to deter flashing. I've no idea on that but it is a reported bug so they know.

Some anoying problem - cant use my device anymore

Hi, I have the Pixel 4 XL, yesterday I just unlocked its bootloader and flashed the patched boot.img, probably "QQ1C.191205.016.A1, Dec 2019, SoftBank, TW carriers" but my device is Unlocked, so maybe It should be patched by another factory image, anyway after some minutes the face unlock stopped to work, I tried to delete face details and repeat the process again bug cannot do... I decided to flash again factory image, and now every time that I clicking the standby button and click it again to use the phone - I see only black screen, the battery and clock icons are flicking I dont know what to do? any idea? thanks!

Assafaviv said:
Hi, I have the Pixel 4 XL, yesterday I just unlocked its bootloader and flashed the patched boot.img, probably "QQ1C.191205.016.A1, Dec 2019, SoftBank, TW carriers" but my device is Unlocked, so maybe It should be patched by another factory image, anyway after some minutes the face unlock stopped to work, I tried to delete face details and repeat the process again bug cannot do... I decided to flash again factory image, and now every time that I clicking the standby button and click it again to use the phone - I see only black screen, the battery and clock icons are flicking I dont know what to do? any idea? thanks!
Click to expand...
Click to collapse
Sure. When you flashed the full image (not OTA) did you edit the flash-all.bat script to prevent wiping by removing the -w flag? If you did prevent wiping, try again and allow the install to wipe your data. As for which image to flash, check HERE... but flashing an image not for your region is not going to cause the issues you describe.

v12xke said:
Sure. When you flashed the full image (not OTA) did you edit the flash-all.bat script to prevent wiping by removing the -w flag? If you did prevent wiping, try again and allow the install to wipe your data. As for which image to flash, check HERE... but flashing an image not for your region is not going to cause the issues you describe.
Click to expand...
Click to collapse
No, I did not edit the script... And tried many of them... I don't know what to do

Assafaviv said:
No, I did not edited the script... And tried many of them... I don't know what to do
Click to expand...
Click to collapse
Flash the correct image per my link, and then do a factory data reset from recovery. Barring any hardware issues this will return your phone to "out of the box" state.

Booting issue after logo? Status bar and back button flashing

So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?

Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.

Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.

DarkusRattus said:
So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?
Click to expand...
Click to collapse
This happened to me too, I originally thought if was the Rom however dirty flashing the Rom again didn't fix it nor did dirty flashing stock image
What I do know is, this happened to me as soon as forced stopped gms services and removed GMS dose from magisk. As soon as I rebooted, this happened

Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It's kinda strange because I didn't touch anything for some days, and after a normal reboot this happened.
I tried restoring the stock boot.img from fastboot -> same issue
Reflash entire factory image without the "-w" so without wiping -> same issue
Even reboot in safe mode -> same issue
I don't think it's magisk fault because happened randomly the last 2 times, but I'll give your method a try if this happens again

It sure is giving off system UI crashing vibes. I definitely agree that this is an issue caused by something you did, not something inherent to the Pixel 4. Like suggested already, I would uninstall magisk as a next logical step since you've tried many of the other things I would have suggested. I wholeheartedly agree with Tulsa that this is a bad flash. Since you didn't wipe userdata when you flashed the factory image, the bad flash is still present so it's pretty safe to assume that you have a bad module installed or a bad combo of modules that don't like working together.

Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?

DarkusRattus said:
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?
Click to expand...
Click to collapse
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.

Tulsadiver said:
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.
Click to expand...
Click to collapse
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.

DarkusRattus said:
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.
Click to expand...
Click to collapse
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.

Tulsadiver said:
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.
Click to expand...
Click to collapse
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.

DarkusRattus said:
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.
Click to expand...
Click to collapse
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.

Tulsadiver said:
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.
Click to expand...
Click to collapse
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.

DarkusRattus said:
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.
Click to expand...
Click to collapse
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).

Tulsadiver said:
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).
Click to expand...
Click to collapse
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.

DarkusRattus said:
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.
Click to expand...
Click to collapse
I don't know how old your phone is but the slots are used for when you receive firmware updates and don't change unless you receive one over the air. You can change it manually in fastboot
fastboot --set-active=a
Try that then install your firmware again. It should now just reference B a few times.

TENN3R said:
Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.
Click to expand...
Click to collapse
Did you have FDE.AI installed by any chance? And what kernel were you using?

DarkusRattus said:
Did you have FDE.AI installed by any chance? And what kernel were you using?
Click to expand...
Click to collapse
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue

TENN3R said:
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue
Click to expand...
Click to collapse
I also feel that it's the issue, although I was using the FDE.AI app, so I guess both methods of installation can cause it. After the nth time resetting my phone, I just changed kernels and uninstalled FDE.AI and for a solid week now I've been booting fine.
Edit: wow I just looked at the thread and it looks like something went down over there.