I have wiped my system by the TWRP recovery - Oppo F1

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

Related

[Solved][C2105]Can't install custom recovery with anything contanining FOTAKernel way

Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!

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 .

installing TWRP dont work

I have two devices where install TWRP dont work.
They are unlocked and i try many times to flash it via fastboot but booting into recovery ends in stock recovery.
Is there any solution to install TWRP or lineageos another way?
it was the issue that recovery is overwritten on stock rom start if the system has ever made an update

Recovery destroyed after booting into the firmware

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.

Question Flash TWRP and custom rom

today the 168 waiting time has expired and I was finally able to unlock the bootloader. Now I'm trying to install TWRP to be able to install ArrowOS, I do everything I have to do via fastboot, I put "fastboot flash....." etc and all good, when booting, it boots in TWRP, but when I reboot to the system and enter the recovery again I get back the MIUI recovery, something I'm doing wrong? I have tried installing the .img directly from the twrp recovery in the first boot using "fastboot reboot" after flashing and nothing. Should I install the custom rom on the first boot from recovery?
I had the same behavior on reboot into stock firmware when I installed Lineage Recovery. My guess would be that the stock firmware is actually rewriting recovery if it detects that it's not original but I haven't really investigated it.
MIUI recovery didn't come back after I flashed the system image of a custom rom.
T.Anri said:
I had the same behavior on reboot into stock firmware when I installed Lineage Recovery. My guess would be that the stock firmware is actually rewriting recovery if it detects that it's not original but I haven't really investigated it.
MIUI recovery didn't come back after I flashed the system image of a custom rom.
Click to expand...
Click to collapse
Do you install the rom directly after flash the lineage recovery and booting on it? without rebooting or something
chavaa said:
Do you install the rom directly after flash the lineage recovery and booting on it? without rebooting or something
Click to expand...
Click to collapse
Read here if you have issues with flashing custom ROMs.
https://forum.xda-developers.com/t/4288121/post-85137963
If your OS is Official MIUI, the recovery will always be replaced with MIUI recovery on every boot.
Try Orange Fox as recovery, it has an option to prevent recovery from being overwritten by stock recovery, but i dont know wether orange fox works with lineage os. I run it with AICP and it runs like a charm..
I haved the same problem when I haved a whyred (redmi note 5 pro), the solution is very easy, when you have the blue screen of the CMD (now powershell), you need to put "fastboot devices", then put "fastboot boot <twrpfilename>.img, this action will do the device restart in TWRP, then you need to copy and paste the twrp.img in a folder of the device, any folder, it doesn't matter. Then go to install, choose the option "Install image", and go to the folder where you copy the file twrp.img, pick it and choose the option "recovery", then install.
That should be works.
Sorry for my english, I'm trying to learn.

Categories

Resources