If you are from Russia, it's even better. Check this guide on this page https://4pda.ru/forum/index.php?showtopic=928321&view=findpost&p=98052577, I have done it with Dasaita PX6 mtce---Android 10.hello. I apologize for my English - I'm from Russia. I write through a translator. On Android 9, ROOT was obtained a long time ago. Work on getting root on Android 10 is underway?? Where else can I see it?
If you are from Russia, it's even better. Check this guide on this page https://4pda.ru/forum/index.php?showtopic=928321&view=findpost&p=98052577, I have done it with Dasaita PX6 mtce---Android 10.
Just go to that page and use Google translator, you won't be able to download any files from there, it is quite simple actually to root it, I have been learning stuff for some time from this forum, in the beginning I used the patched boot image, but later I found out that it wasn't necessary since when magisk gets installed, it patches the stock boot image. I tested it like 5 or 6 times with success. I went back to Android 9 because I noticed one or two little things that I did not liked about it, one of them was that I couldn't modify the build. Prop file, and the other I noticed that they made small changes to the equalizer sound app, I like it a lot better the one from Android 9, I tried to make it work with android 10, but it was not possible. People that are beginners are going to have problems doing it, I ran into one or two complications, but I have to be smart and figure things up. In the guide it tells you to use that app to get it connected to the pc through adb wifi, and then use the batch tool that you need to download, it is even available from this place, I think it is called [How-To] Root- PX6 HU with Android 9.0! it's on the first page, once you go through that process you end up with supersu app installed, and that's when you have to install magisk, it will patch the stock boot image, then later delete supersu app. Very simple, you do it at your own risk that you could end up bricking your head unit, (I am not responsible for that) but there are ways available to recover the head unit....... (wait a minute you are the same guy who made that post about rooting Android 9 using the joying Sofia 3gr Extra Tools, ja, ja,... You should be teaching me how to do this) https://forum.xda-developers.com/an...neral/how-to-root-px5-hu-android-9-0-t3940327.......... @jamal2367, I did not use your exact procedure, I kinda did it mostly manually using the cmd commands from my pc to simple root it.Can you please explain to me how this works?
The problem is that translating Russian is unfortunately very bad.
How was the boot.img patched? Since it is only for PX6.
And how can I download files from 4pda ?
Can you pls translate the Instruction ?
I have a account and i get the files but only for PX6.
You need the Android 10 recovery to install this.
You can find it here:
This link to the Android 10 images doesn't work. Is there another location to download a PX5 Android 10 img so that I can upgrade?
here is the instruction. there are three ways. 1. through a memory card and usb. 2. via cable usb a-a (the easiest one seems to me, you need a laptop or PC). 3. ModPak - for money
# begin common build properties # autogenerated by build/make/tools/buildinfo_common.sh ro.system.build.date=Mon Jul 6 21:04:48 CST 2020 ro.system.build.date.utc=1594040688 ro.system.build.fingerprint=rockchip/rk3368/rk3368:10/QQ2A.200305.004.A1/hct07062104:userdebug/test-keys ro.system.build.id=QQ2A.200305.004.A1 ro.system.build.tags=test-keys ro.system.build.type=userdebug ro.system.build.version.incremental=eng.hct.20200706.211222 ro.system.build.version.release=10 ro.system.build.version.sdk=29 ro.product.system.brand=rockchip ro.product.system.device=rk3368 ro.product.system.manufacturer=rockchip ro.product.system.model=PX5 ro.product.system.name=rk3368 # end common build properties # begin build properties # autogenerated by buildinfo.sh ro.build.id=QQ2A.200305.004.A1 ro.build.display.id=rk3368-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200706.211222 test-keys ro.build.version.incremental=eng.hct.20200706.211222 ro.build.version.sdk=29 ro.build.version.preview_sdk=0 ro.build.version.preview_sdk_fingerprint=REL ro.build.version.codename=REL ro.build.version.all_codenames=REL ro.build.version.release=10 ro.build.version.security_patch=2020-05-05 ro.build.version.base_os= ro.build.version.min_supported_target_sdk=23 ro.build.date=Mon Jul 6 21:04:48 CST 2020 ro.build.date.utc=1594040688 ro.build.type=userdebug ro.build.user=hct ro.build.host=r930 ro.build.tags=test-keys ro.build.flavor=rk3368-userdebug # ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete, # use ro.product.cpu.abilist instead. ro.product.cpu.abi=arm64-v8a ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi ro.product.cpu.abilist32=armeabi-v7a,armeabi ro.product.cpu.abilist64=arm64-v8a ro.wifi.channels= # ro.build.product is obsolete; use ro.product.device ro.build.product=rk3368 # Do not try to parse description or thumbprint ro.build.description=rk3368-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200706.211222 test-keys # end build properties # # from device/rockchip/rk3368/system.prop # # # system.prop # ro.ril.ecclist=112,911 rild.libpath=/vendor/lib64/libril-rk29-dataonly.so rild.libargs=-d /dev/ttyACM0 vendor.rild.libpath=/vendor/lib64/libril-rk29-dataonly.so vendor.rild.libargs=-d /dev/ttyACM0 # end of device/rockchip/rk3368/system.prop # # ADDITIONAL_BUILD_PROPERTIES # ro.bionic.ld.warning=1 ro.treble.enabled=true persist.debug.dalvik.vm.core_platform_api_policy=just-warn dalvik.vm.lockprof.threshold=500 net.bt.name=Android
I think you mean, not all units have a GPS sdcard slot. Often these are hidden and internal to the unit.
The factory methods do work where the unit has an SDcard, id 0/1 USB or use OTG.
Furthermore, some units have OTG without mods by simply connecting a USB-USB. In fact it will work for any rockchip headunit, but must use the correct manufacturer type .IMG.
E.g. all MTCD/E use HCT type or MTCD/E images from HA, GS,
Also with GPS slot it doesn't work with some of them and the method with USB A to A doesn't work either, there is only the OTG variant which not everybody has and you have to remove the radio from the car first.
The Mod Installer Pro from hal9k_ is better suited and less complicated.