Database Info

OP6 got stuck with corrupted internal storage

Hello, i'm a bit in trouble with my internal storage.
Yesterday i wanted to update to newest havoc os so i prepared as usual and wiped system and data under advanced wipe in TWRP ( twrp-3.2.3-0-enchilada(mtp) from joemossjr ).
Then things went strange... op6 reboots itself and since there was no system installed got stuck. i rebooted to TWRP and it started like first time install.
I wanted to do the TWRP Setup but TWRP freezes everytime and after some seconds the device reboots.
I tried different TWRP (joemossjr, eng.stck), tried flashing manually with fastboot flash boot_a twrp.img fastboot flash boot_b twrp.img and even with Tool All In One from mauronofrio
but only recovery that doesn't freeze is newest official TWRP 3.2.3.0.
But now i can't get access to my internal storage. The TWRP filemanager and adb shell are showing weird folders ( see attached jpg ).
It seems something is corrupted... i also tried to flash stock op6 rom in fastboot "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT" with flash-all-partitions-fastboot.bat.
Seems to work but got stuck at bootanimation...
flashed back official TWRP and i think i have to install magisk now but don't know how to do because i have no access to my internal storage.
at this point i wish they would have included a sdcard slot
suggestion anyone?

It's not corrupted, but it's encrypted, when you flashed the havoc rom you kinda ****ed up with the encryption method so now you got files that are encrypted and that you can't decryp, so your solution is to format your internal storage, sorry for you, and if anyone have another solution i would take it

do an adb sideload for magisk zip , that should help

adb sideload sadly doesn't work, just "Starting ADB Sideload feature" ...
and on cmd when i try to adb sideload i got an "error: closed"
can't figure out why the files should be encrypted... makes no sense to me

now i flashed flash-system-boot-vendor.bat
phone boots till startup wizard and then after few seconds freeze and reboot

gdre said:
now i flashed flash-system-boot-vendor.bat
phone boots till startup wizard and then after few seconds freeze and reboot
Click to expand...
Click to collapse
Format data. Problem fixed. This is the ONLY SOLUTION that will work.

Yup, you need to format the data and start all clean and i hope you did a full twrp backup

yes i do always make a backup before flashing something... my problem is i don't have access to files on internal storage.
Data partition is not my problem because all my apps are stored with titanium backup but in the freaking internal memory.
i wiped data partition but it doesnt help... now i have all folders like after complete reset. but i dont know how to get access to my old files in /sdcard folder.
i think of deleting internal storage also and start from scratch and try some data recovery tools... maybe i have some luck.

use Tool all in one

gdre said:
yes i do always make a backup before flashing something... my problem is i don't have access to files on internal storage.
Data partition is not my problem because all my apps are stored with titanium backup but in the freaking internal memory.
i wiped data partition but it doesnt help... now i have all folders like after complete reset. but i dont know how to get access to my old files in /sdcard folder.
i think of deleting internal storage also and start from scratch and try some data recovery tools... maybe i have some luck.
Click to expand...
Click to collapse
Did you ever actually try to flash the Havoc update? What's going on is that you flashed a rom on the August security patch and OOS is still on July. You can't roll back to an earlier patch. Only a rom on the current patch will work.
If it doesn't work, as several have said, you have to format data, not just wipe. That will unfortunately, erase everything on your phone, but there's no other way to go back to OOS.

ok iElvis... things start getting interesting
hmm i want to try that but how should i be able to do that...
how does it work flashing the havoc with all in one tool or could it be done in fastboot mode per cmd?
the phone came with oos 5.1.5 and used that a while then with xXx NoLimits 2.4 over it for a few weeks.
after that havoc os from 6.8.18 for a month or so and i want that as daily driver.
then yesterday updated with fresh install to version from 28.8.18 and setup everything then after reboot wifi was complete dead and SIM also.
flashed newest smurf kernel over and all worked again till next reboot.
i decided to install again from scratch and thats the point where things getting weird...

gdre said:
ok iElvis... things start getting interesting
hmm i want to try that but how should i be able to do that...
how does it work flashing the havoc with all in one tool or could it be done in fastboot mode per cmd?
the phone came with oos 5.1.5 and used that a while then with xXx NoLimits 2.4 over it for a few weeks.
after that havoc os from 6.8.18 for a month or so and i want that as daily driver.
then yesterday updated with fresh install to version from 28.8.18 and setup everything then after reboot wifi was complete dead and SIM also.
flashed newest smurf kernel over and all worked again till next reboot.
i decided to install again from scratch and thats the point where things getting weird...
Click to expand...
Click to collapse
Yep, that's the security patch issue. Once you're on a patch, going back to an earlier one will break encryption. I don't believe there's any other option beyond formatting data.

iElvis said:
Yep, that's the security patch issue. Once you're on a patch, going back to an earlier one will break encryption. I don't believe there's any other option beyond formatting data.
Click to expand...
Click to collapse
ok... formated whole storage and installed OnePlus6Oxygen_22_OTA_012_all_1806140300_e4bacf-FASTBOOT_5.1.8.
but while first setup stll freeze and reboot. also wiped again with stock recovery with no change.
bootloader is unlocked... should i now flash patched boot image with magisk for 5.1.8?

https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Using this will save you time before you **** something up

gdre said:
Hello, i'm a bit in trouble with my internal storage.
Yesterday i wanted to update to newest havoc os so i prepared as usual and wiped system and data under advanced wipe in TWRP ( twrp-3.2.3-0-enchilada(mtp) from joemossjr ).
Then things went strange... op6 reboots itself and since there was no system installed got stuck. i rebooted to TWRP and it started like first time install.
I wanted to do the TWRP Setup but TWRP freezes everytime and after some seconds the device reboots.
I tried different TWRP (joemossjr, eng.stck), tried flashing manually with fastboot flash boot_a twrp.img fastboot flash boot_b twrp.img and even with Tool All In One from mauronofrio
but only recovery that doesn't freeze is newest official TWRP 3.2.3.0.
But now i can't get access to my internal storage. The TWRP filemanager and adb shell are showing weird folders ( see attached jpg ).
It seems something is corrupted... i also tried to flash stock op6 rom in fastboot "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT" with flash-all-partitions-fastboot.bat.
Seems to work but got stuck at bootanimation...
flashed back official TWRP and i think i have to install magisk now but don't know how to do because i have no access to my internal storage.
at this point i wish they would have included a sdcard slot
suggestion anyone?
Click to expand...
Click to collapse
This was happens every day after when i try to mod my device.
When i see weired Folder. I boot to fastboot then flash fastboot twrp. Img.(this will shows all folders with normal names)
Then flash liquid remix rom(its my saviour)
Then flash twrp.Installer.
Then reboot to Recovery and restore my liquid rom backup and boom its boot to everything normal.
Here i want to say that keep one liquidremix rom in otg pendrive.
After fastboot twrp command when u gets working twrp.
Install that rom via otg, and flash twrp installer and then reboot back to twrp and then clean flash rom u want it will work without doing formatting or fastboot flashing stock rom which erase everything everytime

@ whizeguy... did that as mentioned before and gave me the freeze after first time reboot
@ pankspoo... ok i cant understand what is causing this issue but if you say that did the trick for you than i will buy me a otg adapter and check that out.
silly that i already deleted everything and sadly with no affort...
but i dont understand why im not able to boot anymore even after deleting everything

gdre said:
@ whizeguy... did that as mentioned before and gave me the freeze after first time reboot
@ pankspoo... ok i cant understand what is causing this issue but if you say that did the trick for you than i will buy me a otg adapter and check that out.
silly that i already deleted everything and sadly with no affort...
but i dont understand why im not able to boot anymore even after deleting everything
Click to expand...
Click to collapse
Fastboot method of installing rom will work 100%, have u used flash all. Bat (just unzip ur downloaded fastboot rom, connect phone to comp in fastboot mode and click on flash all bat file) command while installation.
Use that command because u have soft bricked u r device.
That installation will boot to normal oos rom.
I think u r doing something wrong.

Hmm thats exactly what i did.
In cmd there are some errors like sparse blabla but finally it completes but with freeze and reboots during startup assistent.
I bought an otg adapter today. Flashed liquid remix and that worked! All seems fine no freezes and reboots but wifi and signal still broken...
Very confusing

gdre said:
Hmm thats exactly what i did.
In cmd there are some errors like sparse blabla but finally it completes but with freeze and reboots during startup assistent.
I bought an otg adapter today. Flashed liquid remix and that worked! All seems fine no freezes and reboots but wifi and signal still broken...
Very confusing
Click to expand...
Click to collapse
U have u r efs backup? If have then restore it via twrp.
That will give u ur signal and wifi

That is what im thinking of...in fastboot there are no infos at bootloader and baseband Version. unfortunately my efs Backup is gone since internal storage messed up.
If i could recover some data that could help but 2 tools i tried yet didnt work.
Tomorrow ill try making raw dump and see If this would help.. still looking for the best guide or method

Need help recovering my phone from bootloop after trying to update custom rom

Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc

Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now

twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.

Why nobody use orangefox?

is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable

joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.

Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you

Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.

CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John

Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.

Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"

You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck

junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John

Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.

I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.

junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John

Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John

I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things

aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.

Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks

aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John

Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.

firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.

Can't flash custom ROMs

I got my phone yesterday, and I can't flash custom roms. My phone gets stuck on the boot screen (the animation is working as expected) for over thirty minutes, then I give up. I am/was rooted on the latest stock image. In the Download folder, I put the ROM (I have tried with crDroid and Bliss), twrp.zip, nano gapps, and Magisk. I flash the ROM and TWRP and reboot into recovery. Whenever I do this, I no longer have a Downloads folder or files. So, not knowing what to do, I sideload gapps and Magisk and reboot system. Then, I inevitably get stuck on the boot screen animation. What am I doing wrong?

Hello have you try to format data before or after flash custom rom? Some rom don’t work if not do.

Are you familiar with A/B slot partitions and their related behaviors? It's markedly different from single slot systems.

c3drik 67 said:
Hello have you try to format data before or after flash custom rom? Some rom don’t work if not do.
Click to expand...
Click to collapse
I tried this. Unfortunately, no luck.
Dungeon47 said:
Are you familiar with A/B slot partitions and their related behaviors? It's markedly different from single slot systems.
Click to expand...
Click to collapse
I am not familiar with A/B slot partitions. I followed a guide step-by-step, so I wasn't too concerned about my ignorance. Should I be doing something special? Thanks.

Kama45 said:
I tried this. Unfortunately, no luck.
I am not familiar with A/B slot partitions. I followed a guide step-by-step, so I wasn't too concerned about my ignorance. Should I be doing something special? Thanks.
Click to expand...
Click to collapse
Yes. A lot. Get very familiar with how A/B slots work. It changes many things about the whole flashing process. Trying to do things the same way as before leads to exactly what you're experiencing.

Kama45 said:
I got my phone yesterday, and I can't flash custom roms. My phone gets stuck on the boot screen (the animation is working as expected) for over thirty minutes, then I give up. I am/was rooted on the latest stock image. In the Download folder, I put the ROM (I have tried with crDroid and Bliss), twrp.zip, nano gapps, and Magisk. I flash the ROM and TWRP and reboot into recovery. Whenever I do this, I no longer have a Downloads folder or files. So, not knowing what to do, I sideload gapps and Magisk and reboot system. Then, I inevitably get stuck on the boot screen animation. What am I doing wrong?
Click to expand...
Click to collapse
Same thing happened to me, I had to forced the phone off (Volume + and Power) without plug-in the USB after is off I went into EDL mode (Volume +- together and Power) then immediately plug in to your ready PC with msm already ready to go.
You might have to try it a few times...
That's what I did a while back.

Qualcomm Crash Dump Mode - PLEASE HELP - Hard Brick ?!

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.