Database Develop

Problems with using "ADB shell" to restore custom recovery image (Cyanogenmod's)

Problems with using "ADB shell" to restore custom recovery image (Cyanogenmod's)
I've got the link to fix my problem for being stuck on ADP1 1.6, thanks to many helpful souls out in xda forums
But i got stuck halfway while trying to fix my problem.
1)
"cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line"
grabbed from [GUIDE] ADB, Fastboot, and Nandroid for Noobs
I did not see a '#' but what i saw was a '$' instead.
2)
As i followed a guide from the Cyanogenmod wiki.
I tried doing 'adb root' in my command prompt after doing adb shell but all it says was "adb: permission denied"
Did i do something wrong?
Or is my phone far from repairs?
Any kind soul out there willing to help me out?
I'm just a rookie in these kind of thing.

[MILESTONE] Problem with ADB

Hi
I've got a problem with adb on my Milestone. My phone IS rooted.
When I try to "adb remount", it gives me this:
Code:
remount failed: Operation not permitted
I wanted to install to Froyo YouTube apk. I deleted the old YouTube.apk in system/app with Root Explorer.
Now I've got another problem.
I have to uninstall the old YouTube with "adb uninstall com.google.android.youtube"
When I enter that command, it gives me this:
Code:
Failure
How can I fix this? Thanks for your help!
P.S.
My phone is show when I use "adb devices"

[Q] How to solve logcat problem

Im using CM 7.2 RC1 hero ported to X8 but when i want check logcat it just blank doesn't appear anything.
Anyone knows about it ?
PLease help
Advance thanks.

weird ...maybe it is a problem with the rom or maybe it is a bug

The ROM it's self have logcat in system/bin/
Others all fine but only this logcat give problem....
Actually i was updated rooting system to SuperSU and Binary plus changed busybox to 1.19.4 version and toolbox too.
Do you thing it's happen because of this updating ?

VillainZ said:
The ROM it's self have logcat in system/bin/
Others all fine but only this logcat give problem....
Actually i was updated rooting system to SuperSU and Binary plus changed busybox to 1.19.4 version and toolbox too.
Do you thing it's happen because of this updating ?
Click to expand...
Click to collapse
I am having a similar concern. Mine says "waiting for device", but nothing happens. The logcat file exists but is blank.

jnow2 said:
I am having a similar concern. Mine says "waiting for device", but nothing happens. The logcat file exists but is blank.
Click to expand...
Click to collapse
do you have usb debugging enabled?

fifo171 said:
do you have usb debugging enabled?
Click to expand...
Click to collapse
Yes, usb debugging is enabled. I am able to copy files between pc and phone, push adb commands via terminal, etc. Logcat is the only issue I'm having.

I was able to find help in another forum. My problem was that I was using adb commands through Terminal Emulator. I initially entered "adb logcat > /sdcard/logcat.txt". As long as you type "su" and receive "#" prompt, type the same command above eliminating" adb". It works. Hope this helps!
Sent from my LS670 using XDA

MIT activity manager
jnow2 said:
I was able to find help in another forum. My problem was that I was using adb commands through Terminal Emulator. I initially entered "adb logcat > /sdcard/logcat.txt". As long as you type "su" and receive "#" prompt, type the same command above eliminating" adb". It works. Hope this helps!
Sent from my LS670 using XDA
Click to expand...
Click to collapse
My adb logcat shows:
W/WindowManager( 152): Window Window{2b2f8b10 com.crashapps.easypccontrol_android/com.crashapps.easypccontrol_android.ServersActivity paused=false} destroying surface Surface(name=com.crashapps.easypccontrol_android/com.crashapps.easypccontrol_android.ServersActivity, identity=152), session Session{2b254ba8 uid 10071}
I want to open it in MIT activity manager any ideias?

Is there any way to require adb shell root?

I got the tool "galaxys2_kernel_repack" to modified the zImage which got from the official release and changed the default.prop "ro.secure=0".
Use the kTool.apk write the image to phone. after reboot, the default.prop value has changed. but the adb shell is still in normal mode, not root mode.
Is there any way to require adb shell root?
Thanks for you help.
My devices software version is N7000ZSLPM_TGY

hello,
have you tried this :

ningoune said:
hello,
have you tried this :
Click to expand...
Click to collapse
Thanks for your answer.
I used the stock ICS release by SAMSUNG, not CM release.
As your answer, there is still the normal mode, but can require root shell type the command "su".
I have resolved the problem by flash the speedmod kernel which provide adb shell root. With adb shell root you can use PC Client command like "adb root", "adb remount", "adb push to /system directly"

Aishon A19--have root, sort of, need to install SuperSU

Problem: I have an Aishon A19 tablet, which it is very hard to find information about. It is an RK3288 tablet running Android 5.1.1.
It is not really rooted in the normal sense. However, "adb root" works; I can get a root shell and mount /system as writeable, I can push any app I want to the device, etc.
Things that will not work:
-- I tried to put on a /system/xbin/su (from SuperSU 2.76), with mode 6755 (rwsr-sr-x) and it didn't work. I also made symbolic links to /system/bin/su and /system/xbin/daemonsu. Running it from a non-root shell in adb prints a 1 and doesn't give me root. Running it from a non-root shell on the tablet does the same thing. Running it from a root shell gives me no error, but that obviously isn't much use.
-- Running SuperSU as an app gives me the error message about "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5....." I have no idea if it actually can't see the ./system/xbin/su or if the error message just isn't that good.
-- Trying to use "adb reboot bootloader" or getting into the bootloader using buttons doesn't work. It reboots the tablet into a blank screen, with the same vendor ID and a new product ID; however, "fastboot devices" shows nothing. This happens both under Windows and Linux, and even when run as root under Linux (thus not having to worry about udev rules). This means that I cannot install TWRP unless someone can explain to me how to install TWRP without using the bootloader.
I *can* use "adb reboot recovery" and get into the recovery menu. And as I mentioned, I can get root access to the tablet and a root shell using "adb root", and push any file I want to it.
Is it possible to use this root shell and/or recovery to install SuperSU somehow, even if I have to just copy files one at a time?
Edit: Moderators., you can lock this. Someone had the same problem in http://forum.xda-developers.com/apps/supersu/how-to-manually-update-su-supersu-file-t3238991 and I was able to folloow that, manually running the commands in update-binary.