Related
Hey guys and gals,
I've got a 7.7 on stock ROM rooted using the original root method the day I purchased the tablet. I've been using my tablet happily for over a month now.
Unfortunately, late last night I opened up Google Play and started updating all my apps, including Busybox by stericson. There was a new busybox version out (1.20.1) and I decided to install it using "Smart install." I'm not sure if it tried to install to /system/bin or /system/xbin but after the install I saw the app give me an error message explaining that the install was unsuccessful. Anyways, now a lot of my root-requiring apps including Titanium Backup Pro is not functioning at all. It seems that my BusyBox installation is corrupt.
I tried using BusyBox Pro by stericson to uninstall but the corrupt busybox seems to have prevented a proper uninstall, so it still lingers. I downloaded JadeEyedWolf's root.zip from his pinned "Root" post which includes SU & BusyBox thinking that installing the root.zip from CWM Recovery would over-write the corrupt busybox. After flashing I rebooted the tablet and I still got the same corrupt busybox issues.
Anyone have any suggestions?
Thanks!
Edit: The corrupt busybox causes the Wifi to show Error when I try to turn on the radio. Not that internet is vital in repairing the tablet, but I've worked around it by tethering Bluetooth internet off of my OG HTC Evo 4G. It's strange though - I can peruse websites and view the items in the Google Play Store but it will never actually download, though the "Downloading --- " bar does display.
I had the same problem, stock rom as well. If you check the reviews for Stericson's Busybox on Google Play, the two top ones a few minutes ago both mentioned the same issue.
Trying to root again and reinstalling Superuser didn't help, neither did a factory reset (manually salvaging settings and data was a pain too).
Re-flashing the original rom fixed it, following the guide at http://forum.xda-developers.com/showthread.php?t=1469635
I switched to JRummy16 Busybox installer and it seems to work.
Surprising that no one else here mentioned the problem ...
Try this fix.
To be more specific: BusyBox installer 8.0 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Installer 8.1 and above has this bug fixed.
Had the same problem with busybox and had to re-install the rom. What does this fix do?
Sent from my GT-P6800 using xda premium
Already answered, see post above.
Deleted
Sent from my GT-P6800 using xda premium
Too late for me to try it, but thanks the same
ginkage said:
To be more specific: BusyBox installer 1.20.1 replaces /system/bin/sh and /system/bin/ash binaries. I don't have any idea why would it do that (considering that I specified /system/xbin as an install folder), but this quick fix restores original ash binary (and sh as a symlink to it).
Click to expand...
Click to collapse
Thank you so much it works well now! You're a life-saver ginkage. Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Thanks again!
Thank you so much it works well now!
Click to expand...
Click to collapse
That's why we are here.
Should I keep the stericson busybox 1.20.1 original install or should I use the busybox installer to install a fresh copy of 1.20.1 in /system/xbin?
Click to expand...
Click to collapse
Personally I always use /system/xbin, so that some custom kernel (like CWM) could use /system/bin if it wanted to.
BTW, the BusyBox installer bug was fixed in version 8.1, and current version is 8.2, so you should update it anyway. I was wrong to mention "1.20.1" version. Post edited.
Hi guys,
First of all, I want to apologize sincerely for the bug that my application introduced in 8.0. I didn't catch the bug because my device wasn't affected by the bug.. (I always test my app myself before releasing..yet I still miss things due to devices file structure being so different.)
At any rate, the bug was that the application symlinked all applets to Busybox. Normally, this is done if you use smart install and change the settings manually. By default smart install will not overwrite applets that are not already symlinked to Busybox.
This was not a problem with Busybox 1.20.1 but was a problem with my application and how it performed the install.
Again, I am very very sorry that this has occured, as a result I am scouring the web trying to find people with the issue and help them resolve it.
If you have this problem, it can easily be fixed by reflashing your current rom. you do not have to wipe or clear any data. Once this is done, you can download my installer, version 8.1 or greater and upgrade busybox as normal.
Please let me know if you guys have any questions.
Best Regards,
Stephen - Stericson
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Deleted
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
ninpo said:
I too had the same situation, updated busybox then noticed something was awry when hidebar wouldn't work. My issues go way beyond broken root and WIFI, I've also been getting constant reboots. I was just about to re-install the stock rom until I read about the possible udate.zip fix. I'm very interested in how to apply the zip (I don't have CWM) being that i do extensive customization (with no backup, I know, I know) and I'd hate to re customize everything again. If I can get things right the first thing I'll do is install CWM and perform a nandroid backup.
Click to expand...
Click to collapse
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
regius said:
you don't need CWM, just copy the fix onto external storage card,enter recovery (PWR + Vol. up Buttons) and apply the update from there. just fixed my tablet this way
Click to expand...
Click to collapse
A thousand thanks kind sir, I'm back in business, that was pain free
---------- Post added at 07:29 PM ---------- Previous post was at 07:27 PM ----------
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thanks for posting this, I'm in love with my 7.7 once again.
Appreciate the response stericson. I had purchased your Pro version but even after I fixed the uninstall failed and it also did not detect superuser permissions even though SU gave a notification that Busybox Pro was granted superuser. All other root-requiring apps work. Had to refund the Pro purchase though
No problem. there seems to be an issue with the application detecting root sometimes, that's why you can still try the install.
I'm looking into this issue, it just started showing up so I am not sure what is going on.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Really appreciate this fix. On the verge of wiping out everything....
But decide to see if its busy box since its the last thing i install before all this happens....
Just to note that uninstall busybox also doesnt solve the issue...
so need to fix.
I had a lot of problems with root permissions not being granted by Superuser app. Recently I have tried SuperSu from the market and uninstalled original Superuser app (important to follow the instructions for the App! ).
My main problem was that ntfssd was not granted root permissions at startup, so I had to start it again manually. With SuperSu it is no problem. Also I use Busybox and successfully updated to the latest binary recently.
ginkage said:
Try this fix.
Click to expand...
Click to collapse
Thank you so much for that, I had been driven crazy and had also gone through a factory reset to try and get my device back working, to no avail. Can I ask where you got the ash you're including here? It worked for my Samsung Galaxy Tab 7 Plus, on 3.2, but is it a generic enough file that it can be dropped on nearly all Android devices without any issues arising?
I only ask out of curiosity and understanding the system more.
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
TraderJack said:
I have done s-off via firewater, installed Philz CWM and done SU from there.
For all intents and purposes the system appears rooted (TiBu works, I get toast pop-ups etc).
I am also able to use ES File Explorer to mount /system as r/w.
I have also tried to remount system as r/w via adb shell.
All of these work as I am able to "touch /system/test.file" via adb and then delete it via ES File Explorer.
It would appear the system is writable.
However, when I try to install BusyBox from here:
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
I get "Insufficient storage available" (and I have plenty of space).
I have found this information on modifying the kernel either through a boot.img or a .ko:
http://forum.xda-developers.com/showthread.php?t=2708686
http://forum.xda-developers.com/showthread.php?t=2701816
But both have some indications that they may be out of date and cause problems with the latest release.
I'm not even sure I have to do either of these, because it appears writable from my tests.
It is possibly the busybox program - but that is the one I have used in the past.
I would like to find both a trusted way to install busybox AND understand why I might be getting this problem in the first place.
thanks
Click to expand...
Click to collapse
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
S1L3nTShaDoWz said:
If you do try one of the kernel related solutions do the first one as the second is based on firmware we won't have until next week. Also here is a little trick you can try: navigate from the root directory to /data/data ND look for the Busybox folder and delete it then attempt reinstalling it from the play store. May or may not work but worth a shot.
Click to expand...
Click to collapse
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
TraderJack said:
Well if you read the thread for the first link it looks like people are saying it was for the "older firmware" and people were having issues. I am not sure what "firmware" they are referring to, but the OP closed that thread and I am wary to use that since all of this stuff seems to be back from April and nothing more on it.
What do you mean about the second link not having firmware until next week? I don't see anything in there that talks about a particular firmware version. Also, I found this thread:
http://forum.xda-developers.com/showthread.php?t=2731893
That Rom uses 1.55.506.2 (latest OTA I believe???) and states that it is using flar's method from the second link....so I'm confused by your statements (but want to understand!).
I don't have any busybox folders in /data/data.
I'm having a similar problem trying to install Xposed as well:
"Xposed Installer couldn't be installed. Free up some space and try again"
I'm really not sure what's going on since it appears I have proper s-off and root using the standard methods. I can't believe no one else is trying to do these things on a stock ROM and not having issues :/
UPDATE: I'm thinking you meant the 4.4.3 update coming for us? That second thread has .ko for both 4.4.2 and 4.4.3.
Click to expand...
Click to collapse
Yeah on the kernel my bad, didn't see it had a normal one for non 2.23 firmware users lol, if you don't wanna use that kernel you can always use one of the other ones, maybe Faux's or Evolutionmods kernel. I actually currently use Evolutions kernel and it's quite nice. Also that ROM will work fine I believe, quite sure 1.55 is the latest OTA and if not it doesn't really matter. All though as some people have stated on your previous thread (i think?) you might as well use an optimized stock ROM such as CleanROM or ARHD (Android Revolution HD 8.1), all it is is a stock ROM thats been optimized for better performance and maybe has some tweaks to make it better. To be clear on the ARHD ROM, I stated the version because any higher version than that is for 4.4.3 which we currently don't have the firmware for.
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Glad you got your issue solved!
TraderJack said:
UPDATE:
I went ahead and did another factory reset. This time, instead of using the Philz CMW option for "Re-root System (SuperSU)" I used the supersu.zip to flash superSU.
After that, when I went to try and install busybox and xposed I had no issues at all.
I'm not sure why the Philz option didn't work entirely...as it stated it worked, and appeared to give me root when launching my apps...maybe I should switch to TWRP :/
Click to expand...
Click to collapse
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
Just so you know, when asking the recovery to reroot the system it's going to use the supersu app packaged with the recovery. It's likely a much older supersu app. You're always better flashing the latest version from the recovery itself because you can be sure it's running the latest binaries. If you updated the app from the play store after installation it probably would've worked. It's also possible it simply just doesn't inject the file properly, but a flashable zip always will work.
I can assure you that philz is probably the most updated recovery. It runs very well and does everything it's supposed to do. Are you running the Verizon M8 build or the unified M8 build?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
TraderJack said:
I did update to the latest version...the way Philz works is you choose the "Re-root option" and then it tells you to go and install SuperSU from the store. The only thing I may have done wrong (or misunderstood since it isn't well documented) is this was my "root" as opposed to my "re-root." By that, I mean I rooted originally with weaksauce to install firewater, but I used the Root option in Philz instead of the more discussed supersu.zip flash.
The weird thing about it was that root appeared to work properly. I got toast popups and could use things like TiBu. SuperSU said it was rooted, and Philz was passing the root check.
That should teach me from straying from the guides at all to use a feature not very well discussed.
Click to expand...
Click to collapse
Can't say I ever used that option, it probably just didn't flash it correctly. You may want to post the problem in the recovery thread so they know about it.
In theory it should've worked the same way as flashing the zip. The only thing I could think of is how old the binary was or the location of the flash was incorrect.
Sent from my HTC6525LVW using Tapatalk
Hi Guys
as above. Honor 8 - rooted - custom rom (Tastynoogat) but i cant remove system apps with Tib Backup.
I cant figure out why. Comes up saying System app cant be found.
Any ideas?
you absolutely positive you're rooted? if yes, 99% of time its busybox issue. try pushing the one from this rar to system/xbin.
Yep triple checked. Ive rooted hundreds of devices and it all checks out.
Installed the above and still cant remove apps.
I know root works because adway and quick reboot work fine.
Busybox was already installed in the correct place, Ive reinstalled it there and still cant remove system apps.
cant be 100%, since i didnt use TB to cleanup N, but huawei moved some apps to diff location on N, and TB doesnt recognize those properly (same issue with AdAway). you could try and remove them manually with RE, thats what i did. most of them are on /data partition, so start there
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
You need to install drivers twice.
Mhm, sure.
Though, to be honest, this was among the things I tried before. No difference.
Luxor144 said:
While I know there are other threads regarding similar programs with this rather temperamental app, I didn't find any thread that fit my case exactly, nor one that really fixed my problem, so.. sorry if this is a duplicate.
Anyway, situation is this:
Viper4Android 2.5.0.5 (installed through magisk 20.0, MM 7.3.5) was working perfectly (or atleast somewhat) before recent update. Now that my phone is on Oxygen OS 10.0.1.GM21BA, the driver for Viper fails to install (it says "driver installed, please reboot etc.", but upon reboot it says "please reinstall driver, etc.", and the loop continues).
What I've tried so far:
>Reinstalling Viper - no difference
>Disabling SELinux (both through the Viper itself and through some outside app that might or might not work) - no difference
>Read that deleting audio.fx in vendor/etc/ could fix this problem - couldn't find the file
>Yelling at the phone - no difference
>Also read somewhere that an issue might be that Viper might be denied storage access permission, but the app don't seem to be requesting any permissions at all.
Anyone have any tips or pointers at what else I could check or try? Music just sounds kinda bleh without Viper.
Click to expand...
Click to collapse
Uninstall your current Viper and reboot. Sideload Viper 2.7.1.0 apk or use the Magisk module. Install the driver and reboot. Once back in Android, install the driver again. Should work. If not, go into V4A settings and put in compatibility mode.
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
To repeat my question from another thread, i have the same issue and 2.7 only works for me when the "attach audio effects" option is checked and that introduces quite significant audio lag when skipping tracks.
I also can't seem to get rid of the permanent notification without breaking vipers functionality.
Is there any fix for this? Or a way to properly install 2.5.0.5?
Luxor144 said:
Hmm, installing drivers multiple times made no difference in 2.5.0.5, and yet in 2.7.1.0 that fixes everything. I actually thought Tropical Cactus was just taking the piss. Uehh, this Viper and its esoteric rituals.
Anyway, it works now. Thank you for your help.
Click to expand...
Click to collapse
Lol. Forgot to suggest 2.7.1 and then install drivers twice.
Still an issue in 10.3.4
}{Alienz}{ said:
Still an issue in 10.3.4
Click to expand...
Click to collapse
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
GeekMcLeod said:
I got it working after finding a guide that had to do with audio modification library too. Followed it perfectly and all works. I'll try to find it.
Click to expand...
Click to collapse
Tried to find that one again, too.
I ended up installing the Audio modification library magisk module, rebooting, deactivating (not uninstalling) that module and then installing the current Viper 2.7.1.6 module.
May have rebooted after that before installing drivers and therefore rebooting again, can't remember though.
But it does work perfectly and the guide did go something like this.
Also possible that a Viper update fixed the issue.
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?