[Q] MD5: manualnooter looks like it worked but su fails - Nook Color Q&A, Help & Troubleshooting

Hi all. I just rooted a Nook Color using the instructions at http://forum.xda-developers.com/showthread.php?t=1494901 using manualnooter-5.08.20.basic.zip and also installed the Dalingrin OC kernel indicated on that page. It looks like everything worked. I'm able to install apps etc. but:
ROM Manager says 'You must root your phone...'
The Superuser app updated with no problems.
Execute of su in a terminal says 'I/O error'
ls -l /system/bin indicates no su.
I tried uNooter the first time and had the same message from ROM Manager.
Any suggestions?? This is the first android tablet I've tried to root and at this point I'm stuck.
Thanks!

Related

Superuser?

Does anyone know how to install this on the aria?
http://forum.xda-developers.com/showthread.php?t=682828
It's best to flash your Aria to a Liberated ROM. You can find it within the forums here. Since I can't post links yet. This will root the device and SuperUser will be added.
Not sure about that app. It looks like it does the same thing as the SU that comes in the Liberated ROM by attn1, just without the few extra options.
I tried booting into clockwork and mounting the system partition and doing this:
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot
but when it rebooted the superuser app did nothing at all. No prompt or nothing running apps that needs su. I had usb debugging enabled. So I just restored a nand backup.
Might be a dumb question, but did you do adb remount ?
I used clockwork to mount the system partition. When I tried it with just adb remount it wouldn't mount the system partition. I would always get "Not a directory" error. But when clockwork mounted the partition it wrote the files fine with no error. When I rebooted the superuser icon and version were different than the one that came with the liberated rom.
I'm trying this now, I'll report back when I do it. I'll try a few different apps that require SU
I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.
It's probably not compatible with our phone yet.
Could be, but I'm pretty sure it does work, because if I remember correctly, Titanium Backup needs SU permissions, and I haven't encountered any kind of errors with it yet.
I see you posted on the thread for the program itself. Hopefully someone there will have a response.
Yeah, I'm hoping to get a response to it. We will see.
The newer version 2.2.2 works.
Awesome, ill give it a shot a little later.
Tried the newer version, and I get the same issues.
How did you install this one? I booted in to clockwork and selected install from zip file on sd and selected that file on my sd card.
I just did it through adb. I'll give that method a shot.
Looks like after doing your method, it works perfect now. Not sure why using adb doesn't work.

[Q] Help with busybox

Hi guys. I have already rooted my Wildfire with unrevoked3 and worked like a charm. Superuser is OK, I installed Titanium Backup and I installed busybox with it.
But I can't find how to run the busybox shell with root. Can anyone help me?
I downloaded android sdk for my Ubuntu 10.10 (I don't use windows) and I typed as root: ./adb shell and the terminal has not root priviledges.
Is there anyway to do this? Also how to run busybox? Via Terminal Emulator?
I think that the Titanium Backup didn't installed correctly.
My goal is to get a root terminal
Thanks in advance
Assuming that stuff works the same as on my linux computer, you would just su in the terminal emulator, then cd into the busybox directory, then make sure you have execute permissions for it, and then just ./busybox. That should start busybox in shell mode. That's how it should work.I think.
xc1024 said:
Assuming that stuff works the same as on my linux computer, you would just su in the terminal emulator, then cd into the busybox directory, then make sure you have execute permissions for it, and then just ./busybox. That should start busybox in shell mode. That's how it should work.I think.
Click to expand...
Click to collapse
The busybox is executed in my machine not in my phone right?
No, on your phone. Open up terminal on your phone (you can get one off the Market or alternatively connect you phone to the computer and start a ashell using adb), then cd to the directory you have busybox in, and then ececute ./busybox. Remember, you can't put it on the SD card because it doesn't allow execution.
sorry for this Android newbie question..
I installed Titanium Backup on my Desire....but when I ran it, an error message says " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again".
My Froyo is rooted....but whats this BusyBox and where can I get it and install it?
thanks..
I'm assuming you haven't rooted yet. Turn wifi on. Get an app called "universal androot". You need to get a version at least 1.6.2. It's not in the market so you may have to look around. Install and Open it up. Tick the box that says "soft root". Click the button labelled "root ". When the application force closes, wait 10 second and do nothing. then click on force close. Toggle wifi on. Go to titanium. Press allow when asked for root privileges. If it doesn't come up, look around titanium. It should allow you to instal busybox. Busybox is a set of *NIX utilities that are better than androids builtin. It allows the apps to use more advanced features. And It helps users if they are knowledgeable though to know how to use it.
nope..mine is rooted already via unrevoked3
dinoalbert said:
sorry for this Android newbie question..
I installed Titanium Backup on my Desire....but when I ran it, an error message says " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again".
Click to expand...
Click to collapse
Same problem here
rooted with revok3
installed rom manager and did a first backup
install titanium n tried to backup apps
It said " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again"
could some one link me to busybox app for wildfire n guide on how to backup wit titanium
pl reply
realxception said:
Same problem here
rooted with revok3
installed rom manager and did a first backup
install titanium n tried to backup apps
It said " Sorry I cannot acquire root priviledges. This application will not work! Please verify that your ROM is rooted and includes BusyBox, and try again"
could some one link me to busybox app for wildfire n guide on how to backup wit titanium
pl reply
Click to expand...
Click to collapse
Go to titanium backup, go to problems then it,will install busybox
thanks , its worked

ROM Manager problem

Hi, when I tried to flash a rom using ROM Manager, it said that I don't have ClockWork mod, which I do. Also when I try to flash the ClockWork Mod it says
"An error occurred while attempting to run privileged commands".
Any ideas why that happened? Thanks.
Have u rooted it?
Sent from my HTC click using XDA App
i guess andynroid is right... sounds, as if the root wasn't done... just check this possibility
my description in this thread also gives you a brief overview about the steps to flash your rom
I'm having a similar issue:
Any apps state that i don't have root access, but the adb shell starts in # and i'm able to navigate in /system and so on.
RomManager is apparently not able to install the recovery, allthough the 1-click thingy did finish successfully.
the root checker app complains about /system/xbin/su which i can't seem to find in the adb shell
any suggestions?
wolf.thalian said:
I'm having a similar issue:
Any apps state that i don't have root access, but the adb shell starts in # and i'm able to navigate in /system and so on.
RomManager is apparently not able to install the recovery, allthough the 1-click thingy did finish successfully.
the root checker app complains about /system/xbin/su which i can't seem to find in the adb shell
any suggestions?
Click to expand...
Click to collapse
try typing in a root shell: ln /system/bin/su /system/xbin/su

[Q] MN 5.08.20: manualnooter looks like it worked but su fails

Hi all. I just rooted a Nook Color using the instructions at http://forum.xda-developers.com/showthread.php?t=1494901 using manualnooter-5.08.20.basic.zip and also installed the Dalingrin OC kernel indicated on that page. It looks like everything worked. I'm able to install apps etc. but:
ROM Manager says 'You must root your phone...'
The Superuser app updated with no problems.
Execute of su in a terminal says 'I/O error'
I finally got adb sorted out and 'adb shell', 'ls -l /system/bin/su' says I/O error but 'echo su*' indicates the file is present. strange...
I didn't see any errors in output and couldn't find any files in /cache/recovery.
I tried uNooter the first time and had the same message from ROM Manager.
Any suggestions?? This is the first android tablet I've tried to root and at this point I'm stuck.
Thanks!

[Q] How to root ZTE Open / 1.4

I have flashed my ZTE Open to FFOS 1.4 with this method (http://forum.xda-developers.com/showthread.php?t=2680514), only some bugs - AND: How can I root the ZTE, this method ( pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions) don't work. My before 1.2-prerelease-version was rooted of course.
martin_s5670 said:
I have flashed my ZTE Open to FFOS 1.4 with this method (http://forum.xda-developers.com/showthread.php?t=2680514), only some bugs - AND: How can I root the ZTE, this method ( pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions) don't work. My before 1.2-prerelease-version was rooted of course.
Click to expand...
Click to collapse
You can install cwm recovery and root first with 1.1 or 1.2 then install 1.4 and do a factory reset from cwm. It should tell you lost root and install it again for you.
Yes, I have done this several times, but i can't get /system/xbin. There is only a "su" in /system/bin.
martin_s5670 said:
Yes, I have done this several times, but i can't get /system/xbin. There is only a "su" in /system/bin.
Click to expand...
Click to collapse
Have you tried if "su" works from ADB?:
1) adb shell
2) su
if it works from there you must be able to use it to install it in xbin.
I'm repeating the process in a new one I got this afternoon... maybe I can make a quick guide from zero.
Exactly that's my problem: su don't work. I get:
...
[email protected]:/ # su
su
/system/bin/sh: su: not found
127|[email protected]:/ #
...
Therefore: How to root a FFOS 1.4?
martin_s5670 said:
Exactly that's my problem: su don't work. I get:
...
[email protected]:/ # su
su
/system/bin/sh: su: not found
127|[email protected]:/ #
...
Therefore: How to root a FFOS 1.4?
Click to expand...
Click to collapse
That means that the utility you've used to root your phone hasn't worked. Just a heads up: you need to be on Firefox OS 1.0 to root your phone, every version after has patched it (because the only reason you can root it in the first place is a vunerability which has since been fixed).
Google search "Firefox OS 1.2 ZTE OPEN" and click on the top link to the Mozilla Hacks website with the title of "Upgrading your ZTE Open to Firefox 1.1 or 1.2 (fastboot enabled)", then scroll down to the bottom and click the 1 to go to the first page of comments, then scroll to the bottom again and click the bottom link to find a google drive download called "update-signed.zip". Download that and install it, enable "Remote Debugging" in developer settings, root your phone, install CWM Recovery and re-download and install the OS you want to use.
Pardon, but I know all this, how to root etc ZTE 1.0 resp. 1.2 - and I have a rooted ZTE 1.2. The problem is, that after installing 1.4 you have no root, you can't get the su-binaries in /system/xbin.
martin_s5670 said:
Pardon, but I know all this, how to root etc ZTE 1.0 resp. 1.2 - and I have a rooted ZTE 1.2. The problem is, that after installing 1.4 you have no root, you can't get the su-binaries in /system/xbin.
Click to expand...
Click to collapse
Oh I'm sorry I understand now! I assume that is an issue with 1.4 not being finished yet, I imagine the only real solution is to revert back to a "finished" build of B2G

Categories

Resources