Related
A Noobs Guide to Getting Started with a Custom Rom on the Nook Color
So you heard about the nook color. How it's a cheap e-reader that can be pushed to the limit and you are wondering how you can enable this power for yourself. Well you came to the right place!
Table of Contents
1. Why you should NOT use Honeycomb
2. SD or Internal instal
a. SD install
b. internal install
3. Restoring to Stock
4. Other Cool Stuff
5.Issues
6. Conclusion
7. Changelog (Last update 1/10/12)
1. Why you should NOT use Honeycomb
So you've heard about how the Nook Color can run Honeycomb and you are thinking that you want to try it. I mean why not? It's a tablet OS and the Nook is supposed to be turned into a tablet right? Well here's how it is. Honeycomb unlike other versions of Android is not an open source release. That means that developers cannot see how it works and have to reverse engineer basically the entire thing. This leaves you will something that barley runt because of countless missing drivers and many bugs from the SDK simulator. Honeycomb is a very painful and unstable experience. Do not use it. Wait for the next version of Android codename Ice Cream Sandwich to come out. For now use CM7. To check on the progress of CM9 (AKA ICS) check out this thread where you can find the first alpha builds.
2. SD or Internal install
The first decision you need to make is if you want to install CM7 (Android) over your current stock firmware or to run from an SD card.
a. SD Install
The benefit of running from an SD card is that you get to keep your Nook's current stock rom along side your Android install. The downside is that Android will run terribly if you do not use the correct SD card.
When running from an SD card use ONLY a SANDISK CLASS 2 or 4!
Take a look at this thread here for why you need to use a Sandisk:
Instructions for installing to an SD card
b. Internal Install
I recommend you do an internal install just because it is more stable and a lot easier to troubleshoot and upgrade to a newer CM version. If you ever need to return to stock it is very easy (see part 3).
To install to your internal memory follow this guide
Remember if you have a newer Nook that came with stock version 1.2 or above you may want to follow the repartitioning instructions here to have more space available to save files.
3. Restoring to Stock
So something happened and you need to return to stock. You need to make a warranty claim, register you device with BN, or whatever.
Here is what you need to do
When you are done you will have a complete stock Nook to do whatever you want with.
4. Other Cool Stuff
Watch Hulu with a hacked flash app
Make your Nook more Honeycomb like with TransformerBread
5. Issues
Help Facebook keeps force closing!!!!!
Solutions:
1. Use Facebook 1.6 or lower
2. Use tetherGPS lite
3. Use a third party app
Use this thread for help
N64oid won't work!!!!
Starting with N64oid 2.0 and above the new .32 Nook kernel used in CM7 does not work with N64oid.
Solutions:
Use a version of N64oid before 2.0
Use an older version of CM7 without the .32 kernel
Use this thread for help:
6. Conclusion
I hope this guide helped you out. If you think there is anything I should add or you have any questions feel free to comment.
7. Changelog
1/14/11
Restoring to stock guide updated for 1.4.1 zip that will work for people with new touchscreens.
1/10/12
New Guide for restoring to Stock that uses 1.3 and the new clockwork to work on the newer blue dot Nooks.
Removed 1.2 zip as it is no longer needed
Removed "Guide" from Changelog
Changed "Guide Changes" to Changelog in Table of Contents
Added link to CM9 dev thread
12/23/11
Added 1.2 restore zip link
Added Conclusion to table of contents
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
votinh said:
Good work, kookid,
Comment on 2.b. about re-partition. It is an option, not a must so saying "you need to follow ...." might confuse others.
Click to expand...
Click to collapse
Oh good point. Will change.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Good overview for newcomers.
Will return here when I get my NC in November.
Two thumbs up, maybe this should get stickied.
What about overclocking/undervolting kernels?
OrganizedFellow said:
What about overclocking/undervolting kernels?
Click to expand...
Click to collapse
Overclock/undervolt is included in the CM7.1 kernel.
Overclocking is built in to the CM settings. To undervolt you need to use the Nook Tweaks app.
---------------------------------
Sent from my LG Optimus V using Tapatalk
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Could you at least post the name of the thread? I'm always looking for better ways to do things.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
Reverting to the factory original ROM can be done much easier than the link provided. I would post the link but I have not yet posted enough to provide a link.
Click to expand...
Click to collapse
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
I just substitute the full 1.3 .zip for the CM7 and gaaps .zips when booting with the original install image and it works fine. I recommend everyone who installs CM7 to the eMMC save their original install SD card for future needs and buy a 2nd one for use with CM7. The 1.3 .zip now seems to be missing from the drop box site though so someone will need to repost it. It was linked in this thread: http://forum.xda-developers.com/showthread.php?t=914690&page=29
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
vn33 said:
Thanks for a very useful thread ... even though I already have mine running on CM7 since last month, really grateful for the info regarding the Facebook FC.
I'm still very much a noob at this.
One suggestion for more info regarding an issue which many noobs like me may have: How to expand the partition to use the rest of the SD card. On my 16Gb card, it now has four partitions: Boot, 2x unallocated, and Storage. Using EASUS PartitionMaster, how do I expand the fourth partition ? Do I have to delete the two unallocated ? Any further info regarding this would be very much appreciated !!
If I use App2SD, which partition would those programs go to ? Seeing that I already booted from SD, the Apps are already on the SD, right ? No need to "move to SD" ?
Thanks ahead for the schooling !!
Click to expand...
Click to collapse
For your first question: just right click the 4th partition, select resize and then make sure everything is selected.
For your 2nd question: I'm not exactly sure as I do not use an SD install. Maybe someone else with more SD booting experience can help but what I am thinking is that all of your apps are on the 2nd or 3rd partition but when you use app2SD they get moved to the 4th partition.
---------------------------------
Sent from my LG Optimus V using Tapatalk
votinh said:
Link provided by koolkid was for 1.0.1 but I think it was the standard procedure for any other version.
I'm eager to learn a new, better way.
Click to expand...
Click to collapse
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
Unfortunately you cannot use the 8 failed boot method if you replace the stock recovery which most do when installing CM. That is why I used the method I did with this guide. It works no matter what is on your internal memory.
---------------------------------
Sent from my LG Optimus V using Tapatalk
BASIC! said:
I found a link that I could post:
http://forum.xda-developers.com/showthread.php?t=1054027
The simple complete wipe is near the bottom of the first post.
Click to expand...
Click to collapse
I'm probably slow but your provided link is for rooting the 1.2/1.3 NC using ManualNooter. It has nothing to do with reverse back to stock ROM.
And, the complete wipe near the bottom of the first post, again, has nothing to do with reversing if currently running custom ROM on eMMC.
A mod should definitely sticky this...most helpful thread I've read in the general forum yet.
Thank you so much
I just got a refurbished Nook Color and after hours of searching and reading I came across your post. This guide is a like a mother-load of good links and clear instructions. Thank you for taking the time to put it together. It has really helped me understand what was needed to get my NC up and running.
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
-Updated the Restoring to stock guide to use a 1.3 and the newest clockwork it's on Android Central for now but I might move it over here if I get some time.
zhourj said:
This is a really helpful guide for beginner.
I want to ask some thing about the whole workflow. I've used other Android phones to play with rooting and flashing new roms, but NC is quite new to me. So still need to make sure about something.
In this guide, there is nothing about rooting. And when I use CM7 from a SD card, I don't have to do that and already got the su in terminal. So I suppose if I just flash CM onto the eMMC, I'll get root access anyway. I don't have to root it right now in its stock system, right?
Click to expand...
Click to collapse
Nope, no need to root if you are going to flash CM7 because of the ability to boot a custom recovery from an SD card.
every link i see in all the how toos are dead. Very awesome tutorials but NONE of the links work.
I got a bone stock TP and would love to get at least ICS going on it for my daughters B-Day.
Any one help or host for me?
ShannonPricePhoto said:
every link i see in all the how toos are dead. Very awesome tutorials but NONE of the links work.
I got a bone stock TP and would love to get at least ICS going on it for my daughters B-Day.
Any one help or host for me?
Click to expand...
Click to collapse
There's a good lilliputing article that I'm sure you found with dead links. Use that, but Google for the exact file names; they're probably on goo.im.
Or Google the md5sum like here: http://forum.xda-developers.com/showthread.php?t=1838804.
here these are links from my own box account. they will never be dead. ever.
https://www.box.com/s/479acdb6ef9c99fc7b92
all you really need to do initially is flash the moboot bootloader and the cwm-recovery to the touchpad. then everything else like roms and other zip installers you can just move them to the touchpad from your computer or whatever then flash them through CWM recovery. simple as that.
but if you want to just do it all at once then here is the link for the latest cm9-nightly
http://download.cyanogenmod.com/get/jenkins/9588/cm-9-20121007-NIGHTLY-tenderloin.zip
REMEMBER!!!! if you're going to install everything at once using acmeinstaller you MUST change the name of the cm-9-20121007-NIGHTLY-tenderloin.zip or it wont install with acmeinstaller. just add update- to the front of he name like this update-cm-9-20121007-NIGHTLY-tenderloin.zip
then here is the link for the correct gapps .zip file http://goo.im/gapps/gapps-ics-20120429-signed.zip
same thing with the gapps zip you need to add update- to the name like this
update-gapps-ics-20120429-signed.zip
now when you have update-gapps-ics-20120429-signed.zip
update-cm-9-20121007-NIGHTLY-tenderloin.zip
update-cwm_tenderloin-1012.zip
and moboot_0.3.5.zip (only moboot doesnt need to have update- in the name) all inside the cminstall folder of the touchpad. then youre ready to get to work with the acmeinstaller.
enjoy!!
I got.most of.the info.from.this thread...
http://forum.xda-developers.com/showthread.php?t=1838804
New TouchPad: Trying To Install CM9: Guides are outdated.
and used Acmeinstaller3 so.that the.partitions would be compatible with.cm10 once its ready for.daily use.and followed the liliputin guide. Did it last night and like the op is.finding out, the hardest part was.find the right/updates files.
Sent from my "Up all night, Sleep all day" EVO3D!
curently have cm9 with twrp 2.2. How do I start over and load the new ROMS that are out. Any help would be appreciated. I don't care about he current apps and don't have files I need to save. Can someone point me in the right direction? thanks
Please read at least the first page of this excellent guide and view the videos by Roland Deschain.
http://forum.xda-developers.com/showthread.php?t=2147284
It contains all the info you need and and file links. either individually or as part of a package, which should make installation pain and stress free.
Have fun.
sstar said:
Please read at least the first page of this excellent guide and view the videos by Roland Deschain.
http://forum.xda-developers.com/showthread.php?t=2147284
It contains all the info you need and and file links. either individually or as part of a package, which should make installation pain and stress free.
Have fun.
Click to expand...
Click to collapse
I appreciate the information but still have a question. Does the acme uninstaller remove the twrp and do I need to reinstall something else?
r3nem1 said:
I appreciate the information but still have a question. Does the acme uninstaller remove the twrp and do I need to reinstall something else?
Click to expand...
Click to collapse
ACMEUninstaller2 (uninstalls Android and removes recovery, All versions) That's what it says in Rolands thread .
Yes you do need to install something else.But the files and info are all in his thread.
I know it's not easy reading but if you read just the first page your questions have already been answered.
Dear forum readers, geeks & developers,
I have been trying to seek for that one thread that could solve my issue which the title said it all. I have followed many guides & use multiple different tools, both on device & PC but to no success. Most of the threads would just say; "recompile after finished editing whatever you want". But that's definitely not the proper way. Some guides there were hints of keeping/replacing the Manifest.xml & META-INF folder, yes I kept it somewhere else & replace it just before I want to recompile, no it didn't work too.
One of the guides said decompile the APK, copy the *_src folder somewhere else & recompile it back right away, edit the copied _src folder & edit whatever you want. After editing, open/view the recompiled APK as zip & drag/drop the files you edited, yes it was recompiled successfully but when I apply it to the device it FC right away & were unable to boot up although I wiped Dalvik and Art Cache. One more example was, instead of replacing the edited files, this guide replaced the META-INF & Manifest.xml. The problem was I can't even get it to recompile successfully.
Something could be really wrong with me, my PC or my device, if only some generous kind soul would spare some knowledge to help this poor soul I would appreciate it very much, thank you for whoever spared the time for reading this, I hope my noobness made your day.
Cheers all,
- Merry Xmas &
A Happy New Year
DaRdamnDoG said:
Dear forum readers, geeks & developers,
I have been trying to seek for that one thread that could solve my issue which the title said it all. I have followed many guides & use multiple different tools, both on device & PC but to no success. Most of the threads would just say; "recompile after finished editing whatever you want". But that's definitely not the proper way. Some guides there were hints of keeping/replacing the Manifest.xml & META-INF folder, yes I kept it somewhere else & replace it just before I want to recompile, no it didn't work too.
One of the guides said decompile the APK, copy the *_src folder somewhere else & recompile it back right away, edit the copied _src folder & edit whatever you want. After editing, open/view the recompiled APK as zip & drag/drop the files you edited, yes it was recompiled successfully but when I apply it to the device it FC right away & were unable to boot up although I wiped Dalvik and Art Cache. One more example was, instead of replacing the edited files, this guide replaced the META-INF & Manifest.xml. The problem was I can't even get it to recompile successfully.
Something could be really wrong with me, my PC or my device, if only some generous kind soul would spare some knowledge to help this poor soul I would appreciate it very much, thank you for whoever spared the time for reading this, I hope my noobness made your day.
Cheers all,
- Merry Xmas &
A Happy New Year
Click to expand...
Click to collapse
Are you still having issues with this? If so can I suggest using my decompiling tool Tickle My Android? The link's in my signature.
Yes, I'm advertising my work but I also think it could help so..
Ticklefish said:
Are you still having issues with this? If so can I suggest using my decompiling tool Tickle My Android? The link's in my signature.
Yes, I'm advertising my work but I also think it could help so..
Click to expand...
Click to collapse
Well, you're back in business! I was letting you finished off your "Xmas & new year's off" with your 3 sons. I was trying to venture into Linux, hoping it would be more convenient to get tools & because it's free! However, I was wrong. 2 weeks later I am still installing/testing out different distributions. I have kinda abandoned my device most of the time now, unless you fix Toad & deodex my rom i wont be motivated to do anything
P/S: Im not even bothered of you advertising. Google is the main advertiser here, the main mastermind of Android.
The guides & tutorials needs a spring clean too.
DaRdamnDoG said:
Well, you're back in business! I was letting you finished off your "Xmas & new year's off" with your 3 sons. I was trying to venture into Linux, hoping it would be more convenient to get tools & because it's free! However, I was wrong. 2 weeks later I am still installing/testing out different distributions. I have kinda abandoned my device most of the time now, unless you fix Toad & deodex my rom i wont be motivated to do anything
P/S: Im not even bothered of you advertising. Google is the main advertiser here, the main mastermind of Android.
The guides & tutorials needs a spring clean too.
Click to expand...
Click to collapse
Things are still really busy at work so I'm not back to normal right now. But I'm trying to get as much done here as I can.
I don't know enough about Linux really - I just don't have the time or a free PC to play with so I can work it out. Which is a shame as it'd be great for modifying Android.
I did reply to your post on the TOAD thread though. You said about moving apps away and I asked for more clarity about what you were moving and how.
I recently hard bricked my Razer Phone 2(bootloader locked, but the OS got corrupted, and can no longer access recovery), and I need some help from a person with a working, rooted RP2. I found this guide for unbricking phones using an SD card(for those that want to see the guide, the link is here), but it requires information from a working version of the RP2.
For anyone interested in helping, here are the steps:
You will need:
Razer Phone 2(obviously)
SD Card(at least 64+ GB)
Root
Terminal Emulator(on the play store)
Busybox(link here)
Steps:
0.) Clean up your files. The finished file will have your entire internal storage within it. I don't wanna see any weird stuff(also clean your SD card and ensure it is exFAT; this file is going to be very big).
1.) Place the SD card into your RP2.
2.) Start up Busybox and install dependencies.
3.) Start up Terminal Emulator, and type this in:
su
Click to expand...
Click to collapse
4.) Then type this in:
ls /storage
Click to expand...
Click to collapse
5.) Find a hexadecimal set of numbers and letters(for example: 7368-9BEE); keep track of that set of numbers for now, as it is the name of your SD card.
6.) Then type this in(fill in [NAME OF YOUR SD CARD] with the set of numbers you found from step 5):
dd if=/dev/block/mmcblk0 of=/storage/[NAME OF YOUR SD CARD]/Loader.img
Click to expand...
Click to collapse
7.) Wait until the process is done(WILL MOST LIKELY TAKE A LONG TIME; BE PATIENT).
8.) If you see a "Loader.img" file in your SD card(may be around 60+ GB), you're done.
9.) Copy the file to your computer. It should be very large.
For those that complete it, I would be grateful if you could share the file(through Google Drive or MEGA) so that I can use it to unbrick my Razer Phone 2. Thanks.
Possible solution
Hey, I also have a bricked RP2. I'm getting in touch with a friend of mine who also has one to see if his is rooted. If it works out, I'll post the files for you. Thanks for the link.
TBurn420 said:
Hey, I also have a bricked RP2. I'm getting in touch with a friend of mine who also has one to see if his is rooted. If it works out, I'll post the files for you. Thanks for the link.
Click to expand...
Click to collapse
I honestly just sold off my RP2 for parts awhile ago and just used the money to buy a cheap flagship. I hope this method does work for you though.
TBurn420 said:
Hey, I also have a bricked RP2. I'm getting in touch with a friend of mine who also has one to see if his is rooted. If it works out, I'll post the files for you. Thanks for the link.
Click to expand...
Click to collapse
I'm still in the same situation Generic123 was in. I'd really appreciate those files, if you can share, Tburn420. I'm back on an older spare phone until I get this RP2 fixed. I'm sure it'll help others too.
I would also be grateful to need these files, otherwise I probably won't get my phone running
I have clean partition files, but rp2 don't have /dev/block/mmcblk0 (is used to sdcard) but he have other name sda, sde, etc.
I tried use theses files to revive my other rp2 (i have two rp2) but this method doesn't work
If someone have method to revive with sda, sde partitions, share please