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
Hello everyone! Just like others here, I've been somewhat spooked by our inability to enter Ouya's Recovery partition at the earliest stage of booting, meaning a bad flash of the Boot partition would leave the device inoperable. When I heard that Ouya's stock firmware updates were possibly bricking a few units out there, I decided to block updates on mine and see if I could transform the Boot partition such that it would become a logical extension of the bootloader. What I ended up with is something close to the "Ouya Safe Recovery" project, where a user should only need to flash Boot one additional time, along with chain-loading support as well.
Chain-loading in this case refers to the booting of ROM kernel images that reside as regular IMG files under the /sdcard and/or /system filesystems. With this capability it is possible to choose an image to run when the Ouya turns on. As an example, one may wish to set up a 2nd/test kernel+ramdisk image to use with your installed ROM, or he may wish to run Tuomas Kulve's Debian project from time-to-time without having to set up the USB cable for Fastboot mode. When dealing with distinctly different ROMs (not just alternate kernels), only one of them may install to the Ouya's built-in storage (e.g., /system); others must have been designed/created to use external storage.
An image for the Recovery partition is available along with the Boot. The former may be helpful if you wish to try out the boot menu before performing the flash of the Boot partition, or are generally okay with bouncing to Recovery before invoking a chain-load. Either of these may be tested from Fastboot mode, but do note that a successful chain-load requires that the image actually be flashed to the Ouya. (Otherwise it just reboots.) The ClockworkMod (CWM) recovery application is available on both images and is accessible from the boot menu.
Additional Information
There are a few things to consider when deciding if this approach makes sense for you:
- Users of the "Ouya Safe Recovery" project may want to stay put unless the dual-boot aspect is of interest. If so then it would be cleanest to choose my Boot image; the Recovery partition (your ROM image) could be left alone.
- The images here are not compatible with Ouya's stock firmware, due to the auto-update nature of Ouya's ROM. Either your flashed Boot image would get overwritten, or an installed non-Ouya Recovery might cause that update to hang. Therefore, you should be prepared to switch to one of the ROMs here at XDA. If you're currently on stock and don't want to switch right away, that's fine; we'll go over how to block updates for the time being.
- The Ouya CM10 ROM is nice in that it provides the IMG file separately, allowing us to handle it as we wish. However, the other ROMs end up placing their boot.img in the main ZIP. This is standard practice for other devices, but we need to be careful ensuring our Boot partition doesn't get reflashed as part of the ROM installation. Therefore, it would be necessary to investigate repackaging the ROM with an alternate updater-script prior to installation. See my StockPlus post on page 2 for more. (This shouldn't affect those who've opted for my Recovery image.)
This feature is based on CWM's initial ramdisk, and includes a new boot menu application that comes up prior to CWM itself. Basically, CWM shows up later if the menu application exits for any reason. The Ouya stock kernel (561) has also been compiled with HDMI's copy protection turned off, and includes two patch sets:
- KExec-HardBoot is the key to chain-loading on our platform. It overcomes standard KExec's lack of hardware reset (and thus failed execution) by triggering a reboot in the middle of the preparation of the new kernel. This ingenious system has been developed by Tasssadar and others over in the Nexus forums. (Be sure to enable CONFIG_TEGRA_HARDBOOT_RECOVERY if interested in compiling a Recovery kernel.)
- HDMI visual stability has been improved with a little hack of mine: a significant relaxing of a timer in the driver. (The latest Android source has corrected the instability with a significant design change, but my hack seems fine enough for this project.) Also picked up specific Android fixes in the area of Framebuffer double-buffering, as that needs to be working for CWM usability.
Installation
If you're on Ouya's stock firmware, then you should make sure that any future updates do not get applied. There is a project here ("Mod Collection For Ouya") that should help. I personally side-loaded the Baxy custom launcher to avoid Ouya's update environment. It is also likely necessary to stay out of the Ouya/Discover store if going the custom launcher route as I believe the store app can trigger an update.
At this point you can download your chosen image (Boot or Recovery) and unzip to get the IMG file. Boot your Ouya to a working Root/BusyBox environment (ROM or Recovery), and then transfer the IMG to the Ouya. (An example using ADB would be "adb push boot102513.img /sdcard/boot102513.img".)
Bring up the Ouya command prompt (e.g., "adb shell") and run these commands to get started:
su [command not present on CWM - that's okay]
cd /dev/block/platform/sdhci-tegra.3/by-name
ls
You should see the various 3-letter partition names from that last command. Your command prompt should also contain the "#" character to denote root-level access. This next step will save off your current ROM image, both because we may end up overwriting it, and because the saved file will end up as your main bootable kernel for the chain-loader. Run:
cat LNX > /sdcard/kernel.img
(If configured for "Ouya Safe Recovery," then replace the preceding "LNX" with "SOS".)
We are near the flashing stage. Check to make sure your Ouya has a reliable source of power, preferrably from an uninterruptable power supply. Recall that a bad flash of my boot image can leave the device inoperable, but I feel the risk is very low provided the following directions are heeded. Fortunately the flash process only takes a few seconds.
For the Boot image option, verify by running:
md5sum /sdcard/boot102513.img
Do not proceed unless you get "e4b1b1ad553e55ad0b2ce3fb8f5bf623".
Again for the Boot image option, flash to the Ouya by running:
dd if=/sdcard/boot102513.img of=LNX
For the Recovery image option, verify by running:
md5sum /sdcard/rcvy102513.img
Do not proceed unless you get "dda0811a7e8e82a7d4ad3fa4c3ae35e4".
Again for the Recovery image option, flash to the Ouya by running:
dd if=/sdcard/rcvy102513.img of=SOS
You may optionally verify (post-flash) by running "md5sum" on the partition name. Finish up with these commands:
sync
reboot
Usage / Configuration
The menu should come up, defaulting to "kernel.img" for the Boot image and "CWM" for Recovery. That default will then launch after ten seconds of inactivity. You may also briefly press the Ouya power button during the wait to advance through the options. The option list is 1) kernel.img, 2) kernelA1.img, 3) kernelA2.img, 4) CWM, and 5) Recovery Partition.
The defaults from above should be fine for most everyone, but it is possible to fine-tune them. An optional configuration file (/sdcard/bootmenu_b.cfg for Boot, /sdcard/bootmenu_r.cfg for Recovery) may be established to specify the default menu entry as well as the inactivity timeout. As an example, the following command would make Recovery start kernelA1.img after five seconds:
echo "2 5" > /sdcard/bootmenu_r.cfg
It is hoped that the menu would never hang. If it does, then waiting a full minute should allow CWM to start. Otherwise, it may be necessary to attach a wired/USB keyboard and type in the Alt-SysRq-X sequence, similar to Ctrl-Alt-Delete on a PC. The sequence might have to be done early on in the menu startup process, and should blink the Ouya light and place it in Fastboot mode.
The menu may unexpectedly place you in CWM, which would indicate an issue with a chain-load. The reason may be due to a missing or corrupt IMG file. Otherwise you should be able to determine why by checking /tmp/bootmenu.log against the attached source code.
---
I hope this project will be of help to others!
An additional support forum that everyone should be able to post at is available: http://forum.xda-developers.com/showthread.php?t=2450711.
Wow, really great. Thanks a lot for your effort
Gesendet von meinem One X+ mit Tapatalk
nchantmnt said:
Wow, really great. Thanks a lot for your effort
Click to expand...
Click to collapse
My pleasure, nchantmnt. Hope your new Ouya is helping you feel at home!
Yes im happy it already arrived, but after a second miscarriage and lots of stress because of a lawsuit with our neighbour i didn't have time nor nerves to play or code. Seriously this year sucks
Gesendet von meinem One X+ mit Tapatalk
nchantmnt said:
Yes im happy it already arrived, but after a second miscarriage and lots of stress because of a lawsuit with our neighbour i didn't have time nor nerves to play or code. Seriously this year sucks
Click to expand...
Click to collapse
Gosh, I'm very sorry to hear that. Do think ahead to the upcoming holiday season, and may it be a time to reflect and anticipate a fruitful 2014.
@Hal9k+1 - THANK YOU!
I was so nervous flashing CWM and StockPlus as there is no real way to fix things if something goes wrong. This should give people more confidence when flashing their Ouya.
I understand the process using ADB...my question is: can this be used from CWM somehow?
PS. I assume new kernel will always be flashable from CWM, the hack does not require 561 specifically.
Ipse_Tase said:
I understand the process using ADB...my question is: can this be used from CWM somehow?
Click to expand...
Click to collapse
Hi Ipse_Tase - I do hope the feature will be helpful to you and others.
As I think about your question, I suppose I could have have created a ZIP that would have been installed by CWM. Similarly I could have worked through some form of installation shell script. But for an important operation such as flashing, I prefer the one-at-a-time approach of the interactive shell.
Note that CWM does have an ADB service running with it. Your Ouya would show up as a different device while in CWM, so you'd need to enter Device Manager (Windows) and point the unknown device to the same ADB driver as used for the main ROM.
Alternatively you could skip ADB for this Ouya Boot Menu installation and set up an SSH server on your main ROM. I personally have installed "SSH Server" (Ice Cold Apps). I recall two screens to set up (does require the trackpad in cases), where I enabled automatic start on both, and also set the port number to 2222. After an Ouya reboot I had SSH/SCP capability and could use PuTTY/pscp from Windows.
Hal9k+1...fast reply, thank you.
Just to put my ever-so-senile brain at ease: so I run StockPlus 519r1, and WHILE in the ROM, I start ADB and follow your instructions .
OR...I enter CWM, make sure I get the right ADB drivers installed for THAT instance and go from there.
For a developer, I'm sure it's easier and more familiar to run ADB commands - for people like me (5%-over-the average-user) a CVM option to flash a zip and do all this would be more in-line with the abilities to hack.
I have rooted 4-5 devices so far and the only time I type any ADB commands is at root/unlock time - sometimes not even then (Nexus 4 and the Root Toolkit).
So if you ever consider creating a recovery flashable file, it would help many. Probably not me, as by then I would have done the ADB trick
Sounds like great work! I was hoping to implement something like this myself, but I haven't made any more time for OUYA-related development in a while (due to positive life events/busyness)
I will definitely take a look at your work when I have time!
~Troop
Ipse_Tase said:
Hal9k+1...fast reply, thank you.
Just to put my ever-so-senile brain at ease: so I run StockPlus 519r1, and WHILE in the ROM, I start ADB and follow your instructions .
OR...I enter CWM, make sure I get the right ADB drivers installed for THAT instance and go from there.
Click to expand...
Click to collapse
You got it! You don't need to worry about booting to the other partition prior to flashing. That is a given partition (LNX/SOS) is no longer being accessed once the image is booted. For CWM's ADB, you'd simply point Windows to the same INF file that you originally used. Hope this helps.
StockPlus Installation
Well, I finally retired this old stock 393 ROM I was on, and moved to StockPlus 519r2. I was not able to install it the normal way given my Boot image is in place here. So I ended up modifying "updater-script" under META-INF/com/google/android, and then repackaged prior to running the install procedure. I'm attaching my changed version in case it helps anyone, and please note that it makes StockPlus the main image (kernel.img).
(You'll need to right-click to save the attachment. Once done it will need to be renamed such that it does not include the ".txt" suffix.)
The Windows "7-Zip" utility is helpful for packaging. You may start by right-clicking the downloaded ZIP, then 7-Zip --> Extract to "OUYA_[...]". Enter the newly created directory, get to the updater-script, and replace it with mine. Now back up to the area with META-INF, system, and boot.img, still in the new directory. Select all three under Windows (Ctrl+Click), right click that area, and then 7-Zip --> Add to "OUYA_[...].zip". Be sure this new ZIP is the one that makes it to the Ouya.
Still haven't tried this out yet, but I hope to soon.
I missed out on news over the holidays though and just noticed this:
Announcing Ubuntu and Android dual boot developer preview
http://developer.ubuntu.com/2013/12/announcing-ubuntu-and-android-dual-boot-developer-preview/
I'm curious of their dual boot implementation and how it compares and if we can synergize with their approach, but haven't looked into the details of how theirs works yet (its sounds like it uses a custom recovery image, and they have the ability to trigger it to reboot into Ubuntu from an Android app and vice versa, which is cool)
It'd be awesome to be able to multi-boot an Ouya ROM, an Android ROM (CyanogenMod), and Ubuntu with that kind of ease.
EDIT: This may be more our speed though: (MultiROM)
http://forum.xda-developers.com/showthread.php?t=2011403
(did you pull anything from there? Sounds like they have a modified TWRP that can flash zips to the other ROM slots, which is something I was also hoping to implement)
~Troop
Thanks, Trooper. Good to see Ubuntu moving further along in the mobile world.
I briefly looked at MultiROM since it originated from the KExec-HardBoot work, but decided not to go in that direction. The main reason is that I decided not to pursue the setup/learning of an Android build environment, but also because it wasn't clear how I'd deal with our lack of a touchscreen and lack of volume up/down buttons. I ended up creating a small application that fits within Ouya's CWM framework and starts up before CWM itself; it monitors the power button for click events and writes to the framebuffer memory region using regular Linux calls.
I'm not too concerned about the dual-boot aspect of this new Ubuntu, but the lack of touchscreen could be a hindrance if mouse/keyboard were not a viable substitute. Whether this Ubuntu is designed to work from external storage is another question, since our /system and /data would be occupied by Android. But in general I think we could boot it from my framework, and if my Boot image were selected over the Recovery one, then the Ubuntu kernel could reside in Recovery and also be bootable from the Android side with the "reboot recovery" command.
Best of luck, and hope you'll have a chance to try it all!
accidental post please delete
Has anyone managed to encrypt this device? When I try it just sits at the Droid screen and nothing happens.
The following message is displayed in the log:
I/Timeline( 580): Timeline: Activity_windows_visible id: ActivityRecord{42559a68 u0 com.android.settings/.CryptKeeperConfirm$Blank t16} time:6294032
E/Cryptfs ( 168): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
This is with CM11 latest nightly. It seems this problem is not unique to this device.
Is there a recent Android ROM where this works?
pilux_han said:
Has anyone managed to encrypt this device? When I try it just sits at the Droid screen and nothing happens.
The following message is displayed in the log:
I/Timeline( 580): Timeline: Activity_windows_visible id: ActivityRecord{42559a68 u0 com.android.settings/.CryptKeeperConfirm$Blank t16} time:6294032
E/Cryptfs ( 168): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
This is with CM11 latest nightly. It seems this problem is not unique to this device.
Is there a recent Android ROM where this works?
Click to expand...
Click to collapse
It got fixed today so wait for 21-9-2014 nightly and then it should work.
SuperLamic said:
It got fixed today so wait for 21-9-2014 nightly and then it should work.
Click to expand...
Click to collapse
Ah, great!
Do you know whether a simple update to the nightly will be enough or will the file systems have to be recreated (since some of the articles on this topic mention that the file system needs to leave some space on the partition unused)?
Note that once you encrypt the phone you wont be able to access internal sdcard in recovery -> cant use cm updater and you have to copy and flash manually new roms from external sd
Do we actualy gain something from this encryphting thing or it is just for "paranoid " people ?
dimi89 said:
Do we actualy gain something from this encryphting thing or it is just for "paranoid " people ?
Click to expand...
Click to collapse
For me it is a work requirement. I've lost access to work mail and calendar while my phone is not encrypted.
I know the updates will be more difficult and cumbersome after the phone is encrypted. I've already switched from CWM to TWRP for this reason (even though that switch is only half working).
I apologize but I don't know much althoug i am quite interested,
what does this mean? how is the phone encripted?
Does it need a pw in adb?
From demetris' post
I already flash everything from ecternal sd
I don't need internal within recovery
I don't use cm updater (i'm on lsmooth)
Other downsides?'
Rudjgaard said:
I apologize but I don't know much althoug i am quite interested,
what does this mean? how is the phone encripted?
Does it need a pw in adb?
From demetris' post
I already flash everything from ecternal sd
I don't need internal within recovery
I don't use cm updater (i'm on lsmooth)
Other downsides?'
Click to expand...
Click to collapse
It does indeed work with yesterday's nightly. I looked at the changelog and didn't see anything that matched, but it does work. Thanks!
Supposedly there is a small performance impact, but I haven't noticed it at this point. It uses your default unlock PIN to encrypt the data on the phone. After it is encrypted you can apparently change this to a different PIN or password. You only need to enter this PIN when the phone is rebooted.
My newly encrypted phone appears to work as normal. Next challenge will be the next CM11 upgrade.
pilux_han said:
It does indeed work with yesterday's nightly. I looked at the changelog and didn't see anything that matched, but it does work. Thanks!
Supposedly there is a small performance impact, but I haven't noticed it at this point. It uses your default unlock PIN to encrypt the data on the phone. After it is encrypted you can apparently change this to a different PIN or password. You only need to enter this PIN when the phone is rebooted.
My newly encrypted phone appears to work as normal. Next challenge will be the next CM11 upgrade.
Click to expand...
Click to collapse
If you want to see REAL changes, you have to take a look at Cyanogenmod repos:
kernel
https://github.com/CyanogenMod/lge-kernel-p880/commits/cm-11.0
AND device repo
https://github.com/CyanogenMod/android_device_lge_p880/commits/cm-11.0
also there is a chance to nightly will not include fixes from same day because build started before developer commited the change, so you can look at jenkins: http://jenkins.cyanogenmod.org/view/All/builds (there you can see builds and it's build times)
BlankBlackDroid said:
So that means if i encrypt now my LG 4X HD (i have 2014-09-26 nightly installed) the internal CM updater and the update from the internal sd didn't work anymore and only from the external sd will work?
Click to expand...
Click to collapse
that means you will be able to write/read from android but not in recovery. So if you want to flash anything you have to move it to external sd which is not encrypted..
BlankBlackDroid said:
Okay use the external sd card is not the problem. But how flash then if not from recovery mode?
Thanks for you fast response!
Click to expand...
Click to collapse
I haven't said you can't use recovery (if yes i'm so sorry, my english skills are just terrible) I wanted to say you can't use internal sdcard from recovery.
It's slightly off-topic, but now that it should be possible to encrypt my device, does someone know a way to let the device reboot after some failed attempts to unlock the screen?
ddorian said:
It's slightly off-topic, but now that it should be possible to encrypt my device, does someone know a way to let the device reboot after some failed attempts to unlock the screen?
Click to expand...
Click to collapse
I believe this is governed by the installed device administrator. If you sync to workplace Exchange server, then you probably already have it. However, the device won't just reboot, it will be a remote wipe.