Android 10.0 version from HA/Dasaita for PX6 Head Units.
Enjoy
Download:
Fast --> Download
build.prop:
Code:
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Mon Jul 6 19:46:51 CST 2020
ro.system.build.date.utc=1594036011
ro.system.build.fingerprint=rockchip/rk3399/rk3399:10/QQ2A.200305.004.A1/hct07061946: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.195022
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=rockchip
ro.product.system.device=rk3399
ro.product.system.manufacturer=rockchip
ro.product.system.model=PX6
ro.product.system.name=rk3399
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ2A.200305.004.A1
ro.build.display.id=rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200706.195022 test-keys
ro.build.version.incremental=eng.hct.20200706.195022
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 19:46:51 CST 2020
ro.build.date.utc=1594036011
ro.build.type=userdebug
ro.build.user=hct
ro.build.host=r930
ro.build.tags=test-keys
ro.build.flavor=rk3399-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=rk3399
# Do not try to parse description or thumbprint
ro.build.description=rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200706.195022 test-keys
# end build properties
#
# from device/rockchip/rk3399/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/rk3399/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 installed HA3 Android 10 on Max 6 Android 9 using Mod Installer Pro 2, and it worked perfectly.
Thanks so much.
firmware
Hi, did you take the Firmware from this Thread?? i have also a MAX 6 Android 9
thienthanty said:
I installed HA3 Android 10 on Max 6 Android 9 using Mod Installer Pro 2, and it worked perfectly.
Thanks so much.
Click to expand...
Click to collapse
Can someone extract for me the "HA3 Launcher" with the "HA3 Widgets apk"? Thanks!
can i use this update.zip to update to android 10 on my Dasaita px6 from android 9?
i think i have to use a update.img file for this first, am i right?
geldorf said:
can i use this update.zip to update to android 10 on my Dasaita px6 from android 9?
i think i have to use a update.img file for this first, am i right?
Click to expand...
Click to collapse
Hi, i have also a Dasaita px6. Today I make the update, first with only the .img in my USB Stick. Failure!!!
Then i put only the update.zip(ota) on the USB Stick and now all is fine. I do the Firmware Update with the Mod installer pro 2..it's so easy
volker64 said:
Hi, i have also a Dasaita px6. Today I make the update, first with only the .img in my USB Stick. Failure!!!
Then i put only the update.zip(ota) on the USB Stick and now all is fine. I do the Firmware Update with the Mod installer pro 2..it's so easy
Click to expand...
Click to collapse
then i have to buy the mod installer pro 2, which .img file did you use?
so far you like the new android 10?
Hi, i Like the new Android 10..all is fine. I take this https://docviewer.yandex.ru/view/0/?*=57W8JAFt8mlMmuchZnxm69fvACx7InVybCI6InlhLWRpc2stcHVibGljOi8vQ1dueWZoYjBBbzRuNnVrczVaYU9CNWpFK3J6a2IyTTRIcHViUSs3ejZxVT06L1JvY2tDaGlwIFBYNiBBbmRyb2lkIDEwL0hDVC9oY3Q3X3JrMzM5OV8xMC4wX290YSgyMDIwMDUyMykuemlwIiwidGl0bGUiOiJoY3Q3X3JrMzM5OV8xMC4wX290YSgyMDIwMDUyMykuemlwIiwibm9pZnJhbWUiOmZhbHNlLCJ1aWQiOiIwIiwidHMiOjE1OTM3ODQ0MDMxMDcsInl1IjoiNTkxMDk0MjU2MTU5Mzc4NDQwMyJ9 it have a Day and night screen and the Ui is much better as the Dasaita Ui..for me ...and sorry for my bad Englisch
Now HA3 have Split Screen like MX - Tested on Max 6 up to Android 10 by M.I.P 2
Hi guys,
I need to know something before update from 9 to 10.
Could you please check something for me?
Does Android 10 os have widevine lv3 drm?
Info can be checked via DRMinfo free app in google Play store.
Tried it, now i cant get my wifi to connect. It detects wifi networks around me, but wont connect to them.
I need to rollback to 9, does modinstaller need an Internet connection to work?
Morpheuspt said:
Tried it, now i cant get my wifi to connect. It detects wifi networks around me, but wont connect to them.
I need to rollback to 9, does modinstaller need an Internet connection to work?
Click to expand...
Click to collapse
When I first installed the HU in the car(April 3), I could not share my phone Wifi hotspot because of to many Wifi instability... ONLY when Bluetooth was also connected to my phone.
If I did not connect bluetooth... Wifi was OK.
I fix this by changing the BT module in Factory setting. (To WQ_BC6. Was SD-BC6).
But after upgrading to A10, the Wifi problems Again .
I fix the problem by changing the BT module in Factory setting back to SD-BC6.
All is good. Love A10,
I don't think ModInstaller pro needs internet.
Morpheuspt said:
Tried it, now i cant get my wifi to connect. It detects wifi networks around me, but wont connect to them.
I need to rollback to 9, does modinstaller need an Internet connection to work?
Click to expand...
Click to collapse
he don't need Internet Connection:good:
I am dumb.
Turns out there was no problem at all.
Im using a Huawei USB modem / router. Turns out that in A10, the head unit recognises the modem and connects to it through what it calls an ethernet connection, and when that's on, the WiFi doesn't work on purpose, because the head unit is getting Internet directly from the USB port.
So all is well.
Morpheuspt said:
I am dumb.
Turns out there was no problem at all.
Im using a Huawei USB modem / router. Turns out that in A10, the head unit recognises the modem and connects to it through what it calls an ethernet connection, and when that's on, the WiFi doesn't work on purpose, because the head unit is getting Internet directly from the USB port.
So all is well.
Click to expand...
Click to collapse
What is the model of the huawei?
E8372, iirc
Reliable thing, has never let me down.
Android Auto and Apple Carplay
Can you confirm Z-Link is working well and CarPlay runs well on Android 10 in a Dasaita Android 9 upgraded unit?
Dasaita informed me that Android 9 units could not be upgraded to Android 10... we all know it can be done, but are we loosing any function?
Cheers!
How to upgrade from max6 to 10 version
green99226 said:
How to upgrade from max6 to 10 version
Click to expand...
Click to collapse
What happened?
I can't upgrade to version 10, is there any way
Related
This came from a brazilian store...
I flashed a mod that replaced my framework-res.apk, but now I can't find the original one (my bad not to backup)
from the build.prop: (it says H.6.2-21)
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=H.6.2-21
ro.build.display.id=H.6.2-21.1300904098
ro.build.version.incremental=1300904098
ro.build.version.sdk=11
ro.build.version.codename=REL
ro.build.version.release=3.0.1
ro.build.date=Wed Mar 23 12:18:06 CDT 2011
ro.build.date.utc=1300900686
ro.build.type=user
ro.build.user=a22916
ro.build.host=il93lnxdroid47
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MZ604
ro.product.brand=MOTO
ro.product.name=PORTLA
ro.product.device=wifi_hubble
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=wifi_hubble
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=wifi_hubble-user 3.0.1 H.6.2-21 1300904098 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/PORTLA/wifi_hubble:3.0.1/H.6.2-21/1300904098:user/ota-rel-keys,release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
rild.libpath=/system/lib/libmoto_ril.so
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
persist.ril.mux.noofchannels=8
persist.ril.modem.mode=1
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
ro.telephony.default_network=4
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.full=Blur_Version.6.2.21.MZ604.Brasil.en.BR
ro.mot.setuptype=2
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Cobalt.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=3.0_r4
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
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.ms=android-motorola
Does any one have the same version????
Config ... About Tablet ... Version Number (last item) says "H.6.2-21.1300904098"
Yeah, it's Brazilian. Look at the build number und additional build properties. Have you tried flashing the us mz604 framework-res.apk? You should be able to fastboot flash the boot.img and system.img to the us wifi images and be fine.
Sent from my Xoom using Tapatalk
So I have 2 questions...
1) Can I use the canadian one??? as it have the brazilian portuguese translation??
2) How can I make a system.img and boot.img from my xoom, just in case something goes wrong so I can restore to as it is now?
The US framework-res.apk give me lots of FC
I have two framework-res.apk that works, both seens canadian, but I'm not sure... one, kinda works, but have some glitches the other have no glitches, but the market stops working
I'm afraid US or Canadian system.img & boot.img will not work... do I have reson to be afraid?
judison said:
2) How can I make a system.img and boot.img from my xoom, just in case something goes wrong so I can restore to as it is now?
Click to expand...
Click to collapse
Yes, in Clockwork Mod Recovery do a nandroid backup.
judison said:
I'm afraid US or Canadian system.img & boot.img will not work... do I have reson to be afraid?
Click to expand...
Click to collapse
The have been reports that the us image works on canadian MZ604s, so try it after making a nandroid backup.
I have flashed the canadian system.img & boot.img
It worked
(after that, I re-rooted it)
now I'm thinking about flashing the US Wifi Image, because most MODs are based on it...
but I will lose the brazilian portuguese translation, right?
Hi, I have a Laime L2+ MTK6589T Quad core 4.0.3, can't boot in to fastboot, can only reach recovery mode, as it keeps bootlooping, it loads to the boot screen say "Laime" and that's it, which leads me to think a corrupt boot, went ahead and wiped the cached etc. , is there an "update.zip" I can get from somewhere or I'm willing to make it myself as tbh i've had enough of my phones turning in to expensive paperweights
Also when I got the phone it didn't include any form of OTA firmware upgrading & there was no play store, if there's any way to include this that would be helpful.
Sorry for being a pain in the arse and asking so much for a first post :silly:
Anyone???
TheOMFG said:
Anyone???
Click to expand...
Click to collapse
www.needrom.com/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG
techrefresh said:
wwwneedromcom/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG
Click to expand...
Click to collapse
The phone does not boot in to fastboot mode, only recovery is there any way I can apply the rom as an update in recovery mode?, if so do need to compile a zip from what the "Upgrade application" downloaded???
I put the .pac file in and my phone never restarted and by the looks of it, no files were flashed to my device so I pulled all the files from the temp folder that it downloads to, here's what I've got:
boot.img
cache.img
DSP_DM_G2.bin
fdl1.bin
fdl2.bin
laime.bmp
nvitem.bin
recovery.img
SC8800G_sc8825_modem_vlx_6825.bin
SC8825.xml
system_2.img
u-boot.bin
u-boot-spl-16k.bin
userdata.img
vmjaluna_6825.image
WVGA_logo_256_t6_guangxin_180.bmp(1)
Where do I go from here?
????
http://specdevice.com/showspec.php?id=a7cb-ae42-ce49-2af60033c587
KERNEL: Linux version 3.0.8 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Aug 13 11:51:42 CST 2014
CODENAME: REL
Mainboard: sp8825c2
BRAND: L200
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: s9_1602
DISPLAY: T6GUANGXIN1602_4.3L035_CN_140813
FINGERPRINT: T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
HARDWARE: sc8825
ID: IML74K
TAGS: test-keys
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.version.incremental=140
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.date=Wed Aug 13 11:49:03 CST 2014
ro.build.date.utc=1407901743
ro.build.type=user
ro.build.user=jenkins
ro.build.host=relserver1
ro.build.tags=test-keys
ro.build.version.release=4.0.3
ro.product.model=L200
ro.product.brand=L200
ro.product.name=s9_1602
ro.product.device=s9_1602
ro.product.board=sp8825c2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=L200
ro.wifi.channels=
ro.board.platform=sc8825
# ro.build.product is obsolete; use ro.product.device
ro.build.product=s9_1602
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=s9_1602-user 4.0.3 IML74K 140 test-keys
ro.build.characteristics=default
#-----below add or modified by revo begin------------
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.language=zh
persist.sys.country=CN
ro.macro.pro=t6_1602-guangxin
ro.macro.subpro=t6_1602-guangxin-4.3_l035
ro.device.support.gps=1
ro.device.support.gsensor=true
ro.device.support.psensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.bt=true
ro.device.support.wifi=true
ro.device.support.uplmn=false
ro.device.flashlight=true
ro.device.single_camera=false
ro.sf.hwrotation=0
ro.build.display.id=T6GUANGXIN1602_4.3L035_CN_140813
ro.build.fingerprint=T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.config.ringtone0=Backroad.ogg
ro.config.ringtone1=Backroad.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=
ro.macro.music_light_style=true
ro.macro.single_signal=yes
universe_ui_support_revo=true
ro.lockscreen.android42=false
ro.lockscreen.four.point=true
ro.macro.androidlogo.jellybean=yes
ro.macro.incall_touch_lock=yes
ro.macro.InCallScreenOffTime=
ro.macro.focus=true
ro.macro.auto_time_zone=no
ro.macro.connectdata=no
ro.macro.default_inputmethod=baidu
ro.macro.is24hour=yes
ro.macro.ip_dail=yes
ro.macro.screen_brightness=b_80
ro.macro.volume_music=d_12
ro.macro.volume_ring_notifi=d_7
ro.macro.volume_alarm=d_5
ro.macro.volume_fm=d_15
ro.macro.screen_timeout=lvl_1
ro.macro.install_no_market=true
ro.macro.font_size=Normal
ro.macro.boot_ani_choose=no
ro.email.default.signature=
ro.macro.status_bar_bg=transparent
ro.macro.status_bar_bg2=part_transparent
ro.macro.status_bar_bg3=
ro.macro.baseband_mtk_type=MTK6589T
ro.macro.baseband_mtk_number=quad_core
ro.macro.showcpuwithbb=
ro.macro.android_version=4.2.1JOP40D
ro.macro.kernel_version=3.4.35-g1f428cc
ro.macro.lockscrn_no_statusbar=yes
persist.sys.timezone=Asia/Shanghai
ro.macro.fake_romsize=
ro.macro.increase_ram=
ro.macro.vibrate_on=yes
ro.macro.accele_rotation=false
dailpad_search_list_custram=
ro.macro.camera_fullscreen=
ro.macro.dtmf_volume=40
ro.macro.custom_logo=
ro.macro.cycle_slip=
ro.macro.simcardnumber=
ro.macro.shutdownanim=
ro.macro.wifi_tether_ssid=
ro.macro.audio_profile=
ro.macro.hide_qsb_bar=yes
ro.macro.haptic_feedback=
ro.macro.native_launcher=
ro.macro.dtmf_tone=
ro.revo.testcase_alert=true
ro.revo.testalert_code=true
ro.revo.dcaf_orientation=false
device.support.dccaf=0
device.support.dvcaf=0
ro.macro.not_show_focustip=
ro.revo.gs_replace_ps=true
ro.revo.gs_replace_ps_value=
ro.revo.call_connection_notify=
ro.revo.exchange.notification=
ro.revo.fakedisplaysize=
ro.revo.useoneincomingsrc=
scroll_quick_switch=
ro.contacts.showstarredonly=
ro.revo.ori_incallscreen=true
ro.macro.statusbar_add_font=
ro.macro.wifi_policy=0
ro.revo.android_calc_style=
ro.revo.homepage=
###---3rd party func property
ro.macro.lqplay_lock=
ro.macro.yl_lock=
ro.sky.browser.support=true
ro.macro.cooee_lock=no
ro.macro.ouxin_switch=
ro.macro.all_apps_button_pos=
ro.macro.ibingo_lock=
ro.macro.yllg_lock=
ro.macro.ringcool=
ro.revo.mcetools=
#-----add or modified by revo end-----------
ro.macro.fake_new_function=
ro.macro.fake_score=
ro.macro.fake_resolution=
ro.macro.fake_camera=
ro.macro.fake_cpu=
ro.macro.fake_cpu_hz=
ro.macro.fake_gpu=
ro.macro.fake_rom=
ro.macro.fake_ram=
ro.macro.fake_pixel=
ro.mocro.single_simcard=
ro.macro.pro_sub=
ro.macro.fake_cpu_model=MTK6589
ro.macro.fake_android_version=
ro.macro.fake_dpi=
ro.macro.fake_freq=
ro.macro.google_ui=
ro.macro.vibrate_last=
ro.macro.vibrate_sleep=
ro.revo.sound_save_path=
ro.revo.sales=
ro.revo.sales_number=
ro.revo.add.reboot.menu=
ro.macro.display_battery=
ro.com.android.dateformat=MM-dd-yyyy
ro.macro.own_wallpaper_lock=
ro.revo.power_save=false
ro.macro.close.dc.sound=no
ro.device.support.vt=0
ro.revo.uui_incallscreen=
ro.macro.sync_wallpaper=
persist.sys.salescount=
persist.sys.sales_num=
persist.sys.sales_time=
ro.macro.yingmai_googleui=
ro.macro.yingmai_zen=
ro.macro.mms_signature=
ro.macro.tracker=
persist.sys.trackerstatus=
persist.sys.trackernum=
persist.sys.trackerpass=
persist.sys.trackerimsi=
ro.macro.statusbardata_mkt=
ro.browser.fontsize=
ro.macro.simcardnozero=
# end build properties
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.gpu=mali
ro.opengles.version=131072
ro.device.support.mmc=1
hwui.render_dirty_regions=false
ro.hwui.text_cache_width=2048
persist.ttydev=ttyVUART0
#if our product support cmcc feature, then set the value true, else do nothing
ro.wifi.support.cmcc=true
#our sp6825c1 product supports Trout chip
ro.wifi.chip.vender=trout
# Can not install packages if the data space has used more than the following ratio value
ro.datastorage.threshold=85
#if out product surport trout chip, we set this
ro.fm.chip.vendor=trout
#if out product surport trout chip, we set this to support hci rset to power off
ro.bt.trout=true
ro.device.support.vt=0
#if our product support single link version
ro.system.property.singleconn=true
ro.product.hardware=sp8825C2_V1.0.0
#true default, false if bt/wifi should not coexist.
ro.btwifi.coexist=true
#if out product support fastboot feature, set as true
persist.sys.support.fastboot=false
# modify for AMS kill background process
ro.support.amskill=true
#if our product not support bt wifisoftap coexist
ro.btwifisoftap.coexist=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
lmk.autocalc=false
ksm.support=false
zram.support=true
zram_for_android.enable=true
persist.sys.service.delay=false
persist.sys.lowmem=16
ro.build.product.lowmem=1
persist.blcr.enable=0
ro.callfirewall.disabled=true
persist.msms.phone_count=2
persist.msms.phone_default=0
persist.sys.lowcost=true
persist.sys.sprd.modemreset=1
persist.sys.kdump.enable=0
dalvik.vm.heapstartsize=3m
dalvik.vm.heapsize=64m
dalvik.vm.heapgrowthlimit=48m
ro.config.ringtone=BeatPlucker.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.logappslow=0
ro.floatkey.show=false
persist.sys.kb.auto=1
device.support.face.smile=0
device.support.pano=0
have you already tried factory reset in cwm and clear cashe/data/dalvik cache? try deleting and reseting everything posible. This might remake partitions and reflash some files that maybe have somehow gone wrong and causing bootloop. Also sometimes apps or combinations of apps can make the phone bootloop. Then wiping dalvik cache can help or factory reset can delete the non-system apps that caused it. Either way, it's worth trying it.
If this didn't fix the problem, try to find somthing with a working laime l2+ and ask him to make an backup in cwm and sent his files to you. You should have a file named "clockworkmod" on your sd-card, check if there's a file named "backup" (if there isn't, just make it), and place the backup file inside this folder. The backup file should be name somthing like "2015-04-24.18.03.57" so just a date, and contain some files like boot.img, .android_secure.vfat, cache.ext4.tar, data.ext4.tar and so on. Then go into recovery and restore this backup.
That's the best I can do for you as I don't know a lot about pushing rom's with pc, don't have a laime l2+ myself and don't know anyone who have one.
Pleas hit thanks, as I took the time to try to help you
Hi, thank you for taking the time reading my post and any help or directions you could give to solving my problem.
I was given a phone (Samsung Galaxy Note 3) to replace my aging LG Optimus P509.
When I received the SGN3 I did a wipe of the user data so it was pristine through the recovery feature to put it back to 'stock'.
And that's when my issues began.
PROBLEM #1
First thing that happened after wiping is I 'lost' the internal 16Gb SD storage.
PC would only see the 2Gb's of application storage. Android system would see the 16Gb's, BUT it was reported as 'filled' with 15Gb's of data. If I just DID a wipe of the user data then where did all this 'data' come from???
So started looking around the system using different root explorers to see if I could manually delete the bloated data.
Couldn't find it.
I DID discover that the 'folder' that the 16Gb storage was under had no permissions. Just a series of dashes where the permissions would be listed. The OS's corrupted somehow...
Used a different Home loader and IT was reporting the 16Gb internal SD storage as there and pretty much empty. But still no access.
So I take it to a 'phone repair' place and explain to the guy what my issue was. Figured he was just going to look around and see what he could see. Nope, he starts pressing buttons and gets to the "recovery screen"...eventually. When I realized what he had did it was too late to stop him.
PROBLEM #2
The 'recovery screen' was not what I once saw, blue and orange screen with a droid on it, to a black screen with white characters with three options. Fast Boot, Recovery, Normal
AND the screen was now upside down in orientation and you could not use the 'enter' key (volume up). Refuses to select anything. So no more recovery option.
I learned through researching the issues here on XDA that a replacement ROM would be something I should do to address my issues, just reflash. Start anew.
I learned that the Device (Samsung Galaxy Note3) is NOT a SGN3! It's a KnockNote (my term). To my understanding you cant flash an OEM ROM on a non-OEM device. It's a Mediatek MT65xx device, made by China.
So I start looking around for a ROM to put on there. Not much that I can understand...
Here is the kernel information that 'could' help with identifing the device.
Code:
SM-N9006
Android version: 4.4
Baseband Ver.: N9006ZCUBMI3
Kernel Version: 3.4.0-1590669
[email protected] #1
Wed Sep 11 23:59:42 KST 2013
Build Number: JSS15J.N9006ZCUBMI5
Possible model (android tuner, build information) MT6620 (mt6582)
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=ALPS.JB5.MP.V1.5
ro.build.version.incremental=eng.rs.1390483692
ro.custom.build.version=.N9006V116En20140123
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.4
ro.build.date=2014年 01月 23日 星期四 21:29:52 CST
ro.build.date.utc=1390483792
ro.build.type=user
ro.build.user=rs
ro.build.host=rs-ThinkStation-D30
ro.build.tags=test-keys
ro.product.model=Samsung GALAXY Note 3
ro.product.brand=alps
ro.product.name=lcsh82_wet_jb5
ro.product.device=lcsh82_wet_jb5
ro.product.board=lcsh82_wet_jb5
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lcsh82_wet_jb5
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lcsh82_wet_jb5-user 4.4 JDQ39 eng.rs.1390483692 test-keys
ro.build.fingerprint=alps/lcsh82_wet_jb5/lcsh82_wet_jb5:4.4/JDQ39/1390483692:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
persist.sys.timezone=Asia/Shanghai
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB5.MP.V1.5
ro.mediatek.platform=MT6582
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB5.MP
ro.mediatek.version.sdk=1
# end mediatek build properties
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=180
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=MT6620
mediatek.wlan.module.postfix=_mt6620
ril.radiooff.poweroffMD=0
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.ringtone=Over_the_horizon.mp3
ter.service.enable=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
So I began using it as basically a PDA until I could get things sorted out.
PROBLEM #3
I allowed my niece (9yrs) to play some games on it and...she set up a very nice and complicated pattern lock that was so pretty to her that she forgot the pattern. not a problem as long as wi-fi or cell service is on...which this device has neither.
(no SIM, I turned off wifi before I handed it to her)
My questions are these:
Q 1 : Can I install a recovery ROM, stock ROM to the device?
If so, can you direct me (link) to where I can find the one I should use, based on your knowledge?
Q2: I can not get into the phone (pattern lock), is there a way to establish a connection to the phone even though I don't have access to 'developer options'?
Q3: Could you describe the steps needed to complete this task, I KNOW there are tuts galore. That's part of the problem. So many different ways, options, etc.
Since I am residentially challenged at the moment due to a fire this device is pretty critical to me and I can't screw it up, no fails, no bricks.
Any and all help you could offer would be appreciated.
If you need any more information about the device or require clarification please ask your questions.
Additional Information:
No WiFi (local/cell)
No Cellular Service
No 'developer/debug options' (because I am locked out of device with a pattern lock, see above)
No Adb
***BoM***
If this post is in the wrong place please direct me where to place it. XDA is a large place with a lot to sort through.
***EoM***
Hi,
The only way to get past a pin lock you can't figure out is completely wiping and flashing the stock firmware again, or custom ROM.
You will need to find out more details on the device. Make, model and exact model number, as flashing something not made for your device will likely brick it.
That said, you will need to ask for help here,
> Android Development and Hacking > Android Q&A, Help & Troubleshooting
And personally, I'd leave out the don't waste my time or yours part...as that likely will cause many to pass you by. Not every reply is going to be 100 percent accurate or relevant...but trying to help is better than not trying. That's the spirit here. And it's a part of any internet forum. Just my humble opinion.
Good luck!
Thank you. Thread closed.
This thread is for Nextbook Ares 8 5.1.1
I don't have this device yet, @Conan1201 has offered to send me one, once I get it, I can begin the process of dumping the tablet, pulling the firmware, root, then TWRP.
What I would like is everyone that has this tablet, to post their build.prop and boot.img for each version they have, I am trying to see what the pattern is that is causing some versions to lose sound yet others don't.
Anyway all posts related to Nextbook Ares 8 5.1.1, should be posted in this thread, helps to keep all related posts in one thread, right now 3 or 4 threads have people posting about Nextbook Ares 8 5.1.1, most of those threads have nothing to due with this tablet.
A lot of people are contacting me, after failed attempt of using @greatbal instructions or backup, I have nothing to due with @greatbal, I did read his thread yesterday downloaded the backup he provided, unpacked it, and see that is for an entirely different device, His backup manufacturer Logitech.
It should be, manufacturer Yifang.
Yifang version is nxm890bap
Logitech version is ebm890bap
They indeed two different tablets, one might be able to port one version to the other, but just trying to use one version over the other would cause problems.
Anyway @greatbal did let people know what version he had, and I believe if you had the same version @greatbal had, you would have been fine, the differences in the hardware/software isn't @greatbal fault.
Update 3-22-2017
I have received the tablet from @Conan1201.
Below is a part of the build.prop, an important part is the last line ro.build.flavor, that was the fix for sound on my tablet.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.hwversion.id=V3.0.1
ro.ota.version.id=V1.0.2
ro.git.version.id=520cd962040ded28926dfaf6e07385aac0420aca
ro.build.id=LMY47V
ro.build.display.id=V1.0.2.LMY47V.eng.midpublic.20160529.132930
ro.build.version.incremental=eng.midpublic.20160529.132930
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-11-01
ro.build.version.base_os=
ro.build.date=Sun May 29 13:30:49 EDT 2016
ro.build.date.utc=1464543049
ro.build.type=user
ro.build.user=midpublic
ro.build.host=mid
ro.build.tags=release-keys
ro.product.model=NXA8QC116
ro.product.brand=NextBook
ro.product.name=NXA8QC116
ro.product.device=NXA8QC116
ro.product.manufacturer=Yifang
ro.build.flavor=nxm890bap_e_jj_64-user
Ok, some back ground, I got the tablet today, I work out of town stay in a hotel, my wife brought me the tablet and a small Linux laptop.
Setup tablet, enable usb debugging, reboot to bootloader
adb reboot bootloader
Now unlock bootloader
fastboot oem unlock
the tablet is supposed to reboot into recovery and format itself, it didn't I gave it 3 or 4 minutes.
I manually reboot tablet.
Got boot screen up android down recovery
choosing down, I get boot image error, which means recovery partition is locked, due to oem unlock.
boot into bootloader
fastboot oem lock
now reboot recovery no problem.
so recovery partition is out.
This tablet can have a permanent TWRP recovery, only temp TWRP recovery for now, I pulled system, recovery.img, boot.img, fastboot.img,ESP.img.
I backed doored the device and in doing so lost sound, I was able to recovery sound by examining different boot.img and build.prop there is always a pattern just finding it sometimes is the *****.
The pattern ro.build.flavor
Update 3-23-2017
Ok, I put together a Linux / Windows package to let people backup their tablet, you should do this before you root device or anything else some people lost sound, restoring your backup made by this recovery will fix that.
Code:
This is for LInux
You need to already have your tablet setup with usb debugging enabled.
adb reboot bootloader
sudo ./fastboot oem unlock
sudo ./fastboot format userdata (note this is optional, you will lose everything on internal sdcard.)
sudo ./fastboot format cache
sudo ./fastboot.sh
on tablet volume down until you see RESTART BOOTLOADER
power
sudo ./trigger 4
wait for recovery to load will take several minutes.
do a backup to micro sdcard, don't backup data or cache as nothing is there, back up system recovery boot to micro sdcard
Code:
I am don't use windows much from memory the below should be correct, look over it if something needs to be changed let me know.
Note [user=4821597]@social-design-concepts[/user] has a complete windows version of tethering twrp, you still need my files to switch bootloader, once that is done you can then use [user=4821597]@social-design-concepts[/user] tool, or continue using below instructions.
This is for Windows
You need to already have your tablet setup with usb debugging enabled.
adb reboot bootloader
fastboot oem unlock
fastboot format userdata (note this is optional, you will lose everything on internal sdcard.)
fastboot format cache
fastboot flash ESP esp.img
fastboot flash fastboot droidboot.img
on tablet volume down until you see RESTART BOOTLOADER
power
Note if you are going to use [user=4821597]@social-design-concepts[/user] windows tool use it now, else continue with my instructions.
fastboot flash /tmp/recovery.zip recovery.zip
fastboot flash /tmp/recovery.launcher recovery.launcher
fastboot oem start_partitioning
fastboot flash /system/bin/logcat recovery.trigger.new
fastboot oem stop_partitioning
wait for recovery to load will take several minutes.
do a backup to micro sdcard, don't backup data or cache as nothing is there, back up system recovery boot to micro sdcard
Note [user=4821597]@social-design-concepts[/user] tool listed below, any question on his tool ask in below thread, I have no personal experience, but I know it has helped many windows users.
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Download tethered recovery package
You need to extract to use, set permission on files if needed.
https://www.androidfilehost.com/?fid=457095661767147708
Now that the bootloader has been replaced flashing permanent recovery is possible, I already have permanent recovery on mine.
You all need a few more steps, the first is above backing your tablet up.
Next you need to get familiar with Carliv Image Kitchen for Android - unpack/repack boot-recovery
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
Those backed up boot.img need to be modified, we will get into that later.
credits
@greatbal
5.1 rom backup
@Conan1201
Giving me this tablet
@cellneuron
boot.img, build.prop
@social-design-concepts
recovery.launcher, recovery.trigger.new, recovery.trigger.original
@teamwin
recovery source
@vampirefo
putting this together
If you had done above and changed bootloaders, you can now install permanent recovery.
fastboot flash recovery TWRP_ARES_8_5.1_recovery.img
use bootloader to boot into recovery
in twrp
Wipe > Format Data
https://www.androidfilehost.com/?fid=529152257862713741
If you have same version as I have here is a flashable rom for it, should be used will above recover.
ro.build.flavor=nxm890bap_e_jj_64-user
to install boot into twrp
Wipe > Format Data
install Ares8_5.1_nxm890bap_e_jj_64.zip
https://www.androidfilehost.com/?fid=745425885120718639
This is 3.1 TWRP for those that want it.
https://www.androidfilehost.com/?fid=817550096634761287
This is one of my build.prop.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.hwversion.id=V7.0.4
ro.ota.version.id=V3.0.3
ro.git.version.id=bd615d50e1043c67a980a006a6d2d9a9bd8ff687
ro.build.id=LMY47V
ro.build.display.id=V3.0.3.LMY47V.eng.midpublic.20160815.090809
ro.build.version.incremental=eng.midpublic.20160815.090809
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-11-01
ro.build.version.base_os=
ro.build.date=Mon Aug 15 09:09:05 HKT 2016
ro.build.date.utc=1471223345
ro.build.type=user
ro.build.user=midpublic
ro.build.host=mid
ro.build.tags=release-keys
ro.product.model=NXA8QC116
ro.product.brand=NextBook
ro.product.name=NXA8QC116
ro.product.device=NXA8QC116
ro.product.manufacturer=Yifang
ro.build.flavor=nxm890bap_e_hd_64-user
ro.product.board=baytrail
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nxm890bap_e_hd
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=nxm890bap_e_hd_64-user 5.1.1 LMY47V eng.midpublic.20160815.090809 release-keys
ro.build.fingerprint=NextBook/NXA8QC116/NXA8QC116:5.1.1/LMY47V/V3.0.0:user/release-keys
ro.build.characteristics=nosdcard,tablet
# end build properties
#
# from device/intel/baytrail/nxm890bap_e_hd/system.prop
#
#
# system.prop
#
ro.intel.screenoff_time=-1
ro.intel.def_brightness=145
ro.intel.homepage_base=http://search1.ereadingsource.com/home?client=KBM-0001&source=browser-home
persist.sys.timezone=America/New_York
ro.intel.need_wizard=1
ro.bool.adddemomode=true
ro.intel.demo_mode=0
ro.mtp.manufacturer=Yifang
ro.mtp.model=NXA8QC116
ro.ota.product.name=nxm890bap_e
ro.product.ota.host=wota.yifangdigital.com:9881
ro.com.google.clientidbase=android-efun
ro.com.google.clientidbase.ms=android-efun
ro.com.google.clientidbase.yt=android-efun
ro.com.google.clientidbase.am=android-efun
ro.com.google.clientidbase.gmm=android-efun
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.disablelonglongpress=true
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=174m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
systemui.lfb.enabled=1
drm.service.enabled=true
persist.tel.hot_swap.support=true
ro.opengles.version=196609
ro.sf.lcd_density=160
ro.blankphone_id=1
ro.com.google.clientidbase=android-intel
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.ril.status.polling.enable=0
dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1
---------- Post added at 04:48 PM ---------- Previous post was at 04:23 PM ----------
My second Ares 8 v5.1.1. I still have another one which has flashed Batville without sound. These two also have no sound after flashing Greatbal's recovery.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.hwversion.id=V5.0.6
ro.ota.version.id=V1.0.6
ro.git.version.id=bd615d50e1043c67a980a006a6d2d9a9bd8ff687
ro.build.id=LMY47V
ro.build.display.id=V1.0.6.LMY47V.eng.midpublic.20160913.102503
ro.build.version.incremental=eng.midpublic.20160913.102503
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-11-01
ro.build.version.base_os=
ro.build.date=Tue Sep 13 10:26:01 HKT 2016
ro.build.date.utc=1473733561
ro.build.type=user
ro.build.user=midpublic
ro.build.host=mid
ro.build.tags=release-keys
ro.product.model=NXA8QC116
ro.product.brand=NextBook
ro.product.name=NXA8QC116
ro.product.device=NXA8QC116
ro.product.manufacturer=Yifang
ro.build.flavor=nxm890bap_e_jd_64-user
ro.product.board=baytrail
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nxm890bap_e_jd
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=nxm890bap_e_jd_64-user 5.1.1 LMY47V eng.midpublic.20160913.102503 release-keys
ro.build.fingerprint=NextBook/NXA8QC116/NXA8QC116:5.1.1/LMY47V/V3.0.0:user/release-keys
ro.build.characteristics=nosdcard,tablet
# end build properties
#
# from device/intel/baytrail/nxm890bap_e_jd/system.prop
#
#
# system.prop
#
ro.intel.screenoff_time=-1
ro.intel.def_brightness=145
ro.intel.homepage_base=http://search1.ereadingsource.com/home?client=KBM-0001&source=browser-home
persist.sys.timezone=America/New_York
ro.intel.need_wizard=1
ro.bool.adddemomode=true
ro.intel.demo_mode=0
ro.mtp.manufacturer=Yifang
ro.mtp.model=NXA8QC116
ro.ota.product.name=nxm890bap_e
ro.product.ota.host=wota.yifangdigital.com:9881
ro.com.google.clientidbase=android-efun
ro.com.google.clientidbase.ms=android-efun
ro.com.google.clientidbase.yt=android-efun
ro.com.google.clientidbase.am=android-efun
ro.com.google.clientidbase.gmm=android-efun
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.disablelonglongpress=true
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=174m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
systemui.lfb.enabled=1
drm.service.enabled=true
persist.tel.hot_swap.support=true
ro.opengles.version=196609
ro.sf.lcd_density=160
ro.blankphone_id=1
ro.com.google.clientidbase=android-intel
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.ril.status.polling.enable=0
dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1
cellneuron said:
This is one of my build.prop.
Click to expand...
Click to collapse
Thanks I need boot.img for each as well.
vampirefo said:
Thanks I need boot.img for each as well.
Click to expand...
Click to collapse
I only backed up one of them in twrp, which is not img format. How to get it for you? The tablet itself has been flashed Greatbal's boot.img.
cellneuron said:
I only backed up one of them in twrp, which is not img format. How to get it for you? The tablet itself has been flashed Greatbal's boot.img.
Click to expand...
Click to collapse
I already downloaded @greatbal boot.img, I don't need it, so all your tablets have been flashed via @greatbal backup?
the one you backed up with twrp should have backup up your boot.img, it will be called boot.emmc.win.
vampirefo said:
I already downloaded @greatbal boot.img, I don't need it, so all your tablets have been flashed via @greatbal backup?
the one you backed up with twrp should have backup up your boot.img, it will be called boot.emmc.win.
Click to expand...
Click to collapse
This boot is for v1.0.6.
cellneuron said:
This boot is for v1.0.6.
Click to expand...
Click to collapse
Ok, thanks I built a recovery based on this boot.img and 1.0.6 build.prop.
Once I receive the tablet I will pull the build.prop from that tablet to compare with yours, if it's correct or close enough I will then dump the tablet's firmware.
vampirefo said:
Ok, thanks I built a recovery based on this boot.img and 1.0.6 build.prop.
Once I receive the tablet I will pull the build.prop from that tablet to compare with yours, if it's correct or close enough I will then dump the tablet's firmware.
Click to expand...
Click to collapse
That's great. Can't wait. Just keep in mind my boot was pulled by wrong recovery.
cellneuron said:
That's great. Can't wait. Just keep in mind my boot was pulled by wrong recovery.
Click to expand...
Click to collapse
Everything the recovery backed up would be correct and usable, a recovery just backs up.
The recovery doesn't modify the backup in anyway, what ever a recovery backed up is what was on the device.
Sent from my NS-P08A7100 using Tapatalk
Does anyone use Linux? I want to know what happened when using trigger 4?
Has anyone backed up ESP?
Would anyone be willing to back up ESP and upload it?
Sent from my NS-P08A7100 using Tapatalk
I have received the tablet from @Conan1201 , I work out of town, be a couple day before I am able to release anything.
I do have some info, I am posting to OP.
vampirefo said:
I have received the tablet from @Conan1201 , I work out of town, be a couple day before I am able to release anything.
I do have some info, I am posting to OP.
Click to expand...
Click to collapse
Great.
cellneuron said:
Great.
Click to expand...
Click to collapse
The temp recovery is up, if people use it and share their back ups, everyone's tablet will get fixed.
We need a backup of each flavor, restoring the correct flavor, to the correct tablet fixes sound.
The recovery will back up recovery, boot, and system, restoring these on the correct tablet returns tablet to out of box, eg working sound.
We can't trick the tablet, it knows what flavor it originally came with, only restoring the exact flavor fixes the problem.
vampirefo said:
The temp recovery is up, if people use it and share their back ups, everyone's tablet will get fixed.
We need a backup of each flavor, restoring the correct flavor, to the correct tablet fixes sound.
The recovery will back up recovery, boot, and system, restoring these on the correct tablet returns tablet to out of box, eg working sound.
We can't trick the tablet, it knows what flavor it originally came with, only restoring the exact flavor fixes the problem.
Click to expand...
Click to collapse
More people should join. I don't have any virgin nextbook ares 8 now.
Just found the topic. Thanks a lot for working on this.
I got two Ares8 without sound due to the root process. I was able to find another unrooted table and followed the exact steps to backup the boot/recovery/system as in the first post.
However, after shutdown, my unrooted one will no longer boot. It got stuck at the next book logo screen for a few minutes, then reboot to this screen again. I could still get into the boatloader and the stock recovery, but what do I do now?
I also used the backup to restore one of my rooted Ares 8, before realizing this. It also wont even boot.
minmao said:
Just found the topic. Thanks a lot for working on this.
I got two Ares8 without sound due to the root process. I was able to find another unrooted table and followed the exact steps to backup the boot/recovery/system as in the first post.
However, after shutdown, my unrooted one will no longer boot. It got stuck at the next book logo screen for a few minutes, then reboot to this screen again. I could still get into the boatloader and the stock recovery, but what do I do now?
I also used the backup to restore one of my rooted Ares 8, before realizing this. It also wont even boot.
Click to expand...
Click to collapse
Reboot to what screen, I am not following you.
Upload your recovery and boot that you backed up.
They will be called
boot.emmc.win
recovery.emmc.win
Also a flashable rom has been upload for my version see post two, I still need your
boot.emmc.win
recovery.emmc.win
and exact details of what you did.
the boot.img needs to be modified, else it takes a while to boot cause by default the boot.img is force encrypted, in stock recovery do factory rest and in time the tablet will boot, cause it has to encrypt.
Sent from my Life_Max-FL using Tapatalk
Here are the files I backuped following the first post.
Once powered on, it will stay on the nextbook logo screen (also a line of text saying "Powered by android"). After a while, the screen will flash once ( that is hwy I thought it rebooted) then it goes into the stock recovery (the lying down android with the chest open) and I could go into the recovery by pressing power+ volume up.
The other tablet, restored using the backup, is the same situation.
minmao said:
Here are the files I backuped following the first post.
Once powered on, it will stay on the nextbook logo screen (also a line of text saying "Powered by android"). After a while, the screen will flash once ( that is hwy I thought it rebooted) then it goes into the stock recovery (the lying down android with the chest open) and I could go into the recovery by pressing power+ volume up.
The other tablet, restored using the backup, is the same situation.
Click to expand...
Click to collapse
That's not the recovery you gave me recovery.emmc.win.md5 I need recovery.emmc.win
anyway in stock recovery factory reset and you should be fine.
Android 10.0 version from HA/Dasaita for PX5 Head Units.
Enjoy
Download:
Fast --> Download
build.prop:
Code:
# 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
Root? )
-Monty- said:
Root? )
Click to expand...
Click to collapse
No Root at the moment for Android 10 MTCE Devices
1- What is the difference from HCT4, HLA and HA3?
2- My radio is dasaita but any of these 3 roms are compatible right?
3- all roms include day and night mode?
Regards.
JonatanP said:
1- What is the difference from HCT4, HLA and HA3?
2- My radio is dasaita but any of these 3 roms are compatible right?
3- all roms include day and night mode?
Regards.
Click to expand...
Click to collapse
1. Look at the screenshots. It's almost the UI.
2. Yes!
3. No. Only the MX/Witson ROM.
jamal2367 said:
1. Look at the screenshots. It's almost the UI.
2. Yes!
3. No. Only the MX/Witson ROM.
Click to expand...
Click to collapse
3. The dasaita rom have a night mode, if you have activate ngiht mode in your google acount with android 10 the googles app are all in night mode, also the seettings and others thinks. Don't have a day and night mode like Mx/witson with the launcher, music or bluetooth.
segu45 said:
3. The dasaita rom have a night mode, if you have activate ngiht mode in your google acount with android 10 the googles app are all in night mode, also the seettings and others thinks. Don't have a day and night mode like Mx/witson with the launcher, music or bluetooth.
Click to expand...
Click to collapse
That's what I meant.
jamal2367 said:
That's what I meant.
Click to expand...
Click to collapse
:good:
Screenshots
I installed it, tried it, it works well!
Here are some screenshots.
Doky1988 said:
I installed it, tried it, it works well!
Here are some screenshots.
Click to expand...
Click to collapse
Can you do me a favor? Can you extract the amp,file browser, Bluetooth and radio apks from this rom.
Guys sorry, can I install this on my px5 mtce_lm? Or is it better wait Android 10 from erisin/lm?
Francex10 said:
Guys sorry, can I install this on my px5 mtce_lm? Or is it better wait Android 10 from erisin/lm?
Click to expand...
Click to collapse
I installed HCT4 on my PX5 MTCE_LM.
Was A9. InstallModPro help me for upgrade to A10
Android 10 is very Good as well as GPS.
Can't install this update
Hi guys,
I have an RK3368 octa core PX5 device currently running Android 9. I've tried to install this update, but am getting an error. The process starts, but then the recovery screen appears. The sequence of messages reads :-
Verifying Update Package...
Update package verification took 46.2 s (result 0).
Installing update...
Target: rockchip/rk3368/blah blah blah
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")
E:Error in /mnt/usb_storage/update.zip (Status 7)
Installation aborted
I then need to reboot.
When I insert the USB card and the system picks up the update file, there is an option to format the device - I'm not selecting that. Do I need to tick the box to format the device ? Or does anyone have any ideas whet the issue might be ?
Thanks.
Archbishop666 said:
Hi guys,
I have an RK3368 octa core PX5 device currently running Android 9. I've tried to install this update, but am getting an error. The process starts, but then the recovery screen appears. The sequence of messages reads :-
Verifying Update Package...
Update package verification took 46.2 s (result 0).
Installing update...
Target: rockchip/rk3368/blah blah blah
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")
E:Error in /mnt/usb_storage/update.zip (Status 7)
Installation aborted
I then need to reboot.
When I insert the USB card and the system picks up the update file, there is an option to format the device - I'm not selecting that. Do I need to tick the box to format the device ? Or does anyone have any ideas whet the issue might be ?
Thanks.
Click to expand...
Click to collapse
You need the Android 10 recovery to install this.
You can find it here:
http://hal9k.ru/?page_id=207
Jamal,
Thanks - I've purchased the recovery tool, and upgraded successfully. Actually it was a breeze using the recovery tool, made it really easy !
Thanks again.
jamal2367 said:
You need the Android 10 recovery to install this.
You can find it here:
[l]
Click to expand...
Click to collapse
People can also try the upgrade to Android 9 or 10 using manufacturer free tools and the ROM .img file - an OTA ZIP wont work.
This is how the manufacturer does it.
See my thread.
---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------
Archbishop666 said:
Jamal,
Thanks - I've purchased the recovery tool, and upgraded successfully. Actually it was a breeze using the recovery tool, made it really easy !
Thanks again.
Click to expand...
Click to collapse
Also see thread regarding upgrading to Android 10 using free tools.
marchnz said:
People can also try the upgrade to Android 9 or 10 using manufacturer free tools and the ROM .img file - an OTA ZIP wont work.
This is how the manufacturer does it.
See my thread.
---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------
Also see thread regarding upgrading to Android 10 using free tools.
Click to expand...
Click to collapse
It doesn't work on any head unit.
jamal2367 said:
It doesn't work on any head unit.
Click to expand...
Click to collapse
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,
marchnz said:
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,
Click to expand...
Click to collapse
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.
jamal2367 said:
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.
Click to expand...
Click to collapse
When people have money, they will pay for what they like and feel the best, the easiest. For example, they like Rom Dasaita but do not have the img file, if using the free tool, they must download another img file of another company to install, then be able to install the rom with their favorite ota file. They pay for time wasted and spend that time to experience, to do other things and make more money for them, haha