Disclaimer: Before the 'Wrong section police' goes all Nazi on me, I wanted to say that I realize this MAY be in the wrong section but I wasn't sure since this has to do with actual development.
Anyway, question is.. we now have 4 great ways to root using a computer. (See below for those threads.)
Is it possible to maybe make an app that you can just run off your phone to root, without the use of a computer? I understand ADB is needed but doesn't "Terminal Emulator" work just as good over the phone?
If not, can someone be bothered to explain as to why it would not work?
Threads to root:
My fav./"Perma" root: http://forum.xda-developers.com/showthread.php?t=1159354
J.eremy's <Script>: http://forum.xda-developers.com/showthread.php?t=1152101
Wisefire's [TOOL] (from htc sensation section(works on 3VO)): http://forum.xda-developers.com/showthread.php?t=1158400
Another one: http://forum.xda-developers.com/showthread.php?t=1159540
I don't think it will work because once you lose your temp root you won't have the permissions needed to use the terminal emulator.
SeNt FrOm YoUr MoThErS VaGiNa!!!
AssAssiN FtC said:
I don't think it will work because once you lose your temp root you won't have the permissions needed to use the terminal emulator.
SeNt FrOm YoUr MoThErS VaGiNa!!!
Click to expand...
Click to collapse
Have you checked out:
http://forum.xda-developers.com/show....php?t=1159354
It's a temp root that sticks!
But either way, you answered my question. I was not aware that you need Root to be able to use "Terminal Emulator".
Thanks amigo.
arozer said:
Have you checked out:
http://forum.xda-developers.com/show....php?t=1159354
It's a temp root that sticks!
But either way, you answered my question. I was not aware that you need Root to be able to use "Terminal Emulator".
Thanks amigo.
Click to expand...
Click to collapse
um i doubt you do need root... you will be in shell as $... in theory you could just get a windows script and rename the commands... theyll probably say 'shell' within the command... which would be bad since youd be IN a shell... and maybe run it? as for the files that you normally ADB push, you can store them in /vendor/bin and it will stick after reboot. so make the pathin as /vendor/bin instead of /data/temp or w/e it is... you will have had to've ADB pushed the files the first time tho. the rest can be scripted... im sure of it. then again... idk if the app has built-in ADB.. 3rd party app maybe?
Tilde88 said:
um i doubt you do need root... you will be in shell as $... in theory you could just get a windows script and rename the commands... theyll probably say 'shell' within the command... which would be bad since youd be IN a shell... and maybe run it? as for the files that you normally ADB push, you can store them in /vendor/bin and it will stick after reboot. so make the pathin as /vendor/bin instead of /data/temp or w/e it is... you will have had to've ADB pushed the files the first time tho. the rest can be scripted... im sure of it. then again... idk if the app has built-in ADB.. 3rd party app maybe?
Click to expand...
Click to collapse
That's exactly what I was thinking.
Perhaps a DEV can answer? =/
Related
In addition to enabling ADB, SuperNooter will also mount the NC /system partition and copy over Superuser.apk and the su binary. This means you do not need z4root! You should see Superuser in your Extras/App Drawer after booting from the SD card.
Tested with WinImage under Windows and dd under Ubuntu.
http://muffinworld.net/android/nookcolor/supernooter0.1.zip
Thanks for making things even easier!
-CC
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Novarider said:
Do we just write this to the sdcard like nooter? Install it like nooter? Do we need to wipe anything if we are previously rooted with nooter? Any adb commands needed?
A little more info and/or a tutorial would be really helpful
Click to expand...
Click to collapse
Yup...do exactly what you did with nooker only use this image. Same steps.
Ok but do we need to wipe anything if we already used nooter? I don't want to brick my NC. Who is going to be the first to try it out? I would but I don't know anything about programing so if I messed it up I would be screwed
You can use supernooter on top of an existing nooter to gain Superuser. I would not try it if you already have Superuser (why would anyone?).
Mistar Muffin...you are the man!!!!
Just picked up a NC today and have been prepping for the past couple days...and pleasantly surprised that the steps have diminished with this.
Thank you!!!
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
johnopsec said:
OK. The other utility Mistar Muffin created does not "brick" devices.
(1) I've yet to see a NC truly bricked. Only people who crap their pants when things don't go perfect.
(2) The script that is having problems is not Mistar Muffin's script. It is one that someone else (rboatright) created for people who run Winblowz and it is only based on Mistar Muffin's script.
Seriously folks... You REALLY need to watch the tone here and at a minimum, get your facts straight.
<under breath>What a bunch of crybabies!</under breath>
Click to expand...
Click to collapse
What tone? I didn't say a single bad thing about the guy. I just dont want to brick my NC since im not a programmer and probably dont have the skill to fix it if something went wrong
Mistar Muffin said:
I was actually crafting a very similar reply when I saw yours, johnopsec....thanks for setting Novarider straight!
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with. The other thread you started has people in it that are getting "bricked" devices. I didn't know you didn't write the particular program that was causing this. I was not implying you were doing anything wrong I just don't want a "bricked" device.
Novarider said:
What tone? I didn't say a single bad thing about the guy.
Click to expand...
Click to collapse
Novarider said:
Setting me straight? LOL I simply asked if it is safe. I didn't need setting straight all you had to do was say yes its safe and that you didn't write the program people are having problems with.
Click to expand...
Click to collapse
Novarider, I think that it's just the frustration of people coming on the forum and making posts with big bold red letters that say "YOU BRICKED MY NC!!!" and the like... As many others (including myself) have already stated, it's very difficult to brick a NC. I've yet to do it and I've done some VERY off-the-wall stuff with mine. My personal frustration comes from those two things.
So, sorry if you felt wrongly persecuted by my post. It wasn't directed only at you but at others who have screamed, yelled and lamented about one thing or another "bricking" their NC.
Friends?
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Novarider said:
How safe is this? The other utility you created seems to be bricking devices. I'm not saying your a bad guy or anything I just don't want to brick my NC
Click to expand...
Click to collapse
What are talking about "bricking" devices? Have yet to see anyone claim to have "bricked" a Nookcolor...
That being said, don't think it's possible to brick one with current set of tools..
-CC
Novarider said:
Fair enough.
I have a question about this Utility. If I install this will I be able to gain access to the data folder so I can drop some apks into it with root explorer? I would like to be able to use a different keyboard and I was reading I need to be able to rename a keyboard and drop it there for it to work.
I had used adb to install superuser but it didn't do anything once installed so I deleted it
Click to expand...
Click to collapse
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
norkoastal said:
This should do it since the script installs Superuser and Root Explorer can perform the functions mentioned (you may need to hit the button on the top of the program for R/W). As with any mod - proceed with caution or find a step by step to guide you.
Click to expand...
Click to collapse
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Novarider said:
I can follow the root guide on nookdevs site and just replace the program with this one right? I have root explorer now but it doesnt allow access to data since it can't be granted root access
Click to expand...
Click to collapse
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
johnopsec said:
Yep. That will do it.
I got the droid-x multi-touch keyboard working a few days ago but that was several resets ago as well. Things didn't go exactly perfect for me and there were several reboots where I didn't have a keyboard at all. I can't remember the exact steps I took but, I eventually side-loaded the droid-x keyboard and it worked. I'll tinker more tonight on that. It's beer-thirty now though!
Click to expand...
Click to collapse
If you figure out an easy way to install the keyboard without having to rename files in system or anything like that please let me know. I hate the stock keyboard on the NC
Step-by-Step Needed
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
docfreed said:
Does the script install Root Explorer or do we still have to use ADB to install apps? Is it possible to put APK's on an SD card and install them?
Click to expand...
Click to collapse
It would be great if this activated it because I can't install apks from the sd card now
When will it arrive?for 101 i mean
It won't happen until we get permanant root. No telling when that will happen.
a better question is, when will root be available, doesn't seem we have people with the right skills interested on the 101
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
adb push root/rageagainstthecage /data/local/tmp
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage
./data/local/tmp/rageagainstthecage
Click to expand...
Click to collapse
It should kick you out and display some messages on the screen...just not errors. Then type:
adb shell
Click to expand...
Click to collapse
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
jerdog said:
Does the rageagainstthemachine root patch not work? Are you able to get to the /data/local directory and place something there that will allow for a flash_image command to be run? Do we know if they have the same type of hardware-level protection like HTC does?
EDIT: Can someone do the following:
1. download the rage zip enclosed, and unzip to it's own directory
2. run the following from your command prompt, assuming you have the Android SDK installed and in the path
It should kick you out and display some messages on the screen...just not errors. Then type:
You Should see a "#".
If so, then we have temp root and then we should be able to perform some other functions like flash a recovery, etc....
Sent with my fingertips and voice on my Evo
Click to expand...
Click to collapse
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Tsusai said:
It does not work as of the latest Archos firmware. All the previous firmwares/z4root work fine for temp root. The ADB device part of the Archos just never comes back (doesn't show in device manager for instance). I do not know if this helps, but Archos also has a crippled busybox and it seems furthered crippled as of the last firmware upgrade.
Click to expand...
Click to collapse
Maybe have something to do with newer ARM architecture?
Sent with my fingertips and voice on my Evo
Why do you need permanent root?
Archos kindly released SDE which provides a way to install your own builds in dual boot.
Some links for more info:
http://forum.xda-developers.com/showthread.php?t=871335
http://www.openaos.org/
IRC #openaos on freenode
Maurice
The SDE require booting in recovery mode, and people said that it's often not perfect.
A permanent root for main OS would still be very useful, and still allow us to dual boot when we need to..
I think so too. PermaRoot would be very usefull.
Anyone accomplished this?
If so, elaborate.
Thanks,
Its possible to do it with adb and the command line. Are you familar with using one?
Im very familiar with my mac. I've only used terminal twice to run some java code I wrote.
Sent from my MB860 using XDA App
dmappdev said:
Im very familiar with my mac.
Click to expand...
Click to collapse
i think he meant ADB and the command line
Ok, so the extent of my knowledge, as it pertains to ADB and terminal, is limited. I can search my mac for files using terminal. Thats it..
I too would appreciate someone to break it down for a n00b such as myself. I don't have a copy of windows so if there is a way without bootcamp that would be awesome!
I've ported DG's aRoot script to a mac form, but I've never done anything like this before so at the moment I'm waiting him to respond to a PM asking permission to post it.
I thought I remembered him saying somewhere that he gave public permission to use the script, but I've been unable to find it. If anyone can find me this link, I'll post it, otherwise I will as soon as I get DG's blessing (assuming he gives it).
Would you be able to use VMware Fusion for something like this - with windows installed? I was about to try that until I read this thread. May have dodged a bullet there. I've been reading this forum for weeks, very informative. Learnin' a bunch.
Cheers.
Hey guys,
I currently have LeoMar Revolution ROM installed, so phone is rooted, Superuser works fine etc.
Want to start playing around with adb (am new to this) and have the device showing up when running 'adb devices' but i cannot get adb root? Although the device is rooted ok?
So question is (yes i searched but cant find the answer) are phone root and adb root different things?
If so how do i go about getting adb root so i can push apps etc from cmd line?
Thanks in advance
kangfu84 said:
Hey guys,
I currently have LeoMar Revolution ROM installed, so phone is rooted, Superuser works fine etc.
Want to start playing around with adb (am new to this) and have the device showing up when running 'adb devices' but i cannot get adb root? Although the device is rooted ok?
So question is (yes i searched but cant find the answer) are phone root and adb root different things?
If so how do i go about getting adb root so i can push apps etc from cmd line?
Thanks in advance
Click to expand...
Click to collapse
When through cmd, you write su and press enter
If you get a $ sign, then you aren't adb rooted!
If you get a # sign, then you are adb rooted!
Umm, for adb root, I guess use superoneclick root and click shell root, you will get the # sign then!
Thanks for quick reply
I run abd shell and then su and i do get the #.
id=0 so i have root in an 'abd shell' but i cant get root when i just put 'adb root'
Tried to adb push the apks manually in adb shell but adb push doesnt exist in shell?
But i am trying to run a batch file that pushes some hidden apks and i get the error "cannot run as root in production builds" when i run the batch file?
Edit: I may have had a secure kernel installed, will try another kernel and re-try. Is it possible to have su rights when booted up with a secure kernel? That would explain things ..
kangfu84 said:
Thanks for quick reply
I run abd shell and then su and i do get the #.
id=0 so i have root in an 'abd shell' but i cant get root when i just put 'adb root'
But i am trying to run a batch file that pushes some hidden apks and i get the error "cannot run as root in production builds" when i run the batch file?
Edit: I may have had a secure kernel installed, will try another kernel and re-try. Is it possible to have su rights when booted up with a secure kernel? That would explain things ..
Click to expand...
Click to collapse
I have never tried doing pushing/pulling on stock/secure kernels ... so I can't tell you what's going wrong!
Will have a play with flashing other kernels and try again.
I have the yellow triangle show up on boot so i thought i had an insecure kernel. But maybe it is just there from when i installed a previous ROM/insecure kernel?
kangfu84 said:
Will have a play with flashing other kernels and try again.
I have the yellow triangle show up on boot so i thought i had an insecure kernel. But maybe it is just there from when i installed a previous ROM/insecure kernel?
Click to expand...
Click to collapse
Yellow triangle means you have a insecure kernel, maybe, Cf-root
"adb root" was only available on the original "Google dev phones" and requires special code somewhere on the phone (in the kernal?) to support it. When you root the phone it does not include the special code for "adb root" to work. I don't know what you need to do to get it working, but most people don't bother because there are other ways to do the same thing.
{Build:KI4, Version:1.3.4 (stock, rooted)}
LouisJB said:
"adb root" was only available on the original "Google dev phones" and requires special code somewhere on the phone (in the kernal?) to support it. When you root the phone it does not include the special code for "adb root" to work. I don't know what you need to do to get it working, but most people don't bother because there are other ways to do the same thing.
{Build:KI4, Version:1.3.4 (stock, rooted)}
Click to expand...
Click to collapse
Can i adb push apk's as su in an adb shell?
If so i guess i can push the apks i want to manually instead of using the batch file which is trying to get adb root.
kangfu84 said:
Can i adb push apk's as su in an adb shell?
Click to expand...
Click to collapse
1. If you use one of my insecure kernels, adb will be running as root, issue "adb root" and it will reply "adb is already running as root"
2. Yes you can adb push when using su root.
3. Why do you want to push APKs? If its to install them, then just use adb install <FILE NAME>
adb root can be used when ro.debuggable is set to 1 in /default.prop
and on every reboot ro.debuggable is replaced by the one in kernel you are using
Why did you bump a thread from November 2011 to post this gem? Is that what "Recognized Contributors" do? I did wonder.
Geez Oinky. I could really take that comment of yours (which is true on so many levels) & run with it ;-) But I can't be arsed these days (like more than a few people on here).
Probably one of the criteria for getting RC status; how many 8 mth old threads you bump over X period of time
oinkylicious said:
Why did you bump a thread from November 2011 to post this gem? Is that what "Recognized Contributors" do? I did wonder.
Click to expand...
Click to collapse
i was googling something related to this but not this and found this thread, readed it all and found that no one had answered this
then i thought many others can also look for this and i thought of answering for others who are googling for it not for the op, because i know op had got the answer many moths ago
and real xda member never offense but help others
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..