I installed the latest and greatest Dorimanx ROM. Lite. And everything is going great except the fact i can not use script manager. If i 'adb push' a new busybox file, or even the same one, script manager works but i lose root access. heres the logcat for the launching of SManager .
Nobody has any idea what so ever?
Related
[Q] "Application Not Installed" when trying to get my Gallery3D.apk installed again
I feel like a dope, but I need some help here.
I was testing out some of the alternate Gallery3D builds, attempting to find something that zooms in with higher quality. Those apps have been able to install/uninstall fine using AndroidMate + a good reboot. Strangely, when I try to reinstall the original Gallery3D.apk from my SDcard (I backed it up before doing any of this), I get "Application Not Installed" -- using AndroidMate, Astro, or the built-in installer.
I've also tried "install gallery3d.apk /system/app/gallery3d.apk" from Terminal Emulator (I have BusyBox) installed, but no love. It seems to work ok, but the Gallery app doesn't show up.
Lastly, I don't have ADB going -- as I've never had good luck with that on my Win7 x64 install. Can't I do this without ADB?
Any other ideas??
Thanks,
Yip
I THINK you can just push the apk to /system/app dir and itll work fine. I've done this before with my G1 and had no issues.
Edit: read you didn't have adb, you can try to cp via terminal from the /sdcard/ or something, I have never tried that though.
Thanks. I tried some of that, but without any success. There was also a Gallery3D.odex file in the \system\app folder that I *had* copied prior to all of this, but couldn't ever find where I put it. That MAY have been part of the issue, but I'm not sure.
I ended up restoring an earlier backup (from 2 days ago) and all is well.
Thanks for trying.
Curse these programs that won't use newer su/busybox combinations.
After installing one of the latest blur ROMs, I wasn't able to get webtop2sd to run (a very common problem), nor Cisco's Anyconnect VPN client. webtop2sd did the usual FC, while Anyconnect would complain that it couldn't start a "critical component". Going back to the one I was running before the upgrade didn't help either.
These problems are not unique to the beta, nor this ROM, but here's what I had to do:
Follow the steps in this thread starting in step 6:
http://forum.xda-developers.com/showpost.php?p=21155110&postcount=852.
Total props to dicksteele for the original post. Thought it might be better to put out here since this seems to be a recurring issue on most ROMs now.
Specifically,
6. Install Busybox installer from Market. Ran app installed busybox into /system/bin.
7. Open Root explorer Go to /system/etc mount r/w create webtop2sd directory
8. Go to /system/bin copy busybox over to /system/etc/webtop2sd
9. Still in root explorer, go to /system/bin and /system/xbin and delete su
10. Can't use quick reboot to reboot into recovery because su has been deleted. Wherever your adb is located, run adb reboot recovery.
11. Install the superuser app from the zip I have attached. Reboot.
12. Open some other app besides webtop2sd that needs root. Verify root is working.
13. Install webtop2sd.
14. Open webtop2sd, hopefully no FC's. Do the webtop2sd partitioning and copy webtop over to new partition on sdcard.
Click to expand...
Click to collapse
Yes, webtop2sd was very picky to the point of needing busybox from the installer, not the identical one installed by the ROM. Once I got webtop2sd running, I tried Anyconnect again and it started right up.
I can understand webtop2SD not working since it hasn't been updated for a long time, but a company like Cisco should be sure their tool, available on the Market, works with the latest superuser/busybox combinations.
I would go so far as to say that if you are having trouble with any programs requiring root access, try the steps above used to get webtop2SD working. Hope this helps others stuck on similar issues with these newer ROMs.
Hi, I'm trying to install v5-supercharger on my puny Defy as I have heard wonders about it... however, I can't seem to be able to run it even after doing everything just like ordered.
Installed Busybox 1.19.4
Installed Script Manager.
DL the V6 script.
And that's it... that's as far as i can go as SManager Ads crashes as soon as I run it and su -> sh /sdcard/v6.sh (I moved and renamed my script to root and simplified the name) simply jumps back to prompt.
Any ideas about what might be wrong?
"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.
busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.