Recovery destroyed after booting into the firmware - Realme 5 Pro Questions & Answers

Hello everyone.
I installed the in-depth app on the realme ui, followed every step according to the guide.
Booted into the fastboot mode
ran the unlock command
installed the vbmeta and then twrp
then booted into the system. My device booted up fine.
But then I had to install the pixel experience for which I wiped system, data, cache and then installed the realme ui firmware as it was required before installing the pixel rom. But the pixel rom could not boot and when i reverted back, it says recovery destroyed.
I can boot into fastboot so tell me what should I do.

Reflash TWRP using Fastboot commads.
If Your TWRP is replaced by stock recovery, it is a bug in twrp. Reply if you are having this problem.

Related

I have wiped my system by the TWRP recovery

my device is f1f
I accidentally wiped my system using TWRP recovery so there is basically no OS on the device
how can I move from there to get my device functioning again?
I have downloaded the stock rom but it refuses to being flashed by the TWRP recovery
​
Put back the ColorOS recovery and install ColorOS zip from OPPO. Or switch to CM13.
no further help needed guys, I solved it on my own
I flashed stock recovery using adb command by those two lines
fastboot flash recovery stock-recovery.img
fastboot boot stock-recovery.img
and then flashed stock rom using stock recovery and it worked well

No fastboot in recovery after TWRP installed failure

Ok.... So i unlocked my bootloader on a verizon pixel and installed magisk with a patch boot image. no problem
I just tried to install TWRP (3.2.2). I booted the image first, the flashed the TWRP zip in the booted image. Then TWRP would boot, but only TWRP would boot. it would never progress to booting up the rom.
So i found a thread that suggested flashing the magisk patched boot image.... that just made it worse. It would only boot to recovery... and NO FASTBOOT. I was able to get to the menu and use adb to side load the latest OTA. Now i can boot into the ROM and use the phone as usual
However, I still don't have fastboot in recovery mode. I don't think its drivers. I must have mucked up recovery. It gotta be related to the TWRP snafu. I can boot into the stock boot loader and my PC beeps and recognizes the phone, when i use the arrows to go to recovery, my pc loses the device. My PC just can't see the pixel in recovery mode.
Not sure how to proceed
Can I side load the factory image after removing the wipe tag (-w)? Do i need to factory reset?
Am an idiot.... fastboot works in bootloader.... please delete

What's New(?) procedure to install Custom ROMs coming from OOS 9.0.5?

Hello guys,
I'm having trouble trying to install a Custom ROM (Tresk Mod, but I get it with others too)
So basically some days ago my whole Internal Storage got encrypted so I had to a full wipe.
From there I decided to use Msmtools just in case, so I got back to OOS 5.1.5 from there I updated to OOS 9.0.5 via OTA and unlock the bootloader and install TWRP everything works fine.
But when I tried to install any custom ROM I either cannot boot and just boots to Bootloader (Not even the recovery works) and I get "Failed to load/authenticate boot image: Load Error" which I can fix fastboot flashing all the partitions...
Or I straight get a black screen with the White Notifications LED whenever I try to boot either to system or recovery and from there I can only recover using Msmtools...
So I'm now asking, what are the steps for flashing Custom ROMs now?? Because seems like I'm doing something wrong since I'm ending having a Bricked device...
try to flash rom with bluespark recovery
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Mdknight said:
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Click to expand...
Click to collapse
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Mdknight said:
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Click to expand...
Click to collapse
I finally figured it out
The problem was that as I was updating via OTA OOS 9.0.5 was only installed in one Slot so I need to install it in the other as well.
Did the following process:
1. Boot to Bootloader and do "fastboot boot TWRP.img"
2. From there flash TWRP.zip and Reboot back to it (Recovery)
3. Flash OOS Latest (9.0.5)
4. Flash TWRP
5. Reboot to TWRP
6. Flash OOS Latest (9.0.5)
7. Flash TWRP
8. Reboot to TWRP
9. Wipe data, dalvik cache
10. Flash ROM
11. Flash TWRP
12. Reboot to TWRP
13. Flash gapps + Misc (Magisk, etc)
14. Boot system
Technically just one 1 installation should do as the other slot was already populated but the twice just to be safe.

Bricked device?

I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.
you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .

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?

Categories

Resources