***Solved*** I ended up using Albert's 4.5 along with his videos, worked great!!
Thanks again for all the help.
Believe it or not I have searched and read much in attempting to answer these questions without starting another thread. Probably because I am such an android noob I am not able to find answers I understand.
Primary questions:
Using windows SD card flash method from this thread:
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
I am able to flash the SD card with the image fine.
Not sure what the note under instruction step 2 means
Instruction 2 "NOTE: Do not extract the .zip with superuser and su."
step 6 says to put "the zip" in the root of the sd card. What zip are we talking about? There was only a single download zip with all the files including the image so I assume it means this complete download zip even though it makes references later to "update.zip" (I do not have a file named "update.zip".
When I reboot after inserting the sd card I get the screens as described but the verbiage is not exactly as listed in the instructions.
Options I receive:
"install zip from sd card"
"choose zip from sdcard"
"apply /sdcard/update.zip"
selecting /sdcard/cwm_sd_flash_and_exe.zip
receive
"finding update package"
"opening update package"
"installing update...
"installation aborted"
Secondary questions:
o Do all of the many rooting options get you to the same end result?
ie same version of android, market access, updates blocked, additional apps, loader options, etc
o Are we close enough to a true dual boot sd option (leaving base device untouched) as referenced in the cm7 release thread that I should just wait for that?
Thanks much for any help for a noob, and I beg forgiveness if I am treading ground that has been explained many times before.
As i see that you can boot into CWM i would suggest to get a more finished ROM for yourself, i have posted one of them. They are in development section you might want to take a look, there are 2 roms for 1.4.0 and one for 1.4.1.
All the root methods are not the same, and it all relies on what you want, for example keep B&N content or debloat B&N content, also there are some methods that don't include all google apps. So take a look at what they offer and pick what best suits you.
As for dualboot sdcard it is possible as everything in life but its not close. First let devs release a beta of CM7 and wait for CM9, eventually we will get there just be patience.
~ Veronica
Noob Root Questions me too!
I haven' t tried this yet but had the same basic questions about the instructions (i.e. which zip is being referred to). I believe you are told not to click on the su, super user zip cause you should install that AFTER you have established the basic root (i.e., get CWM and install Nook/Zergy). I could be wrong, maybe one if the kind people that know more can clarify this. In the meantime I think I am going to use the video AlbertWeitz made on youtube with accompanying links to scripts for root. Check youtube or development threads, he offers videos on rooting NT with an SD card to include or not include access to the Barnes and Noble software for your library. I think having the video will help. This is not really a different root method but based on the work of Indirect (whose post you are following) and many others...Albert did add some apps I think. Indirect also released a Superuser Tool recently (in dev thread) which has root in it but no specific instructions when you select the root process...just what you find in the post you are looking at (no offense to Indirect....you are a god!) Albert's mission has been to help us noobs along with the root already developed by making videos. I think he intends to make one for Indirect's Supertool but why wait? Once you've rooted you will b able to instsll beta ROM theoretically coming this Tuesday internally. External ROM as suggested in previous posts, is sometime off in the future.
I hope this info helps. I've pmed Albert to make sure that OP is up to date as far as the links go, I checked the whole thread and don't see any subsequent changes. Hopefully he will have time to respond and I will repost reply here (if I can figure out how to do that)! Still unsure of how to attach links to posts...how do you do that?
L
---------- Post added at 12:21 AM ---------- Previous post was at 12:09 AM ----------
Checked your suggested ROM and looks great...just too chicken to try it without a video to follow! Noob jitters....
From the thread you jsut quoted, it took me a day to figure it out the first time I rooted
I've been keeping up on that forum as much as I can since I got my Nook Tablet two weeks ago. In order to get my install to work, I ended up having to read that entire thread, bouncing between instructional posts, downloading repetative files, and getting confused over some personal issues. So I think I'll toss in my personal version of how to install things using Windose, an SD card, and the file links scattered throughout that thread:
In summary, read the folllowing posts:
Original Thread (Post #1)
Post #14
Post #141
Wach this Youtube as well:
http://www.youtube.com/watch?v=I403bagL9rw
Assuming you have a brand new microSD card, plop it into the cormer or your nook. Don't worry about formatting it, you'll be re-formating it again. Connect your Nook to your PC with the USB, and your PC will recognize two new drives:
MyNOOK, and whatever your new microSD card happens to be factory named.
Stage 1: Mounting the boot image
1. From Post #14, download the linked file "CWM_SD_flash_and_exe.zip"
2. Extract the zip and run "Win32DiskImager.exe"
3. Select the "cwm_sd_flashing_boot.img" and ensure that the Device drive is the correct one (like I: and not your C
**Reading through other threads, there are links (now dead) to other image files, and an appended "update.zip" file. Do not worry about these, as the packaged image is all you need.
4. Your miscroSD card will now be named "boot" and only have a size of about 70MB.
**Your nook will think your SD card is bad at this point. A Warning popup will say, "SD card format required - This memory card is unrecognized and needs to be formatted.
5. Ignore the message to format, and reboot your Nook. Either hold down the power key and power back on, or hold the power+N key.
6. The moment your nook powers back on, hold down the N key until you get a white screen with a cardboard box. This will bring up the boot menu
**You do not need your USB plugged in, despite other posts instructing you as such. As long as you hold down the N key within 3 seconds of it rebooting, you get a box on a white bachground that leads to the boot loader.
7. usign the volume buttons to scroll, select the "update.zip". Use "N" to select and tap the power button to back out of a menu.
After you've finished, you'll boot up with the option of going to "Home" or "ADW.Launcher"
That should be it!
---------- Post added at 04:24 AM ---------- Previous post was at 04:17 AM ----------
P.S. I have a brand new Nook Tablet with 1.4.1 preinstalled.
I've rerooted my NT a few times already in the last week, and I now think the best version is actually Albert's 4.5 found here:
http://forum.xda-developers.com/showthread.php?t=1439630
... at least until CM7 is ready.
**Solved** Thanks much!!
Thanks everyone for the help, I certainly appreciate it!!
I am about to try the process again. Just to confirm:
ZirbMonkey -
1st, I am assuming the recommended method you describe in your post is a more recent recommendation than the one in your sig (Albert's 4.5).
CWM_SD_flash_and_exe.zip is the same file name I have been using. I realize it may be a different version and will check it as I go through the process you detailed so well, but the version I used before didn't have an "update.zip" in it. Am I expecting that there will be an update.zip on the SD card after taking the steps you've detailed, is there already a file with that name on the NT, or something else? Also, am I browsing to an "update.zip" file on the sd card or taking the menu option that has "update.zip" in the name?
Maybe this will all become evident as I go thru the process but I'd like to understand as much as I can before I start so I don't screw up.
Again, thank you for your patience dealing with my lack of knowledge in this area.
If using Albertwertz 4.5 root Update Hidden settings to block OTA updates
I finished root too using Albertwertz's 4.5, very easy with video. If you used this be sure to update your hidden settings app from the market then block OTA updates. This app in the currently uploaded zip is earlier version and does not block OTAs. Check your software version in About Your Nook in settings after your root is complete. If it does not indicate that OTAs are blocked you need to do this by updating hidden settings app already installed with root by downloading the app update from the Android Market......then going in app to choose OTA updates block, otherwise a future update could kill your root! It does not roll it back to V 9.9.9, but stays V1.41 (with note below version number stating OTAs are blocked) when you are done.
There is a separate post by Albert (in dev thread...look for key word OTA updates) indicating he updated the hidden settings app (after uploading Root 4.5 zip). You also need to go into DEVELOPMENT option in updated Hidden Settings app and click on both USB debugging boxes. Don't forget to enable Unknown Sources too!
Geez really need to learn how to embed links in his site!
Thanks to Albert, Indirect and everyone else involved in root and bootloader crack!
L
prsa01 said:
**Solved** Thanks much!!
Thanks everyone for the help, I certainly appreciate it!!
I am about to try the process again. Just to confirm:
ZirbMonkey -
1st, I am assuming the recommended method you describe in your post is a more recent recommendation than the one in your sig (Albert's 4.5).
CWM_SD_flash_and_exe.zip is the same file name I have been using. I realize it may be a different version and will check it as I go through the process you detailed so well, but the version I used before didn't have an "update.zip" in it. Am I expecting that there will be an update.zip on the SD card after taking the steps you've detailed, is there already a file with that name on the NT, or something else? Also, am I browsing to an "update.zip" file on the sd card or taking the menu option that has "update.zip" in the name?
Maybe this will all become evident as I go thru the process but I'd like to understand as much as I can before I start so I don't screw up.
Again, thank you for your patience dealing with my lack of knowledge in this area.
Click to expand...
Click to collapse
The "update.zip" is for the original method, where there was a file with that name in the base directory of the flashed card. I believe this is/was the second option on the rooting menu.
But the new (4.5) method uses a different zip file, so you have to "update from a .zip" (first menu option?) and select the zip that shows up at the bottom of the next menu. Sorry, but I'm working from memory as I reset my memory card after I flash it to get full use of it back again.
It's still not working for me - Like prsa01, I found no such "update.zip" file, so I tried "CWM_SD_flash_and_exe.zip" (the only "zip" file on the SDcard).
It starts to install, then aborts:
Code:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
what am I doing wrong?
---------- Post added at 06:14 PM ---------- Previous post was at 05:51 PM ----------
I couldn't get this method to work (is it because I didn't enable debugging first? Enabling debuggin is not mentioned in the instructions. CWM loads, but I get an "Installing update... Installation aborted." message - see prev post)
This method says you have to enable USB debugging first, but the instructions for doing so don't work for me. You're supposed to download and install an apk, then click "settings" when you see the "install blocked" message - trouble is, my installs are NOT blocked - not since the first time I sideloaded an app. Is there another way to get to the hidden settings menu? or do I need to do a factory reset and start over?
KyleK...
Perhaps you have this taken care of this issue by now. I just rooted my Nook and used the Hidden Settings apk I think you are referring too. I see that others on the forum have reference the Play Store as the source for the apk.
here is the link: https://play.google.com/store/apps/details?id=com.brianf21.nthiddensettings&hl=en
Once installed you can use your file manager to locate the app. Going into settings/development where you find the selectable states for USB debugging (on) and Auto Mount (off).
There are notes in the forum about keeping track of these settings to make sure they stay set. I noticed before I rooted the setting would change on every re-start.
In my case I use ES explorer to look at my files. I launch it from the search tab, the Hidden Settings app icon is sitting on my home directory. Every time I use this application it says it will re-install and retain all previous data. You may find that a bit odd.
Related
Hi all,
First off, just want to say thanks to all of the hardworking devs out there that put a lot of time and effort into these projects. You guys are really awesome!
Secondly, I tried to post this as a reply in the developer's forum, but didn't have enough posts to qualify.
That all being said, I followed all of the instructions in Indirect's post here, but can't get the Nook Tablet to bring up recovery mode when I reboot. It just continues to load the standard B&N image. I even tried a factory reset to see if that would work, but same problem. I verified that the files on the micro-SD card match those as shown in Albert's excellent video here. The device is still running 1.4.0.
Any assistance is greatly appreciated!
No luck here either...I tried the root while watching Albert's You Tube video at the same time. I think the significant thing is that my screen displays something like:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installation Complete!
Install from sdcard complete.
Whereas the screen in the video shows:
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
Installing GApps 29110878
For Android 2.3.5 Customized for the nook tablet
Mounting data...
Extracting files to data...
Unmounting data...
Install complete. Enjoy!
Installation Complete!
So clearly my install seems to silently abort somewhere in the middle...
Any insight or advice would be appreciated!
Removed...
~ Veronica
Sent from XDA premium using my Nook Tablet
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
It's not about Rooting OR recovery. It's about the fact that this method is still being worked on. Indirect has been making modifications to the various files and it is my opinion that the file used in Albert's video is NOT the same file that would be downloaded if you went and obtained it right now.
I would wait this out until Indirect writes an updated post explaining that the method is finalized.
If this is not an option the original root method works perfectly.
Land - when you say "original root method" are you talking about something that predates Albert's solution?
jearley9 said:
Land - when you say "original root method" are you talking about something that predates Albert's solution?
Click to expand...
Click to collapse
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
jearley9 said:
Beatbox,
Just re-reading your post I think I got farther than you, but also got stuck on your issue earlier. If you keep the Nook plugged into the PC via the USB cable during the power on, the Nook will boot into the recovery mode - that at least was what got me past your issue.
Click to expand...
Click to collapse
Cool jearley9, this did indeed work for me and I was able to load the image. Problem now is that I always end up at the normal B&N Setup screen. Were you able to get past that part?
And thanks to all the other thread participants. I know it takes time to work these things out, so no biggie. We all get a little too excited and impatient with things like these sometimes.
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
jearley9 said:
Thanks - looking it over now...
---------- Post added at 02:58 PM ---------- Previous post was at 02:53 PM ----------
Beat,
Does your screen match my screen or the one in Albert's video? If it matches then you and I have the same problem. If not then you have something different going on...
Click to expand...
Click to collapse
Definitely matches yours. Just didn't know if you got further than I did after rebooting.
Land Master said:
See this Thread
If you are running 1.4.1 you will need to downgrade first.
See Here
Click to expand...
Click to collapse
Just wanted to provide an update. I attempted the instructions from the original rooting thread (my nook tablet doesn't have 1.4.1 yet, so didn't need to downgrade). When I ran the batch file to root, it detected that the device was already rooted - which I quote from the script, "Is bothersome."
Okay, so i think my device is half-rooted somehow. Just can't get the new home screen that I'm seeing on all the videos. I'll keep you guys updated with my further troubleshooting attempts.
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
I'm having the same issue, but I can use the search function to determine that apps WERE installed (and will execute properly). I believe that Indirect has removed ADW launcher and Homecatcher from the zip we're suppossed to drop onto the SD Card. My guess is that we're waiting for him to come up with a solution to the "Market not showing up in launcher" issue.
Can someone confirm this?
Well any other tactics I've tried have been to no avail, so I'll just be patient and wait for Indirect to address it. I'm sure he has enough on his plate without us bugging him.
Many thanks to him again for even working on something like this.
Edit:
Okay, for some reason I missed Albert Wertz's helpful Youtube comment:
Please Vote this comment up so everyone else can read it among all the others. Indirect is making some changes to the script, if you dont get adw to launch right after the first reboot from root, you may have to download it manually from the market. You can use the N button menu search function to pull up market by typing M in the search. You can launcher it from here. Until the bugs are worked out, you may only be able to install from market, sideloading may still be an issue. Indirect is fixin
Click to expand...
Click to collapse
I did this and have no problem bringing up the Android Market now. Just installed an app successfully. Not sure where it lives though. I could only seem to launch it from the Recently Downloaded icon at the bottom bar.
Edit 2:
Okay, just restarted after installing the ADW and now it prompted me to start with it. Only issue I have now is if I hit the N button, it reverts back to the original Barnes & Noble homescreen and I have to reboot to launch ADW again.
I got pretty much to the same place - I downloaded HomeCatcher but that seems to be non-functional - Looks like the Nook home screen is winning this round...
jearley9 said:
Beat, you and I are at least synchronized - I too tried the original root method, and I had the same exact problem as you describe... a message saying "already rooted". I did a system reset right before I tried the root, so I don't see how it could be "already rooted".
I just purchased my Nook yesterday. I am wondering if there are newer units (mine included) that are more resistant to being rooted?
Click to expand...
Click to collapse
To truly "reset" the system run the downgrade I linked previously EVEN IF you are on 1.4.0. After that it will be just like you took the NT out of the box. Then run the Indirect Root Batch and the "you are already rooted" should be gone. I would hope so anyway
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
jearley9 said:
Land,
I did the press and hold 9 times and got back to factory state.
Also, I tried Brianf21's files and I got the same problem as you. If I try to open Update.Zip from Windows it gives me "Please insert last disk of a multi-volume set...". I would guess that the zip file is malformed or incomplete, but that's just a guess...
-jearley
Click to expand...
Click to collapse
I copied this post to the Development Thread in my recent reply to Brianf21. It is conceivable at this point that you and I are the only ones that have tried this. lol
Please put information regarding future attempts in that thread to help him troubleshoot.
Glad to see that you were able to reset. I don't believe it will be necessary again if Brian fixes the issue. To my knowledge simply entering CWM using his image had NO affect on my NT.
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
jearley9 said:
Land,
Sorry I can't comply with your request - the forum software won't let me post in the development area due to my "newness" - I am 53 years old and have 30 years of software/firmware development experience, but to this forum I am a "newbie"
jearley
Click to expand...
Click to collapse
Alrighty then.... I don't know if I should laugh or cry. You can't even "post" in the Dev section? I wonder how many posts you need. Seems a little extreme to me but you will get there soon enough I guess.
In the meantime I'll make sure that your comments are known. Thanks!
i purchased 2 nook tablets for an 8 and 11 year old. im debating whether to not root it because i think it wil be easier for them to follow interface and the only downside i see is having to pay for apps that may be free on amazon or play store. can i have some input here? is there a super easy rooted rom that a child can follow? or are there many free aps if i just keep it as an out of box nook. thanks so much guys, these are the 1st gen nook tablets not the hd
Rooting just opens up the device. You'll still have full access to the stock interface and BN app store and what have you.
You can make a really child friendly user imterface with a rooted device running an alternate launcher. That way you can make different home screen with the apps you want them to use easily accessable.
Give it a go! It's really easy to go back should you want to.
asawi said:
Rooting just opens up the device. You'll still have full access to the stock interface and BN app store and what have you.
You can make a really child friendly user imterface with a rooted device running an alternate launcher. That way you can make different home screen with the apps you want them to use easily accessable.
Give it a go! It's really easy to go back should you want to.
Click to expand...
Click to collapse
thanks i dread having to do the whole sd card ota block thing again and havent done it in about a year. is there a good video out there to walk me through step by step again for the ota block? and can someone recommend the best barest bones rom to root afterwards to make it as easy for a child to use as possible?
and i think i had trouble the last time because only a certain size sd card could be used. wasn't it just the 2 or 4 gb that worked? thanks and sorry for all the questions. just have to get this done tonight so i can fedex it to texas to get there in time for xmas.
A rooted nook is just marginally better than a stock nook in terms of access to more apps, but might be more confusing to kids since it has two coexisting interfaces. You would be better off sticking with stock or go all out android with full-fledged CM10.
I think the rooted stock NT is loads better than than the true stock. LOADS! Had the stock reader dealt better with my side loaded books I wouldn't have installed CM10 internally.
I agree that the double interface can be a bit confusing but to kids that age it shouldn't be much of a problem.
The OTA block is just a process of a few clicks from within the NT hidden settings app.
asawi said:
I think the rooted stock NT is loads better than than the true stock. LOADS! Had the stock reader dealt better with my side loaded books I wouldn't have installed CM10 internally.
I agree that the double interface can be a bit confusing but to kids that age it shouldn't be much of a problem.
The OTA block is just a process of a few clicks from within the NT hidden settings app.
Click to expand...
Click to collapse
im trying to use the same albert video http://www.youtube.com/watch?v=1zbT1Fj38nE, but the file doesnt even seem to be there anymore, and his updated video shows how to create a root v4 card. im totally confused. do you still need to block otas? and if so is there another link that shows that step by step. im ready to just send these back and forget the whole thing
No need for any video!
There are a couple of ready-made root images that are almost automatic. Burn the card, pop it in, install zip from card and you're rooted. Go to Google Play (it may show up as "market" at first and make sure you have updated version of NT Hidden settings to block OTA. It could not be much easier! If can watch a film on your DVD player you can do this without instruction video!
Brian's root (that I havetried once and really liked!): http://forum.xda-developers.com/showthread.php?t=1488035
Alberts (that I have also used several times and like as well): http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
---------- Post added at 06:02 PM ---------- Previous post was at 05:39 PM ----------
And to expand a little:
1. Root the Tablet following the instructions in the root method you choose
2. Go to Google Market/Play and search for NT Hidden Settings
3. Open NT Hidden settings. Tap on "Hacks". When the prompt comes up "Allow" root access. You now get to a new menu where you can chhos Block OTA, Done!
Basic rooting instructions:
1. Download image file
2. Download imaging software if you don't already have it. (I like WinImage. I keep it in a folder and put my various image files in the same folder to make them easy to find)
3. Use your imaging software to burn a sd card. Albert's image will fit on a small card. I use a 1 GB, but I think smaller ones will do as well. Brian's image needs a larger card. I'm not sure how large, but the instructions probably tells you!
4. Boot to your sd card and follow the instructions for the method you have choosen. There are step by step instructions in both of the methods I have linked to, and probably others as well!
5. Done!
asawi said:
No need for any video!
There are a couple of ready-made root images that are almost automatic. Burn the card, pop it in, install zip from card and you're rooted. Go to Google Play (it may show up as "market" at first and make sure you have updated version of NT Hidden settings to block OTA. It could not be much easier! If can watch a film on your DVD player you can do this without instruction video!
Brian's root (that I havetried once and really liked!): http://forum.xda-developers.com/showthread.php?t=1488035
Alberts (that I have also used several times and like as well): http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
---------- Post added at 06:02 PM ---------- Previous post was at 05:39 PM ----------
And to expand a little:
1. Root the Tablet following the instructions in the root method you choose
2. Go to Google Market/Play and search for NT Hidden Settings
3. Open NT Hidden settings. Tap on "Hacks". When the prompt comes up "Allow" root access. You now get to a new menu where you can chhos Block OTA, Done!
Basic rooting instructions:
1. Download image file
2. Download imaging software if you don't already have it. (I like WinImage. I keep it in a folder and put my various image files in the same folder to make them easy to find)
3. Use your imaging software to burn a sd card. Albert's image will fit on a small card. I use a 1 GB, but I think smaller ones will do as well. Brian's image needs a larger card. I'm not sure how large, but the instructions probably tells you!
4. Boot to your sd card and follow the instructions for the method you have choosen. There are step by step instructions in both of the methods I have linked to, and probably others as well!
5. Done!
Click to expand...
Click to collapse
thank you so much for this help, figured it would be a slam dunk from here but when i try and unzip brians ntsdcard image file it says its corrupted and when i try and run alberts 32 diskimager it says it cant computer it. ive reinstalled and rebooted 3 times. can someone else try and open these file to se if its just my computer? dont know why it would be. or is there another work around? i heard he just sells the bootdisks. maybe thats the way to go. thanks again for all your help
I downloaded Albert's package. My virus protection alerter me, but that's probably because of the scripts that do need to be in that package, so I ignored that (I trust Albert!).
I then unzipped that into anew folder.
Inside that folder I find Wini32DiskImager, and I just open it from within that folder. (I realize I was mistaken in my previous post, This is the disk imager I prefer to use even though I've used others as well)
The program just opens in a small window. In the "choose file box" you automatically get directed to the folder you opened up from. That's why I keep my images there. Pick the one you want (you'll jut have one unless you've added)
Click "Write" when you've made sure the sd-cards drive letter is the one in the top right box.
gorelow said:
thank you so much for this help, figured it would be a slam dunk from here but when i try and unzip brians ntsdcard image file it says its corrupted and when i try and run alberts 32 diskimager it says it cant computer it. ive reinstalled and rebooted 3 times. can someone else try and open these file to se if its just my computer? dont know why it would be. or is there another work around? i heard he just sells the bootdisks. maybe thats the way to go. thanks again for all your help
Click to expand...
Click to collapse
this is the error i get the program cant start because libgcc_s dw2_dll is missing from your computer
I have now downbloaded and unszipped Brians file as well. Totally problem free!
What are you using to unzip? I use 7-zip.
By the way, I can now see that it looks like Brian's image needs a 2 GB card.
And for clairfication, you don't actually have to install Win32DiskImager. Just open it from within the folder!
---------- Post added at 08:33 PM ---------- Previous post was at 08:26 PM ----------
gorelow said:
this is the error i get the program cant start because libgcc_s dw2_dll is missing from your computer
Click to expand...
Click to collapse
Check the folder. That dll should be in the folder. It is in mine (the one I created just now). Are you really opening the program from within the folder?
The simplest and best rooting instruction I've found is one provided by liquidzoo's here.
I'd also suggest that before rooting the NT, you make a backup of your NT current software using the backup option of the same Recovery program that you will use to install the rooting mods.
If you have problem writing disk image with Win32DiskImager, you can use DiskImage_1_6_WinAll.exe instead.
---------- Post added at 04:47 PM ---------- Previous post was at 04:11 PM ----------
asawi said:
I think the rooted stock NT is loads better than than the true stock. LOADS!
...
Click to expand...
Click to collapse
We'll learn soon enough the moment the kids want some recently released game apps and find out they can't have them because they are not compatible with 2+ year-old Android Gingerbread which is what the stock ROM is based on.
gorelow said:
thanks i dread having to do the whole sd card ota block thing again and havent done it in about a year. is there a good video out there to walk me through step by step again for the ota block? and can someone recommend the best barest bones rom to root afterwards to make it as easy for a child to use as possible?
and i think i had trouble the last time because only a certain size sd card could be used. wasn't it just the 2 or 4 gb that worked? thanks and sorry for all the questions. just have to get this done tonight so i can fedex it to texas to get there in time for xmas.
Click to expand...
Click to collapse
You are getting your terminology confused as well. Asking what is the best barest bones ROM to root is incorrect.
To root means you give the nook superuser access which in turn allows you to load play store, apps, new launcher, and any SU related functions.
A ROM is a fully functioning version of android. IE: CM 7(GB), CM 9(ICS), CM 10(JB). It automatically has root access built in.
As for loading a ROM due to worrying about the kids and the interface, stock nook sucks...period. My 8 y/o has had zero issues with either cm 7 or cm10. Do yourself and them a favor and put at least CM 7 but preferably CM 10 on it.
Image files for dummies can be found at iamafanof.wordpress.com
Sent from my CM 10 SD nook tablet. Thanks devs.
gorelow said:
i purchased 2 nook tablets for an 8 and 11 year old. im debating whether to not root it because i think it wil be easier for them to follow interface and the only downside i see is having to pay for apps that may be free on amazon or play store. can i have some input here? is there a super easy rooted rom that a child can follow? or are there many free aps if i just keep it as an out of box nook. thanks so much guys, these are the 1st gen nook tablets not the hd
Click to expand...
Click to collapse
My sons are 8 and 12. Trust me, your kids won't have a bit of trouble with the CM10 interface. One of the nice extras in CM10 is that you can configure profiles to block them from getting into apps you don't want them to -- like settings, email, etc... Also, you can PIN-protect the Play Store so that they don't accidentally purchase anything.
SlowCobra96 said:
...
Image files for dummies can be found at iamafanof.wordpress.com
...
Click to expand...
Click to collapse
Since the OP will be using two NTs I'd suggest building the CM10 SD card from scratch (using the info and tools posted at http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/ and which I have provided a summary digest here), since there have been reports of NTs running the precooked CM10 SD image having identical MAC addresses and hence not able to concurrently access a same WiFi network (in this case the OP's household WiFi network).
I'm not saying rooted stock is as good as for example CM10. Not at all! CM 10 is awsome, and user interface is really nice!
But for a user that is intimidated by even the simple rooting process putting CM10 internally should not be even considered at this point. Thankfully the sd version of CM runs just as smooth as the internal install (at least it does from my 8GB Sandisk class 4) so that could certainly be an option as soon as the OP has figured out how to use the disk image writer! Yesterday even that was troublesome.
What I'm saying (if not straight out in my previous posts) is that rooted stock certainly is not bad! It depends on the kids and what they are used to if it will be "enough". For the kids near me (ages 4, 8,5 and 14) it certainly would! The bigger ones are girls that read a lot and apart from reading, watching Youtube videos and surfing (reading fashion blogs...) they are happy with a few cute games. Maybe if they had been boys and/or had tech savvy parents they would have asked for more, but they don't.
Either way, let's try to help the OP as well as we can!
asawi said:
I have now downbloaded and unszipped Brians file as well. Totally problem free!
What are you using to unzip? I use 7-zip.
By the way, I can now see that it looks like Brian's image needs a 2 GB card.
And for clairfication, you don't actually have to install Win32DiskImager. Just open it from within the folder!
---------- Post added at 08:33 PM ---------- Previous post was at 08:26 PM ----------
Check the folder. That dll should be in the folder. It is in mine (the one I created just now). Are you really opening the program from within the folder?
Click to expand...
Click to collapse
i think it was the winzip that was screwing me up. i used 7zip and it opened right up and i burned it onto the sd card. then after i powered off i held the n button and the N button and i was only brought to a screen that said so you want to factory reset. isnt that the way to boot up? it didnt seem to recognize the unziped ntboot file. thanks
Try to just boot up (from completely turned off) without holding any buttons. If you do need to keep the "n" pressed down at first, that's just for a few seconds and then let go. Some people need to keep the Tablet turned off and insert apowered USB cable (menaing it's coneected to the charger, not computer) to get it to boot from sd-card. No buttons pressed! I have never needed that myself, but I hear many others do.
I am now making post that there really shouldn't be any need for, because all that's in here is already covered elsewhere. 100% Apparently not easy enough to find for newcomers, so I'm making an attempt to help info collection.
NOTHING here is my work! All I’ve done is trying to make easy to follow instructions to other people’s hard work. Those people deserve your thanks, not me!
I’m a newbie myself and that’s why I can say that this really is very easy! If I can do it without problems, so can you! I try not to chat away too much in the instructions. Make regular searches, here or Google for more info. I found it, so surely you can too! Any questions? Well, being a noob myself I probably can't answer. Google is a very good friend of mine though...
Please do not ask questions through pm. It's better if people that know more than I do get a chance to answer them in the thread instead!
You need to know how to burn an sd image. Separate instructions to that after the other instructions if you don’t.
Step 1: Establish what it is you want to do! Choose A, B or C
A: You do not want to touch the internals of your NT but want to try CM10 anyway
B: You want to stay in the BN environment but would like to be able to install apps from elsewhere (for example Google Play Store)
C: You want to get rid of BN and install CM10 instead.
A: Run CM10 from sd card – no root required
This should work on 8GB Tablet as well as 16GB
When you boot into the card you’re running Android ICS. Remove the card and you’ll boot to internal BN operating system. (Or keep the card in, boot to Cyanoboot Menu and choose “internal boot”)
Ready-made card image download links to be found here: http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
It’s a large download (around 500 MB), but it is a ready-made sd card image. As it says in the instructions there, you’ll more than likely want to expand the user partition to take full advantage of the card, but that’s covered in his instructions.
There are other, more manual ways to make these cards as well. Also covered both in that blog and here at XDA! Go search!
B: Root the Tablet
This works on both 8GB and 16 GB Tablet.
“Rooting” is like unlocking your device, giving you access and control over it. You’re still running BN operating system though. Several excellent root guides here on XDA.
For example: http://forum.xda-developers.com/showthread.php?t=1488035
Or http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
The first one (Brian’s) require a 2 GB card the other one (Albert’s) just needs a very small card. (I think 128 MB would do, but I don’t have any that small to try)
Both give good instructions in their topics.
Both install gApps.
If you want to block OTA updates from BN, go to Play Store and find NT Hidden Settings. Even if it got installed with the root it’s probably not latest version and doesn’t have the Block OTA function.
C: Installing CM10 internally
***8GB owners must make sure to use ROM that works with their device!***
Since I’m a noob I look for easy way, and this is very easy and needs very little know-how!
***Warning! CWM is a very powerful tool. Do not "wander around" and "experiment" with stuff without doing proper research! Seriously! DON'T!***
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/showthread.php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
3. Boot into the sd-card and it should take you to CWM 5.x.x. environment.
I guess a backup of you current system would be a good thing (even though I admit to skipping that myself). To backup you'll probably need another card if you're using "The Albert Card" now, because I doubt it's enough room on that.
You navigate with the volume rocker, go back to previous menu with “power” and confirm choices with “n”
Choose “install zip from card” – “choose zip from card” – your CWM zip
See warning above!
4. Power off and prepare your sd card for ROM flashing. (If you’re working with just one card you will need to format it with SD Format or similar to get it back to full capacity.) Put your CM10 ROM zip and the appropriate gApps zip on the card.( It doesn’t matter if there’s other stuff on the card, so you don’t have to format it because of that!). I will not link to a specific ROM. Make your own choice but be sure it works for your model and also make sure you use the right gApps!
5. Reboot into Cyanoboot. This took me a couple of attempts to get right.
From powered down device, press power and right after that press and hold "n", You should boot into Cyanoboot and get the boot menu. Choose "Internal recovery" and you should get into new CWM
6. I don’t know how much clearing is needed, but I prefer to clear pretty much everything to make sure of a clean install. Cache and Dalvik I always clear.
***DO NOT format anything unless you knwo what you're doing! *** (See Satan's posts below)
7. Flash ROM and gApps same way as you flashed the CWM 6.x.x (install zip from card – choose zip from card) reboot and go!
How to burn an sd-image:
I use Win32Diskimager. Download link in Albert’s root topic (and numerous other places!!)
Unzip into a folder.
(I also copy my various img files to that folder to have them easily available)
No need to install, just run by doubleclicking the EXE in the folder.
Make sure the device letter really is your sd card.
Click on the blue folder and navigate to your img file, choose it and “write”.
It will take some time if it’s a large img, but that’s what the progress bar is there for, isn’t it?!
Nice work ,
But you should add 'do not format any partition ' warning. Android users coming from other devices might do this by default during flashing rom.
Almost every one with bricked tablets has tried formatting partitions.
Sent from my ST21a
Thanks Satan! I did not know that! Will do!
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
satan89 said:
but looks like some people missed it.
Click to expand...
Click to collapse
It looks like a lot of people miss a lot of things...
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
+1000
Do not format especially the rom partition and, most critically, the factory partition which respectively contain a set of small files with device-specific unique data (not only Serial No. but also MAC address, public/private key certificates, etc.) and the backup archive copy of the same data files (/factory/romdata.zip).
Unfortunately, I've seen some "unbricking" tools (including some that are very frequently cited/recommended on these NT forums) reformat/zero-out and flash over these 2 partitions. The end result being, even in the event the "bricked" NT gets "restored to stock", depending on the specific tool used it could be carrying device-specific data of someone else's (e.g., tool developer's) NT.
EXACTLY!
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
I think this is exactly what happened to my NT. Took me weeks of researching (I don't have a lot of free time) to figure out how to restore my 16GB NT.
Help
Im trying to single boot CM10 from sd card without touching nook os. I am using guide (CM10.0 Jellybean SDCard IMG for Nook Tablet (12/31) FINAL)
I have tried for hours using different methods also and cant even get it to boot to CM, no CM logo at all. I have a BNTV250 NT on 1.4.3. I have tried multiple sd cards, I am using a Sandisk 8gb class 6.
In a nutshell all I should have to do is
-Format the card with SD formatter,
-Extract the (Extract cm10_xxxxxx_sd_hd.img from cm10_xxxxxx_sd_hd.7z/rar)
-Use Winimage to write the image to the SD card, correct??
The Nook still refuses to boot into Cyanogen, just boots up normal every time!
same with every procedure i have tried,
Any pointers????
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
asawi said:
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
Click to expand...
Click to collapse
No, I have not, will try now.........ty
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
HOLY ****!!!! I LOVE YYOU!!:laugh::laugh::laugh::laugh::highfive::victory:
That worked, I cant believe it. Why is this not written anywhere??
LOL! :laugh: Glad you got it working!! :good:
Any clue of how to get rid of booting that way? I'm not always with a USB cable witj me.
Enviado desde mi Nexus 4 usando Tapatalk 2
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
asawi said:
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Tried doping that with no luck. After 8 or 10 attempts magically boots todo cm. Thanks.
Enviado desde mi Nexus 4 usando Tapatalk 2
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
ThePhantom97 said:
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
Click to expand...
Click to collapse
Thank you very much for putting this together, it was very helpful!
I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
E:Can’t mount / cache/recovery/command/
E:Can’t mount / cache/recovery/log/
E:Can’t open / cache/recovery/log/
E:Can’t mount / cache/recovery/last_log/
E:Can’t open / cache/recovery/last_log
After that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!
(I have removed the guide as requested by AFTVNEWS but please use the link below to see more information via there web page)
The link for the original post at AFTV if you wanna go there & leave them credit or ask questions feel free -
http://www.aftvnews.com/how-to-block-updates-on-a-rooted-fire-tv-or-fire-tv-stick-by-setting-a-custom-fire-os-version-number/
This is great news & another step to stay protected & keep root for our FireTv.
deanr1977 said:
I take no credit for this work I just noticed this new work over at AFTVNews & am passing on the info for everyone over here at XDA FireTv forums. The dev behind this is rbox & AFTVNews was posting & making the guides for everyone to use.
Here's all the information -
This is a new method of blocking software updates on a rooted Fire TV or Fire TV Stick. It involves setting a custom software version number in the device’s build.prop configuration file. Rbox came up with this idea and asked me to test if it works. The main advantage to this update blocking method is that it can be implemented from within TWRP custom recovery before the device boots. That means, if you factory reset (i.e., wipe data partition) a Fire TV, you can ensure the device does not update during the initial setup process. Prior to this method, you had to rely on external router or OpenDNS update blocking methods when going through the Fire TV initial setup process after factory reseting. Now you can block updates internally before starting the initial setup process. If you have a rooted device and are blocking updates using the “pm disable …” method (method 1 in my blocking guide), it’s a good idea to also follow this guide to have an additional update blocking method in place.
Important
This update blocking method MUST BE REDONE EVERY TIME YOU INSTALL A ROM. That is why it’s best to use both this method and the “pm disable …” method (method 1) from my blocking guide. This blocking method does survive a factory reset, which method 1 does not. So this method will cover you when factory resetting your device, and method 1 will cover you if you flash a new ROM but forget to re-apply this method, since method 1 survives installing a new ROM.
You can implement this update blocking procedure from within TWRP or within Fire OS. Obviously, if you are following this method to block updates during the initial setup process, you need to implement this update block from within TWRP. If your device is already setup and you are following this guide to just have an additional blocking method in place, then it’s actually simpler to implement this method from within Fire OS.
NOTE: I will be updating this guide with screenshots for each step within the next few days. So if it’s difficult to understand, you should wait for the screenshots to be added.
Guide using TWRP
Boot into TWRP Custom Recovery. Be sure you are following this guide AFTER you’re done installing a ROM. Installing a ROM will remove this blocking method, so it should be done last, just before you boot into Fire OS.
Select Mount from the TWRP main menu.
Check the box next to System and then return to the main menu by pressing the home shaped button in the bottom center.
You now need to transfer the file /system/build.prop from your Fire TV to your PC. You can do this using ADB or by copying it to a microSD card or USB drive connected to your device.
To transfer the file using ADB:
Connect to your device via ADB. You will need to be connected over ethernet and the IP of your device is displayed in the upper left of the main TWRP menu.
Transfer the file to your PC by running the command:
adb pull /system/build.prop [PATH-ON-YOUR-PC]
Be sure to replace [PATH-ON-YOUR-PC] with the directory on your PC where you want the file to be saved.
Mac example:
adb pull /system/build.prop /Users/AFTVnews/Downloads/
Windows example:
adb pull /system/build.prop C:\Users\AFTVnews\Desktop\
To transfer the file using a microSD card or USB drive:
Insert the microSD card or USB drive into your Fire TV.
Select Mount from the TWRP main menu.
If it is not already checked, check the box next to Micro SDCard or USB (depending on which one you’re using). Then return to the main TWRP menu by clicking the home shaped button in the bottom center.
Click Advanced from the TWRP main menu.
Click File Manager from the menu.
Click the system directory.
Click the build.prop file.
Click Copy File from the menu.
Click the external_sd if you’re using a micro SD card, or select usb if you’re using a USB drive.
Click the Select Current Directory button in the lower right.
Click the Swipe to Confirm button to copy the file to your external storage device.
Press the home shaped button to return to the main TWRP menu. Go back into the Mount menu and uncheck your external storage device. You can now remove your microSD card or USB drive and connect it to your PC.
Now that you have the build.prop file on your PC, open it with a plain text editor.
Find the line (near the top) that starts with ro.build.version.number=
Replace the numbers on that line with 987654321 and save the file.
Now you need to transfer the file back to your Fire TV.
To transfer the file back using ADB:
Run the command:
adb push [PATH-TO-build.prop-ON-YOUR-PC] /system/build.prop
Be sure to replace [PATH-TO-build.prop-ON-YOUR-PC] with the location on your PC where the build.prop file is stored.
Mac example:
adb push /Users/AFTVnews/Downloads/build.prop /system/build.prop
Windows example:
adb push C:\Users\AFTVnews\Desktop\build.prop /system/build.prop
To transfer the file using a microSD card or USB drive:
Insert the microSD card or USB drive into your Fire TV.
Select Mount from the TWRP main menu.
If it is not already checked, check the box next to Micro SDCard or USB (depending on which one you’re using). Then return to the main TWRP menu by clicking the home shaped button in the bottom center.
Click Advanced from the TWRP main menu.
Click File Manager from the menu.
Click the external_sd if you’re using a micro SD card, or select usb if you’re using a USB drive. (You may need to select “Up A Level” first.)
Click the build.prop file.
Click Copy File from the menu.
Click the system directory. (You may need to select “Up A Level” first.)
Click the Select Current Directory button in the lower right.
Click the Swipe to Confirm button to copy the file to your /system directory.
Press the home shaped button to return to the main TWRP menu.
That’s it. To confirm the custom version number is saved correctly, do one of the following:
If you’re connected via ADB, run the following command:
adb shell cat /system/build.prop | grep number
Or, within TWRP, go to Advanced, then to Terminal, and type the following command:
cat /system/build.prop | grep number
You should see ro.build.version.number=987654321 printed out. If you get the original version number printed out, then you did something wrong and need to repeat this guide from the beginning.
Guide using ES File Explorer within Fire OS
It will be a lot easier to follow this guide if you have a keyboard and mouse connect to your device. First, install the app ES File Explorer onto your Fire TV or Fire TV Stick from the Amazon Fire TV appstore.
Open ES File Explorer.
Scroll down the menu on the left and turn on the “Root Explorer” option under the “Tools” sub-menu.
Grant su permission if you’re asked.
Press back or escape to dismiss the popup menu.
Scroll up the menu on the left and select “Local”.
Select “Device” from the options that appear.
Scroll down and select the “system” folder.
Scroll down and select the “build.prop” file.
Select to open it with “ES Note Editor”
Select the pencil icon in the top right to edit the file.
Find the line that starts with ro.build.version.number and replace the number on that line with 987654321. It’s best to use the error keys on your remote or keyboard, instead of clicking with a mouse, to edit the number.
Click the back arrow icon in the upper left. Not the one in the upper right.
Click “Yes” when asked if you want to save.
Click the back arrow icon in the upper left again.
To verify your changes were saved, open the build.prop file again and ensure the number next to ro.build.version.number is still 987654321
Here is the original post on AFTV if you wanna go there & leave them credit on there post -
http://www.aftvnews.com/how-to-block-updates-on-a-rooted-fire-tv-or-fire-tv-stick-by-setting-a-custom-fire-os-version-number/
@rbox & @AFTVnews.com if you would like me to remove this let me know or if you would like to post on the below comments & I will link the thanks to the comment post number so you get the proper credit for your work.
This is great news & another step to stay protected & keep root for our FireTv.
Click to expand...
Click to collapse
Not trolling you extremely long guide but wouldnt it be a whole lot easier doing this from within Fire OS to open the build.prop from within root explorer and use the built in text editor? Just a thought, might save some people a few hours work.
---------- Post added at 01:11 PM ---------- Previous post was at 01:05 PM ----------
Or you could even use build.prop editor apk, if you wanted to keep things very simple.
Sure rbox or AFTVNews will comment here soon but if you want a quicker reply follow the link above over to aftvnews.com & leave the comment there if you like? Like I said I'm just passing on the info this is not my guide, I'm not bothered about thanks & take no credit for this guide
Sent from my SM-G900F using Tapatalk
Stupid request, but can you add "July" to the title? The date as written hasn't occurred yet in the US [emoji6]
ldeveraux said:
Stupid request, but can you add "July" to the title? The date as written hasn't occurred yet in the US [emoji6]
Click to expand...
Click to collapse
Done mate
sconnyuk said:
Not trolling you extremely long guide but wouldnt it be a whole lot easier doing this from within Fire OS to open the build.prop from within root explorer and use the built in text editor? Just a thought, might save some people a few hours work.
---------- Post added at 01:11 PM ---------- Previous post was at 01:05 PM ----------
Or you could even use build.prop editor apk, if you wanted to keep things very simple.
Click to expand...
Click to collapse
My guide has two parts: Doing it within TWRP and doing it within Fire OS. deanr1977 just copy and pasted my entire guide, which lost the formatting, which makes it difficult to actually tell the guide has multiple parts. That's why I asked him to remove the copy and pasted part of his post.
AFTVnews.com said:
My guide has two parts: Doing it within TWRP and doing it within Fire OS. deanr1977 just copy and pasted my entire guide, which lost the formatting, which makes it difficult to actually tell the guide has multiple parts. That's why I asked him to remove the copy and pasted part of his post.
Click to expand...
Click to collapse
I understand it has 2 parts, i just wondered why the need to drag over to a pc the build.prop to edit then push it back over, when the same thing could be done with build.prop editor apk or from within root explorers built in text editor, which would be a whole lot quicker ?
First thanx to AFTV for working @ this device and discovering another method to block updates.........
Second @ sconniyuk it was already mention that the guide has 2 parts 1 if you like to work on a PC and a keyboard (which I prefer) and another to work directly on the device ...your choice..... not mine
htchd2fix said:
First thanx to AFTV for working @ this device and discovering another method to block updates.........
Second @ sconniyuk it was already mention that the guide has 2 parts 1 if you like to work on a PC and a keyboard (which I prefer) and another to work directly on the device ...your choice..... not mine
Click to expand...
Click to collapse
Ah, now I get it.... You cleared it all up for me @htchd2fix ?
I know I should of realised there are people who love climbing a mountain instead of flying over it......
I myself and probably speak for 99.9 % of people (apart from you of course) would like to do a tedious thing like blocking updates the simplest, quickest and shortest way possible.
I was in no way discrediting anyone or the guide. When @AFTVnews.com replied and said it was in 2 parts here I said I already new this, I dont know why you felt the need to tell me its in 2 parts also?
sconnyuk said:
Ah, now I get it.... You cleared it all up for me @htchd2fix ?
I know I should of realised there are people who love climbing a mountain instead of flying over it......
I myself and probably speak for 99.9 % of people (apart from you of course) would like to do a tedious thing like blocking updates the simplest, quickest and shortest way possible.
I was in no way discrediting anyone or the guide. When @AFTVnews.com replied and said it was in 2 parts here I said I already new this, I dont know why you felt the need to tell me its in 2 parts also?
Click to expand...
Click to collapse
Can you let it go already? Leave the thread alone. If you don't want to use his method, go elsewhere. Don't lump other users into your crazy hangups.
ldeveraux said:
Can you let it go already? Leave the thread alone. If you don't want to use his method, go elsewhere. Don't lump other users into your crazy hangups.
Click to expand...
Click to collapse
Theres no need to bite @ideveraux I will actually use the guide but will do it an easier method. Im not lumpimg any users with crazy hang ups and im not letting anyone try to get one over on me when all I originally did was ask why not complete the editing of the build.prop with 1 of 2 very simple methods and im getting the crap for it.
No thanks
sconnyuk said:
Ah, now I get it.... You cleared it all up for me @htchd2fix ?
I know I should of realised there are people who love climbing a mountain instead of flying over it......
I myself and probably speak for 99.9 % of people (apart from you of course) would like to do a tedious thing like blocking updates the simplest, quickest and shortest way possible.
I was in no way discrediting anyone or the guide. When @AFTVnews.com replied and said it was in 2 parts here I said I already new this, I dont know why you felt the need to tell me its in 2 parts also?
Click to expand...
Click to collapse
....ok i do not have time for this....this is my last one.......
......quickist and shortest????????????????...are you sure????????? how much sure you are?
''''I garanti you that the time you download the app to edit build.prop.....I have already edited and pushed over my 4 devices ...while you still walking around your house....
htchd2fix said:
....ok i do not have time for this....this is my last one.......
......quickist and shortest????????????????...are you sure????????? how much sure you are?
''''I garanti you that the time you download the app to edit build.prop.....I have already edited and pushed over my 4 devices ...while you still walking around your house....
Click to expand...
Click to collapse
Very childish but very very amusing.
By the time anyone gets through that essay the next fire device is out dated.
Have you got anymore jokes? That one was excellent ?