Hello Everyone,
I have supposedly rooted my new Galaxy Nexus (CDMA) phone. All the apps that request root on the phone are able to get access to it, also if I use "adb shell" and then use the "su" command to switch to root it will grant me access, albeit without ever prompting me on the phone. However when I try to use the "adb root" command from the terminal window it gives me an error of "adbd cannot run as root in production builds".
I need this function to work, but cannot seem to find my way around it. I am not the only one I know who has seen this, but we cannot seem to figure it out. I was hoping to get some suggestions? Any thoughts?
No luck it looks like...will this bumb it?
Why do you need the command "adb root" ?
Mostly for grabbing logs via the logcat command.
Sent from my GNex,
-Originalme8
Why not "adb logcat" ?
Still don't understand why you need the specific "adb root" command.
Does it really matter what my reasons are? Maybe I am worried that there is a problem with my such controller? I just want to know why this command isn't working. If your not going to help, please don't post hand waste my time.
Sent from my GNex,
-Originalme8
you could use adb logcat as mentioned above
http://forum.xda-developers.com/showthread.php?t=833756
forum search, it's magic.
and yes, reasons matter.
Seriously...you two have been no help...
Sent from my GNex,
-Originalme8
So you are saying the link i posted, does not contain the answer to your question, although it states what causes the error message and how it can be fixed?
Originalme8 said:
Seriously...you two have been no help...
Sent from my GNex,
-Originalme8
Click to expand...
Click to collapse
So you have a "recognized developer" trying to help you out and posting a link to the problem and the fix, and that is how you respond? Good luck on XDA buddy.
Oh, and don't worry, I will hit their thanks button for you.
Old Thread and that attitude certainly wasn't the nicest but incase someone else Google Searches this...
First you need to decompile the kernel.
In your Root of decompiled files, find a file called
default.prop
Edit it with Root Explorer or ES File Explorer
Find these lines
ro.secure=1 and change it to ro.secure=0
ro.debuggable=0 and change it to ro.debuggable=1
Save and recompile. If this is already too complicated for you, then you can read about what decompiling and compiling is. Search it.
Your Kernel is likely stock kernel and will not allow this change if you don't have USB Debugging option available within your ROM.
If you have this option, then enable it. It is possible that you have half root - Unlocked boot loader, but Kernel is from a stock ROM. You can still get shell access. You just won't get it while your System is Mounted if you don't have USB Debugging enabled and you plugged into Windows while your System is running. So Reboot into Recovery, and then go into your ADB Directory and type
adb start-server
adb devices (see if it lists the connected device) if yes then type
adb root (It should say adb is already running as root)
then type
adb shell
you can use the ls command to list all the directories.
cd to change into them. like cd /sdcard then ls and so on.
and cd / to go back.
Look up basic linux shell commands.
and then you can do whatever you want. List of ADB Noob Commands
http://forum.xda-developers.com/showthread.php?t=517874
Hope this helps anyone who got in here from a Google search.
Next time try to be nice to others, and be patient. I spent time trying to help you. As did the other guys. Try to give back.
ocd_amp said:
Old Thread and that attitude certainly wasn't the nicest but incase someone else Google Searches this...
First you need to decompile the kernel.
In your Root of decompiled files, find a file called
default.prop
Edit it with Root Explorer or ES File Explorer
Find these lines
ro.secure=1 and change it to ro.secure=0
ro.debuggable=0 and change it to ro.debuggable=1
Save and recompile. If this is already too complicated for you, then you can read about what decompiling and compiling is. Search it.
Click to expand...
Click to collapse
Terribly sorry for bumping a post this old in advance. I would PM but I am also leaving a reply for people Googling this later on.
I have been searching on how to compile a .prop file for 2 hours now. The most relevant thing I could find online was a tutorial on how to compile my own ROM's but that compiles the whole ROM and seems unrelated to what you said (using Es file manager). Also, I just want to make my Stock rooted ROM debuggable.
Could you direct me to a source or simply explain how I would do that?
Related
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Sorry, completely new to android but where would you put this file so it would allow side-loading?
You'd have to replace
Code:
/data/data/com.android.providers.settings/databases/settings.db
with it. You'll have to have your phone rooted first though. Then you'll have to transfer the file to your phone with adb, and you'll then copy it over the existing settings.db file.
Honestly, it might not even be worth the trouble now that attn1 is just doing the whole ROMs.
But make sure you take off the .txt.
This works. Thanks.
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
justince said:
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
Click to expand...
Click to collapse
did you boot the phone and do adb remount with debugging enabled?
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
justince said:
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
Click to expand...
Click to collapse
That's why made the ROM without all that -er- stuff.
attn1 said:
That's why made the ROM without all that -er- stuff.
Click to expand...
Click to collapse
Attn's Rom is ****ing great. many thanks btw
a little help please
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
fluffyarmada said:
I'm not sure if any other user-specific settings are kept in that file that I don't know about!
Click to expand...
Click to collapse
The only issue I see (as an Android newcomer, but with a development background) is that the settings.db contains an android_id that is supposed to be unique (it gets generated when you boot the phone the first time after a reset). So anyone installing your settings.db is going to have the same ID.
I'm sure it won't be an issue for most people but I wonder if there'd be a collision in any apps that are designed to communicate between Android devices? For this reason I'll be tweaking my own settings.db once the phone arrives later today.
Big thanks for posting this though!
Thanks for that, I honestly had no idea. I'm very new to Android. And this was a kludge.
fluffyarmada said:
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Click to expand...
Click to collapse
NOTE: You MUST have root access in order for this to work
sqlite3 is included in the Android SDK tools, so this would be the best way:
COMMON
Enable USB debugging (settings > applications > development > USB Debugging)
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks fluffyarmada)
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Cobus said:
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
It is possible. The Google apps all use the android_id, afaik.
Although, I do remember I was never able to get the settings menu to setup the voicemail forwarding... I always had to use the weird GSM code. (The weird number with a bunch of * and # that you have to type in if you follow google's directions.)
judicious said:
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
Click to expand...
Click to collapse
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
tiga2001 said:
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
Click to expand...
Click to collapse
Well, it's
Code:
$ adb push /path/to/file/on/computer/settings.db /path/to/file/on/phone/settings.db
So, if your settings.db is in your tools folder, then you can do
Code:
$ adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
what happen to the file download? i cant find it..
judicious said:
what happen to the file download? i cant find it..
Click to expand...
Click to collapse
Please follow the instructions posted by attn1 on reply number 13 to this thread.
I removed the settings.db, because it actually has a bunch of extra settings I didn't know about like a handset specific android_id variable... that caused me a bit of trouble...
But, follow the instructions on reply #13 on this thread, and you'll be able to fix it yourself.
Sorry for the inconvenience.
so if we already used the file, is there anyway to revert it back to default and then change the settings via the method outlined above? or.. if we failed to make a copy of our original settings.db file.. basically am i SOL?
EDIT: nevermind, just rebooted into Clockwork and wiped the phone.
This is for anyone who is experienced with rooting using the rage method (command-line), using the Terminal Emulator, etc. I'm looking to root my phone, but aside from that, just looking to poke around and see what I can do at this point.
Ok, here's the skinny: I can get a temporary root (#) on my phone via the Terminal Emulator (will NOT show up in cmd.exe via adb) using the rage method, detailed steps are in my post here.
I can't push any files to /system after I get the temporary root - /system seems to lock up with any commands, like cat, attempting to do so (another post with details). However, I can copy /system files onto /sdcard, no limits as far as I know. Also, I can use dd to make a back-up of some of the mtd partitions. That's about the extent of the poking around that I've done after many hours of poring over other forums of different devices.
Where can I go from here? Can I use a different directory on the phone to try and push either su or Superuser to? Should I just give up? Haha.
I know that I already have my own thread dedicated to my phone and trying to figure out stuff for it. So, I hope I'm not stepping out of bounds by asking a question like this in regards to this rooting method...my apologies if I am being improper. My thanks and gratitude for anyone who reads this and can help me get to the next step, as little or big as that may be.
hello xda!!! been doing alot of reading here and desided that i wanted to be part of the action...with that said...
did some reading on how to get clockworkmod on the mesmerize and have no clue how in gods name to use adb...is there a how to that could help me better understand how to use it and get this on my phone after i have it rooted...soory for the noob question but as you can see. im a noob at this. only phone i have really modded is the samsung acclaim (which btw is a weak phone but good for the noobie droid user) so any help is greatly appreciated. thanks in advance guys and i look forword to helping devs by testing and such
adb, or android debug bridge, is a tool distributed with the android sdk. In current versions of the sdk, it is located in the platform-tools folder, which only appears after you download the sdk tools after downloading the sdk zip itself.
It should be noted that usb debugging needs to be enabled on your device in order for adb to work properly. This can be turned on under: Applications > Development
To use adb, you open up a command window if on windows or a terminal emulator if on linux or mac. Type:
adb <command> [options]
Where command is any one of the commands listed when typing "adb help" and options are things like file names, paths, or other flags.
Common commands include:
pull
push
shell
pull copies a file on your device to your current working directory (or the optional specified location)
push copies a file from your computer onto the device
shell invokes a simple shell on your device allowing you work in a linux like environment on your device
There is a reboot command that is sometimes helpful but that can always be done using the power button on the device.
You will probably only use push and shell.
Examples:
adb shell
adb push update.zip /sdcard/update.zip
Hope that clairifies things a bit.
yes it does sir...so with those commands i can "push" the clockworkmod onto my mesmerize and have that beautiful recovery? the only directions i found where using the adb. if there any way i can screw this up ei: mistyping or will it just say invalid command or something? and again ty for the fast response!!!
you got the thanks for that...lol...im grateful for any and all help
Typos shouldn't hurt. If it's a bad command it just won't execute. If it's a bad filename you may have to clean up a bit (like remove the file that is improperly named or in the wrong directory) but nothing fatal should happen.
alright...i feel a bit more confident that i can make clockworkmod happen when i get my mesmerize and get it rooted...any other suggested mods for spped?
You should install a custom ROM, (I use Super Clean, some people prefer the pick n pack) then a theme you like from the themes and apps section, then install the voodoo lagfix kernel. Everything mentioned can be found in the Mesmerize forum.
yea i seen voodoo but wasnt quite sure what exactly it does. as far as the pick n pack or super clean...could you tell me the difference or does it say it on the page where it was posted and im just blind and didnt see it?
BakedTator said:
yea i seen voodoo but wasnt quite sure what exactly it does. as far as the pick n pack or super clean...could you tell me the difference or does it say it on the page where it was posted and im just blind and didnt see it?
Click to expand...
Click to collapse
Its obvious you didn't read the threads.
Sent from my SCH-I500 using XDA App
ADB is nice and all ..
But there other ways to install and do everything needed to Flash a ROM or Kernel.
How to get ADB up and running.
And a couple other great links for learning more.
http://forum.xda-developers.com/showthread.php?t=502010
http://forum.xda-developers.com/showthread.php?t=872128
If you look in the Clockwork Mod thread here in the Mez forums there are walkthroughs on BOTH ADB method to get CWM working and sans ADB methods.
And again. Always Read.. Read again.. if all else fails.. Read once more.. And ask.. Everyone here is very informative and glad to help when we can.
I knew nothing of Android before I came here and a month later I know enough now to be dangerous.. LOL
skitzo_inc said:
Its obvious you didn't read the threads.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
i did read just havnt read over it several times to see if i have missed anything...just a lil scared of adb because i have never used it before..i have an acclaim and could do everything from the swupgrade flasher for the moment and that made life easy(aint tryin to brick a 600$ phone)
to Sighcosis
thanks for the link...will read over them tonight seeing as my phone will be here no later than Wednesday and i wanna have everything downloaded and ready to roll cause the second i get this phone imma start fashing it and getting everything i want on it...again thanks for all the help guys...now more reading
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
I can't help with your specific questions, but there is some info about rooting the i1, another iDEN with Android. Although it looks like the i1 is actually Android, and not the Motorola-altered, not-really-Android, proprietary software that the i886 has.
http://www.howardforums.com/showthread.php/1662431-Motorola-i1-Rooted
http://forum.cyanogenmod.com/topic/5520-ive-rooted-my-i1/
garbb said:
I am trying to root a motorola i886. Its a really wierd nextel iDEN PTT phone that is running (i believe) android 2.0 or 2.1 but has no touchscreen...
Basically I have been able to get a root shell (#) from 'adb shell' by pushing some program called psneuter to the phone and running it. Once I had this I could install apps via adb ok, but it seems like whenever I try to run any apps that require root they error saying they do not have root access.
As far as I can tell pretty much every rooting guide for every other phone has you putting 'su' and sometimes 'busybox' into /system/bin and 'Superuser.apk' into /system/app. I did both of these but still got the same errors about apps not having root. I tried a few different versions of these files I found from different sites to no avail. Running su on a terminal emulator on the phone itself would get the error "operation not allowed" or something like that. Then I found some other guide where you just copy 'sh' to 'su' and chmod su to 4755. When I did that I could get to a # prompt on the phone's terminal emulator app by typing 'su' but still got root errors for apps that need root.
I though maybe someone here would know something that I missed. As far as I can tell, I have applied the correct permissions to all these files or have at least tried every combination I can think of to no avail (shouldn't chmod 777 just make everything work?)
Also, does the phone usually come with a stock version of busybox on it? Do you need a specific version of these files for your device or version of android?
When an app on the phone tries to get root access is it just basically trying to run 'su' internally or something like that?
Also forgot to mention I have tried all the one-click-root apps and they do not work for this stupid phone. (well the super one click one was how I figured out how to get the adb shell root but the regular root button doesn't work...)
Click to expand...
Click to collapse
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
geminis said:
PM to me,i rooted sucefully, and install many applications with android SDK suite.
Regards.
Click to expand...
Click to collapse
Wow, I can't believe someone found this thread and replied after so long. Thanks, but in the meantime I actually figured out how to root it fully and get root apps to work. I think i just tried different su's and superuser.apk's that I found on the internet until one worked...
Now, if you have figured out how to change the nextel push-to-talk chirp/beep sounds then let me know how you did that. I actually found the .wav files for the PTT sounds in some .apk in /system (phone.apk I think?) but for some reason changing them had no effect on the sound the phone makes when using the push-to-talk feature...
Its been 10 years but do you still have the firmware for this device? I need to flash it, it doesnt finish booting up
I don't have a full ROM .zip file for this phone, only some update .zips. But the first link result for a google search for "motorola admiral stock rom" worked for me for downloading a file.
Wrong phone, sorry.
Sorry but i don't understand. Isn't the Motorola admiral a different device? Does that zip work for the i886? If so, how do I flash it, because the i886 doenst have a recovery mode.
Oh, oops sorry, I was confusing this phone with another one. I looked and I don't have and firmware files for this, sorry.
OK, thanks for replying
Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.