Root Explorer FC's on my rooted Bionic! - Motorola Droid Bionic

I'm running th3ory's 1.2x rom and every time I try to open up Root Explorer it force closes right after superuser accepts permissions. Any idea on what's going on here?
UPDATED: i was running wrong version fixed it thx

Related

[Q] New Market in 1.1 Stock?

Is there any possibility to get the new market (2.2.11 or 2.2.7) to work with the B&N Stock 1.1 image (rooted with gapps already)?
greetz,
fattymcdirty
Just need to get the apk and install over the included market. There was a thread with it and the old one in a thread not to long ago
Sent from my MB300 using Tapatalk
actually this doesn't work.. i took the 2.2.7 market apk and pushed it to /system/app/ - then rebooted. after that, market opens for 1sec and then just closes back to the homescreen. same with 2.2.11 - any other suggestions?
Thread moved to General.
fattymcdirty said:
actually this doesn't work.. i took the 2.2.7 market apk and pushed it to /system/app/ - then rebooted. after that, market opens for 1sec and then just closes back to the homescreen. same with 2.2.11 - any other suggestions?
Click to expand...
Click to collapse
The APK should be "Vending.apk". Use Root Explorer or ADB to remount system as Read/Writable, then rename your old Vending.apk to "Vending.old" or something (just incase you want to go back). Copy the new market "Vending.apk" to /system/app. IMPORTANT: Change the permissions of the Vending.apk to match the other APKs in the directory. Reboot.
If after a reboot you are having some problems try clearing the Market's cache.
EDIT: I'm running 2.2.7. Haven't tried 2.2.11 since this is working perfectly fine for me on nootered BN 1.1.0.
could you upload the market version 2.2.7 you are running at the moment?
then i'm gonna give it another try..
hmmmmmmmmmmmm ....... :/
What is the difference between the different versions of the android market?
question now to anyone: has anyone the market 2.2.7 working on the nook with rooted stock 1.1? if so: could u please upload your vending.apk???
My market updated by itself yesterday to the newest one.
V 1.1 stock
And it works much better than the old one
k4str0 said:
The APK should be "Vending.apk". Use Root Explorer or ADB to remount system as Read/Writable, then rename your old Vending.apk to "Vending.old" or something (just incase you want to go back). Copy the new market "Vending.apk" to /system/app. IMPORTANT: Change the permissions of the Vending.apk to match the other APKs in the directory. Reboot.
If after a reboot you are having some problems try clearing the Market's cache.
EDIT: I'm running 2.2.7. Haven't tried 2.2.11 since this is working perfectly fine for me on nootered BN 1.1.0.
Click to expand...
Click to collapse
On my froyo SD card install, i cannot get this method to work. I have replaced the APK there with the newest one (2.3.2 actually), but it makes no difference; the system still sees it as 2.2.11, and trying to do an "install" doesn't work either.. hmm
any update on this? can we get a newer market on rooted 1.1?

[Q] New Android Market crashing, unable to install old one

Hi Everyone,
Looking for help for an issue, I installed the new android market and was messing around with Titanium Backup (forgot to backup the app, dumb me!) anyway I tried to uninstall the new market to go back to the old one but when I did this the market app is gone from the manage apps area. My phone is a N1, running 2.3.4 and rooted, this what I have tried:
- Install the old market manually from a downloaded vending.apk, not working crashes to .com.android.vending every time
- After this I went to look in the /system/app folder for vending.apk and the app is not there, neither I am unable to copy the app using Droid Explorer or Root explorer, it says it is coping the app but is not there
- Re-install gingerbread update again to see if it gets the app back, did not work, still not in system/app folder
Does anyone know why I am unable to copy the vending.apk to the system/app folder? the phone is rooted but still can-t
Thanks!
If you're having problems with root permissions, try using ROM Manager to fix permissions. Another possibility could be busybox, so I recommend installing the version with Titanium backup (under the Problems? section of the menu).
Updating the market can be tricky, but I always find wiping data from Google Services Framework and (use app manager) Market (easier to use Titanium), and rebooting helps. Make sure you reboot before trying to use the Market...
I didn-t know about the Fix Permissions feature of ROM manager, I tried it and it work, I can now place the file on the system/app folder.
Thanks a lot!

Root Explorer force closes on my bionic!!!

I'm running on my rooted bionic with th3ory's 1.2x rom and every time I try to open up Root Explorer it force closes right after superuser accepts permissions. Any idea on what's going on here?
UPDATED: i was running wrong version fixed it thx

root explorer problems...

im having a problem mounting r/w in system apps for root explorer anyone else had this problem or any success in getting it to mount properly..I hit the button and nuthing happins..I am fully rooted running latest version of thriller rom..
daddy4life09 said:
im having a problem mounting r/w in system apps for root explorer anyone else had this problem or any success in getting it to mount properly..I hit the button and nuthing happins..I am fully rooted running latest version of thriller rom..
Click to expand...
Click to collapse
Go into superuser and clear root explorer. When you open root explorer you should be asked again to give su permissions.
If that doesn't work go to /system/bin and make sure you have a file called 'su'.
Sent from my LG-P925 using Tapatalk

SuperSU and ES File Explorer on Lollipop

I'm on a rooted Nexus 4 with Lollipop and SuperSu v2.20. I've noticed that ES File Explorer does not request root permissions nor is it listed as one of the apps in SuperSU even though its installed and working fine. I've tried reinstalling ES but it still does not ask for root persmissions in SuperSU. There are other root apps that are going thru SuperSU fine. Anyone else experiencing this issue?
shobuddy said:
I'm on a rooted Nexus 4 with Lollipop and SuperSu v2.20. I've noticed that ES File Explorer does not request root permissions nor is it listed as one of the apps in SuperSU even though its installed and working fine. I've tried reinstalling ES but it still does not ask for root persmissions in SuperSU. There are other root apps that are going thru SuperSU fine. Anyone else experiencing this issue?
Click to expand...
Click to collapse
Install latest version of SuperSU (2.23) and latest version of ES (3.2.3).
Srandista said:
Install latest version of SuperSU (2.23) and latest version of ES (3.2.3).
Click to expand...
Click to collapse
Thanks for the response. I was already on ES 3.2.3. I update SuperSU to 2.23 but still having the same issue where ES does not go thru SuperSU.
shobuddy said:
I'm on a rooted Nexus 4 with Lollipop and SuperSu v2.20. I've noticed that ES File Explorer does not request root permissions nor is it listed as one of the apps in SuperSU even though its installed and working fine. I've tried reinstalling ES but it still does not ask for root persmissions in SuperSU. There are other root apps that are going thru SuperSU fine. Anyone else experiencing this issue?
Click to expand...
Click to collapse
I had this issue so deleted and reinstalled ES File Explorer, but now I just get "ES File Explorer isn't responding".
I've Googled this error but no one else seems to be getting it.
So, I have switched to FX for the moment, till ES fix the problem (or I discover what is causing it)
Did you go under the tools tab and turn on root browser? I don't have lollipop so i can't try it out myself.
jhuebert95 said:
Did you go under the tools tab and turn on root browser? I don't have lollipop so i can't try it out myself.
Click to expand...
Click to collapse
This worked for me, thanks!
Yeah no prob! Make sure to turn on show hidden files. It really comes in handy. Ive actually had some issues with ES lately where it corupts apk files when you manually push them to /system/app. So be careful its been a real pain in the butt...

Categories

Resources