Develop Bugs

CWM / TWMP in boot loop

Hi all,
After I've installed color os 2.1.1 from sniper-joe I cannot back into my recovery.
The phone can boot on OS and in fastboot but not into recovery.
My phone still boot loop as long I press volume down. When I release the button I'm in fastboot.
Model x9006
I try to remove SD and SIM : same
I've installed different TWMP and CWM : same
I've got some issue with 2.1.1 and want to go back to 2.0.8 but cannot

Mine has too after installing the official Lollipop, any help? Lollipop was buggy for me so I'd like to unbrick my Oppo.
So plug in phone AFTER booting into Fastboot mode (power+volume up) then open a command window by pushing shift and right clicking anywhere that the platform-tools folder is and then type fastboot devices and hit enter and then type fastboot oem unlock and hit enter and then fastboot flash recovery recovery.img or whatever the name of your rcovery is then just power+volume down and boot into the recovery. It helped me!

droidiam said:
Mine has too after installing the official Lollipop, any help? Lollipop was buggy for me so I'd like to unbrick my Oppo.
So plug in phone AFTER booting into Fastboot mode (power+volume up) then open a command window by pushing shift and right clicking anywhere that the platform-tools folder is and then type fastboot devices and hit enter and then type fastboot oem unlock and hit enter and then fastboot flash recovery recovery.img or whatever the name of your rcovery is then just power+volume down and boot into the recovery. It helped me!
Click to expand...
Click to collapse
You need one of these recoveries if you own a R63419 LCD (newer find 7 have this model) - For me the first was OK :
forum.xda-developers.com
/find-7/find7-development/x9076-r63419-lcd-recoveries-t3049886

NEED HELP !!! OPPO FIND 7 stuck on boot with logo only

Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT

kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck

roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076

Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers

Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance

ROOT Elephone S7 4gb on Windows 10x64 at last!

For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!

I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk

When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?

vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success

I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?

stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!

dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look

During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...

Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)

Unable to boot into TWRP

Hello everyone,
I really need help from you guys.
Yesterday I successfully flashed LineageOS 17 but unfortunately I forgot to flash Gapps using TWRP. I booted into system and then only few seconds afterwards I realized that I forgot to flash Gapps.
Then I tried to boot into recovery but the problem is I got forced to boot into stock recovery instead of the TWRP that I managed to flash in the first place. After that I tried to re flash the TWRP but then I got booted into the stock recovery everytime. Here is what I did and still failed to boot into TWRP:
1. adb reboot bootloader
FastBoot Mode
PRODUCT_NAME - ZS620KL
BOOTLOADER VERSION - WW_90.11.162.72
SERIAL NUMBER - J8AZB760J064ADX
SECURE BOOT - yes
ACTIVE SLOT - b
DEVICE STATE - unlocked
2. fastboot --set-active=a
3. fastboot reboot bootloader
4. fastboot flash boot boot.img
5. disconnected my usb cable
6. press volume keys to change the START to RECOVERY MODE
7. long press power key
8. press volume down and power key at the same time until Bootloader Warning Message appear
9. and then "POWERED BY android" appear
10. my phone is now booted into STOCK RECOVERY.
Please help me guys
I really need to install Gapps

How to stop Stock ROM overwriting the Custom Recovery?

I was trying to flash a Custom Recovery(TWRP) on my Friend's phone(Realme 3) It was officialy supported by TWRP and was listed on their website so I downloaded the Custom Recovery. Then I unlocked the bootloader of his phone but yes a strange thing happened there after it asked for pressing the volume button to be pressed it unlocked the bootloader but after that there was option "Select boot type"(Not sure what it said). It had three options Boot to Bootloader, Boot to recovery and last Normal boot and also there was a arrow on the bootloader option. And there were some instructions something like volume up for select and volume down to move. But I tried every button but the arrow was stuck on the bootloader option. So I connected it to my device and used the "fastboot reboot" command to restart the device after restarting at the realme logo it was saying "You are unlocked you cannot be trusted" But after it booted normally and the phone was Factory Reset. After this in the Developer options the OEM unlocking was grayed out saying Bootloader is unlocked. Ok so we were successful in unlocking the bootloader. After that I pasted the twrp img file in the platform tools directory and put the command adb reboot bootloader and after the device was in bootloader I used the command fastboot flash recovery name.img to flash the recovery. It said sending and then writing in my terminal after that I used the command fastboot reboot and the the key combinations(power+volume down) for the device which used to get into recovery for that phone but this time instead of going into recovery it was in the bootloader. So again I tried fastboot reboot command and this pressing the power+volume up but the phone booted normally so this time I tries adb reboot recovery but it booted into stock recovery so again I tried flashing the recovery and tried using fastboot reboot recovery but it didn't work. And yes I know that after flashing the custom recovery the phone should first boot into the recovery but as I said neither the key combinations nor the fastboot reboot recovery command so what can I do to prevent the system from overwriting? PS: Sorry for long paragraph...