Hi, sorry I'm new to all of this Android head unit things.
I just got a Evo X with a android head unit, and from what I can tell it's not up to date.
Some apps don't seam to work correctly, so I want to make an update to the system.
Can someone give me some information about where to download the file and how to update everything?
Here is every info I have and some pics:
Model: px5 (1024x600) A-MEDIA AUTO
Kernel: 4.4.93+ [email protected] #130
Android version: 8.0.0
MCU Version: MTCE_HA_V2.75_1
Build number: px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180305.135439 test-keys
Img1 hosted at ImgBB
Image Img1 hosted in ImgBB
ibb.co
Img2 hosted at ImgBB
Image Img2 hosted in ImgBB
ibb.co
Img3 hosted at ImgBB
Image Img3 hosted in ImgBB
ibb.co
Img4 hosted at ImgBB
Image Img4 hosted in ImgBB
ibb.co
Img5 hosted at ImgBB
Image Img5 hosted in ImgBB
ibb.co
Img6 hosted at ImgBB
Image Img6 hosted in ImgBB
ibb.co
Img7 hosted at ImgBB
Image Img7 hosted in ImgBB
ibb.co
Img8 hosted at ImgBB
Image Img8 hosted in ImgBB
ibb.co
StephenGrosjean said:
Hi, sorry I'm new to all of this Android head unit things.
I just got a Evo X with a android head unit, and from what I can tell it's not up to date.
Some apps don't seam to work correctly, so I want to make an update to the system.
Can someone give me some information about where to download the file and how to update everything?
Here is every info I have and some pics:
Model: px5 (1024x600) A-MEDIA AUTO
Kernel: 4.4.93+ [email protected] #130
Android version: 8.0.0
MCU Version: MTCE_HA_V2.75_1
Build number: px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180305.135439 test-keys
Img1 hosted at ImgBB
Image Img1 hosted in ImgBB
ibb.co
Img2 hosted at ImgBB
Image Img2 hosted in ImgBB
ibb.co
Img3 hosted at ImgBB
Image Img3 hosted in ImgBB
ibb.co
Img4 hosted at ImgBB
Image Img4 hosted in ImgBB
ibb.co
Img5 hosted at ImgBB
Image Img5 hosted in ImgBB
ibb.co
Img6 hosted at ImgBB
Image Img6 hosted in ImgBB
ibb.co
Img7 hosted at ImgBB
Image Img7 hosted in ImgBB
ibb.co
Img8 hosted at ImgBB
Image Img8 hosted in ImgBB
ibb.co
Click to expand...
Click to collapse
You could do a factory reset and see if that fixes any issues. As for updating the Android Version it may or may not be possible, not without issues, due to hardware (BT and Wi-Fi )/driver incompatibility.
There is plenty of info on upgrading to the next version of Android.
This is the Dasaita website with all updated firewares.
Firmwares | Dasaita
Warm Notice: If your system is working well, please do not upgrade it !!!Because the upgrade is risky, it might lead to CRASH, BLACK SCREEN, OR SYSTEM ERROR; Unless there is a major bug in the car system, it unable to be used normally. At this time, you can choose to upgrade the system to...
www.dasaita.com
Related
Integrated all program and widget....
https://rapidshare.com/files/767778485/bada.rar
link showing 0 size and blank
Rapidshare Link seems not valid, NO download possible.
Please, fix it.
Thanx in advance.
Best Regards
Edit 1.
Code:
File not found. (e029a7af)
Blub...
I can not download this file...
French
Code:
Télécharger
Nom du fichier: bada.rar
Taille du fichier: [B]0.00[/B] MB
Type de fichier: rar
Lien de téléchargement: Facebook Twitter Google+
[B]Fichier introuvable.[/B]
English
Code:
Download
Filename: bada.rar
File size: 0.00 MB
File type: rar
Download link: Facebook Twitter Google+
[B]File not found[/B].
Please, check Link again... and please fix this.
Thanx in advance.
Best Regards
Download for Official
info:
KINZIE_RETLA_DS_7.0_NPKS25.200-12-9_cid12_subsidy-DEFAULT_CFC.xml.zip
Size: 1593961437 bytes
MD5: F82F782C664FC6F239A27E0BC887E08C
SHA1: 94112F27AE85BFDF8F8C648AB1B17A3E1E22784F
CRC32: 5B2EB7FE
access denied...I'm looking for RETMX 7.0 can you help me?
alternative link:
https://androidfilehost.com/?fid=745849072291694796
I am looking for the N108.zip file in particular as flashing custom roms require you to start from a clean up-to-date official base. If anyone has this file downloaded from the original Nextbit server, please share your hash.
You can use 7-Zip to generate a list of hashes:
Right click the file.
Pick CRC SHA.
Pick * (or just SHA-256) and post the result.
Feel free to post multiple hashes of all the Nextbit downloads you might still have. This helps verify if files downloaded from other servers might have been tempered with or not. With operating systems on any device, this is rather crucial.
Thanks in advance.
This is what I have right now from an unofficial source.
Name: Phone_Nextbit_USB_Driver_v1.0.1.msi
Size: 3801600 bytes (3712 KiB)
CRC32: 3FBA7C07
CRC64: 2663D5BD6EE42494
SHA256: 2B3CB2B354BB083A04C51F37D5F7EB1381F1611FE6D544112E00CF264C9DF585
SHA1: 6A6F91F6B4A1C736526AEA1FD13CD08FEF520776
BLAKE2sp: 2CB812ACC8F4FDF12258932265BE757E78AB2C66C7FC1A74A0A3F8D56CED5957
Click to expand...
Click to collapse
Name: N108.zip
Size: 1347268089 bytes (1284 MiB)
CRC32: 5A8C4B70
CRC64: FA8E972A82D4669C
SHA256: CEEB173233E22064BD420C2229FF3F5C8810CAD87F0DE7A01BBD51689E34F8C8
SHA1: B8846F9C0E5B6436E16A33C905F574B7AAC30DF3
BLAKE2sp: 6339B688B4CCBAC721EE9BD299634ACC0BD52AD908AE0B404CEBE4B0215A970D
Click to expand...
Click to collapse
Dear Developers.
A year ago, my Wileyfox Swift device, which was turned off and connected to the cable to charge, did not turn on when I checked again.
On the grounds that the problem is not in the hardware, an attempt was made to install a rom on the phone with different software download systems, but it was unsuccessful.
Right now, when trying to install ROM on the phone, it gives the following error.
Code:
Programmer Path:<Maincode>\prog_emmc_firehose_8916.mbn
Start Download
Program Path:<Maincode>\prog_emmc_firehose_8916.mbn
***** Working Folder:<AppData>\Roaming\Qualcomm\QFIL\COMPORT_3
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: '<Program Files (x86)>\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: <AppData>\Roaming\Qualcomm\QFIL\COMPORT_3
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: <Maincode>\prog_emmc_firehose_8916.mbn
15:44:30: <Maincode>\prog_emmc_firehose_8916.mbn"
15:44:30: 85224 bytes transferred in 0.063000 seconds (1.2901MBps)
15:44:30: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
15:44:30: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:16384 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:<AppData>\Roaming\Qualcomm\QFIL\COMPORT_3
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
15:44:35: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
<Program Files (x86)>\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM3 --sendxml=rawprogram_unsparse.xml --search_path=<Maincode> --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
15:44:35: INFO: Current working dir (cwd): <AppData>\Roaming\Qualcomm\QFIL\COMPORT_3\
15:44:35: INFO: Showing network mappings to allow debugging
15:44:37: INFO:
15:44:37: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
15:44:37: INFO: Looking for file 'rawprogram_unsparse.xml'
15:44:39: INFO: User wants to talk to port '\\.\COM3'
15:44:39: INFO: Took 0.00000000 seconds to open port
15:44:39: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
15:44:39: INFO: If you don't want this, use --dontsorttags
15:44:39: INFO: Looking for file 'sbl1.mbn'
15:44:39: INFO: Looking for file 'sbl1.mbn'
15:44:39: INFO: Looking for file 'emmc_appsboot.mbn'
15:44:39: INFO: Looking for file 'emmc_appsboot.mbn'
15:44:39: INFO: Looking for file 'rpm.mbn'
15:44:39: INFO: Looking for file 'rpm.mbn'
15:44:39: INFO: Looking for file 'tz.mbn'
15:44:39: INFO: Looking for file 'tz.mbn'
15:44:39: INFO: Looking for file 'hyp.mbn'
15:44:39: INFO: Looking for file 'hyp.mbn'
15:44:39: INFO: Looking for file 'devinfo.bin'
15:44:39: INFO: Looking for file 'dummy.bin'
15:44:39: INFO: Looking for file 'dummy.bin'
15:44:39: INFO: Looking for file 'misc.img'
15:44:39: INFO: Looking for file 'splash.img'
15:44:39: INFO: Looking for file 'oem_1.img'
15:44:40: INFO: Looking for file 'NON-HLOS.bin'
15:44:40: INFO: Looking for file 'fs_image.tar.gz.mbn.img'
15:44:40: INFO: Looking for file 'sec.dat'
15:44:40: INFO: Looking for file 'boot.img'
15:44:40: INFO: Looking for file 'system_1.img'
15:44:40: INFO: Looking for file 'system_2.img'
15:44:40: INFO: Looking for file 'system_3.img'
15:44:40: INFO: Looking for file 'system_4.img'
15:44:40: INFO: Looking for file 'system_5.img'
15:44:40: INFO: Looking for file 'system_6.img'
15:44:40: INFO: Looking for file 'system_7.img'
15:44:40: INFO: Looking for file 'system_8.img'
15:44:41: INFO: Looking for file 'system_9.img'
15:44:41: INFO: Looking for file 'system_10.img'
15:44:41: INFO: Looking for file 'system_11.img'
15:44:41: INFO: Looking for file 'system_12.img'
15:44:41: INFO: Looking for file 'system_13.img'
15:44:41: INFO: Looking for file 'system_14.img'
15:44:41: INFO: Looking for file 'system_15.img'
15:44:41: INFO: Looking for file 'system_16.img'
15:44:41: INFO: Looking for file 'system_17.img'
15:44:41: INFO: Looking for file 'system_18.img'
15:44:41: INFO: Looking for file 'system_19.img'
15:44:41: INFO: Looking for file 'system_20.img'
15:44:41: INFO: Looking for file 'system_21.img'
15:44:41: INFO: Looking for file 'recovery.img'
15:44:41: INFO: Looking for file 'persist_1.img'
15:44:41: INFO: Looking for file 'cache_1.img'
15:44:41: INFO: Looking for file 'cache_2.img'
15:44:41: INFO: Looking for file 'cache_3.img'
15:44:41: INFO: Looking for file 'cache_4.img'
15:44:41: INFO: Looking for file 'userdata_1.img'
15:44:42: INFO: Looking for file 'userdata_2.img'
15:44:42: INFO: Looking for file 'userdata_3.img'
15:44:42: INFO: Looking for file 'userdata_4.img'
15:44:42: INFO: Looking for file 'userdata_5.img'
15:44:42: INFO: Looking for file 'userdata_6.img'
15:44:42: INFO: Looking for file 'userdata_7.img'
15:44:42: INFO: Looking for file 'userdata_8.img'
15:44:42: INFO: Looking for file 'userdata_9.img'
15:44:42: INFO: Looking for file 'userdata_10.img'
15:44:42: INFO: Looking for file 'userdata_11.img'
15:44:42: INFO: Looking for file 'userdata_12.img'
15:44:42: INFO: Looking for file 'userdata_13.img'
15:44:42: INFO: Looking for file 'userdata_14.img'
15:44:42: INFO: Looking for file 'userdata_15.img'
15:44:42: INFO: Looking for file 'userdata_16.img'
15:44:42: INFO: Looking for file 'userdata_17.img'
15:44:42: INFO: Looking for file 'userdata_18.img'
15:44:42: INFO: Looking for file 'userdata_19.img'
15:44:42: INFO: Looking for file 'userdata_20.img'
15:44:42: INFO: Looking for file 'userdata_21.img'
15:44:42: INFO: Looking for file 'userdata_22.img'
15:44:42: INFO: Looking for file 'userdata_23.img'
15:44:42: INFO: Looking for file 'userdata_24.img'
15:44:42: INFO: Looking for file 'userdata_25.img'
15:44:42: INFO: Looking for file 'userdata_26.img'
15:44:42: INFO: Looking for file 'userdata_27.img'
15:44:42: INFO: Looking for file 'userdata_28.img'
15:44:42: INFO: Looking for file 'userdata_29.img'
15:44:42: INFO: Looking for file 'userdata_30.img'
15:44:42: INFO: Looking for file 'userdata_31.img'
15:44:42: INFO: Looking for file 'userdata_32.img'
15:44:42: INFO: Looking for file 'userdata_33.img'
15:44:42: INFO: Looking for file 'userdata_34.img'
15:44:42: INFO: Looking for file 'userdata_35.img'
15:44:42: INFO: Looking for file 'userdata_36.img'
15:44:42: INFO: Looking for file 'userdata_37.img'
15:44:42: INFO: Looking for file 'userdata_38.img'
15:44:42: INFO: Looking for file 'userdata_39.img'
15:44:42: INFO: Looking for file 'userdata_40.img'
15:44:42: INFO: Looking for file 'userdata_41.img'
15:44:42: INFO: Looking for file 'userdata_42.img'
15:44:42: INFO: Looking for file 'userdata_43.img'
15:44:42: INFO: Looking for file 'userdata_44.img'
15:44:42: INFO: Looking for file 'userdata_45.img'
15:44:42: INFO: Looking for file 'userdata_46.img'
15:44:42: INFO: Looking for file 'userdata_47.img'
15:44:42: INFO: Looking for file 'userdata_48.img'
15:44:42: INFO: Looking for file 'userdata_49.img'
15:44:43: INFO: Looking for file 'gpt_main0.bin'
15:44:43: INFO: Looking for file 'gpt_backup0.bin'
15:44:43: INFO:
Total to be tansferd with <program> or <read> is 673.85 MB
15:44:43: INFO: Sending <configure>
15:44:43: INFO: TARGET SAID: 'Host's payload to target size is too large'
15:44:43: INFO: TARGET SAID: '[email protected] [email protected]'
15:44:43: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 16384
15:44:43: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 16384
15:44:43: INFO: Target returned NAK for your <configure> but it does not seem to be an error. This is ok, fh_loader.exe attributes updated
15:44:43: INFO: In handleProgram('sbl1.mbn')
15:44:43: INFO: Looking for file 'sbl1.mbn'
15:44:43: INFO: =======================================================
15:44:43: INFO: {<program> FILE: '<Maincode>\sbl1.mbn'}
15:44:43: INFO: {<program> (247.07 KB) 495 sectors needed at location 131072 on LUN 0}
15:44:43: INFO: =======================================================
15:44:43: INFO: TARGET SAID: '[email protected] [email protected]'
15:44:43: INFO: TARGET SAID: 'start 131072, num 495'
15:44:43: INFO: FILE ACCESS SLOW!! 247.50 KB in 0.015 seconds ( 16.11 MBps) --- Overall to target 0.047 seconds (5.14 MBps)
15:44:43: INFO: {percent files transferred 0.04%}
15:44:43: INFO: TARGET SAID: 'Write failed Sector 131072, Errno 14'
15:44:43: INFO: TARGET SAID: 'Finished sector address 131072'
Download Fail: FireHose Fail: FHLoader Fail: Process fail
Finish Download
Of course the device does not respond at all with key combinations. There is also no response on Get Flash Information from device with software other than Qualcomm Flash Image software.
Can you help on the subject? Thank you in advance!
***
Some useful information.
* Serial code and OEM Hash Pack Locks can readable.
* It gives No Storage Drive Number error in Partition Manager operation.
* Device shows itself as MSM8909.
20220903-193650 hosted at ImgBB
Image 20220903-193650 hosted in ImgBB
ibb.co
20220903-193646 hosted at ImgBB
Image 20220903-193646 hosted in ImgBB
ibb.co
20220903-193642 hosted at ImgBB
Image 20220903-193642 hosted in ImgBB
ibb.co
Or at least change the icon so it doesn't look like a missed call
Bootloader is unlocked. Thx