Database Users

Meizu MX2 TWRP recovery 3.0 through UART adapter

Warning! Update the phone to the latest Flyme 4 before to actualize the phones MMC partitions! I used 4.5.7.1a(CN) version with HK version of the phone.
Here are UART-TTL pins for MX2 HK and CN versions. You'll need UART adapter to flash custom recovery, 32 bit OS real or virtual, special drivers and application to flash system partitions. Drivers are 32bit only!
HK pins:
{
"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"
}
CN pins:
Putty settings (COM* - your port number):
Sample UART dmesg:
Older version of TWRP with wrong colors. Now everything is ok.
View attachment 3675318
I used 2 needles to connect to those pins and cp2102 UART adapter. Do not solder, you'll damage the pins.
So the sequence is as follows:
Power the phone off (better use battery connector to power off)
Connect adapter's RXD to the phone's TXD (RXD <---> TXD)
Connect adapter's TXD to the phone's RXD (TXD <---> RXD)
Connect GND to any metal cover of the phone or to its metal border.
Now connect battery back and power the phone on with power button and you'll see booting log in putty's terminal. To stop booting press Ctrl+C right after vibro and now you're in UART console.
Type "insdroid recovery" without quotes. The command turnes the phone into the recovery restoration mode. Remove your UART adapter now and connect the phone using usb wire. Install new driver. And flash recovery-uboot.img just throwing it with mouse on applications exe or use windows cmd "win32-smdk-dltool.exe recovery-uboot.img". Virtual machine with WinXP sometimes goes into BSOD - just manually power it off and then on and try to use smdk tool again.
I used manualy built and patched kernel for this recovery. So everything should work properly (mtp, adb, flashing backing up, restoring). System (kernel, ramdisk, recovery) partitions are visible and flashable.
kernel = mmcblk0p6
ramdisk = mmcblk0p7
recovery = mmcblk0p10
Links:
Drivers and SMDK application:
View attachment Windows32DriversAndCommandLineApp.zip
TWRP Recovery 3.0 (unzip before flash)
View attachment recovery-uboot.zip

goog job

Very good!!!

Fire hd 8 gen 7th bootloop

i have bootloop fire hd 8 and usb debugging off, how i can fix it?
Try:
1/ Factory reset in recovery => dont work.
2/I go recovery mode -> " apply update from ADB" ->
{
"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"
}
it not found my device because USB Debugging is off (?), so i cant sideload Firmware in https://forum.xda-developers.com/showpost.php?p=73033483&postcount=2, plz help

blackerghost said:
i have bootloop fire hd 8 and usb debugging off, how i can fix it?
Try:
1/ Factory reset in recovery => dont work.
2/I go recovery mode -> " apply update from ADB" ->
it not found my device because USB Debugging is off (?), so i cant sideload Firmware in https://forum.xda-developers.com/showpost.php?p=73033483&postcount=2, plz help
Click to expand...
Click to collapse
Enabled USB debugging is not required for sideloading in recovery mode. That would render the whole recovery functionality useless. I just checked it.
Make sure your USB port and cable are okay, maybe use another. Some hubs don't work with ADB.
Also check your drivers. Uninstall and reinstall the official or universal ADB driver. You should notice when the device is detected.
Attention: Only sideload the system version you're on or higher. Downgrading could brick your tablet.

lassemacchiato said:
Enabled USB debugging is not required for sideloading in recovery mode. That would render the whole recovery functionality useless. I just checked it.
Make sure your USB port and cable are okay, maybe use another. Some hubs don't work with ADB.
Also check your drivers. Uninstall and reinstall the official or universal ADB driver. You should notice when the device is detected.
Attention: Only sideload the system version you're on or higher. Downgrading could brick your tablet.
Click to expand...
Click to collapse
Tks u, my sideload is in process.
I change cable but it still not recognize my devices, so i update driver software and pick it from list driver.

Problem to recognize device with ADB

Hello all,
after hours of searching and tries, i need some help.
I have Android 8.1 on my Asus Zenfone Max pro M1 and i have a win 10 PC
I have followed this guide --> https://forum.xda-developers.com/as...obs-to-unlock-relock-bootloader-twrp-t3894847
I have unlocked my bootloader with the apk without any problem
My phone is not recognized by adb. I have install drivers (with the phone, try to install also from the guide), when i plug my phone on USB (with USB debugging active) is recognized by Windows in the device manager (without yellow flag)
{
"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 the command "adb devices" return nothing and like "fastboot devices" when i am on fastboot mode too
I have also tried another usb cable and another PC (on win 7)
I am stuck now, don't know what to do more.. Any clue?

Did you turn on USB debugging & OEM Unlock from developer settings?

debdeep98 said:
Did you turn on USB debugging & OEM Unlock from developer settings?
Click to expand...
Click to collapse
USB debugging is enable but OEM Unlock is not present from developer settings.

Yeah my bad no OEM unlock on asus.. Did you accept that allow pc thing with security key when first connecting to adb? If yes then revoke auth and try connecting. Also reinstall the drivers both asus and adb and try different cables and keep the device in mtp mode.

debdeep98 said:
Yeah my bad no OEM unlock on asus.. Did you accept that allow pc thing with security key when first connecting to adb? If yes then revoke auth and try connecting. Also reinstall the drivers both asus and adb and try different cables and keep the device in mtp mode.
Click to expand...
Click to collapse
I have tried MTP and other mode, different cable including the original one..... Still the same.
Can't revoke auth because adb never recognized my device

OP 6T fastboot device not detected

I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"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"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks

Same problem here. Please help.

Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.

Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.

Rockchip based Android 9 AI Box - ADB Connectivity

I recently acquired a Rockchip based Android 9 AI Box (RK3399 / PX6 based):
{
"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"
}
https://de.aliexpress.com/item/1005002449034431.html?spm=a2g0o.productlist.0.0.4dd831faAIkqhg
It connects to my car's headunit via. Apple Carplay (USB Type-A plug into the headunit's USB Type-A socket), and has 3 USB Type-A ports, two of which appear to be in USB host mode, while the third appears to be a Qualcomm 3.0 compatible fast-charge port.
I've been struggling to connect to it via. ADB over USB, to be able to grant restricted permissions to apps like Tasker, but, while I have made some headway, I have not yet managed to get into it via ADB.
Here's what I've done so far:
Installed Universal ADB driver for Windows
Enabled Developer Mode and USB Debugging
Set USB to default to "File Transfer"
Enabled "USB Connect to PC". This causes the link to the headunit to be dropped, but I'm still able to control the device via. Teamviewer. The device appears as an "Apple Mobile Device" when the USB Type-A plug is connected to a USB port on my Windows PC, with USB hardware vendor id 0x05AC.
Added 0x05AC to adb_usb.ini in .android\ found in my Windows user's home folder
Launched "adbd_zxw" on the device (by tapping the version number on the device's "Version" screen under "Settings")
Plugged in the device to the USB port (device shows up under Windows device manager), then ran adb kill-server, followed by adb devices
But no devices are listed.
What might I be missing?

Did you ever make any progress with adb over usb on this unit?
I have a similar carplay ai box (from a company KSPIV) and would like to adb into it to grant permissions, but cannot get the unit to show up when I do adb -devices.