Database Users

Permission issues with su and rom .3

Hey guys,
Im new to Android and after being a BlackBerry user for 8 years, anyway heres my issue.
1. I did the root rom per the instructions...no problem
2. flashed the recovery and have that working...no problem
3. downloaded the .3 rom with the built in busybox and su...Here's where things get confussing for me.
I tried to use adb and it asks me (are you root?), tried adb remount and got (operation not permitted) the usb debug is on and working and the su app on the phone maintains a black screen....(I think this is not right...)
Then I closed out the current cmd window...opened a fresh cmd window and typed>adb shell and got $, then i entered su and got # from here im stuck, what are the commands to get back to adb shell and su also how do I get the whitelist permissions working...
In short adb shell worked fine with the original root rom, I'm sure its an operator error any help is appreciated.
Chris

SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.

t2noob said:
SO if I understood correctly you already have v3 installed?
If you do check on your phone its probably asking you for permission on the phone when you click on always allow the command should go thru adb.
make sure you have debuggin on otherwise all you will get is a black screen when su permission pops up.
Click to expand...
Click to collapse
can you guys post a walk through for noobies? imstuckat black screen

vash8806 said:
can you guys post a walk through for noobies? imstuckat black screen
Click to expand...
Click to collapse
There are plenty around... seriously google it. But, this specific issue I just experienced. Seems on the custom ROM that is out (EvilEris) the SU request screen doesn't work right off the bat. I went and used an app on the device to request root (terminal) then when the black screen pops up, hit back or home, or action. As the phone is basically frozen at this point it prompted me to forceclose the superuser.apk. I did. Once forceclosed, it worked fine.

adb shell
su
look at phone, click allways all
...
..
.
jcase

jcase said:
adb shell
su
look at phone, click allways all
...
..
.
jcase
Click to expand...
Click to collapse
Or just download Terminal Emulator from Market.
open it up.
Type su.
Hit allow/always allow.
Now try it for other stuff (like wireless tether) and see if it pops up instead of a black screen.

haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]

vash8806 said:
haha..I simply went to settings>Applications>Development and checked the USB debugging mode.... [read it on another thread...should have read before I posted...haha]
Click to expand...
Click to collapse
niiiice

Problem with adb

Im tring to push a bootanimation.zip through adb but when i type adb remount is says operation failed
Can any help?

Did you try
adb kill-server
adb start-server
If that doesn't work try rebooting the phone.
If that doesn't fix it, Google it. I think that's the fix though.
Sent from my Burnt EVO via the XDA app.

I always use Pushboot. Its a simple batch file that does everything for you.
http://forum.xda-developers.com/showthread.php?t=701295

Hey thanks for the help...the pushboot killed my bootscreen but i got it back. Ill have to see what i can find out googleing it.....i know i have full root since im running the wireless tether and i get the # when i su.

trizzcuitt said:
Hey thanks for the help...the pushboot killed my bootscreen but i got it back. Ill have to see what i can find out googleing it.....i know i have full root since im running the wireless tether and i get the # when i su.
Click to expand...
Click to collapse
There's 2 pushboot files in the folder. Did you use Pushboot2?

Yup i used pushboot 2 since im rooted.....unless i read the instructions incorrectly.

Anyone going to do a 1 click root ?

Non of the rooting methods are working for me.

What is not working? I was having difficulties as well but found a workaround.

I have rooted and flashed my Vibrant but cannot understand the directions enough to attempt to root the Nexus S. I have tried hooking the phone up to adb which is installed on my PC but it does not recognize the device and says permission denied. I am confused do I use adb? Do I use fast boot ( which I have no idea how to use)? I have used Terminal Emulator on the Vibrant and my Nexus One but you have to have root to use it. I know I am not very educated in these matters but any all help would be greatly appreciated, other than I should take the phone back and get a refund as I am not bright enough to own one!! Which I have been told.They may be right LOL LOL

In my opinion, the creators of wonderful one click rooting apps like z4root, universal one click root, visionary etc. should try to integrate support for nexus S in their upcoming builds.

aliwaqas said:
In my opinion, the creators of wonderful one click rooting apps like z4root, universal one click root, visionary etc. should try to integrate support for nexus S in their upcoming builds.
Click to expand...
Click to collapse
These root options use a security exploit that don't work anymore on Gingerbread (tested yesterday on IRC #NSdev)

What no more one-click roots! Err....

I get adbwinapi.dll not found when I type fastboot devices

siberslug said:
I get adbwinapi.dll not found when I type fastboot devices
Click to expand...
Click to collapse
I was just lazy in setting up my ADB/Fastboot and stopped for work at this point, but interesting that I have the same issue.

I don't think it can't get any easier than: fastboot oem unlock

siberslug said:
I get adbwinapi.dll not found when I type fastboot devices
Click to expand...
Click to collapse
in the latest SDK revision they moved adb to \platform-tools. you need to change the PATH variable to that folder and restart your computer for it to take effect

Good call. Thanks >;]
slowz3r said:
in the latest SDK revision they moved adb to \platform-tools. you need to change the PATH variable to that folder and restart your computer for it to take effect
Click to expand...
Click to collapse
Sent from my Nexus S using XDA App

southeastbeast said:
Good call. Thanks >;]
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
no problemo, at first I didnt realize it either

[Q] Can't Get S=OFF, I rooted, But it Stays On?

Hi, I have just joined the forums to seek a fun, helpful community, I just got the Mytouch 4g as well, This is my first Android Phone.
In the middle of my Root process, after I entered..
su
cd sdcard/root
sh root.sh
I get the instructions. But After I turn off and reboot my phone while holding down Volume Down, I get the S=ON still.
May anyone please help me, I am even willing to donate $ Via paypal
Thank you for your time.

http://forum.xda-developers.com/showthread.php?t=858996
Try that first. Not sure why people are still using older methods with gfree available.

Kline said:
http://forum.xda-developers.com/showthread.php?t=858996
Try that first. Not sure why people are still using older methods with gfree available.
Click to expand...
Click to collapse
Because they want to do it the easy way. They do not want to take the time to do it they way it was meant to be done.

Well, Whenever I search for Adb devices in the command prompt nothing is founnate $. Thank you.d, When I do the Adb messages, Can anyone still help me with visionary or adb, I will do

assurgency said:
Well, Whenever I search for Adb devices in the command prompt nothing is founnate $. Thank you.d, When I do the Adb messages, Can anyone still help me with visionary or adb, I will do
Click to expand...
Click to collapse
If you are using Windows use the link in my signature for TrueBlue's ADB setup.

Thank you, This has let me use ADB Command Prompt, But not as I wanted.
When I typed ADB Devices
I get a blank list.
When I plug in the phone, and the installed drivers are showing, all are installed but Adb.
I really do not know what is wrong, many anyone view my computer screen via teamviewer.
Thank you very much, I would like to donate to anyone who solves my solution.!

assurgency said:
Thank you, This has let me use ADB Command Prompt, But not as I wanted.
When I typed ADB Devices
I get a blank list.
When I plug in the phone, and the installed drivers are showing, all are installed but Adb.
I really do not know what is wrong, many anyone view my computer screen via teamviewer.
Thank you very much, I would like to donate to anyone who solves my solution.!
Click to expand...
Click to collapse
are you sure usb debugging is enabled under settings/applications/developemnt?

neidlinger said:
Because they want to do it the easy way. They do not want to take the time to do it they way it was meant to be done.
Click to expand...
Click to collapse
Don't really understand you. To me, gfree is the easy way. It's not much simpler than unzipping a file and running it. It has a better track record of success than any of the previous methods, but, whatever. To each their own struggle.

assurgency said:
Thank you, This has let me use ADB Command Prompt, But not as I wanted.
When I typed ADB Devices
I get a blank list.
When I plug in the phone, and the installed drivers are showing, all are installed but Adb.
I really do not know what is wrong, many anyone view my computer screen via teamviewer.
Thank you very much, I would like to donate to anyone who solves my solution.!
Click to expand...
Click to collapse
I dont take donations, but I am happy to help in any way I can. If you have a blank list you probably havent installed the drivers correctly or you have not turned on USB debugging.I will be happy to view your screen. Send me a Private Message with the info to do that if you still need the help.

Kline said:
Don't really understand you. To me, gfree is the easy way. It's not much simpler than unzipping a file and running it. It has a better track record of success than any of the previous methods, but, whatever. To each their own struggle.
Click to expand...
Click to collapse
We know that it is the easiest. But yet we've taken the time to learn ADB and what does what. Most people see the ADB commands and get nervous and want to do something that is automated and scripted. where all they have to do is punch in a "go" command and everything is done for them.

if you have issue with ADB using SDK just download this zip, extract it and transfer it to the SDK it will work just fine
http://www.mediafire.com/?547p5fc2b5wvf6b

I need some help too,,,I tried everything and I have the same problem
Sent from my HTC Glacier using XDA App

Need a quick favor

I'm working on an application. Could you guys do the "adb devices" command and tell me what the device ID output it gives you. I'm wondering if there is some common element to each device ID generated for each particular device. Also tell me what particular Nexus S it is (i9020T, i9020A, etc.)
Thank you!

I have the i9020a
adb devices - 39347396C5D200EC
Sent from my Nexus S using XDA Premium App

lyall29 said:
I have the i9020a
adb devices - 39347396C5D200EC
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thank you for your reply. If anyone could also check theirs, it would be much appreciated.

How do we check it? I have a sprint nexus s 4g
apreichner said:
Thank you for your reply. If anyone could also check theirs, it would be much appreciated.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App

apreichner said:
I'm working on an application. Could you guys do the "adb devices" command and tell me what the device ID output it gives you. I'm wondering if there is some common element to each device ID generated for each particular device. Also tell me what particular Nexus S it is (i9020T, i9020A, etc.)
Thank you!
Click to expand...
Click to collapse
???
it's the serial number of the device

Its not the serial number of the device. Its a device id created by adb. If you don't believe me check the back or your device and compare.
Everyone can do it by plugging in their phone with debugging enabled and doing the command adb devices in the command prompt or terminal.
Sent from my Google Nexus S using XDA Premium App

Yeah I know it's created by the device but it's still specific to the device and always stays the same for the device. There isn't really a connection between the Nexus S serials. What exactly are you wanting them for?

derekwilkinson said:
Yeah I know it's created by the device but it's still specific to the device and always stays the same for the device. There isn't really a connection between the Nexus S serials. What exactly are you wanting them for?
Click to expand...
Click to collapse
I think there might be a connection because device ids are similar for each particular device. My program is going to need to detect what model of phone it is. Would you mind humoring me? I don't think any of this can be used maliciously, if you like I will post mine.
I'm probably going to end up having to grab it from the build.prop but the only issue with that is it the device is in fastboot mode.
Sent from my Google Nexus S using XDA Premium App

apreichner said:
I think there might be a connection because device ids are similar for each particular device. My program is going to need to detect what model of phone it is. Would you mind humoring me? I don't think any of this can be used maliciously, if you like I will post mine.
I'm probably going to end up having to grab it from the build.prop but the only issue with that is it the device is in fastboot mode.
Sent from my Google Nexus S using XDA Premium App
Click to expand...
Click to collapse
why in fastboot modus? then adb devices will not work you will need fastboot devices?
Sent from my Nexus S using XDA Premium App

This is not going anywhere lol.
Sent from my Google Nexus S using XDA Premium App

apreichner said:
I think there might be a connection because device ids are similar for each particular device. My program is going to need to detect what model of phone it is. Would you mind humoring me? I don't think any of this can be used maliciously, if you like I will post mine.
I'm probably going to end up having to grab it from the build.prop but the only issue with that is it the device is in fastboot mode.
Sent from my Google Nexus S using XDA Premium App
Click to expand...
Click to collapse
no no man you got it all wrong, i'm not saying it's malicious, I'm just wondering why you were trying to do it. I was thinking you would want it to identify the device, and I was correct. There are other ways to get the device ID besides using ADB.
I know you're working on your Sense ROM, is this to identify the device for the ROM or for flashing? If it is for flashing there is a way to do it by the recovery image.

derekwilkinson said:
no no man you got it all wrong, i'm not saying it's malicious, I'm just wondering why you were trying to do it. I was thinking you would want it to identify the device, and I was correct. There are other ways to get the device ID besides using ADB.
I know you're working on your Sense ROM, is this to identify the device for the ROM or for flashing? If it is for flashing there is a way to do it by the recovery image.
Click to expand...
Click to collapse
Actually it's not for my sense rom. It is for an application I am programming. Yeah there are other ways like: adb shell getprop, but that is no help for a device connected via fastboot. (as I've already mentioned before)
If there is another way to identify the device via a fastboot connection, I would be very delighted to hear how you do it.

Let me clarify a few things. lol
1. The program will be need to read from both adb and fastboot.
2. I already coded the program to read from the build.prop from adb.
3. While in fastboot, the build.prop won't be readable so we need another way to read the type of device plugged in.
We're hoping that the device ID will give us a clue as to what kind of device is plugged into the computer if the device happens to be in fastboot.

apreichner said:
Actually it's not for my sense rom. It is for an application I am programming. Yeah there are other ways like: adb shell getprop, but that is no help for a device connected via fastboot. (as I've already mentioned before)
If there is another way to identify the device via a fastboot connection, I would be very delighted to hear how you do it.
Click to expand...
Click to collapse
I suggest trying udev. it gives: ATTRS{idProduct}=="4e20" which is the nexus s in fastboot mode and is unique to the device.