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.
Related
Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is here: http://www.youtube.com/watch?v=KEP9aJzUFGo
dh2311 said:
Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is uploading as I type this, allow 20 minutes (my internet is that bad)
Click to expand...
Click to collapse
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
skinsfanbdh said:
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
Click to expand...
Click to collapse
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
dh2311 said:
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
Click to expand...
Click to collapse
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
skinsfanbdh said:
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
Click to expand...
Click to collapse
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
dh2311 said:
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
Click to expand...
Click to collapse
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
skinsfanbdh said:
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
Click to expand...
Click to collapse
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
dh2311 said:
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
Click to expand...
Click to collapse
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
skinsfanbdh said:
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
Click to expand...
Click to collapse
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
ive had that also i just restored my backup and quit for the day then tried the next day and it worked
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
try with re-downloading the file and put it in root of your sd card
rambo12345 said:
try with re-downloading the file and put it in root of your sd card
Click to expand...
Click to collapse
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
dh2311 said:
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
Click to expand...
Click to collapse
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Okay, in a weird turn of events, I thought i would rather than going to an RUU just wipe everything and reinstall everything, and the Aroma installers for the ROM and tweaks are working so far...
EVERYTHING WORKED! Dont know whether it was the wipe, just luck, installing using only volume keys and power button. But this seems to have gone away :fingers-crossed:
nolimit78 said:
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Click to expand...
Click to collapse
I could well be... have some working now, but if one breaks, Ill try reinstalling using volume keys and power button and never touch the screen
awesome. glad you got through it bro:good:
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.
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.
Is anyone else having an issue where their device will randomly reboot, and then when it boots back up it boots to a stock wallpaper and is endlessly stuck on "Pixel is Starting"? I know one time through a combination of rebooting I got it to work and boot again, but the last time it happened and this time I had to factory reset my device (Fully, not just a data wipe) and I want to know if it's my hardware or something I flashed? I do have the Hardware Off module and this never happened until after I flashed that module.
When this happens too data totally fails to decrypt, so I want to think it's the Hardware Off Module messing with encryption somehow, but idk.
ryaniskira said:
Is anyone else having an issue where their device will randomly reboot, and then when it boots back up it boots to a stock wallpaper and is endlessly stuck on "Pixel is Starting"? I know one time through a combination of rebooting I got it to work and boot again, but the last time it happened and this time I had to factory reset my device (Fully, not just a data wipe) and I want to know if it's my hardware or something I flashed? I do have the Hardware Off module and this never happened until after I flashed that module.
When this happens too data totally fails to decrypt, so I want to think it's the Hardware Off Module messing with encryption somehow, but idk.
Click to expand...
Click to collapse
How did you "fully" reset your device? If you didn't fastboot flash a full factory image allowing a full wipe then you should go back and start there. If you already did that, I would run it rooted but no modules for a day or two. You probably already identified the culprit, but this would rule out/in a hardware issue and confirm the module was at fault.
v12xke said:
How did you "fully" reset your device? If you didn't fastboot flash a full factory image allowing a full wipe then you should go back and start there. If you already did that, I would run it rooted but no modules for a day or two. You probably already identified the culprit, but this would rule out/in a hardware issue and confirm the module was at fault.
Click to expand...
Click to collapse
Other than the first time in which I managed to somehow get out of it, I flashed the full factory image to both slots along with issuing the commaand to format userdata.
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Hi. I am also using Kraken rom. Check out this post if you want.
[GUIDE] Go back to stock - Galaxy S10 series
Hi 🙂 So you have bricked your Samsung S10 series handset and you need it fixed. Sometimes we try to modify our phones and it goes wrong, fret not it can be restored. DOWNLOADS Frija Microsoft Visual C++ 2008 Microsoft Visual C++ 2010 Phone...
forum.xda-developers.com
puul said:
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Click to expand...
Click to collapse
Hi, don't know if it's too late but I did have the same problem before and all I did was boot into TWRP. When you wipe make sure to check everything from Dalvil to Internal Storage and format data as well. Also if you are going to install Magisk try to do it after your phone boot into os otherwise it will stuck in bootloop again. I hope that's can help!