[Q] Busybox won't install. - X 2014 Q&A, Help & Troubleshooting

I can't get busybox installed. I get the following error:
"I am unable to verify whether or not certain utilities needed for this application to run are present and functional on your device.
This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured. Please try the install again."
This is a Moto X 2014 US Pure Edition that was rooted with this guide: http://forum.xda-developers.com/mot...e-edition-superboot-style-root-motox-t2889264
I can't create TWRP backups either with version 2.8.4.0. I get errno=13 Failed to make backup folder.
What can I do?
Thanks

Ok so I got busybox installed by first installing it with this installer https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
Then I used the normal installer here https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
TWRP still isn't working though :/

Related

installing busybox failed,please help me.

When I was following http://forum.xda-developers.com/showthread.php?t=1327599 for my first time rooting, I encountered problem in Step 5. (Install Busybox.)
After I pressed install in the bottom, an error message poped up
Installing BusyBox v1.20.1 failed
We have detected that your system cannot function with this version of busybox.
Please try installing a different ROM or fixing your system.
Error.
reloc_library[1311] : 9287 cannot locate 'android_reboot'...
CANNOT LINK EXECUTABLE.
Please help me, I am noob on android and extremely confusing in the moment. Thank you in advance:good:
Try to install this one instead. If that does not work make sure you system partition is not full (by uninstalling some useless system apps first.)
Thanks it worked!:highfive:
I will try to install rom later.

[Q] LG G3/ arm v7a not compatible with xposed??

hello,
I once installed xposed on LG G3 via recovery before the updated version.
it was working, but only when i changed to permissive.
now with the updated xposed, when i try to install from the app itsef it says my phone not compatible.
"Xposed is not (yet) compatible with android SDK version 21 or your preccessor architecture (armeabi - v7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by "/data/data/de.robv.android.xposed.installer/chache/app_proccess"; caused by library "libdvm.so" not found"
i saw other writing about their d855.. it means the problem is on my phone?
anybody had this issue too?
also i cant remove xposed, says it cant find a backup.
thanks !
I am by no means an expert so the following is only related from my experience,no warranty is implied or given, but this was the first rom I have flashed etc and I only did it last night
Once I put lollipop on to my phone as per this post xposed would not install via the app itself after reading the various threads I found this
[OFFICIAL] Xposed for Lollipop followed the instructions and xposed was installed.
Not sure if I went wrong somewhere but this threw up an issue with lgquickcover not working , some more reading found this booted to recovery using the power/volume key method and flashed the zip from here and the issue was resolved
I think it is worth mentioning xposed is only at alpha at the moment and as such some modules ( in particular g3tweaks I miss it ) do not work
working here. (lg g3, d855, blisspop v2.1 with selinux status already set to permissive)
xposed should say
Xposed on LG G3 D855 - error armeabi and libdvm.so - update ?
hi there,
any update regard this ?
I'm able to install / uninstall the "Xposed install" app but, cant get it install/update due to those errors:
Xposed is not (yet) compatible with android SDK version 21 or your preccessor architecture (armeabi - v7a)
CANNOT LINK EXECUTABLE: could not load library "libdvm.so" needed by "/data/data/de.robv.android.xposed.installer/chache/app_proccess"; caused by library "libdvm.so" not found"
a[[_process - 58
xposedbridge.jar - 54
Phone is root
Android 5.0
core 3.4.0
V20h-ISR-XX
is there a workaround or something ?
i had similar problems on my g3 (d855) on lollipop, then i tried this:
http://forum.xda-developers.com/lg-g3/development/tool-installer-xposedlg-g3unofficial-t3094514
and problem solved. good luck !!!
tnx, working process... still have some problems
when pressing install I'm getting a black screen and an error
"Parse error, failed to mount sd card (unknown error 150) and failed to map file. installation aborted."
attached picture
when rebooting system, I have the xposed app installed but not working, asking for restart, but noting happen after soft or hard rest.
ludstr said:
when pressing install I'm getting a black screen and an error
"Parse error, failed to mount sd card (unknown error 150) and failed to map file. installation aborted."
attached picture
when rebooting system, I have the xposed app installed but not working, asking for restart, but noting happen after soft or hard rest.
Click to expand...
Click to collapse
as i can see in the picture you are using CWM. I did it with TWRP. you can try....
hi @ludstr and @rhystagram
i found another solution. you need to install xposed for lollipop 5.1 instead of xposed 5.0. here is the link: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Hi , I once flashed xposed in my g3/D855 stock rom and get cover error so I renamed lgcover.apk in twrp recovery and problem solved , now I changed my rom into cm12.1 and NOT instaled xposed , is there any way that I can make my smart cover work again ? if not would restoring to stock rom make the cover work again or ... ?
ludstr said:
when pressing install I'm getting a black screen and an error
"Parse error, failed to mount sd card (unknown error 150) and failed to map file. installation aborted."
attached picture
when rebooting system, I have the xposed app installed but not working, asking for restart, but noting happen after soft or hard rest.
Click to expand...
Click to collapse
As I can see you don't have a custom recovery, like TWRP, first you need to do is root "if your phone is rooted then skip this" then download an app called "Flashify" then go to this thread and download the latest TWRP and make sure it is unziped, http://forum.xda-developers.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
then open Flashify, Grant for root access, then select flash recovery and then select the recovery boot.img file and flash it after that you should be OK.
then try and flash the xposed framework zip and you should be good to go
hope this helped you
PS see this before flashing xposed
http://forum.xda-developers.com/lg-g3/general/how-to-xposed-running-properly-stock-t3030261

[ROOT][6.0][XT1097] Systemless root for Moto X 2014

Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.
glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good
** Duplicated **
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?
glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092
oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!
oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.
guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?

[MM 6.0] Modules don't work even tho the installation was successful

Hi all!
So I recently bought a Cubot Max but cant get any Xposed Modules to work!
Specs:
Cubot Max
Android 6.0
FW v11
arm64
I got the zip and apk off the official thread and used the latest sdk23 arm64 version obviously.
I mainly need the modules "Youtube Adawy" and "Youtube background playback".
But for the sake of testing if the issue is a result of incompatibility I also installed the modules
"PinNotif" and "SlideBack".
None of them worked.
The UI of "SlideBack" seemd to work properly while the UI of Youtube Adaway said that the app was not actived, even tho i tried it several times.
The log file read "cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT" so i created the missing txt file and gave it - rw rw permissions.
Does anyone has a clue what causes this problem?
greets
wambooo23 said:
Hi all!
So I recently bought a Cubot Max but cant get any Xposed Modules to work!
Specs:
Cubot Max
Android 6.0
FW v11
arm64
I got the zip and apk off the official thread and used the latest sdk23 arm64 version obviously.
I mainly need the modules "Youtube Adawy" and "Youtube background playback".
But for the sake of testing if the issue is a result of incompatibility I also installed the modules
"PinNotif" and "SlideBack".
None of them worked.
The UI of "SlideBack" seemd to work properly while the UI of Youtube Adaway said that the app was not actived, even tho i tried it several times.
The log file read "cannot read log/data/data/de.robv.android.xposed.installer/log/error.log: open failed: ENOENT" so i created the missing txt file and gave it - rw rw permissions.
Does anyone has a clue what causes this problem?
greets
Click to expand...
Click to collapse
Exactly I am also facing the same problem.
Same here
Can we have a thread to get the Cubot Max working with Xposed? A 500+ page general thread is difficult to follow. Thanks!
Success!
I did it! This is what I did.
The problem is that there is a firmware error which affects a number of MTK6735 phones and stops Xposed from working. You have to install another module called grorkmod first, but this will not work if you have previously tried to install Xposed. So what I did was set the phone back to its initial state (after backing up data etc.).
1. Download the Custom TWRP and the Cubot Max official ROM from here:
mod edit: link removed
2. Unrar the official ROM, and, using SP Flash Tool, set to "Format and Download", Flash the ROM in full. You will now have an unrooted, untouched factory-set phone.
3. When I did this, the Firmware version (Build Number) was V04 — check this through your system settings as my phone originally arrived with Build Number V09. So, after unzipping the TWRP download, I had to use the older version of the Scatter file. So use SP Flash Tool again, and Flash TWRP and reboot the phone, you will have an unrooted phone but with TWRP installed. Do the usual stuff with becoming a developer and changing the necessary permissions.
4. Now you can transfer files to your phone's memory.
UPDATE-SuperSU-xxx,zip
grorkmod_v1.1+lite.zip
xposed-v87-sdk23-arm64.zip
XposedInstaller_3.1.1.apk
5. Boot to Recovery, and, from TWRP:
(a) Install UPDATE-SuperSU-xxx.zip but do not reboot.
(b) Clear Dalvik cache etc
(c) Install grorkmod do not reboot.
(d) Install xposed — this time reboot.
6. Run your file manager and attempt to install the .apk file. If you are diverted to give permission for this, change the settings and do it again.
Hope this helps.

[HELP] Magisk SuperSU Not installed and no binary >> VTR-L09

Hi everyone. So like the title says I finally got my P10 running EMUI 9.0.1.186 and got the pie version of Resurection Remix installed and working smoothly. So now I am trying to get root back which is annoying because currently there is no TWRP for EMUI 9+. So I followed the tutorials on installing magisk without custom recovery using the recovery_ramdisk partition which I finally did get figured out.
What I did:
I downloaded stock firmware (Exact same version as the one installed on my phone) and then extracted the RECOVERY_RAMDIS file and transffered it to my phone, then in Magisk Manager I installed and selected the option to edit a file. Selected the RAMDIS file and then transffered the file back to computer. I did the fastboot flash of recovery_ramdisk and then reboot my phone and it says installed on both Magisk and Magisk Manager. Safetynet check all green aswell. Basically everything that should be green is. I then installed directly because it gives you that option now and after booting the phone again I tried some root required apps but nothing was asking for root permission and I cant use the apps. In the Supersu section of Magisk Manager there are no apps coming up to allow me to enable supersu for the app or not. I can install Modules though and that does work as I tested it by downloading and installing the busybox static module. I then went to root checker pro and did a check and it says busybox is installed correctly. When I do the check for root status it comes back as follows:
Feedback Mode: Install Root
Issue: Not installed superuser app and su binary, and unable to access root user account.
Feedback: Locate a guide for root installation on a Kirin Treble device.
Stage 1 - Superuser App: Not Installed
NOT installed: SuperSU by chainfire, Superuser by ChainsDD, or Superuser by Koush
Stage 2 Superuser Binary Files: Not Installed
Alternative Location
Command: ls-l /sbin/su
Result: lrwxrwxrwx 1 root root 8 2019-12-29 13:49 /sbin/su-> ./magisk
Version: 20.1:MAGISKSU
Analysis:
The rest of the Alternative Locations came back as "does not exist"
Stage 3 - Root User Account Error
Error: Timeout of 27 seconds on 2 attempts
Optional - ADB Shell User
Status: Checked /default.prop for ro.secure setting: No world/other read access to fault.prop
Additional - SELinux
Status: Unable to determine due to lack of permission, no world/other read access to /sys/fs/selinux/enforce
Please help me figure out why I dont have full root access, Thankyou very much!
(I would also like to note that I did try uninstalling by just restoring the partitions via Magisk Manager Uninstall option and then reinstalling and this time not using the direct install feature and nothing changed)

Categories

Resources