I have a Samsung Galaxy A13 5G (SM-A136U, MT6833 Dimensity 700, this is the 5G version). I also have a Windows 11, 64-bit computer. I have tried installing different MTK USB Vcom Preloader drivers and still, my phone is not able to run on the preloader. When I install the MTK drivers, they show up in the device manager with a yellow exclamation mark. It's said that the yellow exclamation marks are because the drivers are unsigned but that they should still work, but my drivers do not make my phone go on MTK preloader mode. I have tried disabling the driver's signature. Tried uninstalling and leaving the driver box blank and still nothing. I tried the different button combinations with the Android phone off and nothing. I even opened the back of the phone and tried the test points and still nothing (I attached an image of the test points that I followed). None of those things I tried to make my phone go to preloader mode. When I try all the things that I mentioned, what the phone does is reboot completely. Even if I only plug the Android phone when is off (without pressing any buttons in the phone) to the computer with the USB cable then the phone will start up completely, it starts up completely too when I press the combinations keys and when I do the test points. I tried with 2 (two) different computers and different USB cables. My questions: - What am I doing wrong in all these steps? - What have I not done? - Are the test points the correct ones? - Is my phone (Galaxy A13 5G) able to be forced to preloader mode without bricking it?

My Lenovo phone doesn't turn on. When I connect it to the PC, it vibrates. The PC sees it as a MediaTek PreLoader USB VCOM Port. On flashing, the SP Flash Tool gave me a Scatter storage type error. How to fix it? Flash the preloader? Before flashing, I formatted it, and the phone started flashing, but didn't turn on.

I am a Linux beginner, I just wanted to know how I properly download and use a "**Mediatek USB driver**". I am using a Linux Mint MATE, and I cannot turn on the USB debugging of that phone because it was locked via FRP. When I open it and go to the settings, I cannot activate the Developer options. I wanted to fix (or flash) phones for free, but I can't because I am not able to download the MTK USB driver, which is needed to help my PC communicate with the phone. It seems that all MTK USB drivers are perfectly fine for Windows, that's what I saw on the internet and tutorials on YouTube. The phone I currently reviving is; **Vivo y69** with a **MT6750** chipset which suffers from **FRP lock**. I have 2 working properly with "SP flash tools" with different versions, an official auth file, a scatter file, and a DA file. I just need an MTK USB driver. Every time I attempt to flash the phone, nothing happens. It doesn't show any lights it doesn't boot up and the progress bar on my PC does not show any changes. I hope you can help me because I have already searched the web and downloaded different files but nothing has worked so far. I'm desperate to fix the phone(s) to give them new value.

I have an Infinix Note 10 Pro. I would like to know if there is any way to fix the 0-byte partitions issue and storage being inaccessible. I saw this when I was trying to copy out the vbmeta and boot.bin files for rooting, and for some reason, I got that issue. Prior to the issue, I upgraded my firmware after a full wipe, and that's when the issue popped. It is also to note that I do not have access to my internal memory for some reason either. I am absolutely clueless about how these Mediatek devices work. I need advice since I have skimmed through multiple forums, and am unable to land on a decisive conclusion. In short, I do not want to ruin more than I already have. Thank you for your time.

I have a Huawei Mediapad T1 10 (model T1-A21w) that I want to root since it has a modified old EMUI; i'm trying to install a basic Android 4 or wharever. I've tried with MTKroot already and manually with CMD (im in Win10-11) and i always get stuck on the bootloader, as its locked and cant seem to find a way to unlock it. I've read around about some codes that are needed for the unlocking, but havent seem to find any, and in the tablet itself the bootloader stays stuck. any ideas?

The Realme 3 smartphone, developed by Oppo, comes in two variants: one with the Mediatek P60 chipset and another with the Mediatek P70 chipset. The global variant has the P60 chipset, while the Indian variant has the P70 chipset. The model numbers for these variants are RMX1821 for P60 and RMX1825 for P70. The question revolves around the compatibility of the ROM (Read-Only Memory) for two different chipsets. According to Realme's official website, the ROM version 'RMX1821EX_11.A.22' seems to be intended exclusively for the RMX1821 device with the P60 chipset. The concern is whether it is feasible to install this ROM on the RMX1825 device, which has the P70 chipset, and whether it will function correctly. Alternatively, it would be helpful to know if there is a separate ROM available specifically designed for the P70 chipset.

This is the log I got from adb logcat when the TV is at sleep mode:

03-05 00:50:40.242  9534  9647 I uicksetsdk.son: Starting a blocking GC Alloc
03-05 00:50:40.242  9534  9647 I uicksetsdk.son: Starting a blocking GC Alloc
03-05 00:50:40.271  9534  9647 I uicksetsdk.son: Alloc concurrent copying GC freed 19943(12MB) AllocSpace objects, 29(3092KB) LOS objects, 49% free, 2295KB/4590KB, paused 110us total 28.982ms
03-05 00:50:40.671  9986  9986 D LIBIWPRIV: Ethernet_WoPacket  ifc_set_Ethernet_listen_port
03-05 00:50:40.671  9986  9986 D MTK PowerHAL: ACFGGGGGGGGGGGGGGGGGGGGGGGGGGGGG : AM_BRDCST_MSG_PRE_POWER_OFF
03-05 00:50:41.178  2902  9975 I BatteryStatsService: In wakeup_callback: suspend aborted
03-05 00:50:41.179  2902  3203 D AlarmManager: Wakeup history#0 Wakeup alarmType=RTC_WAKEUP package=com.mediatek.agent wakeups=1 alarms=1 whenElapsed=0 when=2023-03-04 23:47:47 nowRTC=2023-03-04 23:47:47 workSource=null uid=1000 tag="*walarm*:mtk.intent.rtctimer.set.bgm"
03-05 00:50:41.179  2902  3203 D AlarmManager: Wakeup history#1 Wakeup alarmType=ELAPSED_WAKEUP package=android wakeups=3 alarms=3 whenElapsed=-21s956ms when=-21s956ms nowRTC=2023-03-04 23:48:10 workSource=null uid=1000 tag="*walarm*:DeviceIdleController.deep"
03-05 00:50:41.179  2902  3203 D AlarmManager: Wakeup history#2 Wakeup alarmType=ELAPSED_WAKEUP package=android wakeups=4 alarms=4 whenElapsed=0 when=0 nowRTC=2023-03-05 00:50:32 workSource=null uid=1000 tag="*walarm*:DeviceIdleController.deep"
03-05 00:50:41.179  2902  3203 D AlarmManager: Wakeup alarmType=ELAPSED_WAKEUP package=android wakeups=5 alarms=5 whenElapsed=0 when=0 nowRTC=2023-03-05 00:50:41 workSource=null uid=1000 tag="*walarm*:DeviceIdleController.deep"
03-05 00:50:41.180  2902  2980 W AlarmManager: Unrecognized alarm listener com.android.server.DeviceIdleController$4@2730dbf
03-05 00:50:41.225  9810  9990 W adbd    : timed out while waiting for FUNCTIONFS_BIND, trying again
03-05 00:50:41.225  9810  9990 I adbd    : UsbFfs: connection terminated: monitor thread finished
03-05 00:50:41.225  9810  9810 I adbd    : UsbFfs: already offline
03-05 00:50:41.225  9810  9810 I adbd    : destroying transport UsbFfs
03-05 00:50:41.225  9810  9810 I adbd    : UsbFfsConnection being destroyed
03-05 00:50:41.268  9810  9811 I adbd    : opening control endpoint /dev/usb-ffs/adb/ep0
03-05 00:50:41.268  9810  9811 I adbd    : UsbFfsConnection constructed
03-05 00:50:41.437  9993  9993 D MTK PowerHAL: for GCM case,update port info
03-05 00:50:41.437  9993  9993 D MTK PowerHAL: wopacket Sony behavior(for GCM case,update port info)
03-05 00:50:41.437  9993  9993 D MTK PowerHAL: enable WoPacket before power off
03-05 00:50:41.437  9993  9993 D MTK PowerHAL: XXXXXenter: AP 7668 a_nw_wlan_set_ip_and_port_to_driver
03-05 00:50:41.437  9993  9993 D MTK PowerHAL: XXXXX AP first clear all ethernet port
03-05 00:50:41.437  9993  9993 D LIBIWPRIV: Ethernet_WoPacket  ifc_clear_listen_port
03-05 00:50:41.438  9993  9993 D MTK PowerHAL: XXXXXXXXget valid Ex v4port 40918
03-05 00:50:41.438  9993  9993 D MTK PowerHAL: (WOWL)tcp v6 port2 = set_wow_tcp 0 8008,8009,1900,40918
03-05 00:50:41.438  9993  9993 D MTK PowerHAL: XXXXXethernet tcp port0 is 8008
03-05 00:50:41.438  9993  9993 D MTK PowerHAL: XXXXXethernet tcp port1 is 8009
03-05 00:50:41.438  9993  9993 D MTK PowerHAL: XXXXXethernet tcp port2 is 1900
03-05 00:50:41.438  9993  9993 D MTK PowerHAL: XXXXXethernet tcp port3 is 40918
03-05 00:50:42.273  9810  9991 W adbd    : timed out while waiting for FUNCTIONFS_BIND, trying again
03-05 00:50:42.273  9810  9991 I adbd    : UsbFfs: connection terminated: monitor thread finished
03-05 00:50:42.273  9810  9810 I adbd    : UsbFfs: already offline
03-05 00:50:42.273  9810  9810 I adbd    : destroying transport UsbFfs
03-05 00:50:42.273  9810  9810 I adbd    : UsbFfsConnection being destroyed
03-05 00:50:42.338  9810  9811 I adbd    : opening control endpoint /dev/usb-ffs/adb/ep0
03-05 00:50:42.339  9810  9811 I adbd    : UsbFfsConnection constructed
03-05 00:50:42.976  9993  9993 D LIBIWPRIV: Ethernet_WoPacket  ifc_set_Ethernet_listen_port
03-05 00:50:42.977  9993  9993 D MTK PowerHAL: (WOWL)udp port = set_wow_udp 0 5353
03-05 00:50:42.977  9993  9993 D MTK PowerHAL: XXXXXethernet udp port0 is 5353
03-05 00:50:43.341  9810  9994 W adbd    : timed out while waiting for FUNCTIONFS_BIND, trying again
03-05 00:50:43.341  9810  9994 I adbd    : UsbFfs: connection terminated: monitor thread finished
03-05 00:50:43.342  9810  9810 I adbd    : UsbFfs: already offline
03-05 00:50:43.342  9810  9810 I adbd    : destroying transport UsbFfs
03-05 00:50:43.342  9810  9810 I adbd    : UsbFfsConnection being destroyed
03-05 00:50:43.388  9810  9811 I adbd    : opening control endpoint /dev/usb-ffs/adb/ep0
03-05 00:50:43.389  9810  9811 I adbd    : UsbFfsConnection constructed
03-05 00:50:44.391  9810  9995 W adbd    : timed out while waiting for FUNCTIONFS_BIND, trying again
03-05 00:50:44.391  9810  9995 I adbd    : UsbFfs: connection terminated: monitor thread finished
03-05 00:50:44.391  9810  9810 I adbd    : UsbFfs: already offline
03-05 00:50:44.391  9810  9810 I adbd    : destroying transport UsbFfs
03-05 00:50:44.391  9810  9810 I adbd    : UsbFfsConnection being destroyed
03-05 00:50:44.458  9810  9811 I adbd    : opening control endpoint /dev/usb-ffs/adb/ep0
03-05 00:50:44.458  9810  9811 I adbd    : UsbFfsConnection constructed
03-05 00:50:44.515  9993  9993 D LIBIWPRIV: Ethernet_WoPacket  ifc_set_Ethernet_listen_port
03-05 00:50:44.515  9993  9993 D MTK PowerHAL: ACFGGGGGGGGGGGGGGGGGGGGGGGGGGGGG : AM_BRDCST_MSG_PRE_POWER_OFF

ADB is highly possible to be disconnected after the last line is printed. Android version: 10 Kernal version: 4.19.75 Because everytime this happens I see different PID for PowerHAL, I guess the TV is actaully being rebooted fequently? Does anyone know what could possibly be the reason, or how can I troubleshoot this issue?

I have a Xiaomi Redmi 9 phone, and in case of this device I use a custom ROM - crDroid. From time to time, I update the phone's firmware by downloading a corresponding firmware package from xiaomifirmwareupdater.com . When you look inside the firmware package, you can see the following content: Path = fw_lancelot_miui_LANCELOTEEAGlobal_V12.5.4.0.RJCEUXM_67a1671939_11.0.zip Type = zip Physical Size = 40808894 Date Time Attr Size Compressed Name ------------------- ----- ------------ ------------ ------------------------ 2022-02-28 13:40:44 D.... 0 0 META-INF 2022-02-28 13:40:40 ..... 280488 171992 preloader_raw.img 2022-02-28 13:40:40 ..... 282536 172052 preloader_ufs.img 2022-02-28 13:40:42 ..... 1 3 type.txt 2022-02-28 13:40:40 ..... 859 364 scatter.txt 2022-02-28 13:40:40 ..... 282536 172052 preloader_emmc.img 2022-02-28 13:40:40 ..... 59329408 35869684 md1img.img 2022-02-28 13:40:42 ..... 2505440 2166963 tee.img 2022-02-28 13:40:42 ..... 37984 7454 spmfw.img 2022-02-28 13:40:40 ..... 352816 144110 scp.img 2022-02-28 13:40:42 ..... 505616 483321 sspm.img 2022-02-28 13:40:24 ..... 1302976 522804 lk.img 2022-02-28 13:40:22 D.... 0 0 META-INF/com 2022-02-28 13:40:44 ..... 1634 1144 META-INF/CERT.RSA 2022-02-28 13:40:42 ..... 2217 999 META-INF/MANIFEST.MF 2022-02-28 13:40:42 ..... 2270 1091 META-INF/CERT.SF 2022-02-28 13:40:42 D.... 0 0 META-INF/com/android 2022-02-28 13:40:22 D.... 0 0 META-INF/com/google 2022-02-28 13:40:24 D.... 0 0 META-INF/com/google/android 2022-02-28 13:40:24 ..... 2340536 1090127 META-INF/com/google/android/update-binary 2022-02-28 13:40:44 ..... 3559 863 META-INF/com/google/android/updater-script 2022-02-28 13:40:22 ..... 316 220 META-INF/com/android/metadata 2022-02-28 13:40:42 ..... 1594 1077 META-INF/com/android/otacert ------------------- ----- ------------ ------------ ------------------------ 2022-02-28 13:40:44 67232786 40806320 18 files, 5 folders So I have the following questions: 1. Will the preloader be touched in any way when I flash this zip via TWRP/SHRP recovery? 2. What's the difference between preloader_raw.img , preloader_ufs.img and preloader_emmc.img ? 3. In the fastboot ROMs there's preloader_lancelot.bin which (according to the scatter.txt file) goes to: > partition_index: SYS0 > partition_name: preloader > file_name: preloader_lancelot.bin > is_download: true > type: SV5_BL_BIN > linear_start_addr: 0x0 > physical_start_addr: 0x0 > partition_size: 0x80000 > region: EMMC_BOOT1_BOOT2 > storage: HW_STORAGE_EMMC > boundary_check: true > is_reserved: false > operation_type: BOOTLOADERS > is_upgradable: true > empty_boot_needed: false > combo_partsize_check: false > reserve: 0x00 Is this preloader_lancelot.bin file related anyhow to preloader_raw.img, preloader_ufs.img or preloader_emmc.img ?

I downloaded mtkclient from the GitHub and followed the installation instructions but when I plug my phone in after running the command it never recognizes my phone. I've tried all different types of button combos and none seem to work. My phone is a Moto g 5g 2022 codenamed Austin and it is a mediatek dimensity 700.

I'm trying to update an app on a smartwatch, but whatever I try, I ran into errors. 1) adb install newversion.apk => [INSTALL_FAILED_VERSION_DOWNGRADE] 2) adb install -r -d newversion.apk => [INSTALL_FAILED_UPDATE_INCOMPATIBLE] 3) adb uninstall {packagename} => Failure [DELETE_FAILED_INTERNAL_ERROR] 4a) adb shell pm uninstall --user 0 {packagename} => success 4b) adb install newversion.apk => [INSTALL_FAILED_VERSION_DOWNGRADE] App is a launcher. OS has no launcher now. I still cannot install my new version. Checking for other users: pm list users -> users: UserInfo{0:Owner:13} running. So I'm the only user. Also tried the uninstall --user command with other user IDs like 0, 1, 10-15, 2000+, 300+, all nothing. I am not rooted. su does not work. It's an MT6739 chipset with Android 7.1.1 running. Nothing that I try lets me install my new app. Also not after factory reset.

When I walk through the system folders of my old Android phone to clean it, I could see that there was a **mtklog** folder containing an **audio_dump** folder, itself containing many files in the form **VMLog_%Y_%m_%d.vm** in the **Internal Storage** folder. As the name of the folder suggests that I have to make audio files, I tried to play them as a PCM RAW file, without success. Despite several searches on the file format, I did not find any information. Someone knows what these files are, if it is possible to read them to know what they are, or just if there is a risk to delete them because I would not like to make the system unstable by deleting them?

I currently have a phone named Symphony W17 (MT6572). I had flashed stock ROM using SP Flash Tool, but it's stuck in the boot loop. I tried clearing data and Dalvik cache from recovery but no luck. fastboot getvar all (bootloader) partition-size:userdata: 32000000 (bootloader) partition-type:userdata: ext4 (bootloader) partition-size:cache: 17800000 (bootloader) partition-type:cache: ext4 (bootloader) partition-size:system: 28a00000 (bootloader) partition-type:system: ext4 (bootloader) partition-size:expdb: a00000 (bootloader) partition-type:expdb: raw data (bootloader) partition-size:logo: 300000 (bootloader) partition-type:logo: raw data (bootloader) partition-size:misc: 80000 (bootloader) partition-type:misc: raw data (bootloader) partition-size:sec_ro: 40000 (bootloader) partition-type:sec_ro: raw data (bootloader) partition-size:recovery: 600000 (bootloader) partition-type:recovery: raw data (bootloader) partition-size:boot: 600000 (bootloader) partition-type:boot: raw data (bootloader) partition-size:uboot: 60000 (bootloader) partition-type:uboot: raw data (bootloader) partition-size:seccfg: 20000 (bootloader) partition-type:seccfg: raw data (bootloader) partition-size:protect_s: a00000 (bootloader) partition-type:protect_s: ext4 (bootloader) partition-size:protect_f: a00000 (bootloader) partition-type:protect_f: ext4 (bootloader) partition-size:nvram: 500000 (bootloader) partition-type:nvram: raw data (bootloader) partition-size:pro_info: 300000 (bootloader) partition-type:pro_info: raw data (bootloader) partition-size:ebr1: 80000 (bootloader) partition-type:ebr1: raw data (bootloader) partition-size:mbr: 80000 (bootloader) partition-type:mbr: raw data (bootloader) partition-size:preloader: c00000 (bootloader) partition-type:preloader: raw data (bootloader) kernel: lk (bootloader) product: UP11_ID_SYMPHONY_W17 (bootloader) version: 0.5 all: Done!! finished. total time: 0.078s ................................................................... Firmware I flashed - https://www.mediafire.com/file/8csalmwtcxf0nme/Symphony_W17_V01.5_UP11.zip SP flash tool version - 5.1516 Scatter - https://drive.google.com/file/d/12jhrdeM8bKjPU5Ej0KZVfEK4ZBg5DVzq/view?usp=sharing MT6572_Android_scatter.txt ############################################################################################################ # # General Setting # ############################################################################################################ - general: MTK_PLATFORM_CFG info: - config_version: V1.1.1 platform: MT6572 project: mtk_android storage: EMMC boot_channel: MSDC_0 block_size: 0x20000 ############################################################################################################ # # Layout Setting # ############################################################################################################ - partition_index: SYS0 partition_name: PRELOADER file_name: preloader.bin is_download: true type: SV5_BL_BIN linear_start_addr: 0x0 physical_start_addr: 0x0 partition_size: 0xC00000 region: EMMC_BOOT_1 storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: BOOTLOADER reserve: 0x00 - partition_index: SYS1 partition_name: MBR file_name: MBR.bin is_download: true type: NORMAL_ROM linear_start_addr: 0xC00000 physical_start_addr: 0x0 partition_size: 0x80000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS2 partition_name: EBR1 file_name: EBR1.bin is_download: true type: NORMAL_ROM linear_start_addr: 0xC80000 physical_start_addr: 0x0 partition_size: 0x80000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS3 partition_name: PRO_INFO file_name: NONE is_download: false type: NONE linear_start_addr: 0xD00000 physical_start_addr: 0x0 partition_size: 0x300000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: PROTECTED reserve: 0x00 - partition_index: SYS4 partition_name: NVRAM file_name: nvram.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x1000000 physical_start_addr: 0x0 partition_size: 0x500000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS5 partition_name: PROTECT_F file_name: protect_f.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x1500000 physical_start_addr: 0x0 partition_size: 0xA00000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS6 partition_name: PROTECT_S file_name: protect_s.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x1F00000 physical_start_addr: 0x0 partition_size: 0xA00000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS7 partition_name: SECCFG file_name: NONE is_download: false type: NONE linear_start_addr: 0x2900000 physical_start_addr: 0x0 partition_size: 0x20000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: INVISIBLE reserve: 0x00 - partition_index: SYS8 partition_name: UBOOT file_name: uboot.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x2920000 physical_start_addr: 0x0 partition_size: 0x60000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS9 partition_name: BOOTIMG file_name: bootimg.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x2980000 physical_start_addr: 0x0 partition_size: 0x600000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS10 partition_name: RECOVERY file_name: recovery.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x2F80000 physical_start_addr: 0x0 partition_size: 0x600000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS11 partition_name: SEC_RO file_name: secro.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x3580000 physical_start_addr: 0x0 partition_size: 0x40000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS12 partition_name: MISC file_name: misc.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x35C0000 physical_start_addr: 0x0 partition_size: 0x80000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS13 partition_name: LOGO file_name: logo.bin is_download: true type: NORMAL_ROM linear_start_addr: 0x3640000 physical_start_addr: 0x0 partition_size: 0x300000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS14 partition_name: EXPDB file_name: NONE is_download: false type: NONE linear_start_addr: 0x3940000 physical_start_addr: 0x0 partition_size: 0xA00000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: INVISIBLE reserve: 0x00 - partition_index: SYS15 partition_name: ANDROID file_name: system.bin is_download: true type: YAFFS_IMG linear_start_addr: 0x4340000 physical_start_addr: 0x0 partition_size: 0x28A00000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS16 partition_name: CACHE file_name: cache.bin is_download: true type: YAFFS_IMG linear_start_addr: 0x2CD40000 physical_start_addr: 0x0 partition_size: 0x17800000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS17 partition_name: USRDATA file_name: userdata.bin is_download: true type: YAFFS_IMG linear_start_addr: 0x44540000 physical_start_addr: 0x0 partition_size: 0x52C00000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS18 partition_name: FAT file_name: fat.bin is_download: true type: YAFFS_IMG linear_start_addr: 0x97140000 physical_start_addr: 0x0 partition_size: 0x4E5E0000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: true is_reserved: false operation_type: UPDATE reserve: 0x00 - partition_index: SYS19 partition_name: BMTPOOL file_name: NONE is_download: false type: NONE linear_start_addr: 0xFFFF00A8 physical_start_addr: 0x0 partition_size: 0x1500000 region: EMMC_USER storage: HW_STORAGE_EMMC boundary_check: false is_reserved: true operation_type: RESERVED reserve: 0x00

I extracted system.img of my rom using MTK extractor and edited a app then tried to repack but it failed. MTK extractor says system_unpack/file_contexts:No such directory found. Can anyone please tell me how to repack my system.img? I'm struck :/

When I enabled USB debugging in settings for Zopo ZP300+, an unrecognized device appeared in device manager: H9000+. Then I followed this: https://web.archive.org/web/20160918125953/http://www.zopomobileshop.com:80/zopo-rom/how-to-install-driver-for-zopo-mobile-phone-step-by-step-instruction/ . MT65XX Preloader replaced with "MediaTek PreLoader USB VCOM Port (COM3)", then it disappeared. I unplugged the USB, turned on the phone, and plugged it back in. No new drivers were installed. H9000+ is still unrecognized. Eclipse says: No compatible targets were found.

I got hold of this bare mobile phone board (didn’t come with the original cover, so no real way to confirm, only knowing it’s non-Western manufactured). Just needing to identify the model. I’m attaching a snapshot of the backside: Notice the K107TOZCG V8.7 (A9) & B20210625 M32 serial. Doing a search on these serial numbers didn’t turn up anything (these agencies, huh?). Only confirming that the hardware is meant to conform to Android 9, which the board came preinstalled with, & it is an ARM32 (confirmed by it *apparently* being equipped with 4GB — to be confirmed still); as I booted the board already. The approximate dimensions are 6.5mm x 11.5mm. EDIT: I actually meant, 6.5cm x 11.5cm — centimeters. I meant the BOARD. Stupid, glitchy brain enabling even stupider people. No need to rig the search results to show those dimensions of the chips. Like I’ll desolder these chips to be re-used. Just buy any embedded device & you’ll get just as good capacities.

So far, all the download addresses I can find are from third parties, does MediaTek officially offer downloads?

Bought what I thought was a Galaxy S20 Ultra, but not so. Will it work? My SIM works as far as phone and text but the internet doesn't work. WiFi is on and it's all fine. - IMEI says Apple iPad 10 Pro - Zankyo Maxpad 10 is what my Google account identifies - Build number: H_X25_S20U_20200523 - Custom build version: alps-mp-m0.mp1-V2.39_hy6580.weg.m_P96 Can I root this device? Some device info and specs