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!
Related
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.
ok so I had a rooted phone running AOKP and franco kernel, it was all fine. but then being the irritatingly impatient person that i am, i wanted android 4.3 so flashed the stock rom, and so everything is now stock, which is what i wanted. BUT, I can't use root! I have supersu installed but whenever an application request root...nothing. literally nothing happens, it's meant to pop up with a little box asking me if i want the app have root access, but now it doesn't come up. It may be linked to the fact that whenever I open supersu it says "The SU binary needs to be updated. Continue?" so obviously i tap continue, but then it says installing for a about half a second, then it just says "Installation failed!". I've looked around and some people say they can't update their supersu binary if they don't have busybox. When i rooted with Nexus 4 Toolkit (thanks so much mskip. also because of what i say after this it may make this thanks look sarcastic. it's not, nexus 4 toolkit has been amazingly useful to me) it told me busybox had been installed, so i just assumed that it had been. when i saw people saying that i may need busybox i download a busybox installer from Play and it told me i didn't have busybox. so i told it to install busybox and it said "Installing BusyBox v1.20.2 failed. Please try installing a different version. Please note that BusyBox installer attempts to install BusyBox to your system. Some versions of busybox may not work with some devices. If problems persist please email us and we will be glad to offer our assistance". as it suggested i tried other versions of busybox. in fact i tried every version the app would let me try, and none of them worked.
I have Android 4.3 and stock kernel
rafspeik said:
ok so I had a rooted phone running AOKP and franco kernel, it was all fine. but then being the irritatingly impatient person that i am, i wanted android 4.3 so flashed the stock rom, and so everything is now stock, which is what i wanted. BUT, I can't use root! I have supersu installed but whenever an application request root...nothing. literally nothing happens, it's meant to pop up with a little box asking me if i want the app have root access, but now it doesn't come up. It may be linked to the fact that whenever I open supersu it says "The SU binary needs to be updated. Continue?" so obviously i tap continue, but then it says installing for a about half a second, then it just says "Installation failed!". I've looked around and some people say they can't update their supersu binary if they don't have busybox. When i rooted with Nexus 4 Toolkit (thanks so much mskip. also because of what i say after this it may make this thanks look sarcastic. it's not, nexus 4 toolkit has been amazingly useful to me) it told me busybox had been installed, so i just assumed that it had been. when i saw people saying that i may need busybox i download a busybox installer from Play and it told me i didn't have busybox. so i told it to install busybox and it said "Installing BusyBox v1.20.2 failed. Please try installing a different version. Please note that BusyBox installer attempts to install BusyBox to your system. Some versions of busybox may not work with some devices. If problems persist please email us and we will be glad to offer our assistance". as it suggested i tried other versions of busybox. in fact i tried every version the app would let me try, and none of them worked.
I have Android 4.3 and stock kernel
Click to expand...
Click to collapse
Try this link: http://forum.xda-developers.com/showthread.php?t=2378413
nikhilodeons said:
Try this link: http://forum.xda-developers.com/showthread.php?t=2378413
Click to expand...
Click to collapse
it worked, thank you so much!
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Thanks for posting this, I will have time to try it to tomorrow, hopefully it fixes this issue for me as well!!
boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload Mod Collection 4.0
Open Xposed Framework and check Mod Collection 4.0 as a module
Open Mod Collection 4.0 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open Mod Collection 4.0 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
Where can I download Mod Collection 4.0 or did you mean Mod_Collection4Ouya.3.6.apk?
Thanks I will try this.
Sent from my GT-I9100 using xda app-developers app
@Toxic_Dragon - you are correct. I meant ModCollection4Ouya version 3.6. I've updated the original post. Thanks!
boo13oo said:
I am unable to post in the development forum yet, so I am posting here. For the past several weeks I have been having trouble installing CWM Recovery. I've tried using the Mod Collection tool and manual installation and still received the Ouya (!) screen. With the new Ouya update, I needed CWM to work to preserve root. If you are also having issues installing and booting to CWM, the below worked for me.
Steps I used to gain Root, setup Play Store and install CWM:
Sideload and run One Click Root
Sideload Jrummys Busybox Installer & Install Busybox
Sideload and Install Xposed Framework
Sideload ModCollection4Ouya 3.6
Open Xposed Framework and check ModCollection4Ouya 3.6 as a module
Open ModCollection4Ouya 3.6 and performed the following:
Install Play Store and Select "On" for Play Store option
Install CWM Recovery
Reboot into CWM but receive error Ouya (!)
Below corrected my CWM Install Issue and allowed me to update to the newest firmware:
Open Play Store & Install Busybox Installer (Stephen Stericson version)
Open Busybox installer - smart install automatically installed busybox
Open Mod Collection 4.0 and reinstalled CWM
Reboot to CWM
CWM Recovery worked
Open ModCollection4Ouya 3.6 and select option to Preserve SU
Reboot then install upgrade
Good Luck and hope you experience the same results! It seems the Jrummy Busybox version didn't work for me. After installing the other version, CWM installed successfully.
Click to expand...
Click to collapse
It didn't work for me.
Sent from my GT-I9100 using xda app-developers app
I had issues with ADB and fastboot until i changed the drivers for the ouya manually for every step in the device manager.
THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:
CheeseMcGee said:
THANK YOU!!! You are the freaking man!!!! I have wasted hours trying to figure out how to fix CWM and I couldn't get anything. Finally stumbled upon this post, and I am kicking myself for not finding it sooner. Thanks a ton! :laugh:
Click to expand...
Click to collapse
What exactly did you do as I can't get this to work.
Sent from my GT-I9100 using xda app-developers app
robinscp said:
What exactly did you do as I can't get this to work.
Click to expand...
Click to collapse
I had used a different method to root and install CWM, but in order to fix the problem, I literally followed every step in order starting with sideload One Click Root. It was redundant and un-necessary, but it produced the results in the end by following step by step.
Hi there,
A quick question - has someone here recently updated to Magisk 13.3 / Magisk Manager 5?
I am currently on Magisk 12.0 / Manager 4.3.3 (Resurrection Remix) and would like to update as Safety Check is failing after the Playstore update.
However according to this thread
https://forum.xda-developers.com/showpost.php?p=73142437&postcount=17290
there is a problem with the Axon 7 and the latest Magisk...
So which version is everyone one using and how did you get there (update Magisk first/Manager first...)?
(Magisk Manager is prompting me to update to 13.1 at the moment - not sure that's wise then?)
I updated to magisk 13.3 using magisk manager. Everything went smoothly and safety net passes even with a few modules installed. I was using A2017G on stock B05
Grogros4 said:
I updated to magisk 13.3 using magisk manager. Everything went smoothly and safety net passes even with a few modules installed. I was using A2017G on stock B05
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - when you updated to Magisk 13, did you already use Manager version 5 or are/were you still on version 4 and updated afterwards?
I am not sure.... I think I was running magisk 13 beta so I guess I was using magisk manager 5
I'm using magisk 13.3 with manager 5.1.1 on a stock chinese rom. I already fixed my issues regarding our unit which crashes the manager after giving su permissions.
After installing magisk in twrp and booting into system, open terminal manager and type these codes.
Code:
su
cd /data/data/com.topjohnwu.magisk/
mkdir /sdcard/Android/data/com.topjohnwu.magisk
cp -R ./databases /sdcard/Android/data/com.topjohnwu.magisk/
mv databases .databases_old
ln -s /sdcard/Android/data/com.topjohnwu.magisk/databases databases
chcon -h "u:object_r:app_data_file:s0:c512,c768" "/data/data/com.topjohnwu.magisk/databases"
Credits to @zorgzd for his fix.
Thanks a lot both of you -
I'll try the fix once I updated, that's really helpful. (Still wondering if I should try to update to Magisk 13 from Manager 4 and then install the Manager 5 apk after reboot...).
Whoooo? said:
Thanks a lot both of you -
I'll try the fix once I updated, that's really helpful. (Still wondering if I should try to update to Magisk 13 from Manager 4 and then install the Manager 5 apk after reboot...).
Click to expand...
Click to collapse
I would suggest to remove your old magisk using the latest uninstaller flashed in twrp. That will also install manager v4.
Then restore your boot.img backup if you have any.
And lastly, flash the latest version, 13.3 as of writing. It contains the latest manager also included in the zip.
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.