TWRP malfunction success flash but nothing happens - One (M8) Q&A, Help & Troubleshooting

Hi can anyone help me out? Im using TWRP and on sd redbulled v20 I want to change rom after booting on TWRP wiping and flashing a new rom it success after 2-3 seconds and nothing happnes same as old rom, I tried to update the TWRP on latest version now it says unable to mount cache and more over it saying full selinux support is present upon wiping
please help

What hboot number, and what TWRP versions did you try?

Related

[Q] Bootloop on recovery

Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
offti1 said:
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
Click to expand...
Click to collapse
Flash the PIT file together with a 4.1.2 stock firmware downloaded from SamMobile. Root and do whatever you want after.
My mix is CyanogenmodX (by UtkarshGupta)+f2fs+agni. It's kinda weird and I did not found someone else with this problem except this topic. I did a lot of reflashing to nail it down to the following:
I'm stuck with a twrp loop (twrp logo appears and then reboots) when using f2fs (/data only) and the system is installed. This problem is now for some months, before it worked fine with the same setup. Also complete wipes of all partitions and even repartition did not help.
-It works as long as there is no OS present or not booted for the first time.
-To fix it, I can either format /system or /data (to ext4). To do that, I have to flash an other recovery.
-It does not matter if I use the format script (as provided in the OT), or with twrp advanced wipe/change partition type (which only works if TWRP is not newer than 2.8.1.0 - newer versions give an error: unable to wipe data).
-The OS itself runs fine.
A strange thing to note: there was a time, where this problem occurred, to fix it, I had to flash an other recovery via odin, boot into that recovery, do nothing(!), reflash twrp with odin again, and I could access twrp again until I booted the OS again. This suddenly stopped and the only fix is the way I described above.
And a site note: the "loop" only occurs when using the advanced reboot options from the OS (or any other tool from the OS to boot into recovery), as it sets a recovery flag. When using volup+home to access recovery, it only happens once, still allowing the workaround to flash another recovery to remove the flag, and able to reboot system afterwards again (but no access of twrp anymore).
I also tried updating bootloader (and modem) with no success.
Process on installing: wiping everything except externalSD, change /data to f2fs, reboot recovery, install CMx, gapps, supersu, agnikernel.
Aaaaany input that might help to resolve this is really appreciated.

Please Help!! Phone reboots to TWRP and not to system

Please help me,
i have the MIUI8 Developer ROM and i updated it to Version: 6.9.8 (MIUI8) yesterday and found that root function was not working so i installed TWRP recovery again and since then my phone is just rebooting to TWRP.
I tried wiping the data, factory reset, restoring from CM13 backup and MIUI8 Stable ROM backup, installing new ROM but the phone is just rebooting to TWRP after all that.
I also tried this from an earlier post:
http://forum.xda-developers.com/showthread.php?t=2451696
still nothing works.
Please help me resolve this.
I had a similar problem. I fixed it by fastboot flash using the stock rom which would also overwrite the recovery partition. Then flash back TWRP and CM13. Save your data using TWRP before doing any destructive writes.

[help] 5t just booting into recovery

Okay guys, I tried flashing the latest Open beta and am facing a problem.
I was not decrypted and the TWRP flashing completed successfully but it is only booting into recovery. Mounting the MTP storage in TWRP on the computer shows the storage in full.
I flashed the stock recovery and sideloaded the Open beta. It flashed successfully but then too, it is only booting back into the stock recovery and is not booting system. Please help guys.
Any pointers on how to fix this? please...
You may need to flash the factory images manually using fastboot
The radios modem etc.... And clean wipe
Did you try factory reset and flash Official OTA from One plus ?

Flashing Custom Roms from A10; Bootloop

Hello,
I've been trying to flash /e/ or carbonOS with no success. I flashed the stock OS (Newest Android 10), booted, configured, and enabled USB debug, rebooted to recovery, booted into twrp (3.3.0), installed twrp, rebooted into the installed twrp; this is where my first problem is, I cannot mount /system. I can wipe it. Once I format everything and try installing either /e/ or CarbonOS; neither boot. Once I reboot out of twrp, I get the error that says there is no OS installed.
I know I'm doing something worng, so any help is appreciated
Is anyone else experiencing this issue? and is there a fix for this issue?
Thanks
Will
xer01ne said:
Hello,
I've been trying to flash /e/ or carbonOS with no success. I flashed the stock OS (Newest Android 10), booted, configured, and enabled USB debug, rebooted to recovery, booted into twrp (3.3.0), installed twrp, rebooted into the installed twrp; this is where my first problem is, I cannot mount /system. I can wipe it. Once I format everything and try installing either /e/ or CarbonOS; neither boot. Once I reboot out of twrp, I get the error that says there is no OS installed.
I know I'm doing something worng, so any help is appreciated
Is anyone else experiencing this issue? and is there a fix for this issue?
Thanks
Will
Click to expand...
Click to collapse
I believe issue is because carbon is for pie not Q.
You'll have to roll back to August pie to flash any of those ROMs. There are no available 10 ROMs yet.
I'm assuming devs are waiting for a TWRP update.
Otherwise we'd see some by now

[AOSiP, Android 9] Not booting after OTA on encrypted device

I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!
Have you tried installing another kernel?
kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?
SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!

Categories

Resources