Database Users

[GUIDE] Update Superuser From Market FIX!

I am running LeeDrOiD, but I know many people have this issue.
If you are trying to update Superuser from the market, and you get invalid signature and installation fails. This is my work around, which works for me.
My rom had superuser.apk and not Superuser.apk, which linux takes as two files whilst windows references everything in capitals.
Download Superuser Update Fixer.
Run the application, which will say that signature fails. Then run the fix, which will say okay all the way through and the signature still fails.
Download Root Explorer, and mount /system/ as rw.
Go to /system/apps/ and you will find Superuser.apk and superuser.apk, rename or delete superuser.apk and then rename Superuser.apk to superuser.apk.
Restart your phone.
Go to app drawer, and launch Superuser. Your whitelist and blacklist has been erased.
Run Superuser Update Fixer and you should see signature match is okay, now click update from market and enjoy.
- Antony

thanks for your work, can explain what exactly the app is doing?

Is there a free vers of root xplorer?
Sent from my Desire HD using XDA App

snowwhite007 said:
Is there a free vers of root xplorer?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I don't think there is. There may be another app that does this job though. You need something that can mount system rw.
It may be possible to do this step with ADB, however I just posted how I did it.

ES file explorer has this system rw option, it says that it only works with CM and some other rom but it works for me and I'm running leedroid. Only problem is you have to unmount and mount it again every now and then.

Yeah to make it work just select the non CM7 mod option, HIAPK i think it's called? either way just select that one, apart from what the guy above me said about the remounting every now and then, should be a good substitute for root explorer

I downloaded superuser from market and the fix but wen using es explorer i only see one superuser?
Sent from my Desire HD using XDA App

All good now cheerz
Sent from my Desire HD using XDA App

I only have the Superuser.apk, but still have problems on the update. I had lost root and just decided to reroot, but got the Ninja Icon app. I tried to update - sig failed. Tried the Update Fixer and on changing to 644 fail, check sigs fail. Then I tried this.
Any other ideas on how to get it?

Wat rom u using?
Sent from my Desire HD using XDA App

Just updated SuperUser thanks to your guide, cheers mate

similar to the rootexplorer
[free alternative to Root Explorer]
PartTimeLegend said:
I don't think there is. There may be another app that does this job though. t.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
http://code.google.com/p/androotfile/
The ultimate file manager for root users, similar to the rootexplorer,It can access the whole of file system and support copy, cut, paste, delete and rename.The next version will add management and setting functions
Click to expand...
Click to collapse
not me tested

it worked for me ( upgrade from version Superuser 3.07 to 3.2 ) thanks !
it worked for me ( upgrade from version Superuser 3.07 to 3.2 ) thanks !
i just had to delete , the file from the folder ( directory ) the "rename" did not work .
after delete & re-boot , the upgrade and installation worked fine !
thanks again for sharing !
if anyone needs the link for the root system browser [ Root Explorer ] let me know , i found a place with free download .

hi i want to know which is best for desire hd superuser or superSU

Cannot for the life of me get system r/w permissions

I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.

You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.

Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.

no CWM after reboot

hi
Ive rooted my nexus s & unlocked the boot-loader
installed superuser
Ive tried installing CWM a couple of times
it installs
but after reboot no recovery or CWM
checked the following posts but no luck
it says install aborted
http://forum.xda-developers.com/showthread.php?t=1317524
http://forum.xda-developers.com/showthread.php?t=1098168

Read : http://forum.xda-developers.com/showthread.php?t=895545
as far as i remember, CWM will be removed each time you restart your phone,unles you have a custom kernel/rom.
but its been long time ago when i did that x3

If stock there is a file that needs to be removed or renamed,
Sent from my Nexus S using XDA Premium App

Try to flash again.... Works for me...

ghost010 said:
Read : http://forum.xda-developers.com/showthread.php?t=895545
as far as i remember, CWM will be removed each time you restart your phone,unles you have a custom kernel/rom.
but its been long time ago when i did that x3
Click to expand...
Click to collapse
No. You merely need to rename / remove the install-recovery.sh script in /etc to prevent the stock recovery from writing at boot.
Sent from my Nexus S using xda premium

krohnjw said:
No. You merely need to rename / remove the install-recovery.sh script in /etc to prevent the stock recovery from writing at boot.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Thanks I to was having the same issue. I assume that to revert you just rename the aformentioned file back to original?
Sent from my A500 using xda premium

spaz2k7 said:
Thanks I to was having the same issue. I assume that to revert you just rename the aformentioned file back to original?
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Yeah, restoring the file will then cause the stock recovery to be written upon reboot (if you want to go back to the stock recovery for some reason).

same but i solved it
clockworkmodrecovery rom manager find and install
open it and touch flash clockworkmod recovery(first item)
select reboot into recovery manual
mount and storage select
mount USB storage
unmount
++++ go back +++++
install from zip sdcard
find
'' super user.zip'' flash
reboot
es file explorer select setting mark root explorer and mount file system after
select phone in file explorer find etc folder select and find ''install-recovery.sh'' file and rename file for example ''install-recovery.sheski'' and
open rom manager again touch flash clockworkmod recovery(first item)
check it...

system R/W problem after 4.3 update. please help

I updated to JB 4.3 via adb/fast boot and everything went smooth. The only issue I'm having is that when setting up ROM toolbox ad blocker I'm getting an error can't mount system read/write after the host file is downloaded. I installed busy box beforehand and had no problems mounting the system r/w there and also able to mount r/w inside es file explorer. Anyone have any idea what's going on...I'm I missing something?

Did you root ? Which method ? Flash chainfires binary .
Sent from my HTC Explorer A310e using xda app-developers app

Red Devil said:
Did you root ? Which method ? Flash chainfires binary .
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Yea, I rooted. I used a version of super su that is recommended for JB 4.3. I updated the su binaries. There's something keeping the ad blocker from mounting r/w on the / I decided to go back to 4.2.2 for now. I was having another issue with 4.3... I couldn't uninstall the stock launcher through titanium backup. When I tried it said the system apk couldn't be located. I didnt really notice much to speak of in the way of new features in 4.3

Viper4Android not installing drivers.

Hi, I tried to install viper4android sound mod but it is not installing. It says please check if the device is rooted or busybox is installed or not.
I am on PA 17th August and Franco kernel, with busybox and full root naturally. Is there any explanation or solution to install drivers?
I've tried:
°Uninstalling app and re-installing…
°changing Roms and kernels…
°turning on "safe mode" and "compatible mode" in the app
°deleting dalvik cache
°selecting A8 drivers and A9 drivers too (users said both work).
But still it won't install, it gives the same error if someone can be of help, I'd be really grateful thanks!
Sent from my Nexus 4 using xda app-developers app

Jamal Ahmed said:
Hi, I tried to install viper4android sound mod but it is not installing. It says please check if the device is rooted or busybox is installed or not.
I am on PA 17th August and Franco kernel, with busybox and full root naturally. Is there any explanation or solution to install drivers?
I've tried:
°Uninstalling app and re-installing…
°changing Roms and kernels…
°turning on "safe mode" and "compatible mode" in the app
°deleting dalvik cache
°selecting A8 drivers and A9 drivers too (users said both work).
But still it won't install, it gives the same error if someone can be of help, I'd be really grateful thanks!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Make sure that u have installed busybox by opening that busybox installer app, people get confused by installing app only.
Rest I don't know, I have install this mod yesterday only working fine.

mohitgalaxy3 said:
Make sure that u have installed busybox by opening that busybox installer app, people get confused by installing app only.
Rest I don't know, I have install this mod yesterday only working fine.
Click to expand...
Click to collapse
I also have installed busybox through the app too! :/ it still won't work xD
Sent from my Nexus 4 using xda app-developers app

I had this problem as well, try downloading supersu and updating the su binary via TWRP. viper somehow worked after that.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Make sure you have the latest version by updating thru the in app settings. Also, superuser will not work. You must be using supersu for root.
Sent from my Nexus 4 using Tapatalk 4

Jamal Ahmed said:
I also have installed busybox through the app too! :/ it still won't work xD
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
no need install busybox also working perfectly on s2.
flash supersu on top superuser.

i read this post because i have the same inssue on MTK6582 phone...i have root only by irrot aplication and installed the superSU app, updated via Normal mode, but i read somewhere i only can install the viper4 driver if i update my superSU via TWRP, is true? and if i dont have the TWRP installed can i update this way anyway? i dont want my phone get bootloop or anything...plz help!
Thanks

was also having problem with driver installing, updated supersu through recovery, driver was installed successfully but still no effect on audio, driver is reporting Abnormal and not supported.

I'm also unable to install drivers due to busybox error.

Set SELinux to permissive

legodark said:
Set SELinux to permissive
Click to expand...
Click to collapse
Accurately :fingers-crossed:

Tied everything everyone else has tried still same problem including changing selinux to permissive. please anyone have a fix?

Uninstall existing Viper APK. Locate XDA thread with viper_v2.3.3.0.zip in it (it also has 2 more tweak zips) and then first flash viper_v2.3.3.0.zip and then the other two from recovery. This flash wipes davlik cache so it takes some time to rebuild on boot. Then install Viper driver and boot again. Done.

same problem on device never had before
Hjicons said:
Uninstall existing Viper APK. Locate XDA thread with viper_v2.3.3.0.zip in it (it also has 2 more tweak zips) and then first flash viper_v2.3.3.0.zip and then the other two from recovery. This flash wipes davlik cache so it takes some time to rebuild on boot. Then install Viper driver and boot again. Done.
Click to expand...
Click to collapse
I'm having this broken busybox or not rooted completely/correctly error trying to install any version of viper4android as well. I have always had viper on this tablet, latest complete install of firmware is when problem started. But I have tried all fixes as everyone else has including using a cached buybox apk from previous install just to make sure something hadn't changed in Stericson's busybox, no go.
This is a real head scratcher!
Zach

Way late, but fix found
Jamal Ahmed said:
Hi, I tried to install viper4android sound mod but it is not installing. It says please check if the device is rooted or busybox is installed or not.
I am on PA 17th August and Franco kernel, with busybox and full root naturally. Is there any explanation or solution to install drivers?
I've tried:
°Uninstalling app and re-installing…
°changing Roms and kernels…
°turning on "safe mode" and "compatible mode" in the app
°deleting dalvik cache
°selecting A8 drivers and A9 drivers too (users said both work).
But still it won't install, it gives the same error if someone can be of help, I'd be really grateful thanks!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Here is what I found that fixes this:
OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
Even though this file was where it said to copy to, contents were different. Either way, afterwards all I had to do was open the V4A apk and it asked to install driver, BAM........!!!!!!! Worked!
Zach

Dumb question, but have you made sure that you have granted storage permission in the Apps Menu?

coolbeans2016 said:
Here is what I found that fixes this:
OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
Even though this file was where it said to copy to, contents were different. Either way, afterwards all I had to do was open the V4A apk and it asked to install driver, BAM........!!!!!!! Worked!
Zach
Click to expand...
Click to collapse
Thanks Thanks alot for this, i was navigate for hours!!! This really works, thanks ^^

coolbeans2016 said:
Here is what I found that fixes this:
OK all I have a fix for installing Viper on the Tab S.
Use any file explorer and navigate to /system/vendor/etc
Copy the audio_effects.conf in that location
Navigate to /system/etc and paste the file you copied there
Once copied change the permissions to match the other files in the /system/etc folder
Install Viper and it should work this time, apparently the audio.effects.conf file is expected to be in the /system/etc location and is not there by default for some reason....*"
Even though this file was where it said to copy to, contents were different. Either way, afterwards all I had to do was open the V4A apk and it asked to install driver, BAM........!!!!!!! Worked!
Zach
Click to expand...
Click to collapse
OMG DUDE OMG BRO OOOOOOOMMMMMMMFFFFFFFFGGGGGGG. it worked. ****ing love you to death man

driver still not working
my audio_effects.conf file it is system/etc and viper4android is still not installing that driver. please help me

thanks button
K9-1000 said:
OMG DUDE OMG BRO OOOOOOOMMMMMMMFFFFFFFFGGGGGGG. it worked. ****ing love you to death man
Click to expand...
Click to collapse
Don't 4get the thanks button,
---------- Post added at 03:44 PM ---------- Previous post was at 03:42 PM ----------
lukzifer said:
Thanks Thanks alot for this, i was navigate for hours!!! This really works, thanks ^^
Click to expand...
Click to collapse
Don't 4get the thanks button,
---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------
rauul95 said:
my audio_effects.conf file it is system/etc and viper4android is still not installing that driver. please help me
Click to expand...
Click to collapse
like I said, my /etc had the file already as well, but by pasting over it, obviously changed contents, afterwards V4A installed drivers and worked.
I also found another mod that works, V4A FX, is 16ghz, but by downloading and installing V4A XHIFI, then installing the FX over it (you just activate the XHIFI, first check option under settings, then go back to FX), you get 32bit sound! Yeahhhh Baby!!!!!!!!