Database Users

[Q] SU files installed but not giving permission via ADB

I've been trying to fix my kindle fire for a while now. My ultimate problem is that my build.prop is not in my /system/ but I have been trying to push a replacement build.prop to that directory to no avail. It looks like I have superuser installed. Superuser.apk is in system/app/ and there are a few SU directories around my file system.
My problem is that even though I have SU in my file system, I am not getting the correct permissions when accessing the KF through adb. Whenever I type in su it says permission denied. Similarly, whenever I try to change the permissions for /system/ I am denied as well. Whenever I type in su, it says "segementation fault".
It seems to me that there are three possibilities:
1. I somehow have the superuser files in place but the SU program itself is not installed.
2. SU is installed but because I can't fully boot up my KF, I can't give ADB Root access through SU because I can't pull up the "allow access" dialog box.
3. Something stupd like I"m trying the wrong commands.

Maybe your kindle auto updated and broke root? But if you've already updated and re-rooted I'm not sure what the issue would be.
Sent from my Nexus S 4G using XDA App

hmmm...I think a main thing I need to know for sure before I continue is if my phone is even rooted for sure. I have the superuser.apk in system/app. I don't have anything in data/local. I have a SU directory in a couple places. Is there any way for ADB to recognize if a phone is rooted (perhaps if the file system is set up a current way?) without having access to root priveledges itself?

Same here, BurritoRoot, I've tried this on both Linux/Mac, but either way, I can never get su to work so my Kindle can be r/w.

Maybe try
adb shell
$su
If $ changes to # you have root.
When installing su check the file permissions on the directory as well.
Sent from my Kindle Fire using Tapatalk

just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w

b63 said:
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
Click to expand...
Click to collapse
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.

Jessical said:
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Click to expand...
Click to collapse
that command only remounts the system partition r/w - not permanent !
but after issuing the comand:
you can copy files, change permission or whatever
you can also run kfu to permantly root with superuser

Fixxxxxxxxxx!
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue

taseedorf said:
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
Click to expand...
Click to collapse
It just stalls at:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'...
Then nothing.

Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory

taseedorf said:
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
Click to expand...
Click to collapse
How would I do that? I downloaded twrp-blaze-2.0.0RC0.img
I have used the terminal in the past, even compiled stuff like Chrome OS, but I don't know anything except the stuff that people put in the instructions...
Where is the boot.img itself coming from?

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.

Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...

the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop

Did you remember to restore the read/write permissions to build.prop? It should be set to 644.

As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.

I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.

gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium

You dont have access to recovery? Either TWRP or CWM?

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.

gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium

Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.

abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.

sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.

I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk

I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.

would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?

how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk

Possible new way to ROOT

New possible root method on Thinkpad tablet forums, by OPDECIRKEL. He needs help testing it out.
look here and lets cross our fingers =D
http://www.thinkpadtabletforums.com...nt/yareftpt-yet-another-root-exploit-for-tpt/

opdecirkel released the exploit -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/

unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
***EDIT***
updated script worked!

-=HOLLYW00D=- said:
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
Click to expand...
Click to collapse
Not sure if it can help you, but try checking the TPT forum thread again, there has been some advances and troubleshooting going on

Moved To General​
As the first post is just a link and contains no development, this has no place in this section​

updated -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
Someone thinkpadtabletforum reported that it worked for him.

updated script worked for me! cwm installed fine as well!

I achieved root with the new method on OTA 2.5. Also installed CWM with no issues. Works great.
Sent from my PC36100 using Tapatalk

I can confirm it worked!
I had to update first because the "Disable Battery Discharge" option was not there. (I guess my Tablet stopped getting OTA updates since I was on ThinkPadTablet_A310_02_0024_0065_US... Also, you have to update one at a time, you can't go from 24_65 straight to 37_75. Also, I stopped at 39_86 since I was impatient.)
I like this once since we can see how it worked rather than blindly running some guys program (I never tried the first root.)

I can also confirm the new method to be working. Just rooted my 0089_WE TPT. Works like a charm

I am quoting the following post (i don't have privilege to post there): forum.xda-developers.com/showpost.php?p=23902281&postcount=64
daswahnsinn said:
I unrooted and then updated, now I can't root. I updated the SDK and made sure I have the proper drivers needed. So I take back my easy comment. I'll keep trying I might just manually push the files back.
Click to expand...
Click to collapse
How did it fail? At which stage and what error did you get?

Okay, I'll try and flash the oldest update zip, and it fails as it should, then I wipe the cache part, reboot, and I hit enter when I gets to the unlock screen then the CMD window closes.
EDIT: I spent a good hour or so combing through my PC and these forums and tried both methods a lot, and this one finally worked. It wouldn't let me get to the /cache/recovery/pwn/su part of the script. Thank you all for your support.

I have problems...
Hi all,
Apologizes for my english, too bad to discuss this kind of issues. Sorry in advance.
I had the "fantastic" idea to update the firmware some weeks ago, when I was SU. After this, I've lost most of capabilities!
I tried to follow the procedure, but I cannot reach 'root' in any case. I have version WE089. Downloaded US060, but there's only 065 for Western Europe. I got both, just in case..
Unfortunately, in the first step it failed I'm not able to update anything. The process crashes when is loading old firmware, either US060 or WE065.
I've realised that during the process I loose the USB link connection (when I reboot), and the system tries to install again and again the driver. If the TPT is running in recovery mode, it seems that is not connected via USB... If I have the tablet in "normal use", I see it through the Windows Desktop.
Other question: should I disconnect the Internet connection?
I guess other requirements are right (ADBD, debugging mode,...). It's really annoying, it took me a lot of hours and I haven't found any solution.
Can anybody help me? What I'm doing wrong?
Cheers!
jm
W7 64bits - TPT WE089

@jm
goto device manager. right click on Android device. reinstall device driver.
This worked for me in recovery when the device was not recognized.
Edit: look here: http://forum.xda-developers.com/showthread.php?t=1471106&page=2

What do you mean with loosing the connection? Is the adb driver installed correctly? Where did you get it from? Is it an genuine lenovo driver? If so, than you shouldn't worry!
Perhabs it's the MTP driver, that is missing when you boot into recovery? If it's the adb driver, than you should try jlove's method.
In addition I wanted to inform you, that the new method worked for me, too! Even with some complications... by this way, thanks again to opdecirkel!
Because the run.bat script did't worked correctly, I had to do it manually. So I put the "yareftpt" on C:\\, started cmd.exe, booted the TPT into recovery and changed the directory in cmd.exe with "cd.." to "cd yareftpt" ...followed the instructions with the update...
echo 4. Reboot in RECOVERY: (shutdown the tablet, then start it and press volume + few times until it starts in recovery)
echo 5. Go to apply update, select the update from the sdcard and try to apply it. It will fail, but that is OK.
echo 5. Then, go to 'WIPE CACHE PARTITION' and select it (navigate with volume buttons and select it with power button),
echo 6. When wipe cache complete, press (here) ^<ENTER^>.
and after that I copied the first line of the script into cmd and executed. I did it line after line, just to the next step. (dark green= copy line after line, paste and execute)
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
echo 7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete press (here) ^<ENTER^>
pause
some of commands might cause failures, but don't worry and just go on
adb shell "/system/bin/rm /cache/recovery/log"
echo 8. On the device, select REBOOT. When startup COMPLETE press (here) ^<ENTER^>
pause
adb push Superuser.apk /data/local/pwn/Superuser.apk
adb push busybox /data/local/pwn/busybox
adb push su /data/local/pwn/su
adb push pwn-in.sh /data/local/pwn/pwn-in.sh
adb shell "/system/bin/chmod 777 /data/local/pwn/pwn-in.sh"
echo Your PC command prompt appears next. Do the following things:
echo 1. adb shell
echo when '$' (adb shell) appear, do:
echo 2. /cache/recovery/pwn/su
echo when '#' appears. You are root. run the following:
echo 3. /data/local/pwn/pwn-in.sh
now you should try if you have su, even if you don't see in your app list..
download root checker, install, open and try it!
You should have root right now.
In my case, i had root, but no CWM!
So I had to install in manually, but with root it should't be a problem. you only have to download the correct cwm version:
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
then I installed it with the Android Terminal Emulator app, because the cmd.exe method did't worked for me. You should just follow the instructions:
or you can copy img file on /data/local/ folder of your tablet (with a file manager with root permissions)
launch "Android Terminal Emulator" application
and tape the instructions
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
http://www.thinkpadtabletforums.com...nd-development/clockworkmod-recovery-for-tpt/
After a shutdown and reboot into recovery I had cwm! So I am able to do nandroid backups...
In this way, I would particularly like to thank to all devs that made the TPT root possible! Now i like my TPT 1000% more than before...e.g. no status-bar in lecture notes -> sooo great!!

I do get the following error maybe someone can help me out
[*]
[*]
[*]
/system/bin/mkdir: not found
/system/bin/mkdir: not found
cannot create /data/local/pwn-bak/install-recovery.sh.orig: directory nonexisten
t
/system/bin/mkdir: not found
699 KB/s (22364 bytes in 0.031s)
/system/bin/rm: not found
/system/bin/ln: not found
7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete
press (here) <ENTER>
Drücken Sie eine beliebige Taste . . .
it cant find the mkdir command very strange

I'm a little rusty, but are the / and \ facing the correct way? And are you in the correct directory? Not found usually means path is incorrect.

@rangercaptain
thats the commands from the root script. I didnt change them.
the commands are send over from adb shell and the tablet is in root directory i think.
When i go into shell and type in ls i get access denied error.

and you load the update zip and wiped cache before typing the commands, right? You have to do this every time you try to root...
Try to do it with another method. Don't do it directly trough adb shell...just type the shell commands in the cmd.exe
You just have to chance the directory in cmd, before executing the commands.
Then try not to input 'adb shell' before the shortened command, but the whole command as one line like:
adb shell "/system/bin/mkdir /data/local/pwn"
Perhabs it will work..?!?

@neos
yes i do the same procedure.
I also tried over cmd with adb shell "command" and also in shell.
Always the same error.
I looked into the system/bin directory and mkdir does have filesize of 0kb...

[Guide] [L5 II] Root LG Optimus L5 II E450

I had found a way to root L5 II, the method comes from a chinese tool:
1. (The address is in attached file)
Press the blue and white down arrow to download the tool
2. Enable Android debug mode
3. Execute the program, wait for the phone reboot.
4. Rooted!
It works on my e450!

tfe104270 said:
I had found a way to root L5 II, the method comes from a chinese tool:
1. (The address is in attached file)
Press the blue and white down arrow to download the tool
2. Enable Android debug mode
3. Execute the program, wait for the phone reboot.
4. Rooted!
It works on my e450!
Click to expand...
Click to collapse
This works perfectly on my LG E450 too ! But I want to change the Chinese SuperUser to SuperSU, did you try to do that already?
---------- Post added at 09:34 PM ---------- Previous post was at 08:58 PM ----------
Okay, I got SuperSu English version working on my LG E450. These are the steps I have taken.
1) Download SuperSU from the android market
2) Grant Permission for SuperSU to work ( Press the left button on the chinese dialogue )
3) When prompted to update the SU binary, tap on Update
4) Once Update is over, swipe to the Settings tab and select, "Install SuperSU in /system" , option.
5) After Phone restarts, you will find the Chinese SuperUser is not present, but the SuperSU is present.
6) now execute the following command in your terminal or command prompt
---------- For Windows Users ---------------
adb.exe shell "su -c 'mount -o remount,rw /system'"
adb.exe shell "su -c 'rm /system/bin/su'"
adb.exe shell "su -c 'rm /system/xbin/su'"
------------- For Mac/Linux Users ------------
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'rm /system/bin/su'"
adb shell "su -c 'rm /system/xbin/su'"
7) Now Open SuperSU and once again update SU Binary.
If you hve any question, please do reply me in this thread.

No luck on the E460
tfe104270 said:
I had found a way to root L5 II, the method comes from a chinese tool:
1. (The address is in attached file)
Press the blue and white down arrow to download the tool
2. Enable Android debug mode
3. Execute the program, wait for the phone reboot.
4. Rooted!
It works on my e450!
Click to expand...
Click to collapse
Not sure if I am doing something wrong but it seemed to do it however still no root access, thanks anyway

subho007 said:
This works perfectly on my LG E450 too ! But I want to change the Chinese SuperUser to SuperSU, did you try to do that already?
---------- Post added at 09:34 PM ---------- Previous post was at 08:58 PM ----------
---------- For Windows Users ---------------
adb.exe shell "su -c 'mount -o remount,rw /system'"
adb.exe shell "su -c 'rm /system/bin/su'"
adb.exe shell "su -c 'rm /system/xbin/su'"
.
Click to expand...
Click to collapse
edit: my phone has been Rooted now.. by other method will post my tutorial after a few days..
btw thanks for your help..

looking forward to tutorial
alley23 said:
edit: my phone has been Rooted now.. by other method will post my tutorial after a few days..
btw thanks for your help..
Click to expand...
Click to collapse
Looking forward to the tutorial, especially if it will work on the E460, pm me if you can and I will try it on the E460

subho007 said:
This works perfectly on my LG E450 too ! But I want to change the Chinese SuperUser to SuperSU, did you try to do that already?
---------- Post added at 09:34 PM ---------- Previous post was at 08:58 PM ----------
Okay, I got SuperSu English version working on my LG E450. These are the steps I have taken.
1) Download SuperSU from the android market
2) Grant Permission for SuperSU to work ( Press the left button on the chinese dialogue )
3) When prompted to update the SU binary, tap on Update
4) Once Update is over, swipe to the Settings tab and select, "Install SuperSU in /system" , option.
5) After Phone restarts, you will find the Chinese SuperUser is not present, but the SuperSU is present.
6) now execute the following command in your terminal or command prompt
---------- For Windows Users ---------------
adb.exe shell "su -c 'mount -o remount,rw /system'"
adb.exe shell "su -c 'rm /system/bin/su'"
adb.exe shell "su -c 'rm /system/xbin/su'"
------------- For Mac/Linux Users ------------
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'rm /system/bin/su'"
adb shell "su -c 'rm /system/xbin/su'"
7) Now Open SuperSU and once again update SU Binary.
If you hve any question, please do reply me in this thread.
Click to expand...
Click to collapse
How do you type :
- adb.exe shell "su -c 'mount -o remount,rw /system'"
- adb.exe shell "su -c 'rm /system/bin/su'"
- adb.exe shell "su -c 'rm /system/xbin/su'"
in my Command Prompt, thats not working,,,,,,
Please Help Me changing supersu to english!!!!!!!!!!!!!!

Works on e460?
CAn anyone tell me if this works on LG Optimus L5 II (LG e460)???

undon3 said:
CAn anyone tell me if this works on LG Optimus L5 II (LG e460)???
Click to expand...
Click to collapse
I bump this, I would very like to know too!

undon3 said:
CAn anyone tell me if this works on LG Optimus L5 II (LG e460)???
Click to expand...
Click to collapse
Yes this works for LG e460 too. You need to plug into the computer, start the program, wait for it to detect your phone, then click on root.

Rafito123 said:
How do you type :
- adb.exe shell "su -c 'mount -o remount,rw /system'"
- adb.exe shell "su -c 'rm /system/bin/su'"
- adb.exe shell "su -c 'rm /system/xbin/su'"
in my Command Prompt, thats not working,,,,,,
Please Help Me changing supersu to english!!!!!!!!!!!!!!
Click to expand...
Click to collapse
You need to have Android SDK installed for the above command to run. Or else you can download it from the attachments,

subho007 said:
Yes this works for LG e460 too. You need to plug into the computer, start the program, wait for it to detect your phone, then click on root.
Click to expand...
Click to collapse
Thank you very much! I'm assuming you actually tried it, if you didn't may I have the source of that information? You see I really wouldn't like to brick my new phone XD What if it somehow bricks anyway? How do you factory reset the E460?

Divergence-of-B said:
Thank you very much! I'm assuming you actually tried it, if you didn't may I have the source of that information? You see I really wouldn't like to brick my new phone XD What if it somehow bricks anyway? How do you factory reset the E460?
Click to expand...
Click to collapse
Factory reset is something along the lines of VOL-UP+POWER. I've reset a few times accidentally If it doesn't work, it should simply fail though. I can't see how it would brick anything.

spunkylm said:
Factory reset is something along the lines of VOL-UP+POWER. I've reset a few times accidentally If it doesn't work, it should simply fail though. I can't see how it would brick anything.
Click to expand...
Click to collapse
That's what I thought, I had just hacked my old P500 before but since that was a very common phone I was more confident with it, there is a bunch of stuff for the P500 around and pretty much nothing yet for the E460...

spunkylm said:
Factory reset is something along the lines of VOL-UP+POWER. I've reset a few times accidentally If it doesn't work, it should simply fail though. I can't see how it would brick anything.
Click to expand...
Click to collapse
actually it's VOL-DOWN+QUICK MEMO BUTTON+POWER for the E460

Also I'm afraid there are things you can do with root that hard reset can't undo.

mircea89fzr said:
actually it's VOL-DOWN+QUICK MEMO BUTTON+POWER for the E460
Click to expand...
Click to collapse
I knew I was going to be wrong if I posted it. I could do with a list of them for the e460. I usually reboot to recovery through adb. Still want to find a way of enabling fastboot though

spunkylm said:
I knew I was going to be wrong if I posted it. I could do with a list of them for the e460. I usually reboot to recovery through adb. Still want to find a way of enabling fastboot though
Click to expand...
Click to collapse
Do you have recovery on e460? how do you boot to recovery? I would do root if I could backup the entire system partition because if I root maybe I won't be able to install updates from LG.

mircea89fzr said:
Do you have recovery on e460? how do you boot to recovery? I would do root if I could backup the entire system partition because if I root maybe I won't be able to install updates from LG.
Click to expand...
Click to collapse
It's not like a CWM recovery where you can do things like that. It just allows the LG software to flash a kdz as far as I'm aware. You still can't access /system without remounting with root. To boot to it use "adb reboot recovery"

spunkylm said:
It's not like a CWM recovery where you can do things like that. It just allows the LG software to flash a kdz as far as I'm aware. You still can't access /system without remounting with root. To boot to it use "adb reboot recovery"
Click to expand...
Click to collapse
Do you have the kdz for E460? I would need it if something goes wrong.

mircea89fzr said:
Do you have the kdz for E460? I would need it if something goes wrong.
Click to expand...
Click to collapse
I downloaded V10H_00.kdz (02 UK) from here: http://luivit.altervista.org/lg-phone-firmware/index.php?id_mod=23.
See if they have one for your version, but make sure to get the 460 version as their are a few other models jumbled in.

HELP! Wrote to /system and now can't do anything.

Updated: Changed the title cause I'm really stuck here.
Recently re-rooted (seems I have to keep redoing the steps every few days/weeks), I was trying to fix one of the recurring issues of getting 'IMS stopped working' with EVERY phone call I try to make.
A suggested fix was to revert the imsservice.zip file in system/priv-app/imsservice/ with another version. I didn't have the ../imsservice directory so I created it and now my phone is basically useless with non-stop 'IMS stopped working' errors...Even after several factory resets and redoing ODIN.
I can only surmise the issue is that even though I'm doing a Factory Reset, that /system/priv-app/imsservice directory I created isn't getting wiped and therefore causing all the issues. Since I can't get to the directory via GUI, I was hoping I could remove it via ADB but the phone doesn't seem to be able to boot far enough to let me get-in via ADB either ('adb devices' shows the phone, but status is offline so I can't run any commands on it).
I'm at wits end here, any help is much appreciated!

In case anyone else (and for my own records in case I do it again) falls into this trap, here's what I finally figured out and how I fixed it:
It seems I was running an old version of ADB.exe, once I upgraded to the newest version (v1.0.36) I was able to shell into the phone and manually delete the offending /system/priv-app/imsservice directory, reboot and was back to running properly again.
Here's the specific steps:
1. Boot to Recovery Mode.
2. 'adb root' to put the daemon in root mode
3. 'adb shell' to connect to the phone to run commands via command-line.
4. 'su' to change to root user with full root access.
5. 'mount -o rw,remount,rw /system' mount the /system partition to be read/write.
6. 'cd /system/priv-app'
7. 'rm -rf imsservice' to delete the offending directory.
8. 'exit', 'exit', 'adb reboot' to exit out of root, then exit the shell and reboot.

Honestly, I think that your best bet would be to flash stock with odin, see if it boots, then re-root. If not, wipe then try again.

Odin like he said^^
Sent from my SM-G935T using Tapatalk

Binary100100 said:
Honestly, I think that your best bet would be to flash stock with odin, see if it boots, then re-root. If not, wipe then try again.
Click to expand...
Click to collapse
lt.anthonydelgado said:
Odin like he said^^
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
You guys DID see in my original post that I TRIED and RE-TRIED re-flashing with ODIN to no avail, right? If the stock ROM has the imsservice directory, then yes it likely would've worked as running ODIN would've probably overwritten the faulty one I created. Maybe. I don't know because I didn't do that.
But the solution I did find gave me direct access to delete the offending directory (while phone is in recovery mode) and didn't require starting back from scratch with using ODIN.
Thank you for the responses and trying to help though.

Oh wow that's awesome then, well at least we can leave this here in case anyone else runs into the same issue
Sent from my SM-G935T using Tapatalk

Namuna said:
In case anyone else (and for my own records in case I do it again) falls into this trap, here's what I finally figured out and how I fixed it:
It seems I was running an old version of ADB.exe, once I upgraded to the newest version (v1.0.36) I was able to shell into the phone and manually delete the offending /system/priv-app/imsservice directory, reboot and was back to running properly again.
Here's the specific steps:
1. Boot to Recovery Mode.
2. 'adb root' to put the daemon in root mode
3. 'adb shell' to connect to the phone to run commands via command-line.
4. 'su' to change to root user with full root access.
5. 'mount -o rw,remount,rw /system' mount the /system partition to be read/write.
6. 'cd /system/priv-app'
7. 'rm -rf imsservice' to delete the offending directory.
8. 'exit', 'exit', 'adb reboot' to exit out of root, then exit the shell and reboot.
Click to expand...
Click to collapse
Thank you! I thot i was gonna bricked my s7 edge so what happened if we have removed the ims service? anything noticeable performance wise or cellular signal or any trouble receiving and making phone calls? sms? cheers lifesaver! :victory: