Hey guys i currently have the atoto a6 pro model without gesture, and the problem im having is it is currently rooted and every time i open viper4android itll ask me to install drivers then it will reboot and when i open it again it basically asks for me to do it again. I can not for the life of me figure out how to fix this, I tried to change mode to permissive but i try to do it with terminal emulator where i put in setenforce 0 and it comes with selinux disabled or something like that. I even tried the selinux mode changer and it didnt work either. I really want to use viper4android if i cant ill have to send this unit back because there is hardly any eq options stock.
Can anyone help me with this? would really like get this problem fixed.
You have busy box installed??
Enviado do meu iPhone usando o Tapatalk
Yes busy box is installed.
Can anyone recommend the new joying unit? It seems to have a really nice eq, and fastboot. But hows the rca voltage? The atoto a6 has 4v preouts.
Did op ever work this out?
Related
One of the best sound mods for the note4, V4A (http://forum.xda-developers.com/showthread.php?t=2191223), seems to have big problems with the combination of SELinux from Samsung and Lollipop.
I've read around since a few days to find a solution, but there is none as far as I know! All of the working solutions use a custom kernel with "permissive" SE settings, and due to the lack of a N4 Lollipop custom kernel we do not have this option.
Has anyone managed it to get Viper working on N4 and Lollipop?
I can't imagine I have been the only user of N4 and Viper, therefore more people must have this problem...
Edit:
Some info about SELinux:
http://www.all-things-android.com/content/selinux-android-and-samsung-knox
"The Enforcing mode is the default mode for KitKat 4.4. You can use the setenforce command to temporarily switch modes. To change the boot mode, you need to use SEAdmin, the "SELinux Mode Changer" app, or manually modify the init.rc file. The "SELinux Mode Changer" app will not work with Samsung KNOX enabled firmware."
SELinux Mode Changer does not work, has someone experience with modding init.rc or with the "SEAdmin"?
Subscribed to this thread... just decided to root for Viber
Sony MDR 1RBT V2 - Samsung Level Over - Shure 425
They all sound good on the Note 4 but compared to Note 3 with Viper it's hard to switch back to Note 4 910F Adreno
Using AEL custom kernel viper works again on 910f I'm using power amp. On stock music app viper doesn't work for me, only on power amp
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!
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.
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
i tried using kingoroot and it gets stuck at 90% and then does nothing. Im hearing a lot about magisk but have no idea how to do it so if someone can help me it would be greatly appreciated. Thanks!!