Database Users

Need Help Booting In Recovery?

So I know that the oppo find 5 is fairly of a new device and not many people have it, yes there is support from a various users and groups (even the CM team has jumped on nightly builds on it) Anyway I want to write to you guys that in the venture of me trying to port a various "ROM" my oppo find 5 would get stuck on the splash screen Green Oppo Letters.I would try to use fastboot to get it back but I never got anywhere. The main problems were that I couldn't get into my previous ROM or the new one I flashed NOR could i get into recovery since I was stuck on the boot screen.
I found a really nice script on the oppo find 5 bricked thread and I modified it with a more "instructional process" to help us oppo find users get back into recovery after failed attempts of trying to get into a rom.
**Please note that for some odd reason the oppo find 5 takes like 1-2 minutes to boot into recovery after this process. I HAVE NO CLUE WHY.**
Also once you get into recovery in this case TWRP i would definately reccomend doing a back up > mounting SD card and transferring it to your PC.
{
"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"
}
This is only for Windows.
https://docs.google.com/file/d/0Byxlw5J4qbOvRVJDOFhkb2RtWkk/edit?usp=sharing
Extract then run batch file - Good luck! :fingers-crossed:

[Update] WW_4.21.40.352_20170623_7598 OTA for MM

Just got a notice that .352 is out, 33MB upgrade, I will need to reflash stock recovery to install it.
This is about "better wifi connection"

unroot, flash stock boot/recovery, download OTA, install OTA, flash TWRP ---> ok
flash Magisk 13.1 ---> failed, bootloop, I had to install 327 boot.
So if you install the update, please backup boot for me

So before update to 352 is better to wait for an updated toolkit?

Do you have the OTA file?

Magister54 said:
This is about "better wifi connection"
Click to expand...
Click to collapse
Security patch state is 1.May 2017 now
{
"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"
}

Like always I forgot to flash stock boot image beforehand, so I encountered error 7. Can anyone upload just the incremental update?

You can download the OTA here:
http://fota.asus.com/delta_package/...WW_rbr3qenrgGe-20170519-20170623-20170623.zip

[double post]

Weird been to asus and latest update shown for me ZE551ML is 327 . will it be different as I am in UK

I updated ok with system update app

I wonder if they will ever release an Nougat update....

Hi after i do this update WW_4.21.40.352_20170623_7598, my phone doesnt started anymore. just vibrates. so i had to downgrade it to use it again. After i put the phone working again it show me the same update and i thinking it was my mistake in anything i had done before, so i run it again, and again my phone brick one more time. this time i made the downgrade and contact imediatly the suport center and they said never heard about an error with the update. Its a litlle bit strange!!! Pls conctac asus suport center if anyone had the same problem, so they can fix it. I have a zenfone 2 deluxe edition

Help to recover head unit 8227 Demo

Hello everyone. Buy a unit with Haoling frimware 00009_V0001_20191128. To improve it a bit, install the YT9216B_00002_V004_2101012_HIFI_V3 frimware with SPFlashtool. The new frimware was working fine, but the drive seemed slower, so I decided to look for another lighter frimware without so many extras. My problem comes when when installing the new frimware I forgot to uncheck the Preload box and when I realized I got nervous and disconnected the cable, this caused the display of the unit to remain black and illuminated.
My first failure was not to backup the drive in its original state, and since then I have been testing frimwares without success, the most I have achieved is having a home screen with 3 boot options and an arrow moving in a loop, but at not having physical buttons I can not do anything.
I have had access to a unit equal to mine, to which I have been able to make a dump backup, but I am unable to load it, since the unit sounds as if it is constantly connecting and disconnecting and does not complete the loading of User.
The Test Point system does not seem to work for me, or that or something I am not doing well and I cannot find any video to see how it is done.
Ultimately, I don't know if my unit has a fix or if it will stay like a brick.
I hope you can help me, thanks
{
"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"
}

Hello. Has anyone happened to me? Is there no way to fix a failed Preload installation or to know what Frimware can I install to recover my drive?
Thank you

Disconnect the black connector from the radio for at least 30 min..next, it should boot directly to system..if it freezes at the Android logo, you have installed a incorrect firmware

Try this brand new guide

Getting g.co/ABH link(dm-verity corruption) after 2 years of stock 9.0 ROM

Hello everyone, hope all of you are in great health!
I had my Max Pro M2 for almost two years now (march 2019), running stock android 9 which came with the device with all its OEM updates installed,
but for the first time yesterday when I rebooted I got this first image which I immediately thought was ransomware,
after visiting the link it redirected me to a google page which says my OS could be compromised.
{
"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"
}
here's a list of things which were working prior to this warning
Installed GCam from trusted source on XDA -2019
Installed Youtube vanced from trusted source on XDA and subsequently installed vanced manager -2019,2020, 2021
Changed device display to aftermarket one -2020
changed microusb port at local repairs hop (he serviced it in front of me, so no rootkit or malware injected afaik) -2021
Can any of the above compromise the stock OS?
or does google like to force people to stop using older android versions?
I performed a full cache and partition wipe and revert to stock image and later did a systems check and got the second image as result.
Later I just booted into the phone after the stock factory image by pressing the power button during the warning screen and it boots up, but during device restart this warning still persists!
Currently running Android 9.0 with all the latest security patches from OEM,
should I finally flash a custom ROM and get rid of this warning? any other information required?
if so anything close to resurrection remix or better in terms of battery life and performance?

Flashing a custom ROM on a ZED AN817DK?

Hey fellas,
I've done some flashing on android before, but only on smartphones, instead of a car multimedia. My model is ZED AN817DK.
It looks like 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"
}
The launcher it came with is kinda disgusting, so I installed Nova Launcher instead.
Regardless, the system barely works, even on the stock settings / factory reset status.
Apps are crashing, changing the audio option in Waze takes a whole 2 minutes to even open up the menu for the option
(the app works but the input is unresponsive for 2 minutes until the menu appears).
I've tried contacting the shop I bought it in and they sent me a "firmware" update in the form of an APK file that will not launch in the device. I don't think I saw an option in it's administrator settings or anywhere else to update firmware via file (only check for firmware update - and it's always "up to date").
So I think I'll resort to flash a custom rom on this. I'm a bit worried since in the scenario where things go wrong I rely only on a pen hole style reset button which I don't fully trust to reset successfully if a custom rom is installed.
Is there a general flashing guide for these devices? How safe is it, as in what are the chances of completely bricking the device?
Are there general or common roms that work well on these devices?