I hope I'm not just being an idiot here, but I am having a lot of trouble with adb shell right now.
When starting the shell, instead of starting in $ it defaults to #.
However, whenever I attempt to use 'su', I receive an access denied error. I am not receiving any prompt on the device as I normally would.
At first I thought this was just related to CM7, but even flashed back to rooted 1.0.1 I am getting this issue.
Can anyone offer some insight?
Thanks
Edit: Damn, forgot to add [Q] to the title. Sorry!
Related
Ive had the hero for a while now and now feel its time to root it since there doesnt look like there will be anymore major updates.
I had first tried to root it through the unrevoked method and couldnt get passed code #8: su
It just kept saying that su wasnt a valid code or something like that. so after a couple other tries i scrapped it. eventually found the 1-click way and did that on my phone. But nothing seems to have changed. The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
If you guy could give me a little insight on what i need to do or point me in the right direction i would appreciate it.
there is just so much info on this site that it makes it a littl overwhelming for somebody just getting into the game.
best way to test if you have root is open terminal emulator and type su if you get a # in the prompt you have root.
Or from adb try
adb remount
adb shell and if you have a # instead of a $ in the prompt you have root.
If that works then to remove the crappy sprint apps open a cmd and type
adb remount
adb shell
cd system/apps
ls
then look through and find the ones you dont want and type this
rm my_bloat_app.apk (replace my_bloat_app with the app you don't want)
and hit y to comfirm and its gone.
madeSICC said:
...The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
Click to expand...
Click to collapse
Titanium Backup can do it. Download it and learn how to use it. It will become your friend.
If it can't do it, you still aren't rooted!
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
Do you have the "superuser" app on your phone?
cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
TheRomero09 said:
Do you have the "superuser" app on your phone?
Click to expand...
Click to collapse
Yes, I have it on my phone
miztaken1312 said:
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
Click to expand...
Click to collapse
I have the app on my phone, but when I try this, I do not get a prompt for super user permissions, and the CL shell returns permission denied
EDIT: I was going to look at the superuser app to see what was in it to give you more info, but it the "app" that I assume is actually my computer had denied permissions. After changing it back to allow, the shell returns
Code:
su
#
Well, this is interesting.
On my Revo4g, all I did was enable USB debugging in internet only mode, and i'm faced with this:
Code:
c:\tools\android\android-sdk-windows\platform-tools>adb shell
# busybox whoami
busybox whoami
whoami: unknown uid 0
#
Looks like there's no need for rageagainstthecage, or any exploits. ADB is run as superuser already! (although for some reason ro.secure is set, and it seems to be ignored, so it possibly may be a bug)
EDIT: Nope, verified. Toggle ADB debugging on and off, and you're root!
This is most definitely not what LG intended, but hey- it works!
Still no signs of fastboot without accidentally erasing recovery or something. Looks like it's left in as emergency-only.
If you're not rooted, try this:
Open ADB shell
Your command prompt should be "$"
Run
Code:
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Congrats! You're root.. now you can push "su" and whatnot.
That was strangely easy...
thecubed said:
Well, this is interesting.
On my Revo4g, all I did was enable USB debugging in internet only mode, and i'm faced with this:
Code:
c:\tools\android\android-sdk-windows\platform-tools>adb shell
# busybox whoami
busybox whoami
whoami: unknown uid 0
#
Looks like there's no need for rageagainstthecage, or any exploits. ADB is run as superuser already! (although for some reason ro.secure is set, and it seems to be ignored, so it possibly may be a bug)
EDIT: Nope, verified. Toggle ADB debugging on and off, and you're root!
This is most definitely not what LG intended, but hey- it works!
Still no signs of fastboot without accidentally erasing recovery or something. Looks like it's left in as emergency-only.
If you're not rooted, try this:
Open ADB shell
Your command prompt should be "$"
Run
Code:
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Congrats! You're root.. now you can push "su" and whatnot.
That was strangely easy...
Click to expand...
Click to collapse
OKAY... So, I don't need to do superoneclick? And I don't need to go through the painful process of downloading 3-4 programs?
markapowell said:
OKAY... So, I don't need to do superoneclick? And I don't need to go through the painful process of downloading 3-4 programs?
Click to expand...
Click to collapse
Well, if you've got ADB installed, then no you don't need superoneclick, but it's main claim to fame is that it's got all of the tools bundled together.
Stick with superoneclick until I get an easy method put together...
LOL... That's sweet!
Like I mentioned elsewhere... LG wants Verizon to think all is locked down and such but secretly behind its back it is giving us free candy. Like when grandpa and grandma hide money in your room before leaving...
They left in everything needed, we only had to put the pieces together.
Bravo LG bravo... now can we have the source code for this device for 2.2 and 2.3..
Now i'm for sure rooting today, as i already have adb installed. Epic.
So i ran ADB Shell and it automatically gave me "#". I then proceeded to "kill 'busybox pidof adbd' " and it said it did it. Still had "#". I don't seem to have root though. I can't delete bingsearch.apk, can't do anything in setcpu.
When i installed super user from the market, it did say there was an update, so it asked if i wanted to install it. I said yes, and it said an error occurred but it put a zip on my sd card to update the binary and that i need to reboot into recovery and install it.
Any ideas? I don't have cwm yet so i can't exactly do that. Here's how the whole thing went down:
Code:
C:\AndroidSDK\platform-tools>adb shell
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
# kill 'busybox pidof adbd'
kill 'busybox pidof adbd'
[1] Terminated kill "busybox pidof adbd"
#
Nevermind, i just went with super one click and i have root now.
powder007 said:
I then proceeded to "kill 'busybox pidof adbd' " and it said it did it.
Click to expand...
Click to collapse
Those were back-ticks, like this: `` not single quotes: ' '
powder007 said:
I don't seem to have root though. I can't delete bingsearch.apk, can't do anything in setcpu.
Click to expand...
Click to collapse
setCPU will require superuser.apk and a working su. Did you mount the system partition r/w by hand before trying to delete bing? Using this method, you'd have to mount r/w, then push su, etc.
Ah, my bad. I'm semi new to adb. Thanks for pointing that out.
I had the super user app from the market. On root explorer it didn't give me a Mount r/w button, so i knew i wasn't rooted.
The problem with this rooting method is that it's incomplete.
My method gives you entry to a root shell-- it does not "root" your device.
A "rooted" device requires a file in /system/bin/ called "su", which allows normal Android apps to access root functionality on the device.
The method I detail allows you to manually remount /system as r/w and push the required file to the proper location without requiring an exploit.
Once I have some time free from working on the deodex'd rom, and porting CM7, I will make a super-super easy one click root application for windows/linux.
Until then, this thread is mostly for technical reference for devs, and something interesting that I found
I've been trying to figure this out all day and I'm stumped.
My stock Droid recently failed to get past the bootloader.
I'm following the directions from the CM Wiki titled "Motorola Droid: Full Update Guide" (no direct link because of my new account, sorry) and others I've found and they all seem to be exactly the same.
I've got SPRecovery installed no problem and after I run the update.zip I get a successful install message, including "enjoy your root".
The problem is in the next step where I ADB it doesn't appear I actually have root access.
I think this may be because I'm connecting to my phone from the SPRecovery menu, but I'm not sure.
This is what my cmd screen looks like when I try to follow the steps under "Installing ClockworkMod Recovery" > "Second Method (manual method)".
Code:
C:\Users\XXXX>adb shell
/ # su
su
/system/bin/sh: su: not found
I noticed that in SPRecovery there are "mount options", so I tried mounting /system and trying again and I get basically the same thing, but without the "/" and without the directory
Code:
C:\Users\XXXX>adb shell
# su
su
su: not found
I'm not Linux savvy enough to know the difference unfortunately. I've tried 3 different update.zip from 3 different sources, but all appear to be the exact same thing.
Typing "busybox" in the ADB shell kicks back all the functions so it appears to be installed.
"adb devices" kicks back "040388990E0EDITED recovery"
Any ideas would be greatly appreciated, it's getting very frustrating.
Do you have the opportunity to root your phone from the Recovery-Menu?
I have OpenRecovery (OR) and when I boot in OR i can manually chose to root my phone.
----wrong----
Quinity said:
You can also simply download the SuperUser App from the market. This roots your phone.
Click to expand...
Click to collapse
I'm about 99% certain that is false. If it was that easy, I would have heard about it. Plus the only SU app on the market states " Grant and manage Superuser rights for your phone. This app requires that you already have root.."
I did something stupid, which involved not staying up to date with the news on my kindle hd 7 inch since i got comfortable with my setup and hadn't really done anything much to it lately that needed me going to the forums. Anyways, my kindle decided to download the ota update, which was like a slap in the face because 3/27 was my birthday and I was in the middle of reading manga and it rebooted then tried to update so I naturally held the power button down. Is there anyway to cancel the update via adb? I typically leave adb on as a precaution to any problem I might have. I thought maybe I could run a shell and tell it to remove the update file which I'm assuming is still in /sdcard/kindleupdates (I think thats the folder name), and maybe push the 7.2.3 update as a precaution in case it started to flash already and I didn't notice. I don't want to turn it back on until I know that I can connect to it with adb because I don't want it to update, I planned on flashing cm10 to it whenever it became stable, and I heard the latest update will break the ability for me to put a bootloader on it. Any help would be appreciated.
stunts513 said:
I did something stupid, which involved not staying up to date with the news on my kindle hd 7 inch since i got comfortable with my setup and hadn't really done anything much to it lately that needed me going to the forums. Anyways, my kindle decided to download the ota update, which was like a slap in the face because 3/27 was my birthday and I was in the middle of reading manga and it rebooted then tried to update so I naturally held the power button down. Is there anyway to cancel the update via adb? I typically leave adb on as a precaution to any problem I might have. I thought maybe I could run a shell and tell it to remove the update file which I'm assuming is still in /sdcard/kindleupdates (I think thats the folder name), and maybe push the 7.2.3 update as a precaution in case it started to flash already and I didn't notice. I don't want to turn it back on until I know that I can connect to it with adb because I don't want it to update, I planned on flashing cm10 to it whenever it became stable, and I heard the latest update will break the ability for me to put a bootloader on it. Any help would be appreciated.
Click to expand...
Click to collapse
You can find here instructions on how to disable OTA services:
Code:
adb shell su -c "busybox mount -o remount,rw /system"
adb shell su -c "mount -o rw,remount /dev/block/mmcblk0p1 /system"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAUpdateMessageHandler'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.InventoryUploadService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.UpdatesLookupService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.AppStateMonitorService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.CheckForOTAUpdatesService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.ViewUpdateActivity'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAStatusActivity'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.ResetOTAMessageHandler'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.InventoryUploadService$InventoryUploadReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.UpdatesLookupService$MountStatusChangedReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTAWakeupReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTADedupeReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTAInstallNowReceiver'"
adb shell su -c "busybox mount -o remount,ro /system"
adb shell su -c "mount -o ro,remount /dev/block/mmcblk0p1 /system"
adb reboot
adb wait-for-device
The question is how to get access to ADB. If you boot your device normally then I guess it will be too late. Kindle OS will proceed with the update. Perhaps, you can get into recovery (if you have it) and run these commands.
Anyway, it is better if you hear a second opinion from somebody more experienced.
thanks for that, i found that script when i was browsing earlier in a sh script, and was going to ask if it worked until i noticed that the script was linked back to the xda forums, wish i had sen it before my kindle started updating, and i don't have a custom recovery installed, thats why i wanted to not install this update i had been waiting around for one to come out and i kinda forgot about it and never checked back to see that it was out. I hope someone can still help me out, or atleast tell me if i will just have to boot up and I'm assuming wait for a new root exploit, since i think they usually patch the previous one when they update. Hope to hear a reply soon because i hate reading manga on my ipod... its got a small screen compared to my kindle... (I NEED MY MANGA FIX xD) and yes i know i could read it on my pc bu ti cant lay in my bed while i do it... love the quickmanga app.
stunts513 said:
thanks for that, i found that script when i was browsing earlier in a sh script, and was going to ask if it worked until i noticed that the script was linked back to the xda forums, wish i had sen it before my kindle started updating, and i don't have a custom recovery installed, thats why i wanted to not install this update i had been waiting around for one to come out and i kinda forgot about it and never checked back to see that it was out. I hope someone can still help me out, or atleast tell me if i will just have to boot up and I'm assuming wait for a new root exploit, since i think they usually patch the previous one when they update. Hope to hear a reply soon because i hate reading manga on my ipod... its got a small screen compared to my kindle... (I NEED MY MANGA FIX xD) and yes i know i could read it on my pc bu ti cant lay in my bed while i do it... love the quickmanga app.
Click to expand...
Click to collapse
When kindle is updated to 7.3.0 you lose your root and some applications will stop working or get deleted. You can still re-root your Kindle 7.3.0 using exactly the same procedure as for 7.2.3. I just re-rooted my device yesterday. it worked without any problem. I had to reinstall Google Play and custom launcher after root.
ok well thanks, I guess I have no choice but to let it finish updating, well maybe unless they find a new bug to let us put custom recovery on it, that other project will get more attention, can't remember the name of it because I haven't been browsing around in the community much for atleast a month. Funny thing is I have to remember how I rooted my kindle... I left all my rooting utilities and scripts in a folder, but my mom has a kindle fire 1st gen that i rooted as well so the stuff is also in the folder, shouldn't be a problem though I'm a pc tech so i can sort this stuff out easily.