Database Info

[Q] e signature verification failed installation aborted

OK. I have been searching all over the place, and there were solutions, but my phone will not listen to me.
Instructions
1)Download and extract the file below
2)Use a terminal emulator or ADB shell and type.. (or you can use Root Explorer or SGSTools to mount system RW)
Code:
mount -o rw,remount /dev/block/stl9 /system
3)Use a file manager like Root Explorer and copy the recovery file to /system/bin and replace the one there
4)Now, reboot and you should have a modded 3e recovery with no signature verification
Click to expand...
Click to collapse
On the 2nd part, it will not allow me to mount -o rw,remount /dev/block/stl9 /system.
The terminal emulator is not receiving the "superuser permission", since it's not even asking for the superuser permission.
I did not deny the app nor ignore. I tried reinstalling the terminal emulator, same thing happens.
Also I downloaded ROM Manager. It downloaded me the flashclockworkmod recovery, but it will not reboot into that. Instead it shows the regular recovery mode, and when I try to install the update.zip manually, the error shows again despite the fact that I did all the parts except the 2nd step, because my terminal emulator kept getting denied access when I entered that in.
Please help me. I don't know what hard life my phone is going through.

Asked and answered many times. You could have posted in an existing thread. If your phone is not rooted you will not be able to do this.

My phone is rooted. It has superuser app, along with other apps that require superuser permissions.
How would I have done step 3 without my phone being rooted? if by using root explorer?
I just stated that Terminal Emulator is not receiving the "superuser permission".
I don't know how to manually give Terminal Emulator the "Superuser permission" since, it is not asking me for it, as previously in Eclair.

Are you entering
Su
Sent from my SGH-I897 using XDA Premium App

? I am sorry, I did not understand what you said.
on my Su, I have
Allow
AdFree
ROM Manager
SGS Tools
because they asked for su permission.
But on the terminal emu, it does not even ask for a su permission.

to do unrooted you use adb to push
or root it then use root explorer to drop new 3e fix
try uninstalling terminal em and reinstall. you might have pressed back when it asked the first time, that will screw you

When you mean drop new 3e fix, does that mean to delete file and replace with the updatedone on xda?
I did that previously and rebootseveral times before, but same error came up

Thread closed, already answered.

2.3.4 rooting/recovery Q

Quick question about rooting and clockwork. I managed to gain root on 2.3.3 without using clockwork a while back (i find it buggy sometimes) but the current re-rooting guide for 2.3.4 assumes clockwork usage. Does it matter if I use the procedure in http://forum.xda-developers.com/showthread.php?t=1007782 but bypass clockwork? I.e. using vanilla recovery.

Actually you don't need clockworkmod -- or even recovery mode -- for rooting. The process of rooting is simply putting the su binary into /system/bin directory and install Superuser app.
You could try to install zip from stock recovery, I'm pretty sure it won't hurt even the installation is not successful. For me, I always do the rooting by:
Code:
adb remount
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
Then install the Superuser app from Market.

suksit said:
Actually you don't need clockworkmod -- or even recovery mode -- for rooting. The process of rooting is simply putting the su binary into /system/bin directory and install Superuser app.
You could try to install zip from stock recovery, I'm pretty sure it won't hurt even the installation is not successful. For me, I always do the rooting by:
Code:
adb remount
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
Then install the Superuser app from Market.
Click to expand...
Click to collapse
Does the bootloader need to be unlocked w/this method?

suksit said:
Actually you don't need clockworkmod -- or even recovery mode -- for rooting. The process of rooting is simply putting the su binary into /system/bin directory and install Superuser app.
You could try to install zip from stock recovery, I'm pretty sure it won't hurt even the installation is not successful. For me, I always do the rooting by:
Code:
adb remount
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
Then install the Superuser app from Market.
Click to expand...
Click to collapse
Thanks for that. But for the n00b part of me, could you tell me which directory I need to launch that command from? I.e. which directory of the android sdk.
From memory it was something like c:\program files (x86)\android\android-sdk\tools... or something.
EDIT: mm, I just tried initating those commands from within both the \\tools and \\platform-tools and in both instances I either get "unrecognised command" or "error: device not found" or "remount failed: operation not permitted"; depending on whether the device is fully booted or just in recovery. Any ideas?

Stock ICS Boot Animation!!

Here's the Stock Ice Cream Sandwich Boot Animation for our G2x.
The resolution is a little messed up IMO but it's smooth and works well.
HOW TO GET IT WORKING:
Method 1) via Root Explorer
Step 1) Buy Root Explorer or any other file manager that allows you to mount you /system partition as R/W
Step 2) Download the attached "bootanimation.zip" to your phones sdcard. You will find it in your "Download" folder.
Step 3) Go to /system/media via root explorer and copy your current "bootanimation.zip" to the root of your SD card (this steps for a backup incase you want to revert"
Step 4) Copy the newly downloaded bootanimation.zip from your downloads folder to /system/media (don't forget to remount /system as R/W) Say "yes" to the over write prompt that root explorer shows you.
Step 5) This steps for making sure your permissions are correct. Long press the bootanimation.zip file in /system/media (the one you copied over in the previous step) and select the "permissions" option.
They should be
Owner: Read and Write shoould be checked
The others must only have "read" checked
Reboot and you should be done!!
Method 2) via ADB
Step 1) (not going into the installation of ADB) Open a terminal window and "cd" your way to your SDK directory.
Step 2) Type in "adb root or on a mac ./adb root" this should restart the ADB daemon as root.
Step 3) type in ./adb remount (this remounts /sytem as R/W"
Step 4) This is the step where you push your new bootanimation.zip to /system/media
Make sure you know which directory on your computer the new bootanimation.zip is in
run this command ./adb push /THE PATH TO THE DIRECTORY/bootanimation.zip /system/media
Step 5) Now that the file has been pushed to the correct directory, the permissions need to be changed again.
run ./adb shell
then type su
then cd /system/media
then, this is the command to change the perms chmod 755 bootanimation.zip (the permissions required are 644 but to be safe change it to 755)
Thats it!! YOur DONE!! now just reboot and you will see your shiny new Animation!!

Put the boot animation in /data/local/ so it doesn't get re-written when you flash a new rom, nightly, release, whatever.
No need for permissions editing if you use adb to push the animation, it is only required b/c the sd card file partition is unable to keep the permission information. When using adb, it all works automagically.
There are plenty of free file manager apps that can use root functionality. Also, it is the stock ICS animation that has been out for a while now, http://www.youtube.com/watch?v=ceBI5RJjScQ

thanks it looksvokay
Sent from my LG-P999 using xda premium

Don't forget about the easy method from your phone terminal
Cp /sdcard/bootanimation.zip /data/local
But you have to do it every time you flash a new rom
Sent from my LG-P999 using XDA

i edited the desc.txt to match my screen's resolution and place it under my roms bootanimation directory because default media didnt work but worked out in the end for my htc amaze 4g. thanks!

jerrypcon said:
Method 1) via Root Explorer
Step 1) Buy Root Explorer or any other file manager that allows you to mount you /system partition as R/W
Click to expand...
Click to collapse
Root Browser Lite gets the job done for free. Thanks for the info.

[Q] Mysterious Superuser/root problem

Ok, so this is the problem:
I have a TF101, rooted since 3.2. I have been able to do OTA updates without problems so far, keeping my root with OTA Rootkeeper.
Last week, I tried figuring out how to automatically mount cifs-shares through Tasker. Whatever I tried, the share would not mount through Tasker. It mounted without problems through command line in Terminal Emulator.
Eventually, i narrowed it down to a root acces problem in Tasker, or the Locale Execute plugin, or the secure settings plugin. I noticed that neither of those had ever asked for SU-acces and there were no logs of it in the Superuser app. When downloading other root-needing apps (e.g. rootchecker), I had the same problem: whenever a new app would normally ask for root acces, instead of the usual Superuser-prompt, the app stalled for a few seconds and then gave an error message or just plain nothing. There was no log of this in the superuser app.
When setting the superuser app to 'always grant root', the situation stayed the same: new apps didn't get root, older apps still had root without problems.
While searching for similar occurences on the internet, I saw a suggestion somewhere to clear the cache and data for the superuser app, so I did.
Now superuser still doesn't prompt and NONE of my apps have root. Apparently even the superuser app itself has no root acces anymore, since it fails to get root acces when updating the su-binary.
My guess was that completely removing su and the superuser app and subsequently re-rooting the whole thing would fix this.
I tried unrooting/rerooting through various methods (Brk, Vipermod, this one, and the new Wolf's thingy), but to no avail.
Brk tells me eveything worked fine, but changes nothing, except it gave me an even older version of the su-binary.
Vipermod hangs on "daemon started succesfully" but apparently does nothing even after 10 minutes.
The Asus Backup Utility method changed absolutely nothing
The Wolf's method looked promising, but installing the "Superuser-3.0.7-efghi-signed.zip" failed. (maybe because I did this from CWM recovery instead of his recoveryblob recovery? Dunno.)
So far I can't seem to remove root, as OTA Rootkeeper assures me the superuser app is installed and the device is rooted, even if the root acces is not granted to it (or any other app).
Any ideas?
Update: tried installing SuperSU from CWM recovery to replace Superuser app, but it gave the same 'installation aborted' message. Is this because CWM has no root acces also?
update2: I have root acces through adb shell apparently. I looked here and here for a way to replace the superuser app. I managed to remount /system, delete Superuser.apk and push the Superuser.apk and su from "Superuser-3.0.7-efghi-signed.zip" onto the device.
No apparent change, not even in the su binary version number reported by Superuser app.
I downloaded the standalone su-binary from here too, and replaced /system/bin/su with that one, too, but after reboot the Superuser app still indicated su binary version 2.3.2-efgh.
I don't know exactly when this problem started, but it could have been caused by the recent update from 9.2.1.17 to 9.2.1.21? Is it possible to revert to the previous version? If so, how? Would I lose data/apps?

Type the following in terminal:
ls -l /system/*/su
My guess is that you have two binaries and one or both of them is not superuser with permission rwsr.xr.x

Ensuring CWM working properly, you just try do backup using CWM then, if it worked then it's has nothing to do with being root access problem. And flashing wolf's root zip via CWM is all it takes to regain root after the 9.2.1.21 update.
Mine was similar root access messed after flashing the 9.2.1.21 update. Tried rectified this by copying su from system/bin to system/xbin but still nothing, but my CWM work though and use it to flash wolf's root zip to correct the su missing in the system. Now it work great..
Sent from my awesome rooted Defy: 2.3.6

@gee one
ls -l /system/*/su gives me this:
-rw-rw-rw- root root 22364 2008-02-29 02:33 su
-rwsr-sr-x root shell 26324 2008-02-29 03:33 su
So you're on to sth. Top one is located in /system/bin, lower one is in /system/xbin.
Now what do I do with this? Copy one over the other? chmod? chown?
@farsight73
As said in the OP, I tried flashing wolf's root zip in CWM, but got an error and it aborted. I did the following:
put zip on removable sd
reboot to CWM
choose update from zip
select the right zip
confirm
I also tried this with /system mounted, but same result.
I don't have acces to pc now, I will try more tonight.a

[SOLVED]
Thanks for the replies, you got me in the right direction in that I was replacing the wrong su in the wrong way.
Since Brk Toolkit managed to get me an older su, I thought it could as well give me the right one second time.
I replaced the su and superuser.apk in the /adb folder of the Brk rootkit with the one from wolf's root zip, and then used Brk Toolkit to install su and superuser.
Upon reboot, the problem was solved.
Thanks a bunch!

For future reference, I think you could just elevate to the superuser by typing in terminal "/system/xbin/su" Then you could fix system/bin/su with "chmod 06775/system/bin/su"
Then " exit" should drop you to a normal shell, and "su" will promote you in the usual way.
The issue here is that xbin and bin are both in your path, and bin is probably first, so the non-super version is "found" first. "echo $PATH" will reveal your path variable.
sent from my transformer

gee one said:
For future reference, I think you could just elevate to the superuser by typing in terminal "/system/xbin/su" Then you could fix system/bin/su with "chmod 06775/system/bin/su"
Then " exit" should drop you to a normal shell, and "su" will promote you in the usual way.
The issue here is that xbin and bin are both in your path, and bin is probably first, so the non-super version is "found" first. "echo $PATH" will reveal your path variable.
sent from my transformer
Click to expand...
Click to collapse
HEY MY FRIED I HAVE EXACTLY THE SAME PROBLEM
chmod 06775 /system/bin/su results"unable to chmod /system/bin/su: readonly filesystem "
echo $PATH RESULTS /system/bin/su: /system/Xbin/su
COULD U HELP ME WITH ZIS MY FRIEND
10Q

From adb or the terminal, type in "/system/xbin/su" to elevate to the superuser. Then mount system to read-write and delete the /system/bin/su version. Remount system as read only.
This will work if you have two versions of su and one of them is not really super.
sent while running with scissors

[Solved] Replace KingUser with SuperSU and Binary Update fix

Hey everyone,
I'll be showing you the easiest way to replace Kinguser/KingoSuperUser or any other superuser app with SuperSU.
Procedure:
1. Download & Install ES File Explorer
2. In ES File Explorer menu ☰ , scroll down and enable the Root Explorer option
3. Now click on Homepage > Device > System > app
4. Once you're in the system/app folder, look for Kinguser.apk or KingoSuperUser.apk or any other Superuser apk that you have.
5. Delete that Superuser.apk, and go to Playstore and install that same Superuser app. Once installed, uninstall it from Playstore.
6. Now download and install SuperSU and update binaries via normal mode.
7. After 2 to 5 minutes, your binary will be updated, SuperSU will be installed correctly and now reboot your phone.
Note: Do not worry, deleting the SuperUser .apk will not unroot your phone. And this is also a fix for binary update issue.

MSalmanKhan17 said:
5. Delete that Superuser.apk, and go to Playstore and install that same Superuser app. Once installed, uninstall it from Playstore.
Click to expand...
Click to collapse
I don't understand that step. I rooted with KingRoot but this App isn't on playstore.
So I deleted the .apk, installed new from my downloaded apk and uninstalled with Titanium Backup.
The SuperSU still complains that it cannot replace the su-binary.
Any idea?
My phone is a Honor 4X Che2-L11 with an ARM Cortex-A53 Processor.

tosho1 said:
I don't understand that step. I rooted with KingRoot but this App isn't on playstore.
So I deleted the .apk, installed new from my downloaded apk and uninstalled with Titanium Backup.
The SuperSU still complains that it cannot replace the su-binary.
Any idea?
My phone is a Honor 4X Che2-L11 with an ARM Cortex-A53 Processor.
Click to expand...
Click to collapse
I followed the manual steps that Supersu says when installing the app (redirects to a web). It says there are 2 options, the other is installing Supersu-Me, but I haven't tried that (there seems to be issues for Lollipop). Also, in my device there was only one Kingo Superuser app and a Kingo Link app (I have seen webs where Kingo installs up to 3 things).
You need root (Kingo), su binary file, busybox, terminal emulator, ES explorer, supersu app.
Step 1: Install ES explorer with root.
Step 2: Rename Su to .SU
Step 3: Copy .SU to system/xbin
Step 4: Authorize .Su. For that, open terminal and type:
system/bin/su
mount -o rw,remount -t rootfs rootfs /system
chmod 777 /system/xbin/.su
Step 5: delete the other SU files, such as ksu, etc.
# check attributes
busybox lsattr /system/xbin/su
# remove a and i
busybox chattr -a /system/xbin/su
busybox chattr -i /system/xbin/su
# remove su
rm /system/xbin/su
Step 6: Rename.SU to SU
Step 7: Go back to the desktop to delete the other authorization apps, uninstall KingoRoot,
open SuperSU, it should ask to update binaries, choose yes, choose NORMAL, and reboot.
Hope it helps!

where is file ,
pzl upload the su file here,
and ur procedure is not understanding
properly ,
plz give procedure how to do this ,
or upload video,

@tosho1 its because huawei protect system partition on locked bootloader devices.
reflash stock rom, root with kingroot, flash twrp with rashr, unroot inside of kingroot and flash supersu with twrp
(you will be able to unroot because system is still mounted after rooting but after reboot you wont be able to touch it, thats why you have to use kingroot only to flash twrp and then remove it when you are still able to)
(method tested and working on my own che2-l11)

Thanks for your reply MarcoPLs.
Meanwhile I managed to get root working flawlessly. Don't ask me, how It's too long ago.

hijackerdev said:
where is file ,
pzl upload the su file here,
and ur procedure is not understanding
properly ,
plz give procedure how to do this ,
or upload video,
Click to expand...
Click to collapse
What worked for me was finding older version of kingroot app and rooting with that then using super SU me.apk

Replace kingroot with supersu
Here you will learn how to replace kingroot with supersu
Replace Kingroot With SuperSU