Hello, I recently gotten the WCDMA Oppo Find 5 ( X909) And it came rooted. I flashed OmniRom and the prompt: "Touchscreen Firmware Update in Progress - Please Wait..." and remained for 2 hours. I figured the flashing process screwed up so i tried to enter bootloader and it didnt work. The OPPO logo just shows on the screen and will not boot into recovery or bootloader. Nor can I use fastboot or ADB. As far as i can tell there is no public recovery tool for the Find 5. Any suggestions?
If you could flash the ROM, then a recovery must be available.
Try to keep the power button more than 10 seconds.
This is then a soft reset.
After that you should be able to boot into recovery while holding volume minus an power at the same time.
Related
Hi,
Currently on 2.22.40.54 firmware, and successfully rooted it, but with a wrong root method. Therefore I lost camera access. Followed this guide , and flashed the 2.22.40.30 fastboot / recovery (which was successful), but the firmware flash didnt proceed, (had to restart), which resulted in not able to access fastboot / recovery. Tried flashing a new recovery tru xFSTK, but encountered the driver error and the ASUS Flash Tool gives me "serial number not found" error... I usually get the USB logo on start up, but sometimes I get a normal boot (which is nice).
Now, what is the best way to recover my recovery / fastboot? I'm willing to try everything except bringing it to a Service Center.
turn off devices and then pres power buton and vol. up y will see asus logo then pres only vol. up .. if it will works please write there
Hello All
I have problem with my Axon7 G. I had 8.00 version installed and tried to make a system write option with using a method mentioned in
Official (Beta) Android 8.0.0 V1.30B01 EU Version by NFound thread. I flashed zip mentioned in this tread -ZTE_A7_UniversalBootStack.
Then restart devices and...whats happened....soft (or hard) bricked my phone!!!!!
1. After restart i had a standard warning about unlocked bootloader with yellow fonts . After 5 sec yellow fonts changed into red and wrote my device is corrupt...
2 using vol down i can enter into bootloader mode - then i can choose option like fastboot, recovery,restart and power off.
- pressing recovery and restrt , phone restart and again boot into bootloader mode with option above (cant get into twrp or stock recovery mode)
-pressing fastboot i can enter into this mode .
3 . Use fastboot mode to flash recovery and boot ( fastboot flash recovery recovery.img and fastboot flash boot boot.img)
everything seems ok but...nothing changed , i cant boot into recovery -twrp or stock. Still go back after restart to bootloader menu
4. edl mode.....i can`t enter . Use vol + and vol- and power button then after 3 sec phone went black screen with red light upper left. Applications cant recognize phone in this mode...
somene can help me ???
I also get the warning but I can just continue with the boot. I can't access recovery however. Don't know hot to fix that.
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Antistar said:
Ok I did this. A7 is working )
I flashed this via fastboot flash file: A2017G_B06_NOUGAT_STOCK_FASTBOOT_EDL.zip then i went into twrp and everything works
Click to expand...
Click to collapse
did you manage to get the error message away?
I got it recently after installing LOS 15.1, but for me everything works fine .
I'm just afraid if the device randomly reboots at night my alarm won't go off in the morning since it's the device is shutting itself down after the 30 second warning.
If you've fixed this can you please detail me through the steps.
Hi all,
I unlocked bootloader and tried several custom ROMs. Then I came back to ColorOs 5 version A.15 by converting ozip to zip and flashing from TWRP (twrp-3.4.0-20200610-RMX1801.img) but then I made a great mistake. Without upgrading the stock ROM, I directly wiped 5 and flashed PixelExperience android 10. Upon reboot after a momentary "Realme" splash screen the phone turned off. It can't boot or bootloop, it can't boot to recovery or even bootloader. The only time the screen ever shows a momentary splash screen of Realme is when I long press and release power, thereafter pressing power+volume up. Otherwise it looks dead. The PC can't detect any adb or fastboot interface, only the interface as in attached picture is detected. I think it is EDL mode. At this pandemic situation it's very difficult to access service center, and even if I can, they'll probably flash Realme UI, thereby making bootloader unlock impossible. The most pathetic situation is that I have the ofp file version A.17 for EDL flashing but no virus-free and authentication-free tool to do so. After searching for hours I am asking for your help, if there is any.
EDIT: Nevermind, problem solved by trying different key combinations.
ood morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
Help me!
I run AOSP 7.3 and TWRP 3.4.0.0 (or 3.3.0.0, i don't remember)
I flashed orangefox 11 following this: https://techrrival.com/flash-recovery-adb-fastboot/
after last step: (Reboot the Device Type the following command to reboot your device “fastboot reboot”), phone stuck loading AOSP.
I then managed to re flash TWRP 3.4.0.0 trying to solve the problem but still stuck loading AOSP...
The problem is that when i run ADB commands it responds: error: no device\emulators found,
I managed to solve it the first time by killing adb and exiting usb device, then running again, but now this doesnt work anymore.
Please Help as this is my main and only phone...
By pressing and holding both volume buttons and power button for 15 seconds, After vibration signal released the power button, while keep holding both volume buttons I’ve successfully booted into TWRP recovery.
By choosing reboot to system it still stuck loading AOSP.
What should i do now?
I wiped cache and everything went back to normal.