Related
Wondering if many others of you have run across this, what causes it, and how to avoid it. Basically, I download the factory image from google's image page, flash-all using adb/fastboot. All looks good, every part of installation says OKAY, no fails. Then upon reboot it goes back to bootloader, but now with a yellow banner at the bottom - ERROR: LoadImageAndAuth Failed: Load Error. Sometimes the banner reads ERROR: Slot Unbootable: Load Error. (see attached pictures)
There's no way out of it, flashing images, bootloader or boot.img or whatever separately, flashing twrp, switching between a/b partitions, nothing changes it. Adb/fastboot is current. It's happened after regular flash-all, it's happened when "-w" is removed. It's happened with and without twrp installed. This last time I tried to avoid it by updating without flashing the image, removed twrp and tried to sideload the OTA in stock recovery, which also landed me in the same spot, in the bootloader with that yellow banner of death. Been hit by this using Dec., Feb., and March updates. I stayed on the Dec. update for a while because I've been afraid of it happening again... sure enough it did.
I've replaced a few pixel 2's because of this, every time Google willingly stands by their product and replaces it. One google worker told me this is a known issue they were working on, others said it isn't, and none have provided an explanation for why it happens or how to avoid it. I assume it's some kind of instability with the a/b partition system. I did the same process with my N5x a couple days ago (flashed image then added twrp, magisk, all that stuff) and as usual everything went swimmingly. Tried just flashing current image on p2 the next day and another one bit the dust. Another replacement is on its way now.
So I turn to you. Any of you run into this? What causes it? How can I flash updates without this happening again?
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
deepdvd said:
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
Click to expand...
Click to collapse
Tried boot.img but not working for me, still stuck in bootloader. But good to know, I didn't realize that was a possibility. Sucks having to be tethered like that though. I backed up double before messing with it, both nandroid and titanium, expecting I might run into this again.
The replacement process is relatively painless, only takes like 3 days to get a new one. Just be sure to do it while covered under warranty.
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
clcdev said:
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
Click to expand...
Click to collapse
Thanks man, seems like it since not many people are experiencing this. Can't think of what external issue it could be other than something with my computer, but im sure not having any troubles doing the same stuff and more on my nexus.
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
craigacgomez said:
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
Click to expand...
Click to collapse
Well I tried flashing the ota in recovery and that's what triggered it this last time. But I didn't try doing each partition, maybe that's where it went wrong
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
COMpulse said:
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
Click to expand...
Click to collapse
That's what gets me, can't simply fastboot the image to recover, that fail-safe isn't reliable for me.
Got the replacement and set it up so I can update normally. Just booted twrp but didn't install, so I could flash magisk. With no twrp and easily uninstall magisk I can just update via regular OTA when it shows up. Then temporarily boot twrp again to reinstall magisk. Just did that for the March update and worked fine.
A little inconvenient of a workaround but I'm updating without concern about this image flashing problem.
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
kkjb said:
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
Click to expand...
Click to collapse
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
kkjb said:
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
Click to expand...
Click to collapse
Wow great to hear it worked! I tried the deuce script but couldn't get it to work either. I heard there was an issue with the bootloader in December and was supposed to have been fixed in January. But that bootloader error was one that I was also getting after the yellow banner started showing up, even on this last go around. Just before the initial bricking fastboot was reporting all successful on the flash.
More of my troubles
I have twrp 3.2.1-2, Magisk v16.1(1610) Jan 18 8.1.0. The device is working as before. So to recap...first post is what I HAD. My bootloader is stuck on 002.0059.00 this is the one from opd1.170816.025 which is 8.0.0 Nov 17. This some how flashed through Deuce's script and stuck. Now of course nothing will flash with Factory images because I have a botched up Boot.img. From looking back the trouble started with going to update to P. Removed Magisk through manager. It "patched" boot but some how on mine (with flashed twrp) recovery caused a flag I guess to set.
So some point I'm going to get Magisk to patch current Factory Boot.img 002.0067.00 which is in Feb, Mar 18 and P.
Need time to read though Magisk or wait for others to experience. I believe this is the warning message of TWRP and Pixel 2 A/B slots.
update to my troubles
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
kkjb said:
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
Click to expand...
Click to collapse
That's pretty slick that you got it working again, especially with the bootloader error. I didn't think you could get the current OS working with an old bootloader at all. Hopefully at some point you will be able to update it all the way.
I soft bricked it..so don't do this.
See previous to catch up. Since I pulled the plug and had a Google Warranty phone in hand...21 hours later!
I decided to do all the things NOT TO DO.
Pulled factory Image file from last bootloader with 0059 bootloader.. Nov 17
Flashed tdbo.img, boot.img.
Didn't change same Flash failure device return message. Had to boot TWRP, flash twrp to get working again. Since phone needs to return for credit.
Nothing to lose, I have been on slot = A always. Moved to slot = B....
Now it is a brick.
First couple of power cycles, one line flash, vibrate. Then after 3-4 more cycles no more vibration. longer time to one line flash.
Warm to touch, overnight charge. Same.
So message is to keep backup of files used in first portion of Magisk and twrp installs. Must follow instructions if want to remove Magisk root.
Somehow my problem is a weird one off with the bootloader oddity.
After successfully installing Magisk, I got 9.5.4 update. As my bootloader is unlocked, system forced full image update
Now, update install successfully through OTA updater but on reboot I get stuck in stock recovery. From there, I had to manually boot to fastboot and switch to slot b to boot OS, back. After spending an hour, couldn't get any leads. Any advice is appreciated..
arvindgr said:
After successfully installing Magisk, I got 9.5.4 update. As my bootloader is unlocked, system forced full image update
Now, update install successfully through OTA updater but on reboot I get stuck in stock recovery. From there, I had to manually boot to fastboot and switch to slot b to boot OS, back. After spending an hour, couldn't get any leads. Any advice is appreciated..
Click to expand...
Click to collapse
I think you've to flash magisk again after an update. I'm not sure though. Not taking responsibility for anything that'll happen if you do so.
icyfire said:
I think you've to flash magisk again after an update. I'm not sure though. Not taking responsibility for anything that'll happen if you do so.
Click to expand...
Click to collapse
Ofcourse I own the responsibility,
Yes tried flashing it seperately for slot a. Then seperately for slot b. Since nothing worked out, flashed twrp on slot a and still nothing.
Then, tried going to slot b 9.5.2 ROM, did local sys update then without reboot, inside Magisk flashed Recovery zip. Even then slot a ROM, doesn't boot
arvindgr said:
Ofcourse I own the responsibility,
Yes tried flashing it seperately for slot a. Then seperately for slot b. Since nothing worked out, flashed twrp on slot a and still nothing.
Then, tried going to slot b 9.5.2 ROM, did local sys update then without reboot, inside Magisk flashed Recovery zip. Even then slot a ROM, doesn't boot
Click to expand...
Click to collapse
Maybe try unrooting by flashing the stock boot.img. You can get the boot.img for 9.5.4 here.
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Hi. What software channel does your device have? There's already android 10 firmware available
LuisLFSS said:
Hi. What software channel does your device have? There's already android 10 firmware available
Click to expand...
Click to collapse
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
On a side note, when I got to that screen, not even re-flashing the OTA, correctly this time, (beware, new updates have 10 sparse system chunks instead of 9...) let me get past it, so the solution was to erase userdata. (no re-flashing involved) As for Magisk, I just re-patch/flash boot.img at every update, it's not like it's updated that frequently
eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
This is kinda weird because reflash stock ROM android 10 should work for you... What errors did you get when trying to flash android 10?
eworm92 said:
I have always used the "restore images" method to keep my Magisk after applying OTA updates (Magisk Manager -> Uninstall -> Restore images -> [update without rebooting] -> Magisk Manager -> Install to inactive slot), but after today's update, it didn't quite work. Now my phone won't boot, saying "Can't load Android system. Your data may be corrupt".
Now, I didn't realize it at first, but this was a more major update - an upgrade from Android 9 to Android 10, which is likely the problem. The error screen shows: "motorola/ocean_retail/ocean10/QPO30.52-29". The most I can do is perform a big factory reset (which might not even work) or reboot to stock recovery (do not have TWRP, as I installed Magisk before it was available for G7 Power and missed its release since).
Now, my go-to idea for a solution is to download the most recent ROM I can find - which unfortunately can't be the brand new Android 10 one, as it seems it's nowhere to be found yet - and flash the boot.img from it (and worry about reinstalling Magisk later, shouldn't be that much of a problem). However, I'm not sure if it's going to work, as perhaps an update this big has changed more than usual. Obviously I'd like to restore my phone to a state as close as possible to what it was yesterday, so before reflashing the entire ROM, I'd like to seek advice regarding any other solutions if possible.
I've also considered trying to use the Rescue and Assistant Tool to possibly download a good ROM. Does anyone have experience with this app?
I'd very much appreciate any and all help.
Click to expand...
Click to collapse
Next time do the following:
1. Restart to bootloader
2. connect to PC, open ADB terminal and type
"fastboot getvar all" to get active slot
3. change active slot by
"fastboot -aa" => change to slot _a
"fastboot -ab" => change to slot _b
You are running a A/B device. Is there is any error after an update then change the slot to the last working one.
eworm92 said:
I've been running a RETAIL ROM and despite the software update channel showing in the settings as RETEU, the other OTA updates installed fine.
In this case what I've done is:
a) tried to "restore images" and install OTA normally. This didn't work - had to reflash the Android 9 ROM
b) tried to download and install the Android 10 RETAIL ROM from lolinet. This also didn't work. Reflashed again.
c) tried to flash the Android 10 RETEU ROM from lolinet. Same result again.
d) tried to flash the Android 9 RETEU ROM from lolinet. This actually worked no problem and I am now on this ROM, matching my software update channel.
e) tried to "restore images" and install OTA normally again, now that the software update channel is the same as the ROM I'm running. Still didn't work.
f) tried to uninstall Magisk and then install OTA normally. Even this didn't work.
I really have no idea what is wrong. For now, I've decided to simply not update but if someone has an idea on what might help, I'd be glad to hear it.
Click to expand...
Click to collapse
Check if you're running 10 sparse system image flash commands instead of 9 (The only difference between flashing Android 9/10)
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
eworm92 said:
I've tried everything proposed above: flashed to both slots, made sure to flash all 10 system sparsechunks.
I guess the solution is to erase userdata, which I've avoided doing thus far. What exactly am I gonna lose if I do?
Click to expand...
Click to collapse
Erasing userdata will make it like you had just bought the phone. (factory reset) I also had to do that, but I assumed it was because I'd forgotten to flash the 10th system sparsechunk, which caused a bootloop asking me to do a factory reset no matter what I did. (Unless blankflash/flashing Android 9 image was the solution, I just flashed the missing sparsechunk and erased userdata)
I'm just confused because it is an update. I'm supposed to be able to keep my data.
eworm92 said:
I'm just confused because it is an update. I'm supposed to be able to keep my data.
Click to expand...
Click to collapse
You're right, you should keep your data. But I had the same issue on my Moto G6 plus. It was only a security patch update without an Android upgrade.
After it was successfully installed I wasn't able to boot and had to erase my data.
Before factory reset, try switching partition for backup
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
ElFalko said:
I basically ran into the same problem today, the update banner popped up at an unfortunate moment and I clicked it in accident. I was also running a RETAIL rom.
The G7 Power didn't boot anymore, instead complaining that the image was corrupted, and did not go into recovery.
adb saw nothing, fastboot saw the device after the usual reboot into bootloader.
A mate of mine suggested switching to partition b with `fastboot set_active b` (or a if yours is set to b already) and after rebooting it failed to start ocean 9 instead of 10. Success ?! On the second reboot it came back up normal, which allowed me to do a normal backup of things before getting into the hassle of upgrading (which I have put off until I have more time).
Click to expand...
Click to collapse
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
WoKoschekk said:
That's the advantage of the A/B partition scheme. I already advised him to do so in post #6...
BTW: "adb devices" will recognizes your device only when fully booted up into system or TWRP.
Click to expand...
Click to collapse
Seems I was selectively blind I read #5 and #7 and somehow skipped that one exactly.
It's been a while since I did anything with adb, so I wasn't sure about when it detects things. I tried getting into TWRP, but at least on the A partition TWRP had been wiped by the update.
Anyway thanks for the solid advice!
Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashing recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Please can you help me? I tried with some tutorials, but no success...
What did you try doing if OTA wasn't working?
You won't be able to use TWRP since you're on Android 11.
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
I would disable the magisk modules first in case that is what caused problems. Then do a local upgrade using the full OTA zip. Then install magisk to the inactive partition. I think that would work, but I'm not sure if a messed up A partition might affect the installation. I don't think so, but I haven't read anything about it. After, you can try re-enabling the magisk modules.
I turned off all the modules obviously and still OTA is not working via the oneplus updater. It does not see the zip rom even though it's in the main directory. I don't know what is wrong...
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
L
trinidude4 said:
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
Click to expand...
Click to collapse
Lol yes you're right it was jar. Now the updater sees the zip file, but I'm afraid to update because I'm not sure if the phone won't brick or bootloop. What do you think?
I think it should be fine. I think the only thing that got messed up was the boot partition on the A slot and that will get overwritten with the OTA.
How about the root and magisk?
Okay I updated and it's working fine. I'm on 11.0.7.7 but now magisk is not working, how to get it back?
remialfa said:
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
Click to expand...
Click to collapse
Any idea if it's possible to do something similar to rooted OP6?
I have a similar situation where I tried to update magisk and ended up with a bricked device.
I can reboot to fasboot, but I can't boot to recovery or flash anything through some pc flashing apps.
Hello all,
Everything was working on my rooted oneplus 7 pro, until I applied the latest OTA update. Once that was installed and the phone rebooted, my once working mobile network was no longer working. The phone says no sim card detected and every few seconds the default phone app displays the force close crash dialog. Has anyone else encountered this issue? It looks like rolling it back to the previous OxygenOS version is the only solution, but I'm not quite sure how to go about that safely. Any help would be greatly appreciated.
The device is using Magisk and TWRP
I also tried uninstalling Magisk, but that did not resolve the issue.
Have you tried just doing a reset in settings?
.This is how I install stock oos
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage,or copy to otg drive,Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
7. If root is needed fastboot flash magisk patched boot.img
I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks
ChimmyChanga said:
I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
I don't have the oos 11 off hand , I know you can download the latest and greatest directly from OnePlus website under support
I have the same problem i cant do nothing
No SIM card, or No network available -- Any help would be kind and appreciated.
At the start:
Oneplus 7 pro - GM1915 /US- active t-mob sim
LOS 18.1 (latest)
magisk 22.x upgraded along the way to current magisk 25.2, 8.0.7 app
Running LOS recovery ##// no issues since 18.1 came out
USB 2.0 port(s), good'ol red/white cable(s). ##// verified cables/ ports.. typical troubleshooting to rule them out)
Current Platform tools in $PATH
Issue. No SIM card.
Steps to masonry school:
I upgraded my LOS 18.1(magisk 25.2 persistent) to oos 12, then went to LOS 19.1. The update(s) went fine, or so it seemed... Booted fine. Still rooted. All's good until reboot. Then no SIM card found.
Mess around with turning off wi-fi, nfc, mobile data turn on airport mode... all iterations of that..
Occasionally it saw the sim card! Says, "Network unavailable." Shows T-mob on sim 1... Thinks it has 2 sim cards... ##// can't help but think this might be something
Set APN T-mob blah blah... wait.. go to local t-mob verify my sim is provisioned properly get new sim..
Their take is(of course) it's time to upgrade lol... Got a spare $800 laying around? If not, you can pay for it after there is no longer a recession lol... I digress(in distress)
##//
I started having worse problems upon performing the next 19.1 LOS_11-13-22 ota.
Immediately I got into a bootloader loop. I first tried my patched_110622-LOS_boot.img and got nothing but a seemingly successful boot, then those lovely "Power Off" words and back to bootloader.
Once back in fastboot I changed partitions(keep in mind I have not flashed anything to alter the LOS 19.1 boot restructuring at this point. Reboot. Same outcome. Bootloader loop. Booting to recovery, start, power off or bootloader all do the same thing... quickly reboot into bootloader.
I then decided to boot to twrp. I went ahead and did this
#>/ fastboot getvar all ###/// yielding partition a
#>/ fastboot flash boot_a twrp.img
#>/ fastboot boot twrp.img
The screen goes to "fastboot mode" and hangs. power+up_vol & it finally boots into twrp.
I then twrp installed the LOS update, which lead to more bootloops. Various dalvik cache/data and cache wipes after flashing, factory reset won't complete the reset... I have exhausted my limits of attempts at this point, so off to MSM I am.
All versions/drivers correct. On a win10Px64 now. Connects fine.
Now this is where it gets odd(to me anyway). I tried to go to stock oxy10, for GM1911AA and it hangs on the param preload. Something I don't remember seeing since 2020'ish. Tried multiple firmware until it took one, that was H.30. Successfully flashed. Booted. Found SIM card. Thought that was it.. Then I unplugged my usb cable from the op7p and *poof * reboot. After much digging and changing metedata preloads, various things to try to get this thing to work.
Current:
I can get it to run LOS 19.1 No SIM card found. Rooted with twrp and magisk no prob.
Just can't get it to work with the SIM, whether seen or not.
I am suspicious that I should have used H.31 for the MSM... however now it won't get past param preload with anything earlier than 11.5.1 Oxy 12. Also, I even went so far as to try flashing the CB firmware variant to see if it would take the T-mob firmware. Won't let me, says not compatible. So now I have a rooted op7pro that can only communicate via signal lol.. and not long at that...
Any thoughts/help/direction/suggestions, would be greatly appreciated.