Develop Bugs

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

[guide] flashing guide for pixel experience.

BASIC FLASHING GUIDE BY BHAGYESH RANE.
UNLOCKING PROCEDURE:
Unlock bootloader required. To do so, Go to Settings, About Phone, and tap of Build Number 7 times.
After that go back and go to Settings, System, Developer Options, and enable Oem Unlocking.
After that, Long press vol- and power to enter fastboot mode.
Enter these two commands for unlocking (read NOTE):
- fastboot flashing unlock
- fastboot flashing unlock_critical
NOTE: All your data will be lost, so keep your backup somewhere other than your Mi A3.
FLASHING PIXEL EXPERIENCE:
After you have unlocked the bootloader, download the Pixel.7z file and extract it in a folder.
After that, enter fastboot again by long pressing volume down + power.
Open Cmd-here file and enter these commands one by one. Wait for each command to execute successfully.
fastboot set_active a
fastboot erase boot
fastboot erase system
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot recovery.img.img
fastboot reboot -> After you enter this command, press volume up + button to boot into TWRP recovery.
After you enter TWRP Recovery,
- Go to Wipe, select Format Data and Type yes to format.
- Go back and go to Reboot, Select Recovery, select do not install.
- keep your phone connected during this, Again in the same Command Prompt, Type following commands:
1. adb push boot.img /sdcard
2. adb push recovery.zip /sdcard
3. adb push patch_no_fde10.zip /sdcard
- Now, go to install, select image, select boot.img, select boot and swipe to flash.
- then again go to install, select recovery.zip and swipe to flash
- then again go to install, select patch_no_fde10.zip, swipe to flash
- then Go to Wipe, select Format Data and Type yes to format.
- Go back and go to Reboot, Select system, select do not install.
now hopefully you will boot to the AMAZING PIXEL EXPERIENCE ROM.
link for files - https://mega.nz/#!V2QHwK6A!Wol5iP3zwPhVhrQ_7kkHk-3Htb3CkzV49TBFc0VO0F0

I'm stuck since I can't upload any files because adb doesn't detect any devices while on TWRP. I've disabled and re-enabled MTP and mounted every partition but still no luck. It's a brand new MI A3: I just switched on, unlocked bootloader and tried to install PE.
EDIT: I solved the problem. If someone has the same problem these are the steps I followed:
- disconnect the usb cable while on TWRP
- on TWRP go to Mount
- tap on Disable MTP
- go back to Reboot
- Reboot to Recovery
- Re-enable MTP and connect the usb cable

yossarian82it said:
I'm stuck since I can't upload any files because adb doesn't detect any devices while on TWRP. I've disabled and re-enabled MTP and mounted every partition but still no luck. It's a brand new MI A3: I just switched on, unlocked bootloader and tried to install PE.
EDIT: I solved the problem. If someone has the same problem these are the steps I followed:
- disconnect the usb cable while on TWRP
- on TWRP go to Mount
- tap on Disable MTP
- go back to Reboot
- Reboot to Recovery
- Re-enable MTP and connect the usb cable
Click to expand...
Click to collapse
Try to install from platform tools, not from minimal adb. Download Platform tools for windows and try again.

any others mirros???

Booted to pe rom but nothing seems to work. Everytime i try to click inside settings phone get stucks. And hangs and then reboot itself

Why do i need twrp if I'm gonna flash from flshboot

Arkapravoarka said:
Why do i need twrp if I'm gonna flash from flshboot
Click to expand...
Click to collapse
If you want to root. To flash magisk

Can flashing be done through fastboot mode only??
Becoz im facing issue like signal 4 error in twrp while flashing rom. So, can i flash pixel experince via fastboot mode?

BhagyeshGamer said:
BASIC FLASHING GUIDE BY BHAGYESH RANE.
UNLOCKING PROCEDURE:
Unlock bootloader required. To do so, Go to Settings, About Phone, and tap of Build Number 7 times.
After that go back and go to Settings, System, Developer Options, and enable Oem Unlocking.
After that, Long press vol- and power to enter fastboot mode.
Enter these two commands for unlocking (read NOTE):
- fastboot flashing unlock
- fastboot flashing unlock_critical
NOTE: All your data will be lost, so keep your backup somewhere other than your Mi A3.
FLASHING PIXEL EXPERIENCE:
After you have unlocked the bootloader, download the Pixel.7z file and extract it in a folder.
After that, enter fastboot again by long pressing volume down + power.
Open Cmd-here file and enter these commands one by one. Wait for each command to execute successfully.
fastboot set_active a
fastboot erase boot
fastboot erase system
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot recovery.img.img
fastboot reboot -> After you enter this command, press volume up + button to boot into TWRP recovery.
After you enter TWRP Recovery,
- Go to Wipe, select Format Data and Type yes to format.
- Go back and go to Reboot, Select Recovery, select do not install.
- keep your phone connected during this, Again in the same Command Prompt, Type following commands:
1. adb push boot.img /sdcard
2. adb push recovery.zip /sdcard
3. adb push patch_no_fde10.zip /sdcard
- Now, go to install, select image, select boot.img, select boot and swipe to flash.
- then again go to install, select recovery.zip and swipe to flash
- then again go to install, select patch_no_fde10.zip, swipe to flash
- then Go to Wipe, select Format Data and Type yes to format.
- Go back and go to Reboot, Select system, select do not install.
now hopefully you will boot to the AMAZING PIXEL EXPERIENCE ROM.
link for files - https://mega.nz/#!V2QHwK6A!Wol5iP3zwPhVhrQ_7kkHk-3Htb3CkzV49TBFc0VO0F0
Click to expand...
Click to collapse
i want to flash another custom kernel but after flashing pixel experience 4 custom rom my device is not rooted . and i m unable to fastboot the device . it shows qualcom flashdump mode. please help!!!

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

Problem Rebooting into Recovery

I am in the process of installing LineageOS 18.1 onto a Pixel 3 XL (I have done a Pixel 3 before with no issues). I am following the instructions from lineageos.org (https://wiki.lineageos.org/devices/crosshatch/install). It is specific instruction for the Pixel 3 XL. I have successfully completed the first number of steps but got stuck on the last one noted below:
Unlocking Bootloader (ALL COMPLETE)
enable OEM unlock
connect device to PC
adb reboot bootloader
fastboot devices
fastboot flashing unlock
reboot
re-enable usb debugging
Temporarily Booting a Custom Recovery
download a custom recover (lineage-18.1-20210803-recovery-crosshatch.img) - COMPLETE
connect device to PC - COMPLETE
adb reboot bootloader - COMPLETE
fastboot devices - COMPLETE
fastboot flash boot lineage-18.1-20210803-recover-crosshatch.img - COMPLETE (received msg that sending and writing to boot_a is okay)
reboot into recovery - INCOMPLETE
will not reboot into recovery, stays in fastboot mode
last line on fastboot mode screen says "no valid slot to boot" at one point it also said "error booting boot.img"
Any idea/suggestions on what would be the problem? I did try redoing the fastboot flash boot command an additional time and again it said it sent and wrote ok, however, still unable to reboot into recovery. I did not check the version of android on the phone before i flashed the lineage 18.1 recovery - could that be the problem? Might it be that the phone cannot run LIneage 18.1 because it is on android 10? (which I'm not sure how to check at this point). If this is the problem what would be the best solution - reflash with a lineage 17.1? Or, is there a way at this point to check and upgrade the android on the phone? Perhaps there is another problem entirely.

How To Guide [RMX3363] Install TWRP Android 12 recovery with LOS (no decryption issue)

My smartphone :
- RMX3363
- unlocked bootloader
- rooted with Magisk
- unofficial LOS 19.1 Android 12
- LOS recovery
What I did :
- download TWRP lz4 image : 3.6.2_12-0
- boot my phone into LOS recovery
- enter fastboot from LOS recovery menu (it's important, fastbootd is not fastboot)
- type CMD on PC : fastboot devices (check phone is detected)
- type CMD : fastboot getvar all (note active slot)
- type CMD : fastboot flash vendor_boot:recovery recovery.cpio.lz4
- type CMD : fastboot --set-active=x (a or b, different of your getvar result)
- type CMD : fastboot flash vendor_boot:recovery recovery.cpio.lz4
- reboot from LOS recovery menu on phone (it should reboot into TWRP recovery)
- wipe data and reboot
- proceed to new config of LOS 19.1 and GIVE ONLY A PIN FOR SECURITY
- reboot into recovery advanced power menu
- it's TWRP recovery and it just ask you your PIN code to decrypt data partition
- You enter it and enjoy
- After that, you can configure fingerprint
In the end, I wanted my RMX3363 with an AOSP ROM on Android 12 with a TWRP recovery. It's done, so I'm happy

Hi dev,
Can u flash rom via twrp now?
Means directly instead of sideload and does rec stays permanent?

Hi,
I've flashed some ZIPs directly from TWRP without sideload, it works perfectly. But never a rom because I 've installed my custom rom before TWRP and have no time for the moment to test it.

enonaw said:
Hi,
I've flashed some ZIPs directly from TWRP without sideload, it works perfectly. But never a rom because I 've installed my custom rom before TWRP and have no time for the moment to test it.
Click to expand...
Click to collapse
will u try flashing rom via it too?

xrpdigital said:
will u try flashing rom via it too?
Click to expand...
Click to collapse
No, I returned to LOS Recovery. I'm waiting for official TWRP.