Modified Boot/Installer - Nook Color Android Development

Hello again fellow nookie lovers....
DISCLAIMER: If you do not know what the following information does, means, or could result in if not performed correctly, please stop now and go no further. I hold no liability for how you use the following information or if you brick, bork or f&*k up your device.
Now with that, let's continue.....
I decided to post up a modified .IMG file I was able to throw together after getting my hands on a honeycomb preview. The original IMG was provided to me by a good friend (Thanks J and Thanks to the creator of the IMG) and then honeycomb come shortly after.
Using WinImage or a similar program to burn the IMG to a SD card, 1G or larger, will give you a bootable SD allowing you to boot directly into clockwork recovery and install the following:
B&N Original Firmware 1.0.1
Nookie Froyo
Nookie Honeycomb (SN:Overclocks to 1100 default)
Google Apps
Before installing any of the 2 Android systems, remember to visit "Mounts and Storage" and format the Data, System, and Boot partitions. Save Boot for last as it will lock up the nook and require a restart of the device. Once these areas are formatted, continue to install your preferred system of choice. Once that is completed, be sure to install the Google Apps zip to give you the market.
As of this time, the IMG file is approx 978 MB. As I modify I am sure it will grow to require a 2 GB SD.
For my next project, I will be including an image with some of the most important apps a Droid user needs, ie:
ADBWireless
Applanet
BetterTerm
SetCPU
etc
If there are any good apps that I might overlook, hit me up here and let me know.
Nookie-Installer - http://www.megaupload.com/?d=PLNQ9QYZ
~Exile~
"When All Else Fails, Try Linux"

could you provide some more detail as to why your method of installing these images is better then what we have now?
thanks

How does this require only a 1gb sdcard when HC itself requires almost 4? or am I misunderstanding?
sent from nookcolor

lafester said:
could you provide some more detail as to why your method of installing these images is better then what we have now?
thanks
Click to expand...
Click to collapse
I am not saying that my post is better than anyone else's. I am simply adding something in attempt to give more options to a resource that has already proven useful to me, as well I am sure to others.

Midnitte said:
How does this require only a 1gb sdcard when HC itself requires almost 4? or am I misunderstanding?
sent from nookcolor
Click to expand...
Click to collapse
Because you use it to flash the emmc zip which isnt very large. The 4gb image is the sdcard version. But this is no different then the flashable CWR.

Midnitte said:
How does this require only a 1gb sdcard when HC itself requires almost 4? or am I misunderstanding?
sent from nookcolor
Click to expand...
Click to collapse
The HC file is not the Full release. But thus far, other than bluetooth, the3.5 3rd pole and FM radio, everything else works fine for a pre-release. There are a few graffix glitches such as the scaling on the home screens, flickering in the market....
Other than that, HC looks amazing on the NC,

Flashing ROMs with flashable zips in CWM > anything else. Pretty much the safest, easiest method and I wish more people would post up those kinds of ROMs.

Related

Modified Boot/Installer

Hello again fellow nookie lovers....
DISCLAIMER: If you do not know what the following information does, means, or could result in if not performed correctly, please stop now and go no further. I hold no liability for how you use the following information or if you brick, bork or f&*k up your device.
Now with that, let's continue.....
I decided to post up a modified .IMG file I was able to throw together after getting my hands on a honeycomb preview. The original IMG was provided to me by a good friend (Thanks J and Thanks to the creator of the IMG) and then honeycomb come shortly after.
Using WinImage or a similar program to burn the IMG to a SD card, 1G or larger, will give you a bootable SD allowing you to boot directly into clockwork recovery and install the following:
B&N Original Firmware 1.0.1
Nookie Froyo
Nookie Honeycomb (SN:Overclocks to 1100 default)
Google Apps
Before installing any of the 2 Android systems, remember to visit "Mounts and Storage" and format the Data, System, and Boot partitions. Save Boot for last as it will lock up the nook and require a restart of the device. Once these areas are formatted, continue to install your preferred system of choice. Once that is completed, be sure to install the Google Apps zip to give you the market.
As of this time, the IMG file is approx 978 MB. As I modify I am sure it will grow to require a 2 GB SD.
For my next project, I will be including an image with some of the most important apps a Droid user needs, ie:
ADBWireless
Applanet
BetterTerm
SetCPU
etc
If there are any good apps that I might overlook, hit me up here and let me know.
Nookie-Installer - http://www.megaupload.com/?d=PLNQ9QYZ
~Exile~
"When All Else Fails, Try Linux"

Clear Cache and Data from Stock Recovery

I've seen a number of requests for this functionality and recently it became necessary for one user who had a disabled Home Key to clear cache and data without the use of ClockworkMod. I have reserached two methods to address this issue. These instructions require some familiarity of android, computer and tablet terminology and usage. Feel free to ask for clarifications in comments. Here we go...
Method I - Stock Recovery Command File
Technical: Stock Recovery command file can be used to perform a few additional functions as well as to alter the path to update files. These commands will execute with all privileges available to recovery mode.
Advantages: Very easy to use. Very little technical knowledge required. No third party software is required for use.
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Prepare a text file named "command" (no file extension) with one of the following commands on a single line. The wipe data command will wipe both data and cache. Wipe cache will wipe cache only.
--wipe_data
--wipe_cache
2) Place the file in a folder named "recovery" in the root directory of your MicroSD card.
3) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
4) Allow the command to execute completely then the tablet should reboot (this may not occur automatically depending on firmware installed).
Method II - Updater Script
Technical: The attached "Updater Scripts" perform delete commands (recursively if necessary) on the named directory or file(s). The directories are mounted automatically by the system before the script executes but it could be easily revised to include that step if necessary. The partitioning, formatting and directory structure are left untouched. Only files are deleted.
Advantages: No third party software is necessary for execution. Relatively easy to modify for more surgical precision (i.e. leaving installed apps but clearing possibly corrupted system data). Included example: "Clear Battery Stats"
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Download the attached archive (ClearData.zip) to your computer.
2) Extract the files to your computer. You should then have a folder named "recovery" (which contains a file named "command") and an additional archive named "update.zip"
3) Place the recovery folder and the update.zip in the root directory of the MicroSD card.
4) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
5) Allow the script to execute completely then reboot the tablet (this may occur automatically depending on firmware installed).
This will become handy someday.
Thanks for sharing your knowledge.
You're welcome. One quick note... the new stock recovery adds a menu simiilar to ClockworkMod. These methods will still work since the recovery folder/command file are checked first but it really isn't as necessary any more.
Need Help
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Me too
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
lrgche said:
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Click to expand...
Click to collapse
That's an indication that you may have more serious problems. nvflash will be required. http://forum.xda-developers.com/showthread.php?t=861950
Once done you will likely need to install ClockworkMod and repartition your internal storage.
Loukoebel said:
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
Click to expand...
Click to collapse
If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://forum.xda-developers.com/showthread.php?t=865245
Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
Does your method in opening post have to be run from external micro sdcard?
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
K J Rad said:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
Click to expand...
Click to collapse
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
K J Rad said:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
Click to expand...
Click to collapse
Wipe data does what--remove the apps installed?
And the partitions?
Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...
1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.
2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
lsu205 said:
Wipe data does what--remove the apps installed?
Click to expand...
Click to collapse
Removes user apps and their associated data as well as system related data and settings.
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
CodeNamePapa said:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
Click to expand...
Click to collapse
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.
If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)
Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.
http://forum.xda-developers.com/showpost.php?p=13059520&postcount=57
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
More thoughts:
because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?
I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...
I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip
Also:
read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?
edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.
I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.
Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.
The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.
I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.
I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.

[ROMS]Dualboot Phiremod / Honeycomb Image for SDcard [UPDATE-6/22]

Hi again everyone,
I've prepped an IMG file that you can dualboot Phiremod v6.1 and HC v4 2nd Edition off one SDcard.
1-The image file is 3.7gb. So you will need a 4gb SDcard or larger.
2-Both roms share the same SDcard partition. So on a 4gb card, the available space is limited to 1.8gb.
3-If you use an 8gb SDcard. To get use of the remaining storage on your SDcard. Just burn the image and then use EASUS Partition Manager to extend the SDcard partition. (Which is the 7th partition on the card)
4-I've udpated the Phiremod v6.1 with:
-The latest OC Kernel by Dalingrin 041811C
-Alsa update for smoother video playback
-Honeycomb Softkey Icons by XDA user Bawb3
I've done this mainly just for fun and to see if it would work and thought I'd share it with everyone if you wanna give it a go. Thanks to all the devs for all their hard work in getting these great ROMs for our Nook Color.
Credits:
The CM7 Team
Dalingrin
Deeper-Blue
Samuelhalff
Divine_Madcat
Phiredrop
j4mm3r
Rookie1
Bawb3
Download:
ph-hc-dualboot-sd.img.zip
MD5: 36b474afb9436bc2e887aeecec8b5c7e
Click to expand...
Click to collapse
Follow directions from Nookdevs.com to burn the image to your SDcard.
Burning a bootable SD card
Once you burn the image to your SDcard. Power off your nook and place the SDcard in your nook.
-To boot into Phiremod Nook v6.1 just power on your nook with the sdcard in and leave it alone.
-To boot into HCv4 2nd Edition, hold the HOME button while powering on. Continue holding the HOME button until you see the "Android..._" screen.
Take it or leave it, just hope you enjoy it.
---------------------------------------------------------------------------------------------------
Edit 5/23: Updated Img with Phiremod 6.2 and Madcat's Honeycomb Hybrid-RC1
Reason for creating a new image and not just a flashable update is because the HC Hybrid /system was too large to fit on the original Dualboot img. So I prepped a new one for that reason as well as making the image smaller so it will definitely fit on a 4gb uSDcard.
What's included in this new image:
1- A 3.4gb Img file that should fit on any 4gb uSDcard or larger
2- J4mm3r's u-boot menu! (Read here for more info on how to use it)
3- Latest Phiremod 6.2 with Dalingrins 4/13a OC and Alsa update
4- Latest Divine_Madcat's Honeycomb Hybrid RC1
5- Honeycomb Hybrid RC1 has my sdcard mount workaround. I also included a file manager.
6- Read here for more info on the sdcard mount workaround.
7- Follow the steps above to burn the image to your uSDcard
8- Enjoy!
Keep in mind that the Honeycomb Hybrid RC1 is a work in progress so there are known issues. I suggest you read the OP in this thread here to see what's working and what isn't.
Download:
ph-hc-dualboot-sd-v0.2.img.zip
MD5: 9cda109f5fb8397d5bbd1912714b6a57
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------
Update 5/31-Phiremod Nook 6.3 Dualboot SD Flashable Update:
This will only format /system. Data stays intact.
1-If you're still using the original Dualboot-SD img. Follow directions below from 5/5 update on how to install latest Phiremod to your Dualboot-SDrom.
2-If you're using latest Dualboot-SD v0.2 with j4mm3r's boot menu. Choose to boot into SD-->Recovery and flash from there.
phiremod-nook-6.3-Dualboot-SD-Update.zip
MD5: 445482d78263e8596063ea104a46fb7d
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------
Update 6/22-Phiremod Nook v7-Test Dualboot SD Package Update:
This will format /system and /data of your Phiremod rom. So please backup all your apps!
Well I went ahead and made it easier for everyone. So I packaged the whole Phiremod v7-Test as a CWM-SD Flashable zip. This will install phiremod-nook-v7-test, gapps, and will install the launcher-pro backup to the sdcard partition for you.
-All you have to do is download the 'phiremod-nook-v7-TEST-SD-CWM-package.zip' file, no need to extract anything
-Boot into CWM-SD and flash the package zip file
-Reboot when done
-It will prompt with 2 different options on startup, choose "Setup Wizard"
-For some reason it won't get past that, even when touching the Android guy, to get around this touch all 4 corners of the nook screen starting with:
1. top left hand corner
2. top right hand corner
3. bottom right hand corner (just above the 'change language' button)
4. bottom left hand corner (just above the 'emergency' button)
-That should get you to the main screen.
-Connect to a wireless network
-Market will not populate correctly, so go into the app drawer and choose 'Talk'
-That should give you an option to add a google account
-Once completed go back to the main screen and goto options--> preferences --> and restore the launcher pro backup
-You should now see Market on the home screen
-Don't forget to thank the devs!
-Personal thank you to "bdeville" for testing the .zips for me before I borked any more installations!
phiremod-nook-7-Test-Dualboot-SD-Package.zip
MD5: b814eb7681ea57669764e449b77ef4c1[/QUOTE]
---------------------------------------------------------------------------------------------------
Edit 5/5: Update Phiremod to 6.2 and Honeycomb to Madcat's Honeycomb_RC1
1- I forgot to mention that with your dualboot rom SDcard. It also contains a Modded CWM that will allow you to flash updated roms from "my" thread only!
2- Place the .zips you downloaded from this thread onto your /sdcard (7th) partition.
3- To boot into the Modded CWM. When powering on your nook. Hold the "volume+/volume-" together while booting up, until it loads up CWM
4- Now select "choose zip from sdcard"
5- Choose the .zip file and confirm "yes"
6- Sit back and let it do its thing
7- You can either flash another rom or go back to the CWM main menu and choose "Reboot system now"
8- Enjoy your updated roms!
Downloads:
Phiremod 6.2 Dualboot SD Update: (This will keep your /data partition intact)
phiremod6.2-SD_Dualboot-Update.zip
MD5: f6350cb0393576d5e53fe5ce3315aec1
Click to expand...
Click to collapse
Divine_Madcat's Honeycomb RC1v2(Working su, market, sound) Dualboot SD Updated: (This will format both /system and /data)
update-HC-rc2-Dualboot-SD-a.zip [Updated 8pm EST. / Tested and working by me]
MD5: a4231f7e141c1e875ad07cef2e97d912
If you get a keyboard failure error on first boot. Just do a quick reboot and it should go away. Downloads from market seems very slow off an SDcard install. Might just depend on what Class it is. And remember. This is a WIP. Don't forget to thank Madcat for his work on this!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If I've helped in some way, please say thanks in one way or another!
Thanks,
Racks
Nice. Will try
Sent from my SGH-T959 using XDA App
AAAAAAAAAaaaaaaaaaahhhhhhhhh
Just when I think: "Enough of this craziness, let's just sit down and enjoy my nifty little device," along comes YET ANOTHER rom to flash!
If I do this one, though, I get back one, maybe two of my 8 GB cards. So, win/win.
Excellent work, Racks!
glg
glgehman said:
Just when I think: "Enough of this craziness, let's just sit down and enjoy my nifty little device," along comes YET ANOTHER rom to flash!
If I do this one, though, I get back one, maybe two of my 8 GB cards. So, win/win.
Excellent work, Racks!
glg
Click to expand...
Click to collapse
Please let me know if it works out for you or not. Just so I can make any needed changes if necessary.
Thanks,
Racks
Worked great for me. Had my flashing 4gb and it booted right up into HC. Great work. Didn't realize how good HC looked on here, but I'm sticking to Phiremod for now.
racks11479 said:
2-Both roms share the same SDcard partition. So on a 4gb card, the available space is limited to 1.8gb.
3-If you use an 8gb SDcard. To get use of the remaining storage on your SDcard. Just burn the image and then use EASUS Partition Manager to extend the SDcard partition. (Which is the 7th partition on the card)
Thanks,
Racks
Click to expand...
Click to collapse
Howdy,
Any way to implement this "mod" into your image???
[ZIP][CM7] Nook Color SDcard and emmc swap!
Thanks very much Racks, it works really well. Finally get a chance to try Phiremod and honeycomb without using 2 SD cards!! I only have one, the poor guy that I am
I too loaded the image to a 4 gig card and it seems to work fine so far. Thanks for your efforts!
Thanks man.... It worked for me as well!
oops maybe I spoke too soon, the phiremod works ok, but, the honeycomb loader never gets by the screen with the android_ on it. I will reflash later without epanding the partition on the SD card to see does that make a difference.
(yeah I used an 8GB card and used easus to expand the 7th partition.)
Glad to see that this image was useful to some!
Thanks everyone for the thanks,
Racks
racks11479 said:
Please let me know if it works out for you or not. Just so I can make any needed changes if necessary.
Thanks,
Racks
Click to expand...
Click to collapse
Didn't actually get to try it last night. Bandwidth trouble.
Downloaded, unzipped, flashed to a 8gb Sandisk card. Left it as burned.
Installed in Nook: Booted to Phiremod AOK. Rebooted into Honeycomb AOK*.
Shut down and put sdcard back in my PC to resize the sdcard partition. Hmmm.
Both EASUS and MiniTool show the card as 8GB unallocated (ie: no partition information available!!).
Put it back in nook and reboot. Comes up to phiremod AOK. Weird.
OK, second time around putting SDcard in PC, I got correct mount and could edit partitions.
glg
* - Honeycomb lock screen says "Running on internal eMMC" which we know is not true.
** - I love that you changed the POST message. Those of us in Pennsylvania see the stock message as Touch the Future of Redding (the city). Um.. Not without latex gloves, I think.
glgehman said:
Didn't actually get to try it last night. Bandwidth trouble.
Downloaded, unzipped, flashed to a 8gb Sandisk card. Left it as burned.
Installed in Nook: Booted to Phiremod AOK. Rebooted into Honeycomb AOK*.
Shut down and put sdcard back in my PC to resize the sdcard partition. Hmmm.
Both EASUS and MiniTool show the card as 8GB unallocated (ie: no partition information available!!).
Put it back in nook and reboot. Comes up to phiremod AOK. Weird.
OK, second time around putting SDcard in PC, I got correct mount and could edit partitions.
glg
* - Honeycomb lock screen says "Running on internal eMMC" which we know is not true.
** - I love that you changed the POST message. Those of us in Pennsylvania see the stock message as Touch the Future of Redding (the city). Um.. Not without latex gloves, I think.
Click to expand...
Click to collapse
Lol. I really appreciate you sharing your experience with everyone.
And regarding honeycomb mentioning it's running off emmc. That's because I took the complete zip from samuelhalffs thread without modification and prepped it for the SD install.
Thanks,
Racks
How would i benefit if i already have phiremod v6 installed emmc?
First ever post: Great Job!!
Have been a lurker in the site for the longest time. Been actively watching the developments in the HD2, NookColor and GTab forums.
Kudos to all the developers and modders who've made Android dream a reality.
And, a special thanks to you, who made it a double treat for people like me.
Only trouble, with this dual ROM (which I've to tell you, my friend, has blown my mind away), that I've not been able to overcome yet is, getting my XP Pro or Win 7 Pro to recognize my 7th partition (SDCard). Nothing I've done so far has helped.
Tried both ADB and NookColorUMS. I sure am doing something wrong. Any help is much appreciated.
Once again, THANK YOU!
pisces73 said:
Have been a lurker in the site for the longest time. Been actively watching the developments in the HD2, NookColor and GTab forums.
Kudos to all the developers and modders who've made Android dream a reality.
And, a special thanks to you, who made it a double treat for people like me.
Only trouble, with this dual ROM (which I've to tell you, my friend, has blown my mind away), that I've not been able to overcome yet is, getting my XP Pro or Win 7 Pro to recognize my 7th partition (SDCard). Nothing I've done so far has helped.
Tried both ADB and NookColorUMS. I sure am doing something wrong. Any help is much appreciated.
Once again, THANK YOU!
Click to expand...
Click to collapse
Thanks for the kind words. Just remember to thank the guys who developed the roms. To mount the 7th partition try running the following command in adb shell:
#echo /dev/block/mmcblk1p7 > /sys/devices/platform/usb_mass_storage/lun0/file
This should mount the 7th partition. Let me know if it works.
Thanks,
Racks
I was looking to dual boot Phiremod and Stock on EMMC after seeing how awesome Phiremod is, but the place that I found supplying ROMs for dual-boot EMMC doesn't have Phiremod. Do you know where I could find it/do it (total n00b)
Source mentioned- http://forum.xda-developers.com/showthread.php?t=959461
Market script
Excellent work OP (and obviously all the devs that made the roms etc.). One quick question though, I first flashed this image on a transcend class 6 8gb card and, due to the low random write speeds, I experienced random sluggishness and force closes. I will be resolving this issue tomorrow, but another issue has arisen. When I first ran the market a script ran that asked which gapps i wanted installed. After it directed me to install the first two gapps the market force closed. Before I had realized that it was my SD card that was causing the force closes I tried reflashing the SD card with this image again but when I opened the market again after reflashing the script didn't run.
My question is this: When I flash the new SD card will the market script run again? And if not, how would I go about have the market script run again?
Thanks in Advance,
Deusx
I just love it, i just love it racks. Now i'm tryinna get used to the honeycomb. How do i change wallpaper?
Blaggah said:
I just love it, i just love it racks. Now i'm tryinna get used to the honeycomb. How do i change wallpaper?
Click to expand...
Click to collapse
Lol. Glad it's working out for you. Make sure you thank the roms devs as well.
Just long press the home screen and it will bring up options todo so in honeycomb.

[DEV][BETA][PREVIEW] TWRP 2.2 Recovery for NT

Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ORIGINAL POST (from May):
This is a work in progress.
TWRP (Team Win Recovery Project) 2.1 by TeamWin is an alternative recovery (instead of ClockworkMod) that is a good companion for Goo Manager. See this video for more info.
This is an experimental, mostly untested build of TWRP2 for entertainment purposes only. USE OR ATTEMPT TO USE ENTIRELY AT YOUR OWN RISK. It is intended for those who are willing to risk any and all damage, loss, and STD infection to their hardware, data, person, and associates resulting from this software. Do not attempt to use unless you understand and accept these risks.
Please note this is using the still-being-developed 3.x kernel.
I am including the raw .imgs which can be fastbooted or used on an SD (rename recovery.img.sdcard to recovery.img and put on SD in place of the existing version). Which I don't recommend doing of course, given the disclaimer above. Remember I don't have an NT so I haven't run this... ever.
Finally, this has not at all been put through any kind of paces. That's for you, assuming all the risks, to do. And report it back here for everyone's benefit.
Thanks to dees_troy, eyeballer and demetris_I & frustro for testing this. I'm busy the next few days, so I'm volunteering demetris_I, who has it running, to answer anyone's questions per his availability
twrp-2.1-nt-2012-05-17E-fullofbugs.tar.gz
History
6/12/12 - updated first post.. No binaries yet.. Can someone make one?
5/17 -
Updated 3.0 kernel to support new 512GB NTs (untested)
Updated twrp codebase to latest
Newer cm9 stuff as well
5/17B&C
Use cmdline from u-boot.bin to determine max ram size.
fix device showing up as "B" to "NookTablet"
5/17D&E
I can't remember. But it's betterer.
Has anyone successfully flashed this yet? And can anyone offer up the steps in a more-in-depth way?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Well... there's always update.zip
I haven't tried it, but I'm guessing if you've installed fastboot to your computer, this should work:
1. boot into cyanoboot and choose Fastboot from the menu.
2. On your computer, navigate to where recovery.img is and enter into the terminal
fastboot flash recovery recovery.img
Or... maybe someone could whip up a quick update-twrp2-nt-2012-5-14.zip maybe?
I guess that someone might as well be me. This is intended for use with an existing cwm recovery. This will flash to emmc...maybe.
update-twrp-2.1-nt-2012-05-14-fullofbugs-emmc.zip
MD5: 337269fa77017150325d398216a6dd3c
Thoroughly and completely untested. I really don't know if it will even install, and if it does, if it will work. See all disclaimers above, plus make up some additional ones yourself.
Edit: See below about a possible issue with possible difficulties accessing the external SD card. Internal /emmc seems to work consistently. Looking into it, but if you want to help debug this, that would be much appreciated. Just knowing what works or doesn't work and log samples (dmesg via adb) would be great.
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
It will replace cwm.
Rom doesnt matter , they reside in different partitions.
Cyanoboot is all you want if anything goes wrong or/and CWM/TWRP from sd card so you can dd the recovery.
SilentStormer said:
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Should replace it completely. I say should because if you do this with the update.zip, you will be the first one to try it.
Oh, Mister_Argent is trying it on IRC...
The Zip seems to work! Android boots fine, and it's entirely possible to get into TWRP via Cyanoboot. This might just be me, but the terminal seems to lock up...
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
So we can still flash stuff through emmc?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Indirect gave me this command to flash recovery via terminal emulator and it worked out nicely
dd if=/recovery.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
where "/recovery.img" is the file path/file name of the recovery image
Recovery looks nice. I'll do some more playing with it later when I have time.
fattire said:
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
Click to expand...
Click to collapse
No issues with external sd it just take some seconds to mount, is not instant but it will mount.
8gb NT. Successfully flashed internally; will test, log and provide feedback on any issues.
The zip file name is overly long and CWM doesn't like it. Renaming to something shorter solves the issue.
In my experience with other android devices, it is normally recommended you wipe 'dalvik cache' whenever changing / updating kernel. Perhaps this step will avoid some issues for people.
Edit: Flashing gapps update via Goo Manager results in failure of rom to load after Cyanoboot screen. I did not choose to wipe dalvik / cache in Goo Manager. Also unable to access Cyanoboot via N. Screen appears but does not seem to respond and automatically boots emmc (blank screen).
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
demetris_I said:
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
Click to expand...
Click to collapse
I could not access twrp as already stated, because Cyanoboot did not respond to button press. I've managed to get access to CWM via sdcard and reflashed another gapps. CM9 still will not load.
Next, I plan to wipe everything and flash CM9 anew.
Edit: Still won't boot. Looks like I have a brick to fix.
Edit2: Flashing CWM internally got everything working again. Cyanoboot would previously go automatically to loading from emmc; there was no delay / opportunity to press N to access the menu. Now the delay occurs and I have access. CM9 also loads.
Edit3: Reflashed TWRP internally again. It's not working on 8gb NT. It doesn't break Cyanoboot or prevent CM9 from loading, but any attempt to load TWRP results in a black screen.
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
demetris_I said:
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
Click to expand...
Click to collapse
I flashed the above emmc zip via cwm internal
I have adb working, however fastboot seems to require a separate driver to work in windows. I've searched the forum and have not found a clear answer.
I'm guessing the 3.0 kernel doesn't have support added for the 8gb nts yet. I guess maybe I could look into that...
Sent from my HTC Vision using XDA
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Recovery is separate from the rom. You'll be fine. I have it running on my 16GB.

[HOW TO] Root/Run from sd/Install CM10

I am now making post that there really shouldn't be any need for, because all that's in here is already covered elsewhere. 100% Apparently not easy enough to find for newcomers, so I'm making an attempt to help info collection.
NOTHING here is my work! All I’ve done is trying to make easy to follow instructions to other people’s hard work. Those people deserve your thanks, not me!
I’m a newbie myself and that’s why I can say that this really is very easy! If I can do it without problems, so can you! I try not to chat away too much in the instructions. Make regular searches, here or Google for more info. I found it, so surely you can too! Any questions? Well, being a noob myself I probably can't answer. Google is a very good friend of mine though...
Please do not ask questions through pm. It's better if people that know more than I do get a chance to answer them in the thread instead!
You need to know how to burn an sd image. Separate instructions to that after the other instructions if you don’t.
Step 1: Establish what it is you want to do! Choose A, B or C
A: You do not want to touch the internals of your NT but want to try CM10 anyway
B: You want to stay in the BN environment but would like to be able to install apps from elsewhere (for example Google Play Store)
C: You want to get rid of BN and install CM10 instead.
A: Run CM10 from sd card – no root required
This should work on 8GB Tablet as well as 16GB
When you boot into the card you’re running Android ICS. Remove the card and you’ll boot to internal BN operating system. (Or keep the card in, boot to Cyanoboot Menu and choose “internal boot”)
Ready-made card image download links to be found here: http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
It’s a large download (around 500 MB), but it is a ready-made sd card image. As it says in the instructions there, you’ll more than likely want to expand the user partition to take full advantage of the card, but that’s covered in his instructions.
There are other, more manual ways to make these cards as well. Also covered both in that blog and here at XDA! Go search!
B: Root the Tablet
This works on both 8GB and 16 GB Tablet.
“Rooting” is like unlocking your device, giving you access and control over it. You’re still running BN operating system though. Several excellent root guides here on XDA.
For example: http://forum.xda-developers.com/showthread.php?t=1488035
Or http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
The first one (Brian’s) require a 2 GB card the other one (Albert’s) just needs a very small card. (I think 128 MB would do, but I don’t have any that small to try)
Both give good instructions in their topics.
Both install gApps.
If you want to block OTA updates from BN, go to Play Store and find NT Hidden Settings. Even if it got installed with the root it’s probably not latest version and doesn’t have the Block OTA function.
C: Installing CM10 internally
***8GB owners must make sure to use ROM that works with their device!***
Since I’m a noob I look for easy way, and this is very easy and needs very little know-how!
***Warning! CWM is a very powerful tool. Do not "wander around" and "experiment" with stuff without doing proper research! Seriously! DON'T!***
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/showthread.php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
3. Boot into the sd-card and it should take you to CWM 5.x.x. environment.
I guess a backup of you current system would be a good thing (even though I admit to skipping that myself). To backup you'll probably need another card if you're using "The Albert Card" now, because I doubt it's enough room on that.
You navigate with the volume rocker, go back to previous menu with “power” and confirm choices with “n”
Choose “install zip from card” – “choose zip from card” – your CWM zip
See warning above!
4. Power off and prepare your sd card for ROM flashing. (If you’re working with just one card you will need to format it with SD Format or similar to get it back to full capacity.) Put your CM10 ROM zip and the appropriate gApps zip on the card.( It doesn’t matter if there’s other stuff on the card, so you don’t have to format it because of that!). I will not link to a specific ROM. Make your own choice but be sure it works for your model and also make sure you use the right gApps!
5. Reboot into Cyanoboot. This took me a couple of attempts to get right.
From powered down device, press power and right after that press and hold "n", You should boot into Cyanoboot and get the boot menu. Choose "Internal recovery" and you should get into new CWM
6. I don’t know how much clearing is needed, but I prefer to clear pretty much everything to make sure of a clean install. Cache and Dalvik I always clear.
***DO NOT format anything unless you knwo what you're doing! *** (See Satan's posts below)
7. Flash ROM and gApps same way as you flashed the CWM 6.x.x (install zip from card – choose zip from card) reboot and go!
How to burn an sd-image:
I use Win32Diskimager. Download link in Albert’s root topic (and numerous other places!!)
Unzip into a folder.
(I also copy my various img files to that folder to have them easily available)
No need to install, just run by doubleclicking the EXE in the folder.
Make sure the device letter really is your sd card.
Click on the blue folder and navigate to your img file, choose it and “write”.
It will take some time if it’s a large img, but that’s what the progress bar is there for, isn’t it?!
Nice work ,
But you should add 'do not format any partition ' warning. Android users coming from other devices might do this by default during flashing rom.
Almost every one with bricked tablets has tried formatting partitions.
Sent from my ST21a
Thanks Satan! I did not know that! Will do!
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
satan89 said:
but looks like some people missed it.
Click to expand...
Click to collapse
It looks like a lot of people miss a lot of things...
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
+1000
Do not format especially the rom partition and, most critically, the factory partition which respectively contain a set of small files with device-specific unique data (not only Serial No. but also MAC address, public/private key certificates, etc.) and the backup archive copy of the same data files (/factory/romdata.zip).
Unfortunately, I've seen some "unbricking" tools (including some that are very frequently cited/recommended on these NT forums) reformat/zero-out and flash over these 2 partitions. The end result being, even in the event the "bricked" NT gets "restored to stock", depending on the specific tool used it could be carrying device-specific data of someone else's (e.g., tool developer's) NT.
EXACTLY!
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
I think this is exactly what happened to my NT. Took me weeks of researching (I don't have a lot of free time) to figure out how to restore my 16GB NT.
Help
Im trying to single boot CM10 from sd card without touching nook os. I am using guide (CM10.0 Jellybean SDCard IMG for Nook Tablet (12/31) FINAL)
I have tried for hours using different methods also and cant even get it to boot to CM, no CM logo at all. I have a BNTV250 NT on 1.4.3. I have tried multiple sd cards, I am using a Sandisk 8gb class 6.
In a nutshell all I should have to do is
-Format the card with SD formatter,
-Extract the (Extract cm10_xxxxxx_sd_hd.img from cm10_xxxxxx_sd_hd.7z/rar)
-Use Winimage to write the image to the SD card, correct??
The Nook still refuses to boot into Cyanogen, just boots up normal every time!
same with every procedure i have tried,
Any pointers????
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
asawi said:
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
Click to expand...
Click to collapse
No, I have not, will try now.........ty
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
HOLY ****!!!! I LOVE YYOU!!:laugh::laugh::laugh::laugh::highfive::victory:
That worked, I cant believe it. Why is this not written anywhere??
LOL! :laugh: Glad you got it working!! :good:
Any clue of how to get rid of booting that way? I'm not always with a USB cable witj me.
Enviado desde mi Nexus 4 usando Tapatalk 2
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
asawi said:
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Tried doping that with no luck. After 8 or 10 attempts magically boots todo cm. Thanks.
Enviado desde mi Nexus 4 usando Tapatalk 2
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
ThePhantom97 said:
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
Click to expand...
Click to collapse
Thank you very much for putting this together, it was very helpful!

Categories

Resources