So i know im rooted, through Terminal Emulator, cause it gives me a #
but when ever i type adb shell in abd i get $..
My device is recognized and i can push and pull.. i think but whenever accessing the shell, i cant..
help?
You're typing su?
Sent from my HERO200 using XDA Premium App
typed su in TE = #
but in ADB, adb shell = $
which i think is the same thing just different commands.
im goona run the ruu and see if that helps, cause thats really weird to me
ran the latest ruu and got the classy 140 error, yay =]
i hate phones sometimes lol
I'm pretty sure that adb shell should just give you the $. When you open terminal emulator you start there already because you're on the device. If you want root after getting in the shell you type su. Maybe I'm mistaken.
[dpeeps74]
Adb shell gives me the superuser/root (#) without having to give any substitute user command...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kyouko said:
Adb shell gives me the superuser/root (#) without having to give any substitute user command...
Click to expand...
Click to collapse
same here.
hmm, i installed the adb and everything, should i have rooted it through that way? cause i used z4 root?
and when i ran an ruu it give me that wonderful 140 error
fixed it =]
thanks for chiming in
oh nope it changed his mind again, back to $...
davidevan said:
hmm, i installed the adb and everything, should i have rooted it through that way? cause i used z4 root?
and when i ran an ruu it give me that wonderful 140 error
Click to expand...
Click to collapse
When I rooted the phone I used for my screenshot I used z4root as well, so I dunno why it's automatic for mine and not yours :/
You do have a custom recovery flashed correct?
Sidenote
On my phone I get error 140 as well, but it's because of the s-off bootloader so I'm not worried about it - If I need to unroot, I do so through the bootloader using a HERCIMG.zip of the stock sprint RUU.
davidevan said:
oh nope it changed his mind again, back to $...
Click to expand...
Click to collapse
This may or may not help.
Are you using the latest update from sprint?
if so you will actually lose root on reboot. Try an earlier ruu and do not apply the update. That's what I did when I had the same thing happen to me.
Hope it helps.
just fixed it, regaws methos doesnt install a busy box, so i downloaded one off the market and i was set. but i also looked in to your method and that helped as well, thanks =]
Cool glad you got it sorted. It's been ages since I have used adb.
[dpeeps74]
i use it, to install apps directly, and if something goes screwy, its your saving grace. thats only why i wanted it haha
Dav I suggest unlocking S-OFF as well from my understanding that would almost make our phones brick-proof aside from screwing things up when flashing the radio...
http://forum.xda-developers.com/showthread.php?t=759955
Related
!!!!!!!!SOLVED!!!!!!!!
So a few months back I decided to so what all the hype was about and got root and JF 1.51. Everything went smoothly until I saw JF quit and no one was making themes for his stuff. I waited a while but decided to reflash with cyanogen because of the nice themes but low and behold I lost root. I tried the one click thing and it always says failed. So I went back to RC29 and did the whole spiel again... the first time I almost couldn't use the thing. Wiped and all went well until I tried to mod a little more in the terminal. I hit su, got a force close from superuser permissions, and it told me permission denied. I have hardspl, the radio with the long number recommended in every post, and cyanogen's recovery. I figured maybe it got corrupted somehow so I tried again from RC29 on up. It worked for 2 days. Superuser permissions worked like a charm until it just stopped working. I flashed again and the same thing. 2 days good and then boom... permission denied. I tried reinstalling superperms but it told me I can't. Is there something I can do wihout having to reflash every 2 days?
Bump?? Not quite a priority but have been working on this for about 3 weeks now and since I've found nothing googling and only similar problems here I was hoping for any kind of response.
Cyanogen has root..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
maxisma said:
Cyanogen has root..
Click to expand...
Click to collapse
Hopefully that solves your question...
Yeah... I know. It's a patch to keep the security flaw open. I get that part. What I'm saying is that when I use an app to gain root (ie terminal with su, backup for root, or cache to sd and so forth) I get an error saying that superuser permissions needs to close and permission is denied. I want to use su in the terminal emulator. I can't and have never been able to with cyanogen. Worked wonderfully in JF 1.51. Can I reinstall superuser permissions app somehow or bypass it somehow to I can get root? I know the OS has access but I want to have access too.
try this, remove the .zip extension from the file. put it on the root of your sdcard, go to the recovery console and type this
Code:
mount system
mount sdcard
cp /sdcard/Superuser.apk /system/app/Superuser.apk
(or use [B]mv[/B] if [B]cp[/B] doesn't work)
reboot
Thank you so very much David1171. That did the trick perfectly. You are a god among men. Not only did you solve my problem but you also gave me some insight on the system structure. Thanks a million.
siknasa9 said:
Thank you so very much David1171. That did the trick perfectly. You are a god among men. Not only did you solve my problem but you also gave me some insight on the system structure. Thanks a million.
Click to expand...
Click to collapse
i think that is taking it way to far man but yeah anytime you see a command to move something to /system/app/appname.apk with adb that will work for doing it in the recovery console. also i always do it in the recovery console because it is easier to type mount system then it is to type the command to mount system in the terminal emulator.
siknasa9 said:
Thank you so very much David1171. That did the trick perfectly. You are a god among men. Not only did you solve my problem but you also gave me some insight on the system structure. Thanks a million.
Click to expand...
Click to collapse
I am not sure what rom you ended up on, but with the hardspl and cyanogen recovery image it is nearly impossible to lose root unless you specifically want to.
So if you were on rc29 whenever you took the advice and got "su" working, flash a newer rom, like cyanogen 4.0.4. Dont just use rc29 with the super use whitelist app working because it is outdated and there will be problems for you.
rondey- said:
I am not sure what rom you ended up on, but with the hardspl and cyanogen recovery image it is nearly impossible to lose root unless you specifically want to.
So if you were on rc29 whenever you took the advice and got "su" working, flash a newer rom, like cyanogen 4.0.4. Dont just use rc29 with the super use whitelist app working because it is outdated and there will be problems for you.
Click to expand...
Click to collapse
he's on 4.0.4 (from what i ascertain), his superuser.apk got corrupted somehow and wouldn't let him use his root access.
Battery percentage mod by SMABERG
Ive made theese only for myself, but decided to share em cause of demand.
i dont take any responsible for damage to phone or malfunction, theese work on my phone, so they are tested though.
For theese mods to work, and for it to not go into bootloop, you got to put phone in bootloader(power on while holding vol.up) the use ADB from android SDK and run in commandprompt (in windows, startmenu, run, cmd) then input this command. Dont forget to enable usb debuging
adb shell mount /system (thanx for reminding me on this s60mike)
adb push framework-res.apk /system/framework/
A big thanx to theimpaler747 for making this mod work. and also for the gingerbread battery below
NEXUS S - 2.3.2 - STOCK ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- blue-with-black-outline
- green battery gingerbread
- green with black outline numbers
- Green-galaxy-S-style (My favorite )
- green circle
nice thanks!
the blue one is the best
Haven't personally flashed these yet, but wanted to say thanks. Digging the Galaxy S one.
THANKS!!!! I like the blue one
One more thing ^^
maybe you should write that they must enter:
adb shell mount /system
before entering your:
adb push framework-res.apk /system/framework/
Again - Thank you !!!
Mike
i have bionix rom works? it possible flash zip or only work to adb push? thanks
funny... adb does not recognize my device in bootloader mode, but fastboot does.
But when i turned on the phone in usb debugging mode, adb recognise my device.
So with the phone turned on, i used root explorer to set the permissions to /system/framework folder and used the above adb command line and it worked!
out of topic : ADB not recognized in bootloader mode but fastboot does, normal?
the blue one looks really sweet, might have to throw those files into tonight's CM7 nightly framework and give it a shot
It'd be awesome to have a battery percentage mod on the cm nightlies!
foxehkins said:
It'd be awesome to have a battery percentage mod on the cm nightlies!
Click to expand...
Click to collapse
But then you'd have to make one every night
theimpaler747 said:
But then you'd have to make one every night
Click to expand...
Click to collapse
+1 thats a pain
rubino90 said:
i have bionix rom works? it possible flash zip or only work to adb push? thanks
Click to expand...
Click to collapse
only thoose rom's using stock framework from 2.3.2. and only way to be safe is adb.
smaberg said:
+1 thats a pain
Click to expand...
Click to collapse
Trust me, it is
Those of you that have flashed this which one most closely matches the stock gingerbread theme?
Sent from my Nexus S
Bronk93 said:
Those of you that have flashed this which one most closely matches the stock gingerbread theme?
Sent from my Nexus S
Click to expand...
Click to collapse
The one that's named gingerbread
I Got bootloop on GingerS Rom
MrNameless said:
I Got bootloop on GingerS Rom
Click to expand...
Click to collapse
That's because this will only work on the stock 2.3.2 rom
Ahm - you've quoted the wrong line in the first post
adb shell mount /system
not the adb push ...
^^
s60mike said:
Ahm - you've quoted the wrong line in the first post
adb shell mount /system
not the adb push ...
^^
Click to expand...
Click to collapse
He he he, fixed IT...
wultan said:
funny... adb does not recognize my device in bootloader mode, but fastboot does.
But when i turned on the phone in usb debugging mode, adb recognise my device.
So with the phone turned on, i used root explorer to set the permissions to /system/framework folder and used the above adb command line and it worked!
out of topic : ADB not recognized in bootloader mode but fastboot does, normal?
Click to expand...
Click to collapse
Also had the same issue but, since I don't have root explorer, I just used Clockwork Recovery to mount the /system and then use the adb push, worked great!
Congrats on the mod, just what I needed!
Thanks,
Very good, thanks! One thing, on the green battery with the black outline I think the charging image is a little off from the regular icon. While my phone is charging the icon jumps up and down a bit
I want to change the icons for all my apps and APK edit needs the .apk file. Unless there's an easier way to do this.
Adb shell
Would give u terminal
Then su.
Would give you root access
But you could also do ...
Adb pull /where/your/app/is/located
Sent from my SAMSUNG-SGH-I897 using XDA App
^ What he said. You can also use DroidExplorer but in my opinion it isn't the best thing to depend on.
For some reason I just couldn't get adb to work right. Every time I tried to launch it it screwed up and then closed again. I'll try DroidExplorer. If that doesn't help I'll try adb again. Thanks guys.
You have to use a command prompt. You don't just double click it to open.
Hm, when I tried to install DroidExplorer I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BigTortoise said:
Hm, when I tried to install DroidExplorer I got this:
Click to expand...
Click to collapse
Learn how to use adb or go home
Sent from my SAMSUNG-SGH-I777
you could use a root file explorer on your phone and copy all the apks to your sdcard, mount that to the pc, modify the apks, and then either drop all those back in with the same file explorer or make a flashable zip containing all of them...
studacris said:
you could use a root file explorer on your phone and copy all the apks to your sdcard, mount that to the pc, modify the apks, and then either drop all those back in with the same file explorer or make a flashable zip containing all of them...
Click to expand...
Click to collapse
adb pull /system/app/nameoffile.apk
or
adb pull /system/app/*
so much faster.
if you dont learn how to use ADB, you will find yourself up **** creek at some point, if you plan on doing ANY modifications/theming. especially theming, because if you screw up your framework-res.apk, you have no way of fixing it without adb access....
lets not take the lazy ass way out of it here. when you are doing anything to your phone, you should know basic adb commands. if you dont, you shouldnt be touching your phone
This page should help with learning the commands
>>HERE<<
This page is a thread where I had problems with adb on Ubuntu
>>HERE<<
And this is a page that Pirateghost recommends on getting you started with adb
>>HERE<<
Now, we have done about everything we can for at this point, short of coming to your home and doing it for you. Have fun, and be careful out there.
please delete thread
deleted
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
jcwxguy said:
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
Click to expand...
Click to collapse
...what he said, or just use the RUU to go back go stock.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Either way it sounds like you'll be just fine but make sure there's juice in your battery before trying any of the solutions.
ADB Can't find the device :/
deleted
Wipe and reflash rom
Sent from my HTCONE using Tapatalk 4 Beta
raphyv23 said:
I tried to sideload it but adb would not recognize my HTC One. I have installed the drivers correctly on Windows 8 and its recognized as Android ADB Interface under Android Devices on my device manager. when i type adb devices on adb it doesnt come up with anything. I also tried using my Windows 7 Laptop but the drivers wont install on windows 7
Please help :/
Click to expand...
Click to collapse
your cmd window needs to be in the folder with the adb tool, normally something like c:adroid sdk\platform tools navigate to this directory in windows explorer the hold shift and right click on and empty part of the window and select "open command prompt here"
Still wont work
deleted
raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
in your recovery, when your in advanced, did u swip to start sideload? even if it doesnt recognize it, try to sideload a rom anyways, should give u a %
raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
Click to expand...
Click to collapse
are you running as administrator, try typing after that adb reboot bootloader and see what you get
another thing are you using a 3.0 usb port??
It worked thank you
deleted
Does anybody get the prompt for authorizing the PCs that connect through ADB?
According to several articles (example here), whenever a computer connects it's RSA key will be validated and a prompt will appear on the device if it's still not registered:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm running 4.2.2 (10.3.A.0.423 Generic ES) and never get this prompt, despite using the latest ADB version (1.0.31).
/data/misc/adb/ exists on the device but is empty, BTW.
Can anyone else confirm this, or preferably a way to activate the behavior?
UPDATE
I found the problem :victory:
On the /default.prop file (which is part of the kernel and therefore can't be manipulated directly), there's this:
Code:
ro.secure=1
It controls whether adb connections will run as root (if 0) or as shell (if 1).
But there's an additional parameter that should be there:
Code:
ro.adb.secure=1
which if set, triggers the standard behavior described before - prompting for a visual confirmation of the RSA key of the incoming connection.
Once I added an init.d script with
Code:
[COLOR="SeaGreen"][B]setprop ro.adb.secure 1[/B][/COLOR]
everything is working properly.
Bump!
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Sent from my C6603 using Tapatalk 2
kingvortex said:
Apparently the prompt only appears when you issue a command via adb. I would try it for you, but cannot be bothered to boot my laptop just now
If you haven't already, just try adb devices or something and see if the prompt appears.
If you already tried it (I realise you probably have, just throwing ideas around ) and the prompt doesn't appear, Sony probably removed the functionality from their rom for whatever reason (I can't think of any valid reason!).
Click to expand...
Click to collapse
I had tried all that
After digging into the code I found the solution, check the OP.
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Sent from my C6603 using xda premium
gm007 said:
Like this one
http://forum.xda-developers.com/showpost.php?p=43886371&postcount=104
Click to expand...
Click to collapse
It would be useful if I had stumbled on that earlier
Actually, I want mine to be "secure" in the sense that it only allows adb connections from my computer, and prompt for any new ones.
That's what the ro.adb.secure is for.
As for the uid of the shell once you're connected, I want to be root and therefore ro.secure=0.
But since I'm running the stock kernel and can't unlock my bootloader to run a custom one, I use an insecure adbd binary, instead of changing ro.secure to 0.