Develop Bugs

Phone always boots into twrp not able to see one plus boot logo.Pls help

I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue

Flashing a lower version and then the 28 version back helped me... Had the same problem

jaganmohans said:
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Click to expand...
Click to collapse
1 ) flash stock recovery and sideload full zip of 3.2.8 oxygen os
2) boot to system
3) reboot to stock recovery
4) sideload full zip of 4.0.1
5) boot to system
6) boot to bootloader and flash twrp -28 recovery (adb fastboot flash)
7) after flashing boot to twrp recovery from bootloader
8) flash SU SR2 v2.79 and boot to system

Android 8 update with FlashFire breaks TWRP or TWRP boot-loop

Hi everyone,
I tried to update my rooted Pixel C with Android 8 and TWRP 3.1.0.0 from August build to September build with FlashFire.
All of the following have I done on my Nexus 5x as well and it worked as a charm there.
Therefore i dl'd the corresponding zip-file from google dev page and started the update with FF. It said to me it can update the boot, system, recovery and vendor partition so I unchecked the recovery partition only to keep TWRP. I also told FF it should include SuperSU again to root the new Android.
After the update the device was unrooted, so i tried to start into recovery to install superSU manually. But TWRP was gone and i get everytime the android on the back with the text "no command".
Therefore I tried to flash TWRP with NRT again. But after the flash the device always starts into TWRP and Android isn't starting anymore.
I can use NRT again to flash Android without loosing my data but than TWRP is gone again.
So either the device always starts into TWRP or I have no recovery installed.
Anyone an idea what i can do to flash TWRP again and to fix the boot order or whats broken than?
Regards,
flattervieh

I don't have the C but here's what I would try. First, have your device booting normally with the stock recovery. Then use fastboot to boot into TWRP, not flash it. When it boots into TWRP then flash supersu. From TWRP then boot back into the bootloader and then flash TWRP with fastboot.

Flash the latest (beta?) TWRP. It allows reading the encrypted data folder.

Short notice, i'm still struggling with the problem.
In the meantime I tried the following:
1. I temporarely booted TWRP 3.1.0.0, with this version I was not able to encrypt the data partion (always invalid key) but I was able to see the system partition and I installed SuperSU. After that i restarted into the bootloader and flashed TWRP 3.1.0.0.
This led to the same phenomenon, that my pixel always boots into TWRP and not into Android itself.
2. Same thing as before but with TWRP 3.1.1.1.
With this version I was able to see the size of the data partition, but I was also not able to read or write onto it. (Again invalid code) I installed SuperSU and made a device restart without flashing TWRP 3.1.1.1.
This led to a totally softbricked device with a boot into "no command" screen.
After flashing Android again via fastboot Android starts correctly and I can use the device but root is still not working.
Regards

I'm not sure why twrp isn't sticking. But the android on its back with "no command"is the stock recovery. To get into it simultaneously press and release the power and vol up keys. You might have to try it a few times as the timing can be very finicky. From there you can boot into the system, you don't need to flash the factory image and start all over.

Honor 7x bricked

model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 10 (boot image)
Error NO : 2 (load failed)
Click to expand...
Click to collapse
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.

AlexLebul said:
model: BND-L21(c432)
bootloader unlocked
FRP unlocked
My phone was running omnirom beta 5 for 2 months, was rooted with magisk (patched_boot flashed in ramdisk_recovery partition)
The bluetooth wasn't working so I wanted to install phhusson aosp 9
So I flashed emui 8 stock recovery then tried to flash phhusson aosp 9 as a system image in fastboot
Now, when the phone boot, it shut down instantly then boot into erecovery without the ability to factory reset or wipe cache (the only thing I can do is "reboot", "shutdown" and "download latest version and erecovery")
What's working and what's not:
access to erecovery (with ability to wipe cache and factory reset) when the phone is powered off then I press power & vol +
can't access twrp (even if the flash on recovery_ramdisk succeed with fastboot )
access to fastboot mode
access to erecovery (without the ability to wipe, only "download latest and erecovery) when the phone try to boot
access to dload installation
Here's my tries to fix the issue:
after installing emui 9 through fastboot: honor boot animation for 30-40s then bootloop
after installing emui 5 or 8 through fastboot: boot into error mode which displays this: (I can't flash ramdisk or boot (error: partition length get error))
dload installation don't work, even with service rom
tried installing phhusson aosp 9 and omnirom beta 5: boot into rescue mode error
huawei multi tool failed
hwoat failed (I can't reboot into twrp)
erecovery "download latest version and erecovery" failed
My thoughts are that my BOOT is broken, but since I can't flash a new one, I don't know what to do.
Click to expand...
Click to collapse
I had the same error "error: partition length get error" with my BND-L24. What I did, I found the stock rom from the firmware finder application. Unloaded the boot.img and flashed it without any issues.
I used the guide in the OpenKirin webpage to find the correct rom (you can check the info of your phone using fastboot commands or download multitool and read the phone info there) and to extract the .img files (go to Openkirin webpage and press support for the guides).
Good luck!

i, I have an issue with my phone and would need your help in recovering it back to life.
I have rebranded mate SE to Indian version few months back. so far so good. I have unlocked bootloader and started playing with it by downgrading etc.
the current situation is the phone is bricked with a android pie erecovery and no boot. tried using all the roms visiting various threads here with no luck (including service rom, multi-tool flashing etc)
multi-tool says Orio version 8.0.0.375. I am not able to flash any Oreo images since multitool says partition mismatch (boot, recovery etc) but when I flash 9.0.XX versions or Nougat versions, system is flashed successfully, yet, boot loops and back to latest erecovery.
don't have twrp (despite multitool flashing is successful) all I get is phone boots only to erecovery (latest)
unable to flash any stock recovery or kernels - as multitools says, partition mismatch.
I tried above method of boot.img flashing but multitool says partition error. tried various boot.img (EMUI 5 / 8 / 9) with no luck.
any help? suggestions?

I had a similar issue the last two days. The only thing that worked was rebooting to fastboot. I tried to get back to Oreo but used a method, that bricked my phone since it flashed an older kernel.img. I got it back running by detecting the version of the bootloader with Multitool and fastboot-flashing recovery, kernel and system that have been aligned with that version.
Be aware: You will have two recovery partitions:
- Huawei has renamed the partitions from "recovery"/"recovery2" to "recovery_ramdisk"/""erecovery_ramdisk"
- unlocking the bootloader does only let you flash recovery_ramdisk
- if you boot into recovery (Pwr & Vol+), the image from erecovery_ramdisk gets loaded
- To boot into recovery you are able to flash, it requires three buttons to be pressed (Pwr & Vol+ & Vol-)
- To flash erecovery_ramdisk, you have to flash TWRP into recovery_ramdisk and from there you can install an image into erecovery_ramdisk.
After having flashed back everything to 9.1.0.162, it was possible to format damaged /data and to setup the device via erecovery and WIFI.

Problem flashing TWRP

Attempting to flash TWRP on my Mi max 3 but encountering problems.
MIUI version: MIUI 11.0.3 Stable. 11.0.3.0 (PEDCNXM)
Android version: 9
Android security patch level: 2019-10-01
Before everything I successfully unlocked the bootloader (didn't have to wait at all, was instantaneous).
Then I tried to flash TWRP images from twrp.me, I tried both versions twrp-3.4.0-0-nitrogen.img and twrp-3.3.1-0-nitrogen.img.
This what happens: https://i.imgur.com/YAE4E62.png
I then attempted another method I found (https://forum.xda-developers.com/mi-max-3/help/flash-twrp-rollback-warning-please-t3926026) : instead of flashing recovery from PC, I tried to boot into twrp (fastboot boot twrp.img) and flash from within.
I pasted the twrp.img in the internal memory, along with magisk.
I successfully booted into twrp but it could not read my internal memory properly? I could not see the twrp.img file to flash. I also couldn't see the magisk.zip file.
So I then pasted the twrp.img onto the sdcard, success. I could now see the file so I attempted to flash the recovery but I received errors; https://i.imgur.com/LLYEv11.png
I then rebooted to recovery, it booted into TWRP, it seemed to have worked? But it still couldn't read my internal memory properly, only sdcard. I did not install magisk.zip here, I was worried I would brick it now.
So I then booted to system, it seems to be fine. Tried to reboot back into twrp, it reboots back into the default 'mi-recovery 3.0'. I tried this with both twrp3.4.0 and twrp 3.3.1. Same results.
What am I doing wrong? Please help.

LG F400S/K Kitkat unable to install TWRP recovery / unable to install Gapps (solved)

Now the phone is unable to boot to system, I have no idea what I could do to fix it as there is no way to use adb or fastboot command…
I remember that the stock rom version is S11a, it have some problems when I tried to root it, and failed to flash recovery even I've got the root permission (response "write error: no space left")
------↑solved by using LG flashtool↑------
Now I am facing the problem that unable to install TWRP recovery using dd, it responds “ write error: No space left on device” I’ve reinstall the LG drivers, reboot the phone, reboot the computer, unroot and root again, but the problem still occurs.
----- update ------
solved by using flashify, and TWRP version 3.3.1 instead of latest 3.6.1, so that it won’t have “secure boot error” warning, and boot to recovery successfully.
But there is a new problem now, when I tried to sideload MindTheGapps after installed LOS 18.1 successfully, it warns me “could not mount /mnt/system! Aborting”. This is the third phone that having this warning for me, and I still couldn’t figure out which step goes wrong.
Nothing goes wrong after flashed to lineage recovery, installed MindTheGapps now.
--update--
I also tried to flash lineage recovery from TWRP on my D855, it also works, I installed MindTheGapps and everything works fine. So this is the problem of TWRP? Or reinstall the recovery is the solution? Maybe I would have a test later.