So, I think my question is useful to a lot of us, even myself, so I hope someone could help me out. It goes a little something like this:
I have a Nook Tablet, wrapped under my xmas tree. Going straight to the point: what is the best way to get it rooted, under the light of this new software update? On the 25th December, should I turn it on, register it, quickly disable wifi, and start to root it, along with the titanium backup solution? Shoud this work? Or do you have another (and better) solution?
Thanks in advance to all who can help us!
Just got mine today and root couldn't have been easier using this thread -> [Update 12/10/11] Full root for Nook Tablet. [11/20/11] [Permanent root!]
I never saw anything come up on the tablet about an update. Side loaded apps work fine also, just installed all 3 angry birds.
Thanks! A bunch, really! You made my day!
Just got mine today as well. Prepare to root after reading the thread here.
SteelH said:
Just got mine today and root couldn't have been easier using this thread -> [Update 12/10/11] Full root for Nook Tablet. [11/20/11] [Permanent root!]
I never saw anything come up on the tablet about an update. Side loaded apps work fine also, just installed all 3 angry birds.
Click to expand...
Click to collapse
Hi, would like to know if you have the Wi-Fi ON all the way during the process? Thanks!
keidgeibef said:
So, I think my question is useful to a lot of us, even myself, so I hope someone could help me out. It goes a little something like this:
I have a Nook Tablet, wrapped under my xmas tree. Going straight to the point: what is the best way to get it rooted, under the light of this new software update? On the 25th December, should I turn it on, register it, quickly disable wifi, and start to root it, along with the titanium backup solution? Shoud this work? Or do you have another (and better) solution?
Thanks in advance to all who can help us!
Click to expand...
Click to collapse
Just to be safe, first thing I would do after turning on and registering is go straight to root thread and download tgps app. then disable wifi. then after rooted, enable wifi and download titanium backup, then freeze devicemanager.apk. this will block verification of software version.There are other methods of blocking OTA.
Also, there is still a question on if they are even pushing OTA, some of us never got one and have left our devices on for the past couple of days...
albertwertz said:
Just to be safe, first thing I would do after turning on and registering is go straight to root thread and download tgps app. then disable wifi. then after rooted, enable wifi and download titanium backup, then freeze devicemanager.apk. this will block verification of software version.There are other methods of blocking OTA.
Also, there is still a question on if they are even pushing OTA, some of us never got one and have left our devices on for the past couple of days...
Click to expand...
Click to collapse
Do I need to download tgps app directly on the nook, can't I push it through my sd card?
Yes, comptonsoft.com/test and select the top left link.
So it looks like we can still root if ee have one sitting under the tree waiting for us huh? I had been debating between this and the acer a100 and chose this for the battery life and ease of root/use factors. Hmm. Thanks for the info
Sent from my LG-P925 using Tapatalk
you can root anyway, just might have to sideload stock rom of 1.4.0 through sdcard restore
---------- Post added at 10:36 AM ---------- Previous post was at 10:36 AM ----------
keidgeibef said:
Do I need to download tgps app directly on the nook, can't I push it through my sd card?
Click to expand...
Click to collapse
yes, can be done through sdcard as well
Thanks, albertwertz
I just wish someone could post a really simple guide (n00b alert) on how people who don't have their NT yet could root it and bypass this software update as soon as possible...
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
In theory if this is all true; we should be ok even after the weekend.
I will do mine tonight but I need to do my wife's after she opens it; I'm not letting B&N spoil the surprise
radtechy said:
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
In theory if this is all true; we should be ok even after the weekend.
I will do mine tonight but I need to do my wife's after she opens it; I'm not letting B&N spoil the surprise
Click to expand...
Click to collapse
Thanks I'm filled with relief... Happy xmas, everyone!!!
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
You just made my day.....
Root and don't worry thanks a bunch albert.
Are you are the guy who made the you tube tutorial?
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
Looks like I WON'T be sending my Nook back after all! Thanks so much!
radtechy said:
From what I heard as with any nook device in the past....."a software update shouldn't start to update immeadtely as soon as it's turned on"
So hopefully like mentioned above register turn off wifi, root then TGPS etc. This way you avoid leaving yourself open to get hit with the update.
Click to expand...
Click to collapse
Assuming your modem is not also your wifi router, just unplug the modem before you register the device and if you like, you can still use wifi to load files from a local file server. No need to worry about how quickly you disable wifi if there is no line to the outside world.
albertwertz said:
Just got confirmation that Indirect's root removes OTA automatically. So once you root with a PC, ***and install GAPPs***, it will forever be rooted unless you force sideload the update.
Click to expand...
Click to collapse
How did you confirm?
Not saying your lying, but I don't know how you would be able to confirm it blocks OTA updates.
radtechy said:
You just made my day.....
Root and don't worry thanks a bunch albert.
Are you are the guy who made the you tube tutorial?
Click to expand...
Click to collapse
yes, the link in my signature should direct you there. I make a bunch of other stuff too
---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------
xdahgary said:
How did you confirm?
Not saying your lying, but I don't know how you would be able to confirm it blocks OTA updates.
Click to expand...
Click to collapse
we talk through gtalk and irc. He said that the GAPPS part removes OTA and he just added those comments to his root thread.
albertwertz said:
yes, the link in my signature should direct you there. I make a bunch of other stuff too
---------- Post added at 12:12 PM ---------- Previous post was at 12:12 PM ----------
we talk through gtalk and irc. He said that the GAPPS part removes OTA and he just added those comments to his root thread.
Click to expand...
Click to collapse
Is there a default location to get these GAPPS from beforehand? As well as any other needed software for root/applications etc.
Related
The folks at liliputing have just published a fix for the 1.4.1 upgrade that will allow normal sideloading just as was possible with 1.4.0. All that is necessary is that you must have enabled sideloading when you had 1.4.
ROOTING IS NOT NECESSARY!!!
Here is the link to enable 3rd party apps in 1.4.1
http://liliputing.com/2011/12/sideload-apps-on-a-nook-tablet-with-os-1-4-1-no-root-required.html
Here is the link to enabling 3rd party downloads in 1.4.0 if you don't have it
http://liliputing.com/2011/11/how-t...ok-tablet-amazon-appstore-go-launcher-ex.html
Now quit yer bellyaching and get to work. Merry Christmas
Special shout out to Indirect for pointing the way to this simple work around for the rest of us.
mohawkx said:
All that is necessary is that you must have enabled sideloading when you had 1.4.
Click to expand...
Click to collapse
Forgive me if I misunderstand. But that means it's still NOT possible to do it once you have 1.4.1? I'm worried because I'll be opening one tomorrow and don't know if I should even turn it on until I'm ready to root it.
DagobahSamurai said:
Forgive me if I misunderstand. But that means it's still NOT possible to do it once you have 1.4.1? I'm worried because I'll be opening one tomorrow and don't know if I should even turn it on until I'm ready to root it.
Click to expand...
Click to collapse
the instructions further down on the first page explain how to revert a 1.4.1 updated NT to 1.4.0. For moreinfo you can find the original thread for that procedure on this forum
DagobahSamurai said:
Forgive me if I misunderstand. But that means it's still NOT possible to do it once you have 1.4.1? I'm worried because I'll be opening one tomorrow and don't know if I should even turn it on until I'm ready to root it.
Click to expand...
Click to collapse
Don't worry. I turned mine on for the first time yesterday. Registered and downloaded the tgps apk and did some surfing around for about 30 minutes before turning wiring off without it download the update. I was able to do a successful root and launcher install following Indirect's thread. You'll be fine as long as you can follow simple instructions.
they show you how to do it using ADB, honestly this is not easy for the average user and very inconvenient. It is easier to follow a video on reverting back to 1.4.0 and block OTA IMHO...
To give credit where it's due, the tutorials on Liliputing are based on information (and tools) gathered from Indirect and AdamOutler at xda-developers.
I just tried to flesh things out with a slightly more detailed walkthrough and photos.
Indirect's utility for sideloading: http://forum.xda-developers.com/showthread.php?t=1407023
AdamOutler's tool for performing a factory reset and rolling back to OS version 1.4.0: http://forum.xda-developers.com/showthread.php?t=1402190
What about enabling USB debugging ???
albertwertz said:
they show you how to do it using ADB,...
Click to expand...
Click to collapse
Has anyone actually USED this with ADB???
I mean, you need to have USB debugging enabled in the NT after the upgrade, and I think the upgrade resets it. It certainly is now reset in my NT, and I'm fairly sure I had it enabled before the 1.4.1 upgrade.
On the Acer A500 section of this site, someone has posted a trick to gain root if:
You have root and apply the trick.
You update to a new version that removes root.
You can then access the device via ADB.
If there's a way to turn on USB debugging in 1.4.1 (I still have command-line access via ConnectBot, just not root access), that would be nice. Or, if someone knows a non-root app that can do it, I will:
Revert to 1.4.0.
Root it.
Install the trick.
Upgrade to 1.4.1.
Enable USB debugging.
Use the trick to regain root access.
DeanGibson said:
Has anyone actually USED this with ADB???
I mean, you need to have USB debugging enabled in the NT after the upgrade, and I think the upgrade resets it. It certainly is now reset in my NT, and I'm fairly sure I had it enabled before the 1.4.1 upgrade.
On the Acer A500 section of this site, someone has posted a trick to gain root if:
You have root and apply the trick.
You update to a new version that removes root.
You can then access the device via ADB.
If there's a way to turn on USB debugging in 1.4.1 (I still have command-line access via ConnectBot, just not root access), that would be nice. Or, if someone knows a non-root app that can do it, I will:
Revert to 1.4.0.
Root it.
Install the trick.
Upgrade to 1.4.1.
Enable USB debugging.
Use the trick to regain root access.
Click to expand...
Click to collapse
You can use NT Hidden Settings but naturally it has to be installed before the update.
I played around with 1.4.1 before reverting and adb install works. Root is the real kicker for me though because I use the host file for ad blocking and I use button savior. Both require root.
Sent from my BNTV250 using xda premium
What about enabling USB debugging ???
dragon_76 said:
You can use NT Hidden Settings but naturally it has to be installed before the update.
Click to expand...
Click to collapse
EDIT: Here: http://forum.xda-developers.com/showthread.php?t=1400615
doesn't work;
i constantly get "device not found"
DeanGibson said:
OK, where is "NT Hidden Settings"???
Click to expand...
Click to collapse
There's a thread in development. Someone on here created it.
jayochs said:
doesn't work;
i constantly get "device not found"
Click to expand...
Click to collapse
With what? Are you getting this with the rooting tools? If so, have you been able to reenable USB debugging? Because without that, the rooting tools won't work.
no, i haven't rooted mine, but i read this script works for the unrooted tab. was i mistaken?
Device Not Found Error
I was able to sideload 5 apps using the Indirect instructions. Then, I needed about two more apps and that's when I received the device not found error message when trying to sideload Launcher Pro.
I have the install third party box checked and both USB debugging boxes and nothing in the auto mount. Although, I tried it with both USB boxes checked and the auto mount checked still the same error.
I even started from scratch in DOS and got the same error.
Any suggestions?
---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------
Ok, after writing the first post, I went back to my NT and unchecked and re-checked the third party box. Then went to the Development area and unchecked the second USB debugging box and left the auto mount box unchecked.
I then went to the first USB debugging box and unchecked and re-checked the box. Then went back to DOS to load my last two apps and it worked!
jayochs said:
no, i haven't rooted mine, but i read this script works for the unrooted tab. was i mistaken?
Click to expand...
Click to collapse
Hm... I'm confused. What script, and where exactly are you getting the "Device not found" message from? On the Tablet? On the PC? What exactly are you doing that triggers the message? (i.e. "I click on the download status notification, and click the .apk that I downloaded and it pulls up a dialog that says, "OH NOES! I HATESES YOU! Device not found." ... text invented for humorous intent.)
nevermind, got it! i didn't have the right ADB drivers installed. i just followed this thread post:
http://forum.xda-developers.com/showpost.php?p=19573474&postcount=11
and i got it working
---------- Post added at 10:46 PM ---------- Previous post was at 10:37 PM ----------
some apps, though, are telling me:
INSTALL FAILED MISSING SHARED LIBRARY
anyone getting that? idk what it means.
i'm able to download amazon apps, then find them in ES explorer, put the apk on my pc, then push it using this method..that works fine..but some apps that i can find on websites give me that (since idk how else to get an app at this point lol)
INSTALL FAILED MISSING SHARED LIBRARY
anyone getting that? idk what it means.
Click to expand...
Click to collapse
This usually means that there is a missing .so file somewhere. Not sure why you would be getting it, and of course, there is no message about _WHICH_ shared library is missing.
Which apps are giving this, and at what stage? Is this the whole of the message it sends you?
1.4.1 rooted with full Android Market access !!!
DeanGibson said:
...
On the Acer A500 section of this site, someone has posted a trick to gain root if:
You have root and apply the trick.
You update to a new version that removes root.
You can then access the device via ADB.
Click to expand...
Click to collapse
Full details on the Nook Tablet in a few hours. I lost the "n" button after reverting to 1.4.0 via Adam's method, and need to retry the whole sequence again after going to a virgin B&N 1.4.0 state. If that works (ie, the "n" button works), I will publish details, but the above is correct.
EDIT #1: Here is the relevant info: http://bookclubs.barnesandnoble.com...ith-full-root-and-Android-Market/td-p/1249365
EDIT #2: B&N removed the above message for "links to a file that could potentially damage our customers NOOK Tablets ... linkage to direct downloads or filehosting sites." I will repost that message in a separate thread here soon.
cfoesch said:
This usually means that there is a missing .so file somewhere. Not sure why you would be getting it, and of course, there is no message about _WHICH_ shared library is missing.
Which apps are giving this, and at what stage? Is this the whole of the message it sends you?
Click to expand...
Click to collapse
i get this with apps like weatherbug...i can NOT for the life of me find one that installs on here. i backed up my apk from my rezound with mybackuppro, tried to push it, and that happened.
also, i've got google voice up and running...anyone know if there's a way to make calls with it? lol..also, are there push notifications? i'm not getting text notifications right away at all
dragon_76 said:
You can use NT Hidden Settings but naturally it has to be installed before the update.
I played around with 1.4.1 before reverting and adb install works. Root is the real kicker for me though because I use the host file for ad blocking and I use button savior. Both require root.
Sent from my BNTV250 using xda premium
Click to expand...
Click to collapse
Please forgive the simple question....been gone from the forum for a week, and came back to all this BN update crap! If I am currently unrooted and on 1.4.0, is it as simple as downloading brianf21's hidden settings app? What do I do after the update kicks in? Try to access the hidden settings app and turn usb debugging back on? Am I missing something? Thanks.
Ok folks,
If you're lucky enough to get a TP that's rootable with RazorClaw, you're gonna wanna keep it. Problem is that Asus keeps trying to ram a firmware update down our throats that kills root. We can't have that.
Problem with the OTA is that it keeps spamming you to update, and also in theory at least, you can only postpone it 3 times before it forces you too. Hitting back works somewhat, but you're still gonna get spammed.
The TP also immediately looks for the update as soon as it attaches to wireless.
SwiftKS provided me with the idea of freezing it with TiBu. While it could work in theory, I couldn't get it work as TiBu will only freeze the app with Pro version. I have the pro version, but it wouldn't recognize my key without connecting to market. Which, as you guessed, also lets the TP go out and grab the OTA.
Thanks to some the folks over in the "For any chance of root on TP..." thread in General, I found something else that works.
As always on here, I'm not responsible for anything going wrong or you bricking your device. You assume all risk. If you have your apps backed up, I suggest moving them to your PC to copy back later.
1. Root with RazorClaw if you haven't already.
2. Download Voodoo OTA Root keeper from Market
3. Run Voodoo OTA Rootkeeper and have it protect root
4. Once it says it's protected, download and install the OTA
5. After the OTA is applied, go back into Voodoo OTA Rootkeeper and have it restore superuser.
6. Enjoy!
Thanks to SwiftKS for planting the idea, and the guys in the mentioned thread above for their idea.
Have a great holiday folks!
Hmm, also, you could probably use File Explorer and go in to system/app and rename Update Launcher.apk
Possibly. Didn't try that as I thought it might still try to do its thing even with a different name.
Hehe, Android isn't THAT smart. But, if they're paranoid they could always remove the file from the system/app folder and drop it onto an SD card for safe keeping.
****.
After a few hours, it pulled it down. Must be another process at work.
Mods, feel free to close/delete the thread. Or if anyone else has any ideas, they're welcome to post.
I tried.
could probably just move the. Apk to somewhere else completely or rename it to ****update.apk.bak (don't have one ATM.) Should have one tomorrow so I'll look more into it.
di11igaf said:
could probably just move the. Apk to somewhere else completely or rename it to ****update.apk.bak (don't have one ATM.) Should have one tomorrow so I'll look more into it.
Click to expand...
Click to collapse
That's what I've been thinking. Seemed to work for everything I didn't want to run in the past. My experience is limited to DInc and GB but there's no reason why it shouldn't work here. Assuming it's the only apk thats responsible for the upgrade process. Alternatively, you could block asus servers from the host file perhaps?
The update makes things so much better though ::-(
Sent from my Transformer Prime TF201 using xda premium
You could always get the update(assuming someone can grab it somehow), see what is does/replaces, then just push the updated system/framework files to the old firmware then have the best of both worlds.
Remember with root you can manually push anything in /system you want just can't flash kernels and the like yet u til we have a recovery working or a way to rite a new kernel.
When I get the tp hopefully it won't be updated. We should be able to grab the update via adb and pre root it (maybe) if that is possible ill post my results
sent from my Atrix via XDA premium
What does it improve?
I can try renaming the apk and awe what happens. I'm not sure what it'll do though as it still says the process isn't running.
I'd prefer to keep root so unless someone has tried rooting then updating, I'm hesitant to try it.
I did find done files that look like they were downloaded last night in the /d directory. Didn't muck with them though without a recovery.
Sent from my Galaxy Nexus using XDA App
when it downloads the update does it reboot into recovery?
if there is a way to get between that with adb we could pull the update and check it out, possibly add root to it and see if the update will continue.
Can you please add in your post what is Prime firmware version!
Thanks
marko! said:
when it downloads the update does it reboot into recovery?
if there is a way to get between that with adb we could pull the update and check it out, possibly add root to it and see if the update will continue.
Click to expand...
Click to collapse
I held off on updating for 3 days but then ******* friend didn't know what to do and hit to update it. I thought about what you said. It does boot into recovery. I was trying to find where the OTA was being stored those 3 days that it was downloaded to my prime, but I couldn't find it. Of course I only checked the system folder and forgot to check the data folder. I'll look to see if it's there now but I have a feeling it's been deleted since the update has been done already.
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
ka911 said:
Can you please add in your post what is Prime firmware version!
Thanks
Click to expand...
Click to collapse
The prime version that is rootable is 8.8.3.23 build
Gamestop retails come out with 8.8.3.27 build (not rootable)
The OTA build makes it 8.8.3.29 (not rootable)
Superguy had a best buy model that had the 8.8.3.23 build.
unknown_owner said:
I held off on updating for 3 days but then ******* friend didn't know what to do and hit to update it. I thought about what you said. It does boot into recovery. I was trying to find where the OTA was being stored those 3 days that it was downloaded to my prime, but I couldn't find it. Of course I only checked the system folder and forgot to check the data folder. I'll look to see if it's there now but I have a feeling it's been deleted since the update has been done already.
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
The prime version that is rootable is 8.8.3.23 build
Gamestop retails come out with 8.8.3.27 build (not rootable)
The OTA build makes it 8.8.3.29 (not rootable)
Superguy had a best buy model that had the 8.8.3.23 build.
Click to expand...
Click to collapse
Most likely it gets downloaded to the cache!
if anyone who is rooted can get into adb after DL the update just try
Code:
adb root
adb pull /cache
has anyone tried any of the other root methods or just the one included with razorclaw?
Find where the download comes from, and block it using the hosts file. Look in the resources/data for the update app for the ip.
marko! said:
has anyone tried any of the other root methods or just the one included with razorclaw?
Click to expand...
Click to collapse
I tried a lot of the methods out there but no luck of course on any of them even the tried the other root method from the original TF.
TONS of people should be getting the TF from Best Buy tomorrow or Wednesday. So hopefully we can get some people to try some things! I'm gonna be searching all over the place for that update!
dsmitty166 said:
TONS of people should be getting the TF from Best Buy tomorrow or Wednesday. So hopefully we can get some people to try some things! I'm gonna be searching all over the place for that update!
Click to expand...
Click to collapse
A zip of the OTA can be found here
unknown_owner said:
A zip of the OTA can be found here
Click to expand...
Click to collapse
Now, to see if we can add root to the update...
I have a rooted Tablet (1.4.0, OTA blocked). I watched Netflix fine last night at the around 10pm.
Today I try opening Netflix and every title I attempt to watch gives me the same error, 1005. It seems to be the error that netflix gives when it's a device that was not previously allowed.
Argh. Should I try installing Netflix from the Amazon App store? Are they the same thing? Would anything like that work?
I've already restarted my Nook and attempted to re-connect to Wifi. My account still works, as I've been able to watch Netflix on my computer.
Anyone else having issues?
Thanks!
Working fine for me and Im on 1.4.0 (ota blocked) also.
I'm pretty sure the netflix app on the amazon store is not the same as the one on the NT.. The NT is netflix certified so it plays at higher resolution than other tablets with the app and the netflix on the NT probably has some changes to support the NT DRM.
Sent from Nook Tablet
So it turns out that apparentally I'm on 1.4.1 now. I tried to go through amazon app store and install their Netflix app... and it said something along the lines of "you don't have permission to install apps." **** you B&N.
I rooted after Indirect released his total root package. I just verified again, since I still have the folder on my desktop, and it contains FOTAKill.apk in the system/app/ directory.
I just followed directions, and I had full root and working Google services after I followed the steps. This is upsetting
I may have messed something up but.. it's hard to mess up double clicking a .bat file haha.
I'll just have to format and revert back to 1.4.0
Wufei74 said:
So it turns out that apparentally I'm on 1.4.1 now. I tried to go through amazon app store and install their Netflix app... and it said something along the lines of "you don't have permission to install apps." **** you B&N.
I rooted after Indirect released his total root package. I just verified again, since I still have the folder on my desktop, and it contains FOTAKill.apk in the system/app/ directory.
I just followed directions, and I had full root and working Google services after I followed the steps. This is upsetting
I may have messed something up but.. it's hard to mess up double clicking a .bat file haha.
I'll just have to format and revert back to 1.4.0
Click to expand...
Click to collapse
Yes people is reporting that some OTA kill methods stopped working, not sure if the replacing device manager method works well but i think B&N will find a way to override it and push the new update again, hopefully someone come up with something definitive. Recommendation always make a backup with titanium backup i've seen many posts that it works good.
Veronica
lavero.burgos said:
Yes people is reporting that some OTA kill methods stopped working
Click to expand...
Click to collapse
Where are people reporting this?
This is the first post I've seen that claims that idirect's method of blocking OTA's doesn't work. If that's really the case, I would expect to see tons of reports coming in that NT's with OTA's blocked via idirect's method are updating.
Is anyone else actually having this issue?
Or is it an isolated incident?
---------- Post added at 05:02 PM ---------- Previous post was at 04:16 PM ----------
Wufei74 said:
I rooted after Indirect released his total root package. I just verified again, since I still have the folder on my desktop, and it contains FOTAKill.apk in the system/app/ directory.
Click to expand...
Click to collapse
Also, Wufei74, did you use indirect's method for modifying data for devicemanager? Because that seems to be only sure way to block OTAs. Having the fotakill.apk in the system directory doesn't do the trick. You need to actually modify the devicemanager, as explained here, by indirect:
http://forum.xda-developers.com/showthread.php?t=1405418
Do us a favor and let us know if you actually did this before your NT updated, yes? Because if you did do it and your NT still updated, then we could all be getting updates soon. On the other hand if you did NOT do it and simply relied on the fotakill.apk, then the reason your NT updated is clear. Either way, the more information you provide, the easier it will be for us to determine what we're dealing with here.
Hello,
I have a rooted NT on 1.4.1 and this morning it seems the the OTA block did not function because it upgraded to 1.4.2 on it own.
It doens't seem to have affected the root so far, but I haven't explored everthing.
When I click on the NT Hidden settings OTA block i have a message stating :
Missing /system/bin/su
What can I do to block any further ota upgrades. When I rooted I am preety sure that I had made sure that OTA were blocked...
Thanks.
Nathalie
same here
I also looked at my rooted tablet today and it said the 1.4.2 OTA installed.
I had rooted from 1.4.1 using the SD card method.
I had run the OTA blocker but still got 1.4.2
It did not appear to break the root but I had limited time to check things.
Hoping to hear others comments on this issue.
And looking for a OTA block that works.
I tried titanium back-up block at one time but had issues, might just try it again.
This is bummer news. I was hoping I was done with the B&N BS.
install cm7 if you can. It works nice and unlocks the mic
Sent from my DROID RAZR using XDA App
You can root 1.4.2 with any "Root Card" method.
michaelkthx said:
install cm7 if you can. It works nice and unlocks the mic
Sent from my DROID RAZR using XDA App
Click to expand...
Click to collapse
I'm sticking with a rooted 1.4.0 for now. The issue is that I've read the B&N stock apps don't work on CM7. You could download the B&N app from the Market but it doens't have the same functionallity. Some who subscribe to magazines have reported they can't view their subscriptions on the B&N Market app. It seems to be an issue that depends on the magazine as some are OK and some aren't.
rwischer said:
I'm sticking with a rooted 1.4.0 for now. The issue is that I've read the B&N stock apps don't work on CM7. You could download the B&N app from the Market but it doens't have the same functionallity. Some who subscribe to magazines have reported they can't view their subscriptions on the B&N Market app. It seems to be an issue that depends on the magazine as some are OK and some aren't.
Click to expand...
Click to collapse
None of my magazines are accessible through any B&N Market app (Time, SI, GQ, etc.), but I thought rooting still allows you to access all the vanilla B&N content in addition to Market apps?
EDIT: Whoops, missed the part about CM7. Yes, a different ROM doesn't access the B&N stock apps, as I understand it.
So what should i do because, it seems that i have lost android market, it is asking for a new account. And the email and talk do not work either...
I am kinda lost here because i do not want to brick my NT...
Any suggestions?
Nathalie0226 said:
So what should i do because, it seems that i have lost android market, it is asking for a new account. And the email and talk do not work either...
I am kinda lost here because i do not want to brick my NT...
Any suggestions?
Click to expand...
Click to collapse
The OTA has removed your root access. Which in turn means you can no longer use the packages installed after the root process. Basically refer back to GabrialDestruir's post where he said the 'root card' methods should still work fine. Your best bet IMO is to either install internally, or use an sdcard version of CWM recovery and if you want stock, download and install one of the stock flashable roms in the development section. Else install CM7. Or stay on 1.4.2, your call.
Know-Fear said:
The OTA has removed your root access. Which in turn means you can no longer use the packages installed after the root process. Basically refer back to GabrialDestruir's post where he said the 'root card' methods should still work fine. Your best bet IMO is to either install internally, or use an sdcard version of CWM recovery and if you want stock, download and install one of the stock flashable roms in the development section. Else install CM7. Or stay on 1.4.2, your call.
Click to expand...
Click to collapse
I'm running 1.4.2 and it's all nicely rooted, you just have to used a "Root Card" aka a card which by whatever means adds all sorts of root glory to your device. There are like two or three of these that actually exist for the Nook Tablet, choose one burn the sdcard and follow the instructions and you get a functioning stock root device.
GabrialDestruir said:
I'm running 1.4.2 and it's all nicely rooted, you just have to used a "Root Card" aka a card which by whatever means adds all sorts of root glory to your device. There are like two or three of these that actually exist for the Nook Tablet, choose one burn the sdcard and follow the instructions and you get a functioning stock root device.
Click to expand...
Click to collapse
I am trying to get mine to update to 1.4.2, so I can get the fixes from 1.4.1 mainly...and plan to use a root card after the update. But I cannot get mine to update after having done the OTA block. I manually downloaded the update and dropped it in the root of my nt, and its been hours and it hasent applies any update and still says version 9.9.9
GabrialDestruir said:
I'm running 1.4.2 and it's all nicely rooted, you just have to used a "Root Card" aka a card which by whatever means adds all sorts of root glory to your device. There are like two or three of these that actually exist for the Nook Tablet, choose one burn the sdcard and follow the instructions and you get a functioning stock root device.
Click to expand...
Click to collapse
So GabrialDestruir, I initially used Albert Wertz root method using an sd card.
Should I re-root my NT using the same method as it is right now or should I un-root it prior rooting it again.
It's not that clear for me yet how I should proceed.
Thanks.
LivDoug said:
I am trying to get mine to update to 1.4.2, so I can get the fixes from 1.4.1 mainly...and plan to use a root card after the update. But I cannot get mine to update after having done the OTA block. I manually downloaded the update and dropped it in the root of my nt, and its been hours and it hasent applies any update and still says version 9.9.9
Click to expand...
Click to collapse
If I'm not mistaken, if your version says 9.9.9, it won't update.
*Sorry to the OP for the hijack*
Moved To Q&A
Please post all questions in the Q&A section
does this work on 1.4.2?
i forgot to block OTA when i was at 1.4.1 and it automatically updated to 1.4.2 now...
http://www.droid-life.com/2013/01/1...-2-receiving-surprise-update-to-build-vrall4/
Probably exynos patch.
Can someone grab the update.zip file and post it here?
Was just about to ask about this. I just got the update but I'm rooted so it failed, just wanted to see if it's anything worthwhile unrooting for
As long as you have a custom recovery it won't install.
So...someone capture the update URL by doing a logcat
adb shell logcat > logcat.txt, accept update and post it.
omgitswes said:
Was just about to ask about this. I just got the update but I'm rooted so it failed, just wanted to see if it's anything worthwhile unrooting for
Click to expand...
Click to collapse
Too bad you didn't logcat it.
Check your /cache for files.
Freakin website for info about it doesnt work either. verizonwireless.com\galaxynotellsupport is in the update page but cant tell if the "ll" is LL's or II's. Why wouldnt they just put the number 2 to eliminate issues. either site doesnt work. That is just ridiculously stupid web admins.
adrynalyne said:
Too bad you didn't logcat it.
Check your /cache for files.
Click to expand...
Click to collapse
Not sure how to do a logcat. Nothing is in my cache though
vtec2k7 said:
Freakin website for info about it doesnt work either. verizonwireless.com\galaxynotellsupport is in the update page but cant tell if the "ll" is LL's or II's. Why wouldnt they just put the number 2 to eliminate issues. either site doesnt work. That is just ridiculously stupid web admins.
Click to expand...
Click to collapse
yeah I tried all of the combinations none worked.
It just failed on my phone. Unfortunately I can only defer it for 5 days, but by then I figure a workaround will be found.
The update installs Google Wallet.
Kidding.
Sent from my SCH-I605 using Tapatalk 2
SeanPlunk said:
It just failed on my phone. Unfortunately I can only defer it for 5 days, but by then I figure a workaround will be found.
Click to expand...
Click to collapse
Too bad you didn't logcat it either.
Did you check /cache for any files?
adrynalyne said:
As long as you have a custom recovery it won't install.
So...someone capture the update URL by doing a logcat
adb shell logcat > logcat.txt, accept update and post it.
Click to expand...
Click to collapse
Hopefully this is what you need.
Looks like I was able to get the update.zip as well, gimmie a minute and I'll post that too.
ILMF said:
Hopefully this is what you need.
Click to expand...
Click to collapse
Unfortunately, no. It doesn't contain the needed info I need a full logcat.
Thanks for trying!
This was in /cache also the update only allows you to defer for 5 days so hopefully we can figure out what it does
I'm thinking that if, as I did, you gained root via the ExynosAbuse exploit application if you turn off the patch but keep root active (in the application settings) that will allow Verizon to patch the exploit however you'll still have root. I think this is correct but I'm not sure.
Here is the update. The file is downloaded to /cache/fota
ryngds said:
This was in /cache also the update only allows you to defer for 5 days so hopefully we can figure out what it does
Click to expand...
Click to collapse
Thanks!
I will let you know whats in it. The first thing I see, is a new bootloader. We can imagine why.
Ok updated are:
1. Phone
2. MMS
3. SystemUI
4. Settings
5. Modem
6. Bootloader
7. Browser
8. Contacts
9. HiddenMenu (maybe)
10. libbcc.so.sha1
11. kernel
I don't know what the updates are, I am going by patch size.
I'm rooted on stock with a few tweaks - nothing I can't live without. The initial update failed. I saved root using Voodoo, unrooted, and tried the update again. It failed the second time. I'm not inclined to do anything else until I see what the update entails and if we can retain root. I like my root
I used exynos abuse apk to achieve root. Then ota root keeper to protect it. I have many disabled apps and installed the ota with no issue and restored root fine.
I never unrooted either.