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.
Related
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
mediaman123 said:
can you get a custom recovery on successfully.........?
did you flash the stock image manually?
Click to expand...
Click to collapse
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
jeromechrome1 said:
Yes I tried pushing the stock recovery individually and it succeeded in the command prompt, but won't enter recovery, just shows google and shuts off. I tried pushing twrp too but same outcome. Yes I had flashed the stock image manually, everything flashed well from what the command promt said, but when it should reboot to recovery after flash to wipe, just shuts off.
Click to expand...
Click to collapse
Please! Anyone!
by manually do you mean flashing all the separate parts of the stock image separately, system, boot, recovery, cache and so on..........
I don't know what else to do after going through with that process.....
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
I'm a total newb here so take what I tell you with a grain of salt. I had your exact same problem on my Nexus 5. Every single thing you just described is what happened to my N5. And just like your N6...I was able to boot up into recovery (stock and TWRP), I was able to flash all the things manually and even used Wug's NRT. But then whenever I tried to actually boot up the device it could never pass the Google logo....basically EVERYTHING THAT IS HAPPENING TO YOU.
What I did to fix everything? Changed my battery. Sounds stupid and totally irrelevant but that did the trick. When I opened up my phone I noticed my battery had a nasty bulge and realized it was defective. Bought a new one for $25 and have never had any issues ever since. I suggest you look at your battery and see if that is the root of your problem. I have heard of the N6 having some batteries expanding and causing the back covers to pop off...this could be related to your problem.
Like I said I am a newb and thought I'd share my experience in the hopes it solves your problem.
Good luck buddy! :good:
my N6 is actually away getting repaired for the exact issue you described, expanding battery [assumed], and cover coming away from the bezel.....
I believe though that if you keep the device plugged into the wall when trying to boot up with this battery defect it will get through the boot, at least in the beginning anyway....
I believe also that if it was a battery issue the device would power off first, as opposed to just sticking on the Google logo.........
ldkud50 said:
Make sure you have the latest fastboot by updating SDK Manager. Then reflash bootloader then reboot back to bootloader to reset. Then proceed to flash each partition again. Directions below.
fastboot flash bootloader bootloader.img <-- rename bootloader to this to make it easier
fastboot flash radio radio.img <--- again rename to make easier
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fasyboot flash system system.img
Hope this helps.
Click to expand...
Click to collapse
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
jeromechrome1 said:
I tried all of that already bro, it takes the files fine i did each individually including the bootloader. yes i have the latest sdk and latest fasboot. same issue no matter what i try. thank you all for ur help so far, really appreciate it.
Click to expand...
Click to collapse
Thats too bad. Maybe the device is hosed. RMA for a new one.
Same thing happened to me. As soon as I updated to the newest version of fastboot on my computer, everything worked...
jeromechrome1 said:
My motorola Nexus 6 won't turn on, when I try to power it on, it shows the Google sign then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, it flashes fine but it still shuts off immediately while showing the google sign. It won't even boot into recovery after the flash, it just shuts off after the google sign. This isn't my first nexus, in know that flashing factory image should fix 99% of issues. Please help.
P.S I didn't purchase officially from google or Motorola, bought it from a guy who claimed he bricked it trying to install a font pack so I figured let me buy it and restore factory image. Didn't work. I tried flashing manually, the process went fine, but it it still turns off at google splash image. I tried Wugfresh toolkit also to no avail. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and it wouldn't boot past google screen after that. It doesnt even get to the boot animation. It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I spoke to my friend who has a local repair shop and he says there is nothing out for his z3x or his other boxes for the nexus 6 because it is such a new and rare device. His theory is that the partition tables have been corrupted somehow and need to be rewritten manually. Please any help would be appreciated. I can promise a hefty $$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I know, it's been a long time, but coud you tell me what happened to the phone?
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here http://bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
MDV106 said:
Which version of twrp did you flash ? Where did you get it from?
Flash the stock recovery of your pie version using the right file from here bit.ly/nokia-nb1 and then do a factory reset or sideload the pie rom.
Once that is done use the same link to flash the corresponding patched twrp boot img, boot into recovery and then flash magisk from inside twrp
Click to expand...
Click to collapse
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
t0r3n0 said:
I got the TWRP version from the folder from that link actually.
I've managed to get the phone to boot somehow. The phone would expose fastboot for a few seconds after having just enough battery from getting a bit of charge after letting it go flat, before freezing when presumably trying to load the OS. So i managed to send 'fastboot reboot recovery' to it after letting it go flat once again, and successfully entered TWRP, and factory reset. Now my phone boots into Android, TWRP still flashed, and bootloader unlocked, but no root. What would the safest option to install magisk? Wouldn't want to brick the phone again...
Click to expand...
Click to collapse
you can install it using Magisk Manager apk, or flash the Magisk zip file inside TWRP, your choice. I dont think either of the two menthods are risky
t0r3n0 said:
Hey there so, I've recently been trying to root my new Nokia 8. I have successfully unlocked the bootloader via downgrade to Android 8.1, and running HMD's app. I then have updated to 9 via OTA, and flashed TWRP to boot_b (the current active slot). Next i flashed Magisk 18.1 from the official thread here on XDA, using TWRP. Upon reboot, the phone now hangs and does not respond to any input. My only option is to let it go flat. Attempting to charge it afterwards, results in the red battery plug in icon, which does come up if i press any buttons. After it charges enough, it attempts to boot (kind of?) on its own, and just freezes, and i'm back to square one. This is a brand new phone so this would suck so bad if i can't fix it..
Thanks for any help guys
Click to expand...
Click to collapse
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
shadow87qft said:
I currently have a similar problem. successfully installed twrp and booted into recovery to see if it works. It did. so now i got the magisk install zip and wanted to install it via twrp, but after executing adb reboot recovery my phone now is stuck on the bootloader unlocked warning screen. The phone doesnt react to any input and doesnt connect to adb or fastboot. currently waiting for the battery to die and try with a fresh reboot after that...
Click to expand...
Click to collapse
For me, i found that fastboot was being exposed for a few seconds when it would start to turn back on after the battery dying out. I was able to send 'fastboot reboot recovery' and it didn't boot into recovery, but it booted into Android... A bit strange.
Hi guys...
Sorry, but I'm a bit concerned as I was rooted on the Oct update and I found I just want to go back to unrooted/normal so, I grabbed the latest image and used the flash-all.bat. I have done this many times and normally don't have an issue but....this time...I'm not sure whats happening.
I wait for flash-all, device doesn't reboot at the end.
I manually reboot, starts with google logo, goes back and says My Device is Corrupt...I continue...
It goes past the "Your Boot-loader is unlocked" and shows the Google logo.....
I have left it for 30mins or so. Power button down for 10+ secs, reboots.
Then it just sits in Fast-boot and I cant start. I hit start and it just loops back to fast boot.
I'm having a heart attack here...
2 things I can think of....
I don't have the right image? I have tried 191205 and 190821... I could try earlier...haven't yet.
The other thing could be I didn't reset to factory before doing the flash-all....not that that should make a dif...
The final thing is, I've .....somehow....*gulp* bricked my new phone...... =(
I have NEVER bricked a phone in my 10 + years of playing around with Android phones so, I'm hopeful its not that.
Any help at all?
Thanks soooooo much in advance guys.
Lambetts said:
Hi guys...
Sorry, but I'm a bit concerned as I was rooted on the Oct update and I found I just want to go back to unrooted/normal so, I grabbed the latest image and used the flash-all.bat. I have done this many times and normally don't have an issue but....this time...I'm not sure whats happening.
I wait for flash-all, device doesn't reboot at the end.
I manually reboot, starts with google logo, goes back and says My Device is Corrupt...I continue...
It goes past the "Your Boot-loader is unlocked" and shows the Google logo.....
I have left it for 30mins or so. Power button down for 10+ secs, reboots.
Then it just sits in Fast-boot and I cant start. I hit start and it just loops back to fast boot.
I'm having a heart attack here...
2 things I can think of....
I don't have the right image? I have tried 191205 and 190821... I could try earlier...haven't yet.
The other thing could be I didn't reset to factory before doing the flash-all....not that that should make a dif...
The final thing is, I've .....somehow....*gulp* bricked my new phone...... =(
I have NEVER bricked a phone in my 10 + years of playing around with Android phones so, I'm hopeful its not that.
Any help at all?
Thanks soooooo much in advance guys.
Click to expand...
Click to collapse
1. Did you disable all magisk modules and themes before you started?
2. Are your platform-tools up to date?
3. Were you trying to go back to October factory image or forward to December?
4. Have you tried switch slots and fastboot the factory image again?
5. You didn't turn off OEM unlocking off did you?
6. Your not having a heart attack!?
7. If you've never bricked a phone in 10 years, you haven't played hard enough on android! ?
Badger50 said:
1. Did you disable all magisk modules and themes before you started?
2. Are your platform-tools up to date?
3. Were you trying to go back to October factory image or forward to December?
4. Have you tried switch slots and fastboot the factory image again?
5. You didn't turn off OEM unlocking off did you?
6. Your not having a heart attack!
7. If you've never bricked a phone in 10 years, you haven't played hard enough on android!
Click to expand...
Click to collapse
1. No
2. Yes
3. Forward to Dec
4. I was just looking this up but No
5. No
6. Haha
7. Haha True
EDIT: I have swapped Slots, but I dont want to flash the Dec image again if it will stuff up slot a... Dam, I'm not sure what update I was on, I think the latest Oct image. Thoughts??
Can I tell from the bootloader screen?
Lambetts said:
1. No
2. Yes
3. Forward to Dec
4. I was just looking this up but No
5. No
6. Haha
7. Haha True
Click to expand...
Click to collapse
First, try switching to your inactive slot with..
..fastboot --set-active=a or b...depending on what your slot your currently on.
Then fastboot the factory image again.
You may have to factory reset since it's very likely that a magisk module not compatible with the December update is causing your problem. Especially if you were using any active edge or Tulsadiver mods.
EDIT: Use the factory image that coincides with your carrier.
Badger50 said:
First, try switching to your inactive slot with..
..fastboot --set-active=a or b...depending on what your slot your currently on.
Then fastboot the factory image again.
You may have to factory reset since it's very likely that a magisk module not compatible with the December update is causing your problem. Especially if you were using any active edge or Tulsadiver mods.
EDIT: Use the factory image that coincides with your carrier.
Click to expand...
Click to collapse
Thank you so much for your responses!!
Ok, from what I can tell, I could go and flash the latest Oct, or, Just flash the Dec update. Both are fine with my carrier, my phones not attached to a carrier.
Either way, am I going to stuff it up either way? No that I swapped slots, it just loops fastboot but doesn't show me the Corrupt warning anymore.
Lastly, how do I Factory Reset from fastboot?
Thanks a million Badger50!!!
Lambetts said:
Thank you so much for your responses!!
Ok, from what I can tell, I could go and flash the latest Oct, or, Just flash the Dec update. Both are fine with my carrier, my phones not attached to a carrier.
Either way, am I going to stuff it up either way? No that I swapped slots, it just loops fastboot but doesn't show me the Corrupt warning anymore.
Lastly, how do I Factory Reset from fastboot?
Thanks a million Badger50!!!
Click to expand...
Click to collapse
Stay with the factory image that you just flashed. Going backwards requires a full wipe, then fastboot the factory with the -w included.
While your device is not technically "attached" to a carrier, the radio is. That's why there's 3 different factory images currently available until google gets it sorted out.
You factory reset from fastboot by hitting the menu and select recovery. Once you see the dead droid laying on his back with no command on the screen, hold power + volume up, the release volume up. Then you should see the menu with factory reset included.
Badger50 said:
Stay with the factory image that you just flashed. Going backwards requires a full wipe, then fastboot the factory with the -w included.
While your device is not technically "attached" to a carrier, the radio is. That's why there's 3 different factory images currently available until google gets it sorted out.
You factory reset from fastboot by hitting the menu and select recovery. Once you see the dead droid laying on his back with no command on the screen, hold power + volume up, the release volume up. Then you should see the menu with factory reset included.
Click to expand...
Click to collapse
Well, I tried factory reset on the current slot "b", reflashed latest Dec image.....still sitting on the Google screen now for 5 mins or so....and I got the Corrupt error again....
I haven't tried slot a.... I feel that is my last option isn't it....I don't want to stuff that slot up too....
Lambetts said:
Well, I tried factory reset on the current slot "b", reflashed latest Dec image.....still sitting on the Google screen now for 5 mins or so....and I got the Corrupt error again....
I haven't tried slot a.... I feel that is my last option isn't it....I don't want to stuff that slot up too....
Click to expand...
Click to collapse
At this point you can't do much more damaged since you've already factory reset.
Badger50 said:
At this point you can't do much more damaged since you've already factory reset.
Click to expand...
Click to collapse
1. I see... So I'm going to assume slot a is 'fresh'. But I feel if I flash the latest Dec, what if the problem is my bootloader is mismatching or something, I might have the same issue....
2. The flash-all.bat has the -w switch in it doesn't it?
3. Even though I factory reset (thanks for telling me how to do that on this too, I totally forgot that) why am I getting the Corrupt Error still?
EDIT: So, your recommendation is still, change to slot A, factory reset, then flash latest Dec image?
Don't know if it matters but OEM Unlocking is ON, and my bootloader is still UNLOCKED, just making sure I haven't left that out lol.
UPDATE: Changed to slot A, factory reset, then flashed factory Dec image. At the end of the flashing, this came up and it did on all the other slot b attempts too...
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/2 (524284 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...
Thanks again man, I really appreciate all your help.
Lambetts said:
1. I see... So I'm going to assume slot a is 'fresh'. But I feel if I flash the latest Dec, what if the problem is my bootloader is mismatching or something, I might have the same issue....
2. The flash-all.bat has the -w switch in it doesn't it?
3. Even though I factory reset (thanks for telling me how to do that on this too, I totally forgot that) why am I getting the Corrupt Error still?
EDIT: So, your recommendation is still, change to slot A, factory reset, then flash latest Dec image?
Don't know if it matters but OEM Unlocking is ON, and my bootloader is still UNLOCKED, just making sure I haven't left that out lol.
UPDATE: Changed to slot A, factory reset, then flashed factory Dec image. At the end of the flashing, this came up and it did on all the other slot b attempts too...
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/2 (524284 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...
Thanks again man, I really appreciate all your help.
Click to expand...
Click to collapse
Ok, so.... I was using a USB-C to USB-C cable....
I recommend in trying a USB-A to USB-C. It passed that line in the bat file and now I'm fine.
Thank you for all your help anyway Badger, I really appreciate it. Hopefully someone finds this helpful!!
Thanks again. ^_^
Lambetts said:
Ok, so.... I was using a USB-C to USB-C cable....
I recommend in trying a USB-A to USB-C. It passed that line in the bat file and now I'm fine.
Thank you for all your help anyway Badger, I really appreciate it. Hopefully someone finds this helpful!!
Thanks again. ^_^
Click to expand...
Click to collapse
Dude...after all the posts you've read and participated in on the P2XL and now P4XL about USB A to USB C cables, I just assumed you already were doing that. That's usually the #1 go to solution. Try to remember that going forward. I hate watching you have heart attacks! ?
Lambetts said:
Ok, so.... I was using a USB-C to USB-C cable....
I recommend in trying a USB-A to USB-C. It passed that line in the bat file and now I'm fine.
Thank you for all your help anyway Badger, I really appreciate it. Hopefully someone finds this helpful!!
Thanks again. ^_^
Click to expand...
Click to collapse
Glad I'm not the only one this happened to. Flash a system image on this phone is a pain in the a$$.
I was convinced I was going to have to send it back to google for replacement.
It's actually quite easy; make sure you've got the latest tools, use the proper cable which ironically isn't what came with the phone, don't forget to remove the wipe. That's it, from there it's the usual flashing the boot and victory is at hand. Next time don't reset until you've given a few different cables a go and have verified it's not the tools. That way if one of those were the problem you can often get out of it without losing data with a successfully completed flash.
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.
Long story short, I hard-bricked this thing to Hell. I'm in Download mode and have QFIL but I don't have a saved fstab so I can't flash the rom properly.
Someone wanna kindly post one, please??
Much obliged.
jake5253 said:
Long story short, I hard-bricked this thing to Hell. I'm in Download mode and have QFIL but I don't have a saved fstab so I can't flash the rom properly.
Someone wanna kindly post one, please??
Much obliged.
Click to expand...
Click to collapse
What firmware are you on?
kountry83 said:
What firmware are you on?
Click to expand...
Click to collapse
Heh. So, after a long day i neglected to plug my phone in to charge before the battery totally died and now it's stuck in a bootloop. This seems to be a somewhat common issue with this phone when it's been modded. Understandable but managable quirk. Usually I can just fastboot flash boot and it seems to resolve the problem, then I reboot-bootloader (after a successful boot) and re-flash my magisk_patched boot. For some reason, my stock boot image trick didn't work so I tried again, specifying boot_a and boot_b, just to make sure i hit the right slot. Still no luck. So I pulled out the heavy guns and ran flashall.bat (edited to NOT delete userdata). Being tired, annoyed, frustrated, in a hurry at 1:30AM, and tired of re-flashing this damn thing, I realized as it rebooted to a BLACK DEATH SCREEN that I really fu***d up and flashed MATA Q.032 update!
So currently it's boned.
But it automatially seems to be dropping itself into DOWNLOAD mode so I believe that means I should be able to use QFIL to restore partitions and upload at least enough partitions to get into a fastboot-able state and then run the correct flashall of the latest AURA CHERYL2.
jake5253 said:
Heh. So, after a long day i neglected to plug my phone in to charge before the battery totally died and now it's stuck in a bootloop. This seems to be a somewhat common issue with this phone when it's been modded. Understandable but managable quirk. Usually I can just fastboot flash boot and it seems to resolve the problem, then I reboot-bootloader (after a successful boot) and re-flash my magisk_patched boot. For some reason, my stock boot image trick didn't work so I tried again, specifying boot_a and boot_b, just to make sure i hit the right slot. Still no luck. So I pulled out the heavy guns and ran flashall.bat (edited to NOT delete userdata). Being tired, annoyed, frustrated, in a hurry at 1:30AM, and tired of re-flashing this damn thing, I realized as it rebooted to a BLACK DEATH SCREEN that I really fu***d up and flashed MATA Q.032 update!
So currently it's boned.
But it automatially seems to be dropping itself into DOWNLOAD mode so I believe that means I should be able to use QFIL to restore partitions and upload at least enough partitions to get into a fastboot-able state and then run the correct flashall of the latest AURA CHERYL2.
Click to expand...
Click to collapse
This struck a chord with me as I'm currently suffering from the same bootloop problem and I'm using the same fix kind of, except when it happens I use "fastboot restart recovery" from the bootloader and then flash a boot.img backup I have on my SD. My last phone was a MATA and I still have the images in my SDK directory, definetly going to clean it up now