Anyone had experienced in using busy vi command before?
Please help.
The busybox vi editor is very different from the original. I can not switch from command mode to insert mode from ADB shell.
I've got the same problem.
I would like to be in adb shell and run busybox vi. But for some reason the ESC doesn't seem to take and I'm stuck in insert mode or something.
I have tried using busybox vi but gave up.. Its different from the original vi..
Sent from my U20i using XDA App
Related
ok so on most roms this happens. i need a SU request but my phone freezes obn a black screen and on the top in gray it says SU request. i wait paciently and maybe 1-2 mins later is asks to FC because its not responding. is there a fix or what am i doing wrong. usb debugging is on and so is install nonmarket apps idk wtf im doing wrong or if somthing is just not working. any input??
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Marisa said:
I've heard su is not working properly until you activate it once via adb. In your teriminal (cmd or similar)
Code:
adb shell
$su
You should get a working super user request after which all other su requests should work fine.
Click to expand...
Click to collapse
yes same thing happens to me
plug in your phone
goto your android sdk tools
and input adb shell
now go back to your phone and try it while still plugged
thats what i have been doing...
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
WalkingTaco said:
the same thing is happening for me and the instructions of simply input adb shell into terminal arent helping really. if someone could tell me exactly where to be aiming the command prompt and what the exact commands are in order to fix this I would greatly appreciate it.
Click to expand...
Click to collapse
Are you getting the same crshes and things, but when you do the adb shell # pops up instead of $?
whenever i do adb shell I get #, so that means SU is already activated, but it's actually not on my phone, so i have no idea what's going on and no one seems to know how to fix it.
no. my Su permissions always force close after a minute of black screen. there is a fix posted above but my nerd level is not high enough to.infer the rest
Sent from my Eris using the XDA mobile application powered by Tapatalk
I don't know the exact command prompt setup, I'm running linux. However, when you originally rooted your phone you used the Android SDK correct?
With your phone plugged in, and USB Debugging enabled on your phone (Settings -> Applications -> Development -> USB Debugging) Open command prompt and get to the tools directory you used during rooting, I don't know where you installed it, so I cannot guide you through that part. If you used Ivan's guide http://forum.xda-developers.com/showthread.php?t=647707 it's probably best to refresh yourself there.
Once you've found your SDK /tools/ in command prompt, it should be as easy as running the code I mentioned earlier
Code:
adb shell
$su
in the command prompt.
The superuser prompt should show up on your phone, tell it to allow it and it should work without fail until you flash a new ROM that has the bug.
thanks very much. I used Ivans guide. I rooted it yesterday when o got my replacement from Verizon in store. I had been using the 2.1 leak on my old one and complained in store for thirty seconds. they didn't even look at it gave me a replacement in ten minutes
Sent from my Eris using the XDA mobile application powered by Tapatalk
Rock out thanks for the Super Help
hey guys i'm having problem in adb when i put the remount command
it gives this message : opreation remount not prometted
why is that??? i'm rooted on ba023 and a lot of programs that use su is working correctly
h.boushi1987 said:
hey guys i'm having problem in adb when i put the remount command
it gives this message : opreation remount not prometted
why is that??? i'm rooted on ba023 and a lot of programs that use su is working correctly
Click to expand...
Click to collapse
Try typing 'su' (without inverted commas) before that command, when using your phone, and on a PC, do 'adb shell su' or 'adb shell' then 'su'. The command should now work.
You have to do this, if you followed the 'secure root' instructions before.
thanks man it works!!!!!
Sent from my X10i using the XDA mobile application powered by Tapatalk
I tried loading the Aria into an adb shell, then tried the reboot command (just "reboot"). It replies "reboot: no such tool".
I also wrote a quick script with GScript and ran it with su permissions (my phone is rooted with clockworkmod, and liberated), and the same message showed on screen.
I also made a separate script that just runs "ls /system/bin" and I can clearly see the "reboot" command in the directory. Again, when I try to run /system/bin/reboot with su priveleges, it gives the same message.
I'm tempted to think that the reboot command in /system/bin simply runs the command "echo reboot: no such tool". Does anyone have any more information about this? I'd like a script that would use the reboot command to reboot into recovery mode.
I believe you should be able to use "shutdown /r" to reboot the phone.. probably needs to be done with sudo though..
jleehey said:
I tried loading the Aria into an adb shell, then tried the reboot command (just "reboot"). It replies "reboot: no such tool".
I also wrote a quick script with GScript and ran it with su permissions (my phone is rooted with clockworkmod, and liberated), and the same message showed on screen.
I also made a separate script that just runs "ls /system/bin" and I can clearly see the "reboot" command in the directory. Again, when I try to run /system/bin/reboot with su priveleges, it gives the same message.
I'm tempted to think that the reboot command in /system/bin simply runs the command "echo reboot: no such tool". Does anyone have any more information about this? I'd like a script that would use the reboot command to reboot into recovery mode.
Click to expand...
Click to collapse
I can reboot the phone using ADB by typing adb reboot... Or in terminal on the phone itself I su and then enter reboot and voila...
Not sure if this helps or not.
Edit: I am also running CM6 which has busybox installed.
The way I do it from shell is to type 'exit', this takes you out of shell. Then I type 'adb reboot'
Your path is probably not correct on the device. To change the path you need to edit init.rc and add the correct path.
I have had this same problem and now think that the tool unrevoked is messing the path variable up.
Let me know what you discover.
Same
I also have the same problem. I checked init.rc and i didnt find something about reboot. I run S5 Sensenation ROM. I will check again, But i happy to see that im not the only one who have the problem.....
Hi everyone, i need a little help.
While in adb i was about to do some modding and i entered adb shell, so as soon as i het enter i also started typing su.
well now when i enter adb shell i dont just get the # sign.
mine looks like this ~ #
no commands can be found now.
How do i get back to the default directory?
Thanks
hackit said:
Hi everyone, i need a little help.
While in adb i was about to do some modding and i entered adb shell, so as soon as i het enter i also started typing su.
well now when i enter adb shell i dont just get the # sign.
mine looks like this ~ #
no commands can be found now.
How do i get back to the default directory?
Thanks
Click to expand...
Click to collapse
Type 'cd /' without the quotes.
Did the default.prop file get changed?
I've been searching for many threads on how to uninstall chainfire 3d on adb, but as of now none of them are working, I have a samsung galaxy s3(GT-19300). My phone is rooted, Ive installed chainfire3d-pro-v3.3.apk , heres what I've been doing as of now.
1.I already run adb on cmd.
2.I type adb shell and got the # sign.
3.I type "cd /system", got pass through, that until "cd /lib" but when i, type "sh cf3d_uninstall.sh or sh /cf3d_uninstall.sh" It say sh cant open cf3d_uninstall.sh.
Why is that and what am I doing wrong? Is there a way to know where the location of cf3d_uninstall? Or is there any other way on how to fix the boot-loop caused by chainfire?
Thank you in Advance
PS: typing sh /system/lib/cf3d_uninstall.sh does not work for me either.