Find 7 Can't install Working Recovery - Oppo Find 7 and 7a

SOLVED
I had to flash the recovery from here: http://forum.xda-developers.com/find-7/help/recovery-unbrick-t3199938 This recovery worked and my problem is fixed.
I am trying to return my Find 7 to the stock recovery so I can reinstall ColorOS. My problem is that no recovery that I try works upon flashing. I have tried both the stock coloros recovery and twrp, and both of them have issues that don't allow me to continue.
When I flash the TWRP recovery, I get stuck in bootloop. It doesn't attempt to enter TWRP, it just tries to boot as normal. I have wiped the system and all data trying to fix the problem, so there is no OS to boot into, leading me to be stuck on an infinite Oppo logo. (I have tried to enter twrp through power+volumedown and fastboot boot twrp.img, both give me the same result)
When I flash the ColorOs recovery I can boot into it but I get a very weird interface glitch. The recovery only is shown on the right side of the screen and flashes up and down so that I can't select any options. (I will include an image of this, as it is not explained very well)
I don't know what is wrong or what I can do at this point, I have been trying to fix this for 4+ hours. If anyone has any advice I would really appreciate the help.
(This is what is shown when booting into the coloros recovery)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

Lost custom recovery but still have root

I am running stock 4.3 rooted. When I rooted I installed custom recovery. My phone has been choppy lately so in hopes that it would make my phone run smoother I tried to go into recovery (first time in ages) to wipe cache and dalvik. When I tried to go into recovery I got a "no commend' error and then regular stock Android recovery started. In the background was a dead android robot with a "!" symbol coming out of him.
I wiped cache with stock recovery and then selected the reboot option. The phone didn't reboot, I got "error!" message and that was it. I powered down, restarted and everything is back to the way it was. But what happened to my custom recovery? What should I do at this point to get it back?
Only thing I can think of is at some point I accidentally clicked on the OTA update notification. So my phone tried and failed to update because I'm rooted. Could that cause problems? What should I do?
Just Odin Philz Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROM: WICKED X
Did you do as bilgerryan said? Would like to know the outcome of your issue.
Sent from my Note 4 using XDA Premium.

[Q] Help, TWRP and CWM somehow installed at the same time. can't boot into phone OS

So, I attempted to install Cyanogenmod via the installer, it didn't work. So manually, I went and looked up a tutorial and it said to install TWRP because cyanogen wasn't working for me. I installed that and I booted into recovery. It opened CWM, weird. So I try to start the phone, it boots into TWRP. eventually I attempt to install Cyanogen to see where it gets me, I install it and when I boot it does nothing. you see samsung logo then blackness. I am assuming because TWRP didn't get removed from it. I can still access recovery and download mode. What to do next Also flashing with odin did not fix it.
Flash a different ROM in recovery or the stock tar with Odin. Those are your only options. I also highly recommend Philz Recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROM: WICKED X
bilgerryan said:
Flash a different ROM in recovery or the stock tar with Odin. Those are your only options. I also highly recommend Philz Recovery.
My ROM: WICKED X
Click to expand...
Click to collapse
Do you think that it's TWRP stopping it from starting?

Unable to flash xposed

I am running nougat 7.1.1 on oneplus 5t phone. It is rooted.
I am using [BLACK]twrp-3.2.1-0-20180309-codeworkx-dumpling.img Recovery which I downloaded from this link
https://forum.xda-developers.com/oneplus-5/themes/theme-black-themed-official-twrp-t3651669
When I boot into recovery I am getting these jumbled up letters when I navigate to sdcard folder. What should I do to resolve this error.
I downloaded xposed apk, installer zip and uninstaller zip.
Then I installed the xposed apk, then rebooted my phone to recovery to see this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What should I do to resolve this issue?
Try reflashing your recovery, or flash blu_spark recovery.
You get these random letters because your haven't decrypted your data in TWRP.
Encrypted devices have to enter a pin everytime it enter TWRP, if you press cancel (not sure if you did) it will result in seeing these random letters / encrypted data.
I flashed the native TWRP for my phone. Now the problem is gone.
The earlier recovery was also a compatible one. It was from a reliable source - XDA and was posted by a senior member there. I got an option to write text in the beginning with that recovery but I couldn't find the "write your password" option. It only said "decrypt your phone" and I was clueless that I had to enter my pin. Everything is all cool now. I'm grateful for your reply. Thanks for answering.
What is the advantage/disadvantage of encrypting or decrypting phone? If my phone gets stolen, no one can access my data as it's protected by fingerprint and pin lock. Or does encrypting makes things safe?

Unbrick H815 after wipe

Hello guys,
I have an OEM EU (I guess) H815 with unlocked bootloader (running rooted stock firmware + TWRP before). I did something stupid and bricked my G4 by doing a full wipe in TWRP before, without thinking to much. Apparently I managed to delete Recovery and the System partitions. At least I can no longer enter Recovery (even though I was not aware TWRP can delete itself before?)
Now, I am a bit lost. How can I unbrick my phone? I thought about flashing TWRP again through fastboot as a start. However, I don't seem to be able to enter the download mode anymore. I tried to boot the phone by pressing vol up + power, or vol down + power, and so on but nothing. I am stuck in the boot screen forever (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any advises?
On a second note: how would I flash stock (only) again through fastboot / TWRP? I don't seem to be able to find flashable zip/img files for either TWRP or fastboot, only the full image( https://forum.xda-developers.com/g4/development/h815-nougat-stock-t3659860 )
Thanks!

g960w stuck booting into recovery

Hi. I have a phone, not mine, given to me broken in this state, so not sure how it got into this state. I can only reboot it into recovery mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some things.
1. Volume up doesn't work. Apparently it didn't work when the phone was working.
I wonder if it's stuck in some position that forces it to go into this mode??
2. Tried to wipe cache and wipe data/factory reset, doesn't help.
3. Tried the "Apply update from ADB", and when I pick that, it tells me to run 'adb sideload <filename>'. So I tried to get stock firmware (G960WVL9FUJ1_G960W)YV9FUJ1_FMC.zip) and tried to sideload that from PC. Always gets stuck verifying the package (and 0% on PC adb).
Wasn't sure if I was supposed to do it with the zip or the files within the zip. Tried both and no luck
4. Tried to do it with SD card, it failed immediately (forget the error, could try to reproduce and tell you error if you think it will help).
5. Tried to use Odin. Cannot get Odin to recognize the phone at all.
I think drivers are installed properly (would adb devices work if the drivers weren't installed right??).
Not sure what else to try next.
Any suggestions would be welcome.
Thanks!

Categories

Resources