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!!!
Related
Tutorial: How to transfer files to/from our Moto G while in TWRP recovery
This tutorial have been tested in 7, 8, 8.1 and 10 Windows versions. It can work with other devices beside Moto G.
{
"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"
}
Sometimes we need to transfer files to our device while we are in recovery mode. When we forget to copy the zip we were going to flash, when we are installing a
GPE based ROM (we must format /data and erase all files), to transfer a backup... ect. In many cases we need this function.
The purpose of this tutorial is to make our PC succesfully recognize our Moto G as a storage device being in TWRP recovery.
Many users have reported that their devices are not being recognized.
Requirements:
-Have installe the last TWRP recovery version.
-Have installed ADB drivers in PC. You can try this ones Universal ADB Drivers or Motorola Mobile Drivers 64 bits
-USB data cable.
-PC runnig Windows 7, 8, 8.1 or 10 (can work with older versions).Steps: Sorry for spanish images, if you can provide me english captures would be great.
1) Boot into recovery mode and connect to PC with USB data cable.
2) Being completely sure your device is not being recognized, otherwise this tutorial will be totally useless to you.
3) Open Control Panel and click on Hardware and Sound
4) Go to Device Manager.
5) Look for 'Android Device' or 'Android Phone' or any related name, open the list, rigth-click on the device and click on 'Update driver software'.
6) Now click on the second option.
7) Now click on the option below:
8) Make sure 'ADB composite device' is there and click next.
9) Once this is donde, reboot your PC and it will be in capacity to recognize your device as a storage device while you are in TWRP recovery. We can freely transfer files.---------------------------------------------------
Last Update: 17-07-2015
Reserved
Thanks
Hello!
Does anyone know where is KCOL0 test point on motherboard to short with ground to enter mediatek meta mode?
MediaTek PreLoader USB VCOM driver is installed on system but device won't use it (tired pluging usb while holding vol+ or vol-). Can't enter download mode - error "Your Device is Corrupt. It can't be trusted and may not work properly."
Want to use this [GUIDE] How to 'unbrick' your Mediatek MT65xx (https://forum.xda-developers.com/showthread.php?t=1943442) but test point location on PCB is needed?
I tried modified micro usb cable (where pin 5(GND) and 4(NC) is straped) but it doesn't force device to be visible as PreLoader USB VCOM driver.
I attach pcb image, how can I unbrick this phone?
kyk1 said:
Hello!
Does anyone know where is KCOL0 test point on motherboard to short with ground to enter mediatek meta mode?
MediaTek PreLoader USB VCOM driver is installed on system but device won't use it (tired pluging usb while holding vol+ or vol-). Can't enter download mode - error "Your Device is Corrupt. It can't be trusted and may not work properly."
Want to use this [GUIDE] How to 'unbrick' your Mediatek MT65xx (https://forum.xda-developers.com/showthread.php?t=1943442) but test point location on PCB is needed?
I tried modified micro usb cable (where pin 5(GND) and 4(NC) is straped) but it doesn't force device to be visible as PreLoader USB VCOM driver.
I attach pcb image, how can I unbrick this phone?
Click to expand...
Click to collapse
Use this test point for enter to mediatek usb port and flash the firmware.
{
"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"
}
oscar25alex said:
Use this test point for enter to mediatek usb port and flash the firmware.
Click to expand...
Click to collapse
THats is not test point. that pin is for Buzzer
NECRO: Same question.
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.
If my upgrade fails, how do I boot from the slot that I installed the crap on the inactive slot from so the phone boots to the old version before the update?
I wanted to know and found the answers. I'll post here in case anyone wants to know cause I found nothing on these forums:
How to Check if Partition Slot A or Slot B is Currently Active?via https://krispitech.com/check-partition-slot-a-b/
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
This process will vary from device to device but usually involves holding certain button(s) down during the boot cycle.
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
{
"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"
}
In this instance, my device was currently using partition slot B.
How to Boot from One Active Partition Slot to Anothervia https://krispitech.com/change-active-partition-slot/
Boot the smartphone or tablet into Fastboot Mode
Connect the device to the PC with a USB cable
Open a Command Prompt, PowerShell, or Terminal and type out the following command. . .
fastboot --set-active=a
OR
fastboot --set-active=b and then press Enter on the keyboard
Make sure you get a successful OKAY response before restarting the device
So if my updates go pear-shaped, I should be okay. And if not, well, I'm not buying a OnePlus ever again cause I've had it with all the extra steps, headaches, and disappointments with this model.
Excellent guide, I like it.
Think check out TWRP too, I think ( not 100% ) but I think it can change slots for you too.
Hi everyone,
(Sorry if my english is bad) I recently saw Crosscall device must have a key to unlock their bootloader with fastboot (common way), and most of Crosscall devices are SnapDragon except the S4 Core, because there's an universal way for MTK to unlock the bootloader, without waiting time and key needed.
Requirements :
PC or Laptop (at least running Windows 10)
Crosscall Core S4
USB cable
/!\IMPORTANT/!\ : THIS PROCESS WILL WIPE ALL YOUR DATA, SO IF YOU HAVE IMPORTANT FILES BACKUP THEM BEFORE DOING THIS
Ready ? Go !
First : Install USBDK (depends on your processor arch download x64 for 64 bits and x86 for 32 bits)
Download MTKClient extract it and copy the extracted folder on your C: drive folder
Ok now open a Powershell session (if you're on W11) or a cmd session (if you're on W10)
{
"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"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked