Was wondering if it's easy to root or unlock the bootloader on the new chromecast with google tv
Sent from my A0001 using Tapatalk
We should wait for a custom recovery first. But you might loose all the DRM keys when the recovery partition is flashed. So choose wisely.
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
dictorclef said:
The 4gb storage is putting me off from buying it, if it was possible to root it to use apps2sd (or link2sd) to install entire apps on external storage, it would be a good upgrade to my fire tv stick 4k (vulkan support for emulators, slightly more powerful processor and better gpu drivers, as well as gapps installed from the start)
Click to expand...
Click to collapse
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
xnamkcor said:
Isn't installing on external media a built in option? And forcing it for all apps in in the developer options.
Click to expand...
Click to collapse
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/android-tv/chromecast/chromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
airwolf1544 said:
Yeah you are right! This works without Problems.. you only need an USB C Hub with SD support.. look here: https://forum.xda-developers.com/an...hromecast-google-tv-ethernet-usb-hub-t4176725
I use an USB C Hub with Gigabit Ethernet and 128GB SD Card. It works nice!
Click to expand...
Click to collapse
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
EsotericCleric said:
How did you get the SD card working? I put in a 64GB in mine, but wasn't working until I discovered that the CCwGTV only supports FAT32 which has a max volume size of 32GB. I even tried creating two volumes of 32, but in the end the only thing that worked was just using 32GB of the 64GB as a single FAT32 volume.
Click to expand...
Click to collapse
I've succeeded to format large USB sticks (64GB) on FAT32 with Rufus portable (free software). SD card is working only in an USB stick adapter on my hub.
Hi,
Did anyone succeed to write files on a second USB stick?
I have the first USB stick formatted to extend the storage, and a second one as an external USB storage.
The second stick can be read or write on a PC, can also be (only) read on Chromecast with Google TV, but cannot write on it on chromecast. It's a write permission restriction there.
There is an ADB solution or similar?
Thanks,
Any sign of being able to root the Chromecast with Google TV yet?
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
card13 said:
@Twotoneeddy It sounds like we have to wait for TWRP to be ported to support Android11, once that is done then you can have full Recovery functionality and Root (unless someone wants to port fastbootd like what we did in OP8T). Atm A10 just got support recently from the TWRP Team (https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html).
Click to expand...
Click to collapse
Dude, you're putting the cart before the horse. If you don't have root or equivalent*, you can't boot a twrp, assuming you even wanted to.
Technically, you need the ability to boot an unsigned boot/recovery image, which includes the ability to feed that unsigned image into the device. If you can do that, then take the original boot image, install magisk on it, feed it in, and tell it to boot it. There's your root, no twrp required.
EDIT:
card13 said:
**Edit**
Didn't realize device was A10, figured due to release time frame that it would have been released w/A11.
But the basics still stand, there is much more work to be done to get root (we can argue chicken or egg all we want but it doesn't change the end answer just the how you got to the answer).
Click to expand...
Click to collapse
This isn't a chicken and egg problem AT ALL. twrp is just a custom recovery image. Without already having root or equivalent, there is NO WAY TO RUN IT.
Let me give you a simple example of the process as it works on a pixel phone;
1) Developer options --> OEM unlocking
2) adb reboot-bootloader
3) fastboot flashing unlock
4) fastboot [boot|flash boot] boot-magisk.img
* where boot-magisk.img is the boot.img found in the factory package, after being modified by magisk.
Steps 1-3 are the barrier for this device. twrp won't help you with them because you need to COMPLETE STEP 3 before you can install or boot twrp, and by the time you've completed STEP 3, you've already achieved the goal.
There are 2 ways to get there;
1) figure out how to accomplish steps 1-3.
2) figure out a privilege escalation exploit, either through Android, or through recovery, or whatever else you can come up with.
Here is a very simple question that could help start this process off; IS THERE ANY WAY TO BOOT INTO FASTBOOT?
Delete
has anyone tried to boot off sd card? possibly running emuelec?
The real reason to root this thing has to be to bring support for HD audio passthrough.
Apparently the Amlogic S905D3G used to have HD audio passthrough on older firmware. If someone could figure out how to reenable it it would be the perfect streamer.
You can find twrp builds for the S905 but they are for older versions of android
blaze2051 said:
has anyone tried to boot off sd card?
Click to expand...
Click to collapse
wanna know if you found the answer.
What's the answer
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
npjohnson said:
Stricted and I just wrote a bootloader unlock exploit - for those of you with compatible units, enjoy: https://www.xda-developers.com/chromecast-with-google-tv-bootloader-unlock-exploit/
Click to expand...
Click to collapse
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
urbanman2004 said:
Not to necromorph an old thread, but I was curious to know by chance if it would be possible to apply your root method onto a Chromecast with Google TV that has been automatically updated to Android 12 even though it was manufacture 12/2020? After the update, some functionality I was used to that was present before the update occurred has been neutered and the OS sound effects are ruined and there's noticeable crackling/pop. Now I'm actively searching for a way to root my device so I can downgrade to either Android 11 or Android 10.
Click to expand...
Click to collapse
Nope. Locked up tight.
Related
Just wondering if anyone is working on a one-click root or custom ROM (obviously, for a donation!!!) for the NC? I am going to take the time to root this weekend, but would obviously love to just DL something and flash it.
Well, one click isn't really one click. There are lots of other clicks involved, turn on computer clicks, go to download page clicks, download clicks, then load on SD card clicks or Start - Run - cmd clicks, then the closing windows clicks.
What I believe you should have been asking, without the sugarcoating of the "one-click" phrase, is: "If it isn't too much trouble, can I use your third Genie wish after you've rubbed the lamp? I'll donate, of course, not that it would matter because I can only assume one of those first two wishes was an insane amount of money"
devis said:
Well, one click isn't really one click. There are lots of other clicks involved, turn on computer clicks, go to download page clicks, download clicks, then load on SD card clicks or Start - Run - cmd clicks, then the closing windows clicks.
What I believe you should have been asking, without the sugarcoating of the "one-click" phrase, is: "If it isn't too much trouble, can I use your third Genie wish after you've rubbed the lamp? I'll donate, of course, not that it would matter because I can only assume one of those first two wishes was an insane amount of money"
Click to expand...
Click to collapse
Precisely, what you said!!!! lol. Believe me, I try...
coldbeverage said:
Precisely, what you said!!!! lol. Believe me, I try...
Click to expand...
Click to collapse
Glad you enjoyed reading it as much as I did writing it
Now... that out of the way, and in all seriousness, can I use that third wish from someone?
devis said:
Glad you enjoyed reading it as much as I did writing it
Now... that out of the way, and in all seriousness, can I use that third wish from someone?
Click to expand...
Click to collapse
I'll have more time to mess with this after this week is over. On my todo list is trying the BN kernel's video console support so we can at least write a message to the screen when Nooter is done rooting, and copying over superuser.apk and su and maybe Astro for starting out.
With the above we could have an almost-1-click root if someone could make the card writing process easier. It would be nice if we had a Linux boot CD or boot USB image that can reformat the card (check that it's a USB device first and ask the user!) to make the boot partition the whole disk automatically. Or someone could verify the rumor that HP's USB bootdisk maker formats the drive correctly.
I'm not the guy to do a 1-click root; exploits aren't my thing, but my goal is to make Nooter easy enough that we don't need to go that route.
My apologies if this has been covered....but with my eken slate, we use an update.zip file....the device automatically does a restore with this file if its present on the sd card
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Thanks. I am just an IT lawyer who's only been at this android stuff since August so much to learn (for instance, figuring out what you wrote below.....I do try to learn and not constantly ask on here though)!!!!
johnopsec said:
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Click to expand...
Click to collapse
coldbeverage said:
Thanks. I am just an IT lawyer who's only been at this android stuff since August so much to learn (for instance, figuring out what you wrote below.....I do try to learn and not constantly ask on here though)!!!!
Click to expand...
Click to collapse
No problem. Just so nobody is confused about anything I posted above: I take absolutely no credit for anything (especially nooter) in my post. I simply wrote down the steps I took using OTHER PEOPLES ideas and code.
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
johnopsec said:
Until someone actually does a custom rom roll, it's unlikely that you're going to see one-click root. Since B&N decided to hide the Android menus that would allow us to side-load Apps, we have to boot from the SD image as part of the process.
I will look into making things a little easier though by adding a few items to the list of things that nooter does:
+ Install ADW and/or Zeam.
+ Install android.hardware.touchscreen.multitouch.xml to enable multi-touch on Android applications that support it.
+ Enable the installation of Non-Market Apps.
I personally took a shortcut when it came to rooting my personal Nook Color. Others may want to use this method as well.
(1) Write the nooter image to SD:
# dd if=nooter_sdcard_40mb.img of=/dev/<sdcard>
(2) Make sure that the Nook Color is powered off.
(3) Install the SD card with nooter written to it in the Nook Color
(4) Connect the Nook Color via USB to your computer. (Linux in my case). The Nook Color will power on all by its lonesome when it is connected to the USB.
(5) Wait a few minutes for nooter to do its thing. Seriously folks. Trying to time this down to seconds until you power the Nook Color off at this step is way overkill. Look at your watch. Add 5 minutes to whatever time it is. When 5 minutes have passed, you can safely go to step 6.
(6) Hold down the power button on your Nook Color for what seems like forever. You can count this one in seconds but, make sure that it has powered down. Without something on the screen, that is difficult to tell that it has powered down. I just timed it and an 8-10second continuous hold of the power button powered the Nook Color off. To be safe, lets say you hold it for 15 seconds.
(7) Remove the SD card from your Nook Color.
(8) Power your Nook Color Back on. (Hold the power button until you see the screen turn on. Duh!)
At this point, your Nook Color is should be rooted.
I then followed the instructions at nookdevs.com/NookColor_Rooting to use ADB to enable multi-touch and Non-Market Apps.
Click to expand...
Click to collapse
jasoraso said:
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
Click to expand...
Click to collapse
^ This.
Thats the main reason I am holding out on rooting... That and I want to see how far it goes before the market place comes out unless an easy solution like this comes out. While I like the updates here, I am also not in a huge needs for a large phone... but still Great work so far!!!
johnopsec said:
No problem. Just so nobody is confused about anything I posted above: I take absolutely no credit for anything (especially nooter) in my post. I simply wrote down the steps I took using OTHER PEOPLES ideas and code.
Click to expand...
Click to collapse
Lol. I just meant that I try to help you guys, but I have so much to learn on actually doing the stuff you do. Everyone is sharing there stuff on here openly. All good.
I am going to try to teach myself how to use ADB. Kinda nervous though.
jasoraso said:
Your simple instructions are pefect! The only thing I would add is for the Windows users to use WinImage on step 1.
Rooting really is easy; it is getting the ADB drivers to work properly (for us Windows users) that is the difficult step. If you can modify nooter to add the extra steps of writing the file to allow .apk installation; installing Astro or other file explorer; installing a launcher (Zeam seems to be a good choice); and maybe SlideME as a Market until the Google Market is figured out - I think the rooting process couldn't be much easier given the nature of the device!
Click to expand...
Click to collapse
coldbeverage said:
I am going to try to teach myself how to use ADB. Kinda nervous though.
Click to expand...
Click to collapse
No kidding, that is whaat ij aam strugglliing with. Thhaatt and tthe stupid keyybboard!
pokey9000 said:
With the above we could have an almost-1-click root if someone could make the card writing process easier. It would be nice if we had a Linux boot CD or boot USB image that can reformat the card (check that it's a USB device first and ask the user!) to make the boot partition the whole disk automatically. Or someone could verify the rumor that HP's USB bootdisk maker formats the drive correctly.
Click to expand...
Click to collapse
I was messing around with UNetBootin, which is similar to the HP USB formatter. It is designed to take linux ISOs and format them as bootable. But I don't know what specialized format Nooter uses. I didn't get far on this front.
It seems windows users are having trouble with windows drivers needed to get USB ADB working. An alternative is to enable ADB over IP. Leaving this open persistantly is a security hole, but it may be appropriate for initial setup.
PHiZ said:
I was messing around with UNetBootin, which is similar to the HP USB formatter. It is designed to take linux ISOs and format them as bootable. But I don't know what specialized format Nooter uses. I didn't get far on this front.
It seems windows users are having trouble with windows drivers needed to get USB ADB working. An alternative is to enable ADB over IP. Leaving this open persistantly is a security hole, but it may be appropriate for initial setup.
Click to expand...
Click to collapse
Getting the OMAP to boot off of SD requires a few things:
-the OMAP wired to boot from SD
-an SD card with a specific disk geometry as reported by the partition table
-a FAT16 or 32 filesystem on the first partition
-a first and second stage bootloader (MLO and u-boot.bin) in the FAT filesystem
The hardest part of getting Nooter installed correctly is creating that special partition table, and so I released it as a raw dump of an SD formatted using that scheme to only a 40MB image. The theory I've heard is that for maximum BIOS compatibility the HP USB formatter tool generates this same sort of geometry, after which you just need to drag and drop the four Nooter files onto the drive. I haven't had a chance to try this yet though.
edit: I'll be damned, it does work! Just format using hpusbfw.exe (Google it) with "quick format" checked and "create a dos startup disk" unchecked. Then copy MLO, u-boot.bin, uImage, and uRamdisk over. That's it. Plus you wind up with a FAT32 partition that takes up your whole disk, not just 40MB.
pokey9000 said:
Getting the OMAP to boot off of SD requires a few things:
-the OMAP wired to boot from SD
-an SD card with a specific disk geometry as reported by the partition table
-a FAT16 or 32 filesystem on the first partition
-a first and second stage bootloader (MLO and u-boot.bin) in the FAT filesystem
The hardest part of getting Nooter installed correctly is creating that special partition table, and so I released it as a raw dump of an SD formatted using that scheme to only a 40MB image. The theory I've heard is that for maximum BIOS compatibility the HP USB formatter tool generates this same sort of geometry, after which you just need to drag and drop the four Nooter files onto the drive. I haven't had a chance to try this yet though.
edit: I'll be damned, it does work! Just format using hpusbfw.exe (Google it) with "quick format" checked and "create a dos startup disk" unchecked. Then copy MLO, u-boot.bin, uImage, and uRamdisk over. That's it. Plus you wind up with a FAT32 partition that takes up your whole disk, not just 40MB.
Click to expand...
Click to collapse
Sounds like we may be getting close to a custom rom....????
Is the uImage the ROM? or is it all 4 pieces
Sorry if I am misunderstanding this pokey since I am a total noob. I too have been holding out on rooting hoping for an easier solution (I do not even know how to navigate to directories in terminal) I believe you are implying that the NC can be rooted using this method and is in fact much easier to accomplish. You said that you had to copy over those 4 files once you format the card. Where can one obtain those files?
Thanks man for all your dedication and hard work!
sudermatt said:
Sounds like we may be getting close to a custom rom....????
Is the uImage the ROM? or is it all 4 pieces
Click to expand...
Click to collapse
MLO - first stage bootloader. The OMAP's built in ROM looks for this on the SD and runs it. MLO then looks for u-boot.bin and runs it if it can find it on the card. It's like the Nook's boot sector.
u-boot.bin - second stage bootloader. This is responsible for figuring out how to get Linux and the ramdisk in memory. This copy loads up uImage and uRamdisk from microsd and starts running the kernel. This is similar but not the exact same as the one on the internal flash.
uImage - The Linux kernel. This copy is built specifically for Nooter.
uRamdisk - a Linux filesystem that gets loaded into RAM. Contains the Nooter script, disk utilities for performing the root, and other bits and pieces that let you log in over USB and get a shell.
This really has nothing to do with a custom ROM, it's just an easier way to install Nooter.
th3c1am said:
Sorry if I am misunderstanding this pokey since I am a total noob. I too have been holding out on rooting hoping for an easier solution (I do not even know how to navigate to directories in terminal) I believe you are implying that the NC can be rooted using this method and is in fact much easier to accomplish. You said that you had to copy over those 4 files once you format the card. Where can one obtain those files?
Thanks man for all your dedication and hard work!
Click to expand...
Click to collapse
If you have a card with Nooter on it, you could mount it on a PC and pull all 4 files off. Using the HP utility is an easier option for people who want to root under Windows and are having trouble with the disk utilities. When I get a chance I'll post the files separately.
I've just got my Nook Color today and had it rooted.
It's a nice little thing. However, I'm pretty new to Android and got lots of
questions:
1. adb doesn't work after rooting. Connecting my nook to pc only gets the usb mass storage. Is there someway to turn off the auto-mount and gets RNDIS working?
2. b&n's default home screen doesn't look good to me. is it possible to remove it and replace with a customized launcher? - something like removing all b&n stuff?
3. does nook come with usb host? or has anyone tried? I have a 3G usb modem which i think'll be cool to use with nook.
4. any quick explanation on how clockworkmod works? it doesn't seem to replace the ipl or u-boot, so how does it keep itself intact after wiping out the emmc partition?
Hope I could get some guidance here. and thanks!
DairyKnight said:
1. adb doesn't work after rooting. Connecting my nook to pc only gets the usb mass storage. Is there someway to turn off the auto-mount and gets RNDIS working?
Click to expand...
Click to collapse
nookdevs.com/NookColor_USB_ADB
try that link to help get adb working. it worked for me
DairyKnight said:
I've just got my Nook Color today and had it rooted.
It's a nice little thing. However, I'm pretty new to Android and got lots of
questions:
1. adb doesn't work after rooting. Connecting my nook to pc only gets the usb mass storage. Is there someway to turn off the auto-mount and gets RNDIS working?
2. b&n's default home screen doesn't look good to me. is it possible to remove it and replace with a customized launcher? - something like removing all b&n stuff?
3. does nook come with usb host? or has anyone tried? I have a 3G usb modem which i think'll be cool to use with nook.
4. any quick explanation on how clockworkmod works? it doesn't seem to replace the ipl or u-boot, so how does it keep itself intact after wiping out the emmc partition?
Hope I could get some guidance here. and thanks!
Click to expand...
Click to collapse
1. As pointed out by the previous post, go to NookDevs and follow the instructions there to get ADB working. You can turn off auto-mount through NookTools app.
2. Yes, you can use many 3rd party launchers. I personally use Zeam, it works great and it's free. Make sure you get HomeSwitcher app from Market first. It will help you pick which launcher to use as default.
3. Not sure. Never tried it..
4. I believe CWM replaces the stock Nook recovery (uRecRam and uRecImg) in the boot partition. So as long as you don't touch it, you can flash the eMMC all you want.
Enjoy..
Here's a quick run through on how to root the Galaxy Tab 10.1. I'm doing this for people (like me) that had a tough time getting the USB drivers to work after getting their Tab at I/O.
Assuming you have adb and the SDK set up on your Win7 machine, proceed.
1. Download the new USB drivers at http://downloadcenter.samsung.com/c...78/Samsung_USB_Driver_P4_Including_Escape.exe
2. Reboot your machine
3. Plug the 10.1 Tab into USB
4. Download the root exploit at http://lts.cr/bqf (or use allidoiswin.zip somewhere else)
5. Then, open up a command prompt ("cmd" under Run...)
6. Run the following commands:
Code:
adb push Samsung_Galaxy_Tab_10.1_root.zip /sdcard/Samsung_Galaxy_Tab_10.1_root.zip
Code:
adb reboot recovery
7. Once you're in recovery, select the zip file, then apply, then reboot.
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card. How is it being pushed to one?
keyl10 said:
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card. How is it being pushed to one?
Click to expand...
Click to collapse
Great question. Looks like Sammy and El Goog have set up the 32GB on board as the "sdcard". You can push stuff to the personal storage by sending things to /sdcard/.
keyl10 said:
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card. How is it being pushed to one?
Click to expand...
Click to collapse
What recovery are you booting into to get an option to flash the update? Not the factory one I suspect
bcmobile said:
What recovery are you booting into to get an option to flash the update? Not the factory one I suspect
Click to expand...
Click to collapse
The stock recovery DOES allow you to choose whatever .zip file you want to flash as well as actually coming stock UNLOCKED. Awesome stuff. Thanks Google.
^ wow thats a first
oxeneers said:
The stock recovery DOES allow you to choose whatever .zip file you want to flash as well as actually coming stock UNLOCKED. Awesome stuff. Thanks Google.
Click to expand...
Click to collapse
Excellent! Anyone dumped an image yet?
oxeneers said:
Great question. Looks like Sammy and El Goog have set up the 32GB on board as the "sdcard". You can push stuff to the personal storage by sending things to /sdcard/.
Click to expand...
Click to collapse
10.1v model without the SD card, it could work with this guide?
worked like a charm, thanks!
johnblade said:
10.1v model without the SD card, it could work with this guide?
Click to expand...
Click to collapse
Not yet, as the 10.1v doesn't have the option to boot into recovery...
Sent from my GT-P7100 using XDA Premium App
thanks for the write up and thanks to drod and birdman as well. My tab is now rooted! woot!
dracoaffectus said:
worked like a charm, thanks!
Click to expand...
Click to collapse
Did you try something need root access
Like screen shot or titanium backup
B.r.
Sent from my GT-P7510 using Tapatalk
hi,
I used the recovery to "execute" the zip file attached to the first post.
It seems to execute correctly, but... I'm not sure that it rooted the tab. In fact If I try the command su in the shell (adb shell) it does nothing... till a timeout expires...
any idea?
EDIT: my fault... I didn't look at the tab screen (waiting for auth) :-D
Nice! Love Root being available before I even get a device (picking up my Google I/O 10.1 tomorrow!).
Wait, so the Tab 10.1's they gave out at I\O don't have SD Card Slots, but the ones that'll be in retail in June DO have expandable SD slots? Seems like a weird thing to do to a device you're giving to DEVELOPERS, right?
so it says i got root privalage and i do see super user but i cannot get titanium backup to run. I've even installed busybox but still not luck. help?
will89 said:
so it says i got root privalage and i do see super user but i cannot get titanium backup to run. I've even installed busybox but still not luck. help?
Click to expand...
Click to collapse
Did you click on Problem? button in TB and install busy box through there? or TB is not running at all?
bella92108 said:
Wait, so the Tab 10.1's they gave out at I\O don't have SD Card Slots, but the ones that'll be in retail in June DO have expandable SD slots? Seems like a weird thing to do to a device you're giving to DEVELOPERS, right?
Click to expand...
Click to collapse
I thought so too, but, I am not going to complain
It's a free device. The mobile bands and SD slot would have been nice, but hey they gave us the 32gb version when 16gb would have been plenty IMO.
I don't see why you'd need an SD card slot to develop for it. I've been writing just fine without it
Thanks to the people that got it rooted and such already. I never even bothered checking because I (stupidly) doubted anyone there would have bothered yet, but I decided to today to get rid of the crap loaded on. I wish it was just a basic image, but, again -- not complaining.
Thanks Google, Samsung, and the XDA devs!
keyl10 said:
I was under the impression that the Galaxy Tab 10.1 devices at I/O did not have an SD card.
Click to expand...
Click to collapse
That doesn't mean Android (or any Linux based OS) can't have an 'sdcard' partition
Anyone else having the issue where your windows machine or Mac doesn't see the device?
SGT 10.1 uplink initiative
By now some of you are anticipating in getting one & have researched every known articles. But while reading all these wonderful articles, I kept asking myself, "how about dev'n these bad boys. Is it easy to root, load a new ROM & recover from a brick?"
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from an unbootable device.
Here's the basics on recovering from an unbootable device by booting into fastboot & re-installing
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
You can go into the Dev forum to learn how to root, install recovery & location of the Google N7 image.
I left out the screen, storage, & etc... because you can find it here or on the net.
EDIT:
will include the full instructions since I assume you had Android SDK installed on your system
1. Download & unrar Google's Android SDK
http://developer.android.com/sdk/index.html
2. use the SDK to download platform-tools
2. download Googles N7 image & unrar in the platform-tools folder
https://developers.google.com/android/nexus/images#nakasi
3. make sure N7 is in bootloader (hit power & hit vol down when you see the google logo)
4. plug to your Mac or linux box
5. open up terminal & CD into the folder that has the N7 image (.../.../platform-tools/N7 folder)
6. type ./flash-all.sh or sudo ./flash-all.sh
7. you are now back to stock
That concludes it, I'm just your typical geek, flash happy gadget dude.
Apps used in testing:
stock text/PDF reader, video & music player
MX Player w/ ARM7 neon plugin
Stick It player with plugin
Quick Office Pro
Root Explorer
Hardware used:
I/O Nexus 7
Belkin 2 Port USB powered hub
generic OTG
generic usb sdcard adapter
32gb microSD
Files used:
text & pdf file
MP3
MKV anime
AVI XVID
Formatting sdcard via
formatted FAT32 & NTFS using Win 7 pc
formatted EXT3 & EXT4 using G-Parted from linux (VMWare WS running Ubuntu)
1st testing:
FAT32 & NTFS: I copied the files from the PC to the sdcard.
EXT3 & EXT 4: I copied the files from linux (VMWare WS running Ubuntu) to the sdcard.
results from 1st testing:
FAT32 & NTFS: Unable to read PDF's & play the video files
EXT3 & EXT 4: Unable to read PDF's & play video files
2nd testing:
I copied the files from the PC to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards
results from 2nd testing:
FAT32: Unable to play music, video files & read PDF
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
3rd testing:
I used AirDroid to copy files from Linux to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards.
results from 3rd testing:
FAT32: Did not test
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
what about windows?
RMXO said:
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from a brick device.
Here's the basics on recovering from a brick device.
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
Click to expand...
Click to collapse
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
rcrd-pt said:
what about windows?
Click to expand...
Click to collapse
My advice for folks on Windows that don't have a Mac or linux box is to download & install Sun's VirtualBox & install Ubuntu. It's very easy to do & doesn't take up much space.
revmra said:
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
Click to expand...
Click to collapse
No need to apologize, I was wondering how long before I took me to brick & learn how to get it back to stock. I'm now more comfortable in messing around with the device since I know I can restore it back to stock within 5-10mins.
RMXO said:
reserved for my power hub & MHL testing later
Click to expand...
Click to collapse
yeah, that really begs the question of whether I can plug OTG into a powered usb hub to use peripherals and a mass storage device AND charge at the same time.
Will be interesting to see:highfive:.
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Hemidroids said:
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Click to expand...
Click to collapse
That is correct, I created a folder & moved files from the tablet using Root Explorer
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
doctahjeph said:
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
Click to expand...
Click to collapse
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
RMXO said:
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
Click to expand...
Click to collapse
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
aaronpoweruser said:
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
RMXO said:
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
Click to expand...
Click to collapse
Did the UI change when you put it to 160 or did it stay in the phone UI?
doctahjeph said:
Did the UI change when you put it to 160 or did it stay in the phone UI?
Click to expand...
Click to collapse
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
RMXO said:
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
Click to expand...
Click to collapse
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
doctahjeph said:
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
Click to expand...
Click to collapse
I'm completely redoing all my testing with hopefully less confusing test methods. Once, I get done with that, I will re-do everything in Tablet UI mode.
Thank you for going to such great depths with this testing RMXO - it's reassuring for all of us that don't yet have our hands on our ordered N7's that there is hope It's greatly appreciated.
Revised my testing methods & posted results in thread #2
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
danny8 said:
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
Click to expand...
Click to collapse
Yo're welcome & I honestly can't answer the downside of rooting because I love tinker & the only way to do that is to root. Actually, by rooting, you open yourself to bricking your device. That is the extreme case if you don't know what you are doing & can't follow directions properly. I've listed a way to recover from a bricked N7 device.
There is an app called "Voodoo OTA Rootkeeper" that allows you to unroot & go back to root when needed.
My tablet is unlocked, rooted & able to play movies from the Google Play Store.
I'm new to the Nook scene, but I've read the someone/leapinlear threads on rooting/putting google apps on the device.
Now that 2.0.5 is out, that seems to break the above.
One of my confusions is the talk of OOBE ( a new acronym for me to learn. )
Is it possible for me to open the Nook HD+ on xmas morning, and play with it without registering/updating?
Does the Nook force you to connect to wifi? What if I had no wifi?
If I can play with it without registering/updating, then use the current rooting methods later in the afternoon ... will that stop 2.0.5?
Do I need to read more?
curiousmike said:
I'm new to the Nook scene, but I've read the someone/leapinlear threads on rooting/putting google apps on the device.
Now that 2.0.5 is out, that seems to break the above.
One of my confusions is the talk of OOBE ( a new acronym for me to learn. )
Is it possible for me to open the Nook HD+ on xmas morning, and play with it without registering/updating?
Does the Nook force you to connect to wifi? What if I had no wifi?
If I can play with it without registering/updating, then use the current rooting methods later in the afternoon ... will that stop 2.0.5?
Do I need to read more?
Click to expand...
Click to collapse
You said you read my thread. Yes you can do the xmas thing by skipping OOBE ( look in my thread for how to do it). Which basically means skipping registration. And you don't have to turn on wifi so that it updates itself. But you do have to turn on wifi to register and you can do nothing with it without either registering or skipping OOBE. But it may be kind of not much fun without apps, books and wifi. I also just posted a new way to have an old version and still register. But you might want to wait to see if other users do ok with it.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
Yes you can do the xmas thing by skipping OOBE ( look in my thread for how to do it).
Click to expand...
Click to collapse
Found it and read it. Great.
leapinlar said:
But it may be kind of not much fun without apps, books and wifi
Click to expand...
Click to collapse
Agreed.
But I also don't want to do the update and risk never being able to root it and get Google App Store on it; I have a large array of apps/games for my phone that I'm hoping will work on the HD+.
You can immediately boot straight to CM10 without registering if you'd like. That's exactly what I did, and it has worked flawlessly.
OOBE, known as Out-of-Box-Experience. Basically after registering, you get the experience you should. Skipping OOBE is basically not registering the product, and entering a development/test mode. OOBE is associated with not registering the device.
The Nook HD+ requires a WiFi connection to register the product, and what if the end-user doesn't have WiFi? I guess that's tough on them, they can't register. To be honest, I can't believe it either. To use the HD+ if you do not have WiFi, is to skip OOBE (which is the same procedure as the Nook Color's).
If you skip OOBE, then there is nothing to play with on the tablet; other than familiarising yourself with the interface. That's it. Not even the browser works; actually it has no apps at all. If you later root the tablet [and install GAPPs], whilst not registering the tablet, you will eventually get a lot more features; and pretty much use it like any other Android tablet. However, a lot of features will be disabled, such as the stock Android Browser (it will not load, as it will not be installed). A lot of other apps may then cause problems, due to the default browser not being present (i.e. BBC iPlayer). With the All in One root, developed by someone0, it will disable automatic OTA updates, so you will not update any further than your current factory version. However, some users (including myself) have been forced the update, so you cannot be certain that you will remain on the factory version (those prior to 2.0.5).
However, I would recommend you reconsider your options. If you want a better experience, I would recommend that you register the device (do NOT register now, please read the rest of my post). Important, remember the credentials you register the device with. If there are any future updates for the Nook, you will need to input the same e-mail address and password (unless password changed). If you create another B&N account at this stage, your Nook will constantly output an error; I contacted B&N today, and they couldn't solve it either. I found the solution, you have to remember the exact e-mail address you used to register. So, remember the e-mail address you use to register; and absolutely the password too, or the security question. Without them, you will not be able to register your device again.
Continuing on, I stated I would recommend you to register the device. However, before you do so, please make sure you have a minimum 4GB microSD card present (I used a SanDisk 4GB class 4). When you register your device, your Nook will check for updates. It will find 2.0.5 and update to it. Just so you know, someone0 and leapinlar have worked together to bring a "Universal Root" for the Nook HD+ and that universal root even roots version 2.0.5 (thank you someone0 and leapinlar; I'm currently using it). After registering your device, you will be introduced to your Nook interface. It's empty, even the apps are pretty much useless (except for Browser, only positive); you can't even spend more than 10 minutes on it, without enjoying what your doing. So I would recommend the root + GAPPs to unlock most of the "Android" features. To use the universal root, you'll need to boot into CWM (ClockWorkMod) via SD card (minimum of 4GB, anything less won't be detected/viable). Before registering and continuing with what I say, please make sure you are able to write onto your SD card using your computer. Although we are using CWM, we are NOT going to flash any ROMs (unless you want to of course, but the following "guide" below won't detail so).
First, you'll need to insert your SD card into your computer; where you're in a position where you can write on the card. (Files links/sources/information was sourced from http://forum.xda-developers.com/showthread.php?t=2062613)
Write the CWM .img (NookHD+bootable-CWM-6023-for-emmc-stock-4GB.zip) onto the SD Card using "Win32diskimager in Windows or use the dd command in Linux or OSX".
Download NookHD+Universal-Root.zip and place it within the SD Card. Also do this for the GAPPS + EXTRAS (including ManualOTA and Unknown Sources) .zip file, which you can download here (put together by leapinlar). DO NOT extract the .zip, just place them into the SD card.
At this point, make sure you have registered your Nook HD+, updated and installed version 2.0.5. Also make sure you have launched the stock ROM at least once (i.e. turned on the device into the Nook software/modified Android OS).
Now, turn off your device (hold the power button until a message is displayed on screen, and press shut down, or similar on screen). At the bottom of the Nook, on the left of the charging port, there is a cover protecting the SD card slot. Take it out (not all the way, it's attached to the body), and place in your SD card (with the CWM and universal root, as well optionally the GAPPS; although recommend installed on the SD card).
With the SD card in, turn your Nook on. After a few seconds, you should load into CWM. Select the option "install .zip from SD card" (use volume up/down to move across the list, "n" button below screen to select, and power button to move up one menu).
Firstly, install "NookHD+Universal-Root.zip". Wait for it to fully install, then install the GAPPS + Extras.
After the last step, reboot your device and take out the SD card before reboot. You should now load into your stock OS, whilst being rooted and and GAPPs installed on version 2.0.5. Success!
After the above guide, I would personally recommend Nova Launcher Prime; it unleashes the full experience of Android for me anyway. Haha, from now it's all yours.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
HiddenG said:
OOBE, known as Out-of-Box-Experience.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
Click to expand...
Click to collapse
Fantastic; I happen to have a 4GB card and I'm writing out the .img as I type.
Merry Christmas to you.
Yea, I probably taking a day off from xda forum tomorrow, so enjoy guys.
leapinlar deserves most of the credits since he is doing all the scripting and testing. All I did was giving him ideas(good and bad).
Ahh.. CuriousMike, from BARF, right?
Small world. Let me reemphasize that if you immediately throw in the CM10 install, you can totally skip the registration step. You essentially boot around it, and the next time the device boots without the CM10 SD card plugged in, if you so choose, it will be like opening it up fresh out of the box, with the nook asking you to register and so on.
If you *just* want a full android tablet, the CM10 SD is by far the way to go. Odds are your Xmas wrapped nook doesn't yet have 2.0.5 installed. You should be able to jump straight into CM10 and avoid the current mess of trying to preserve root, avoiding updates, working around the B & N interface and so on. It doesn't mean you can't do that at a later date, but right now CM10 seems to be a much better option than trying to deal with the B&N interface. Best part is that you can continually boot right off that SD card and never have to worry about dodging updates.
I'd recommend it above the current alternative of trying to root and apply fixes to have a usable tablet.
KestrelYI said:
Ahh.. CuriousMike, from BARF, right?
Small world. Let me reemphasize that if you immediately throw in the CM10 install, you can totally skip the registration step. You essentially boot around it, and the next time the device boots without the CM10 SD card plugged in, if you so choose, it will be like opening it up fresh out of the box, with the nook asking you to register and so on.
If you *just* want a full android tablet, the CM10 SD is by far the way to go. Odds are your Xmas wrapped nook doesn't yet have 2.0.5 installed. You should be able to jump straight into CM10 and avoid the current mess of trying to preserve root, avoiding updates, working around the B & N interface and so on. It doesn't mean you can't do that at a later date, but right now CM10 seems to be a much better option than trying to deal with the B&N interface. Best part is that you can continually boot right off that SD card and never have to worry about dodging updates.
I'd recommend it above the current alternative of trying to root and apply fixes to have a usable tablet.
Click to expand...
Click to collapse
I guess we can disagree on that. The way I see it, doing Skip OOBE and then root it would be more stable than CM10. A lot of things still not working yet on CM10. So, I decided to stick w/ stock for my personal use. Considering there is universal root for 2.0.5 now also, it's possible to be on 2.0.5 and still get root+gapps. I guess it could just end up being what do you need it for.
my nook is up
posting this from the nook, using firefox! surprising that chrome comes up as not-compatible.
i've got a few of my play store apps already installed... looking good.
i bought nova-launcher for 0.25$ during googles last big sale, so i'm using that. the experience is androidy-enough.
word-hero is also incompatible... that will push me to "cm10" when it's compatibler-er.
My Nook HD+ came out of the box with 2.0.2 and hasn't updated to 2.0.5 after a couple hours of use. Tried a couple times to do a manual update and says no updates available. ??
Will this work, on my registered device? I have it all setup and working on205, but want gapps too.
Thanks,
Steve
piperman7 said:
Will this work, on my registered device? I have it all setup and working on205, but want gapps too.
Thanks,
Steve
Click to expand...
Click to collapse
It worked for me, just as described.
That sounds good, I just picked up a 8gb class 10 to use.
Thanks again,
Steve
HiddenG said:
OOBE, known as Out-of-Box-Experience. Basically after registering, you get the experience you should. Skipping OOBE is basically not registering the product, and entering a development/test mode. OOBE is associated with not registering the device.
The Nook HD+ requires a WiFi connection to register the product, and what if the end-user doesn't have WiFi? I guess that's tough on them, they can't register. To be honest, I can't believe it either. To use the HD+ if you do not have WiFi, is to skip OOBE (which is the same procedure as the Nook Color's).
If you skip OOBE, then there is nothing to play with on the tablet; other than familiarising yourself with the interface. That's it. Not even the browser works; actually it has no apps at all. If you later root the tablet [and install GAPPs], whilst not registering the tablet, you will eventually get a lot more features; and pretty much use it like any other Android tablet. However, a lot of features will be disabled, such as the stock Android Browser (it will not load, as it will not be installed). A lot of other apps may then cause problems, due to the default browser not being present (i.e. BBC iPlayer). With the All in One root, developed by someone0, it will disable automatic OTA updates, so you will not update any further than your current factory version. However, some users (including myself) have been forced the update, so you cannot be certain that you will remain on the factory version (those prior to 2.0.5).
However, I would recommend you reconsider your options. If you want a better experience, I would recommend that you register the device (do NOT register now, please read the rest of my post). Important, remember the credentials you register the device with. If there are any future updates for the Nook, you will need to input the same e-mail address and password (unless password changed). If you create another B&N account at this stage, your Nook will constantly output an error; I contacted B&N today, and they couldn't solve it either. I found the solution, you have to remember the exact e-mail address you used to register. So, remember the e-mail address you use to register; and absolutely the password too, or the security question. Without them, you will not be able to register your device again.
Continuing on, I stated I would recommend you to register the device. However, before you do so, please make sure you have a minimum 4GB microSD card present (I used a SanDisk 4GB class 4). When you register your device, your Nook will check for updates. It will find 2.0.5 and update to it. Just so you know, someone0 and leapinlar have worked together to bring a "Universal Root" for the Nook HD+ and that universal root even roots version 2.0.5 (thank you someone0 and leapinlar; I'm currently using it). After registering your device, you will be introduced to your Nook interface. It's empty, even the apps are pretty much useless (except for Browser, only positive); you can't even spend more than 10 minutes on it, without enjoying what your doing. So I would recommend the root + GAPPs to unlock most of the "Android" features. To use the universal root, you'll need to boot into CWM (ClockWorkMod) via SD card (minimum of 4GB, anything less won't be detected/viable). Before registering and continuing with what I say, please make sure you are able to write onto your SD card using your computer. Although we are using CWM, we are NOT going to flash any ROMs (unless you want to of course, but the following "guide" below won't detail so).
First, you'll need to insert your SD card into your computer; where you're in a position where you can write on the card. (Files links/sources/information was sourced from http://forum.xda-developers.com/showthread.php?t=2062613)
Write the CWM .img (NookHD+bootable-CWM-6023-for-emmc-stock-4GB.zip) onto the SD Card using "Win32diskimager in Windows or use the dd command in Linux or OSX".
Download NookHD+Universal-Root.zip and place it within the SD Card. Also do this for the GAPPS + EXTRAS (including ManualOTA and Unknown Sources) .zip file, which you can download here (put together by leapinlar). DO NOT extract the .zip, just place them into the SD card.
At this point, make sure you have registered your Nook HD+, updated and installed version 2.0.5. Also make sure you have launched the stock ROM at least once (i.e. turned on the device into the Nook software/modified Android OS).
Now, turn off your device (hold the power button until a message is displayed on screen, and press shut down, or similar on screen). At the bottom of the Nook, on the left of the charging port, there is a cover protecting the SD card slot. Take it out (not all the way, it's attached to the body), and place in your SD card (with the CWM and universal root, as well optionally the GAPPS; although recommend installed on the SD card).
With the SD card in, turn your Nook on. After a few seconds, you should load into CWM. Select the option "install .zip from SD card" (use volume up/down to move across the list, "n" button below screen to select, and power button to move up one menu).
Firstly, install "NookHD+Universal-Root.zip". Wait for it to fully install, then install the GAPPS + Extras.
After the last step, reboot your device and take out the SD card before reboot. You should now load into your stock OS, whilst being rooted and and GAPPs installed on version 2.0.5. Success!
After the above guide, I would personally recommend Nova Launcher Prime; it unleashes the full experience of Android for me anyway. Haha, from now it's all yours.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
Click to expand...
Click to collapse
Just got my Nook HD+ for Christmas, 1st Android device. I followed the above instructions to root it, after reboot it is just sitting at the first nook screen. It's been about 15 minutes or so, should I manually reboot the device or wait longer? Is it possible it just needs to be redone? The only odd thing I can across was after selecting reboot it said "ROM may flash stock recovery on reboot", should i have selected Yes/No, Should I backup the stock ROM?
Thanks for all the Help
curiousmike said:
posting this from the nook, using firefox! surprising that chrome comes up as not-compatible.
i've got a few of my play store apps already installed... looking good.
i bought nova-launcher for 0.25$ during googles last big sale, so i'm using that. the experience is androidy-enough.
word-hero is also incompatible... that will push me to "cm10" when it's compatibler-er.
Click to expand...
Click to collapse
Glad you got your tablet working with GAPPs! Hope it's all good; of course it's much better than sticking to B&N's book reader, haha. Indeed yes, I can't believe that a few apps in Google Play are not compatible either; although as suggested, sideloading them often work fine. :laugh:
mzjc said:
My Nook HD+ came out of the box with 2.0.2 and hasn't updated to 2.0.5 after a couple hours of use. Tried a couple times to do a manual update and says no updates available. ??
Click to expand...
Click to collapse
Did you skip the OOBE? The registration process of the device? If so, this problem could occur. If not, and you're registered then no problem either. If you're truly stuck on 2.0.2, that could be seen as a benefit; as your roots would never be broken, due to no future updates. If you'd like to root and place GAPPs on your tablet, I'd recommend you follow someone0's all-in-one guide. someone0's allinone will root your Nook HD+, install GAPPs, manual OTA and installation from Unknown Sources; provided your HD+ is on version 2.0.0 to 2.0.4, where you are eligible. This rooting method provides the exact same end-result as the 2.0.5 root, and is no different in performance or usability; they're exactly the same, just different installation process.
I've not tested it, but you may use the same rooting process as I've described on the last page; since the rooting method is universal. However, I have not tested it, other than on version 2.0.5. You'll also need a microSD card for this process, so I'd just recommend the adb-allinone method by someone0.
Best of luck.
ifdwolf2008 said:
Just got my Nook HD+ for Christmas, 1st Android device. I followed the above instructions to root it, after reboot it is just sitting at the first nook screen. It's been about 15 minutes or so, should I manually reboot the device or wait longer? Is it possible it just needs to be redone? The only odd thing I can across was after selecting reboot it said "ROM may flash stock recovery on reboot", should i have selected Yes/No, Should I backup the stock ROM?
Thanks for all the Help
Click to expand...
Click to collapse
First Android device? Haha, hopefully it'll make a good impression after rooting and GAPPS. Sorry about the wait. Once you've loaded/rebooted into the Nook HD+ after CWM/rooting/GAPPS etc, press the "n" button below the screen. You should be given the option to select a launcher; temporarily select ZeamLauncher and set it as default action. After that, you should be good to go. Personally, I would recommend Nova Launcher Prime instead of ZeamLauncher. If you'd like, you can download the free version of Nova Launcher from Google Play (I would recommend it strongly over ZeamLauncher). It should provide you a better "Android-experience".
If pressing the 'n' button below the screen did nothing, then you can try the rooting process again. Also selecting yes, or no shouldn't make a difference during reboot; "ROM may flash stock recovery on reboot". You may backup your stock ROM if you feel necessary, but it's not absolutely essential (if you ever run into problems, you can force the tablet to fail booting 8 times, and the tablet will automatically restore to factory defaults). If you have further problems, please reply.
Best of luck.
Boom, thanks for the help, working like a champ now! Does the mic feature in nova require chrome? Gonna side load it now. Device is much better rooted, big thanks all to all envolved!
Sent from my BNTV600 using xda app-developers app
Hey folks. I'm having some issues with the "Root your device with a bootable microSD card" method. I followed the instructions precisely.. wrote the image to a 32 GB microSD (I don't own any 4 GB cards).. and my nook REFUSES to even see the card nor boot from it for that matter.. just goes straight to the registration screen every time. Is there something that I could perhaps be missing here...? or is it that I MUST have a 4 GB card (and no bigger)?? (the microSD is the cream of the crop Sandisk 32 GB class 10 model. I couldn't resist picking one up, as they were on sale for only $26 at the time.
My HD+ is a pretty paperweight at the moment, and I'd love to get it back up and running. I really don't want to do the "all in one" method, as it keeps you in "TEST" mode.. which bugs the crap outta me.
What am I missing?!
HiddenG said:
OOBE, known as Out-of-Box-Experience. Basically after registering, you get the experience you should. Skipping OOBE is basically not registering the product, and entering a development/test mode. OOBE is associated with not registering the device.
The Nook HD+ requires a WiFi connection to register the product, and what if the end-user doesn't have WiFi? I guess that's tough on them, they can't register. To be honest, I can't believe it either. To use the HD+ if you do not have WiFi, is to skip OOBE (which is the same procedure as the Nook Color's).
If you skip OOBE, then there is nothing to play with on the tablet; other than familiarising yourself with the interface. That's it. Not even the browser works; actually it has no apps at all. If you later root the tablet [and install GAPPs], whilst not registering the tablet, you will eventually get a lot more features; and pretty much use it like any other Android tablet. However, a lot of features will be disabled, such as the stock Android Browser (it will not load, as it will not be installed). A lot of other apps may then cause problems, due to the default browser not being present (i.e. BBC iPlayer). With the All in One root, developed by someone0, it will disable automatic OTA updates, so you will not update any further than your current factory version. However, some users (including myself) have been forced the update, so you cannot be certain that you will remain on the factory version (those prior to 2.0.5).
However, I would recommend you reconsider your options. If you want a better experience, I would recommend that you register the device (do NOT register now, please read the rest of my post). Important, remember the credentials you register the device with. If there are any future updates for the Nook, you will need to input the same e-mail address and password (unless password changed). If you create another B&N account at this stage, your Nook will constantly output an error; I contacted B&N today, and they couldn't solve it either. I found the solution, you have to remember the exact e-mail address you used to register. So, remember the e-mail address you use to register; and absolutely the password too, or the security question. Without them, you will not be able to register your device again.
Continuing on, I stated I would recommend you to register the device. However, before you do so, please make sure you have a minimum 4GB microSD card present (I used a SanDisk 4GB class 4). When you register your device, your Nook will check for updates. It will find 2.0.5 and update to it. Just so you know, someone0 and leapinlar have worked together to bring a "Universal Root" for the Nook HD+ and that universal root even roots version 2.0.5 (thank you someone0 and leapinlar; I'm currently using it). After registering your device, you will be introduced to your Nook interface. It's empty, even the apps are pretty much useless (except for Browser, only positive); you can't even spend more than 10 minutes on it, without enjoying what your doing. So I would recommend the root + GAPPs to unlock most of the "Android" features. To use the universal root, you'll need to boot into CWM (ClockWorkMod) via SD card (minimum of 4GB, anything less won't be detected/viable). Before registering and continuing with what I say, please make sure you are able to write onto your SD card using your computer. Although we are using CWM, we are NOT going to flash any ROMs (unless you want to of course, but the following "guide" below won't detail so).
First, you'll need to insert your SD card into your computer; where you're in a position where you can write on the card. (Files links/sources/information was sourced from http://forum.xda-developers.com/showthread.php?t=2062613)
Write the CWM .img (NookHD+bootable-CWM-6023-for-emmc-stock-4GB.zip) onto the SD Card using "Win32diskimager in Windows or use the dd command in Linux or OSX".
Download NookHD+Universal-Root.zip and place it within the SD Card. Also do this for the GAPPS + EXTRAS (including ManualOTA and Unknown Sources) .zip file, which you can download here (put together by leapinlar). DO NOT extract the .zip, just place them into the SD card.
At this point, make sure you have registered your Nook HD+, updated and installed version 2.0.5. Also make sure you have launched the stock ROM at least once (i.e. turned on the device into the Nook software/modified Android OS).
Now, turn off your device (hold the power button until a message is displayed on screen, and press shut down, or similar on screen). At the bottom of the Nook, on the left of the charging port, there is a cover protecting the SD card slot. Take it out (not all the way, it's attached to the body), and place in your SD card (with the CWM and universal root, as well optionally the GAPPS; although recommend installed on the SD card).
With the SD card in, turn your Nook on. After a few seconds, you should load into CWM. Select the option "install .zip from SD card" (use volume up/down to move across the list, "n" button below screen to select, and power button to move up one menu).
Firstly, install "NookHD+Universal-Root.zip". Wait for it to fully install, then install the GAPPS + Extras.
After the last step, reboot your device and take out the SD card before reboot. You should now load into your stock OS, whilst being rooted and and GAPPs installed on version 2.0.5. Success!
After the above guide, I would personally recommend Nova Launcher Prime; it unleashes the full experience of Android for me anyway. Haha, from now it's all yours.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
Click to expand...
Click to collapse
Hey there. I followed your directions EXACTLY as posted. I didn't have a 4 GB microSD, but I DID have a 32 GB class 4. I used that. Long story short, the nook will NOT "see" nor boot from said microSD no matter what I do. Is there some sort of button combo I need to be doing while the nook HD+ is turning on to see the sd card? I'm totally lost on this.
Thanks in advance for your help!!
If you'd like to PM me, that way my email will notify me when a response has been received, I'd REALLY appreciate it! Thanks for all your hard work!
The one difference might be that I did the whole oobe; I registered the nook... I rebooted twice to the stock Os (somewhere I read that you had to reboot once after setting up bn account.) I don't know if that's your issue, but it's what I did and I'm running gapps.
Sent from my SPH-L710 using Tapatalk 2