Database Info

[DEV] USB-BRICK FIX - Restore USB function on your bricked Desire

Kubino was spot on - the misc overwrite was what caused the issue. If you modify a misc.img to include your CID and flash it back to mtd0, you will restore functionality. I can confirm that USB, BT, FM, recovery all work again on my Desire. The only thing we're not certain about is whether the ROM value in misc.img matters at all, but it doesn't appear to.
Stupid amounts of props go to IEF and adam235 at MoDaCo and kubino here. Thanks to all of you, so much.
MOD EDIT:
below is the post, as this was a combined effort, we don't need to link to modaco.....
As most of you know, people have been hard at work to fix the USB issues we've been seeing due to recovery setting us into USB debugmode.
After unsuccessful attempts to change the kernel commandline , eg. to:
board_bravo.disable_uart3=0
board_bravo.usb_h2w_sw=0
we've been successful in discovering (with the help of XDA-developers) that these switches are stored in the first NAND partition, mtd0, or 'misc'.
You must be rooted to try the following, it seems you can't write to mtd0 without root.
Do step 1 again if you have to.
Also, SD card functionality has to work. For this, do 'fastboot oem enableqxdm 0' in fastboot mode.
Steps involved:
1. Find out your CID. Go into fastboot mode, and do 'fastboot oem boot'.
The log will say something like the following:
CODE
#INFOTAG:Ramdisk OK
#INFOTAG:smi ok, size = 0
#INFOTAG:hwid 0x0
#INFOTAG:skuid 0x21F04
#INFOTAG:hero panel = 0x0
#INFOTAG:engineerid = 0x0
#INFOMCP dual-die
#INFOMCP dual-die
#INFOTAG:mono-die = 0x0
#INFODevice CID is not super CID
#INFOCID is HTC__E11
In this specific case, the CID is HTC__E11.
2. Get the following mtd0.img from the attached files below
Edit this image to the CID you found above with a hex editor.
Optionally, you can use this CID generator by stevebrush instead. Untested by me, but it should work properly.
//Edit: Updated link location for stevebrush. Thanks a ton for the generator!
3. Get flash_image from the attached files below
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)
4. Repeat step 3 a couple of times if it doesn't seem to work well.
5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
Credits:
-kubino @ XDA for providing us with the 'misc' information
-TheProfessor @ irc.freenode.net #modaco for being the first test subject + debugging
-adam235 @ irc.freenode.net #modaco for being a test subject as well + debugging
-SgtDavePwnage @ irc.freenode.net #modaco -> moral support + debugging
{
"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"
}
-DrMon @ irc.freenode.net #modaco -> being brave enough to test on his non-bricked device!

That's great news !
Good work to all !
Now that you know what the problem was, any chance to fix what was causing it in the recovery / flashing / rooting / anything process, to avoid bricking in the future (even if usb-bricking doesn't seem to be much of a problem anymore) ?

PascalMARTIN said:
That's great news !
Good work to all !
Now that you know what the problem was, any chance to fix what was causing it in the recovery / flashing / rooting / anything process, to avoid bricking in the future (even if usb-bricking doesn't seem to be much of a problem anymore) ?
Click to expand...
Click to collapse
at least we've learned how to enter debug mode on Desire

Next steps are to try and get recovery running from SD. IEF has made a ton of good strides there recently - hopefully we can get that rockin'.

People, if you have a different CID and need to hex edit the file, share here and say also for what CID is edited and for what ROM number.

I edited mine, since my CID was HTC__E11. Attached if somebody else would like to give it a try. This has ROM version 1.15.405.3 listed in it.

does this fix everything? i sent my desire for repar yeserday DOH! i was just wondering if this will fix the super battery drain that happens after a brick?

mardox said:
does this fix everything? i sent my desire for repar yeserday DOH! i was just wondering if this will fix the super battery drain that happens after a brick?
Click to expand...
Click to collapse
This fixes everything. Obviously we can't be 100% sure on battery life yet, but now that we're out of the debug mode, I can't imagine it would continue. I'll report back after a day.

This is brilliant chaps! I've backed up my misc fs already ;-) Even though I mush have flashed about 10 times without any issue.

If you've flashed and not run into issues, it might be worth checking out your misc.img in a hex editor anyway just to see what state it's in. It should start with your CID and contain some other strings, including a ROM version. Make sure it's still good.

the problem with the radio gets fixed too!

My misc.img, if anyone is interested.
misc.img

kubino99 said:
at least we've learned how to enter debug mode on Desire
Click to expand...
Click to collapse
Thats what haykuro asked me too. Is it possible to use jtag this way?

allla said:
Thats what haykuro asked me too. Is it possible to use jtag this way?
Click to expand...
Click to collapse
I think we can do lot of things via qualcomm diag devices but I don't know yet how If there is anyone who know how to use/connect the device to QPST/QXDM I'm sure we can do a lot with that.

adam235 has been playing with that on an XP machine.

kubino99 said:
I think we can do lot of things via qualcomm diag devices but I don't know yet how If there is anyone who know how to use/connect the device to QPST/QXDM I'm sure we can do a lot with that.
Click to expand...
Click to collapse
I also tried to get in contact with cmonex. She (and others) did the sspl and the hspl for the htc hd2...

I'm currently working on a serial cable interface for the HTC Desire.
Unfortunately, my electronics skills are 'teh sux0rs' , so it could take while

The Professor said:
adam235 has been playing with that on an XP machine.
Click to expand...
Click to collapse
Did he found something interesting ? it should be possible via QPST have full control over the device. Most interesting looks to me disabling NAND write protection.

ieftm said:
I'm currently working on a serial cable interface for the HTC Desire.
Unfortunately, my electronics skills are 'teh sux0rs' , so it could take while
Click to expand...
Click to collapse
it shouldn't be neccessary because when you enter debug mode (previous called as USB brick ;-) ) you get 3 serial devices :
Code:
Qualcomm HS-USB Modem 9002
Qualcomm HS-USB Diagnostics 9002 (COMx)
Qualcomm HS-USB NMEA 9002 (COMx)
but unfortunately I don't know about anyone who successfully connected the QPST tools.

kubino99 said:
it shouldn't be neccessary because when you enter debug mode (previous called as USB brick ;-) ) you get 3 serial devices :
Code:
Qualcomm HS-USB Modem 9002
Qualcomm HS-USB Diagnostics 9002 (COMx)
Qualcomm HS-USB NMEA 9002 (COMx)
but unfortunately I don't know about anyone who successfully connected the QPST tools.
Click to expand...
Click to collapse
sorry ... wrong post

help root

Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses

Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?

DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it

Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?

{
"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"
}

you have to run the root.bat file, you cannot dir the boot.img

I know I have to run the bat file but you asked me a screen of the folder

I have this message:

strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?

A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.

I am running win 8.1 as well

POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)

The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628

using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...

Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?

is your bootloader unlocked?

And I take it you've enabled Developer Options and USB Debugging?

After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.

maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK

ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!

[GUIDE]How to reboot to EDL from fastboot

Most Qualcomm-based Android PDAs support emergency download (EDL) mode allowing to unbrick device, unlock bootloader or modify protected device parameters. If ADB interface is accessible, "adb reboot edl" can be used to reboot to EDL mode.
Many bricked PDAs cannot be booted with full ADB support while FastBoot mode is accessible. But if bootloader is locked, there is no way to flash a partition or boot an image.
Some firmwares support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device.
Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
In the attached example, the mentioned string is located at offset 2685c.
I occasionally locked bootloader in my unlocked/rooted Xiaomi Redmi Note 3 Pro (Snapdragon) so it could boot to FastBoot or Diagnostic 900E modes. Tried to swich from 900E to 9008 with QPST but it reported unspecified error.
Analyzing aboot (emmc_appsboot.mbn), found that it supports "reboot-edl" so the only remaining thing was to find a way to send it to the bootloader.
With the attached fastboot.exe, successfully rebooted to EDL mode (9008) and re-flashed proper partition images.
Of course, patched version does not support "reboot-bootloader" command because it has been replaced by "reboot-edl".
There also is a detailed guide.

Works perfectly for me

It's working and for me also! Great work!
Many users can to reject the test point method.

s_wheel said:
It's working and for me also!
Click to expand...
Click to collapse
Please don't forget to vote to collect a proper statistics.

Thank you very much. You are a genius ;D

Thank you so much.
I was able to enter edl-mode but miflash gives error 0x80070008 max buffer sector is 256. What can i do?

Unfortunately, I'm not familiar with MiFlash so cannot help you. It is better to search other threads (here and on Xiaomi).

It doesn't work on xiaomi Mi5
What a pity, I saw for the moment the hope

tecno789 said:
It doesn't work on xiaomi Mi5
Click to expand...
Click to collapse
Will take a look at Mi 5 bootloader. Maybe there is a solution too.

emuzychenko said:
Will take a look at Mi 5 bootloader. Maybe there is a solution too.
Click to expand...
Click to collapse
Thanks too much.
I will appreciate it

Who has no success with this method, please upload somewhere (or post URL to an existing file) the image file of your "aboot" partition from FastBoot firmware, I will try to analyze them. For Redmi Note 3 Pro, image file is named "emmc_appsboot.mbn". If your FastBoot firmware contains a batch file that calls fastboot.exe, the appropriate image file name can be found there.

hi i can't get it work on xiaomi mi max
here is my aboot and emmc_appsboot.mbn
https://drive.google.com/open?id=0B2M9hEQgSgheZjFNeFR4U2tCb00

scarletnokarasu said:
can't get it work on xiaomi mi max
Click to expand...
Click to collapse
Your bootloader supports the following oem commands in FastBoot mode:
oem unlock
oem lock
oem edl
oem device-info
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem poweroff
oem select-display-panel
So "oem edl" should switch the phone to EDL mode (any fastboot.exe will support that).
Additionally, "oem poweroff" should power the phone off.

Checked Mi 4c, Mi 5 and Mi Max bootloaders - all of them support "oem edl" to switch to EDL mode. Looks like a kind of "protection" is implemented in RN3P bootloader that supports only "reboot-edl" command.

emmc_appsboot.mbn file from Fastboot firmware of 7.3.5.0 MAAMIDD Global Stable of Mi 5 - https://mega.nz/#!OUZ1QaoI!EIgsKTOn6PQZ236pluhHmVRQ5D9HCKWeNRfzqgFbkgM
This will support all of that mentioned by @emuzychenko
{
"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"
}
But it is mentioned that edl is blocked in 7.3.x.x firmware, so how to check whether edl is working or not ??
Thanks

anil4523 said:
https://mega.nz/#!OUZ1QaoI!EIgsKTOn6PQZ236pluhHmVRQ5D9HCKWeNRfzqgFbkgM
Click to expand...
Click to collapse
Sorry but cannot download the file - mega.nz asks me for creating an account.

you are a genius . I can now say bye bye to testpoint method

Awesome guide ...
Worked for me also....

Here is google drive link of boot.img & emmc_appsboot.mbn file of 7.3.5.0 MAAMIDD Global Stable for Mi5 - https://drive.google.com/open?id=0B0M_ponZ2Qxjd0lueS1fREtWRkE
Video - https://www.youtube.com/watch?v=4GOi61S-qUs

my miflash is giving error 0x80070008 Open Serial Port "\\.\COM8"

adb android not support on security

Hello, when im trying to change charge mode with command "fastboot oem off-mode-charge" i got message
Minimal ADB and Fastboot>fastboot oem off-mode-charge disable
...
FAILED (remote: not support on security)
finished. total time: 0.013s
Phone is unlocked (checked in fastboot getvar all unlocked: yes)
Phone is Alcatel 1x 2019 with android 6.0
Anyone can help me with it?

I also have the same problem with Hotwav (wheatek) H1 device. Unlocked the bootloader, but when trying to disable off-mode-charge I get the same error. Maybe there is some security setting that needs to be disabled first?

You both are speaking of FASTBOOT, and not of ADB as cited in this theads header.

Yes, but this is changed in fastboot, no? It should work, bu doesn't

I get the same error. And when I enter "adb devices" I get "1023456789ABCDEF unautorized". "fastboot devices" does not show anything

To fix this "unauthorized" error you
1. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" .
2. Restart ADB Server:
Then restarted adb server
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
It is now authorized!

Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
{
"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"
}

time2fly said:
Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
View attachment 5899259
Click to expand...
Click to collapse
First of all: The command fastboot is for fastboot. The command adb is for adb. When booting into fastboot then adb doesn't work.
To use it in your car as GPS tracker. With an additionally mobile connection? Or only pure GPS? Where is the phone? Somewhere outside the car on the top or well hidden inside the glove box?
Let's assume your phone is able to get a GPS signal. How to track it?

Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.

Looking at it, this seems intentional from manufacturer's side. They can enable it and you updated firmware if you pay a large sum of money. I've tried all the tricks and hacks mentioned in this forum – nothing helped. I don't know why these Chinese phones are so "secured". Trying to force businesses to pay when they discover that something rarely used by ordinary people but essential for some business project is disabled in the stock firmware?

Well, I don't consider "boot on charge" as rarely needed. Everyone who goes to bed at night and uses his phone as an alarmclock needs this. It's not understandable that this is not an option in the settings. And we're talking about Android 9 here!

0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.

time2fly said:
Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.
Click to expand...
Click to collapse
Try fastboot oem help to see the available options/features. Maybe there is another corresponding option that needs to be enabled.

alecxs said:
0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.
Click to expand...
Click to collapse
Yes, that was my backup strategy. But how do I root it? There is no TWRP version for the Soyes XS12, and I have no other knowledge of how to root phones. I can seem to send adb commands, but not fastboot.

either with WwR MTK v2.51 beta + SP Flash Tool or with mtkclient. your first goal: dump the para partition or the ROM/boot.img off the phone while in preloader mode. once you have it, you can modify it or root the phone.
mtk-su could also work.

There is nothing you can do even if you root the phone. The system partitions cannot be mounted in r/w mode.

don't need to mount system rw on systemless-root.

Doogee S68 Pro - Fastboot commands not working

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