"ADB Shell" gives me "#" instead of "$" when rooting MyTouch Slide, why??
trying to root my MyTouch 3G Slide. Ive tried various methods from different sites to do it but they all seem to come down to running something called "ADB Shell". On the screenshots, it seems to always give you a $ prompt. When I do it, I get a # prompt. Also, anything I type after that is just repeated back to me along with another # prompt. I find where other people get the same problem but cant find any solutions with it. What am I doing wrong?
kellyjaye said:
trying to root my MyTouch 3G Slide. Ive tried various methods from different sites to do it but they all seem to come down to running something called "ADB Shell". On the screenshots, it seems to always give you a $ prompt. When I do it, I get a # prompt. Also, anything I type after that is just repeated back to me along with another # prompt. I find where other people get the same problem but cant find any solutions with it. What am I doing wrong?
Click to expand...
Click to collapse
In Linux and Unix systems (Android Included) a # (Pound Symbol) signifies Root level access or su (Superuser) so since you're rooting your device this means you have done it, $ appears for any other user of the system
i have the same problem too. I'm using window xp and it giving me the # symbol instead of $. any suggestion to fix it? i have checked all the drivers, slideroot files are in androidsdk file
like Captainkrtek said, if you're getting a # for your adb shell, you ARE rooted.
root shell should look something like this:
Code:
$ adb shell
#
Related
I used the directions from Jesus Freke to install the Mod RC30 on my G1.
Then I read and used the instructions provided by Stericson to change my password....
Only one problem! Now it won't let me access root with su or with my password. I wanted to use something generic first and if it was successful I would change it to a good password. So, I used my user name "shaneaus"
Now I get permission denied with both su and shaneaus!
Am I totally screwed? Is there some way to reset the password back to su. That wouldn't make sense, I know, from a security sense. Just hoping.
Thanks
I'm hoping that there is an easier solution.
But, if I flash the update... Will that reset the root password?
I don't know what happened but this can be remedied. First off, it is possible that when you change the superuser command you failed to chmod it to 4755...at any rate, you can solve this by plugging your phone into your computer and starting up an adb shell, this should give you root if you have the modded rc30. Next remount /system to read and write privileges
mount -o remount,rw /dev/block/mtdblock3 /system
now type:
cd /system/bin
ls
Do you see su or your username listed?
If so type:
chmod 4755 (type su or your username here, without parantheses)
now open terminal emulator on your phone and try your superuser command again.
If you did not see su or your username in the output of ls type the following to get a setuid shell:
cat sh > (username or su whichever you want)
chmod 4755 (username or su whichever you want)
now open terminal emulator on your phone and try your superuser command again.
That should get you going.
Ha!
I'm just beginning to learn how to do this stuff. I have no idea how to "start up an adb shell" or even what an adb shell is!
So, I guess I'll start researching on line!
Ok, so I've read up on the adb shell and think I have a grip on how to use it... Except I can't figure out how to get the darn thing started. Do I have to open up the emulator? I thought I would be accessing the device - not the emulator. But, most sites talk about using the adb with the emulator. Also, I have seen where I should be able to run adb devices.exe and have it show my device to confirm it is connected. Only one problem, I can't find the adb devices.exe in the sdk kit.
Oh, and thanks again to Jesus Freke for the 64bit USB drivers. worked like a charm!
Awesome! Y'all are fantastic! I learned a lot tonight! I did the following:
Add $SDK_ROOT\tools to my path
Then had a hell of a time because everything I was reading (except for one location I finally found said to run "adb shell.exe"
I finally found a site that said to run "adb.exe shell"
And, whalla! I was in.
Your above advise was spot on, Stericson! Thank you!
Glad to hear you got it sorted.
shaneaus said:
Oh, and thanks again to Jesus Freke for the 64bit USB drivers. worked like a charm!
Click to expand...
Click to collapse
*looks around* huh? me?
I assume you're refering to this driver?
You should be thanking aziwoqpd for that, not me
Ok... If your wimax isn't working and you want to downgrade to try to get it working this is how to do it...
1st get all of the files like you want to do Toast's Part-2. link: http://forum.xda-developers.com/showthread.php?t=701835
Then do this part:
STEP 2~FLASHING MTD PARTITION TO ENABLE DOWNGRADE:
- download all files posted above
- unzip the flash_image.zip and the mtd-eng.zip
- put the flash_image and mtd-eng.img on the root of your sdcard
- go into shell on ur pc and do:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img
- this should only take a second or two
- now put the PC36IMG.zip on the root of your sdcard
- power off the phone
STEP 3~FLASHING ENG BUILD:
- hold volume down + power to boot into hboot
- it should now find and verify the PC36IMG.zip on the root of your sdcard. itll show a blue status bar on the top right of the screen.
- after a minute or so it will ask u if u wanna flash SAY YES
- affter it flashes the PC36IMG.zip it will ask if you wanna reboot. SAY YES
After if finally boots you should see HTC quietly brilliant which hangs forever but it should eventually get past it. Once it does you will have the oldest everything. This is a beta build and has a bunch of tools but just do an upgrade to root like you normally would. I would suggest going to .6 then upgrading to the latest 47 from there.
Hope that this helps someone.
P.S. is anyone willing to dump all of the tools that are included in this rom. It might be helpful for the other devs.
Thats the hard way... but yeah it'l work.
Why is everyone so hype on adb everything...?
Tell me the easy way. I would love to do it instead.
kthejoker20 said:
Thats the hard way... but yeah it'l work.
Why is everyone so hype on adb everything...?
Click to expand...
Click to collapse
It's just easier to copy and paste stuff, even typing on a real keyboard. It's a pain in the ass doing it via terminal emulator with the lack of a physical keyboard on our Evo's.
Can anyone confirm if this helps fix the 4g issue?
krosemm said:
Can anyone confirm if this helps fix the 4g issue?
Click to expand...
Click to collapse
If you used the unrevoked, no it wont.
There is no fix for 4g from unrevoked yet.
Neotelos_com said:
If you used the unrevoked, no it wont.
There is no fix for 4g from unrevoked yet.
Click to expand...
Click to collapse
I used the toast method. And if i'm not mistaken I should flash roms w/o the 1.47.651.1 OTA update after downgrading right?
Nope, I try this method and it is not working. Some how the new OTA encrypted a code that any lower version will not over write it.
You don't have root access to even copy/paste or push the files to /data. I tried this and got a permission denied error message.
How do you input adb shell into Vista, I clicked "start", "run" and type "cmd" it bring up C:\users\XXXXX\ cd c:\android hit "enter"
then I type
c:\android>adb remount
Access is denied
Please advise what I did wrong. thanks
It worked for me... you have to make sure that when you enter the su command in adb to look at your phone. There should be a super user permission box that pops up. Accept it and youll be able to adb. It went fine for me after that.
urcboss07 said:
How do you input adb shell into Vista, I clicked "start", "run" and type "cmd" it bring up C:\users\XXXXX\ cd c:\android hit "enter"
then I type
c:\android>adb remount
Access is denied
Please advise what I did wrong. thanks
Click to expand...
Click to collapse
1) Put your phone on USB Debug
2) On your Phone make sure the Ninja(SuperUserPermission) is set to prompt you when you have a request.
3) go to your PC and type in adb shell
4) type in SU
5) Once do you that you will see a prompt from the Ninja asking for a request. Allow for it. And it will remember from that point forward.
6) Look at your cmd prompt screen for a # - if you have it you have full access.
Then so what commands you have been given to do.
It can also be done from the Android Terminal Emulator but some might not like working with a smaller screen I like it myself. Makes me feel geeky
mrmomoman said:
1) Put your phone on USB Debug
2) On your Phone make sure the Ninja(SuperUserPermission) is set to prompt you when you have a request.
3) go to your PC and type in adb shell
4) type in SU
5) Once do you that you will see a prompt from the Ninja asking for a request. Allow for it. And it will remember from that point forward.
6) Look at your cmd prompt screen for a # - if you have it you have full access.
Then so what commands you have been given to do.
It can also be done from the Android Terminal Emulator but some might not like working with a smaller screen I like it myself. Makes me feel geeky
Click to expand...
Click to collapse
This would only work if after the messup your still has root access. Some people have root and the "SU" will work but for the people w/o root will get access denied.
also
From above (I hate quoting) have you tried going to your tools folder inside your android folder and from there try your adb commands?
If you applied the OTA sent from Sprint, you lost root access. There will be no Ninja in the programs folder, because it was a new rom that the was flashed with the OTA. Root access has been closed for those that downloaded the update. If you try and type su, you will get permission denied.
Those of you that still have the root and superuser rights, DON'T DOWNLOAD THE OTA!! You are in a better position then the rest of us. I wanted the good battery life, so that's why I did it.
Hello. I have rooted my phone, with superuser mode. or w.e you guys call it.
I was trying to change the Android icons(Rogers HTC MAGIC Android 2.1) using this guide: http://forum.xda-developers.com/showthread.php?t=927405
BUT, when I type adb shell, then su a # pops up on cmd. When I type the other commands nothing happens. EG when I type cp /sdcard/HtcContacts.apk /system/app/HtcContacts.apk it displays cp unknown. What's going on? I have also given it superuser privileges. Help? ^^;
I am trying to update a few things on my G2 and when I go in to adb shell, the prompt opens at the superuser level (the # prompt). Typing exit exits adb shell, it does not take me to the $ prompt. Any thoughts on how I can get to the $ prompt? It has worked fine in the past.
Thanks
Edit: disregard. It appears that I still have the regular adb shell and SU levels, but both have the # prompt. Still curious if anybody knows what causes that, but it seems to be working as it should.
Some custom roms open to a root shell... if you have a stock rom then idk what's going on
Sent from my Droid using Tapatalk
I actually first noticed it when on CM 6.1, but it was still showing the # prompt when I restored to my rooted stock. But, there still is the difference between $ and #, I just need to make sure I keep track of which one I am really using at the moment.
if you use 2nd-init or custom boot image you will get default #
By all accounts, my Nexus S 2.3.4 has been successfully rooted using this method: http://forum.xda-developers.com/showthread.php?t=1138755
Now I can use apps that require root access, and I can also type "ADB shell su" to gain root access if I want to poke around within the file stucture.
HOWEVER, what puzzles me is that when I type "adb shell", I am prompted by a "$" symbol instead of "#". I have to type "su" from the adb shell in order to get the "#" symbol, and when I exit out of shell I lose my su status. It means that I cannot simply do something like "adb shell ls /system/" or "adb remount"; I get a "permission denied" message. It also means I cannot easily pull or push files to/from the /system/ dirs from the command prompt.
When I was using a rooted 2.3.3, I was always promted with the "#" symbol after typing "ADB shell". How do I get this level of root access in 2.3.4?
This is normal.
Sent from my Nexus S 4G using xda premium
Fair enough. But is there a way to get "#" access directly from "ADB shell" ?
The main thing I want to be able to do is pull and push files directly from/to the system directories. As I mentioned previously, with my old rooted OS (2.3.3) I was able to achieve this by simply typing "adb push [myfile] /system/".
But now, it seems my only options are:
a) "adb push [myfile] sdcard/", then "shell", then "su" and then copy the files from /sdcard/ over to /system/, then "exit" "exit".
b) Boot into recovery, mount the system, then "adb push [myfile] /system/".
Is there a simpler method?
shanksworthy said:
Fair enough. But is there a way to get "#" access directly from "ADB shell" ?
The main thing I want to be able to do is pull and push files directly from/to the system directories. As I mentioned previously, with my old rooted OS (2.3.3) I was able to achieve this by simply typing "adb push [myfile] /system/".
But now, it seems my only options are:
a) "adb push [myfile] sdcard/", then "shell", then "su" and then copy the files from /sdcard/ over to /system/, then "exit" "exit".
b) Boot into recovery, mount the system, then "adb push [myfile] /system/".
Is there a simpler method?
Click to expand...
Click to collapse
Yeah, flash an insecure boot image, otherwise no.
Sent from my Nexus S using xda premium
krohnjw said:
Yeah, flash an insecure boot image, otherwise no.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Can anyone recommend an insecure boot image for I9020A, v2.3.4?
I've looked everywhere...
shanksworthy said:
Can anyone recommend an insecure boot image for I9020A, v2.3.4?
I've looked everywhere...
Click to expand...
Click to collapse
no one wants an insecure boot image. imagine if a malicious app was installed onto your phone, and it had complete root privilege to whatever it want. before you would know it, you would have a $20000 bill to some porn site. and there would be a video of you doing whatever you do in privacy, floating around the internet, recorded from your phones front facing camera