Android 10.0 version from SYCH/M.I.C for PX5 Head Units.
Day/Night Theme is included!
Enjoy
Download:
Fast --> Download
build.prop:
Code:
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Sat Aug 8 14:39:50 CST 2020
ro.system.build.date.utc=1596868790
ro.system.build.fingerprint=rockchip/rk3368/rk3368:10/QQ2A.200305.004.A1/hct208081439: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.hct2.20200808.144323
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.hct2.20200808.144323 test-keys
ro.build.version.incremental=eng.hct2.20200808.144323
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=Sat Aug 8 14:39:50 CST 2020
ro.build.date.utc=1596868790
ro.build.type=userdebug
ro.build.user=hct2
ro.build.host=r940
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.hct2.20200808.144323 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
This launcher looks like agama car launcher, is that the stock system launcher ?
alt.d4c said:
This launcher looks like agama car launcher, is that the stock system launcher ?
Click to expand...
Click to collapse
Yes, it's the stock launcher with Day/Night Theme
I installed it, tried it, it works well!
Here are some screenshots.
launcher
hi guys does anyone know where i can download this launcher?
Update
HI ,Can this be installed on my unit ? its ""DVD NAVI BT ANDROID 10.0 4/64GB 8CORE DAB+ VAUXHALL OPEL CASCADA ASTRA J RV5754"
Its PX5 Android 10.00
MCU Version MTCE MX2.V3 53.1
Its from Witson ,
If not any chance someone could please extract the launcher for me ? thanks
pawex said:
HI ,Can this be installed on my unit ? its ""DVD NAVI BT ANDROID 10.0 4/64GB 8CORE DAB+ VAUXHALL OPEL CASCADA ASTRA J RV5754"
Its PX5 Android 10.00
MCU Version MTCE MX2.V3 53.1
Its from Witson ,
If not any chance someone could please extract the launcher for me ? thanks
Click to expand...
Click to collapse
Yes you can install it without any problems
jamal2367 said:
Yes you can install it without any problems
Click to expand...
Click to collapse
Hi Jamal thanks for your reply What is the diffrence between that firmware and this one "HCT4_PX5_10.0_ota(2020/06/03) MX/WITSON" thats actually how mine looks like but HCT 2 this firmware here looks way way better and i would love to have it so you saying it can be installed ? is it standard process ? put in on sd and then just update ?
pawex said:
Hi Jamal thanks for your reply What is the diffrence between that firmware and this one "HCT4_PX5_10.0_ota(2020/06/03) MX/WITSON" thats actually how mine looks like but HCT 2 this firmware here looks way way better and i would love to have it so you saying it can be installed ? is it standard process ? put in on sd and then just update ?
Click to expand...
Click to collapse
The only difference is the launcher, media player, radio and the video app, otherwise the rest would be identical.
Just put the update.zip on a USB stick and start the update.
Thanks a lot for your help it does work perfectly fine and it looks way way better too
Do you know if it's possible to update from android 9.0 to android 10 on same unit as mine ? Asking for my friend thanks in advance
nice looking launcher
New HCT2 Update!
Updated OP!
jamal2367 said:
New HCT2 Update!
Updated OP!
Click to expand...
Click to collapse
thanks for the work you've done. but there is a question !! The YandexNavigator program does not work well on the radio, there is a large error when GPS is working. I read that somehow it is possible to turn on Galileo satellites (Europe), Chinese satellites in the chip, and somehow speed up the work of GPS, since the firmware profile costs a Tablet, but somehow you need to make a head unit or a navigator !!! Not optimized memory, interface. All this is done in the Hulk and Malay mods, but it's all paid. I would like to improve at least some functions. I have translated some of the forums in English on this topic, but I do not understand either in Linux or in Android.
Hey.Not working the bluetooth app for out voice,only in.OK Google working,everithing seems ok.
after how put magic does not want to be sewn. error 7
AndreySanich said:
after how put magic does not want to be sewn. error 7
Click to expand...
Click to collapse
Hi,
For PX5 and PX6, maybe for PX30.
https://forum.xda-developers.com/an...development/root-android-10-px6-mtce-t4134041
Buona fortuna
jamal2367 said:
The only difference is the launcher, media player, radio and the video app, otherwise the rest would be identical.
Just put the update.zip on a USB stick and start the update.
Click to expand...
Click to collapse
Hi, mine is Android 9 currently. Can I install it just put in USB to update?
Hi, does anybody help, how is to manage a new launcher (rename buttons, set another app. and etc.) and to chengeover to the dark theme?
Can someone extract the Launcher from this Rom and make it available as apk?
wanze2001 said:
Can someone extract the Launcher from this Rom and make it available as apk?
Click to expand...
Click to collapse
Hey, I want it too.Can anyone extract?
I've extracted the rom but I can't find it.
Related
P6200XXLB1:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HTJ85B
ro.build.display.id=HTJ85B
ro.build.version.incremental=XXLB1
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Thu Feb 16 19:50:59 KST 2012
ro.build.date.utc=1329389459
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL174
ro.build.tags=release-keys
ro.product.model=GT-P6200
ro.product.brand=samsung
ro.product.name=GT-P6200
ro.product.device=GT-P6200
ro.product.board=GT-P6200
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P6200
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P6200-user 3.2 HTJ85B XXLB1 release-keys
ro.build.fingerprint=samsung/GT-P6200/GT-P6200:3.2/HTJ85B/XXLB1:user/release-keys
ro.build.characteristics=tablet
ro.flash.resolution=1080
# Samsung Specific Properties
ro.build.PDA=P6200XXLB1
ro.build.hidden_ver=P6200XXLB1
ro.build.changelist=629097
# end build properties
Download:
16G:
http://hotfile.com/dl/148631145/4960f65/P6200XXLB1_P6200OXXLB1_16G.rar.html
32G
http://hotfile.com/dl/148631647/0d99ce0/P6200XXLB1_P6200OXXLB1_32G.rar.html
64G
http://hotfile.com/dl/148633091/a711c45/P6200XXLB1_P6200OXXLB1_64G.rar.html
Hello. And thank you. What fetures does this ROM include. Cheers.
Przekret said:
P6200XXLB1:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HTJ85B
ro.build.display.id=HTJ85B
ro.build.version.incremental=XXLB1
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Thu Feb 16 19:50:59 KST 2012
ro.build.date.utc=1329389459
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL174
ro.build.tags=release-keys
ro.product.model=GT-P6200
ro.product.brand=samsung
ro.product.name=GT-P6200
ro.product.device=GT-P6200
ro.product.board=GT-P6200
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=s5pc210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P6200
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P6200-user 3.2 HTJ85B XXLB1 release-keys
ro.build.fingerprint=samsung/GT-P6200/GT-P6200:3.2/HTJ85B/XXLB1:user/release-keys
ro.build.characteristics=tablet
ro.flash.resolution=1080
# Samsung Specific Properties
ro.build.PDA=P6200XXLB1
ro.build.hidden_ver=P6200XXLB1
ro.build.changelist=629097
# end build properties
Download:
16G:
http://hotfile.com/dl/148631145/4960f65/P6200XXLB1_P6200OXXLB1_16G.rar.html
32G
http://hotfile.com/dl/148631647/0d99ce0/P6200XXLB1_P6200OXXLB1_32G.rar.html
64G
http://hotfile.com/dl/148633091/a711c45/P6200XXLB1_P6200OXXLB1_64G.rar.html
Click to expand...
Click to collapse
i am confused is this stock or custom
It's a stock leak that may or may not be a future release.
jasonemorrow said:
It's a stock leak that may or may not be a future release.
Click to expand...
Click to collapse
ohhh right haha will it work on xxkl7? sorry in dumb haha.
This will work on all GT-P6200s. XXKL7 is a build of Honeycomb released by Samsung, not a device.
The important part to look at on this release is the "ro.build.date" property; for DXKL3 (the most-recent ROM before this), the build date was December 23rd. The build date of this ROM (XXLB1) is February 16th. That's nearly two months newer.
We can only hope that this addresses performance issues, etc. I'll flash it when I am around some Internet which isn't expensive.
Will this work on a 6210? Is it flashable with CWM or ODIN?
I see that it is a .pit file so it is flashable via ODIN or Heimdall. I also see a modem file. So I assume that there would be some changes to work on the WIFI only p6210.
Can anyone validate that they've been able to flash the 16GB version? I'm getting errors trying to untar the files:
Code:
$ tar xf P6200_APBOOT_P6200XXLB1_CL629097_REV02_user_low_ship.tar
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
For what it's worth, here are the hashes of my files:
Code:
dd5245c9ddb385ae313929d3aa91523f GT-P6200-MULTI-CSC-OXXLB1_RST.tar
2a0c4228865f68c48f2fcfc72bf559c9 MODEM_P6200XXKL7_REV_04_CL1088622.tar
36cbe18a0a05633e601afac9eb76f485 P6200_APBOOT_P6200XXLB1_CL629097_REV02_user_low_ship.tar
580d281653e61033af6446120b48f580 P6200_CODE_P6200XXLB1_CL629097_REV02_user_low_ship_16G.tar
And the rar download itself:
Code:
$ md5sum ../P6200XXLB1_P6200OXXLB1_16G.rar
cb88b0cf9ae16769bfb89f217d8799cf ../P6200XXLB1_P6200OXXLB1_16G.rar
Update: the 32GB version doesn't untar either.
painter_ said:
Will this work on a 6210? Is it flashable with CWM or ODIN?
I see that it is a .pit file so it is flashable via ODIN or Heimdall. I also see a modem file. So I assume that there would be some changes to work on the WIFI only p6210.
Click to expand...
Click to collapse
Honestly... I don't know. While the hardware on both devices should be identical (besides the modem), I know the P6200 and the P6210 have different partition maps...
i'm using MALAYSIA - GT-P6200UWAXME.
PDA: P6200DXKL3
PHONE: P6200DXKK5
CSC6200OLBKK8
1. can i flash this?
2. can i flash this using ODIN MOBILE?
also cant flash this... i got md5 error...
edan1979 said:
also cant flash this... i got md5 error...
Click to expand...
Click to collapse
My galaxy tab plus getting firmware error after getting stuck on odin,.. Seems like no one get nice ending on flashing this rom?..
hey can some one add an installation guide for this it seems to fail a lot. also may help others solve problem haha
has anyone got it to install successfully?
If so please report any noticeable changes and perhaps some screenshots of settings>about device>
Thanks.
chrisrotolo said:
has anyone got it to install successfully?
If so please report any noticeable changes and perhaps some screenshots of settings>about device>
Thanks.
Click to expand...
Click to collapse
have you give it a go if sa what did u do i may have done it wrong?
no I havent even tried, it looks like they released a similar update for netherlands and serbia. I think this first release is just a non regional - generic- update.
slightly large file size too.
chrisrotolo said:
no I havent even tried, it looks like they released a similar update for netherlands and serbia. I think this first release is just a non regional - generic- update.
slightly large file size too.
Click to expand...
Click to collapse
how do you instal it anyways do you know :-(
jmar8124 said:
how do you instal it anyways do you know :-(
Click to expand...
Click to collapse
You can't install it. It's corrupted. If it wasn't Heimdall or Odin would work.
aorth said:
You can't install it. It's corrupted. If it wasn't Heimdall or Odin would work.
Click to expand...
Click to collapse
ok bro thanks a lot
shal we ask the maker of this post to remove it?
jmar8124 said:
ok bro thanks a lot
shal we ask the maker of this post to remove it?
Click to expand...
Click to collapse
I am surprised he hasn't commented already... where is he?
I'm trying to root my device without success. The device is a Gemini Joytab 9.7 GEM10312G with Android 4.1.1.
I'm trying to use the method described here: http://forum.xda-developers.com/showthread.php?t=1886460 which exploits this bug: http://seclists.org/fulldisclosure/2013/Jun/115
I got to push the 'ro.kernel.qemu=1' into /data/local.prop using the restore bug but when I reboot the device and I open a shell with adb shell I can see that I'm not root (uid = 2000):
$ cat /data/local.prop
cat /data/local.prop
ro.kernel.qemu=1
$ id
id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
Maybe the adb bug is solved in this release? Any suggestion to get root on this device?
The device is not very common so it has no much info available. I get this info from /system/build.prop (maybe it can help to point to another rooting method). Thanks a lot.
cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03H
#ro.build.display.id=JRO03H
ro.build.display.id=20130402-1600
ro.build.version.incremental=user.crownh808.20130315.154827
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Mar 15 15:50:49 CST 2013
ro.build.date.utc=1363333849
ro.build.type=user
ro.build.user=crownh808
ro.build.host=crownho-server
ro.build.tags=release-keys
ro.product.model=GEM10312G
ro.product.brand=Infotmic
ro.product.name=A760
ro.product.device=GEM10312G
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Infotmic
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=imapx800
# ro.build.product is obsolete; use ro.product.device
ro.build.product=A760
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=A760-user 4.1.1 JRO03H user.crownh808.20130315.154827 release-keys
ro.build.fingerprint=Infotmic/A760/A760:4.1.1/JRO03H/user.crownh808.20130315.154827:user/release-keys
ro.build.characteristics=tablet
# end build properties
# system.prop for infotmic A760 reference board
# This overrides settings in the products/generic/system.prop file
# preload class
ro.infotm.no.preloadclass=1
# preload resource
ro.infotm.no.preloadresources=1
#launcher debug
sys.infotm.demoversion=false
sys.infotm.launcher.scrollspeed=middle
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=Hojus.ogg
ro.carrier=unknown
ro.config.alarm_alert=Cesium.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.phone.enabled=false
wifi.interface=wlan0
persist.sys.usb.config=mass_storage,adb
persist.sys.timezone=Europe/London
persist.sys.language=en
persist.sys.country=GB
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
otaupdater.otaid=GEM10312G-rev2-release
otaupdater.otaver=2
otaupdater.otatime=20130402-1600
otaupdater.sdcard.os=sdcard
otaupdater.sdcard.recovery=local
otaupdater.noroot=1
Im sorry,maybe i overlooked it,but i didnt see your device listed,also what genesis tablet is it?Joytab Duo?
The device is a Gemini JoyTab Duo 9.7 10312G. It is the same than this http://www.geminidevices.com/joytab10312bk.html but with no keyboard.
For sure Gemini is just rebranding some chinese tablet, but I have no found which one match. In my original message I paste some of the device info and maybe that can help. I found that others tablets have problems with this exploit: http://forum.xda-developers.com/showthread.php?t=2036539.
I also tried some generic unlockers like unlockroot, but they didn't work for this tablet. Anyone can help with this?
I have the stock rom available, will it be possible to modify the stock rom to be rooted? Maybe this will be a better way to get root on this tablet. If I do that, what will happen with OTA updates? Will them "unroot" my ROM?
Thanks a lot
Rooted system.img
Finally I have modified the stock ROM of the Gemini gem10312g-rev2. I added the OTA v2 upgrade and su and SuperUser.apk binaries:
-------------------------
ARM devices (2.0 – 4.1)
3.1.3
md5: b3c89f46f014c9df7d23b94d37386b8a
Superuser-3.1.3-arm-signed.zip
binary only
md5: d78ec986923b72dfdaa71d1db731a8f3
su-bin-3.1.1-arm-signed.zip
--------------------------
I uploaded the updated ROM to MEGA (h t t p s: / / m e g a . c o . n z /#!6ZNFkBaT!UXXXRxMM_82Hf4wEFIwWaWM7kPtL7bJR2H9MPwjw5yc). I hope than someone will find it useful. Remember that flashing the new ROM will delete all the data, applications and so on stored in the device.
P.S. Sorry about not writing the URLs correctly, but the forum don't allow me to add external URLS :/
hello
Hello, I need this ROM, the link does not work, if you still have it, send it to me by email, [email protected], thanks orium
Reuploaded ROM
jjykika said:
Hello, I need this ROM, the link does not work, if you still have it, send it to me by email, [email protected], thanks orium
Click to expand...
Click to collapse
The ROM can be downloaded here now: we.tl/qSYZ3KGxDH
get the room. please
Hello, the new link is not available someone has this room or can share. I need to be root to put the tablet in multiuser or is there another way?
Thanks
root with kingroot for pc
ruloalg said:
Hello, the new link is not available someone has this room or can share. I need to be root to put the tablet in multiuser or is there another way?
Thanks
Click to expand...
Click to collapse
Finaly i root with kingroot for pc
Rom link
Hello,
I need to recover my Geminy from a bootloop. The tablet is not rooted or a custom recovery is installed. I need this rom or the stock rom but the links doesn't work. The Mega one asks for a key and the other one doesn't work... can you update the link plz?
thank you
orium said:
Finally I have modified the stock ROM of the Gemini gem10312g-rev2. I added the OTA v2 upgrade and su and SuperUser.apk binaries:
-------------------------
ARM devices (2.0 – 4.1)
3.1.3
md5: b3c89f46f014c9df7d23b94d37386b8a
Superuser-3.1.3-arm-signed.zip
binary only
md5: d78ec986923b72dfdaa71d1db731a8f3
su-bin-3.1.1-arm-signed.zip
--------------------------
I uploaded the updated ROM to MEGA (h t t p s: / / m e g a . c o . n z /#!6ZNFkBaT!UXXXRxMM_82Hf4wEFIwWaWM7kPtL7bJR2H9MPwjw5yc). I hope than someone will find it useful. Remember that flashing the new ROM will delete all the data, applications and so on stored in the device.
P.S. Sorry about not writing the URLs correctly, but the forum don't allow me to add external URLS :/
Click to expand...
Click to collapse
ROM url
The rooted ROM can be downloaded here: 1drv.ms/u/s!AlMgcQQQM5h0h8oL3rZuQ32Cdoj23A
Thank you¡
Thank you very much and Happy New Year¡
orium said:
The rooted ROM can be downloaded here: 1drv.ms/u/s!AlMgcQQQM5h0h8oL3rZuQ32Cdoj23A
Click to expand...
Click to collapse
---------- Post added at 07:24 PM ---------- Previous post was at 07:14 PM ----------
I used Rock chip Batch Tool-1.7 to install a rom in other tablet but it was in one file *.img. In this one there are several files ¿Must I use other tool or is there any way to convert this rom in a *img file? How can I do it?...
elviti said:
Thank you very much and Happy New Year¡
Click to expand...
Click to collapse
Flashing The Rom
Hi,
Can anyone tell me a tool to flash this rom and a little explanation about the tool, just a few words please?
Thank you
Hello guys , i've ran into a real problem here...
this android tablet that i received for a gift , is rather odd...
i have no idea if anyone has heard of "MID" Make or model , i tryed searching the xda forums , but nothing turns up...
i really want to change this android os (2.3.1) to something newer...
I just have no clue how i am supposed to proceed with this...?
The least i can provide is the build.prop which doesn't make any sense at all...
other than that i can include the internal component's model's like cpu/gpu/wifi... etc... (if its only possible like that)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.eng.version=bena-20120707_142958
ro.build.version.incremental=eng.version=bena-20120707_142958
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.1
ro.build.date=2012.07.07
ro.build.date.utc=1341642675
ro.build.type=user
ro.build.user=arch
ro.build.host=archdev
ro.build.tags=
ro.product.model=Full Android on S5PV210
ro.product.brand=generic
ro.product.name=full_s5pv210bena
ro.product.device=s5pv210bena
ro.product.board=s5pv210bena
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=s5pv210bena
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_s5pv210bena-user 2.3.1 GINGERBREAD eng.version=bena-20120707_142958
ro.build.fingerprint=generic/full_s5pv210bena/s5pv210bena:2.3.1/GINGERBREAD/eng.version=bena-20120707_142958:user/
# end build properties
#
# system.prop for s5pv210bena
#
rild.libpath=/system/lib/libebena-ril.so
rild.libargs=-d /dev/ttyUSB0
#ro.sf.lcd_density=240
ro.sf.lcd_density=158
#ro.sf.hwrotation=270
ro.url.legal=google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.com.android.dataroaming=false
#ro.error.receiver.system.apps=com.google.android.feedback
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
dalvik.vm.heapsize=32m
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Please help i want this tablet flashed with a new firmware... but neither i have experience doing it , nor i want to risk making it worse...
InFesTeD_ThInG said:
Hello guys , i've ran into a real problem here...
this android tablet that i received for a gift , is rather odd...
i have no idea if anyone has heard of "MID" Make or model , i tryed searching the xda forums , but nothing turns up...
i really want to change this android os (2.3.1) to something newer...
I just have no clue how i am supposed to proceed with this...?
The least i can provide is the build.prop which doesn't make any sense at all...
other than that i can include the internal component's model's like cpu/gpu/wifi... etc... (if its only possible like that)
Please help i want this tablet flashed with a new firmware... but neither i have experience doing it , nor i want to risk making it worse...
Click to expand...
Click to collapse
Go to settings --> Info (There must be any informations about it)
OR have a look on the backside of the cover
Is THIS your tablet?
LS.xD said:
Go to settings --> Info (There must be any informations about it)
OR have a look on the backside of the cover
Is THIS your tablet?
Click to expand...
Click to collapse
Definettly looks like it , shape is diferent , screen wider and it haves touch screen buttons instead of normal ones.
Backside of the cover says nothing concrete.
And god this thing/s touch screen feels horrible.... or its deformed... :l (will have to find a suitable repair technician)
Specs are exactly the same as the one you found on amazon. (atleast the ones listed , idk about how the internal GPU / wifi or anything else is...)
Hello,
I just found this device:
Search on ALIExpress for: OEM A9 Quad core Reine Android 5.1.1 HD1024 * 600 16 GB Spiegel-Link 7 "Touchscreen 2 Din Universal Auto dvd GPS Stereo Radio
Does anyone have some more infos about it? Quality ? Is it really Lollipop?
Thanks
is not stable yet .
breckler said:
Hello,
I just found this device:
Search on ALIExpress for: OEM A9 Quad core Reine Android 5.1.1 HD1024 * 600 16 GB Spiegel-Link 7 "Touchscreen 2 Din Universal Auto dvd GPS Stereo Radio
Does anyone have some more infos about it? Quality ? Is it really Lollipop?
Thanks
Click to expand...
Click to collapse
Joying is selling units with Lollipop 5.1.1
https://www.carjoying.com/android-5-1-car-stereo/android-5-1-car-stereo-2din.html
Edit: Ignore my comment above. Apparently, the Firmware Joying is pushing as 5.1.1 is not. It's 4.4.2 skinned to look like 5.1.1
One xda member looked at the firmware Joying is pushing as 5.1.1 on his website and said "that 5.1 firmware isn't true lollipop, its more of a lollipop skin over the current KitKat firmware."
This xda member grabbed the firmware and opened it. He posted a screenshot of the parameters file that speaks for itself.
http://forum.xda-developers.com/showpost.php?p=66109420&postcount=2653
It appears Joying is pulling a fast one.
why is joying's new units are still 1GB RAM? that's horrible
Could this firmware work with the Pumpkin version? Joying says no but they are basically the same model units so I dont see why not.
I'm totally new when it comes to these android head units. The most important question I have is boot up time - does it have to start up every time the car starts or is it like sleep mode? Some say they take up to 10 seconds to boot up, then an additional 2 seconds to switch to the rear camera - that's a long time to wait! What is the fastest unit on the market at the moment? Do these custom roms help with boot time and overall speed?
savesheep said:
I'm totally new when it comes to these android head units. The most important question I have is boot up time - does it have to start up every time the car starts or is it like sleep mode? Some say they take up to 10 seconds to boot up, then an additional 2 seconds to switch to the rear camera - that's a long time to wait! What is the fastest unit on the market at the moment? Do these custom roms help with boot time and overall speed?
Click to expand...
Click to collapse
My unit, the tonghai 2nd gen, takes 12 seconds to boot. But if i start the car in reverse, the camera displays in 2/3 seconds, making the boot in background
devoidx said:
why is joying's new units are still 1GB RAM? that's horrible
Click to expand...
Click to collapse
It appears that his "new units" are just his old units, but that he may be putting a modified version of Android 4.4.2 on them that is skinned to look like 5.1.1 (See my edited post above)
Wow @Breach that is awfully shady of them to do that.
Breach said:
It appears that his "new units" are just his old units, but that he may be putting a modified version of Android 4.4.2 on them that is skinned to look like 5.1.1 (See my edited post above)
Click to expand...
Click to collapse
I'm not surprised, I honestly don't think we'll ever see a RK3188 based unit get a real upgrade.
The day a manufacturer puts a Mediatek or Qualcomm chip in one of these units, i'm switching.
Xtrons has lollipop HUs as well. Mine should be arriving today or tomorrow. I asked Xtrons for factory image, because I like to be able to restore to factory conditions if I mess with /system files. They hooked me up
Here's the build.prop, after extracting system.img from the update.img using imgRePackerRK, and then ext2explorer to read system.img:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LMY48Y
ro.build.display.id=rk3188-userdebug 5.1.1 LMY48Y eng.root.20160315.104842 test-keys
ro.build.version.incremental=eng.root.20160315.104842
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-12-01
ro.build.version.base_os=
ro.build.date=2016年 03月 15日 星期二 10:53:49 CST
ro.build.date.utc=1458010429
ro.build.type=userdebug
ro.build.user=root
ro.build.host=meng_book
ro.build.tags=test-keys
ro.build.flavor=rk3188-userdebug
ro.product.model=rk3188
ro.product.brand=rockchip
ro.product.name=rk3188
ro.product.device=rk3188
ro.product.board=rk30sdk
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=rockchip
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=rk3188
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk3188
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=rk3188-userdebug 15032016.18:11:53
ro.build.fingerprint=rockchip/rk3188/rk3188:5.1.1/LMY48Y/root03151051:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/rockchip/rk3188/system.prop
#
#
# system.prop
#
#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libril-rk29-dataonly.so
rild.libargs=-d /dev/ttyACM0
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#add Rockchip properties here
ro.rk.screenoff_time=2147483647
ro.rk.screenshot_enable=true
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.sf.hwrotation=0
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=false
ro.rk.systembar.tabletUI=false
ro.rk.LowBatteryBrightness=false
wifi.interface=wlan0
ro.tether.denied=false
sys.resolution.changed=false
ro.default.size=100
persist.sys.timezone=Asia/Shanghai
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.factory.tool=0
ro.kernel.android.checkjni=0
#set default lcd density to Rockchip tablet
ro.sf.lcd_density=240
ro.adb.secure =0
sys.hwc.enable=1
persist.sys.root_access=0
persist.sys.boot.check=false
ro.product.manufacturer9=HengChangTong
ro.product.model9=H660000
ro.product.customer=HCT4
ro.product.hostname=Android
ro.product.instruction=PDF
ro.product.videogesture=false
ro.product.bluetoothname=CAR KIT
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.target.product=tablet
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rksdk.version=RK30_ANDROID5.1.1-SDK-v1.00.00
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=80m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
camera2.portability.force_api=1
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rk.bt_enable=true
ro.factory.hasUMS=true
persist.sys.usb.config=mass_storage,adb
testing.mediascanner.skiplist=/mnt/internal_sd/Android/
ro.factory.hasGPS=false
ro.factory.storage_suppntfs=true
ro.factory.without_battery=false
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.sf.lcdc_composer=0
debug.hwui.render_dirty_regions=false
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ril.function.dataonly=1
ro.config.enable.remotecontrol=false
ro.product.version=1.0.0
ro.product.ota.host=www.rockchip.com:2300
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Everything indicates it's a true lollipop rom, sdk api level, ect.
Luxferro said:
Xtrons has lollipop HUs as well. Mine should be arriving today or tomorrow. I asked Xtrons for factory image, because I like to be able to restore to factory conditions if I mess with /system files. They hooked me up
Here's the build.prop, after extracting system.img from the update.img using imgRePackerRK, and then ext2explorer to read system.img:
Everything indicates it's a true lollipop rom, sdk api level, ect.
Click to expand...
Click to collapse
Interesting, which kernel version is it?
leonkernan said:
Interesting, which kernel version is it?
Click to expand...
Click to collapse
3.0.101, which means they are using an older android kernel like any of the other lolliopop roms for RK3188.
Can you share the image file?
I maybe would like to test it on my RK3188 4.4.4 unit.
Maybe we are able to update
Icefeldt said:
Can you share the image file?
I maybe would like to test it on my RK3188 4.4.4 unit.
Maybe we are able to update
Click to expand...
Click to collapse
Sure, I'll post it later when I get home from work.
Luxferro said:
Sure, I'll post it later when I get home from work.
Click to expand...
Click to collapse
Could you please share the rom?
Icefeldt said:
Can you share the image file?
I maybe would like to test it on my RK3188 4.4.4 unit.
Maybe we are able to update
Click to expand...
Click to collapse
Bart123 said:
Could you please share the rom?
Click to expand...
Click to collapse
https://mega.nz/#!7hMnWRJS!o2k8beD4jwE-7BdUxgj4MWOOUjEY8AeDRRvEyzVQHmk
Use at your own risk. Ideally have your stock ROM so you can return to it if it doesn't work for you.
Luxferro said:
https://mega.nz/#!7hMnWRJS!o2k8beD4jwE-7BdUxgj4MWOOUjEY8AeDRRvEyzVQHmk
Click to expand...
Click to collapse
Thank you very much.
Can you Link the device you ordered, for which the firmware is "intended" by Xtrons?
Icefeldt said:
Thank you very much.
Can you Link the device you ordered, for which the firmware is "intended" by Xtrons?
Click to expand...
Click to collapse
http://xtrons.com/pf75attar-7-inch-...-mirroring-function-obd2-for-audi-tt-mk2.html
http://www.ugsage.com/default/7-and...-mirroring-function-obd2-for-audi-tt-mk2.html
I'm considering picking up one of the Xtons 5.1.1 units for my E46. I can't decide if I should hold out a bit longer to see if any newer SOC's with 2GB RAM show up. For anyone who's purchased one yet do they still have the same issues with crappy microphones and poor radio audio quality?
Hi mates,
I just got it today, I didn't test it or flash it yet, it was created on the following date:
ui_print("Target: rockchip/rk3368/rk3368:9/PQ2A.190205.003/root03 26 1920:userdebug/test-keys");
so its unfortunately not the newest of the newest fw A9 but maybe you guys like to test it too?
DL: https://yadi.sk/d/3b5c-8Mqd67pXQ ... rk3368-ota-eng.root.zip
success
Sure, it is Android 9 and that it should work on px5? Anyone tried this and can confirm?
gforums said:
Sure, it is Android 9 and that it should work on px5? Anyone tried this and can confirm?
Click to expand...
Click to collapse
Hi mate,
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PQ2A.190205.003
ro.build.display.id=rk3368-userdebug 9 PQ2A.190205.003 eng.root.20190326.192040 test-keys
ro.build.version.incremental=eng.root.20190326.192040
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2019-03-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Tue Mar 26 19:20:03 CST 2019
ro.build.date.utc=1553599203
ro.build.type=userdebug
ro.build.user=root
ro.build.host=meng_book2
ro.build.tags=test-keys
ro.build.flavor=rk3368-userdebug
ro.build.system_root_image=true
ro.product.model=rk3368
ro.product.brand=rockchip
ro.product.name=rk3368
ro.product.device=rk3368
# 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.product.manufacturer=rockchip
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk3368
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=rk3368-userdebug 9 PQ2A.190205.003 eng.root.20190326.192040 test-keys
ro.build.fingerprint=rockchip/rk3368/rk3368:9/PQ2A.190205.003/root03261920:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties
#
# from device/rockchip/rk3368/system.prop
#
#
# system.prop
#
#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911
ro.opengles.version=196610
wifi.interface=wlan0
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
persist.tegra.nvmmlite = 1
ro.audio.monitorOrientation=true
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#add Rockchip properties here
ro.rk.screenoff_time=60000
ro.rk.screenshot_enable=true
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
vendor.hwc.compose_policy=6
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.sf.hwrotation=0
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=true
ro.rk.systembar.tabletUI=false
ro.rk.LowBatteryBrightness=false
ro.tether.denied=false
sys.resolution.changed=false
ro.default.size=100
persist.sys.timezone=Asia/Shanghai
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.factory.tool=0
ro.kernel.android.checkjni=0
#set default lcd density for rk3399
ro.sf.lcd_density=240
ro.adb.secure=0
#disable task_snapshots
persist.enable_task_snapshots=false
ro.product.locale=en-US
ro.product.manufacturer9=HengChangTong
ro.product.model9=H660000
ro.product.customer=HCT
ro.product.hostname=Android
ro.product.instruction=PDF
ro.product.gpspkname=null
ro.product.screenclock=false
ro.product.videogesture=false
ro.product.weatherhost=yahoo
ro.product.customer.sub=HCT5
ro.product.defaultlauncher=null
ro.product.drvingsafe=null
persist.display.landspace=true
ro.product.disCarNotifi=false
rf.product.recentshow=false
ro.product.bluetoothname=
ro.product.bluetoothpwd=
ro.product.btthreewaycall=false
rw.zlink.foreground.donotreqaf=1
ro.product.isshowbtvoiceico=true
ro.product.gpsmix=null
ro.product.gpstime=1
ro.product.gpsswitch=null
ro.product.gpsphone=null
ro.product.screentimeout=null
ro.product.time_24=null
ro.product.autotime=1
ro.product.powerdelay=null
ro.product.keycustomeq9=null
ro.product.dateformat=null
ro.product.barbacklight=null
ro.product.drivingoverspeed=false
persist.product.shownavbar=false
ro.product.volchannelgain=false
ro.product.dspversion=null
ro.product.brightnessmode=0
ro.product.sdcardswap=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a7
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xb4756f65ded248ecd6e994ca2af0a8f45a324652000000000000000000000000
I have installed PX5 and it works.Firmware date 26-03-2019
zeyret said:
I have installed PX5 and it works.Firmware date 26-03-2019
Click to expand...
Click to collapse
screenshots?
time bug still present? split screen working?
zeyret said:
I have installed PX5 and it works.Firmware date 26-03-2019
Click to expand...
Click to collapse
Hi Arkadash / Mate,
first thank you for your reply, can you test the following for "us" pls? the time receiving from the gps only, so you turn off the time received from (wifi) network and put it on gps and then after an hour or so go back to your car and see if the time runs well and does not remain the same when you left it?
Second, what do you think of the UI ((skin)) of this A9 is it nice? can you place a picture of it? if not, can you refer via the Ali -express- site to a similar A9 headunit with the same UI?
I don't have the time for it at the moment and I'm waiting for a newer version (have/use now the HA one) like that one from the/our Danish mate.. if he's got lucky with his headunit seller (Not like my seller with his 0,0 fw+mcu support!) and would give him the newest A9 fw + mcu version? that would be great for "us the mx's owners" .. that's why.
Thanks in advance mate.
Android 9.0 test 26-03-2019
1-GPS time is ok
2-Screen pane does not work.
3-1080p .ts videos are not smooth, video quality is not good.
Edit:I want to make a correction.
When you reset to the unit, the gps clock becomes corrupted.
zeyret said:
Android 9.0 test 26-03-2019
1-GPS time is ok
2-Screen pane does not work.
3-1080p .ts videos are not smooth, video quality is not good.
Click to expand...
Click to collapse
Hi Arkadaş / Mate,
thanks a lot for your reply, are you very sure about the time from gps Only but not from the wifi / network kardeş? and that it works 100% ok? I have no problem with that 1080p, I use mx player here with no problems maybe you need to used too?, I don't watch movies except for my boys and sometimes so not always. the UI looks very nice too .. I think I will try it out, it will certainly take 3 hours to do (install) everything again and incl. the entire iGO navi maps etc.
Zaman ayırdığınız için çok teşekkür ederim ve kardeşimi cevap :good:
Edit:
I'm not Turk so I did not read it good as well but it says: navigasyon otomatik zaman = navigation (gps) automatic time .. means time works from the gps receiving!
Goodluck mates
The best Husky wolf of the 3 A9 which I "already test" them..
Hi Mates,
I couldn't even wait until after noon, I already installed it, the gps time works immediately, but here he indicated the winter time after a few minutes, so an hour later, I have it now set it to gtm times and not to region , so select the time yourself if you get what I got.. I do the rest of installations after noon, I am now a bit too tired for that.
Goodluck.
Do you know if this release can be rooted with a common tool or method?
I would need xposed working on it.
Thanks a lot,
Christan
Time Bug is still exists..
Hi Mates,
Unfortunately, all the problems in the world came from bad communications, as I always tell (said to) my buddies, I was perhaps too soon cheered by my joy that the time bug was finally fixed, but unfortunately it is not, so time bug is still exists, for the rest one of the better A9 so far because of his nice UI.
Time Bug, the time was not updated when I turn off my car and after an hour or 2 I turn it on again, the time does not synchronize well with the local time as it should be while its making contact with the gps immediately.. so all in all, the time bug is still present on this fw version too.. regrettable!
Resume: the receiving gps time it doesn't refresh after I turn the car off!
gforums said:
Do you know if this release can be rooted with a common tool or method?
I would need xposed working on it.
Thanks a lot,
Christan
Click to expand...
Click to collapse
Hi mate,
I'm not 100% sure about that but.. take a good look at this one:
https://forum.xda-developers.com/an...5-oreo-rom-t3736950/post75741195#post75741195
Ps: I had once read about the so called ADB root method => https://www.youtube.com/watch?v=4v9s89fYIZ4 .. maybe?
Success mate.