Database Info

Seeking to solve how to successfully enter the ROM

Can anyone tell me what is the reason for the failure to flash the third-party ROM? The phone has been unlocked, and the twrp that was swiped is twrp-3.3.1-24-I01WD-Q-mauronofrio.img. The method I swiped in is to double-clear and then select the rom to flash in. The flash is successful but the system cannot be restarted Boot, can only be stuck in fastboot, seek solutions

There are a couple of similar threads from people with similar problems. Have a look and see if you can solve your issue. If not, feel free to ask again and provide more detailed information about what you did and what did not work.

Unofficial twrp can be successfully brushed in with adb, and the success rate is also high. The probability of official twrp brushing in is greater, but it can also be brushed in, but the official twrp brush third-party rom is easy to fail, the reason is unclear, unofficial twrp brush It is easy to succeed in the third-party rom, but why can't the boot be stuck in fastboot after the unofficial twrp is flashed into the rom?
Because zenfone6 is the ab partition, I think this may be the main reason for not booting. Is it possible that the two partitions are not flashed into the system, and only one partition is flashed into the system, so it will not boot!
I flashed in the rom twice and couldn't boot. The specific method of flashing the phone is: the mobile phone system is the latest system, first use adb to flash into the unofficial twrp (twrp-3.3.1-24-I01WD-Q-mauronofrio.img), flash in Successfully, the phone automatically enters twrp, and then flashes the unofficial twrp in zip format again (twrp-3.3.1-24-I01WD-installer-mauronofrio.zip), restart twrp, click wipe, and swipe to complete. Click lnstall, select rom, and swipe to complete, and click wipe again to complete the slide. Click lnstall, select rom to complete the flashing, click to restart the system, the phone cannot boot, only fastboot.
The above method can not boot, I connected the phone to the computer and re-brushed into twrp with adb. Note: When I first flashed into twrp, the phone did not restart to twrp, but booted to the official system to restore the factory interface, etc. After the operation of the mobile phone is completed, boot up and enter the desktop. I turned on the USB debugging. At this time, the mobile phone can enter the unofficial twrp. Then I flashed into the rom again, and then did not restart the system. I restarted twrp, but the mobile phone reached fastboot again. What I thought was Restart twrp when flashing for the first time, flash once, so that both partitions can flash into the system, but twrp cannot be restarted, only fastboot!
Guiqiu you guys to solve my problem, can't the phone be broken?

OP6 won't get past bootloader after upgrading from 16 to 17.1

I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..

I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom

TWRP 3.5.0 Installation Silently Fails

Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU

Same question here. It seems that you can only boot from TWRP, not install it.

Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.

TWRP shows internal storage folders named as random letters.

I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help

does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)

User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password

#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.

the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.

User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though

Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse

Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully

Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD

#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!

#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?

you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.

I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine

Can't use TWRP in slot A

Hit a nasty issue while trying to upgrade from LOS 17.1 to 18.1. Story begins here.
After not getting anywhere with a normal clean-flash, I backed up all my stuff and totally wiped my phone using a fastboot rom (OOS 10.0.8, here). I applied the fastboot partitions, and then the "criticals" from TWRP, so my phone should be 100% stock OOS10 at this point.
At this point, there is strange behavior. From fastboot, I can boot into TWRP with fastboot flash boot /path/to/twrp.img only if the active slot is B. Running this command with A active, then rebooting to recovery, just kicks me back to fastboot. With B active, rebooting to recovery works as expected.
This is the behavior for the official 3.5.2_9-0 TWRP release. Using mauronofrio's unofficial 3.4.0-10 release, I get a flashing TWRP splash screen instead. I can use adb in this state, but twrp commands don't work (says TWRP isn't running). Official also has issues decrypting data/storage, so I'm sticking with unofficial 3.4 for now. I've also tried with the LOS recovery img, this has the same behavior as 3.5.2 official TWRP.
By flashing TWRP to slot B, I can then do a bunch of different things, none of which get me working TWRP in slot A:
Factory reset, flash OOS11, reboot recovery
Gets me the stock OOS recovery. Works, but can't flash anything.
Factory reset, flash OOS11, flash TWRP, reboot recovery
Same old slot-A-TWRP behavior as when booting from fastboot
Factory reset, flash OOS11, flash TWRP, reboot system
OOS11 works as expected, but if I reboot recovery, same old slot-A-TWRP behavior
Install a TWRP zip, which flashes both slots, then manually set slot A as active and reboot recovery
Same old slot-A-TWRP behavior
What could possibly be causing this?

I have found an incredibly complicated workaround:
Reboot fastboot
Flash mauronofrio's OOS10 fastboot rom (to A & B)
Reboot fastboot (just to be sure)
Flash boot twrp (to slot B)
Reboot bootloader (into TWRP)
Factory reset (just to be sure)
Flash OOS11 (to A; for vendor firmware etc)
Factory reset (just to be sure)
Flash LOS18.1 (to A)
Reboot system (to A)
Complete first-time setup and run a system update (to B)
Reboot recovery (to B; LOS recovery, not TWRP)
Factory reset
Flash gapps, magisk, etc
The magisk install didn't work quite right, but Nikgapps seems fine. This is the only way I've been able to install LOS18.1 with gapps. However, not having TWRP to create backups is concerning. Really, having an unreliable recovery is terrifying.
So, I'm going to load my LOS17.1 backup and wait for the dust to settle on the LOS18.1 ecosystem.

What!! awesome!!!
I am working on developing this logic, how?? Fantastic!