BusyBox on LG K350 K8? - LG K8 Questions & Answers

I have the stock LG K8 (aka K350, that's it, no letters, just K350.)
I've tried installing BusyBox on it. For some reason, before BusyBox starts installing the phone just freezes and after a while it restarts itself. Can I use TWRP in some way to flash BusyBox or is it something to do with lz4 compression format or something? Really need BusyBox here.

Related

[Q] Update to franco kernel but cannot update SU binaries

Hi All,
Please forgive me for this noob question but I updated to franco kernel a few days ago which i absolutely love how fast it its. The problem I am having is that my superSU binaries will not update and neither with busybox. I do have the toolbox and tried to installed the CWM-SuperSU.zip and still have the error message that the binaries failed to update and SU just closes. Can someone help me? I really want to keep this kernel...:crying:
Thanks again
The kernel has no relation to the applications.
nickd1976 said:
Hi All,
Please forgive me for this noob question but I updated to franco kernel a few days ago which i absolutely love how fast it its. The problem I am having is that my superSU binaries will not update and neither with busybox. I do have the toolbox and tried to installed the CWM-SuperSU.zip and still have the error message that the binaries failed to update and SU just closes. Can someone help me? I really want to keep this kernel...:crying:
Thanks again
Click to expand...
Click to collapse
Hi, nickd1976...
That is most peculiar...
A kernel is part of a boot.img file...(along with ramdisk)... and franco's kernel is one of the easiest to flash, consisting of nothing more than a singular boot.img file.
The boot.img in the franco.Kernel-nightly-r47.zip, can simply be extracted and fastboot flashed...
Code:
fastboot flash boot boot.img
The accompanying updater-script in franco's zip does something similar, when flashing via a custom recovery... (although done slightly differently).
Extract...
Code:
..
package_extract_file("boot.img", "/dev/block/mmcblk0p2");
..
-----------
But the point is this... flashing a kernel is flashing a new boot.img... to the boot partition.
AND IT DOESN'T TOUCH SYSTEM... where the SU binary lives... and thus should have no effect on the SU binary.
If you're having problems with root, it probably has nothing to do with franco...
------------
Here's what I would try...
Get Chainfires SU updater package from here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip.
Fully unroot, by going to the SuperSU app>>SETTINGS TAB and select the option 'Full unroot, Cleanup for permanent unroot'.
Reboot your tablet as normal. Confirm you are unrooted (by running Titanium or typing 'su' in terminal emulator..).
Reboot your tablet into recovery (CWM/TWRP)...
...reflash Chainfire's SU updater package..
Upon reboot, you should be re-rooted.
------------
In conclusion, I can only say that I have been running franco's kernels for a couple of months now, and I've never had any problems with root at all.
Rgrds,
Ged.

Multitool Advance v6 by dr.ketan - Busybox Problem

Hi all,
Just flashing my note 3 to stock rom 4.3 latest update. Then using dr.ketan multitool to root, at this stage all is good. Until I install apps like titanium backup (titanium said no binary found) or triangle away (it says supersu needed, even the phone is rooted and supersu can be updated). Tried to install busybox from apps store but still can't fix the problem. checked with root checker, it says device rooted but no busybox found.
Does anyone know how to fix this issue? Have tried to flash and reflash so many time with different options but still no fix. I just need to get the busybox get recognised so my titanium backup and triangle away can work properly.

[Q] TWRP Manager BusyBox conflict with dorimanx kernel

Hi all,
I just installed Dorimanx kernel, and when going into TWRP manager it comes up with a BusyBox conflict:
"the only compatible version of busybox we support is Stericson, etc"
I did try to search for answers but no luck in finding any relevant posts on this.
Busybox says I have installed the "v1.22.2-Dorimanx". Busybox insists on installing v1.21.1
My question is:
- how bad an issue is this with respect to using TWRP Manager? Should I just ignore the warning or is it safer to just not use TWRP Manager with the Dorimanx kernel?
Thanks for your expertise!

FYI: Viper4Android DOES WORK

You just need to use the "Sony Beats Edition 5.5" to make it work. This version is a flashable zip and has the driver prepackaged.
It can be found in this thread:
http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
And here is the direct download link:
http://forum.xda-developers.com/attachment.php?attachmentid=3683972&d=1458053955
Are you getting headset and speaker processing as well? I've flashed stock and rooted fresh then installed BusyBox and flashed the 5.5 Beats zip 3 or 4 times now and it outright refuses to process anything besides Bluetooth. I'm also on the H830 and I'm at my wits end as to why everyone else is able to get this working besides me.
virgilante said:
Are you getting headset and speaker processing as well? I've flashed stock and rooted fresh then installed BusyBox and flashed the 5.5 Beats zip 3 or 4 times now and it outright refuses to process anything besides Bluetooth. I'm also on the H830 and I'm at my wits end as to why everyone else is able to get this working besides me.
Click to expand...
Click to collapse
Yes, all aspects of this are working fine for me. Bluetooth, Headset, and Phone Speaker... All functioning as they should... I doubt this will make any difference, but grab the zip I saved (and used) on my phone, from the Toy Box... It's in the "Apps (Root)" folder.
https://drive.google.com/folderview?id=0B74X5BCK5_hld05DQWdZRjlZczQ&usp=sharing
virgilante said:
Are you getting headset and speaker processing as well? I've flashed stock and rooted fresh then installed BusyBox and flashed the 5.5 Beats zip 3 or 4 times now and it outright refuses to process anything besides Bluetooth. I'm also on the H830 and I'm at my wits end as to why everyone else is able to get this working besides me.
Click to expand...
Click to collapse
If this method wont work,I have another.
1. Just flash clean System partition to get rid of v4a sony.
2. Download v4a apk and install.
3. Install driver if needed.
4. Install Busybox.
5. Install Selinuxchanger and change it to permissive.
6. You are ready to use Viper4Android on the G5
Sent from my LG-H850 using XDA-Developers mobile app
iGridZ said:
If this method wont work,I have another.
1. Just flash clean System partition to get rid of v4a sony.
2. Download v4a apk and install.
3. Install driver if needed.
4. Install Busybox.
5. Install Selinuxchanger and change it to permissive.
6. You are ready to use Viper4Android on the G5
Sent from my LG-H850 using
Click to expand...
Click to collapse
I've tried selinuxchanger but when it opens up and I grant it root access it tells me it wasn't able to get root access and leaves the options greyed out.
tribalartgod said:
Yes, all aspects of this are working fine for me. Bluetooth, Headset, and Phone Speaker... All functioning as they should... I doubt this will make any difference, but grab the zip I saved (and used) on my phone, from the Toy Box... It's in the "Apps (Root)" folder.
Click to expand...
Click to collapse
I'm in the middle of another fresh root flash, I'll give it a shot and report back in a bit.
virgilante said:
I've tried selinuxchanger but when it opens up and I grant it root access it tells me it wasn't able to get root access and leaves the options greyed out.
I'm in the middle of another fresh root flash, I'll give it a shot and report back in a bit.
Click to expand...
Click to collapse
You have to get Root on your Phone first and then try my other steps if Threat Tutorial wont work.
Sent from my LG-H850 using XDA-Developers mobile app
No luck. Wiped and flashed stock tot, flashed TWRP tot, formatted to remove encryption, wiped again just in case, formatted a second time, wiped again just to be sure, formatted a third time, flashed SuperSU, flashed dmverity, flashed V4A, granted storage permission for V4A, installed Busybox, opened the app, driver is normal and audio is supported, but it's not processing headset or speaker. Bluetooth is fine. SELinuxmodechanger is still being granted root access but refusing to acknowledge it.
Am I missing a step installing SuperSU? Should I forego the dmverity zip? Should I install Busybox to a different location? I've tried installing to su/xbin and system/xbin. Does the stock H830 kernel support permissive? How would I go about changing it? Kernel Adiutor has a plugin to change to permissive but it doesn't stick. It takes the su shell command to change it, but I can't confirm it in the phone settings.
virgilante said:
No luck. Wiped and flashed stock tot, flashed TWRP tot, formatted to remove encryption, wiped again just in case, formatted a second time, wiped again just to be sure, formatted a third time, flashed SuperSU, flashed dmverity, flashed V4A, granted storage permission for V4A, installed Busybox, opened the app, driver is normal and audio is supported, but it's not processing headset or speaker. Bluetooth is fine. SELinuxmodechanger is still being granted root access but refusing to acknowledge it.
Am I missing a step installing SuperSU? Should I forego the dmverity zip? Should I install Busybox to a different location? I've tried installing to su/xbin and system/xbin. Does the stock H830 kernel support permissive? How would I go about changing it? Kernel Adiutor has a plugin to change to permissive but it doesn't stick. It takes the su shell command to change it, but I can't confirm it in the phone settings.
Click to expand...
Click to collapse
Try another method to Install V4A. The method with flashing even didnt worked for me
Sent from my LG-H850 using XDA-Developers mobile app
Why are you using a permission changer? And why are you installing the stock TOT before the root TOT?
Here's what I did:
Rooted device (did not use stock TOT, went straight to the rooted TOT)
Reboot Recovery
Flash DM Verify
Flash SuperSU
Reboot System
Reboot Recovery
Make Backup
Flash Xposed
Install BusyBox
Flash V4A
Reboot System... All worked fine... To be fair, I did not mention I had BusyBox installed above... That "might" be the determining factor here? I'm currently making a backup of just my system partition... If you want to try it, I will upload it for you later tonight after I am done with work. It's 3.9Gigs. - If you decide to, make sure you have a backup of your own first. I am not liable for broken stuffs.
tribalartgod said:
Why are you using a permission changer? And why are you installing the stock TOT before the root TOT?
Here's what I did:
Rooted device (did not use stock TOT, went straight to the rooted TOT)
Reboot Recovery
Flash DM Verify
Flash SuperSU
Reboot System
Reboot Recovery
Make Backup
Flash Xposed
Install BusyBox
Flash V4A
Reboot System... All worked fine... To be fair, I did not mention I had BusyBox installed above... That "might" be the determining factor here? I'm currently making a backup of just my system partition... If you want to try it, I will upload it for you later tonight after I am done with work. It's 3.9Gigs. - If you decide to, make sure you have a backup of your own first. I am not liable for broken stuffs.
Click to expand...
Click to collapse
Because I'm grasping at straws.
I followed the your order, I'm still just getting bluetooth processing. I'm willing to try out your system partition, I figure there's not much left to lose at this point. If that doesn't work, I'll concede defeat and wait until the B&O module makes its way over.
virgilante said:
Because I'm grasping at straws.
I followed the your order, I'm still just getting bluetooth processing. I'm willing to try out your system partition, I figure there's not much left to lose at this point. If that doesn't work, I'll concede defeat and wait until the B&O module makes its way over.
Click to expand...
Click to collapse
I messaged you the /system backup. I hope this works for you... Let us know plz
Hey sorry to bump this fairly old thread but I'm having problems getting Viper to work on mine too. Bluetooth only works. I installed the 5.5 beats one too but nothing... Did you ever get it to work??
Thanks.
Busybox installed and selinux mode set to permissive?
You could try this fix: http://forum.xda-developers.com/android/software/mod-viper4android-universal-fixer-fix-t3360192
Hello,
i installed viper and it doesn't work. I rooted my phone, installed busybox with TWRP Manager before, but i don't hear any improvement. Selinux mode is set to permissive and i tried the fix but nothing worked. Can anybody help me?
Edit: It just don't wanna work with Deezer....
Lubastos said:
Hello,
i installed viper and it doesn't work. I rooted my phone, installed busybox with TWRP Manager before, but i don't hear any improvement. Selinux mode is set to permissive and i tried the fix but nothing worked. Can anybody help me?
Edit: It just don't wanna work with Deezer....
Click to expand...
Click to collapse
Doesn't work with spotify either.. Whereas it use to to... Pointless me installing it as only use spotify for music..
Sent from my LG-H850 using Tapatalk
Guys I have installed the dolby atmos version and ran a fix, it works on everything (speaker, headset, spotify..). But still not perfect, I believe an app is interferring with v4a, almost every time I need to do a phone restart before I start playing music, but then it works for hours...

p10 lite set linux permissive fails for viper4android, help needed

stock ROM, installed viper4android both ways:
standard apk for nougat from viper homepage
zip guitarhero modified through twrp
both ends in driver install loop at every startup
google says linux should be set to permissive (due to writing rights?) and then modify an audio effects file in vendor...dev...tree with root explorer
even after trying to change linux to permissive with selinux chnager app, the discontinued one, i never get that entry audio effects in vendor dev etc somewhat
so whenever i reboot the phone, restart viper4android it wants to install the driver, says success, re same thing.
never had these problems on custom but on stock ROM, how to solve the issue please on p10 lite?
thanks ;D
Did you find a fix?

Categories

Resources