Database Users

Erisin 4046 Root

Hi all,
I've been reading this forum for a long time and find it very useful but I can't find a solution to my E46 Android head unit, it's incredibly slow and I want to root it and try to over clock it.
It's an Erisin 4046 with android 5.1
I've tried to root it using the code *#hct#root# and get the message 'ADB root'. I've then tried using the Kingroot app but this always fails at around 30%.
Is there anyway of speeding up this unit or rooting it?
I've seen custom firmwares but I'm a bit confused as to which one would work with my unit.
Regards

Does anybody know which custom firmware I can put on here that works fine and is already rooted?

You should use the Kingoroot apk to root the device, not Kingroot.
It worked in my Erisin 3015, by also entering the *#hct#root# code.

Thanks, you solved the issue for me.
After I used that my unit crashed and reset itself, but it came back rooted so all is well.
I've got it set at 1601Mhz and it keeps that on reboot, and now it boots and loads apps much faster.
Thanks!

Bluetooth pairing lost after every reboot

Hello,
Am I the only one with this problem? Bluetooth loses all paired devices after every reboot...
- no problem pairing with any BT device
- after every reboot some or all previously paired devices are completely gone/missing from the list of paired devices.
- after wiping Dalvik/Cache in TWRP, they all show up again and can be paired without going through pairing (until next normal reboot).
- some device on the paired list may be lost permanently even after wiping Dalvik/Cache IF some new BT devices have been added or deleted. In this case a new pairing procedure is needed, as if the device(s) was never paired before.
It seems some devices are more "sensitive" than others. For example a BT mouse may still be on the paired list after reboot while the car BT (Toyota Venza) will always, invariably disappear from the list. In the car, as it tries to connect, the phone will keep asking for randomly generated pairing codes, which the car will not recognize until the phone gets added/paired again. On the other hand, the phone never disappears from the list of paired phones in the car's BT menu.
Just a thought: it's definitely a phone issue rather than a BT device issue (any). Whether connected or not, within or out of range, the phone will always loose the list of paired devices after a reboot.
Phone: SM-G950F (AQH3)
CSC: XEU (UK & Ireland) / Used in Canada on Virgin Mobile
Rooted with Magisk
Thanks!

Same Problems
Hello, I got the same problems. After seeing that this post is a little older, did you found a solution to this?
Need to try the dalvic/cache solutions next reboot.

Some (unknown) system modifications are the culprit! You need to reinstall the firmware (fresh install) using Odin (all sections, not just AP) and most importantly, during the installation of TWRP make sure you do NOT ALLOW SYSTEM MODIFICATIONS (do not use the slider)..

Just started having this very issue recently. Rooted Snapdragon S8+
Used to ok fine remembering all BT devices after a reboot. Just last week, started to notice I would have to start over pairing all my devices after a reboot. Ex: Car Sync, Gear S3 Frontier, Various Earbuds.
I don't have Twrp recovery due to the locked bootloader. I suspect it could be an app, however, no idea where to begin.... Any advice?

Unlikely for an app to do that, unless the app changed your system. Although I'm not sure what really causes it, I know that "some" system modifications do that. At some point I created shortcuts of some hidden settings, using Activities, which caused that to happen again. I didn't have to go through the hassle of reinstalling everything fresh through Odin since I've had a recent TWRP backup and I've restored both, the System and Data. I've lost many hours trying to figure out what exactly causes it but I didn't get any further than figuring out that: (1) some system modifications cause this to happen and (2) reflashing firmware through Odin without allowing any other system modifications during the process, is the ONLY WAY to get back the normal BT behavior.

Any fix for this
I have started getting this on my rooted S9+
Started to get annoying now.
I have stock rom, custom Kernal and magisk.
What resolved yours in the end?

It seems to be an Xposed issue: https://github.com/rovo89/Xposed/issues/294

Despite the apparency, I don't think this is caused by the XPosed framework. As I've detailed above, the problem may occur even before installing XPosed. Even with XPosed installed, everything may be running just fine indefinitely, until certain system modifications seem to be triggering this problem. Although I pointed out before that this would most certainly happen if, during the TWRP installation, system modifications are allowed (by sliding the bar), I'm almost sure that TWRP in itself is NOT the culprit. The same may be said about XPosed. While both may seem to potentially be triggering the issue, I don't think they really are the cause. My feeling is that the real cause is Samsung's native system (possibly one specific application). I've noticed, for example, that when the problem occurs, while Android loses the list of previously BT paired devices either partially or completely, Samsung's Connect still sees them all - as if nothing happened. How is that possible? It's just assumptions at this point but one thing is certain - after freezing Samsung Connect (Smart Things), I've never had the issue again.
As for permanently resolving this once it happens, there seems to be ONLY two ways:
1. Start fresh by re-flashing the stock ROM through ODIN and if TWRP is also installed, system modifications should not be allowed at this time, or.
2. If you already had TWRP installed and had a nandroid backup (System and Data) done before the problem occurred, (1) wiping system and data and then (2) restoring their respective previous versions, definitely solves the problem, without having to go through ODIN everything fresh.
I hope this helps, and I also hope that someone could eventually identify the root cause and address this once and for all. I definitely wouldn't hold my breath counting on Samsung's help!

Note 10 + sm-n975f
Rooted with Magisk
Definitely not an exposed issue because I am not using exposed, never had exposed on this device.
Same problem with 2 different phones of the same model. One was a international dual sim and the other international single sim.
2 other problems,
Sometimes incoming call notification sound can be heard but no incoming call shows up on the screen (ie. Answer /decline. No missed call notification either, only a new voicemail notification, but if they do not leave a message then you would not know who called. lol
Other issue is Sammy is putting music apps to sleep randomly even though I used an app to set screen time out to never.
Never had any of these problems on any other rooted device always used note phones. Ready to get an Exynos note 8, got the 10 because thought it was cool and I was using the note 8 previously with SamFAIL. Too many glitches though.
Man Sammy is failing big time as usual. Never had this foolishness on any other note always been using rooted notes. (exceptffor note 9) Every Sammy support agent acts like they never heard of this before. I see a bunch of note 9 users on shameful Sammy's forums having this exact Bluetooth problem, shame on Sammy's lies and ignorance!
Update :
Found this Magisk fix, This file name is
nfsinjector-956.zip
Flashed with Magisk module manager.
Update : still not working

From experience, I can confirm that a failsafe way to ALWAYS get back all previously stored BT paired devices is to wipe your Dalvik/cache in TWRP.
I'm still on a Samsung S8, rooted with Magisk + TWRP and XPosed. Once in a while I get this BT issue and the above suggested solution always worked for me. Let me know if it works for you.
As for the rest of the problems, I'm really disappointed to hear that. I was planning on buying myself a Note 10 but that makes me rethink it - it pretty much was THE REASON I held back for so long.
I always suspected this had nothing to do with the XPosed framework but every one on Earth, including the devs, swear by it. Well, you just confirmed it.

Xposed had this issue on s8 we had found a fix somewhere. It may not be present on newer versions. Modifying the libs or something. I studied into it. It's even in the github for xposed. So for me it was most definitely xposed

Thanks for the wipe cash fix, I would like to try it, but not sure if I can since I don't have twrp, can twrp be installed on a Exynos note 10?
Is Its possible that the xposed fix is actually fixing a Samsung failure and not an xposed problem to begin with in the place?
all those people on the note 9 shameful Sammy fourms I assume are unrooted users!

Xposed had always had issues on Samsung's. Until s7 or 8 it was modded by Rovo. The s8 didn't need rovos xposed.

Xtrons PA87MTVP advice please

Forgive me if these questions have already been answered, if they have, i have been unable to find them.
My android Head Unit works as expected for about a month and then it starts having System UI issues. After the first 'Unfortunately System UI has Stopped' message, a simple hard reset clears the error for a day or two, this process can be repeated 5 or 6 times until the error message displays even after the re-boot (see video)
youtube.com/watch?v=VOz_xpOk_vI&feature=youtu.be
(Please add WWW etc and paste into browser i am unable to post links and cannot stop it auto adding the URL wrap)
I have previously been able to enter a recovery menu and perform a factory wipe and reset which stopped the message occurring. However, i do not know how i got that menu up and cannot repeat it. so this is my first question:
What sequence of reset pin-hole button presses do i need to do to access the recovery menu?
my second question is what can i do to prevent the System UI from failing?
Incase it makes any difference I believe the head unit that I recieved is acctually a PB86MTVP (I wanted Android 7 but the unit is running 6.1)

I'd contact Xtrons directly, and let them know about the problem, and ask for a system firmware update.
Best of luck!

I have done, and they have sent me updates which do not install. I think because i have a different unit than i ordered but they say i have the right unit and the right update file...

so i found this on an Xtrons forum thread and tried it and it installed! lets hope it was a newer version and not an older one and it fixes the issue. I'll report back in a month or so.
onedrive.live.com/?authkey=%21AD20TJ6qsQAIJ9M&cid=01F95B9BEAD2D83A&id=1F95B9BEAD2D83A%21440&parId=root&action=locate

Sorry for bringing up and old post, i've seen one of these now slightly older Xtrons PA87MTVP going on eBay - is it worth buying? How is this head unit working for you? What are your like and dislikes of this unit? Thanks

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.