From mobileread I found this amazing post:
the Nook Tablet is still bootable from SD. The rep said that while they think only 3% of sales of the NC go to people who want to root it, they are still sales they wouldnt otherwise have. And they aren't interested in removing the ability to root for those who want to do that. I was pleasantly surprised how ok they are with rooting. Plus, he said they have to keep the boot from SD option. When someone brings a messed up device into a B&N store, they can wipe the device clean and restore it to its original condition by booting the system from an SD card (by using the OS on the card to restore the system on the device).
Click to expand...
Click to collapse
OMG the monkey hitting my head XD
Edit - Not yet found the way to bypass bootloader.
Oh man, I'm really starting to like B&N management.
Smart, smart, smart.
Stuff like this is why I still bought B&N books on my rooted nook.
Perhaps wishful thinking on my part, but I thought I could take a bootable CM7 uSD from my NC and put it in the NT. No dice. It just boots up into the Nook OS. The same card works on my NC.
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
smatticus said:
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
Click to expand...
Click to collapse
Unfortunately it wouldn't even run the installer. I created a fresh bootable uSD using the image from here:
http://forum.xda-developers.com/showthread.php?t=1000957
Then dumped the latest CM7 NC nightly on it, put it in the NT, and turned it on. The NT just went straight into the Nook OS.
Just to make sure nothing was wrong with it, I put it in my NC. The installer started up, CM7 installed, and after a reboot I was in a fresh install of CM7. Next I took the uSD, put it in the NT, and restarted it. Still didn't work.
lionclaw said:
Unfortunately it wouldn't even run the installer. I created a fresh bootable uSD using the image from here:
http://forum.xda-developers.com/showthread.php?t=1000957
Then dumped the latest CM7 NC nightly on it, put it in the NT, and turned it on. The NT just went straight into the Nook OS.
Just to make sure nothing was wrong with it, I put it in my NC. The installer started up, CM7 installed, and after a reboot I was in a fresh install of CM7. Next I took the uSD, put it in the NT, and restarted it. Still didn't work.
Click to expand...
Click to collapse
This method can't simple directly used with NT, we need edit something like autonooter or supernooter to work with the new hardware.
Btw try the supernooter file please.http://forum.xda-developers.com/showthread.php?t=871940
lionclaw said:
Perhaps wishful thinking on my part, but I thought I could take a bootable CM7 uSD from my NC and put it in the NT. No dice. It just boots up into the Nook OS. The same card works on my NC.
Click to expand...
Click to collapse
smatticus said:
yeah i tested it out myself today with no luck. when i get mine i'm gonna try an install just to see what happens. maybe you need to run the installer on the device you want? i know that doesn't make sense but i'll have mine tomorrow so if it works i'll post back here. but the boot from sd was invaluable when i deleted the boot file on my nc. and i've seen people get sold on the tablet based on how easy the nc was to root and tinker with. but the stock experience is nice enough that i won't NEED to root it right away.
Click to expand...
Click to collapse
This won't work because each version of CM is tailored to work for the specific device in question, based on the hardware that device has. The NC does not have the same hardware as the NT, therefore you can't use the version of CM built for the NC on the NT. CM has drivers built-in in order to communicate with the device in question, and the drivers for communication with the NC cannot be used to communicate with dissimilar hardware on the NT.
We will just have to wait until the CM devs rebuild CM to include the drivers for the NT.
Solidsnake726 said:
Stuff like this is why I still bought B&N books on my rooted nook.
Click to expand...
Click to collapse
+1. They've bought my loyalty. The NT also just shot straight to the top of my Christmas list as a result of this.
I just got ahold of my Nook Tablet today. I can't wait until the developers get going on this. I definitely will still support B & N for allowing this to be done.
Honestly, B&N is way better off letting users hack away at it. It makes it a hot sales item, resulting in free advertising and better company image (good for shareholder confidence). Also, hopefully they learned from Sony on how NOT to provide an "open" system--giving freedom then taking it away.
It appears that it may only boot signed code..
also, I'm not able to open build.prop on the device using a file manager or when I transfer it to my local machine..
Hopefully some devs will pick it up soon and let us know where we stand
I don't have the machine yet, but why doesn't the superoneclick program work for the Nook tablet as well? Has anyone tried?
jamus28 said:
I don't have the machine yet, but why doesn't the superoneclick program work for the Nook tablet as well? Has anyone tried?
Click to expand...
Click to collapse
it don't work.
Don't panic people. Just because a bootable card does not boot up the Tablet does not mean it will not boot from a card. A whole new CWR will need to be created for the tablet.
Even without root right now, most everything is available.
Obviously we are still missing the android market, but almost all other gapps are currently working, home replacements as well.
I know this doesn't work as well as CM, but it is definitely a huge improvement over what we had yesterday morning.
diamond_lover said:
From mobileread I found this amazing post:
OMG the monkey hitting my head XD
Edit - Not yet found the way to bypass bootloader.
Click to expand...
Click to collapse
The problem with your quoted text: There's a difference between "booting from SD" and "booting ANYTHING from SD".
B&N can allow the former in order to permit unbricks at the store (signed B&N images) without allowing the latter (unsigned images).
need to look at the xft/mlo boot file on sdcard
hello. I think that the NT might boot from SD but is not seeing the right MLO file on the card. If I remember from the OMAP 3 boot sequence, the MLO has to be put on the sdcard first. The reason is that the MLO is the very low level boot code that get into the internal SRAM of the chip. TI provided a tool to convert the xft image to an MLO file and added some kind of magic number so that the chip accepted it as valid for execution. You do not want to use the NC MLO on a NT. that might kill the OMAP. The first thing to do is get the OMAP4 XFT source code and covert it to an MLO using the OMAP 4 TOOL and put it on an sdcard on the first sector to see if the NT will take it.
Just my 2 cents
Fifcic said:
hello. I think that the NT might boot from SD but is not seeing the right MLO file on the card. If I remember from the OMAP 3 boot sequence, the MLO has to be put on the sdcard first. The reason is that the MLO is the very low level boot code that get into the internal SRAM of the chip. TI provided a tool to convert the xft image to an MLO file and added some kind of magic number so that the chip accepted it as valid for execution. You do not want to use the NC MLO on a NT. that might kill the OMAP. The first thing to do is get the OMAP4 XFT source code and covert it to an MLO using the OMAP 4 TOOL and put it on an sdcard on the first sector to see if the NT will take it.
Just my 2 cents
Click to expand...
Click to collapse
If this is true, BN needs to follow Amazon and release the source code for NT.
discothan said:
If this is true, BN needs to follow Amazon and release the source code for NT.
Click to expand...
Click to collapse
I thought they did, there is a link in the NT developer forum I believe.
Related
Well here I am again,
Not sure if I should have started a new thread for this or not. And although I feel like there are more threads than needs to be in the Development forum at the time being. I felt like the SD image might have it's own issues unrelated to the EMMC version. So I wanted to keep it seperate. If a Mod feels different, please advise so. I'll be more than happy to remove the thread and have the file posted to Divine_Madcat's original thread.
**Disclaimer: As usual, use at your own risk. Backup! And I'm not responsible for anything period**
I've just prepped an Image for Divine Madcat's latest Honeycomb Hybrid RC1. I've included rookie1's dualboot u-boot.bin and my modded CWM for SD, for the purpose of easier updates in the future for the SDcard rom.
Although there is no option to mount an SDcard in this version. I was able to mount the 4th partition as SDcard. So now you can use a file explorer of choice to browse your SDcard partition. I'm not sure if the EMMC version mounted the internal Media partition or not. Not 100% sure, but with this image you should also be able to browse your /media partition on your nook as well. And remember to thank the devs for all their time and effort into getting this to us. All I did was prep it to work as an SD image.
Directions:
1-Download the update-HC-hybrid-rc1-sd.img.7z
2-Uncompress it
3-The .img file should be able to fit on a 2gb card or larger
3-Follow directions from Nookdevs.com to burn the image
4-Pop the SDcard in your nook
5-Enjoy!
Credits:
Divine_Madcat
deeper_blue
rookie1
nemith
Edit: 5/21 - Well since the world is apparently ending today sometime. Figured I'd at least let you guys try a working .img. So here is an updated .img with the apps installing issue fixed. Everything is the same as the last .img except for the fix and I included a file manager. If it hangs at the "android_" screen on first boot. Just do a hard reboot and it should be fine. Enjoy!
Edit: 5/12 - Seems like there is an issue with installing apps where it will do a soft reboot when attempting to do so. I won't have time to take a real look at it till this weekend though.
-You could push individual apps to /data/app via adb for the time being.
Code:
$ adb push app.apk /data/app
-Or to push multiple apps. Create a folder called data. Within that folder, create a folder called app. Then place all your apks in the app folder. Now you can push the whole directory to /data/app
Code:
$ adb push /your_home_directory/data /data
-If anyone else who might want to jump ahead of me and find a fix, would very much appreciate it!
Downloads:
5/21 : update-HC-hybrid-rc1-sd-v0.2.img.7z
MD5: bba35a262821fbb7e4ef42f8bb4807d6
Click to expand...
Click to collapse
If I've helped out in some way, please say thank you in one way or another!
Thanks,
Racks
Awesome! Does this include anything new from 3.1?
Looks good. I was trying to install nook app from market but it kept rebooting. Thanks for the hard work..
Looking forward to giving this a try...
Whats the size of the image, what is the min/max size sd card required?
@Samir- nothing new. Direct image of hybrid rc1 by madcat
@Flyboy- I really didn't get a chance to test. Thanks for the info. Ill take a look when I can.
@Joenathan- sorry forgot to post img size. Its a 1.8gb image. So any card 2gb or larger should be fine. Ill update OP with size later
The more feedback the better. Can't fix things without feedback.
Thanks everyone,
Racks
Sent from my NookColor using Tapatalk
Are there quite a bit of FCs with this version? I tried the emmc one and had to revert back to CM7 because it was too unstable.
Its a bit too big for my 2GB SD card, my sd card weighs in at 1,921,024KB whereas the image is 1,927,168KB
So 2GB SD cards are out....
Thanks Racks, just what I was looking for.
Well done.
crap! I has 2gb SD card too that I use for this.
Any chance of someone making an SD version of the xboxexpert's HC build?
chisleu said:
crap! I has 2gb SD card too that I use for this.
Any chance of someone making an SD version of the xboxexpert's HC build?
Click to expand...
Click to collapse
Any reason for wanting that build? I ask, because it is out of date, and nothing more than some extra apps added by default. This version uses newer framework, and right now is advisable to use until a 3.1 build comes (especially with the SD card fix also made by Racks).
The ROM is nice, Honeycomb apps are much superior, but for me it runs too slow.
Using a class 4 generic SD. Anyone else having problems?
hirano said:
The ROM is nice, Honeycomb apps are much superior, but for me it runs too slow.
Using a class 4 generic SD. Anyone else having problems?
Click to expand...
Click to collapse
Not that the SDK is as fast as CM7, but i am willing to bet the problem is your SD card. Having used a crappy SD card myself, i know how bad they can be; invest in a cheap class 2 or 4 Sandisk card, and get blown away.
Thanks, this is exactly what I was looking for as my next NC project
Divine_Madcat said:
Not that the SDK is as fast as CM7, but i am willing to bet the problem is your SD card. Having used a crappy SD card myself, i know how bad they can be; invest in a cheap class 2 or 4 Sandisk card, and get blown away.
Click to expand...
Click to collapse
Divine,
For awhile I would see you posting around with random things in various sections and wasnt really sure if you were a troll or not, but lately youve pushed some truly amazing things like the work on dals kernel and now this update hc build and I truly am impressed with all your work. You have my complete respect. Thank you.
RileyGrant said:
Divine,
For awhile I would see you posting around with random things in various sections and wasnt really sure if you were a troll or not, but lately youve pushed some truly amazing things like the work on dals kernel and now this update hc build and I truly am impressed with all your work. You have my complete respect. Thank you.
Click to expand...
Click to collapse
Ill certainly admit, i am not the most agreeable at time; commonly, i let my daily stresses flow out on to forums. I am easily annoyed at what i see as something stupid (which sadly, it feels like has been happening more in this forum).
As it is, I am happy i could have committed something useful to the community.
Apps
Great job! Love not having to flash between CM and HC to play with the 3.0 goodness. My only question, anytime I try to install an app it reboots.....Ideas?
Fodizzle1978 said:
Great job! Love not having to flash between CM and HC to play with the 3.0 goodness. My only question, anytime I try to install an app it reboots.....Ideas?
Click to expand...
Click to collapse
You're the second person to say so. Is everyone having this issue? Is anyone having success installing any apps? From market or from a file explorer. I need more feedback so I can pinpoint the problem.
I'll have to take a look at this when I get a chance. Or if you don't mind posting a logcat? Just save a logcat to a .txt file and upload it here. I'll take a look to see where it's erroring out.
*I could be wrong, but most of the time when this happens, it seems to be a caching issue. But again, i won't know till i see the errors.
Thanks,
Racks
Here ya go
racks11479 said:
You're the second person to say so. Is everyone having this issue? Is anyone having success installing any apps? From market or from a file explorer. I need more feedback so I can pinpoint the problem.
I'll have to take a look at this when I get a chance. Or if you don't mind posting a logcat? Just save a logcat to a .txt file and upload it here. I'll take a look to see where it's erroring out.
*I could be wrong, but most of the time when this happens, it seems to be a caching issue. But again, i won't know till i see the errors.
Thanks,
Racks
Click to expand...
Click to collapse
Fodizzle1978 said:
Here ya go
Click to expand...
Click to collapse
Here's a better one....not sure I captured it the first time
I'm getting the same problem, only tried installing from market.
Sent from my PC36100 using Tapatalk
I now have proof that the Nook Tablet is efuse locked and bootloaders signed. We can only boot signed bootloaders, kernels, and ramdisks from microSD.
Don't buy this if you expect any real development to happen on it. The only possible way is through kexec, and that's a lot of trouble to go through considering all the other tablet options.
For what it's worth, the u-boot in the recently posted update image from the Kindle Fire does not appear to have the signed header that the one on the NT has.
Things I learned in the process:
-USB boot is enabled, as is SD boot
-I can boot from a microSD if I format it the same as for Nook Color (modified CHS, fat on p1) and copy the MLO, u-boot, and boot.img renamed to flashing_boot.img
-There is a serial port inside that will let you at the u-boot console and a shell after the OS boots
-x-loader is signed. A known-good x-loader on microsd will not even execute, and the next item in the boot list checked (emmc)
-u-boot is signed. I know this because a known-good u-boot from Pandaboard that should be close enough to boot causes x-loader to take the code path where the secure ROM call with a pointer to the image returns nonzero
-kernel and ramdisk are signed individually in the boot.img. I can modify a byte in the boot.img on the microsd that's in the middle of the kernel or the ramdisk section and u-boot will fail the same exact call that x-loader uses to validate u-boot, but this time emitting a message complaining that the image is corrupt
-Comparing the first part of u-boot grabbed from the NC, NT, and the KF, shows that the signature that's at address 0 of the KF and NC versions is seen about 300 bytes into the NT version, with some unknown junk above. I assume that's the signature, and that the call to the secure ROM returns the image pointer (which is passed by reference, a good clue) plus the size of the header.
Wait.. Nook Touch or Nook Tablet?
DarkDvr said:
Wait.. Nook Touch or Nook Tablet?
Click to expand...
Click to collapse
Tablet. I blame BN's marketing.
what about this?
http://code.google.com/p/pandroid/downloads/detail?name=u-boot.bin&can=2&q=
That's certainly... interesting. Definitely not the direction I assumed they would go given those quotes from the B&N guys that have been thrown around.
I'll hold off any true disappointment until more people have had more time to poke at this thing. Nothing against you pokey, and thanks for your investigations so far.
diamond_lover said:
what about this?
http://code.google.com/p/pandroid/downloads/detail?name=u-boot.bin&can=2&q=
Click to expand...
Click to collapse
Close enough to the one for Pandaboard minimal Linux, which I tried.
pokey9000 said:
Close enough to the one for Pandaboard minimal Linux, which I tried.
Click to expand...
Click to collapse
I hope we can find a workaround, there will be a way to do that, because they installed android in some way.
BTW, have you tried a bootable SD card? I think it's the right path to follow.
EDIT: I see you can't boot by sd card.. what about if you try some file from Nook Color?
pokey9000: what kind of a response you can get when trying to boot your test SD in BB Playbook, I wonder?
diamond_lover said:
I hope we can find a workaround, there will be a way to do that, because they installed android in some way.
BTW, have you tried a bootable SD card? I think it's the right path to follow.
EDIT: I see you can't boot by sd card.. what about if you try some file from Nook Color?
Click to expand...
Click to collapse
Trust me, I've tried every trick used when we figured out how to boot on the NC.
might need some combination of keypress while the thing powers on...
I bet BN built-in some backdoor 'boot off SD' mode. This would allow them to grab the Nook Tablets and reformat the onboard space/memory however they see fit.
This was done in the past with the NC.
discothan said:
might need some combination of keypress while the thing powers on...
I bet BN built-in some backdoor 'boot off SD' mode. This would allow them to grab the Nook Tablets and reformat the onboard space/memory however they see fit.
This was done in the past with the NC.
Click to expand...
Click to collapse
I agree, but it sounds like the problem is not with it blindly skipping the SD card but with it not seeing a signed image on the SD card. In that case B&N might just be providing their stores with SD cards with a properly signed image that doesn't need any other tricks
If B&N really is requiring signed images to boot from the SD card, I guess there might a different method to change the bootloader - after all, most (all?) phones won't boot off of a SD card, and it is still possible to change bootloaders on many of them.
BUT, I don't think this device is going to have nearly the same dev support as a year ago to discover/crack the bootloader issue.
I'll wait a little bit longer, but the quick progress rooting the Kindle Fire makes me think that that might be my next device to replace my lost Nook Color.
Sorry B&N - you might have lost me!
jasoraso said:
If B&N really is requiring signed images to boot from the SD card, I guess there might a different method to change the bootloader - after all, most (all?) phones won't boot off of a SD card, and it is still possible to change bootloaders on many of them.
BUT, I don't think this device is going to have nearly the same dev support as a year ago to discover/crack the bootloader issue.
I'll wait a little bit longer, but the quick progress rooting the Kindle Fire makes me think that that might be my next device to replace my lost Nook Color.
Sorry B&N - you might have lost me!
Click to expand...
Click to collapse
agreeed. there's so many low-cost devices out there and devs are going to have to pick "sides": kindle fire, nook tablet, and who can forget the hp touchpad
Considering most people havent had this in their hands more than 24 hours, I think it's a bit premature to make any calls.
That being said, I'll be holding on to my $$ a wee bit longer it seems.
I really hope it can be rooted and then be able to put ICS on it. I guess I will hold onto my money a little longer also.
Even though I want the NT more, I would get a KF since it can be rooted.
DarkDvr said:
Fill your heart with patience, people =)
Click to expand...
Click to collapse
Let's all just take a deep breath and not get carried away, this stuff hasn't been out for a week yet.
Nuenjin said:
Let's all just take a deep breath and not get carried away, this stuff hasn't been out for a week yet.
Click to expand...
Click to collapse
It isn't even "officially" out at all yet
so far I am happy with it but root would be nice.
I thought it was officially out today?
Ellerbestyle said:
I thought it was officially out today?
Click to expand...
Click to collapse
Official date is 18/11
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 WANT TO START OFF BY SAYING THAT THIS IS THE FIRST TIME I HAVE MADE A THREAD ON THIS SITE.
I FEEL MY ISSUE IS UNIQUE AND ALL HELP WILL BE MUCH APPRECIATED. THANK YOU
Click to expand...
Click to collapse
The tablet that I am dealing with is a "Cruz Velocity Mini Tablet" running android 2.0 and no means of installing apk's.
Currently this is the situation:
A friend of mine lent me her Chinese reader tablet.
I told her that I could probably flash a newer version of Android on it, thinking that I could finally try my hand at making a ROM because I know for a fact that there aren't many ROMs if any at all out there for a chinese off brand reader like this.
After rooting the tablet I deleted the pre installed bloatware via ADB commands (shell) including a file manager (Astro) that I believe was the only way that you could browse files on the tablet, as well as some other pre installed applications that must have been necessary in retrospect. There is no existing vending capability or market application.
I am looking to make a custom ROM (Using android Kitchen and Cywign) through following this tutorial by lokeshsaini94 yet I feel like following that tutorial won't even get me where I need to be.
Click to expand...
Click to collapse
Things that I have tried at this point include:
Attempting to connect the tablet to my computer with the SD inserted (with and without debugging turned on) [Failed to show up on my computer as a device or anything]
Downloading the APK that I need from a file sharing website [Downloads fail]
Uploading the APK that I need to my Google drive and downloading it from the tablet [Says waiting for data connection and doesn't download even though connected to our WiFi]
Inserting the SD card into my computer, copying the APK I need over to it, then inserting the SD card back into the tablet, going into the browser and typing "File:///sdcard/<name here>.apk" to install an APK but getting an error in the installer after pushing 'install' -> 'Application not installed'
Trying to perform a factory reset; this simply makes the tablet reboot with everything the same as it was before.
Essentially guys and gals, my tablet here is running Android 2.0, I want to update it by making my own rom for it to something at least >4.0, and it seems that I've made things worse and have no way out of this mess. I think I've essentially bricked it even though it still works. :silly:
What do I need to do to make a custom ROM let alone flash/wipe this tablet?
All help will be incredibly valuable
There should be plenty of info here http://www.slatedroid.com/forum/93-velocity-micro-cruz-reader/ to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Still no paddles
es0tericcha0s said:
There should be plenty of info here < > to get you on the right track. Not likely you'd be able to get anything beyond Gingerbread on there running due to lack of source code. Your only hope would be to see if there is a newer tablet with the same chipset that has something newer on it to port over.
Click to expand...
Click to collapse
Thank you very much for your response. It looks like on that website I've already found multiple useful roms!
In fact I already downloaded one and put it onto the SD card. Apparently for these tablets you're supposed to, while powered off, turn it back on by holding the power button and the volume up button but all this seems to do as a whole load of nothing.
I fear that what I've done to it by deleting potentially sensitive programs previously, I have somehow managed to make this process impossible.
Is there some kind of way that I can plug this tablet into my computer and be able to completely wipe it so I can, at the very least, have a functional tablet that will work at all? I've done approximately 5 factory data resets yet the background image that my friend has on the tablet as well as seemingly every single setting and application is remaining untouched..
Try the ones here that also install a custom recovery: http://www.slatedroid.com/topic/33586-a-clockworkmod-rom-compendium-for-the-cruz-reader/
You'll want to make sure and rename the file exactly as mentioned there on the OP. Install instructions are included too. I don't think there is a way to reload via the PC. The right zip should get everything working properly.
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
BornReady_ said:
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
Click to expand...
Click to collapse
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
nmyshkin said:
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
Click to expand...
Click to collapse
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
BornReady_ said:
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
Click to expand...
Click to collapse
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
nmyshkin said:
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
Click to expand...
Click to collapse
Yes, I booted with the power cable connected, I tried on being connected to the laptop and power wall as well. I also held down the N button, which is why I got to the Boot Menu.
Bear with me
Are you sure you got the SD card version of TWRP?
Yes, 100% sure.
BornReady_ said:
Yes, 100% sure.
Click to expand...
Click to collapse
Well that was interesting! We're "live" apparently
I want to help but I'm not digixmax... I'll bet he has an idea. Wait for him to get back to you while I rummage around.
Lol, thanks for the help anyways though. I will have to wait for digixmax.
Wow, everytime you mention digixmax, he replies. He just privated messaged me in return.
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
I'm sorry, I should have been more precise. I don't know if it will help, but this is the TWRP recovery image I used successfully when I tried this process. That's v. 2.8.6.0
digixmax said:
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
Click to expand...
Click to collapse
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
nmyshkin said:
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
Click to expand...
Click to collapse
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
BornReady_ said:
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
Click to expand...
Click to collapse
I've already shut down my computer for the night. I'll have a look at the size that an image of the card would be. Maybe that's the easiest way if there's room in my dropbox. If you've read through the CM11/12 thread you know I ran into problems and if you were to look at the CM10 thread you'd find me floundering around there also, so I know how frustrating it can be. And then suddenly it just works.
I'll let you know tomorrow.
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
digixmax said:
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
Click to expand...
Click to collapse
You are totally correct. I enabled Windows Explorer to display file-name extension and the TWRP recovery file turned out as "recovery.img.img" I am going to try it out now and reply with if it works or not.
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
BornReady_ said:
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
Click to expand...
Click to collapse
Is flashing_boot file on your SD card correctly named "flashing_boot.img", and not "flashing_boot.img.img"?