I'm badly in need of help with my broken Android device. The XDA community is where I always found most information on those matters so I'm hoping someone can help me out. Some background on everything that went on today: I recently bought an Oppo A73 (non-5G version), I live in Romania so the best I can offer are these links for the store I got it from:
Source 1
Source 2
My grievance with the device is how it comes with an Android distribution called ColorOS which is filled with bloatware and things being shoved in my face. I was discussing this today and someone brought up adb explaining how I could use the command to remove unwanted system packages. I used it to get rid of some things I wanted nothing to do with, such as Rakuten and Heytap. For some mind boggling reason it appears those garbage packages were connected even to the core system: The device became unable to start up and entered a boot loop. This forced me to do a factory reset from recovery mode, causing me to lose all contacts and SMS messages as I didn't think to back them up first. After that ordeal I want my phone to use the default Android distribution: I'd rather have just Google involved with my phone over all those insane extra services, I'm not going back to this broken bloated OS.
Someone explained to me the basics of ADB and DSU Loader. After enabling Developer Mode I was able to enable the "OEM Unlock" feature then use the DSU Loader option to download a DSU package. My two options are "GSI ARM64" and "GSI+GMS ARM64" I used the later as advised. After the download completed I was prompted to restart my device in order to boot into the new image which I did from the notification. The phone however would only boot into ColorOS each time. I was told this must be because I need to use the commands fastboot oem unlock and fastboot reboot after adb reboot bootloader. The problem is that while adb recognizes my device, fastboot does not due to driver issues.
I spent hours trying to find some format in which fastboot would detect the device but everything seems to be broken, that's presently what I need your help with. I only use Linux these days, Manjaro KDE more precisely: I have a Windows 7 image and in an attempt to find a solution I downloaded Windows 10 as well: I installed Win 10 in VirtualBox and proceeded to install every update and driver I could find, following articles explaining how to get the driver for Oppo A73. None of them would work however: Even with all those drivers installed, the device manager sees an invalid USB device and neither adb or fastbook see it from the VM... same story with Win 7.
Download Oppo Latest MTK QCOM usb Driver 3.1.9 - ROM-Provider
Download Latest oppo usb driver for Window, here we Share Official oppo usb driver for mediatek and qcom based oppo phone
romprovider.com
Oppo A73 USB Driver Download | Device Drivers
Oppo A73 USB Drivers will help your Windows computer recognize your Android device. Then you can transfer files from computer to Android or even install the stock or custom ROM to your Android device.
oemdrivers.com
{
"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"
}
Can someone please tell me what OS and driver I need to get fastboot to recognize the device? If there's no way to, is there an alternative to fastboot to remove whatever's preventing the DSU image from booting and allowing me to flash it? Like I said I have access to adb on my main machine just not fastboot, anything adb can do should work.
I can't change my OS only for this task however. If I need Windows, is it not possible to do it from VirtualBox using the configuration in the screenshot above? If VBox is the issue, I will in an extreme scenario consider using a separate hard drive on my mother's computer to temporarily install Windows just to do this. I strongly hope that won't be necessary however, and this can be solved with a live tool or Linux distribution that has the necessary drivers.
Dynamic System Updates (DSU) | Platform | Android Developers
Dynamic System Updates (DSU) lets developers install a GSI side by side with the device's system image on a DSU-supported device that runs Android 10 or higher.
developer.android.com
Generic System Image releases | Platform | Android Developers
developer.android.com
I've attempted the tutorial described here, including the manual technique using adb commands the downloaded image and of course setting the feature flag as indicated. Even with adb shell am start-activity the custom image refuses to load: The notification says "dynamic system is ready, to start using it restart your device"... I click on "restart" inside this notification, the phone reboots, I see the oppo logo for a little then it goes black then I see it again, but after that I'm back in the original OS. What's breaking it and not letting the DSU load?!
AFAIK the Oppo A73 doesn't support Fastboot.
xXx yYy said:
AFAIK the Oppo A73 doesn't support Fastboot.
Click to expand...
Click to collapse
Is it possible for a device to not have it entirely? What are my options in that case? Can't ADB or another tool or app unlock the bootloader? Is there no safe way to simply get it to use stock Android with just the Google stuff on it by default? Was hoping I could get it to Android 12 too that way.
You flash device's Stock ROM by means of ADB Sideload method.
xXx yYy said:
You flash device's Stock ROM by means of ADB Sideload method.
Click to expand...
Click to collapse
Thanks, I'm looking into that method. The device's recovery mode doesn't have anything with the word "sideload" in it, but does offer the option to install from local storage. Would that do for a full ROM or am I in trouble again?
And where do I get the stock Android ROM from Google? I can only find custom ones, don't want to risk playing with that: I'd like the official Android 12, ideally the same image that would be downloaded by the builtin DSU loader as that seemed to know exactly what it needed.
Generic System Image releases | Platform | Android Developers
developer.android.com
Is this correct or should I look somewhere else?
Google dosn't offer a device's Stock ROM: Google only offers the vanilla Android OS ( AKA AOSP ) what is base for the Stock ROMs OEMs implement on their devices.
xXx yYy said:
Google dosn't offer a device's Stock ROM: Google only offers the vanilla Android OS ( AKA AOSP ) what is base for the Stock ROMs OEMs implement on their devices.
Click to expand...
Click to collapse
I see. So if I install the GSI, can I install Google Play separately to get the apps I need back? Should be all the Google stuff I need. I assume the GSI contains all the other components like call, SMS, camera, loader (homescreen), etc? Is there a risk of missing any base functionality?
I used Treble yesterday and it indicated a valid image I can use. Where do I actually download it from? Then what exactly am I meant to do with it, how do I sideload or install it from recovery and so on?
Sorry for all the questions: First time I'm actually having to flash a phone, very nervous about bricking.
Related
{
"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 every body, I made this guide for thosethose
who are new for Android ( coming from IOS or Windows...)
And for those who wants to know how to understand Guides through XDA.
SO LETS GET STARTED.
Main_Things
About Android
Android is a mobile OS (operating System) currently developed by Google
based on the Linux kernal and designed primarily
for touchscreen mobile devices such as smartphones and tablets.
Now we are going to talk about some main things
that you need in almost every guide:
ADB
A short of : Android Debugging Bridge
What's the ADB??
It's a command line utility which can control your device over USB from
a computer (copy file from and to the device ,install and uninstall apps and more..........).
How to enable it??
Go to Settings>About_Phone>Build _Number and press it 7 times.
Now go back to Settings>Developer_Options and
enable Android Debugging or USB Debugging .
ROOT
What's the ROOT??
Root is the process of allowing users to attain root access over various Android subsystem.
It's like running programs as administor in Windows, or running a command with sudo in Linux.
Notes
1_If you want to root your phone search for it in your device forums.
2_In some modding threads they say:
move it to system>apps and give it rw-r-r. It means to goto app's permissions
and check like in photo.
ROM(s) & MOD(s)
What is the deference between ROM(s) and MOD(s)
Rom(s):
Is a whole Android operating system ( firmware,apps......).
Mod(s):
Is a Modifications added to the software stored on the device.
Here you can learn everything you need before installing Rom(s)
Bootloader
ULB: Short of UnLocked Bootloader
LB: Short of Locked Bootloader
What is the Bootloader
Bootloader is a piece of code that runs before android loads up.
Bootloaders usually contain several ways to boot the OS kernal
and also contain commands for debugging and/or modifying
the kernal environment.
Note:
If you want to unlock your Bootloader you can
look for the way of unlocking n your device forums.
Recovery
What is the Recovery
It's the bootable partition that has the recovery console installed:silly:.
Or Simply it's where you can find tools to repair your phone
and install new ROMs.
The stock ROM recovery is very limited,
but the Custom recoveries offer much more,
they are coded to allow backup and restore function,
selective deletion of data So you don't have to
wipe everything and some of them have file explorer.
And here the most famous custom recoveries:
CWM: Short of ClockWork Mod.
TWRP: Short of TeamWin Recovery Project.
Something
In some ROMs thread's titles you could see these words
Official: it means the phone is supported from
the developer and it's Not port.
Unofficial: it means that it's port and it's not officially
supported from the developer.
Nightly: it means the rom have an every night update
for example: CM.
Shortcut
ADB: Android Debugging Bridge.
AOSP: Android Open Source Project.
CWM: ClockWork Mod.
TWRP: TeamWin Recovery Project.
CM: CyanogenMod.
ULB: UnLocked Bootloader.
LB: Locked Bootloader.
ICE: ICEcream sandwich 4.0
JB: Jelly Bean 4.1 , 4.2 , 4.3
KK: KiKat 4.4
LP: LolliPop 5.0 , 5.1
M: Marshmallow 6.0
Some shortcut that usually used in forums
OP: it means the "original poster" or "original post".
FCorFS: Short of : force close/stop
BL: Shot of BootLoop, it's when the phone stuck
at bootanimation because of something missed in the system.
Hardbrick: It's when your phone is dead
and you can't even boot,
So you must repair the hardware (motherboard....).
Softbrick: it's a software brick which
could be fixed with flashing stock ROM .
If I forgot anything just told me and please feel free to ask
Blackburn: the framework as from its name is the frame that the app work in it's the entire stack of stuff that makes up the OS.
Like siwtchs, buttons, colors, styles and. So on.
This'd the reason that the same app has different look in Samsung (for example) than Xperia .
n78 shadow said:
Shortcut
Softbrick: it's a software brick which
could be fixed with flashing stock ROM .
If I forgot anything just told me and please feel free to ask
Click to expand...
Click to collapse
Awesome work brother it was very useful.
Just one question what is the android framework???
And thank in advance.
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"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"
}
Can someone point me into the right direction?
Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?
{
"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"
}
Supports RMX2051 only
Note: The full kernel sources are available in the link below!
https://github.com/realme-kernel-opensource/realmeX50-kernel-source
Hello Fans of realme X50 5G,
Want to unlock your bootloader? Here is the step-by-step guide you have been waiting for - but please make sure to read the disclaimer too so you will know what to expect!
Keep in mind that the process of unlocking the bootloader will be referred to as in-depth test in the tutorial.
First, please read the “Disclaimer” carefully.
【Disclaimer】
1. After unlocking your phone ALL OF YOUR DATA WILL BE ERASED! Backup before you proceed.
2. In-depth test may have unforeseeable impacts on your phone.
3. Some functions may not operate properly because of third-party firmware, such as the photo-taking function of the camera. It may also cause device damage.
4. Personal and confidential information on phone may leak, and security may be compromised.
5. In-depth test may modify some of the system functions, and prevent you from updating the system version to enjoy the latest ColorOS.
Second, read the steps below for the in-depth test
Preparation:
realme X50 5G - with 60%+ battery
1 x USB Cable
1 x PC / MacBook
Step 1. Make sure you have backed up your data, unlocking your phone will erase all of your data.
Step 2. Make sure your system version is the official and latest one.
Step 3. Download and install the unlock tool apk on your phone.
View attachment DeepTesting_realme_X50.apk
Install it to apply for the bootloader unlock via the tool.
Step 4. Follow the detailed steps below to unlock the bootloader.
#1. enable developer options
Settings > About Phone > Build Number
tap the Build Number option 7 times
#2 unlock oemlock
Settings > other settings> developer mode
#3Open unlock tool.
#4. Click “Start applying”.
#5. Please read the disclaimer in detail, select the checkbox, and submit your application.
The application will be checked by our servers.
Within approximately 1 hour, the unlock tool apk will show the status of the unlock request - if it shows the unlocking is successful, please proceed to the following step.
Download and install the fastboot tool on your PC or MacBook (check this https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/), use a cable to connect phone and PC. In Fastboot mode use engineering command in the picture below to unlock
- Enter the command: adb reboot bootloader
- Press “Enter”on your keyboard
- Enter the command: fastboot flashing unlock
- Press “Enter”on your keyboard
https://forum.xda-developers.com/attachment.php?attachmentid=5137189&stc=1&d=1605631133/IMG]
FAQ
Q1: How to relock the bootloader?
#1. Download the unlock tool again to apply to exit the in-depth test.
[IMG]https://forum.xda-developers.com/attachment.php?attachmentid=5137187&stc=1&d=1605631133
Q2: Are there any risks after unlocking the bootloader?
Please be aware that realme cannot guarantee the full functionality, and will not be responsible, for any third-party unsigned custom ROM being flashed onto your device after the bootloader is unlocked. An unsigned third-party custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
A third-party custom ROM may not work properly on your device, and certain functions and services may cease to work. The performance and device data may also be affected, and may damage the device permanently. In the worst case, unlocking bootloader will cause physical injuries or material damage for ex. due to device overheating.
Q3: Will it affect future OTAs after unlocking?
Secure user data partition may also become inaccessible and you will not be able to get official software upgrades if you unlock the bootloader. Once re-locked the bootloader, users will receive official OTAs again.
Q4: Will it affect warranty?
Warranty will be fully applied to problems caused by realme 3 unlocking or flashing a custom ROM.
Q5: How to flash back the official ROM after installing a custom ROM?
Users need to go to a service center to flash the device FREE of charge.
Hello there, Thank you for your detailed explanation for unlocking bootloader for Realme X50 5G.
I used to download the deeptest apk from other website, but the result was not successful. The deeptest app said "my device is not supported."
My device model is RMX2025. And my quick question is this deeptest app will support RMX2025, won't it?
siamese007 said:
Hello there, Thank you for your detailed explanation for unlocking bootloader for Realme X50 5G.
I used to download the deeptest apk from other website, but the result was not successful. The deeptest app said "my device is not supported."
My device model is RMX2025. And my quick question is this deeptest app will support RMX2025, won't it?
Click to expand...
Click to collapse
This app supports RMX2051.
I received my realme x50 5g yesterday and it was already updated.
My model is RMX2144. It is the European version right?
Will the application work on this model? Thank you!!
totmakina said:
I received my realme x50 5g yesterday and it was already updated.
My model is RMX2144. It is the European version right?
Will the application work on this model? Thank you!!
Click to expand...
Click to collapse
I am not sure about the model RMX2144. May you try it and give us the feedback?
Hello! I have version RMX 2025, the application says that the phone is not supported
Craaazy said:
Hello! I have version RMX 2025, the application says that the phone is not supported
Click to expand...
Click to collapse
That's the sad story. Right now I found no deep testing app that supports RMX2025. So hopeless for this model. :crying::crying:
I have RMX2051 but when I install the deep testing apk, it opens and then the app closes immediately. Any idea why this happens?
Notes:
- OEM unlock is enabled
- All permissions for the app are enabled and I also restarted my phone but it still crashes
- USB debugging is enabled (though this isn't relevant for opening the app)
Could it be because I'm on Android 11 and this apk only supports Android 10?
If no solution.... what is the purpose of the deeptesting application? What would happen if I just skip this step and proceed to the fastboot tool step with the PC?
.gif of trying to open it: https://ibb.co/F3ym46B
wongx said:
I have RMX2051 but when I install the deep testing apk, it opens and then the app closes immediately. Any idea why this happens?
Notes:
- OEM unlock is enabled
- All permissions for the app are enabled and I also restarted my phone but it still crashes
- USB debugging is enabled (though this isn't relevant for opening the app)
Could it be because I'm on Android 11 and this apk only supports Android 10?
If no solution.... what is the purpose of the deeptesting application? What would happen if I just skip this step and proceed to the fastboot tool step with the PC?
.gif of trying to open it: https://ibb.co/F3ym46B
Click to expand...
Click to collapse
It is possible that your deeptesting app does not support Android 11 as you assumed. If you fail to run deeptesting and unlock your phone, your fastboot commands to manipulate the system will not work. That means you cannot skip deeptesting step for unlocking purpose. Another possiblility is Realme changed their mind and canceled unlocking all models of X50 5G. So there is no possible deeptesting app available for X50 5G again.
Anyways if you do intend to unlock your RMX2051, there are a couple methods that may work:
1. Downgrade your Android 11 to Android 10 by flashing tool to flash official firmware of Android 10. Or any possible ways to do this.
2. Try factory reset and install and run deeptesting app again.
3. Search and download deeptesting app for Android 11, if this may exist.
Hope one of this works.
Hi. So i have this issue. My brother has this phone (Doogee S68 Pro) and like a month ago almost every app in the system started to crash. Even 3rd party apps. I tried to update Android System WebView but it was already on latest version so i tried to opt-in to beta versions and no difference here. He also did make a factory reset through recovery mode and the problem still persists. So resetting the device to factory mode doesn't solve this issue. So i told him i could flash a custom ROM to see if that solves the problem. Only custom ROM for that device i could find was LineageOS 17.1. So i unlocked OEM, enabled USB debugging and adb commands work. Only issue is that when i access fastboot and type "fastboot devices" the command line doesn't output any text. It just send the command and nothing happens. Not even "waiting for any device". Only when i type some random stuff like "fastboot erjsifjes" then it says "waiting for any device". I also tried to install universal adb drivers, but the device shows up as Kedacom USB Device in device manager without any yellow exclamation mark or anything. It just shows up like it's properly installed and it works. But when i try to type any fastboot command other than "fastboot devices" it says "waiting for any device". I'm lost. I tried every possible way to make this work but no luck. What am i doing wrong? I disabled driver verification in Windows 10 (idk how it's named in english i'm using czech version but you know what i mean), so the drivers were installed properly. Is there any way how i can bypass the fastboot? I was looking in the recovery menu and there's a method to install "update" via ADB. So can i unlock bootloader this way? Help me please i don't know what to do now. I'm lost...
{
"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"
}
adb commands work in system but not in fastboot
To get Fastboot working install the Doogee USB Driver suitable to your phone:
Doogee S68 Pro USB Driver for Windows (Official Mobile Driver)
Download the official Doogee S68 Pro USB Driver for your Doogee Mobile. We also provide all other Doogee Mobile drivers for free.
gsmusbdriver.com
Uhhh. I don't wanna disappoint you but i have already tried to install them. Both of the drivers included there . That was actually the first thing i tried. When the official drivers didn't work i tried installing universal ADB drivers, still same issue. Anyway i decided to buy a new phone. This piece of s*** is outdated anyways. If the apps didn't crash i wouldn't tried to flash custom ROM which i can't anyways.
Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!
Update:
I got in touch with Doogee support and their technician. The problem was in trying to flash ROM in fastboot mode. They provide me SP Flash Tool which is used to flash ROMs, recovery, bootloader, etc. But the device needs to be turned off. This is kinda new for me, 'cause every time i was flashing ROMs or anything, i was doing it in fastboot mode with fastboot commands. The SP Flash Tool worked. Kinda. It allowed me to flash stock ROM successfully but it didn't solve the crashing apps issue. So yeah. I managed to progress further but still not the result i was hoping for. Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?
nero355 said:
Stupid question : Your phone is in Fastboot mode when you try the Fastboot commands right ?!
Are you using the latest version of the ADB and Fastboot Tools ?
You could try installing the following tool : https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows
Make sure you use a USB 2.0 port if possible!
If not then try a USB Hub between the phone and the PC or Laptop
Other things you could try :
- Use Windows 7 instead of anything newer.
- Use a Linux distro instead of Windows for the ADB and Fastboot part.
Good luck!
Click to expand...
Click to collapse
Yup.
- Device was in fastboot mode while typing fastboot commands. But not a single response from console.
- ADB and Fastboot was downloaded before creating this topic so i assume it was the latest version. Downloaded straight up from official Google page.
- Tried every single USB-C cable that i found, combined with every single USB port on my computer. (that took some time but need to be checked)
- To assure it was not my desktop PC what was potentially the problem, i also tried my brothers desktop PC with totally different HW components and operating system (his was W10, mine W11).
- I was thinking of creating dualboot system on my PC with W11 (primary) and W7 (secondary for this purpose) to try if that was the issue. (still open possibility)
- Same answer above
The drivers ( adb & fastboot ) you downloaded from Google are to be used with Google devices: you have to make use of the relevant drivers provided by DOGEE.
CaptainFedora said:
Update:
Still wanting to flash LineageOS 17.1 based on Android 10 in a hope that it'll solve my problem. When i tried flashing TWRP recovery straight up made for Doogee S68Pro with SP Flash Tool, it shows "Red State" message (see attachment) while booting the system (not able to enter recovery mode). Any ideas how to disable "verified boot"? I am able to access recovery through adb commands from system, however it enters the stock recovery menu, not TWRP which i did flashed. What am I doing wrong?
Click to expand...
Click to collapse
From : https://www.getdroidtips.com/lineage-os-17-1-doogee-s68-pro-android-10/
This should be the way : https://www.getdroidtips.com/twrp-recovery-doogee-s68-pro/
So no VBmeta.img needed it seems ?!
Yes! I was using the method mentioned in the first link. Never found that second link you provided. It looks very promising! I'm gonna try it in this week and post report. Man, that would be awesome.
You have to modify the usb driver .inf file. Add this rows to end of [Google.NTamd64] section:
;Doogee S68 Pro
%SingleBootLoaderInterface% = USB_Install, USB\VID_0E8D&PID_201C
%SingleAdbInterface% = USB_Install, USB\VID_0E8D&PID_201D&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0E8D&PID_2006&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
Need a computer restart (shif+Restart in start menu) and have to switch off the signed drivers recommandation.
Hi ksanci ,and thank you very much it is work for me
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
{
"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"
}
because the driver is not installed for recovery I think:
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Costik said:
Hi all,
I am trying to convert my T-Mobile IN2017 OnePlus 8 to have a global rom. I am currently on 10.5.7.IN55CB and I am following this tutorial here. My bootloader is unlocked (by using the official binaries I got emailed from OnePlus). My PC has driver signature verification off and is in test mode. It seems that my installer is stuck at this point:
View attachment 5499393
because the driver is not installed for recovery I think:
View attachment 5499395
I have tried installing/reinstalling the OnePlus drivers to no avail. The installer runs perfectly fine while in fastboot mode, but does not work once rebooted into recovery. If someone can send me the driver or show what I am doing wrong, it would be much appreciated!
Click to expand...
Click to collapse
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
SilverZero said:
See my post here:
https://forum.xda-developers.com/t/...with-bootloader-re-lock.4345305/post-86144965
You're having the same issue I had. You need to install the fastboot drivers while it's connected in that state from your screenshot. Grab the drivers from Foxy Drew's post (linked in mine above), run the installer until it hangs, then update the drivers on the PC. When I did this the flash-all installer immediately kicked back into gear and finished the process.
The problem, I, think, is that you need to install adb drivers and fastboot drivers while the phone is in 3 different boot modes: normal, fastboot/recovery, and bootloader. So you need to get the phone to be recognized in all of those states so you can apply the drivers to the device the PC "sees" when it's connected in each of those states. Every boot mode basically presents itself as a different device to the PC, and that 3rd fastboot mode is hidden until you get to the spot you show in your screenshot.
Hope that works for you.
Click to expand...
Click to collapse
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Costik said:
Thank you so much for your help! I was actually able to get it to work by doing something really similar. I'll post what I did just in case someone runs into this exact issue:
1) I made sure that I had all the drivers installed
2) I did the entire process over again until I got to that part where my device was no longer recognized
3) I went into device manager > IN2017 > update driver > drivers installed on this pc > chose from a list > Android phone > Android bootloader interface
I did this all while the converter was running and my phone was plugged into my pc. Once I did this, the program continued and I was able to finish the install.
Click to expand...
Click to collapse
Yep, I think that's exactly what I did. I can't remember which fastboot drivers I updated to bit I'll bet they're both the same, and that's the point in the process where I updated drivers as well.
Cheers!