Hi all,
Busybox Installer is simple way for install Busybox in CWM Recovery!
Only G900H *LOLLIPOP, Might be These do NOT work on the G900*, use with caution!
Requirements:
- Recovery CWM
INSTRUCTIONS:
1. Copy attached zip to sdcard.
1. Turn off your phone
2. Press and hold Volume UP + Home + Power.
3. install it.
Source
In instructions, why did you mention "Copy attached zip to sdcard"?
I mean, Do our G900H model support SD card in recovery mode?
My phone is G900H 4.4.2 KK and rooted.
after i instal busybox from PS then use smart install, everything seems OK. But when i restart, all applications that load at boot force close (Home.apk etc. etc.) and i have to factory reset. This my second time i factory reset because at 1st i never thought if the force close problem caused by busybox. I realized after 2nd reset because the only one app i instaled was busybox and i restarted the phone then FC.
Anyone facing this problem? Now my phone don't have busybox instaled from PS and android commander also can not read my root even adbinsecure already set.
Please help..Thanks in advance
Related
I have a Samsung S4 with Android 4.3 and CWM. It was rooted with CF-Auto-root.
I decided to update SuperSU to the latest version 2.0.
1. First I activated the cleanup function from the SuperSU menu to be able to reinstall it from Google play.
I downloaded and installed it. It displayed "The SU library needs to be updated" then it displayed "How would you like to install the SU binary?". I choose TWRP/CWM button because I have CWM.
During automatic reboot into CWM recovery it installed something and then rebooted normally.
It didn't work. SuperSU displayed "The SU library needs to be updated" again.
2. I chose "Normal" button in SuperSU when it asked for binary install.
It failed to install again.
3. I downloaded SuperSU zip package (UPDATE-SuperSU-v2.00.zip), booted to CWM recovery and installed the zip file.
After I rebooted and tried to run SuperSU - it didn't work. It displays "The SU library needs to be updated" again!
Now I can't even uninstall SuperSU because it's not in the list of downloaded apps.
I can't even access its settings to do a cleanup and remove it.
How to make it work correctly or uninstall it completely?
Any suggestions?
Nasvyazi said:
I have a Samsung S4 with Android 4.3 and CWM. It was rooted with CF-Auto-root.
I decided to update SuperSU to the latest version 2.0.
1. First I activated the cleanup function from the SuperSU menu to be able to reinstall it from Google play.
I downloaded and installed it. It displayed "The SU library needs to be updated" then it displayed "How would you like to install the SU binary?". I choose TWRP/CWM button because I have CWM.
During automatic reboot into CWM recovery it installed something and then rebooted normally.
It didn't work. SuperSU displayed "The SU library needs to be updated" again.
2. I chose "Normal" button in SuperSU when it asked for binary install.
It failed to install again.
3. I downloaded SuperSU zip package (UPDATE-SuperSU-v2.00.zip), booted to CWM recovery and installed the zip file.
After I rebooted and tried to run SuperSU - it didn't work. It displays "The SU library needs to be updated" again!
Now I can't even uninstall SuperSU because it's not in the list of downloaded apps.
I can't even access its settings to do a cleanup and remove it.
How to make it work correctly or uninstall it completely?
Any suggestions?
Click to expand...
Click to collapse
I have this problem too. I have tried all three methods on cwm, trwp and philz. Anyone got a fix?
I am using broodplank's aosp 4.4.4 build.
Nasvyazi said:
I have a Samsung S4 with Android 4.3 and CWM. It was rooted with CF-Auto-root.
I decided to update SuperSU to the latest version 2.0.
1. First I activated the cleanup function from the SuperSU menu to be able to reinstall it from Google play.
I downloaded and installed it. It displayed "The SU library needs to be updated" then it displayed "How would you like to install the SU binary?". I choose TWRP/CWM button because I have CWM.
During automatic reboot into CWM recovery it installed something and then rebooted normally.
It didn't work. SuperSU displayed "The SU library needs to be updated" again.
2. I chose "Normal" button in SuperSU when it asked for binary install.
It failed to install again.
3. I downloaded SuperSU zip package (UPDATE-SuperSU-v2.00.zip), booted to CWM recovery and installed the zip file.
After I rebooted and tried to run SuperSU - it didn't work. It displays "The SU library needs to be updated" again!
Now I can't even uninstall SuperSU because it's not in the list of downloaded apps.
I can't even access its settings to do a cleanup and remove it.
How to make it work correctly or uninstall it completely?
Any suggestions?
Click to expand...
Click to collapse
It's not in the the list of downloaded apps bc when you flashed " (UPDATE-SuperSU-v2.00.zip)" it made it a system/app..so therfore the delete it.. download a root explorer and delete it from system/app..
I wouldn't install 2.0 again after you delete it.. maybe try 1.94 or something a little lower and not so new
Sent from my SCH-I605 using XDA Free mobile app
lacoursiere18 said:
It's not in the the list of downloaded apps bc when you flashed " (UPDATE-SuperSU-v2.00.zip)" it made it a system/app..so therfore the delete it.. download a root explorer and delete it from system/app..
I wouldn't install 2.0 again after you delete it.. maybe try 1.94 or something a little lower and not so new
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply.
Should I delete SuperSU's data as well?
Is it in the folder "data/data/eu.chainfire.supersu" ?
It's a long story, but I'll have to tell it so you can understand exactly what happened.
I was toying around with some system files and ended up in a bootloop. So I made a new kitkat ftf file that I flashed in flashtool, then I installed the advanced kernel for twrp and finally I installed a prerooted lollipop zip in recovery that I made with prf creator. When I first booted the device the su binary didn't work, so I had no root acces. I booted the tablet in fastboot and installed advanced kernel for twrp again (over lollipop), then I wiped everything and flashed the prerooted firmware again, plus the supersu zip to make sure it works.
This time root works and everything seems to be ok, except that the device doesn't recognize the internal storage.
I think it's mounted, but the system can't see it. Installing apps from Google Play works, I even installed dungeon hunter which required additional files (which are normally installed in android/obb) and it works fine. But if I try to download anything from the web it says "no SD card".
If I open the preinstalled file manager from Sony it shows that I have 5.3/11gb occupied, but if I press on it it's empty.
Same story on root explorer, with superuser access granted.
What could be the problem? How do I fix this?
as it is asked quite often, here's how you get ota with a modified stock rom.
For example, ota will fail if you have root (as it changes your boot partition slightly) or if you deleted some preinstalled apps (e.g. chrome browser). OTA script always checks the signatures of your running rom and the ota update. If they don't match, it will fail.
An unlocked bootloader does not prevent ota from working!!!
requirements: a backup of a 'clean' stock rom
So if you want to update perform the following steps (edit: you can find a second and easier method at the end of the post)
1. boot twrp
2. backup everything to be safe (boot, recovery, system, data) if something goes wrong
3. restore 'clean' stock boot partition and recovery partition
(4. if you changed something in 'system' restore system as well)
5. boot tablet
6. download and install ota - it should succeed
7. boot twrp and restore data again if needed
(8. root again with magisk)
good to know:
if you restore partitions, make sure they are from the same build! if not, tablet might not boot or ota will fail again.
if you are rooted, you can use the the backup of boot created by the magisk script (-->/data/stock_boot_<sha1>.img.gz)
if you don't have a backup, try to get hands on a stock rom and flash the required partitions manually (e.g. fastboot flash boot.img etc..)
good luck
(if anyone knows a better way, let me know and i will add it here)
edit: @MarkAllen provided this method which is far more simple (but which unfortunately has never worked for me by now).
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser and Magisk manager from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
MarkAllen said:
I was rooted from the last February security update. I was under the impression I would be able to allow the April security update to download then copy it on the root of my internal or sdcard storage then boot to normal recovery to install. I've done this with other devices I own (Shield Tablet and TV) and seemed to work fine for them. You would just re-root later when done. Anyway as you noted this didn't work on the Yoga Book though due to changes rooting makes on this device.
How I ended up doing this was a bit different then you describe, but meets the same end as your instructions I guess? All I had done was uninstalled root, ran OTA update (which worked this time), then rooted again and it worked great.
1) Boot TWRP and install "Magisk Uninstaller"
2) Clear cache and Dalvik cache in TWRP then reboot
3) Uninstall phh's SuperUser and Magisk Manager
4) Start OTA update and follow instructions
This completed no problem for myself and then I just re-rooted again
5) Boot TWRP and installed Magisk 12
6) Clear cache and Dalvik cache then reboot
7) Install phh's SuperUser from the play store
8) Launch SuperUser and Magisk manager each one time (for some reason root checker claimed root was not installed properly until I did this)
9) Check root using root checker
Click to expand...
Click to collapse
great to hear...
using the uninstaller alone has never worked for me...it always aborts...sometimes it complains that some files are missing or were changed, the recovery partition doesn't match the expected one, etc...
mostly i can't remember which things i've done to the rom/system.
but again, good to know that magisk uninstaller works, it definitely is less complicated and time consuming.
Hello , the issue that i have is that my phone only boots to the logo screen ALLVIEW and with powered by android below it , the problem started when i tried to manually delete busybox (It constantly gave me an error when unistalling from the app itself , and it also on apps gave me the No busybox installed! pop up message) I found an thread , it had the instruction to make the /system read and writeable r-w through root browser and then i could THEORETICALLY delete the busybox file inside /system/xbin and install it again . I did this and after i set /system as Readable and writeble the phone froze and gave me an black screen with the clock frozen and the mobile data frozen aswell. It wouldnt respond to just pressing the power button so i took the battery out and tried to bootup . At first it went to logo screen , suddenly restarted and then go to twrp . Now it boots to the logo screen and stays like this.
Can I fix it in any way ? I have an stock rom zip , but it doesnt see it in twrp .
BigVy said:
Hello , the issue that i have is that my phone only boots to the logo screen ALLVIEW and with powered by android below it , the problem started when i tried to manually delete busybox (It constantly gave me an error when unistalling from the app itself , and it also on apps gave me the No busybox installed! pop up message) I found an thread , it had the instruction to make the /system read and writeable r-w through root browser and then i could THEORETICALLY delete the busybox file inside /system/xbin and install it again . I did this and after i set /system as Readable and writeble the phone froze and gave me an black screen with the clock frozen and the mobile data frozen aswell. It wouldnt respond to just pressing the power button so i took the battery out and tried to bootup . At first it went to logo screen , suddenly restarted and then go to twrp . Now it boots to the logo screen and stays like this.
Can I fix it in any way ? I have an stock rom zip , but it doesnt see it in twrp .
Click to expand...
Click to collapse
Hey, seems like you are having a soft brick.
You shouldn’t delete busybox manually as it might be part of the system services, you need to factory reset. Busybox might be meant to OVERWRITE system files instead of adding new files. Busybox requires root for special permissions, and you should uninstall it properly inside the busybox app. Make sure to connect to computer while it is in TWRP, backup everything important. It’s also good to have automatic backup enabled on your device. If factory reset doesn’t help, try formatting your system partition and flash a clean rom.
Well fixing this issue wouldn’t be hard, but if you are experiencing a HARD BRICK(not likely), you surely need to contact your OEM. Just in case. But I don’t see the point why are you uninstalling busybox whether by it’s space or performance.
Sincerely,
HippoInWindow20
Sent from my iPhone using Tapatalk
HippoInWindow said:
Hey, seems like you are having a soft brick.
You shouldn’t delete busybox manually as it might be part of the system services, you need to factory reset. Busybox might be meant to OVERWRITE system files instead of adding new files. Busybox requires root for special permissions, and you should uninstall it properly inside the busybox app.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
The reason why i was unistalling it was because apps would display the message that busybox is not propely istalled or not present at all , the app wouldnt unistall busybox , giving me an error .
I have an question , i do have an zip of the stock rom right out of the box , but i cant find a way in twrp to flash it.
BigVy said:
The reason why i was unistalling it was because apps would display the message that busybox is not propely istalled or not present at all , the app wouldnt unistall busybox , giving me an error .
I have an question , i do have an zip of the stock rom right out of the box , but i cant find a way in twrp to flash it.
Click to expand...
Click to collapse
No, you shouldn't flash the stock rom , you should flash a custom rom instead and completely wipe the system partition.
BigVy said:
The reason why i was unistalling it was because apps would display the message that busybox is not propely istalled or not present at all , the app wouldnt unistall busybox , giving me an error .
I have an question , i do have an zip of the stock rom right out of the box , but i cant find a way in twrp to flash it.
Click to expand...
Click to collapse
You can try to flash the stock rom of the device using adb sideload.
Hello Guys, New Member Here And I Want To share This little Guide Will Help To fix Auto Reboot and Auto Installing Apps So Follow The Guide Carefully ( This Guide Is Needed A Rooted Device)
Note : This Guide Is Specially For Revo Based Roms,Lollipop Version
For Auto Rebooting Phone
Method For Recovery (Team Win Recovery Project)
First Turn Off Your Phone, Then By Pressing And Holding Power Button and Volume Up Button You Are Now In The Recovery Mode Click Advance Then Click File Manager, find Data/app/then Find The App That Cause To Auto Reboot Your Phone..Then Hit Home Button Then Reboot To System..Done
So My Phones Problem Is Theres a App Name : SystemFtools, Tools Etc.....These Apps Are Malware Or Auto Installing Apps so I Investigate The Directory of This Moment so i Discover That the Way to Install That Apps Is From The Fm player, ( Your Right What You Read) Fm player but not all fm player Is Like This So You Need To Disable or delete That App using Rootexplorer Or Other Root Filemanager
So Delete Also the Auto Install Apps....Done....So That apps Will not Installing Again Because You Delete The Way To Install That apps...Sorry To My Grammar. Enjoy