Related
Please note that I gave up on this unit (MTCD PX5 units are so much nicer...). I will try to update this post (however infrequently) with information that may appear in this thread or come my way by other means, but I will not seek information actively and updates will no longer be from my own experience or experiments.
At the time of writing this head unit is available here and (probably) here. These are both custom fit for Kia Sorento, but other versions do exist; in particular several EONON units feature the same hardware configuration (model numbers GA2160, GA7153 GA7163, and I am sure others).
Hardware-wise this seems to be the same unit as described in this thread so many tricks therein will work for this unit. In particular the USB debugging password continues to be "[email protected]" (without quotes); the extra settings password is most likely either 123456 or 668811; the factory reset and developer options passwords appear to be both 7890.
In all the unit is an Allwinner quad core R16, with the MCU version 5.3.19-16-10-650101-161115 and System version V7.3.1-2016-11-12.100233_TW2. Here is the Droid Info report:
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20161112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20161112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 986 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
Software-wise the unit comes with a fairly stock version of Marshmallow, though as usual the operating system is a bit locked down (but to my surprise not too locked down) compared to stock.
The purpose of this thread is to gather information about the software and possible customization for these units. I have added the information I gathered from my experience and I will update this post with any new information I manage to obtain.
1. Partition dump
For reference I dumped all the partitions of my device. The dump is available here. The dump was done by name (for those partitions that have a name) and symlinks point to the device name from /dev/block. Feel free to share (credit appreciated but not necessary) and please share any information that you gather from it (which will be included in this section as it becomes available).
2. Flashing firmware
There are multiple ways of flashing new firmware, depending on the actual unit and also its state (working, bootloop, etc.). All methods require that the all the files (three to six) that contain said firmware (see next section) be placed in the root of a SD card formatted FAT32 and inserted in the GPS slot of the unit. Some reports of the firmware being flashed from a USB stick rather than the SD card also exist; they also mention that choosing one USB port over another might make the difference between success and failure.
On a working system inserting the card and/or USB stick and choosing "update system" from preferences will likely do the trick.
On a system that is not working the following methods have been reported:
Hold Home, press Reset, and keep holding Home until the update starts (thanks).
A hardware solution is to short Key 1 (steering wheel controls) to ground, then press and hold Reset for 10 seconds; release Reset and disconnect Key 1 when "update" is displayed (thanks).
Yet another procedure might be needed for some units (thanks): Using a USB stick prepared as above and inserted in the unit, turn ignition to ACC, press Reset, turn ignition off, then after 5 seconds turn it again to ACC. A video is also available.
3. Flashable firmware
All the reports I have seen indicate that all the firmware versions are interchangeable. However, a factory reset will be needed most of the time for full functionality, especially so when installing firmware from a different vendor. It is VERY important however to note that the file bd07a5ee-fbb0-11e4-ae78-000c29ba27c0 contains the MCU firmware and so SHOULD NOT be flashed on incompatible devices as doing so will brick the unit (thanks).
Partition 11 of the above dump in particular stores a flashable image. It contains the following files:
81cb828c-9b57-11e6-ad2a-df6786178d62
827ba428-9b57-11e6-8dfb-37398ea70e52.0
827ba428-9b57-11e6-8dfb-37398ea70e52.1
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
The files 827ba428-9b57-11e6-8dfb-37398ea70e52.* in particular when cat-ed together form an ext4 file system that appear to be a copy of the system partition. This 4pda forum thread contain more information (thanks @Ahfish22); I do not speak Russian at all but Google Translate does a good job most of the time.
Since I started this thread many people have posted many firmware versions. Here is a hopefully complete list. There might be duplicates and misses and I apologize for both in advance.
The following set of firmware (in particular V7.3.1_20170610.110122_KED1 therein) come recommended by several users (thanks).
EONON firmware:
GA2162_KBT2_20170309 (thanks)
V7.3.1_20170114.111256_KBT2 (thanks)
EONON-R16-20170509 (thanks)
EONON-R16-KLD20170515
V7.3.1_20170427.104257_KBT2 (thanks)
EONON-R16-KLD20170515 (thanks)
KED1 (MEDEKE?) firmware (thanks):
V7.3.1_20170216.180104_KED1
V7.3.1_20170720.152039_KED1
TW2 (TopWinner?) firmware (thanks):
V7.3.1_20170111.114952_TW2-IVT+ROOT+RADIO
V7.3.1_20161229.175327_TW2
V7.3.1_20161201.154419_TW2
TH6 firmware (thanks): V7.3.1_20161129.194710_TH6
JYZC1 (Joying?) firmware (thanks):V7.3.1_20170317.114203_JYZC1
Kaier firmware (thanks)
Rooted KLD (Klyde) firmware (thanks):V7.3.1_20170512.203736_KLD1-0-1-mod
4. Recovery
Mot units do have a working recovery partition, though some are reported not to have such. The command "reboot recovery" at a root prompt (terminal emulator or ADB) will enter recovery (if available).
Alternatively recovery can be reached with an external USB keyboard as follows: While holding Alt and Print Screen keep tapping i; the system will eventually restart in recovery (thanks pir8man) .
It should be noted that despite the on-screen instructions the stock recovery does not react to any buttons on the head unit, but works well with an external USB keyboard.
5. Customization
There are useful tweaks that come with the stock operating system including speed-dependent volume and (apparently, I have not tested exhaustively) the elimination of the full-screen keyboard.
I found this alternative to the stock radio app (context, source code) which is pretty nice except that the app force closes upon attempting to enter settings. If you speak Russian it may be worth discussing this with the developer.
Root: Kingoroot works, though several attempts (reboot and try again) may be needed. Note that a reliable Internet connection is needed during the whole process. I do not like the extra apps and intrusive ads that come with Kingoroot. I therefore recommend once rooted to install Chainfire's SUperSU, let it update the su binary, and then uninstall Kingoroot. Note however that the current Play Store SuperSU (namely, version 2.82) may not be able to overwrite Kingoroot's su (saying instead that "the su binary is occupied"). If this is the case you may want to try version 2.79 (downloadable from here) which is known to work. Once the Kingoroot's su binary is overwritten you can upgrade to the latest (Play Store) SuperSU.
Busybox: Installed without incidents using the usual installer from the Play Store.
Xposed: Installed using the Xposed installer v. 3.1.1 and works well. I tried Gravity Box and Xprivacy.
6. Outstanding issues
It should be possible to redefine the default apps for music, video, and radio but I did not find any way to do it.
Mapping SWC and front button panel events works to some degree (for testing purposes I mapped the "Band" button to the app drawer), but this seems to be exclusively at the mercy of the MCU, which only allows mapping to predefined actions. I could find no way to map these events to custom actions on the OS side. It was reported that button events are communicated to the OS as long as no MCU app is running. However, I was unable to reproduce this; for me no event is ever seen by the OS no matter how many (or how few) apps are running. I stopped all the MCU apps but even so KeyTest does not register any event.
Needless to say, no custom recovery (such as TWRP) exist for these units.
So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?
Can you share me the content of /sbin directory?
sambacha said:
So if the hardware is the same as the other 4.4.2 units then can we update our old units to 6.0?
Click to expand...
Click to collapse
If the hardware matches then I do not see why not. In addition to dd-ing the system and boot partitions of my dump (which you are welcome to try) please see my last edits of the first post for possible flashable firmware being available.
Just make sure that you have a (tested) way to get back if things do not work...
mrtnb said:
Can you share me the content of /sbin directory?
Click to expand...
Click to collapse
See attached.
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Alternative to the stock radio -- help needed
I found this alternative radio app (reference, source code). It works well but I am unable to set preferences as the app force closes on selecting the setting menu item.
I would ask the developer, except that I do not speak Russian. I was wondering if any Russian speaker around here could inquire about the issue. I have also downloaded the sources and I am poking around but I am not holding my breath until I find a solution (I am a coder but not an Android developer). Many thanks in advance!
sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you share your experience and the russian thread's link?
sambacha said:
Found a thread in the russian site about updating the older units that came with 4.4.2 to 6.0. I will give that a try later today and report back. I'm mostly concerned about it's native support to USB DAC's so I can finally stop change audio sources in my DSP every time I want to use any app other than UAPP.
EDIT: spoke too soon before reading the updates to the original post!
Click to expand...
Click to collapse
Can you give us a link?
---------- Post added at 07:40 AM ---------- Previous post was at 07:21 AM ----------
can I flash this over Android 4.4?
This is my unit:
Android 4.4.2 Operation System
CPU Processor: Allwinner R16 Cortex A9 Quad-core 1.6GHz
RAM Memory: Samsung DDR3 1GB/16GB
I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.
sbruda said:
[*]It would be great if long press events (SWC and/or front panel buttons) can be used. Some hints in various threads suggest that this is possible with these units but I found no way to do it. Advice is once more much appreciated.
Click to expand...
Click to collapse
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
If I get something new I'll post asap.
Hope this helps.
pir8man said:
I just installed an EONON GA2162. Link
Which appears to be a clone of the same..
MCU version: 5.3.19-108-10-943101-170114
System version: V7.3.1_20170114.111256_KBT2
Code:
DEVICE
Model: QuadCore-R16 (astar_d7)
Manufacturer: Allwinner
Baseband Version: Not Available
RIL Version: sw-dataonly-ril-for-6.0_v1.0
Build Number: astar_d7-eng 6.0.1 MOB30R 20170112 test-keys
Build Fingerprint: Allwinner/astar_d7/astar-d7:6.0.1/MOB30R/20170112:eng/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0.1)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 160 dpi (mdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 5 (v7l)
Board: exdroid
Chipset: sun8i
Cores: 4
Clock Speed: 480 MHz - 1200 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt
CPU Governor: Not Available
Kernel Version: 3.4.39
Kernel Architecture: armv7l
GRAPHICS
Renderer: Mali-400 MP
Vendor: ARM
OpenGL Version: OpenGL ES 2.0
RAM
Total: 836 MB
Java Heap: 80 MB
STORAGE
Internal: 12 GB
EXTERNAL: Not Detected
I can dump the rom if anyone desires.
Click to expand...
Click to collapse
could you please upload this rom for us
thanks man
me sumo al pedido
Saludos !
no se si alguien puede pero estaría bueno que puedan subir los packs de actualización. para R16 en la resolucion 1024*600
por ejemplo estos son los Nombres de los archivos que hacen falta...
tambien especificar el android si es 4.4 o 5.1 o 6.0
bd07a5ee-fbb0-11e4-ae78-000c29ba27c0
90436790-1e25-11e5-9b35-000c29ba27c0
91973a18-1e25-11e5-b937-000c29ba27c0
92e82e86-1e25-11e5-bffa-000c29ba27c0
khalwd said:
could you please upload this rom for us
thanks man
Click to expand...
Click to collapse
Hi,
(my first post):laugh:
I would also like to have a copy of this ROM.
I have the same Droid report.
Being someone that cant leave things alone i have somehow corrupted my unit.
I rooted with Kingoroot and all worked well. Uploaded a recovery to the cloud, all good.
Decided to down load back to the unit. Wife moves car and interrupts download.
Now when i boot up all i get is the car logo and the android screen, this is where it stops.
Tried installing various updates, They seem to install. Progress bar for abut 5 min shows update end
then boots to the car logo Android screen and stops.
Cheers
Hi,
pirulazul said:
Hi, I recently bought one of these for a Ford Mondeo and I somehow have figured about using keypress events.
The problem doesn't lie in the unit itself, but the damn apps it has.
I have been two entire days staring at Extreme Logcat screen and button event but no go, but, suddently, key event started registering next, prev and play/pause.
GREAT, I thought, and I started configuring Xposed Additions to start some audio visualizers in some buttons but when I started the music app, it stopped registering the events. It closed that app and those events where working again. Tried powerAmp and everything works like a charm. Menu and back keystrokes can also be mapped while the on-screen button still do the default action, so:
Click to expand...
Click to collapse
Thank you for the report. I tried the same (stop all system apps) but even so KeyTest does not register any event. This was done for the panel buttons since I do not have yet any SWC (the unit is on the bench), which may or may not be the cause of my failure.
pirulazul said:
- It seems like the built-in apps capture those events and prevent anyone (tasker, Xposed Additions) to use them.
- MP3 and video player can be replaced pretty easyly but radio and specially bluetooth manager (Which has a whooping 12 keys that can be customized (0-9, # and *)) cannot be replaced.
Click to expand...
Click to collapse
Have you found any way to replace the default association for these apps? By default the "Mode" action cycles through the default apps, did you find any way to convince this action to cycle through some other (custom) rotation?
pirulazul said:
- Decompiling the app, and disabling those captures could be the solution to use all those keystrokes OR finding some way to block those apps from capturing those events.
Click to expand...
Click to collapse
I'll try to look into this, but at this time I cannot promise any timeline.
Cheers!
would one of my units be similar to yours?
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...
zerozoneice said:
would one of my units be similar to yours?
Click to expand...
Click to collapse
Looks pretty much the same as mine (with a slightly newer firmware though).
zerozoneice said:
i received a newer firmware from the chinese (build 29.12) as a ZIP which contains the 4 files as above, but i can't update it since i get a signature error (seen below). In the meantime i managed to **** up the screen by accidentally switching to 800x480 and now i can't see anything useful on the display...
Click to expand...
Click to collapse
Most (all?) Chinese vendors know absolutely nothing about the units they sell so it is quite possible to have the wrong firmware. This, or the file got corrupted during transfer somehow. Have you tried my firmware blob or the others that float around? The probability that it will work look decent and what have you gotta loose?
You can also try to restore the resolution by trial and error (touching the screen where things should be). A couple of success stories have been posted in this thread though the process looks painful...
there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Trial & error...i would need to see another menu next to me in order to see where the hell i'm pressing on my screen
Resolution change is the first menu, but is hidden in the extra settings, behind a password which i'd also need to enter....blindly.
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
LE: LOL, i just read the following passage from the thread you posted above:
"What is the Extra Settings password?
Resolved: 123456
Note: Do NOT change the resolution of the head unit. You will destroy your unit. However it is reversible."
Post 807: another quickfinger like me, changed the res. the other way around, from 800 to 1200, but he still sees something....
https://forum.xda-developers.com/showpost.php?p=70762889&postcount=807
Post 747: same problem as me.
https://forum.xda-developers.com/showpost.php?p=70047172&postcount=747
How can i flash this damn unit? How can we connect to it?
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly... THX!
---------- Post added at 04:43 PM ---------- Previous post was at 04:15 PM ----------
HERE is the link to the FW that infidini support provided me.
zerozoneice said:
there are couple of FWs around, i saw them on 4PDA as well. The latest is february, something. The problem is that the ZIP file has the 4 files you listed above, instead of an IMG file. Shouldn't IMG be the default ROM update? I mean even PowerSuit recognizes only IMGs, that is if i manage to connect to the damn box somehow.
Click to expand...
Click to collapse
I believe that the four files can be used directly to upgrade, at least this is what people have reported (I have never tried to upgrade myself). This also makes sense given that a restore to factory from the (Android) menu will presumably use the partition with those files.
zerozoneice said:
I tried TV out, hoping the signal is ****ed only from the mainboard to the screen and it would manage to display it on another external screen, but....there is no TV out. Didn't work with the cables provided.
Click to expand...
Click to collapse
It would appear that TV out only works for the DVD.
zerozoneice said:
Did you manage to install any of the 4PDA firmwares properly on yours? Try the December 29th one, this is the one that Infidini sent me....
Click to expand...
Click to collapse
No, I meant to but I am really pressed for time nowadays so I have no idea when will I get to it.
zerozoneice said:
@sbruda: i have an idea. Can you please post screenshots of the menu, from the main menu screen all the way to the extra settings, where u enter the password and then the "change resolution" menu option? It can help me to figure my fingers around the screen blindly...
Click to expand...
Click to collapse
Here they are. Sorry for the crappy photos but I have no idea how to take screenshots on this unit (please advise):
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.
sbruda said:
1-main.jpg - main screen
2-notif.jpg - notifications pulled down (two times)
3-settings-scrolled.jpg - the settings app scrolled all the way down
4-car-settings-scrolled.jpg - the Car settings screen scrolled all the way down
5-settings-pass.jpg - the password entry box and keyboard (I would advise the use of a USB keyboard instead though)
6-extra-settings.jpg - the Extra setting screen
7-resolution.jpg - the resolution dialogue
I hope this helps. If somebody can advise on how to take screenshots I will come back with better quality photos.
Click to expand...
Click to collapse
thx, they're good enough. using phone is fine. afaik password for that extras in my case is 123456 and restore to factory settings 7890
i will try tomorrow.
---------- Post added at 07:32 PM ---------- Previous post was at 07:01 PM ----------
How do you power on the thing when not connected in the car???
HI Guys,
Im a newbie here. Posted about a month ago but no reply.
I wish I had found the threads and reviews about the seller before I purchased. Most un helpful
I have a few issues i will list. The last discussion with the seller was about updating firmware. He tells me there is an update but After several weeks of messaging him i have had no reply. I am now discussing with PAYPAL.
http://www.autostereo.com.cn
https://www.aliexpress.com/item/32965483853.html
https://www.ebay.co.uk/itm/283835207820
QUITE FRANKLY. The user interface is very basic and ugly. So looking for assistance to do something.
Wanting to know if the HU is able to be update on firmware or Rooted o think you call it. If so will need instruction, and I am happy to pay someone for this. PAYPAL or Bank Transfer.
OK so issues.
HU
MAIN ISSUE is SOMETIME Screen will Flash a line from top to bottom
1. ECU SPEED AND REVS.. NOT WORKING
( ECU CABLE IS CONNECTED) I
2. ANDROID AUTO… INTERMITTENT. TURNS ON OFF ON OFF ON OFF..
.......FIXED......
3. EASY CONNECT… INTERMITTENT TURNS ON OFF ON OFF ON OFF
FIXED
4. Phone connection AUDIO QUALITY IS TERRIBLE,, SO BAD I cannot hear caller.
In the package, there is the miccorphone, did you connect this?
FIXED
5. DOOR OPEN Shows Wrong side If Car door is open on Left Screen shows on right.
Setting-----user setting----right side
THIS IS FIXED
6. Need to be able to change the Startup Screen (Yellow Car) UGLY. Also Car that show up in PNG file.
CAN ONLY CHANGE BOIT LOGO TO MONDEO OR YELLOW SPORTS CAR
NO OPTION TO USE MY OWN LOGO
Some of these things are nothing major but for what i paid I expect it to work as it should.
Detail are
https://www.aliexpress.com/item/32965483853.html
4gb/64gb 13.6 Android9 13.6" Tesla style Car No DVD Player GPS Navigation For Ford Mondeo Fusion MK5 2017
Android Version 9
Security Patch April 5 2019
Basband Version Unknown
Kernel Version 4.4.167
#24 Thu Dec 26 09:36:21 CST 2019
Build number
rk3399-userdebug 9 PQ2A.190305.002.eng.work2.20191226.161648 test-keys
MCUVer: RL78c_NCHHWY_F047PB -CAN84
FrameworkVer: px6-userdebug 9 PQ2A.190305.002
eng.work2.20191226.161648 test-keys
OSVer: 9 Thu Dec 26 09:3621 CST 2019
APPVer: 200200113-1920x1030-9600chwy-edp
Nandflash: 50.42G/64.00G
RAM: 2G/4G
BTVer: SD_carplay_I2S_191230_sdk1.5
Barcode: ZF-1809X02020033229
Model rk3399
Serial Number
Any help appreciated.
JIMMYRECARD said:
HI Guys,
Im a newbie here. Posted about a month ago but no reply.
I wish I had found the threads and reviews about the seller before I purchased. Most un helpful
I have a few issues i will list. The last discussion with the seller was about updating firmware. He tells me there is an update but After several weeks of messaging him i have had no reply. I am now discussing with PAYPAL.
http://www.autostereo.com.cn
https://www.aliexpress.com/item/32965483853.html
https://www.ebay.co.uk/itm/283835207820
QUITE FRANKLY. The user interface is very basic and ugly. So looking for assistance to do something.
Wanting to know if the HU is able to be update on firmware or Rooted o think you call it. If so will need instruction, and I am happy to pay someone for this. PAYPAL or Bank Transfer.
OK so issues.
HU
MAIN ISSUE is SOMETIME Screen will Flash a line from top to bottom
1. ECU SPEED AND REVS.. NOT WORKING
( ECU CABLE IS CONNECTED) I
2. ANDROID AUTO… INTERMITTENT. TURNS ON OFF ON OFF ON OFF..
.......FIXED......
3. EASY CONNECT… INTERMITTENT TURNS ON OFF ON OFF ON OFF
FIXED
4. Phone connection AUDIO QUALITY IS TERRIBLE,, SO BAD I cannot hear caller.
In the package, there is the miccorphone, did you connect this?
FIXED
5. DOOR OPEN Shows Wrong side If Car door is open on Left Screen shows on right.
Setting-----user setting----right side
THIS IS FIXED
6. Need to be able to change the Startup Screen (Yellow Car) UGLY. Also Car that show up in PNG file.
CAN ONLY CHANGE BOIT LOGO TO MONDEO OR YELLOW SPORTS CAR
NO OPTION TO USE MY OWN LOGO
Some of these things are nothing major but for what i paid I expect it to work as it should.
Detail are
Android Version 9
Security Patch April 5 2019
Basband Version Unknown
Kernel Version 4.4.167
#24 Thu Dec 26 09:36:21 CST 2019
Build number
rk3399-userdebug 9 PQ2A.190305.002.eng.work2.20191226.161648 test-keys
MCUVer: RL78c_NCHHWY_F047PB -CAN84
FrameworkVer: px6-userdebug 9 PQ2A.190305.002
eng.work2.20191226.161648 test-keys
OSVer: 9 Thu Dec 26 09:3621 CST 2019
APPVer: 200200113-1920x1030-9600chwy-edp
Nandflash: 50.42G/64.00G
RAM: 2G/4G
BTVer: SD_carplay_I2S_191230_sdk1.5
Barcode: ZF-1809X02020033229
Model rk3399
Serial Number
Any help appreciated.
Click to expand...
Click to collapse
Hi, with this kind of radio you will never have zero issue. On the other side it can give flexibilty and a lot of things you cannot have on other autoradio.
- To set sometihing you can access the Factory menu (password 126). There you can set logo and others aspets. But please act carefully, and on your own risk. First of all do a config back-up: in Factory menu click the "Export" button; that will create a dmcu.cfg file; save it on an external drive.
-Moreover, you should learn the way you can enter the recovery on your own radio.
- Here you can find about a ROM mod:
https://forum.xda-developers.com/an...t/rom-hal9k-mod-v4-mtcd-e-head-units-t4046361
Anyway if your are not sitisfied, the issue you reported are enough to send back via paypal. I suggest to avoid mods, if you want follow that way.
Usually, the firmware updates that the sellers provide are MCU file (dmcu.img) - if you get, the seller will tell you also the way to install; it's different from ROM.
MediaTerraneo said:
Hi, with this kind of radio you will never have zero issue. On the other side it can give flexibilty and a lot of things you cannot have on other autoradio.
- To set sometihing you can access the Factory menu (password 126). There you can set logo and others aspets. But please act carefully, and on your own risk. First of all do a config back-up: in Factory menu click the "Export" button; that will create a dmcu.cfg file; save it on an external drive.
-Moreover, you should learn the way you can enter the recovery on your own radio.
- Here you can find about a ROM mod:
https://forum.xda-developers.com/an...t/rom-hal9k-mod-v4-mtcd-e-head-units-t4046361
Anyway if your are not sitisfied, the issue you reported are enough to send back via paypal. I suggest to avoid mods, if you want follow that way.
Usually, the firmware updates that the sellers provide are MCU file (dmcu.img) - if you get, the seller will tell you also the way to install; it's different from ROM.
Click to expand...
Click to collapse
Thank you. I will have a look at that.
MediaTerraneo said:
Hi, with this kind of radio you will never have zero issue. On the other side it can give flexibilty and a lot of things you cannot have on other autoradio.
- To set sometihing you can access the Factory menu (password 126). There you can set logo and others aspets. But please act carefully, and on your own risk. First of all do a config back-up: in Factory menu click the "Export" button; that will create a dmcu.cfg file; save it on an external drive.
-Moreover, you should learn the way you can enter the recovery on your own radio.
- Here you can find about a ROM mod:
https://forum.xda-developers.com/an...t/rom-hal9k-mod-v4-mtcd-e-head-units-t4046361
Anyway if your are not sitisfied, the issue you reported are enough to send back via paypal. I suggest to avoid mods, if you want follow that way.
Usually, the firmware updates that the sellers provide are MCU file (dmcu.img) - if you get, the seller will tell you also the way to install; it's different from ROM.
Click to expand...
Click to collapse
Interesting and thanks again.
It doesnt look difficult from what I have read. The only question I would have, Is it worth doing? Can I revert to OEM if it isnt what I want? Further Given the type of HU i have is this possible with the Dowload available or is it for a particular type? Mine is PX6 Android 9.0 from the factory. DOes it make any difference if its 13.6" screen?
But First and foremost I will work out how to get to recovery as you say.
Cheers again, your a good man.
JIMMYRECARD said:
Interesting and thanks again.
It doesnt look difficult from what I have read. The only question I would have, Is it worth doing? Can I revert to OEM if it isnt what I want? Further Given the type of HU i have is this possible with the Dowload available or is it for a particular type? Mine is PX6 Android 9.0 from the factory. DOes it make any difference if its 13.6" screen?
But First and foremost I will work out how to get to recovery as you say.
Cheers again, your a good man.
Click to expand...
Click to collapse
Hi,
It depends on your interest and your intention to dedicate time . In my opinion the @Hal9k_ ROM is a very intersting one.
Yes, you can go back to the original ROM, but you must have the file to do that. May be if you ask to @Hal9k_ , he could tell you more details about the possibility to go back to the OEM.
What makes differece among Head Units is:
- the Hardware model: you have a PX6, a good one
- the Brand, as it tells you the MCU (the low level firmware) you can use when updating it
- the screen size is not so important, but it must be a supported one
About entering recovery have a look https://www.youtube.com/watch?v=lPQgV_55Rkk&feature=youtu.be
It may depend on your specific Unit.
Cheers
Hi Experts,
In possession of a Pioneer Headnit which consists of a amplifier and seperate tablet SDA-8TAB.
Seems to run on a Allwinner A50 Soc and on Android 9. Would like to get root access but well known Rooting Apps do not work. Somebody can help? I captured some info from the tablet and by looking in the logs which were created when you re-install the tablet:
Manufacturer: worldchip
Model: SDA-8TAB
Brand: Pioneer
Board: exdroid
Device: SDA_8TAB
Hardware: sun8iw15p1
Platform: venus
Product: SDA_8TAB_XEEU5_EEA
Installed RAM: 2 GB
<<< CPU >>>
Core Architecture: 4x ARM Cortex-A7 @ 1800 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r0p5
CPU Cores: 4
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
AES: Not Supported
NEON: Supported
PMULL: Not Supported
SHA1: Not Supported
SHA2: Not Supported
<<< Android >>>
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-11-05
Codename: REL
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 256 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118
Tags: release-keys
Type: user
Google Play Services Version: 20.21.15 (100300-313409149)
hjdevries said:
Would like to get root access but well known Rooting Apps do not work.
Click to expand...
Click to collapse
It would be very helpful if you mentioned wich rooting apps you already tried. How would you otherwise get advice about other apps/options.
surfer63 said:
It would be very helpful if you mentioned wich rooting apps you already tried. How would you otherwise get advice about other apps/options.
Click to expand...
Click to collapse
Sure, thanks for the question, apps I tried:
Kingroot
Kingoroot
dr. Foneroot
RootGenius
P.S I don't want to install custom rom, only would like root access
hjdevries said:
Sure, thanks for the question, apps I tried:
Kingroot
Kingoroot
dr. Foneroot
RootGenius
P.S I don't want to install custom rom, only would like root access
Click to expand...
Click to collapse
Try Magisk. It is the universal rooting method.
You do need to know though how to flash a boot image, or how to dd write a boot image.
surfer63 said:
Try Magisk. It is the universal rooting method.
You do need to know though how to flash a boot image, or how to dd write a boot image.
Click to expand...
Click to collapse
Goedemiddag,
Yes I have read tutorials and I need TWRP with a custom file designed for my device, which I cannot find.
So Magisk is one step too far for the moment.
Any suggestion? Dank, HJ
hjdevries said:
Goedemiddag,
Yes I have read tutorials and I need TWRP with a custom file designed for my device, which I cannot find.
So Magisk is one step too far for the moment.
Any suggestion? Dank, HJ
Click to expand...
Click to collapse
Depending on the head unit you do not need TWRP, but I have no idea how your boot/recovery works.
Other tools are Superuser and SuperSU.
surfer63 said:
Depending on the head unit you do not need TWRP, but I have no idea how your boot/recovery works.
Other tools are Superuser and SuperSU.
Click to expand...
Click to collapse
What I did just now:
1. In developer settings Android allow to boot custom image
2. Downloaded MagiskManagere to tablet and chose the option to install ZIP automatically
3. Booted in Android recovery mode by holding down the power button and volume up button
4. I expected to get booted in a different screen than the stock Android one, see attachment.
Bootloader option just shows the Android puppet....with belly open
Am I doing something wrong?
I also surfed the web and found out that it's helpfull to have the stock factory rom from the device so that later on it can be flashed with root access.
But to get the stock rom you need root, which I am actually after. Or use TWRP but hey, they don't have rom for my device.
So basically stuck. Should I give up or is there a way, or perhaps I am doing something wrong?
hjdevries said:
I also surfed the web and found out that it's helpfull to have the stock factory rom from the device so that later on it can be flashed with root access.
But to get the stock rom you need root, which I am actually after. Or use TWRP but hey, they don't have rom for my device.
So basically stuck. Should I give up or is there a way, or perhaps I am doing something wrong?
Click to expand...
Click to collapse
Most units here are Chinese units. Actually there are only 4~5 Android/MCU manufaturers. All the brands you see are resellers of the hardware of these 4~5 resellers. You have a Pioneer. It might be identical to one of those manufacturers, but maybe also a pure Pioneer in-house development. That makes that it difficult for those Chinese head unut owners to help you.
But did you try this link? : http://howtoandroitroot.com/download/pioneer-sda-8tab
(I didn't follow it through)
surfer63 said:
Most units here are Chinese units. Actually there are only 4~5 Android/MCU manufaturers. All the brands you see are resellers of the hardware of these 4~5 resellers. You have a Pioneer. It might be identical to one of those manufacturers, but maybe also a pure Pioneer in-house development. That makes that it difficult for those Chinese head unut owners to help you.
But did you try this link? : http://howtoandroitroot.com/download/pioneer-sda-8tab
(I didn't follow it through)
Click to expand...
Click to collapse
Note to self for good tutorial, method 2. https://www.the***********.com/install-magisk-root-android-devices/
Need Stock root image.
The website you gave doesn't asllow me anything, however it shows options for all ANdroid which is strange, This tablet just came out.
Do you have somebody in your network who could help find that stock boot image looking at my first post with ingo, or contact me how to get it myself from the device perhaps?
Willing to donate of course.
I think I have almost the same unit as you .. I've been looking everywhere for the info about rooting and any available alternative roms ... Mine is a Xomax XM 2VA 757 ... pure allwinner but now you've answered a lot of my puzzles. Thanks
We have almost identical architectures .... and I have asked my vendor if they can find me an OTA type upgrade ROM for it .. I don't hold out much hope but I am trying.
Manufacturer: Allwinner
Model: QUAD-CORE
Brand: Allwinner
Board: exdroid
Device: venus-a3
Hardware: sun8iw15p1
Platform: venus
Product: venus_a3
Core Architecture: 4x ARM Cortex-A7 @ 1512 MHz
Instruction Set: 32-bit ARMv7
CPU Revision: r0p5
CPU Cores: 4 Cores
CPU Clock Range: 480 - 1512 MHz
Core 1 Clock: 1512 MHz
Core 2 Clock: 1512 MHz
Core 3 Clock: 1512 MHz
Core 4 Clock: 1512 MHz
Supported ABIs: armeabi-v7a, armeabi
Supported 32-bit ABIs: armeabi-v7a, armeabi
AES: Not Supported
NEON: Supported
PMULL: Not Supported
SHA1: Not Supported
SHA2: Not Supported
Screen Resolution: 1024 * 600
Screen Size: 155 mm × 86 mm
Screen Diagonal: 6.98 inches
Pixel Density: 170 dpi (mdpi)
xdpi / ydpi: 168 / 177 dpi
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
Refresh Rate: 59 Hz
Default Orientation: Landscape
OpenGL ES Version: 2.0
GPU Version: OpenGL ES 2.0 8c81e1f
Android Version: 9 (Pie)
API Level: 28
Android Security Patch Level: 2019-01-05
Rooted Device: No
Build ID: MCX.UI6_3.USER.BUILD.20201117-095320
Codename: REL
Fingerprint: Allwinner/venus_a3/venus-a3:9/PPR1.181005.003/20201117-095320:user/test-keys
Java Runtime Version: Android Runtime 0.9
Java VM Version: ART 2.1.0
Java VM Heap Size: 192 MB
Kernel Architecture: armv7l
Kernel Version: 4.9.118
Tags: test-keys
Type: user
Google Play Services Version: 21.09.15 (110302-361652764)
And we both live in the Netherlands !! I'm in Den Haag .. where are you ?
I just found anA50 firmware .. don't recognise the device though ...
Here ...
Heya. I have the same device. After a few weeks of research I managed to boot it into a firmware from another device (MultiLaser M7S Lite Oreo) using PhoenixCard. This means that I should be able to use IMGRePacker to extract it, then patch boot.fex with Magisk, flash that back onto the SD Card and from there on out, I should be able to backup the stock img from the internal nand, patch that and then flash it to the nand. I will keep y'all up to date with success/failures.
UPDATE 1: Boot.fex from MultiLaser Stock Firmware is patched and repacked into Firmware IMG. Flashing to SD Card right now.
UPDATE 2: Flashed SD Card with new boot.fex. Wouldn't boot. Will try flashing it with the option "Preserve force encryption" checked.
UPDATE 3: Just found out there are two bootloaders. One on the nand, and one on the SD. Obviously to boot the sd card with a patched img, I will need to unlock the bootloader. Edit: It won't boot to bl with button combo, I am assuming I will need to execute "adb reboot bootloader", so will be trying that.
UPDATE 4: The M7S ROM is booted and rooted baby!
snowlily said:
Heya. I have the same device. After a few weeks of research I managed to boot it into a firmware from another device (MultiLaser M7S Lite Oreo) using PhoenixCard. This means that I should be able to use IMGRePacker to extract it, then patch boot.fex with Magisk, flash that back onto the SD Card and from there on out, I should be able to backup the stock img from the internal nand, patch that and then flash it to the nand. I will keep y'all up to date with success/failures.
UPDATE 1: Boot.fex from MultiLaser Stock Firmware is patched and repacked into Firmware IMG. Flashing to SD Card right now.
UPDATE 2: Flashed SD Card with new boot.fex. Wouldn't boot. Will try flashing it with the option "Preserve force encryption" checked.
UPDATE 3: Just found out there are two bootloaders. One on the nand, and one on the SD. Obviously to boot the sd card with a patched img, I will need to unlock the bootloader. Edit: It won't boot to bl with button combo, I am assuming I will need to execute "adb reboot bootloader", so will be trying that.
UPDATE 4: The M7S ROM is booted and rooted baby!
Click to expand...
Click to collapse
hi,can you send the boot file?i have thepioneer and trying to root it
Lefteris Fragiadakis (Frago) said:
hi,can you send the boot file?i have thepioneer and trying to root it
Click to expand...
Click to collapse
Unfortunately I messed it up and accidentally flashed the internal boot partition with a magisk patched boot from the multilaser and now I have no way to obtain the original boot image. Though you can always check if the multilaser firmware is anywhere near stable on your device using phoenixcard. I'll see if I can find back where I got the flashfile in a bit and post here. Just make sure to use phoenixcard before actually flashing the tablet. This way you can know if it even boots and works in the first place, without risking a brick.
The download quota is exceeded. Imma find a way to download it and reupload it to Mega
i can read system if i take of emmc using ufi box but i dont want to lose guarentee,i also tried to find a boot to patch it with magisk but i didnt,i only want to root this pioneer
snowlily said:
Unfortunately I messed it up and accidentally flashed the internal boot partition with a magisk patched boot from the multilaser and now I have no way to obtain the original boot image. Though you can always check if the multilaser firmware is anywhere near stable on your device using phoenixcard. I'll see if I can find back where I got the flashfile in a bit and post here. Just make sure to use phoenixcard before actually flashing the tablet. This way you can know if it even boots and works in the first place, without risking a brick.
Click to expand...
Click to collapse
also maybe the pathced boot you have i can try to boot it on pioneer to see if this work
Hello !
I have trouble with bought alps device car head unit FF5000 (model 8227L).
System freezes, process com.ts.mainUI8 hanging not allowing to enter and listen any kind of music, dsp worked now just blinks and does nothing, buttons dont work as they are non existant (with SWC also), after car shutdown when HU shutsdown memory empties and resets data like date and time etc.
Can anyone help me bring this HU in order again ?
I don't know what to do anymore, it worked perfectly for three days and then in a sudden started problems.
I tried so far erasing data to factory default but problem still exist.
I will post system data on request... for now have this image of system :
MODEL: 8227L - android 8.1 (displays as Android 10) - patch from March 2019 alps/full_8227L_demo/8227L_demo:8.1.0/O11019/1550113051:userdebug/test-keys
HMI: TSKJ.C.Q.F3.C04.2020.27.08.30
MCU: JUST SAYS H BUT IT HAS ITS NUMBER CANT SEE IT
MEDIA: NULL - MUST BE SOMETHING HERE ASWELL
BTV: BT.19.11.12.1200 (mac ADDRESS)
CAN ANYONE HELP ME WITH THIS PLEASE TO UPGRADE/UPDATE DO SOME THING and turn this hu BACK in life ?
Help with Alps FF-5000 Android 10
I am also interested in this topic, I have the same unit and I would like to get the original Android 10 Firmware, since I changed it for a lower one, if someone knows how to Root this model, it could help us both.
I have a full backup of boot_1 boot_2 and emmc_user partitions. It’s for 2g-32g model 8227l
It’s fake android 10 with api27 which is 8.1 Oreo if that helps
Includes SU binary that’s not hampered from factory. Eonon had SU binary but was not functional per se.
nolimitzr2 said:
I have a full backup of boot_1 boot_2 and emmc_user partitions. It’s for 2g-32g model 8227l
It’s fake android 10 with api27 which is 8.1 Oreo if that helps
Includes SU binary that’s not hampered from factory. Eonon had SU binary but was not functional per se.
Click to expand...
Click to collapse
Well, you would do me a great favor if you would provide them to me. I write to you privately.
ALPS FF5000 model 8227L
Javierlopcast said:
I am also interested in this topic, I have the same unit and I would like to get the original Android 10 Firmware, since I changed it for a lower one, if someone knows how to Root this model, it could help us both.
Click to expand...
Click to collapse
I SOLVED MY PROBLEM WITH THIS DEVICE
It was GPS antenna. Its interference or faulty receiver loses MCU settings in memory. Once disconnected all turns normal.
Do the following :
- diconnect gps antenna
- disconnect radio antenna and then reconnect while ignition is on (gps antenna disconnected)
- turn ignition off, press button reset while turning ignition key, release reset and wait for device reseting
- adjust device settings again and enjoy the music !
+ get a new gps antenna !
:good:
FOR SOFTWARE UPDATES PLEASE CONTACT YOUR SELLER OR download from :
(I assume that yours is android 8.1 - upgraded to android 10)
https://yadi.sk/d/umCvHqCDzHccr
!!! PLEASE TAKE NOTE THAT YOU MUST CHOOSE THE RIGHT MCU AND SOFTWARE !!!
ALPS FF5000 model 8227L
nolimitzr2 said:
I have a full backup of boot_1 boot_2 and emmc_user partitions. It’s for 2g-32g model 8227l
It’s fake android 10 with api27 which is 8.1 Oreo if that helps
Includes SU binary that’s not hampered from factory. Eonon had SU binary but was not functional per se.
Click to expand...
Click to collapse
Hello, do not intermix al softwares in order to get device working !
Download and install with usb/SD card : https://yadi.sk/d/umCvHqCDzHccr
IF THIS LINK IS NOT HELPING YOU....
I'M UPLOADING MY SOFTWARE FOR AC8227L DEVICE THAT MY SELLER PROVIDED ME :
https://drive.google.com/file/d/1Ta2vL7Fc8tWmzmRxaJ-JMYGmlYYnRmud/view?usp=sharing
- it is CHS_8227_8_UI4_Android10_ver3_2019
After install use skin changer or launchers from page 14 !
Cheers to all !
ALPS FF5000 model 8227L
Javierlopcast said:
I am also interested in this topic, I have the same unit and I would like to get the original Android 10 Firmware, since I changed it for a lower one, if someone knows how to Root this model, it could help us both.
Click to expand...
Click to collapse
You don't need to root anything just update software (if not already wiped out).
Download and install in device thru USB / SD CARD :
https://drive.google.com/file/d/1Ta2vL7Fc8tWmzmRxaJ-JMYGmlYYnRmud/view?usp=sharing
thank you very much! Do you have a screenshot of how the Launcher looks like?
Reboot problem
I have installed the one sent to me by @antonTNTand it works, but every time I turn on the unit, after 10 seconds a window appears with a countdown and two options, "cancel" or "update" and the system restarts automatically, and it starts in "usb detected" mode while the pen drive is unplugged, it is quite annoying since it delays the start of the unit every time I get in the car.
https://ibb.co/6P80pDP
ALPS FF5000 model 8227L
Javierlopcast said:
I have installed the one sent to me by @antonTNTand it works, but every time I turn on the unit, after 10 seconds a window appears with a countdown and two options, "cancel" or "update" and the system restarts automatically, and it starts in "usb detected" mode while the pen drive is unplugged, it is quite annoying since it delays the start of the unit every time I get in the car.
https://ibb.co/6P80pDP
Click to expand...
Click to collapse
Turn your usb stick or SD card with software back in port... Then when boots up just click on update. If window not removed after update, go to main menu with password 8888 and find others menu or the one in which to set all settings for device and declick one for updates/software/firmware.
Or maybe usb or SD card with software in it is just stuck in memory and android detects update and wishes to install. If this is the case, unplug usb /SD card clicking on usb icon on lcd and then press eject and then safely remove stick.
Keep me updated will help you out.
Anton TNT said:
Turn your usb stick or SD card with software back in port... Then when boots up just click on update. If window not removed after update, go to main menu with password 8888 and find others menu or the one in which to set all settings for device and declick one for updates/software/firmware.
Or maybe usb or SD card with software in it is just stuck in memory and android detects update and wishes to install. If this is the case, unplug usb /SD card clicking on usb icon on lcd and then press eject and then safely remove stick.
Keep me updated will help you out.
Click to expand...
Click to collapse
I already found the problem, it had the .BIN files copied to the root of the internal memory of the radio, and every time it is turned on it detects them and restarts in USB reading mode. I deleted them and the problem is over
Would someone please send license.dat file, my headunit saya it's not activated after I upgraded firmware?
ALPS FF5000 model 8227L
ashensii said:
Would someone please send license.dat file, my headunit saya it's not activated after I upgraded firmware?
Click to expand...
Click to collapse
You don't need one it will generate automatically when installed software that matches your device and mcu.
Look for software on links that I pinned here in posts, or try find and install the correct one here :
https://yadi.sk/d/umCvHqCDzHccr
NOTE: if your device is not ALPS 5500 then you must follow posts for links that matcgh your device !
Anton TNT said:
You don't need one it will generate automatically when installed software that matches your device and mcu.
Look for software on links that I pinned here in posts, or try find and install the correct one here :
https://yadi.sk/d/umCvHqCDzHccr
NOTE: if your device is not ALPS 5500 then you must follow posts for links that matcgh your device !
Click to expand...
Click to collapse
Well I did code 9191 which clears license code afaik. I installed fw that you uploaded, it went well but still my headunit says activation file not found. But atleast my volume button.(knob) is working now with that fw. Fm freq is restricted to under.90 mhz, but if you are quick enough, you can save bigger frequencies aswell.
My hu is alps 8227l ff-5000, bought from aliexpress, seller claimed it to be hizpo branded but there is no hizpo logo anywhere in frame.
Anton TNT said:
You don't need one it will generate automatically when installed software that matches your device and mcu.
Look for software on links that I pinned here in posts, or try find and install the correct one here :
https://yadi.sk/d/umCvHqCDzHccr
NOTE: if your device is not ALPS 5500 then you must follow posts for links that matcgh your device !
Click to expand...
Click to collapse
I found license.dat from 4pda and with fw you provided all my problems are solved. Thank you.
ashensii said:
I found license.dat from 4pda and with fw you provided all my problems are solved. Thank you.
Click to expand...
Click to collapse
Well glad I could help in some way.... Hit the thanks meter if helped...
hi guys sorry to jump in but I am not finding or getting any help. I think I to reflash my device but cant find a download anyware and NOT getting any help from seller,
please can anyone (HELP) me in finding this software or even an upgraded version
Kirinavi
Android: YT9216CH_AHD_00005_V004_HIFI
Android os: Android 9.1
XY AUTO: B6.2 (X2)
CAN Pro: BNR-OLD English high with-V2.20.9-connect
DDR: 2g FLASH: 32GB
cpu A7 1.3GHz x4
Amplifier AC7315 MOS bile duct 50W X 4
display 1024*768( 6 bits)
MCU: 3.5 (X2)
kernal 4.14.116 (gcc version 6.3.1 20170404 linaro GCC 6.3-2017.05 ) ) [email protected] #12
sheerness said:
hi guys sorry to jump in but I am not finding or getting any help. I think I to reflash my device but cant find a download anyware and NOT getting any help from seller,
please can anyone (HELP) me in finding this software or even an upgraded version
Kirinavi
Android: YT9216CH_AHD_00005_V004_HIFI
Android os: Android 9.1
XY AUTO: B6.2 (X2)
CAN Pro: BNR-OLD English high with-V2.20.9-connect
DDR: 2g FLASH: 32GB
cpu A7 1.3GHz x4
Amplifier AC7315 MOS bile duct 50W X 4
display 1024*768( 6 bits)
MCU: 3.5 (X2)
kernal 4.14.116 (gcc version 6.3.1 20170404 linaro GCC 6.3-2017.05 ) ) [email protected] #12
Click to expand...
Click to collapse
Hi, please, this is forum for ALPS 5000 8227L device only try to put your search for right device
I can help you out with this, can I get some info where this kirinavi is bought ? Ali Express?
And can I get screenshot of device settings (MCU, media, bluetooth, device model, real android version of device etc.) - go to infotainment or similar settings menu and put screenshots.
Anton TNT said:
Hi, please, this is forum for ALPS 5000 8227L device onlčy try to put your search for right device
I can help you out with this, can I get some info where this kirinavi is bought ? Ali Express?
And can I get screenshot of device settings (MCU, media, bluetooth, device model, real android version of device etc.) - go to infotainment or similar settings menu and put screenshots.
Click to expand...
Click to collapse
"THANK YOU SOOOO MUCH"
for getting back to me, i have tried for months to try and get some help with this and you are the only one that has got back to me!...
yes i did get the system from aliexpress but not getting help from them since they have had the money,
i think i have added the pics to this, if there is anymore info you are needing please let me know,
again thank you so much :angel:
ANDROID:202211081700 (4G) 12 (fake 10)
MCU:MLO-mtk_C56_whe02d-aAaAaA_473X-CC568091-8A 20221221
Model: A007_C56_HA11_U859-EN-D_2022-11-08-1652
Octo 2.2Ghz 128GB+8GB 4G LTE on board.
Recently bought this headunit from Alli. It is a very quick unit although it comes with a lot of behind the scenes bloat and I have so far been unable to root and ADB does not work.
My main problem is an app called TXZ VOICE. It is interfering with android assistant. It is installed as a system app and I am unable to remove or disable it. As is the case with many of the other bloat apps.
I guess I'll have to wait for the community to pick it up. But what little information I have learned is the factory code 99992. A testing mode that appears to have an ADB shell, however it will not remove or disable apps.
Any insight would be greatly appreciated
If an ADB shell is provided, then check device's system file build.prop for the follwing entries
ro.build.type=userdebug
ro.debuggable=1
ro.secure=0
Click to expand...
Click to collapse
to check whether you can debloat Android or not.
jwoegerbauer said:
If an ADB shell is provided, then check device's system file build.prop for the follwing entries
to check whether you can debloat Android or not.
Click to expand...
Click to collapse
Thank you for the reply.
ro.build.type=userdebug
ro.debuggable=1
ro.secure=1
So I guess there's the answer.
The bootloader does seem to be unlocked however. I think there is a custom bootloader installed but I can't access it.
A device's bootloader ( Linux kernel ) and device's Android OS are totally different things.
If I understood it well then you want to debloat Android OS: this gets done via ADB ( read: Android Debug Bridge ).
Yeah. I was just adding any information I know about this headunit. My hope is perhaps it may be possible to flash new firmware in the future.