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.
Related
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Hitman3984 said:
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Click to expand...
Click to collapse
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
EDIT: Nevermind I see that there are 2 different root methods and one uses SuperSU. Sorry
shojus said:
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
Click to expand...
Click to collapse
I used the file from imnuts, which used superuser and not supersu.
I went ahead and deleted superuser, xbin/su and am reflashing. hope this fixes the problem.
which worked until the phone randomly rebooted and got stuck in loop..
and it was either sdpeed increase or lbe privacy guard causing it.
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
Ive even removed superuser and installed supersu and doing the all apps mod was causing this issue.
I have a feeling it could be because I was renaming the services.odex file before replacing it.
Trying a direct overwrite was causing a non stop bootloop I couldn't get out of 4 seperate occassions.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
100% agree! I have not used Superuser for ages... Far superior imo...
shojus said:
100% agree! I have not used Superuser for ages... Far superior imo...
Click to expand...
Click to collapse
after rooting I feel like the touch screen has lost some sensitivity. not sure if it's just me and the day or I'm just loco.
and what I mean specifically is when flipping through my home screens they like to snap back now and then.
Hello everyone, first (third, actually, but anyway..) post here.
This morning I installed this wonderful ROM (Beanstalk 4.4.2), and got stuck into a little issue:
With the moving from Android Tweaker to Android Tweaker 2, I've decided to remove the older app (I did not like it anyway, but that is another matter), since last update made it useless. And here comes the problem: I can't.
I've tried with Clean Master and it says fail, I've tried with Titanium Backup and it says complete but the app is still right there (and it also "works"), I've tried via command line: pm uninstall atweakerfree.apk, says he can't (obviously, all of them had root access, and I was "su" on the last one).
I also had the same problem with two of the 3 launchers coming with the ROM, once I've decided which one to use, but in some way, after enabling ADB root access, Clean Master made it through.
Android Tweaker just seems to be unremovable, also tried to remove BeanStalk Explorer (I prefer other file managers), and failed here too.
Any help? I'll be forever thankful.
Maybe You could delete the apk from /data/app (or /system/app) via Root Browser?
Or reboot to Recovery, mount /system and run Aroma Filemanager?
zg85 said:
Maybe You could delete the apk from /data/app (or /system/app) via Root Browser?
Or reboot to Recovery, mount /system and run Aroma Filemanager?
Click to expand...
Click to collapse
First advice did the trick, thanks and solved!
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
Hello,
I have a Samsung Galaxy S6 Edge SM-G925W8 and had SuperSU root access and XPosed Framework installed. I am now attempting to remove all of it so that I can pass Google's safetynet helper test. I have tried numerous things, but the safetynet result is always:
SafetyNet Request: Success
Response Validation: Success
CTS Profile Match: False
I first attempted to remove Root by clicking "Completely remove root" within SuperSU. After doing this, Response Validation was false, which, after doing some research, I learned was caused by XPosed Framework. I then boot into TWRP recovery and flash the Xposed uninstaller. This causes my phone to boot loop, forcing me to restore a NAND backup to before I removed anything. I then try to flash the XPosed Uninstaller BEFORE removing root access and it runs successfully. After this, I use SuperSU to completely remove all root, which also runs successfully then give the phone a reboot removing the app entirely. This is when I receive the SafetyNet Helper response above stating CTS Profile match is false. I'm not sure how to fix this error.
Any suggestions would be very appreciated! Thank you
Edit: I have no idea why this thread appeared twice...sorry I can't seem to delete one of them
Er.. Any ideas?
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
vgplayer54 said:
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
Click to expand...
Click to collapse
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hello, I attempted to use ES File Explorer to search both the system/bin directory and the system/xbin directories. system/bin does not have the "busybox" or "su" files in them, so I assume they were removed when I uninstalled SuperSU. /system/xbin however does have these two files, but I am unable to delete them. I get the error "Cannot delete file". I'm guessing this is because I've already unrooted?
I then opened the terminal in my TWRP Recovery, however when changing directories into the system folder, the terminal shows that it is empty. when using ls -la, only two files are there, both called root and neither can be opened. rm -r /system/xbin/busybox does nothing either, it claims there's no such directory. Any suggestions? or just wipe?
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.