I installed the Active Edge Magisk Module (from this thread) and after it rebooted it got stuck on the "Android is Updating" screen. I forced a reboot and when I got back into the system I was greeted with an impassable "System UI has stopped" (or something) dialog.
So I decided to just scrap it all and restored from a nandroid I'd made not five minutes prior. Restore successful. Rebooted, aaannnd.
ERROR: LoadImageAndAuth Failed: Load Error
I'm stuck in bootloader, unable to get into either System or TWRP. Attempting either just makes the screen go black for a sec before it spits me right back. The upside is that I can at least see it in adb.
I've found one or two other instances of the error message, but they were trying to flash the update whereas I was just flashing a Magisk module. I don't know if they're related or not.
More importantly, though — how can I fix this? Is Deuce's script my only option or is there a simpler, more painless fix?
I got this error yesterday when I tried to update to the latest January patch. I ran deuce's script to no avail but ultimately I fixed it by fastbooting TWRP and switching slots (in my case from b to a.) If I tried to boot to TWRP from booting to recovery, it always hung on the splash screen, I had to fastboot TWRP.
Sent from my Pixel 2 using Tapatalk
HELP
Hi, I got same problem here, and I have no idea what I can do now. Can you give more detail(like step by step) to show me what you did?
Spikelangelo said:
I got this error yesterday when I tried to update to the latest January patch. I ran deuce's script to no avail but ultimately I fixed it by fastbooting TWRP and switching slots (in my case from b to a.) If I tried to boot to TWRP from booting to recovery, it always hung on the splash screen, I had to fastboot TWRP.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
kongpingzi822 said:
Hi, I got same problem here, and I have no idea what I can do now. Can you give more detail(like step by step) to show me what you did?
Click to expand...
Click to collapse
It was a while ago but basically:
Boot into bootloader
Note which slot you're currently on (b or a)
Use fastboot to switch slots
Reboot bootloader to confirm (should then show opposite slot)
That did it for me
Example: if you are on slot b, enter:
Fastboot --set-active=a
Fastboot reboot-bootloader
It should now show a as active
I forget from there if I just had to reboot and all was good or if I had to reflash the factory image.
I think what ultimately caused it for me was that I was immediately flashing twrp/kernel/magisk after updating without first fully booting android so it could complete the upgrade. I'm not 100% sure though, like I said, it was a while ago.
Sent from my Pixel 2 using Tapatalk
Thanks a lot, I totally bricked my phone and nothing worked , then paid someone to fix all problems. OMG, nightmare
Related
I'm stuck in a bootloop on Pixel (sailfish). I've rooted with SuperSU and installed TWRP previously. I've never had an issue applying the new updates until today.
Here's the steps I followed:
I downloaded the 7.1.2 (N2G47O, May 2017) update from the google site and verified the SHA 256 hash
I removed the -w from the "fastboot -w update" in flash-all. Then ran flash-all.bat. It completed successfully. The phone rebooted.
Next I powered down the phone and booted to fastboot.
I then tried to install TWRP by running "fastboot boot twrp-3.0.2-RC1-fastboot.sailfish.img"
It installed fine and booted to TWRP.
I opened TWRP and tried to install TWRP. It ran fine. Rebooted and here's where I went into the problem
The phone boots up and gives me the message about "Your Device software can't be checked for corruption. Please lock the bootloader". I've seen this before, so no issues.
Then the Google screen shows up with a black line through it.
Then it comes back to the previous message about the unlocked boot loader.
If I tried to hold POWER down, I get a message "[RAMDUMP] Writing to EXt 4 file" and back to the message about the unlocked boot loader.
How do I fix this ?
UPDATE: After much trying, i finally caught it when it was powered off and managed to get to boot to fastboot where I reflashed the most recent update. But.. is this still the best way to install TWRP ? Or should I do something else?
The problem is the bootloader in the N2G47O. A temporary fix is to download the N2G47E image and extract the `bootloader-sailfish-8996-012001-1702151126.img` file and then boot your phone into fastboot and run `fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126.img`. Then you can boot into TWRP and install whatever you need
Abolfazl said:
The problem is the bootloader in the N2G47O.
Click to expand...
Click to collapse
Thank you very much! I've followed the temp fix and now have both TWRP and SuperSU installed.
I appreciate the quick response and help
Wow this just happened to me too. Thanks for the fish. I guess a better upgrade path is to not skip the April update ( I was coming from March to May)
Also follow the hardware process of booting to fastboot if this is happening, no need to wait for an oppurtunity. Just press Power + Vol - + etc and release to boot to fastboot.
.
THANK YOU!
Abolfazl said:
The problem is the bootloader in the N2G47O. A temporary fix is to download the N2G47E image and extract the `bootloader-sailfish-8996-012001-1702151126.img` file and then boot your phone into fastboot and run `fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126.img`. Then you can boot into TWRP and install whatever you need
Click to expand...
Click to collapse
Saved my life here! I thought I was going to have to deal with Ads until the next time they updated TWRP! This worked beautifully!
EDIT
Turns out I was two versions of adb/fastboot behind instead of one. Ignore me!
Hey all,
Yesterday I went to flash the factory image on my Pixel 2 that was running unlocked and rooted with Magisk and Snoke kernel, but it failed while trying to erase the cache partition. I found out that I wasn't using the latest fastboot because the Pixel doesn't use a cache partition so I updated and tried again, and the flash-all script seemed to work fine. But when it finished an rebooted the phone, I was back at the bootloader. I tried the start, recovery, and download mode buttons but they all sent me back to the bootloader. If I turn the phone off and plug it into a charger, the charging icon will come up on the screen for a second and then send me to the bootloader.
I tried flashing the files manually, but the process was hit or miss and would either hang forever or return a generic error (either a generic load error or check device console).
I can't boot the alpha TWRP because it returns a generic load/authentication error and quits.
At this point the flash-all will go through the motions and seem to work every time now, but when it reboots I'm back at square one. I can lock and unlock the bootloader and confirm it on the phone screen, I can flash the bootloader, boot, and system images, I can erase those images, I seem to be able to do everything I can usually do in there, but it's almost like my computer says it's working, but the phone isn't actually doing anything. Short of an RMA I'm not entirely sure what to do. Does anyone have any insight?
Click to expand...
Click to collapse
I'm new to pixels phones but i read about the slot a and slot b maybe you have to change the boot to other slot?
There is a tool in development section maybe it can help u some how.
gm007 said:
I'm new to pixels phones but i read about the slot a and slot b maybe you have to change the boot to other slot?
There is a tool in development section maybe it can help u some how.
Click to expand...
Click to collapse
I set the active slot to b and rebooted and I got the warning message that the bootloader was unlocked and to continue, which brought me to the boot logo for a little bit, and then back to the bootloader.
virgilante said:
I set the active slot to b and rebooted and I got the warning message that the bootloader was unlocked and to continue, which brought me to the boot logo for a little bit, and then back to the bootloader.
Click to expand...
Click to collapse
Maybe you need to flash the stock image again in the second slot?
I have faced the same issue and reflash the factory image do not work, is there anyone resolve this?
# updated
https://forum.xda-developers.com/pixel-2/help/fastboot-update-resulted-bricked-device-t3694761
as this thread， just flash every img manually resolved this issue.
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.
hi guys,
my op6 is running stock oos with magisk as root. My phone worked fine for several months. Today I tried switching magisk from the stable version to canary by first upgrading the manager app and then hitting the direct install option. This failed several times and I got an error saying:
! Unable to unpack boot image
I thought this could be fixed by a reboot, but well... it wasn't. Now the phone only boots into the bootloader. I booted into twrp and tried to uninstall magisk via the uninstall.zip. This fails with error
-Unpacking boot image
! Unsupported/Unknown image format
- Unmounting partitions
cd /tmp/repackorig/ && /sbin/magiskboot unpack -h '/tmp/repackorig/boot.img' process ended with ERROR: 1
Error unpacking image
I don't really know what this means. I'm guessing my boot.img is corrupted?
Is there any way I can solve this problem without a factory reset? Can I just flash the stock boot.img via fastboot?
Do you have any idea what went wrong here, so that I can avoid the error next time?
Yesterday I broke op5 during the magisk update. The repair was simple, flash stock boot.img as boot partition.
I flashed it from TWRP.
Try dirty flashing your ROM without flashing magisk.
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Is there any way I can still (temporarily) access the data? I'm panicking a little bit. My OOS is stock and rooted and hasn't been updated in about a year. I'm not sure if I can still figure out the specific OOS version that is installed.
EDIT:
Have been trying to flash the stock boot.img with fastboot. I've tried both 10.0.1 and 10.3.0 so far. Both resulted in the "BOOTLOADER UNLOCKED" warning and got stuck there. 10.3.1 is my last option, because I don't think I've updated this device since. Would it make a difference if I tried to do it from twrp?
EDIT2:
I do however have access to the recovery mode now. If I'm not mistaken this means I might be able to extract the data.
EDIT3:
The recovery mode is not asking me for my unlock pattern (which I think it should be doing) and is not showing up under 'adb devices'. I've tried flashing the boot.img of all OOS versions I can think of with fastboot, nothing will let me boot back in or let me access adb through the recovery. Am I ****ed?
Click to expand...
Click to collapse
Maybe it's worth trying change the slot and see if it will start? Of course from the fastboot level.
MoresM said:
I'm also facing the same issues. Tried updating from the Magisk App. Didn't receive any error messages. After reboot I'm stuck in fastboot mode and I cannot access recovery. I do not have a backup of the data on this phone.
Click to expand...
Click to collapse
I managed to fix it as well by flashing the stock boot.img for my software version to both slot_a and slot_b using fastboot. I left the active slot setting alone otherwise.
Afterwards I booted into twrp through fastboot and installed blu spark twrp and magisk 21.4 from there as a user suggested on the Magisk github: https://github.com/topjohnwu/Magisk/issues/3924
Note that github link also has a solution to flawlessly upgrade to latest Magisk without data loss but I haven't had the time to look at it.
What happened
Attempted to update from Android 11 > 12 using Magisk, following the steps here. This resulted in a bootloop.
I attempted to re-flash my old patched magisk boot image that I still had, and while it does boot, I have the following issues:
The issues
-I have no sound (which is at a system level and not a hardware level, I get errors depending which app I try to use, and videos will not play unless I mute them)
-I am not rooted
-I cannot update using the Android system updater; I get error "Something went wrong. To finish updating, restart your device". Restarting does not do anything (Note: It says "Update to Android 11" on the prompt, even though it says I'm currently using Android 11 RQ1A.210205.004)
-Upon boot it says "System UI is not responding", but I haven't noticed any issues related to this other than the popup.
What I've tried
-I tried patching a Magisk 12 boot image and flashing that with fastboot. When I do this, it boots to the fastboot menu with "Error Boot Prepare". I used Sunfish SQ1A, non-Verizon/non-Vodaphone versions, which I'm pretty sure is correct for my non-5g ATT Pixel4a. I also attempted the November release of 12, same results.
-Doing some research, it sounds like the "no sound, can't update" issue is fairly common when an update fails. A common fix I saw was to wipe the cache partition. When I booted to recovery mode, it says "No commands", so I cannot wipe from there. When I attempted "fastboot erase cache" I got error "FAILED (remove: 'Not allowed to erase (cache)'). Every search I did for this error says to enable OEM Unlocking in dev options, which was already enabled.
Not sure what else to try from here. I would be happy to either update to 12, or to keep 11 and just get my audio/root back.
Thanks
Continuing my research, I'm getting mixed results in regards to cached partition, and if it even exists for the 4a (meaning my attempts are pointless)
This article gives instructions on how to clear it (which don't work for me, but a lot of things aren't working on the phone at the moment haha)
Whereas THIS article states that systems with an A/B slot (like the 4a) do not have a cache partition.
To "get back to normal" I would probably dirty flash the version of Android 11 you had in before...
When I did the Android 12 update, I found lots of warnings that "dirty flashing" breaks from Android 11 to Android 12, so I didn't do my usual process. Instead, I sideloaded the full OTA package in order to do the upgrade. That might even work from your current state...
After the upgrade I used Magisk 23 (release, not canary) to patch the boot.img (which I extracted from the factory image), used fastboot boot patched.img and then used Magisk to install (direct). You can flash from fastboot but I don't do that.
My normal "dirty flash" upgrade looks like this:
1 download the factory image
2 extract it and the embedded zip until you have boot.img
3 send that to the phone and use Magisk manager to patch it. Send it back to the pc
4 replace the -w in the flash_all script with --skip-reboot. Add these 3 extra lines to the end.
fastboot reboot-bootloader
sleep 5
fastboot boot patched.img
5 run the script
6 use Magisk manager to install (direct)
I attempted to sideload both the recent 11 OTA package, and the 12 OTA package. After each one, the results were the same, I got a generic error of "status 1" on the phone (fastboot on my computer completed fine without issues).
I then attempted your dirty flash method with a couple versions of android 11. Again, the script completed successfully each time, but I hit a bootloop when trying to start (G logo with the loading bar for 20+ minutes).
After this, I was completely unable to even flash my old magisk image that was working previously. That would result in the same bootloop.
I attempted the recovery menu option to perform a factory reset (i backed up everything previously). That said it completed, and then the same bootloop happened.
I went to the pixelrecovery site on chrome, and it just gets stuck on "checking software" until the site eventually times out.
Not sure where to go from there, I've pulled out my old phone to use in the meantime.
I finally managed to get it working, I used the android flash website via chrome. It failed the first time, but worked after that, and managed to get an Android 12 image booted. It made me re-lock my bootloader, and it also did a complete wipe (so me trying the failed factory reset earlier didn't mess me up anyway, apparently had to do it regardless).
From there I was able to go through the normal rooting steps, unlock bootloader, patch with magisk, fastboot flash boot magist_patched.img, everything is working fine now.
I feel like I must have done something wrong in the process to get it this broken, and unfortunately this isn't too much of a tutorial for anyone with the same problems (since I ended up essentially just wiping it and starting from scratch), but it is what it is.
Thank you for the suggestions!