Database Users

what have i bought...

Hello, bought a cheap and cheerful "Android 7.1" head unit off eBay (link). It has a 1.6 quad core, 1Gb RAM, 16Gb Internal Storage.
From 'Settings':
ARM Version: 16.08.08_V00I
MCU Version: 17.10.28_01_13M
The settings are very locked down, I cannot access 'About device' so have used an app called 'About Device' to find this so far:
Device model: mid1008l_emmc
Android Version: Lollipop_MR1 7.1 (so not Android 7.1....)
Build: LMY47I
Build Host: YLD (not sure what this is)
Hardware: MT8127
It doesn't have a SD slot that i can see...
I've managed to get the 'Factory Setting' password from the seller, which is 44320, but will only let me set steering wheel controls and startup logo.
can anyone tell me what type of device this is? Hui Fei? MTC/MTCC/MTCB?
thanks for any help :good:
Will

This seems to be the same spec http://4pda.ru/forum/index.php?showtopic=841385&st=140

@mugglesquop
How bizarre. I have exactly the same unit (except the one you have linked to has buttons down the side. Mine doesn't) I installed it into my RangeRover p38. It's a great unit for the price and does pretty much everything i want.
I've searched high and low for information about the unit but haven't come up with much except this ----> http://specdevice.com/showspec.php?id=df9f-5355-0033-c5870033c587
I've had mine about 7 months now. Got round to rooting and superuser last weekend as i fancied a poke about because the system settings seem somewhat locked out as if there is another UI masking the actual ones.
ADB usb is disabled. Have to use wifi adb if you want to get into it.
I rebooted to recovery but not much seems to be going on. Android on his back with Chinese writing underneath that i think translated to "No going forward". So i think TWRP is on the cards and a full backup made.
The build code: LMY47I rang a bell for me when i saw it as i have a nexus 7 2012 and the build for that was LMY47D. Perhaps this is based on a nexus rom?
Hopefully somebody with some knowledge will come along and possibly be able to identify.

thanks for the info i have searched and found the same as you, not a lot!
i'm pretty happy with it, would just like a nicer launcher with nicer apps

There appears to be an apk in the system called "systemui" Not sure if that's the one that's laid over the top of the actual android OS. I had a quick go with Nova launcher but you can't get it to stick. When you reboot, it reverts back.
Would be nice to get it to the standard android home screen and then be able to customize it to your hearts content. I'm not up on this kind of thing tho so i don't want to poke about too much incase i break it. Especially with no apparent recovery as yet.

ah right. was looking at what was running on startup to stop the radio coming on straight away, haven't found it yet.

duplicate

using Startup Manager i have managed to get rid of "Launcher3" which is the standard launcher/interface and now use Car Launcher Free, which is a lot nicer (there is also a Pro paid for version).
just need to stop the radio starting up straight away now, can't see it on the Startup Manager
no further with ROMs...

was there anything under launcher 3 when you uninstalled it?
I wonder if we could extract the apk for the radio app, then uninstall it from the system and then reinstall it as a user app. Would have control over it then.
I'm currently trying to enable usb adb function. Having no luck editing the build.prop so far. I think i've got the goods to make a custom recovery but without usb adb working i can't install it.

i haven't uninstalled it, just disabled it at startup.
have you had a look at Headunit app? think that has an option to try and enable USB ADB

just noticed on the Play Store the headunit comes up as "Alps mid 1008l_emmc", same as this one: https://forum.xda-developers.com/android-auto/android-head-units/slim-profile-head-unit-t3631732

So i've been foiled by irony. The irony being that i wanted to setup recovery incase anything went wrong but it seems that by trying to setup the recovery things have gone wrong. Horribly wrong. lol
Currently got a bootloop. Boot logo back to "recovery" and the android on his back. But there is no recovery. So after 5 minutes, recovery exits by itself and continues on to the boot logo and then goes back to the non existent recovery. This occured after i changed the write permissions of /system as bulild.prop was read only. Wanted to change "persist.service.adb.enable=0" to "persist.service.adb.enable=1". This is what's stopping usb adb. I have an app to force adb but it doesn't force it. There's something in the rom that wont allow it to be changed. I'm pretty much stuck. There's zero information on the web about these units. Unfortunately it's looking like replacement for me. Tragedy!
To make things worse, this afternoon on the school run, the starter motor decided to stop working. So i've just had the car delivered home on a recovery truck. Radio on the back burner til the weekend now.

delited

Oh bugger. Let me know if I can help in anyway

Hello. I have the same stereo, so far it works OK. You have to read in Russian forum which is mentioned earlier, now they have translation of that topic . Big thanks for this to Sander2010 moderator of this page. And if you have questions you can try to ask in English. Regards Dusix.

Strange Problems with Joying 2gb Intel Sofia Head Unit on 6.0.1

Hello, i'm having trouble with my Joying JY-VL-131N2 Intel Sofia 2gb for Volkswagen.
Couple of months ago i installed SuperSU on Android 5 and some months later i updated to Android 6.0.1 september update.
I also used hvdwolfs Joying Extra Tools app to install the Sofia Server Mod so my Tasker is up and running automatic on every ignition.
All went well for some months but sometimes the standard video player has freezes from time to time and my music clips stored on usb stick were halting for some seconds and then continued playing.
I decided to update Joying Extra Tools to latest version (50) and look if there maybe is an updated SofiaServer Mod. I thought it must have to do something with that because after every fresh reboot it plays nice as it should. I installed the Mod again and then unfortunatly i tried to change the Joying Settings to Standard Android Settings via the Extra Tools app. But the installation of settings.apk hangs so i rebooted.
After that the mcu had some strange behavior. The volume rocker sign at notification bar was gone and i couldn't use my steering wheel keys.
Also the storage seems broken or so. I were not able to access files on usb.
First i tried factory reset and the device boots up with standard settings but problems still persists.
Then i put the update files from sept. 1. - 6.0.1 on fat32 stick but update failed.
On reboot it was stuck at command line and shows...
"E:usb volume for path [/mnt/usb_storage/5009_60.zip]
cannot unzip update file!
Error wait here..."
After some minutes the mcu reboots and same odd android with faults is up.
It seems something in android system is broken. I managed to use my phones hotspot to get wifi and downloaded / installed Joying Extra Tools.apk. The device still seems to be rooted but i'm stuck at this point now.
Also under device info it doesn't show anything other then "Unknown" for example the MCU Version...
Can someone figure out what i did to my mcu and how to fix this?
Greetz
gdre

try to flash stock rom from other usb stick

I tried different USB Sticks and SD Cards but still the same with canot unzip error.
Maybe i'll give TWRP and GTX Rom a try.

try to flash this one.. if android doesn't boot completly just flash standard rom afterwards.
Help out someone else with same issue

Ok so i did unrar the 2 files on root of usb but nothing happened after connecting. then i copied whole stock 6.0.1 files on usb root but replaced Allapp.pkg and 5009_60.zip from your archiv.
It flashed! But then i got stuck at command line (see picture)... waited couple of minutes nothing happened.
Then i copied/overwrote back the 2 files (Allapp.pkg and 5009_60.zip) from stock update.
The HU bootet up to faulty android. I flashed the stock update but i got same error as described in first post.
"E:usb volume for path [/mnt/usb_storage/5009_60.zip]
cannot unzip update file!
Error wait here..."
The "Error wait here..." message appears after i got back in the car and turned ignition on.
Did i made some mistake?

gdre said:
Ok so i did unrar the 2 files on root of usb but nothing happened after connecting. then i copied whole stock 6.0.1 files on usb root but replaced Allapp.pkg and 5009_60.zip from your archiv.
It flashed! But then i got stuck at command line (see picture)... waited couple of minutes nothing happened.
Then i copied/overwrote back the 2 files (Allapp.pkg and 5009_60.zip) from stock update.
The HU bootet up to faulty android. I flashed the stock update but i got same error as described in first post.
"E:usb volume for path [/mnt/usb_storage/5009_60.zip]
cannot unzip update file!
Error wait here..."
The "Error wait here..." message appears after i got back in the car and turned ignition on.
Did i made some mistake?
Click to expand...
Click to collapse
What MCU version do you have.. ? Did you flash from stock recovery?.. try to flash latest official rom. See my signature for rom.

D3LTA said:
What MCU version do you have.. ? Did you flash from stock recovery?.. try to flash latest official rom. See my signature for rom.
Click to expand...
Click to collapse
The Problem ist i can't determine the MCU Version because its shown as Unknown Device under Settings.
Ok i need more advice i think... how can i boot into stock recovery? I put the files on usb stick, plugged in an wait until update massage appeared.
Did you mean i should flash the 2 files from testkeys.zip direkt with stock recovery?
so for now i will try to use an app like quick reboot to enter stock recovery.
otherwise please tell me exactly what i have to do

No worries we gonna fix this

Ok thank you I'm hopefull
Now i installed Quick Reboot app and let the app boot into recovery mode.
But when it reboots i got command line with something like sofia6.0! error wait here...
so it seems i even can't enter recovery mode

Can you flash TWRP recovery from within the custom.apk ? Is so you can then flash GTX ROM and update mcu from within car settings app (MCU files are in the rom)

In the gtx thread there is some info in description
"Due to Bluetooth, WiFi, and as well as nvram patches in the ROM and bootloader, you must be running Joying 6.0 firmware dated 2017_12_15 or later to install this ROM."
but i'm on earlier update so i don't know which is the last gtx version i could use.
i have sent gtxaspec a private message couple of days ago but no answer still.
i will try to install twrp first. i think when that works it could take in the right direction

i managed to install custom.apk. i had to access usb stick over root explorer from playstore because the stock filemanager won't let me access storage.
when i choose install custom recovery from custom.apk i get the message that i'm on the wrong update as i mentioned before
i think i maybe need an older version of custom.apk? hopefully then i'm able to install twrp that suits my current update version...
sadly in the mainthred the older versions if there any exists are not provided.

gdre said:
i managed to install custom.apk. i had to access usb stick over root explorer from playstore because the stock filemanager won't let me access storage.
when i choose install custom recovery from custom.apk i get the message that i'm on the wrong update as i mentioned before
i think i maybe need an older version of custom.apk? hopefully then i'm able to install twrp that suits my current update version...
sadly in the mainthred the older versions if there any exists are not provided.
Click to expand...
Click to collapse
Didn't see your message(sorry I get a lot)....
Update to the latest joying Intel room, listed in my thread under Q and A, then you should be able to install my ROM. ?
Don't attempt install on old firmware, it causes issues with the bootloader and if difficult to fix. Follow all directions I'm my thread.

We have to start completely fresh here. If you started from a ROM earlier than October, your current MCU version is < 9.20.
The errors you get ("can't verify ..5009_60.zip") is due to incorrect signing and mixing all kind of ROMs and files and probably the TWRP recovery image. That will definitely not work.
Download/Use the latest ROM (2018-1-26; see below in blue) from here. (From this Joying blog https://www.joyingauto.com/blog/category/updated-files-released/)
Code:
Below updated files is (2018-1-26) version . please check :
Updated files for HD resolution 1024*600 :
MCU version is 9.20 or more later please click Here
[COLOR="Blue"] MCU version is 5.25 or more earlier please click Here[/COLOR]
If you flashed the TWRP recovery from the custom.apk then first write the stock recovery back.
Before trying to flash remove all SD-cards and usb-sticks from the unit and reboot with the usb-stick (or sd-card) with the complete unzipped ROM. Do not alter anything on this downloaded ROM.
Please try to flash that first. Then we see if it works or what error message we get. Do not try all kind of things with the TWRP/gtx ROM before your firmware and MCU firmware is correct.
If this doesn't work then we use the reset method: Use the same usb stick and use a "pointy thing" (needle or so) to reset your unit. Do this 3 times (reset immediately when you see the logo coming). Then the unit's leds will cycle purple/pink a few times and reboot the unit again perhaps 3 times and will then (hopefully) start the flash of the ROM. The pink/purple flashing/reboot can take 10 minutes: Have patience.
Maybe @gtxaspec has a few hints here as well.
Edit: and now @gtxaspec's post and mine are crossing.

旧FYT SOFIA 1024x600 did the trick!
Now i think about flashing twrp and gtxrom
some problem left is my steering wheel control. i can't really remember but i think the profile was rcz_vw_low or something like that.
back then when i purchased the HU, steering wheel control works out of the box. with rcz_vw_l mode the buttons response but volume up and down only response repetitive.
before the update i was able to press and hold the button and the volume was increasing or decreasing without having to press again and again.
is this a problem with maybe wrong profile or some setting i missed?
other thing is i don't see setting for deactivating button/touch beep. before the update it was under car settings t think.
but first at all i'm happy and relieved that the HU is working.
thank you both for your help!

gdre said:
旧FYT SOFIA 1024x600 did the trick!
Now i think about flashing twrp and gtxrom
some problem left is my steering wheel control. i can't really remember but i think the profile was rcz_vw_low or something like that.
Click to expand...
Click to collapse
Nice to hear.
Try the RZC.XP(L)-VolkswagenALL

surfer63 said:
Nice to hear.
Try the RZC.XP(L)-VolkswagenALL
Click to expand...
Click to collapse
That worked!
and the volume increase decrease is working too... sometimes i'm a little bit dump ... i had to press quiet a bit longer then the volume goes up or down when i press and hold up or down key at steering wheel. it seems there is a slightly more delay since the update.
only thing that is annoying is the button/touch beep. there is no option to turn it of... maybe i can get root to find and change / rename the soundfile?
any suggestions?

Ok i figured out the annoying beep thing. In car settings you have to switch to no amp then under sound settings tab the beep can be disabled.
as long as an active amp is choosen the option for beep is gone.
Hope that could help someone.

Touch stops working.

Okay, so... I'm a noob at this. Apologizing up first if I somehow did something wrong or not properly.
Issue:
I have a Verizon Samsung Galaxy S5. About a year ago I managed to get root access and boot LineageOS on my device, and it was working just fine. 2 months ago I decided to try out resurrection remix oreo. It also worked fine... but then I decided to upgrade the rom... Instead of upgrading (by flashing the new build) I went into recovery (TWRP) did an advance wipe and wiped the entire system, data, cache etc... and just loaded the rom like new with Gapps and Magisk.
For some reason TWRP doesnt work well with Aroma Gapps... and I often like to customize what Gapps get installed. It took me a while to figure out how to make a gapps config file and where to put it.
So after booting the new os everything seemed to work fine. Except! Whenever someone called me, my touchscreen would not respond... I couldnt answer calls or even end them. I had to wait till the call ended so I could use the phone again. So I tried clearing the Phone app's data and see if that would help. (It didnt)
I decided to wipe my device again, do a factory reset. So I booted into recovery only to find my touch screen wasnt working again! I pushed the power button to turn off the screen and turn it on back again and my touch worked. (This was strange)...
So I went ahead and cleared everything again, this time I decided to downgrade and go back to LineageOS 14.1. and now..... it's worse.
The touchscreen goes on and off when it feels like it. It doesnt happen with just calls anymore.
The touchscreen would work but the navigation buttons (Recent apps and back button) seem to work.
and then there are times where the touchscreen would work but the navigation buttons wouldnt work.
sometimes both wont work.
I also get a bootloop issue.
The Samsung Galaxy S5 Powered by Android boot up screen usually loops for a good while and then youd get the Lineage os boot animation. Sometimes it comes on as normal.
I know you guys may need a logcat. So ive grabbed one. I'm not sure how to attach because I dont see any option to and apparently after 10 post, only then I can post links.
I also tried flashing a new Kernel but that didnt help...
Again I'm apologizing if i did anything wrong or improper. If you need anything else, I'll be willing to provide more.
Thank you!!!
Link to Logcat:
nofile.io/f/sEA03NPv8rx/2018-06-26-17-47-11.txt
I also used GAPPS Super package with a config file for custom gapps installation.
Link to my GAPPS config file:
nofile.io/f/qONXoDoewuX/open_gapps_log.txt
nofile.io/f/hodHOtCFaTH/open_gapps_debug_logs.tar.gz
nofile.io/f/35qUphmpxOZ/.gapps-config
EDIT: Ive noticed whenever my nav buttons dont work, the recent apps button is lit but very slightly, the back button doesnt light up at all.

hyp3rvybe said:
Okay, so... I'm a noob at this. Apologizing up first if I somehow did something wrong or not properly.....
Click to expand...
Click to collapse
I'm just going to suggest something...
Have you tried the following?
1) Go to Developer options...
2) Then the Drawing Section (or Rendering Section)...
3) Locate and Disable/Turn Off the "Hardware Overlays".
It looks like many Samsung Devices experience this issue (or similar) and is, unfortunately, misdiagnosed as a hardware issue (though it can be Hardware Related).
Sometimes, without any "rhyme to reason", the device can get a bit confused between the use of Hardware or Software settings and acts like its in a "Panic" like state bouncing between the two.
The above steps just manually tells the device to use GPU for all/any screen adjustments.
There's no guarantee that this will work but, I've seen it work for most individuals who has/have/had experienced the same/similar issue.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Apparently it was already off... I tried turning it on. Will use it during the day and see what's up. Also I remember whilst the logcat was running. If I tapped the screen it would show something like "pause audio"... I'll grab some screenshots later.
And as for touching the navigation buttons. It shows Google input method anytime I touch the buttons. I'll grab some screenshots to show specifically. Have to head to work

Okay so if I touch the screen, log records the entry as
AudioService Stream Muted, Skip Playback.
Anytime I touch the navigation buttons it shows
GoogleInput onFinishInput(): Dummy InputConnection bound
GoogleInput onStartInput(): Dummy InputConnection bound

hyp3rvybe said:
Okay so if I touch the screen, log records the entry as
AudioService Stream Muted, Skip Playback....
Click to expand...
Click to collapse
Your best bet is to post this within the following Q&A thread that's specific to the S5 and Variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Members there should be able to provide some better guidance than I can at this point.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

AVIN Android 9 Time Keeping Issue

Hi, I purchased an AVIN unit a few weeks ago for my E83 (2005 BMW x3 2.5i). I have a weird time issue that I submitted a ticket to AVIN for but they only responded with their stock answer, and I haven't heard anything since. Anyhow, the unit doesn't keep time properly. If I set the time manually it doesn't save the time when the unit is turned off. When I turn it back on again it resets to 10:05am and the date as September 2nd, 2016. If I set it to GPS time, it is an hour slow, even though it's getting the correct time zone. I have no idea how to make this right. If there was an option to just turn the time display off I would do that, but there isn't.
MCU: 023042bGs-E39-HW7-190611[B1280_170325]
App Version: 2019072501_1280x480_970
I note there is an MCU version 191118 for the E39 unit which appears to be newer, but how is that possible if it isn't November yet?

AVIN got back to me and said that time must be set via GPS Sync (they are giving me mixed messages). Anyhow they provided no direction on fixing the hour out of sync issue. I installed the app "Smart TIme Sync" and sure enough it detects the hour difference, however it needs the device to be rooted to fix the issue. How difficult is it to root these devices?

Rooting the PX6 Device with Android 8 is quiet simple, just check the following link: https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740
At Point 4, after the first line "adb connect ..." you maybe need perform the "adb disable-verity" command and reboot the device once again.
And don`t install SuperSU as application afterwards, this may cause troubles, root does also work without the app installed.
Chri

Chrisu02 said:
Rooting the PX6 Device with Android 8 is quiet simple, just check the following link: https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740
At Point 4, after the first line "adb connect ..." you maybe need perform the "adb disable-verity" command and reboot the device once again.
And don`t install SuperSU as application afterwards, this may cause troubles, root does also work without the app installed.
Chri
Click to expand...
Click to collapse
Sorry, I forgot to mention I have an Android 9 unit. Is the process the same?

CharismaKenzie said:
Sorry, I forgot to mention I have an Android 9 unit. Is the process the same?
Click to expand...
Click to collapse
Hy
Haven`t seen someone with a PX6 & Android 9 yet who rooted it,
You can try the Snapdragon Android 9 Guide https://f30.bimmerpost.com/forums/showpost.php?p=25195472&postcount=173
please give Feedback if it will work of something needs to be modified
Chri

Hizpo T8 / 7.1.2 No Status Bar, no side buttons, just touchscreen... Help a Teacher!

Hello Friends
I've had issues with this headunit for a long time. Last week, side buttons started not working. After several attempts, I managed to "factory reset" which it does not wipe, just reinstalls without erasing anything. Sometimes it works like normal but the majority of the week it doesn't.
I've tried several methods and I realized that the top status bar was not visible, but when I've been able to activate it, everything is back to normal, including the side buttons.
So I wonder if you can help me saving some money, because it would be pretty sad to get rid of this radio and get another that might have the same issues.
I hope you can help me
specs of my radio
processor: ULTRAOCTA T8
android: 7.1.2
MCU: 5.3.19-123-10-E06101-171205
System version: V9.2.2_20180523.142211_ZYC2-FD

Try to do this (factory reset)
Allwinner R16 (astar_d7) Android 6.0.1 Marshmallow - Partition Dump & Information
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...
forum.xda-developers.com

Thank you SO MUCH! I will follow all the procedure and let y'all know!
Have a wonderful day, Mr. Jones!