Why I cannot install the version of android 10 on my dasaïta multimedia device which is in version android 9
As described below:
Current build number I have:
rk3368-userdebug 9 PQ2A.190305.00220190731.161345 test-keys
Current kernel version I have:
# 134Mon Jul 29 10:24:28 CST 2019
Current MCU version I have:
Aug 6 2019 11:00:20
Only the MCU that I was able to update to version 3.45_1
Thank you for your answers.
I took the time and saw that we had to buy the Mod Installer Pro 2 software from hal9k.
I will do it but pending confirmation of creation of the Paypal account
Can you share me apk file of ModInstallPro2 to upgrade my HU to android 10?
1. Someone have to pay $11,00 to buy the ModInstallPro2, you want free ? Noway
2. The Dev add your SN to the apk, only you can use the apk. You can install the apk if someone share, but can’t install the Recovery Mod !
I would kindly ask you for help. Would anyone like to go to their car, copy and upload somewhere where I would most easily download widget files. I assume the file is called HCTwidgetHA.apk or similar and is located in root/system/app. You can also rename the file extension from apk to zip.
I would try to change my Android 8 widgets look, to make them look the same as Dasaita (HA), Android 10. I like the look as the screenshots are made by Doky1988 in his post.
It would be good to add a background image as well. Probably in the wallpaper folder
Extract from the update IMG or otas?
This is impossible because when unpacked HA3_PX5_10.0_ota (20200706), it is obtained update.zip, and when that file is unpacked, a folder with the following content is obtained.
I can't do anything else. It's a similar thing with the img file.
# 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.