Rooted becomes Unrooted

---

First, thanks for getting all this figured out and posted! I like the idea of getting a rooted Nook Tablet without being stuck at 1.4.0.

I've been through the procedures to root my 16 GB NT twice, and while both times it appears to work at the end of the procedure it doesn't appear that I'm fully rooted. The Superuser application is installed but won't update the su binary (Downloading the manifest fails). The first time I thought it was the version of the su binary that was in gapps/system/bin. It was different than the version in rooting/system/bin and wasn't executible. So I made the versions the same and tried again from the beginning (back to 1.4.0, erase/deregister, etc.). Same result. It looks like I'm rooted at first but when I try to install anything that requires root access it fails. ADB Root Hijack appeared to work but must not have since the adbd daemon is running as "shell". Superuser (com.noshufou.android.su) is running as "app_50".

So I have a few questions:

1. What should I look for to verify whether I do or don't have root? I still have access via adb, although it's not root access.
2. Can I get root access again without going through the whole procedure? I have the Zeam Launcher, Google Play store, etc. but can't install anything requiring root access. Which is kind of the whole point.
3. If I do go through all this again, is there a way to get some of the applications I want installed as part of the process? Also, could a modified build.props be installed in the processs so that it allows any app to be installed from the Play store?

I don't know if it would work in Android, but in Unix it's common to allow sudo access to the root account via the /etc/sudoers file. If that works then that could be set up so that even if root access is lost it could be easily regained, at least for a session, by having some accounts able to do "sudo su -". Just a thought.

Thanks again!

Originally Posted by Nick3193

...
I've been through the procedures to root my 16 GB NT twice, and while both times it appears to work at the end of the procedure it doesn't appear that I'm fully rooted. The Superuser application is installed but won't update the su binary (Downloading the manifest fails). The first time I thought it was the version of the su binary that was in gapps/system/bin. It was different than the version in rooting/system/bin and wasn't executible. So I made the versions the same and tried again from the beginning (back to 1.4.0, erase/deregister, etc.). Same result. It looks like I'm rooted at first but when I try to install anything that requires root access it fails. ADB Root Hijack appeared to work but must not have since the adbd daemon is running as "shell". Superuser (com.noshufou.android.su) is running as "app_50".

So I have a few questions:

1. What should I look for to verify whether I do or don't have root? I still have access via adb, although it's not root access.
2. Can I get root access again without going through the whole procedure? I have the Zeam Launcher, Google Play store, etc. but can't install anything requiring root access. Which is kind of the whole point.
3. If I do go through all this again, is there a way to get some of the applications I want installed as part of the process? Also, could a modified build.props be installed in the processs so that it allows any app to be installed from the Play store?

1. If "AdbRoot-2" didn't give any errors, you have root. Otherwise, the script will give errors.
2. "gapps/system/bin" ??? Where'd that come from ???
3. What happens if you get a shell prompt, and then type "su" ???
4. I have no idea if you can get root again without going through the whole procedure, since I have no idea what the state of your NT is.
5. Installing regular apps via the Market also does some DB updating (I have no idea what), so I'd recommend using the Market (or adb install) to do it. I've run through my procedure more than a dozen times, and I use the Market to install ALL apps each time. It's one less variable to consider if I have issues later.
6. Did you install "Superuser.apk" via the Market, or did you try to do it a different way?
7. The Market will auto-update to "Google Play". You shouldn't have to do anything but be patient.
8. I don't believe "sudo" is installed.

I'm a Linux-type person, but I (surprisingly) find that some Linux users have more problems with the procedure, because they make assumptions about the process. If you follow it exactly, it should work.

Intruders in gapps folder

---

Originally Posted by DeanGibson

1. If "AdbRoot-2" didn't give any errors, you have root. Otherwise, the script will give errors.
2. "gapps/system/bin" ??? Where'd that come from ???
3. What happens if you get a shell prompt, and then type "su" ???
4. I have no idea if you can get root again without going through the whole procedure, since I have no idea what the state of your NT is.
5. Installing regular apps via the Market also does some DB updating (I have no idea what), so I'd recommend using the Market (or adb install) to do it. I've run through my procedure more than a dozen times, and I use the Market to install ALL apps each time. It's one less variable to consider if I have issues later.
6. Did you install "Superuser.apk" via the Market, or did you try to do it a different way?
7. The Market will auto-update to "Google Play". You shouldn't have to do anything but be patient.
8. I don't believe "sudo" is installed.

I'm a Linux-type person, but I (surprisingly) find that some Linux users have more problems with the procedure, because they make assumptions about the process. If you follow it exactly, it should work.

1. AdbRoot2 didn't give any errors, and from what I can see I did have root at that point. All the files copied in by that script are owned by root, and all the symbolic links it creates to busybox in /system/xbin are as well. The command "adb shell chmod 6755 /system/bin/su" in the script doesn't error but unless permissions are displayed different on the NT, the set-uid, set-gid bits in the permissions mask aren't there after the final reboot. Whether they were before or not I can't say.
2. It came from '2.4. Create a folder (in the directory that you will be running ADB from) called "gapps" on your PC.
   Download a copy of the Google base apps onto your PC, and unzip it into your new "gapps" folder.' I found several copies of the google base apps on XDA, and while I thought I used the one from your link it looks like I had a different one which included Superuser. I'll replace it with the right one
3. "Permission denied"
4. Then I'll start over. Just figured I'd ask on the off chance.
5. Superuser was in the gapps set as I mentioned above, along with one called PackageInstaller.apk. I'll make sure those aren't there before I do this again. Somehow I'm betting that was the problem; all the other files were the same.
6. I haven't had any problem with the market. Both times it upgraded to Google play within minutes.

Thanks again for all the help! Third time's a charm, right?

---------- Post added 26th March 2012 at 12:36 AM ---------- Previous post was 25th March 2012 at 11:55 PM ----------

The rogue superuser.apk in the google apps zip was the culprit. This time your process worked just fine. Installed Superuser from the market, upgraded su, and everything's great! Thanks!

i killed it?

---

I've got two NOOK Tabs here, one of them I started the root process as outlined by this thread. Since the tablet I have here is on 1.4.2, so I booted with a SD with only the acclaim_update.zip file to get back to 1.4.0; the NOOK did boot, but then it died. I will not take a charge, will not power on (20sec or 5sec boot). It's bricked.

B&N is sending a replacement. My question is, do you think that this device bricked because of the root process or the timing was coincidental? I'd had to get this replacement and then brick it again.

Note: I'm following all the steps to a "T" on this thread. I had not even begun the main "rooting" process, I was only using the acclaim_update.zip on SD to get back to 1.4.0.

Any help would be greatly appreciated!

ah...

---

Just an update, i received my new NOOK replacement. I just notice it's an 8GB model. I know this thread pertains to the 16GB model, so this may be why my tablet bit the dust as noted in my above post. Hmm...i swear I looked up the memory capacity via model number.

Support for B&N v1.4.3 added

---

It's a release candidate; if no one has issues with it, I will make it a release in a few days.

It may just be my ignorance, but I'm unable to root my NT 16GB using the B&N v1.4.3 upgrade option. When I run "rooting\AdbRoot-2.cmd" the remount fails (permission denied) and of course everything fails after that. One thing I noticed in the script and the "Expected.log" file is that there appear to be extra files not available in the 1.06 zip:

local.rootusb
local.rootwifi
local.usb
local.wifi

These apparently weren't needed in the 1.05 version, and they're not present in the rooting/local directory in the 1.06 version. Is there somewhere where I need to obtain these files? Rooting using the 1.05 version and updating to B&N v1.4.2 *does* work, btw.

Any hints would be much appreciated.

Thanks again!

Ack!

---

Originally Posted by Steve-Z

It may just be my ignorance, but I'm unable to root my NT 16GB using the B&N v1.4.3 upgrade option. When I run "rooting\AdbRoot-2.cmd" the remount fails (permission denied) and of course everything fails after that. One thing I noticed in the script and the "Expected.log" file is that there appear to be extra files not available in the 1.06 zip:

local.rootusb
local.rootwifi
local.usb
local.wifi

These apparently weren't needed in the 1.05 version, and they're not present in the rooting/local directory in the 1.06 version. Is there somewhere where I need to obtain these files? Rooting using the 1.05 version and updating to B&N v1.4.2 *does* work, btw.

I:

1. renamed the local.* files,
2. changed the filenames in the scripts,
3. but forgot to include the new files in the .ZIP file !!!

That's why "it worked here" ... fixed in v1.07 (uploaded).

However, note that I have sold my Nook Tablet and moved on, so I probably won't be posting any new updates (other than stupid stuff like this). Fortunately, B&N is probably at the end of their software support for the Nook Tablet (sales of new units stopped in December).