Related
All Credit to those who are credited on the linked page and no credit should go to me
http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/
nifty... but shouldn't this be in the dev section?
seshmaru said:
All Credit to those who are credited on the linked page and no credit should go to me
http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/
Click to expand...
Click to collapse
+1
P.S. I would like some pizza
T3rry1 said:
nifty... but shouldn't this be in the dev section?
Click to expand...
Click to collapse
its general info, since it isnt the actual guide to rooting.
Good find OP. Seems really straight forward. This will be my day 1 project.
Why was this moved to the dev section? Mods, there is already the ROOT thread, there was no need to move this. =\
I appreciate there are some differences, but why is the process more complex than the Acer A500. Al you do with there is:
1. Set as debug
2. Make sure an microsd is installed
3. Install the root apk
4. Run the apk
5. Reboots in five minutes and rooted
I'm assuming its the differences in the kernals, before the OTA updates, the transformer sounded pretty easy, but now they've locked things down since then
The new root allows boot custom boot and recovery partitions to be flashed to the device. Aloowing for nandroid backups and restores
Apache14 said:
The new root allows boot custom boot and recovery partitions to be flashed to the device. Aloowing for nandroid backups and restores
Click to expand...
Click to collapse
Only get root with certain apps. Titanium doesn't work, nor does setcpu. Root explorer seems to.
Apache14 said:
The new root allows boot custom boot and recovery partitions to be flashed to the device. Aloowing for nandroid backups and restores
Click to expand...
Click to collapse
Can we flash ROMs from internal memory as well?
I don't think so, as part of installing CWM you have to have an microsd card inserted. So I'm pretty sure at this point they don't have a version to use just the internal memory.
Also I did a nandroid and it looks like CWM currently backs up EVERYTHING on the internal SD card. Looking in storage i have about 380 Mb of system, 1.7 for media but my nandroid was ~2 GB.
If this is true, may be a problem down the road, where your nandroid may take almost your whole microsd just to store.
lordgodgeneral said:
I don't think so, as part of installing CWM you have to have an microsd card inserted. So I'm pretty sure at this point they don't have a version to use just the internal memory.
Also I did a nandroid and it looks like CWM currently backs up EVERYTHING on the internal SD card. Looking in storage i have about 380 Mb of system, 1.7 for media but my nandroid was ~2 GB.
If this is true, may be a problem down the road, where your nandroid may take almost your whole microsd just to store.
Click to expand...
Click to collapse
Just transfer off old nandroids and put back on as needed. Just means you have to make sure you have at least enough space to hold the nandroid you want to put on/restore to though.
32GB MicroSD FTW!
Roach2010 said:
32GB MicroSD FTW!
Click to expand...
Click to collapse
Yeah... I only have an 8GB with 12 GB of stuff on the E3T so nandroid is a no-go for me at the moment ):
Tell me about it, I've got a 16GB in the desire that's never more than half full but I only had a 4GB lying around when I got the transformer so I'm tight on space till I get something bigger.
I am going to get a 32GB card for this and keep my media on it rather than the transformer. That way the transformer shouldn't get too big for nandroids.
I'm sure it's only a matter of time before honeycomb is ripped apart and we will be able to mount the /sdcard partition to a part of the nand that isn't backup up by nandroid. It lives in /data/media at the moment but a custom MTD could take care of that if such a thing existed yet...
Wouldn't this prevent me from being able to receive future OTA's though? Or do we have a way to flash an SBF of some sort (I'm pretty sure we don't).
Of course no updates from Asus but devs will give us the updates instead after taking the bad crap out.
i did every steps< 5. Wait up to 10 minutes for gingerbreak to do its stuff, once its done you will have SU (#) symbol< got the symbol try the other steps didnt work reboot ...now im trying to do it again and i get permission denied????
re run the chmod 777 xxx/xxx/xxx command and then try gingerbreak again
Hi,
I just bought a nook color. I'm trying to install nightly cm9 on it. i have been reading and i have some questions .. please help i don't wanna turn my new nook into paperweight lol. I understand i need to make a bootable sd card with CWR on it. i understand there are newer version CWR out there now but I am only able to find 4gb version of 3.0.2.8. Will that cause a problem ? Do i have to use 4gb version CWR? I can find 1gb CWM 3.2.0.1 ( i have a 4g micro sd card ). About wiping, i know with android phones you always wipe before you flash roms but i have been reading, posts suggest to wipe cach and dalvik AFTER flashing cm and gapps. Is that the correct order to wipe? [GUIDE] Install CM7 or CM9(!) + Clockworkmod to EMMC - ALL NOOKS! (Updated:1/16/12) - xda-developers This post don't even mention wiping dalvik. So what exactly should i wipe and in what order? Also in that post it says after you flash, without rebooting you are to remove sd card and format it on a computer... since its a bootable CRW, the nook color doesnt even have the recovery on it , will removing the sd just cause it to crush ? Please help ~ Thank you.
Best advice is to go to the "development forum" and read the CM9/ICS nightly thread.Everything you need is in the first post.I would suggest you test your SD card with CrystalDiskMark 3.0(free program,google it up)first to see if it is suitable for a ROM install.
See the SD card strange thread in this forum first.
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Thanks and what is the "telephony permission fix" ?
bobtidey said:
Don't worry too much about bricking your Nook Color. It is pretty much impossible to get it in a state which you can't recover from as it has priority on booting from the SD card.
That's not say you shouldn't try to get it right to avoid any hassle.
For an internal install use the Eyeballer SD clockwork recovery method as detailed in the development forum. When you image this to an SD then you always end up with a 1GB partition on the card irrespective of the real SD size. Don't worry about that as this is just a staging post and you just need space to put on the zips you want to install.
For CM9 use the "unofficial" nightly builds and put the main ROM, Gapps, and the telephony permissions fix on.
When you boot from this card you will be in Clockwork recovery. First time you want to format system, data, and cache then install ROM, Gapps and telephony fix in that order.
After that you want to put in a cleanly formatted single partition SD card, either by reformatting partitioning the installation one or a different one if you wanted to keep the original. It won't crash but some apps expect the Sd card to be present.
Once rebooted then you should be in CM9. You can install clockwork recovery to the internal memory as well by using the ROM Manager app. This means that if you reboot with the N key held down you get into a boot menu and can choose to go into recovery. That is very convenient for subsequent updates as you can just copy zips onto the SD card via USB or Wifi without having to remove the card (ES File Explorr app helps a lot here).
For small updates you can normally just format system and cache then reapply the set of zips. This will leave your set up and installed apps alone. You don't need to do Dalvik separately as it is in the cache partition.
Click to expand...
Click to collapse
Found the telephony fix thanks
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
I already have cm7 on my phone , hopefully its not gonna be the same thing lol . i was hoping to put cm9 on there so it will entertain me for a while but if its really that buggy mb i will consider just running on cm7.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
Thanks. I already have bobzhome 7.2 on my phone. The reason why i wanna cm* on my nook is because i don't read(i read enough for school XD ) haha so the nook factory rom will be kinda pointless for me. Also just booting from sd and flashing roms seem really straight forward to me so that's why i want to flash cm* on internal memory. As im not that knowledgeble about nook colors, running on a bootable rom still seem complicated for me but i sure will think about it .
brentb636 said:
You might consider simply using the SD card boot ROM's, and leaving the internal Nook alone for the present. That would allow you to try out the various Rom's available and find one that works best for you. I'm currently running CM7.2 Kang on my emmc partition, but booting on SD card from the CM9 nightly builds. The CM7.2 Kang is quite stable, but not as much fun as the alpha ICS CM9 stuff. Best of both worlds.
Click to expand...
Click to collapse
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
optimusv45 said:
when i was downloading cm7 roms , my anti virus kept saying there were viruses in the roms ... is that normal ?
Click to expand...
Click to collapse
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
just making sure since im not very knowledge about nook colors. i rather ask more than do something stupid on my device and cause myself problems.
Benzoman said:
How many places you going to ask this?
It is a false positive.
Normal? No. Crappy antivirus? Yes.
As long as you are downloading from links from the developers here you're safe.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
No problem. Just noticed it was in a separate thread already.
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Dual booting SD
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
I posted what a/v already. its kaspersky internet security. i guess i never look into running off SD. I don't read much so i just don't need nook color stock ROM, i guess that's also part of why i wanna run on internal memory. oh and i bought a refurbished nook color from BNs website and it came defective. part of the screen didn't work. To those who wanna buy it from them i suggest to buy from a retail store so u don't have to pay shipping and waste time I think all they did was a factory restore on a return and sell it again for 149.
TL2000 said:
Please post what A/V you are talking about so others having the same issue will take note.
I'll also give a +1 to the people who suggested that you work off an SD card until you are really comfortable with the process. You can always recover your Nook, but why go through that hassle when the SD card is so easy.
Just my $.02
Click to expand...
Click to collapse
Im gonna buy a new nook color and i read that newer ones have different hardware. newer hardware aren't supported by CM7. I guess I'll have to try a nightly CM9 build.
The1Power said:
I agree with try the Dual boot off the SD card to see what you like. Check out http://forum.xda-developers.com/showthread.php?t=1000957Verygreens process was simple to follow and I am newer at rooting also. Cheers.
Click to expand...
Click to collapse
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
mr72 said:
A bit of unsolicited advice: if you are having these kinds of problems, then I suggest CM9 is not baked enough for you, and you may be much better off with a far more stable and better-documented CM7.x install. I am not being condescending... I myself am quite capable of extreme hacking and tolerant of an array of stability issues, being a Linux software engineer, but I just don't have the time or energy to put into making CM9 work right now, given the quantity of issues. For the hardcore Android hobbyist, CM9 is the way to go right now. For a NC user wanting a functional Android tablet, I say wait a little bit.
Click to expand...
Click to collapse
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I just bought my nook color Dec. 30th, 2011 and I have ran cm7 as well as cm9. Like the others are saying, set up cm7 off of a SD card until you learn what you are doing then consider moving to the emmc.
optimusv45 said:
will CM7 work on a new nook color? i have read that it doesn't have some needed drivers.
Click to expand...
Click to collapse
I believe that is CM9, not 7 that was having issues with the new nook color touch screen drivers.
Here's a post about it:http://forum.xda-developers.com/showthread.php?p=21333209&highlight=touchscreen#post21333209
Looks like it may already be fixed: http://forum.xda-developers.com/showthread.php?p=21353661&highlight=touchscreen#post21353661
Is it possible to run stock nook color Rom off an sdcard while running cm7.2 kang with mirage kernel on emmc?
I know its possible to install and run other Rom off an sdcard, I was just curious. Thanks in advanced if its possible or not.
Sent from my Nook Color on CM 7.2 KANG build
brsingr said:
Is it possible to run stock nook color Rom off an sdcard while running cm7.2 kang with mirage kernel on emmc?
I know its possible to install and run other Rom off an sdcard, I was just curious. Thanks in advanced if its possible or not.
Sent from my Nook Color on CM 7.2 KANG build
Click to expand...
Click to collapse
No. I know dizzyden was working on a way to make that happen, but as far as I know, stock only works on emmc.
But you could put stock back on emmc and your Kang on SD.
Ah ok, thanks for the help
Sent from my R800x using xda app-developers app
leapinlar said:
No. I know dizzyden was working on a way to make that happen, but as far as I know, stock only works on emmc.
But you could put stock back on emmc and your Kang on SD.
Click to expand...
Click to collapse
Would it be possible to just do a cwm backup of my current Rom then restore it onto the sdcard install?
Sent from my Nook Color on CM 7.2 KANG build
brsingr said:
Would it be possible to just do a cwm backup of my current Rom then restore it onto the sdcard install?
Sent from my Nook Color on CM 7.2 KANG build
Click to expand...
Click to collapse
No. Apparently there is some code in the ROM that expects it to be on emmc. It fails if on SD.
Sent from my Nook Color running CM10 and Tapatalk.
Ok. Thanks leap
Sent from my Nook Color on CM 7.2 KANG build
Well in answer to the original poster in this thread, I now have a way to get Stock on a verygreen SD. Look at my tips thread linked in my signature and look at item B11 in the second post of that thread. You can even have rooted stock with OC and apps2SD support.
I am still working on a method of having stock on SD while still using data on /dev/block/mmcblk0p2... I have not given up... just gotten side tracked a time or two.
DizzyDen said:
I am still working on a method of having stock on SD while still using data on /dev/block/mmcblk0p2... I have not given up... just gotten side tracked a time or two.
Click to expand...
Click to collapse
Mine does that. Just had to modify the ramdisk.
Thanks for all the help and Info leap and dizzy ....ill go try it out and let you know
edit: Its been awhile since i made a sd rom....so far i have made the sdcard from This and i dont exactly understand how to do the rest of it properly, my nook color is on the cm7.2 kang build with mirage kernel and in Leap's instructions it says
leapinlar said:
So the procedure to get this working is to prepare a verygreen SD using the image file attached to my SD installation instructions thread here (generic-sdcard...). Then boot it at least once with the SD installed in the Nook so the SD can partition itself. If you have an existing verygreen SD prepared, you can skip those two steps. Copy the zip files to somewhere that recovery can find them. If you use the newest versions of CWM or TWRP recovery they can read files from emmc media storage. Boot to recovery and insert the prepared verygreen SD into the Nook. Flash the ROM zip to the SD. It will format the system and data partitions on the SD and install the ROM. Boot to the SD and the new stock ROM should load. Follow the directions to register with B&N. Once you have registered you can stop there if you are satisfied with plain stock. But be warned, if B&N decides to update to a new version in the future, it may mess up whatever you have installed on emmc. Therefore I recommend that you flash the Block Updates zip which blocks OTA updates. If you flash Manual Nooter you do not have to flash Block Updates separately since it is included in Manual Nooter. To install Block Updates, Manual Nooter or OC/apps2SD support, flash the zips to the SD with recovery just like you did the ROM. If you flash Manual Nooter, it has gapps and Market with it so you must register them with Google. And you need root if you want to the OC and apps2SD support, plus you will need a program like SetCPU to adjust the processor.
You can get the modified 1.4.3 B&N stock ROM zip here, the modified Manual Nooter zip here, the modified OC/apps2SD zip here, and the modified Block Updates zip here (all four modified for verygreen SD installation).
Click to expand...
Click to collapse
I have done the partitioning on the sdcard so it now has the 4 partitions in it....the nook is running CWM 3.2.0.1 emmc recovery. I've downloaded all 4 zip files, but i only plan on putting the stock nook, and manual nooter (leap says it includes the update blocker) on it
Sent from my R800x using xda app-developers app
You need to update your emmc recovery to a newer version so that you can flash those zips from internal memory (emmc media). You will run into problems finding the files with 3.2.0.1 since you have to take your normal SD out and put your verygreen SD in.
So flash this zip:
http://forum.xda-developers.com/showthread.php?p=23537853
Then copy the downloaded files to emmc media, boot to the new CWM and select the files from internal memory and flash them to your inserted verygreen SD.
EDIT: I just updated my instructions in my tips to make that clearer. Thanks.
leapinlar said:
You need to update your emmc recovery to a newer version so that you can flash those zips from internal memory (emmc media). You will run into problems finding the files with 3.2.0.1 since you have to take your normal SD out and put your verygreen SD in.
So flash this zip:
http://forum.xda-developers.com/showthread.php?p=23537853
Then copy the downloaded files to emmc media, boot to the new CWM and select the files from internal memory and flash them to your inserted verygreen SD.
EDIT: I just updated my instructions in my tips to make that clearer. Thanks.
Click to expand...
Click to collapse
Ok, ive put the bandn 1.4.3 rom zip onto the emmc of the nook color and the manuak nooter in the same place. Im running the cwm you linked and i can now select them, my questionnow is: when it says install zip from sdcard i scroll down and select the choose zip from internal and it finds both zips....after i booted to cwm i inserted the verygreen sdcard, how will i know the stock nook will flash to the sdcard and not the internal?
brsingr said:
Ok, ive put the bandn 1.4.3 rom zip onto the emmc of the nook color and the manuak nooter in the same place. Im running the cwm you linked and i can now select them, my questionnow is: when it says install zip from sdcard i scroll down and select the choose zip from internal and it finds both zips....after i booted to cwm i inserted the verygreen sdcard, how will i know the stock nook will flash to the sdcard and not the internal?
Click to expand...
Click to collapse
I have built in safeguards to make sure that won't happen. If no SD is in the slot, it won't flash, if the SD in the slot is not formated with 4 partitions, it won't flash. And when it finally does flash, it is hard coded to go to SD. Flash away. First ROM then a little later after you have registered and let it finish loading books, the manual nooter.
Sent from my Nook Color running CM10 and Tapatalk.
leapinlar said:
I have built in safeguards to make sure that won't happen. If no SD is in the slot, it won't flash, if the SD in the slot is not formated with 4 partitions, it won't flash. And when it finally does flash, it is hard coded to go to SD. Flash away. First ROM then a little later after you have registered and let it finish loading books, the manual nooter.
Sent from my Nook Color running CM10 and Tapatalk.
Click to expand...
Click to collapse
Works perfectly
now to go install the manual nooter
Much Thanks to Leap and Dizzy.
brsingr said:
Works perfectly
now to go install the manual nooter
Click to expand...
Click to collapse
Congratulations! You are my first user to report it working besides my own testing.
leapinlar said:
Congratulations! You are my first user to report it working besides my own testing.
Click to expand...
Click to collapse
cool ....i dont know if its normal or not but it does seem to take forever to download the books, when i wsa using the android app it didnt seem to take as long....maybe they are just have server bugs or something?
i think after the books are done downloading then ill root it.
brsingr said:
cool ....i dont know if its normal or not but it does seem to take forever to download the books, when i wsa using the android app it didnt seem to take as long....maybe they are just have server bugs or something?
i think after the books are done downloading then ill root it.
Click to expand...
Click to collapse
It took me a very long time to download the books and I have a fast connection. I think B&N just pushes them out slow for stock. Other stuff downloads fast, like once you are rooted and you download apps from play store.
leapinlar said:
It took me a very long time to download the books and I have a fast connection. I think B&N just pushes them out slow for stock. Other stuff downloads fast, like once you are rooted and you download apps from play store.
Click to expand...
Click to collapse
hmm ok, so its not just me then...thats good lol
brsingr said:
hmm ok, so its not just me then...thats good lol
Click to expand...
Click to collapse
hmm...now im having problems redownloading some books that started to download, but i turned the nook off when i went out to dinner and now i cant tell if the books that were downloading are actually continuing to download or not...would it be possible to download the books on the cm7.2 android app and then copy them over to the nook sd?
Brah....dang it...I messed up by accidently hitting the erase and deregister button.....it didn't seem to erase anything, but it did deregister it...would I have to remake the SD and then reflash the rom again? (Not that it is a big deal or time consuming to do lol)
Sent from my Nook Color on CM 7.2 KANG build
Bought a brand new Nook HD+ with the intention of using it as an inexpensive tablet in my kitchen, primarily to access the web and run cooking apps. Out of the box, I found it laggy and unresponsive to the point of being unusable.
I have some experience rooting/jailbreaking my phones, very little experience with tablets. I was eager to get KitKat on the device right away—it has proven to be so much better on my phone, much better battery life, much more responsive, less buggy, more fluid, etc. Problem is, KitKat is bleeding edge, and there are no official builds, and most of the install guides for dummies (=me) refer to earlier (JB) versions of Android.
It turned out to be quite time consuming to read all of the different versions of the install process, and to patch together a process that worked. I thought I would document what I did, in order to (possibly) save others some of the time that I invested.
Note: this process does NOT install KitKat to the SD card. In plain English, these steps install a bootable recovery image onto a micro sd card. Booting into the micro-sd recovery will allow you to wipe stock from your device and install kit-kat, google apps and an internal recovery. When you are finished, you remove the micro-SD and you have an Android tablet that boots into kitkat. If you want something different stop reading!
1) get a class 4 micro SD (class 4 seems to be the one that boots most reliably in the Nook HD+ (see this thread: http://forum.xda-developers.com/showthread.php?t=2288688&page=12 )
2) Download win32diskimager (http://sourceforge.net/projects/win32diskimager/?source=directory ) and this bootable CWM recovery image (http://nook.rootshell.ru/hd/emmc-cwm-early3.img.gz ).
3) Extract the CWM recovery image, and use win32diskimager to write the image to the micro sd.
4) Download EMMC (internal) recovery image and latest CM11 EMMC from this thread (http://forum.xda-developers.com/showthread.php?t=2600572) . You want “Ovation Recovery Image (CWM)” and “cm-11-xxxxxxx-UNOFFICIAL-ovation-emmc.zip.” All recoveries and roms for this device are called Ovation. Download Paranoid Android Google Apps from this thread (http://forum.xda-developers.com/showthread.php?t=2397942 ). MAKE SURE the version you download is for Android 4.4.x. It will say 4.4.x in the file name. I chose the Google Stock Package. (PA-Google Apps will allow you to enable ART if you want to.)
5) Turn on the Nook HD+, register it, and download all the system/firmware updates until the Google Play Store installs on your device (Google Play and Gmail etc. just recently got added to the Nook, so probably aren’t installed out of the box).
6) Transfer the three zip files (recovery image, CM11 and PA Gapps) you downloaded in step 4 onto the internal sdcard of the Nook itself. (This step is IMPORTANT: the current bootable version of CWM can ONLY read files on the internal SD, so you won’t be able to flash any roms or apps or recoveries unless they are actually on the device) I was unable to use the USB cable to transfer the files directly to the Nook from my computer—others have also had trouble getting Windows to recognize the Nook HD+ properly— and I didn’t want to spend a lot of time figuring it out, so I used the micro sd card as follows. If you can transfer directly from the computer, skip to step 7.
6a) Copy the new internal recovery, new system image and PA Google Apps from your computer to the micro SD card. Eject micro SD from computer.
6b) On the Nook, use Play Store to install a file explorer. I use Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en . You don’t need root to copy files from external to internal SD (and you don’t have root at the moment) so you can download any file explorer you like.
6c) Insert micro SD in the Nook while the Nook is still booted/on. The nook will flash a message saying that it’s mounting the SD card. Once it does, use the file explorer to copy all zip files downloaded in step 4 from the EXTERNAL to the INTERNAL SD. The internal SD card is referred to as “sdcard” or “sdcard0” and the external SD as “ext_sdcard” or “sdcard1”.
7)Turn off nook.
8) Insert micro SD card if it isn’t in already, and turn on the device. You should see the "Nook" logo, which gets overwritten by the "cyanoboot" logo. Keep waiting. It will eventually go into CWM. If it doesn’t, go back and start reading through the thread referenced in step 1. With any luck, you won’t have trouble. I had boatloads of trouble booting from the SD card until I got a class 4 micro SD, and used the bootable image linked in step 2. Since then I can boot every time.
9) Use CWM to backup stock rom, then wipe data/factory reset. (Very good instructions on using CWM here: http://forum.xda-developers.com/showthread.php?t=2317500 ) Flash the internal recovery. Flash the CM11 Rom. Flash PA Google apps. Remove micro SD. Select “Reboot System now”.
10) When you reboot, go to Settings/About tablet/Build number. Tap on that seven times to enable developer options. Go to Settings/Developer Options and select Advanced Reboot which allows rebooting into recovery from the power button.
11) OPTIONAL: Enable ART. ART is not compatible with all applications, so you might experience problems. You can see which applications work and don’t work here: http://www.androidruntime.com/. Enabling it made a very big difference for me in terms of smoothness; others with more experience seem to achieve similar, or better effects by modding with xposed, gravitybox, etc. See: http://forum.xda-developers.com/showthread.php?t=2579945&highlight=change+and+resolution&page=24) To read more about ART and what it does see: http://www.androidpolice.com/2013/1...-in-secret-for-over-2-years-debuts-in-kitkat/. If you decide to give it a try: Settings/Developer Options/ Select Runtime/Use ART.
12) Reboot—this time will take a while because ART (if you enable it) has to reconfigure itself.
For me, the difference is night and day. I now have a tablet that runs beautifully. Many many thanks to the hard working developers who make this possible, especially Verygreen, who provided the rom and recovery, and e.mote who wrote the "for dummies" thread that helped this dummy make it through the process.
Please comment and change anything that I have garbled. My goal is to consolidate information, not mangle it!
Very good post
Thanks for the excellent post. :good:
I was running 4.4.2 different versions on emmc and sd card.
10.2 nightly is still the best for me!
Performance and battery wise.
Hi I installed the same rom over Carbon rom. I went to format my sd card and every time iI tried the Nook would reboot. I went into CWM recovery and formatted it from there but I think it formatted the internal sdcard, Could someone check this out for me as this is my first post I cant post on the developer forum. TIA Mike
Not sure what you exactly what you mean, but it sounds like you were trying to format your external SD card from inside your nook? If you write the CWM bootable image to your external SD using Win32Diskmanager you don't need to format it. Writing the image will erase everything already on the external sdcard. You should be able to boot from it and install the zips. Is your problem that you can't boot from the external SD, or that you erased the zips from your internal sdcard?
Go back and read over verygreen's thread referenced in step 4-- I think he may have posted an updated version of CWM that can read the external sd card. Otherwise:
Did you make a backup of your carbon rom install? If so, you could write a bootable (earlier) version of cwm to the external sdcard, copy your backup to the sdcard and restore it, and then start over. (or not, as some people seem to think Carbon rom is just as good-- I never tried it) The thread in step 9 has great instructions that might help with that.
This thread (http://forum.xda-developers.com/showthread.php?t=2579945 ) is about installing a different version of cm11, and it's in a non-developer forum, where we can post. You might find answers there.
se1961 said:
Not sure what you exactly what you mean, but it sounds like you were trying to format your external SD card from inside your nook? If you write the CWM bootable image to your external SD using Win32Diskmanager you don't need to format it. Writing the image will erase everything already on the external sdcard. You should be able to boot from it and install the zips. Is your problem that you can't boot from the external SD, or that you erased the zips from your internal sdcard?
Go back and read over verygreen's thread referenced in step 4-- I think he may have posted an updated version of CWM that can read the external sd card. Otherwise:
Did you make a backup of your carbon rom install? If so, you could write a bootable (earlier) version of cwm to the external sdcard, copy your backup to the sdcard and restore it, and then start over. (or not, as some people seem to think Carbon rom is just as good-- I never tried it) The thread in step 9 has great instructions that might help with that.
This thread (http://forum.xda-developers.com/showthread.php?t=2579945 ) is about installing a different version of cm11, and it's in a non-developer forum, where we can post. You might find answers there.
Click to expand...
Click to collapse
Sorry I didn't explain very well, I installed verygreens KK rom succesfully and wanted to do a backup of it. I put in a SD card and thought I would format it as it had some old junk on there. When I tried to format through the settings section the tablet would just reboot. So I booted into evergreens CWM recovery and tried through there, it formatted something but my external card cannot be read. And some of my settings have been lost, some time ago I used 4. Swapping "sdcard" and "ext_sdcard" from this post http://forum.xda-developers.com/showthread.php?t=2062613. So I think that may be my problem. I have back ups so no problem.
mikemelbrooks said:
some time ago I used 4. Swapping "sdcard" and "ext_sdcard" from this post http://forum.xda-developers.com/showthread.php?t=2062613. So I think that may be my problem.
Click to expand...
Click to collapse
Ah! I thought from your first post that you were quite new to this process, but clearly you are ahead of me on this one. Good luck.
Update: installed the latest build which has the touch screen patch. It's PHENOMENAL. Truthfully, the only thing I need this tablet for is using a website that involves a lot of dragging and dropping. I had to train myself not to accidentally zoom and/or copy. No more! I haven't even enabled ART this time because it's working so well. I would have posted on Verygreen's thread to thank but don't have enough posts.
Sent from my BN NookHD+ using xda app-developers app
Back to stock
Great post i want to try this but am wondering is it possible to go back to stock after doing this, i installed clockworkmod before so i have a backup of my original nook before i installed anything.
RADZ1973 said:
Great post i want to try this but am wondering is it possible to go back to stock after doing this, i installed clockworkmod before so i have a backup of my original nook before i installed anything.
Click to expand...
Click to collapse
Yes, just restore your backup.
And BTW, never fully quote a long opening post like that. It just wastes bandwidth and we have to scroll through all that to see your comment or question.
Sent from my SCH-i705 using XDA Premium 4 mobile app
Respond
Sorry about the quote , thank for the info though cos i wasnt sure i could go back to stock. I have just followed this tutorial and all is well, this is good because my Moto g just got this update so im in sync .
RADZ1973 said:
Sorry about the quote
Click to expand...
Click to collapse
You can actually go back and edit out that quote.
Sent from my SCH-i705 using XDA Premium 4 mobile app
kokercey said:
Thanks for the excellent post. :good:
Click to expand...
Click to collapse
Next time, no need to quote the full post.
Nook for Android?
This works very nicely. But Nook for Android won't install. Are there properties I can change to allow Nook for Android to install on this 'new' Nook device?
rogerlig
Great tutorial.
I would suggest around your step 9, after you have made a backup with CWM, before you wipe data/factory reset:
Remove microSD. Reboot into stock Nook and connect to computer. Copy off the backup from clockworkmod folder to your computer. Then boot again with the microSD, and proceed to wipe and flash.
Otherwise, the backup may get wiped.
rogerlig said:
This works very nicely. But Nook for Android won't install. Are there properties I can change to allow Nook for Android to install on this 'new' Nook device?
rogerlig
Click to expand...
Click to collapse
You must get the nook for android app from someplace other than Play Store, like 1mobile.com.
Sent from my BN NookHD+ using XDA Premium HD app
I got everything running, but my HD+ is running extremely laggy. I did a full wipe, but my internal SD card is still a little over 7 gigs full. Is there something else I missed? The Nook reader is particularly slow.
liukuei said:
I got everything running, but my HD+ is running extremely laggy. I did a full wipe, but my internal SD card is still a little over 7 gigs full. Is there something else I missed? The Nook reader is particularly slow.
Click to expand...
Click to collapse
Yes, a full wipe (factory reset) did not remove your previous media files. To do so you need to boot to CWM and go to mounts and storage and format 'data and datamedia'. That clears out previous files and should improve performance.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Yes, a full wipe (factory reset) did not remove your previous media files. To do so you need to boot to CWM and go to mounts and storage and format 'data and datamedia'. That clears out previous files and should improve performance.
Thanks. Will I need to reflash CM 11 after?
Click to expand...
Click to collapse
liukuei said:
leapinlar said:
Yes, a full wipe (factory reset) did not remove your previous media files. To do so you need to boot to CWM and go to mounts and storage and format 'data and datamedia'. That clears out previous files and should improve performance.
Thanks. Will I need to reflash CM 11 after?
Click to expand...
Click to collapse
no if it successfully flashed last time, you just need to reset-up your accounts and install apps again.
Sent from my SCH-i705 using XDA Premium HD app
Click to expand...
Click to collapse
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
sremick said:
So I finally made the leap from Lollipop to Marshmallow. Everything has been going fine for the most part, but I've hit a huge snag: moving apps to SD.
I use Titanium Backup to keep a full backup of my phone on the external SD card. I depend on this backup for two purposes:
1) it makes updating the ROM (like this time) a lot easier. I do a factory reset, get the base Android going, re-install Titanium Backup from the Play Store, point it to my backups on the external SD card, and then I'm good to restore (either full app+data if that's safe, or I first re-install the app from the Play Store then just restore the app's data using TB).
2) It saves my butt in the event of a phone hardware failure, which has happen several times over my many years as an Android user. I just buy a replacement phone, move the SD card over, and restore my apps/data in a similar manner as in #1.
I have a Galaxy S5 with 16GB of internal storage, which is certainly not enough so I depend on my 64GB external SD card greatly. Between keeping all my large media on the external SD, as well as moving what large apps to SD as I can, this has been fine. I use Bliss ROM.
So make the jump from Android 5 -> 6, and finally get to the point where I need to move some of the apps I've restored to SD... but can't find the option. I do some research, and now am in a panic. From what I can tell, you can only move apps to SD if you use the SD as adopted/internal storage, which means it gets re-formatted, encrypted, and can only be used with that phone. This eliminates the possibility of #1 & #2 above. To continue performing #1 & #2, I need to use the SD as "portable storage" (the way it is now), which apparently leaves no way to move apps to SD.
I am in a pickle now, and feel stuck. I'm hoping I'm missing another option. Help?
Click to expand...
Click to collapse
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
ldeveraux said:
From what I've read there is a method for app2sd to work with mm. I never had success with it though, and downgraded to ll.
Click to expand...
Click to collapse
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
sremick said:
A method other than formatting the card as internal/adopted storage? Did the method involve setting up multiple partitions?
While I could set up a FAT32 partition just for TB, then adopt the rest, my backups aren't the only thing I've needed to access after popping out the SD card. For example, just being able to load media that way is quick and sometimes a life-saver. I've also used that as a way to get zip files on that I could then flash via recovery. I'm also not clear if you can "mount" adopted storage as USB while in recovery so it's visible to the computer as a USB mass-storage device while the phone is connected via USB cable (as you have been able to do normally up to this point).
Click to expand...
Click to collapse
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
ldeveraux said:
I'm not the app developer, I have no clue how/if it works. It didn't for me, but did for many others. Go to that thread and read up!
Click to expand...
Click to collapse
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
sremick said:
Which app/thread are you referring to? Or are you talking about Bliss ROM itself? I didn't post in that thread, as this issue seems generically Marshmallow-related, and not specific to Bliss.
Click to expand...
Click to collapse
It's a marshmallow problem, not Rom specific. In xda's app section there are threads for both link2sd (not working) and app2sd (works for some). Check those, I think that's where I saw the info.
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot. :good: Everything still working for you otherwise? I was thinking of upgrading now, and think this might work too:
http://blog.sam.liddicott.com/2016/02/android-6-semi-adopted-storage.html
sremick said:
Ok it wasn't easy but I think I've gotten my head wrapped around Apps2SD and have it working. I tried the free version, backed up my 64GB external SD, partitioned it with a 16GB f2fs partition (for moving/linking apps) and the remainder exfat (for using the way I've traditionally used it). Restored everything back to the exfat partition and fixed where BeyondPod and Titanium Backup were pointing to. Did a few test links and it seemed to be working although fumbling my way through was confusing at first as I didn't find a clear "how to". Ended up buying the Pro version of Apps2SD once I felt good that this was a workable solution.
I still get an error on boot about my SD being corrupt but I just need to search on that, I'm sure there's a simple fix somewhere.
Click to expand...
Click to collapse
Is f2fs and exfat supported by stock MM in Apps2SD? Got it formatted with fat32 and ext4.
ldeveraux said:
I think the consensus was to use NotifyClean (Xposed module) to eliminate that message at boot
Click to expand...
Click to collapse
Ugh. I do not want to have to use Xposed.
Everything still working for you otherwise?
Click to expand...
Click to collapse
Well it was working just great... then I rebooted. Apparently some trouble getting the 2nd partition (fsfs, where the apps are being moved to) to mount at boot. Trying to sort it out in this thread:
http://forum.xda-developers.com/android/apps-games/apps2sd-partition-sd-card-link-apps-to-t3122919
andacro said:
Is f2fs and exfat supported by stock MM in Apps2SD?
Click to expand...
Click to collapse
No idea, I never run stock.