[Q] replacing factory.zip image for 8 failed boots - Nook Color Q&A, Help & Troubleshooting

[Q] replacing factory.zip image for 8 failed boots - Nook Color Q&A, Help & Troubleshooting

is there a reasonably easy way to replace the factory.zip? (partition 3?)
I have what must be an older color, that if I do the 8 failed boots, it reverts all the way back to software 1.0.0
I find that it wont auto update to 1.4.3.
I have to first apply a 1.2 update, before it will take the stock B&N 1.4.3
(or manually thru cwm apply a 1.3 for example)
its not a deal breaker, but I'd prefer a solution that isnt boot into linux/dd the partition
this is a unit I muck around with, testing various roms, and getting it back to stock just involves a few extra steps.
thanks!

The easiest way to get it back to stock is just to flash it directly back with CWM. Go to my NC Tips thread linked in my signature and follow item A15. I have a CWM flashable 1.4.3 there.
However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there.
Sent from my BN NookHD+ using XDA Premium HD app

"However if you want to change the factory zip in partition 3, I can walk you through how to do that. It basically means mounting p3 in a rooted operating system like CM and copying the new zip there."
I'd like to try that if you are willing. Thanks!
I think im pretty experienced.
I have done cm7 / cm10 / on colors/NT many times, have run all the possible scripts you might think of more than once to fix various issues on many colors
one thing Ive noticed on this one after resetting data to the new partition scheme,
that just sort of nags at me, (besides not having a restore to the way I like it from the 8 failed boots)
after Im at 1.4.3 and think Im done, if I do a factory reset from within the stock rom
going to the "factory" screen (and before skipping oobe) seems to flipflop between thinking its got sw 1.0.0 and 1.4.3 , however, the running version in both cases is 1.4.3.
thanks again
----- edit -----
addl info:
I have a CM7 loaded / with the NookColorUMS am able to mount the partition, but have no idea how to maneuver to it, or the format of the zip I'd be dropping in it. (I assume its just a factory rom renamed) On the tablet, cant seem to find the partition after its mounted in either file manager program I've tried, and I've forgotten any real linux/Unix skills I used to have... and it would appear its not usable on the Windows side.

The zip to use is the one I referenced above in item A15. Just rename it factory.zip.
And since you have the UMS utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer. You can tell if you are there by seeing the factory.zip. Backup that one to your PC in case something goes wrong. Then copy the new factory.zip on the drive replacing the old one. Be careful with the other files there, especially the rombackup.zip. That is critical and needs to stay there. (In fact back that up to your PC too).
That's it, you're done. Next 8 failed boot you should be on 1.4.3.
Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier.
Sent from my BN NookHD+ using XDA Premium HD app

" And since you have the ums utility, mount p3 in the first section. Then plug in your USB cable to Windows and it should show up as a drive. Look at it with Windows Explorer."
Yeah, this is where the plan goes south,
anything mounted in UMS doesn't seem to be translated properly for Windows. I get a "you must format the disk" but no additional usable mapped drives.
the internal partitions in the version of cm7 UMS I have are all down below, in the 2nd section
do I have to mount the "big" extended partition first? then in the second tab of UMS the factory p3? (ill try it in a few)

No, don't do that. I'll give you alternate instructions.
Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory
The go to /factory with your root file manager.
Proceed as earlier instructed.
Did you see my edit above?
Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable
Sent from my BN NookHD+ using XDA Premium HD app

the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Edit2:
re: " Edit: and the reason your drives are not showing properly in Windows is you must activate UMS in CM7. Pull up your notification area and tell it to allow access after you plug in the cable "
Yea, Im doing that. Does one have to disable debugging or something too?
Its not a big deal at all, just didn't have it committed to memory and hasn't been necessary to this point to access the protected partitions.

mikeataol said:
the su/terminal thing is just what I need I think. will report back in 5
re:
"Edit: You know instead of doing the 8 failed boot to get back to stock, just do a nandroid backup with CWM while you have stock on it and then you can use that backup for restoring to stock. Much easier."
Oh, I have no trouble getting em back to stock, and "close" to perfect, but I could sell this unit and 6 months from now I wanna be able to tell the user just do this ( 8 factory failed) , and its good to go, and Im not supporting a rebuild to stock 1.0, then 1.2, or a cwm flash.
Click to expand...
Click to collapse
if you sell or give away your unit, be sure to erase and deregister with stock so it is removed as your device on the B&N servers. Otherwise the new user will not be able to register it. And you know stock recovery must be installed before the 8 failed boot works, right?
Also see my edit above about how to fix ums..... Yes you must disable debugging.
Sent from my BN NookHD+ using XDA Premium HD app

"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file

mikeataol said:
"Go to Terminal Emulator in CM7 and set for superuser (type su enter). Then type these commands.
mkdir /factory
mount /dev/block/mmcblk0p3 /factory"
Hi, I did the whole process twice , just to be sure before coming back... 2nd time was with a newly downloaded copy of the signed A15 zip
Are you sure the factory recovery wants the signed zip file and not the stock?
after 8 failed boots it does a data reset, then tried the factory image reinstall but the factory image reinstall part fails about 1/3rd of the way through
---
had to wing it on the mounting / copy a little as just running terminal put me in a read only file system
but im 100% positive I Installed the signed1.4.3. into factory (backed up the 1.0.0 factory.zip first)
just noting , I DID use the repartition scripts on this prior, setting it to the "new" 5gb data / 1gb media
but it seems to me that the stock recovery isnt liking the signed zip file
Click to expand...
Click to collapse
That is possible since I modified it. Go get a clean one from B&N. Go their support page and look for update. There will be a link to a big file that ends in .npk. Download that and rename to factory.zip.
Sent from my BN NookHD+ using XDA Premium HD app

It seems the 1.4.3 update zip from B&N isn't suitable as a factory.zip
neither the signed or unsigned works
I've grabbed 2 factory zips from other units
1.2.0 and 1.3.0 and copied them into factory, and they both work as expected on the 8 failed boots
I didn't get the complete result that I wanted , but good enough.
Thanks again for your help leapinlar, It's appreciated.

Could you put a custom rom as a factory.zip? Just a thought. It'd be cool to rollback to a stable rom like cm7 if something in a cm10/11 nightly goes wrong.

Related

extract nandroid backups?

I flashed my phone to JF 1.5 and in the process some how managed to screw up my sd card and lost all my apps. i did do a nandroid backup of jf 1.41 so i ahve those img files. I tried to restore to that to recover everything but it wont boot past the g1 logo. I tried downgrading firmware to 1.43 (couldnt find 1.41) and using the same restore for nandroid and still wouldnt boot. I also tried jsut applying the user data img to see if i could jsut grab that and it fialed on both firmware revisions 1.5 , 1.43.
In the end im stuck with a backup i cant use, the only thing i need off of it is the apps. I read that you can use the emulator to mount it but i couldnt figure that out. I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Anyone have a simple solution or a complex one i can follow to getting my apps out?

did you follow this?
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2

darkrangr said:
I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Click to expand...
Click to collapse
You go into the source directory, type "gcc -o unyaffs unyaffs.c", then you (create and) go to some directory where you want to extract the contents ("mkdir ~/extract") "cd ~/extract", and finally you extract the image "/path/to/unyaffs /path/to/data.img".

I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?

Unless your backup was corrupted, flashing the backup should have been fine.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
You said it failed - what error did it give? Did it say it couldn't find the command? Be sure you're running these commands on your PC with your G1 connected via USB, the correct drivers are loaded, and you have the fastboot program.
As for using unyaffs - I don't think you understand what you have to do to use it. You have to compile it on your PC...all you get is the source code. I haven't looked on the google code site, but I would imagine there isn't a version for windows.
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?

it didnt fail on the restore with fastboot, it loaded up everything fine and then when i rebooted it just sat on the boot screens forever and never loaded.

I am feeling nice so darkrangr if you want to PM your image files I will unyaffs it on my ubuntu box for you.

TemporalShadows said:
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
Click to expand...
Click to collapse
no, my apps were installed normally. I am running curent jf firmwar enow while i try to get my stuff back, but some of the apps i had are no longer available or have converted to pay apps, plus i forgot a lot of apps i had.

http://forum.xda-developers.com/showthread.php?t=497034
In the other tools archive on this post you can find the unyaffs tool fully compiled. Just move your image to the same folder, drag and drop it on the unyaffs.exe and watch the files appear.

How about YOU DIDN'T INSTALL GCC!!!
darkrangr said:
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Click to expand...
Click to collapse

[HELP] Nook boots directly to ClockWorkMod recovery

I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.

morph3us5 said:
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
Click to expand...
Click to collapse
What ROM did you flash? CM7? Telll us specifically what you did.

Did something rather stupid, I did dd if=%path to cyanogen mod% of=/dev/block/vold/179:0, believing that it should write to my uSD card, but it written the internal memory instead. Fixed this by booting into Nookie-Froyo, fdisked the partition, and boot to clockworkmod again to restore the whole thing. Now I lack the ROM partition in /dev/block/mmcblk0p2. Is there a guide somewhere or tool to rebuild that partition?

Hey this is happening to me to I can't get in to anything but recovery.
morph3us5 said:
I just flashed the CWM to my nook, but now when I try to turn it on, it runs directly into CWM recovery menu. I tried flashing to NC_1.3.zip, even tried dualboot, it does not help.
Click to expand...
Click to collapse
Sent from my PG06100 using Tapatalk

After few days of research, I found the solution!!!! I am back in CM7!!!!!
morph3us5 said:
Did something rather stupid, I did dd if=%path to cyanogen mod% of=/dev/block/vold/179:0, believing that it should write to my uSD card, but it written the internal memory instead. Fixed this by booting into Nookie-Froyo, fdisked the partition, and boot to clockworkmod again to restore the whole thing. Now I lack the ROM partition in /dev/block/mmcblk0p2. Is there a guide somewhere or tool to rebuild that partition?
Click to expand...
Click to collapse
You need to re create DeviceID, MACAddress and SerialNumber under devconf/ in mmcblk0p2 (FAT).
DeviceID (I used "BNRV200", not sure if it is correct).
MACAddress (I used "11:22:33:44:55:66", not sure if it is correct).
SerialNumber (It is under the SD card door)

...and how can I do that? Which program can I use? I think this'll save me, considering my Nook is unregisterable for some reason...

Try with ADB + CWR uSD card
Boot with CWR card with NC connected to USB.
do adb shell:
# mkdir /rom
# mount /dev/block/mmcblk0p2 /rom
# ls /rom/devconf
# mkdir /bkp
# mount /dev/block/mmcblk0p3 /bkp
# ls /bkp
and pos what you see.
after that:
# umount /rom /bkp
Turn it off.

Take out your SD card then try to boot, sounds like cwm is running off you SD
Sent from my HTC_A510c using XDA App

bigsheep123 said:
Try with ADB + CWR uSD card
Boot with CWR card with NC connected to USB.
do adb shell:
# mkdir /rom
# mount /dev/block/mmcblk0p2 /rom
# ls /rom/devconf
# mkdir /bkp
# mount /dev/block/mmcblk0p3 /bkp
# ls /bkp
and pos what you see.
after that:
# umount /rom /bkp
Turn it off.
Click to expand...
Click to collapse
I think recreating the information within the Nook Color's memory would solve all my problems, since without registration, the Nook stock refuses to update. I tried updating through regular means, but the Stock refuses to take any update or any CWM-flashed ROM.
Android311 said:
Take out your SD card then try to boot, sounds like cwm is running off you SD
Sent from my HTC_A510c using XDA App
Click to expand...
Click to collapse
I do, and then the screen just goes black after the initial boot up.

neoage said:
I think recreating the information within the Nook Color's memory would solve all my problems, since without registration, the Nook stock refuses to update. I tried updating through regular means, but the Stock refuses to take any update or any CWM-flashed ROM.
I do, and then the screen just goes black after the initial boot up.
Click to expand...
Click to collapse
These steps are not flashing with CWM, they are just entering to clockwork recovery system wich allow you access to NC's internal memory.
You need to create three files:
/rom/devconf/DeviceID
/rom/devconf/MACAddress
/rom/devconf/SerialNumber
and fill them with your NC's info...
I dont know exactly wich data must be in those files...
EDIT:
With these files I can run CM7 but not sure for NC stock...

I'll try anything, even if it's random gibberish. I need my Nook back.

neoage said:
I'll try anything, even if it's random gibberish. I need my Nook back.
Click to expand...
Click to collapse
I found a complete list of files you need (maybe, maybe not)...
Archive: rombackup.zip
Length Date Time Name
--------- ---------- ----- ----
rom/devconf/BootCnt
rom/devconf/DeviceID
rom/devconf/MainboardSN
rom/devconf/WiFiBackupCalibration
rom/devconf/MACAddress
rom/devconf/ProductID
rom/devconf/Backlight
rom/devconf/EventType
rom/devconf/DeviceAttribute
rom/devconf/Platform
rom/devconf/DateManufactured
rom/devconf/PublicKey
rom/devconf/HashOfPrivateKey
rom/devconf/ean
rom/devconf/ModelNumber
rom/devconf/SerialNumber
rom/devconf/BootCount
--------- -------
957 17 files
I only want to know their format...

The question is, how can I access these files to edit them? What program can I use to see them? It's possible that if I can see them, I can extract them, edit them, then inject them into the Nook. There has to be a way around the missing addresses and numbers...

neoage said:
The question is, how can I access these files to edit them? What program can I use to see them? It's possible that if I can see them, I can extract them, edit them, then inject them into the Nook. There has to be a way around the missing addresses and numbers...
Click to expand...
Click to collapse
I need that file too.
I just want it as a sample because these files are different for each nook.
How did you lost those files?
If you didnt repartitioned your nook you can look here.
You can access them with CWR + ADB.

I keep giving this advice, I feel like a broken record. Oh well, at least it can be helpful...
Do a hard reboot and take your nook directly back to stocking condition. Hold down power,n, and the volume keys all at the same time for ~10 seconds until the nook turns off. It will flash, and reboot, when it begins to load (if you still have the cyanogen screen, as soon as it appears) hold down all the same buttons again until it goes off again. Do this 8 times total. On the final reboot, the nook will load into froyo, go through the normal B&N registration process and then in settings of the nook OS, erase and dereguster device to complete the wipe. That will send it back to stock.
I have seen this fix anything from a black screen to a completely erased system directory. Give it a shot.

mateorod said:
I keep giving this advice, I feel like a broken record. Oh well, at least it can be helpful...
Do a hard reboot and take your nook directly back to stocking condition. Hold down power,n, and the volume keys all at the same time for ~10 seconds until the nook turns off. It will flash, and reboot, when it begins to load (if you still have the cyanogen screen, as soon as it appears) hold down all the same buttons again until it goes off again. Do this 8 times total. On the final reboot, the nook will load into froyo, go through the normal B&N registration process and then in settings of the nook OS, erase and dereguster device to complete the wipe. That will send it back to stock.
I have seen this fix anything from a black screen to a completely erased system directory. Give it a shot.
Click to expand...
Click to collapse
Thanks. But this method only work if you have third partition (factory) intact.
And all I need is a file located at that partition wich I dont have :S

on my first attempt to put cm7.1 on my emmc using cwm I had the same or a very similar thing happen to me.
I somehow ended up with a bad boot partition. I followed a thread on here that had to do with "reformat and a repartition", (cant find it right now) but downloaded and installed these zips through a cwm card then installed an update for b&n 1.4 zip (I was running 1.3 ) but it worked allowing me to go to stock.
Then I tried it again only this time when I first booted to cwm on the main menu I hit wipe data/factory reset then installed zips and all is well.
*forum.xda-developers.com/showpost.php?p=14101197&postcount=1

I Think the file he's talking about is "E_Recovery". When I tried to register the Nook, I got a message that said that this file was missing...

[Q] Why can I not delete my /sdcard/clockworkmod folder?

So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.

Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7

BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..

I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.

erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?

I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app

Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.

[USER Tips] HD/HD+ Stock Root User Tips from LeapinLar

When I originally bought the Nook HD+, I made several futile attempts to get ADB working so I could sideload apps to it. I was so frustrated that I was ready to give up and return it. But I finally got it going and with the help of a few smart users here was able to get it rooted and installing apps directly on the device. So, to save some other users the same frustration I had, I thought I would outline what I did to make this device hum.
Update 12/27/2012: A lot has changed since I first created this tips thread. I am updating it to the latest information. Most of the steps below are not necessary anymore since I now have a new thread here which lets you do these things easily with a special version of ClockworkMod (CWM) recovery for the HD and HDplus. And the text here has been modified to reflect that and include the HD.
Update 11/02/2013: Since B&N has included the gapps and Play Store in version 2.1.0 and above and since verygreen developed the new boot.img that removes B&N /system file protection scheme and I updated my HD/HD+ CWM thread to account for those changes, I decided to give this thread an update. I have added comments to the sections in italics below where necessary
If you have questions or comments on this post, reply to this thread. Please do not send me private messages or emails. By posting in the forums others get a chance to help you and if I answer your question in the forum, others can see my response and it may help them too.
1. Setting up ADB
ADB is very useful for many things but you do NOT need ADB to root anymore. Look at my thread referenced above to use CWM to root.
Also, rather than use ADB via USB, it is much easier to use a Wireless ADB app available in the Play Store.
If you want to know how to set up ADB with USB, click on the "show content" button below.
The first thing you need to do is get ADB working on your PC so that it can connect with the HD+. The instructions to do that is on B&N's own site here. (But you really don't have to do all that, see below). To make it easier for XDA users, I have attached to this post the drivers downloaded from B&N site. Download and unzip that file to your PC.
To install the drivers, do the following (I tested this on Windows XP and Windows 7):
1. On your HD+ go to settings, device information, developer options, and make sure check "Enable ADB" is not checked.
2. Plug in the device to the PC with the USB cable. MTP should install.
3. Unplug the device, go to settings again and check 'Enable ADB'. Plug back in.
4. New devices will try to install. When they do, work your way through the options until you get to the choice "include this location in search" (the terminology is a little different in Win7) and browse to the location you unzipped the driver files above. Continue and the driver should install. In Windows 7 just one device will pop up. On Windows XP, two may. (Edit: If you are having trouble with this step, go to the B&N link I have above and read and follow section 4.6 of that guide. You can skip section 4.6.2 since you unzipped those drivers earlier. But do all of the remaining steps in section 4.6).
5. An "Android Composite ADB Interface" will install. If the computer says it needs to reboot to finish. Do it.
6. If, when it starts back up, and after installing ADB below, it does not work, you may need to go the Device Manager and look to see if "Android Composite ADB Interface" device has a yellow exclamation point by it. If it does, update the driver with the B&N driver again.
7. Create a file named adb_usb.ini and put 0x2080 in it with no line feed or carriage return. Go to \documents and settings\ and open your users folder and create a folder named .android and put that file in it.
8. I have attached a file named adb.rar below. Just unrar the adb.rar file. There will be three files there that you can put in a directory (any name you want).
9. Open a command prompt and cd to wherever you copied those adb files. If you set your path to that directory, you can have the prompt set for any directory, like where your apks are stored. Type 'adb devices'. It should go through some commands ending with a list of devices connected. The serial number of your HD+ should be listed. You can now run ADB commands.
2. Sideloading Apps
Once Unknown Sources is activated by my CWM zip above, you do not really need to install apps this way anymore.
Once you have ADB connected to your HD/HD+, it is very easy to sideload install apps. Just have your command prompt set to the location that you have your apk's stored and type "adb install xxx.apk", where xxx.apk is the name of your app. It is best to name the apk to something simple with no underlines or special characters in the name. It does not matter what you name it, the real name is inside the apk. The app should install. I would start with a launcher app since sideloaded apps cannot be seen in the stock launcher. Then I would install AnyCut which I have attached to this post. This app allows you to put the Home command on your launcher's home screen so that after you make your launcher default, you can get back to the B&N home page. There is a trick mentioned in the B&N guide referenced above that lets the stock app drawer see your sideloaded apps. On the Apps screen, hold the volume up button while you press the "Apps" word at the top of the screen for 2-3 seconds. An "Extras" screen will pop up showing all of the sideloaded apps. You have to do this every time you want to see it.
3. Rooting the HD/HD+
Rooting is now very easy using CWM in the referenced thread above. If you want to use the older manual method, click on the "show content" button below. But be warned these older methods no longer work on version 2.0.5 or newer.
Verygreen came up with the original scheme to root the HD+. But it had a problem. The HD+ checks on boot to see if /system has changed, and if it has, it will not boot. It tries this 8 times and on the last time the "8 failed boot" procedure kicks in and your device is wiped clean (including your storage space) and the factory ROM is re-installed. He later modified it to survive a reboot. Someone0 developed another scheme where he can root without modifying /system directly. So the next time it boots, it boots normally. See his thread here.
ONCE YOU HAVE ROOT, DO NOTHING THAT MODIFIES /SYSTEM OR IT WILL NOT BOOT AND END UP RESETING ITSELF. Also do not install anything that installs to /system, like busybox, AdFree and a few other apps. Ignore this warning with Universal Root rev3 or higher.
4. Setting OTA (Over the Air) Updates from B&N to Manual
When you first register the HD/HD+ it will automatically update itself to the latest version. To protect yourself against further updates that might jeopardize your ability to root or add other mods, you should try to block further automatic updates. But it seems that making this mod is no longer effective, B&N updates anyway.
Again, I have a CWM zip that will do this for you in the referenced thread above. If you want to see how to do it manually, click on the "show content" button below.
EDIT: (2/22/13) I have a new way to block OTA that seems to work so far. Another user (thanks greenya!) discovered this and I have come up with a way to implement it. I use the app AdAway to put my own black list of sites to not allow access to. If you want to try this, you must be rooted. Get AdAway either on the 1mobile.com market or at its developer's site (http://code.google.com/p/ad-away/). Before you do anything go to its preferences and change the target hosts file to /data/data/hosts. That way it will not reset the device. Then go to "Your Lists". Add this site to the black list: su.barnesandnoble.com. Then go to the main menu and select "Download files and apply ad blocking". It will ask you if you want to add a symlink, say yes. (If you installed the new boot.img from verygreen or flashed my latest version of Universal Root (rev3 or higher), you do not need to worry about adaway resetting your device. Just install it normally.)
It does not seem to block any B&N shopping or downloading apps or books. I installed this on my 2.0.5 and purposely tried to update and it says it needs the update but pushing download does nothing. Then I unblocked it and pushed download and it started to download immediately. So it does work.
Basically the same method used on the Nook Color and Nook Tablet should work on the HD+. It requires that you edit a database file and that requires root access. I use the paid Speed Software's SQLite Editor. You need to use the latest version (2.0.1). I could not get my older version to get root access.
So here is a description on how to do it with SQLite Editor. Open the app and it should get granted superuser access. Then browse with it to /data/data/com.bn.devicemanager/databases. There should be a file there named "devicemanager.db". Open that with SQLite Editor. There should be a list down the left side, one being "registry". Click on that. A table opens up that looks like a spread sheet. On line 6 is com.bn.device.fota.mode. Scroll across till you see the value column. It should say auto. Edit that to manual. Save the database and you are done.
This worked on the other Nooks, so should work here. See the post below for another automatic method.
5. Setting Up Installing from Unknown Sources
I also have a CWM zip that will do this for you in the referenced thread above. If you want to see how to do it manually, click on the "show content" button below.
You can toggle the unknown sources using the same method as I used for blocking OTA. Just look for the database in /data/data/com.android.providers.settings/databases. The database is settings.db. Open secure and line 4 - install_non_market_apps and change the value to 1.
6. Setting up Google Play Store and Google Apps
I also have a CWM zip that will do this for you in the referenced thread above. If you want to see how to do it manually, click on the "show content" button below. If you have stock version 2.1.0 or higher you do not need to flash my zip. Play store is included in the ROM.
Someone0 has a post on how to add Google Play Store is here. And he now has it so you can install the entire Gapps package, including Play Store. Again, you must be rooted first.
7. Setting LCD Density
If you are like me, you hate the tiny fonts on these high resolution devices. You can change the default lcd density to help with that. The default lcd density for the HD/HD+ is 240. I changed it to 300 and everything works fine on the HD+ and fonts are a little larger. But you cannot modify build.prop on /system to do that. It will cause the device to reset itself since you are modifying /system. To get around that, create a file in /data named local.prop. Add the following line to that text file:
qemu.sf.lcd_density=300
Then reboot and your new density is set. You need to be rooted to do this on the device.
I found that changing the density on the HD made the SystemUI app crash. If you want larger fonts for the HD, I recommend you use the tip in the next section.
8. Larger System Fonts
If you don't want to set your LCD density higher but you still want larger fonts, a user (Windsor1959) just passed on this tip. Go to the B&N app store and install the free app Go Read. Once that is installed, open it and use the menu to go to accessibility settings. There is an option for larger system fonts. It works great. Thanks Windsor1959.
I also just discovered that there is another hidden setting that lets you set the system fonts from small, normal, large and huge. To get to these settings you need a third party launcher like zeam or adw and the AnyCut app I attached below. On the launcher screen long press and select shortcut. Select AnyCut from the list. Within AnyCut select activity and scroll down to fonts. Select that and a fonts shortcut will appear on the launcher screen. Open that and you can select the font size.
9. Data structures on the HD/HD+
For those of you used to having two separate partitions for data and media files, B&N has used a different scheme for the HD/HD+. They make one very large /data partition ranging from 5GB to 28GB depending on which device you have. Then they create a folder in /data (/data/media) and, using the sdcard fuse feature, link it permanently to /sdcard. So that means it is one big dynamic space for both /data and /sdcard, sharing the free space. /data is considered root and /sdcard is not.
They named it /sdcard because a lot of third party apps expect there to be an sdcard on the system and won't run unless there is one. That creates a little bit of a terminology problem for us Nook Color users. We are used to having /sdcard be an external SD. And on top of that, if we do add an external SD, it is mounted as /ext_sdcard under /mnt and that is hard for some apps to see. And when you connect your device to your PC with MTP, internal media (sdcard) is called 'internal memory' and the SD (ext_sdcard) is called 'SD card'. I think B&N did this with the expectation that users would not be rooted and be able to see that stuff under the hood.
Since sdcard is really just a part of /data, it is formatted as ext4 instead of FAT32 like the Nook Color media partition was. That means you can store a single file larger than 4GB, which is the limit for FAT32. Most external SD cards are formatted FAT32 so they are also limited to a single file size of 4GB. But it makes them directly readable by your Windows based PC. When you first put a new external SD in the HD/HD+, it asks you if you want to reformat it so you can more easily store your media files. If you say yes, it will format it to ExFAT, a new flash drive format that supports larger file sizes. That's good for your media files since you can have very large files on it. But it could be bad if you want to take the card out and put it in your Windows XP PC because XP cannot read it without an update patch from Microsoft. If you have Vista or higher, ExFAT can be read natively.
When you do a factory reset (clear /data) your media directory (/sdcard) is wiped out too.
Also, the B&N media, books, magazines, etc., are stored in /data/nookmedia, which is root.
10. White on White Text for Some Apps
One of the annoying issues with using some third party apps is the HD/HD+ displays some dialogue boxes with white text on a white background so that the text is unreadable. Someone0 and I developed a patch that can repair this. I have a zip in my CWM thread referenced above to repair the HD+ and HD. (Also since stock version 2.1.0, B&N has dramatically changed the color scheme so that the white-on-white issue is no longer the problem it used to be, I have discontinued providing white-on-white mods for version 2.1.0 and above.) If you want to see how to do it manually, click on the "show content" button below.
Someone0 and I have been working on this and have found a solution. It requires a modification to the framework-res.apk on /system. And the mod works very well. The problem is that the apk is on /system and must be symlinked using our symlink trick we use on /system files when we need to modify them. That is easy to do, but this particular apk is very critical to your system. If you do not get it installed properly, it will lock up the device and you either need to reset it completely or repair with ADB.
If you are tech savvy enough you could modify your own apk and install it. In the colors.xml file in the values section of the de-compiled apk, are two settings that need to be changed, "background_light" and "background_holo_light" need to be changed to "ffcfcfcf". The color choice was a compromise between making the text dark enough to be seen against a white background and bright enough to make things like menus show in the grey backgrounds. Re-compile and put the apk in /data, delete the apk in /system and symlink to the one in /data. The problem with doing it manually while running is as soon as you delete the apk, things go bonkers. And you cannot add the new symlink until the original apk is deleted. If you start messing with this mod, be sure to have ADB enabled so if it locks up and gets stuck on booting, you can access things with ADB and hopefully repair it. When I did my system manually, I copied the modded apk to /data with root explorer, used root explorer to set /system to read/write, then used ADB to delete the apk in /system and create the symlink. If you mess up, it will boot, but get stuck at the 99% level. Hopefully if you left ADB enabled, you can use ADB to repair whatever is wrong.
11. Implementing Userinit.d
Userinit.d can be used to run specialized scripts as part of the boot process. The HD/HD+ does not implement userinit.d, but it can be modified to allow it. And these scripts can be used to customize the performance of the device, like modify fonts, change colors, add symbolic links, modify drives, set CPU speeds and tweaks, etc.
I have implemented userinit.d in the new Universal Root zip in my referenced CWM thread above. (The latest version no longer uses it).
The scripts are usually named with numbers at the beginning and no extension. Examples would be the scripts from CM7 init.d which are: 00banner, 01sysctl, 03firstboot, 05mountsd and others. They are executed in the order of the numbers. They are plain text files that have as the first line:
#!/system/bin/sh
Then they have script commands in text format.
The beauty of these scripts on the HD/HD+ is you put them in /data instead of /system which would reset your device. Put the script files in a new folder named /data/local/userinit.d. Set the script file permissions to execute.
There are examples of userinit.d scripts out there if you search for init.d scripts on XDA or the web. Some will work on the HD/HD+ and some won't. I have a great example in the next section.
12. Swapping "sdcard" and "ext_sdcard"
I now also have this modification as a flashable zip in my CWM thread linked above. No need for root with that one.
As explained in section 9 above, the internal media is named "sdcard" so that apps can store their files there. Some users would like them stored on their external SD. I have a userinit script that will swap "sdcard" and "ext_sdcard" so that apps will store their files on the external SD. The external SD will show as "sdcard" and the internal media will show as "ext_sdcard". And it shows swapped using MTP also. It can be a little confusing since we cannot control the names, but they are swapped. If you don't have an external SD plugged in, both sdcard and ext_sdcard will show the internal media.
To swap the drives, make sure userint.d is implemented, then download the attached file, 11SDswap.rar, and extract it and put the file in /data/local/userinit.d. Set the permissions of the file to execute in all three boxes. On the next reboot, they will be swapped. To return to normal, just remove the file and reboot.
13. Skipping OOBE (Out of Box Experience)
Skipping OOBE is when you want to skip the registration step when you first start your device or after a reset. Not registering means that you will not be able to buy books or apps from B&N or, if you already have an account, have access to already purchased items. Your name will show as TEST (which can't be changed). And, if you set up wifi, the device will still check for updates and if found, update.
So if you don't want to register, or that device is already registered to someone else and you can't, just skip OOBE. There are instructions for the Nook Color here. They still work for the HD/HD+.
14. Back Up Your Stock ROM Installation with CWM v6.0.2.8 for Nook HDplus and v6.0.2.7 for the HD
Now you can backup your stock installation with my bootable CWM (ClockworkMod) recovery SDs. That way you can restore if you make a mistake and change /system so the device starts to reset itself. Just catch it before the reset completes, insert the card and restore and you will be back to OK.
You can do anything with these CWM SDs you normally would do with CWM, (nandroid backup, wipe system, data, cache, dalvik-cache, fix permissions, etc).
One of the nice features is you can wipe /data without it wiping your internal media at /data/media. So, if you want to reset, just wipe /data and your media files are still left intact. And when you do a nandroid backup, it can be placed either on internal media or your external card. The nandroid backup feature backs up /boot, /system, /cache and /data (without the media folder). So if you want the media folder backed up you must do it manually from within stock. And when you restore, you can selectively restore any partition. So if you mess up /system by putting something there that causes a reset, just selectively restore /system.
EDIT (5/22/13) - There is a new procedure brought to my attention by another user (thanks fanoush) which lets you make the CWM SD without burning the image. It seems the OMAP4 devices are a little more liberal on the booting requirements than previous OMAP devices. This makes it easier to install on any size SD. Go to my HD/HD+ CWM thread linked in my signature and look at item 1a. There are instructions and files there.
The versions attached below are under 120 MB so they can be put on any size SD. It burns very quickly. But there is no room there for any backups. After burning the SD you can use partitioning software (like Mini-Tool Partition Wizard or EaseUS Partition Manager, both free) to expand it to the full size of your SD card if you want so there would be plenty of room for backups. But be sure to only expand the back end of the partition, being careful not to touch the beginning.
I also now have a 4GB versions for both the HD and HDplus attached to the CWM thread referenced above.
To make the SD, download the version for your device and extract the file. It should be a 120MB .img file. Burn (write) that image file to your SD card using Win32diskimager in Windows. In Linux or OSX (Mac) use the "dd" command.
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). With the small version it should burn fairly rapidly. If you get an error message about access denied, it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
Insert the SD into your powered off Nook HD/HD+ and power on. It should boot to CWM with the label v6.0.2.8 for HD+ stock. The HD version just says v6.0.2.7 for Stock. You can tell it is booting properly if the cyanoboot logo shows up after the Nook logo shows for a few seconds. If the Nook logo stays there and starts changing, it means it is booting to stock. Hard power off by holding the power button for several seconds. Try again.
Manipulate the controls with volume up/down for cursor, n key to activate and power key for back.
15. Modifying System Files on the HD/HD+
Ordinarily you cannot modify system files on these devices because they will detect the change and reset themselves back to factory stock, wiping out all your data at the same time. But there is a safe way to do it if you are rooted.
If you have installed my new Universal Root rev3 or higher or installed verygreen's boot.img, the below procedure is no longer necessary, just modify the files directly.
The HD/HD+ has a manifest file included in the boot files that has a listing of each file that is supposed to be in /system and a checksum of each file. On boot, it reads the files in /system and makes sure each file that is there is on the list and matches the checksum. It ignores directories, symlinks and missing files. If one is added or has the wrong checksum, it stops and tries to boot again. If it reboots 8 times in a row without completing the boot, the automatic reset feature kicks in and your device is formatted and the factory ROM is reinstalled.
So you can see that missing files are OK and symlinks are OK. So if you want to modify a system file, first copy it to /data somewhere, delete the original, and make a symlink in /system to replace the deleted file. The symlink points to the file copied to /data. But be careful, some files, like framework-res.apk, are being used all the time and if you delete it, even temporarily, the system goes crazy.
The scheme that someone0 and I use is to mimic /system under /data/su so that the structures are the same to avoid confusion. For example, if you wanted to modify build.prop, it would be copied to /data/su/system/build.prop and the symlink would point there. Since build.prop is not used very often, it is safe to now modify it however you want. But be careful, some settings there are vital, like hardware rotation. Mess with that and things will go all wonky on the next reboot.
Here are the specific commands to make this happen using build.prop as an example:
1. Use your root file manager to copy /system/build.prop to /data/su/system/build.prop. Set the file's permissions to match the original.
2. Delete /system/build.prop also using your root file manager
3. Set up Terminal Emulator. Start the program and type su enter. After you allow superuser access, the prompt turns to #
4. Type the following command at the # prompt (without the quotes):
"mount -o remount,rw /system"
5. Then this command:
"ln -s /data/su/system/build.prop /system/build.prop"
(That first letter is a lower case L)
6. Then this command:
"mount -o remount,ro /system"
You are done. You can now modify build.prop in /data any way you want and the system will not reset.
But before you do this mod or any other system file mod, I recommend you have backed up your system using CWM as described in the previous section. That way if you did not get it right somehow and it starts to reset, you can insert your CWM card to stop the rebooting and selectively restore /system and try again.
One side benefit of doing this build.prop mod is if B&N tries to update you in the future, it will fail because it cannot verify your build.prop because it is missing. And, in my experience, it does not try again.
16. Nook HD/HD+ internal partition structure and backups
The partition structure for the HD/HD+ is the same and is as follows:
Code:
P# Name Size Type
1 xloader 128K Fastboot Image
2 bootloader 256K Fastboot Image
3 recovery 15MB Fastboot Image
4 boot 16MB Fastboot Image
5 rom 48MB vfat
6 bootdata 48MB vfat
7 factory 448MB ext4
8 system 672MB ext4
9 cache 464MB ext4
10 data varies ext4
There is a simple process to make image backups of your internal partitions. Most people will never have to use the backups, but there is one critical partition that holds vital device specific information that was created at manufacture that is probably wise for you to back up. The process requires that you have either Terminal Emulator installed or ADB set up. And it can be done either in rooted stock or CM10/CM10.1. In Terminal Emulator or ADB Shell in superuser mode, type the following command:
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/factory.img
This will make an image of your partition 7 that has that vital information. It also has a copy of the factory.zip file used to reset your device should you need to. If you want to back up the rest of your partitions, just change the p# and file name in the above commands to match the listing above. Partition 10 is quite large so should not be backed up using this method.
To restore a partition, just reverse the information following the if= and of= statements in the command. The information stored in partitions 1, 2, 3, 4, and 8 is specific to the ROM version you were running when you made the backup, so restoring them to another version is probably not a good idea (and if you do, restore all 5 of them together). Only do it if it is a last resort. And of course you should not restore HD partitions to the HD+ and vice versa.

Enable Unknown Sources and Blocking Auto OTA made easy (updated 12/3)
Instead of making a new thread, I have decide to make the tips that already available, but hard to use and make it simple.
So, what is it? This little thing will set Enable install from Unknown Sources and change the auto update to manual update for Nook HD ROM. I keep hearing how people are saying they have hard time making these changes so, I make it pretty dead simple. It's as simple as I can make. If you are looking at the timeline, root first, then this, and then gapps after. I now make them all so simple that it take me like 15mins to do all those 3 things from scratch. Originally I grab the sqlite3 from one of the app, which I guess I shouldn't have. Now I replace it w/ the one from CM9, which I guess is okay. And smaller size too.
If you were using verygreen version of root, try running this first.
Code:
adb shell su -c "/data/su/busybox chown shell.shell /data/su"
Pre-Requisite:
ADB and root.
NEW Instruction:
download the settings_new.zip in the attachment and save it somewhere.
unzip it.
run install.bat (for windows)
OLD Instructions:
download the settings_old.zip in the attachment and save it somewhere.
unzip it.
run install.bat (it basically just upload settings.sh and sqlite3 and change their permission, if you are on linux just do that instead)
adb shell
su
/data/su/settings.sh
*** OLD TEXT ***
While it's true that we should put heavy emphasis on not touching /system and that is not just manual works, but also any app with root access. You could be installing something like busybox via goole play store and screw everything up. That said, we are not touching /system at the moment because we lack the knowledge of that the nook is doing during boot process. I have been able to get asomething like AdAway to work which actually creating a sym link from /system/etc/hosts to /data/data/hosts file. I been doing this under the assumption that mounting and sym link are ok in the /system. But I would be worried too if there is a lot of those.
Click to expand...
Click to collapse

Lost and Confused
I tried following the instructions on the B&N’s website, but I do not see ‘Android Composite ADB Interface’ or even ‘Android Phone’ within the Device Manager of Windows. I now have ‘BNTV600’ and ‘NOOK’ under Device Manager/Portable Devices. I think this is for the big leagues and I may mess something up. Probably going to wait until there is a YouTube video guide showing step by step on how to successfully root the Nook HD+.
Many thanks to ‘leapinlar’ for the help.

cybersonic_ca said:
I tried following the instructions on the B&N’s website, but I do not see ‘Android Composite ADB Interface’ or even ‘Android Phone’ within the Device Manager of Windows. I now have ‘BNTV600’ and ‘NOOK’ under Device Manager/Portable Devices. I think this is for the big leagues and I may mess something up. Probably going to wait until there is a YouTube video guide showing step by step on how to successfully root the Nook HD+.
Many thanks to ‘leapinlar’ for the help.
Click to expand...
Click to collapse
If you read my description above, it says to update the driver for BNTV600.

No longer able to access internal & external memory on the Nook
leapinlar said:
If you read my description above, it says to update the driver for BNTV600.
Click to expand...
Click to collapse
This is what I did:
1. Plugged my Nook HD+ to my computer (ADB enabled)
2. Device Manager / BNTV600 / Update Driver Software / Browse my computer for driver software / Usb_driver_r04-windows folder / OK
3. Clicked on ‘Let me pick from a list of device drivers on my computer’
4. MTP USB Device appeared so I clicked on ‘Have Disk’
5. Browsed ‘android_winsub’ and clicked Open and OK
6. Android Composite ADB Interface appeared so I clicked ‘Next’
7. Message, ‘Windows can’t verify the publisher of this driver software’
8. Install this driver software anyway
9. Rebooted my computer
10. When the Nook is connected to the computer (ADB not enabled)
a. The Nook shows up as a G: drive and ‘MyNOOK Setup’ is the only file in it
b. Clicking on the ‘MyNOOK Setup’ brings me to a message:
• Welcome to MyNOOK Setup.
• MyNOOK Setup is a one-time installation that will allow you to tranfer your personal files to your NOOK.
• Transferable files include, but are not limited to: photos, music, videos, EPUB, PDF and Microsoft Office files.
• Note: Copyright protected files are not transferable
• To install, go to .... can't post link since im a noob
• For more information, visit ..... can't post link since im a noob
c. MyNOOKSetup.dmg appears when I click on the first link
11. When the Nook is connected to the computer (ADB enabled)
a. AutoPlay ‘BNTV600’ constantly appears.
12. I cannot access the internal or external memory on the Nook for both #10 & #11,
13. Running ‘makeroot.bat’ in the cmd for both #10 & #11 does not work either.
14. Device Manager / NOOK (BNTV600 no longer exist)

Follow my instructions to install the drivers and use my driver file from my first post. Go to device manager and delete any those three drivers you installed earlier, composite, mtp, etc. Then just do the bntv600.
Sent from my Nook HD+ using Tapatalk

Cool but....
...I am having a slight problem. I can not download your attached file usb_driver_r04-windows-Modded-for-HD.zip :/ everytime I do my computer which is running windows xp is telling me there is nothing there. Can you please help me thank you

Possible driver conflict with Samsung Galaxy Tab 7 Plus
leapinlar said:
Follow my instructions to install the drivers and use my driver file from my first post. Go to device manager and delete any those three drivers you installed earlier, composite, mtp, etc. Then just do the bntv600.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I followed your instructions and I successfully installed the driver you provided in your zip but the following actions occur after computer reboots.
When ADB is disabled
• NOOK (G Drive appears in My Computer
When ADB is enabled
• NO NOOK (G Drive in My Computer
• BNTV600 AutoPlay windows constantly pops up
I forgot to say that I have a Samsung Galaxy Tab 7 Plus installed in this computer. The following items are what I see in Device Manager:
• Portable Devices / NOOK
• SAMSUNG Android Phone / Android Composite ADB Interface
I tried deleting all the drivers and repeat your instructions but the SAMSUNG Android Phone / Android Composite ADB Interface keeps appearing.

Dopey32 said:
...I am having a slight problem. I can not download your attached file usb_driver_r04-windows-Modded-for-HD.zip :/ everytime I do my computer which is running windows xp is telling me there is nothing there. Can you please help me thank you
Click to expand...
Click to collapse
I don't know what to tell you. I just tried again with windows XP and it downloaded fine. Just keep trying. And watch where windows puts it.

cybersonic_ca said:
I followed your instructions and I successfully installed the driver you provided in your zip but the following actions occur after computer reboots.
When ADB is disabled
•NOOK (G Drive appears in My Computer
When ADB is enabled
•NO NOOK (G Drive in My Computer
•BNTV600 AutoPlay windows constantly pops up
Click to expand...
Click to collapse
I experienced a lot of the same symptoms.
The Nook G: is for Mac users that do not have MTP. It is so they can get the drivers they need. Notice the .dmsg (sp ?) is for them. That will only go away when you get MTP working or switch to enabled adb.
I was most concerned with getting the adb interface working, so I just ignored the MTP issues until later. In fact I temporarily disabled it so it would not keep popping up during adb.
After I got everything sideloaded and rooted, I tackled the MTP issue. With adb unchecked, I went to USB devices and uninstalled the USB mass storage device (which was the Nook G). Then it recognized MTP.
Sent from my Nook HD+ using Tapatalk

I think it's safe to say that what we(me and other who got all the stuff out seperately) did so far aren't anything very dangerous. We havn't touch any other partition or boot loader. Unless you mess them up yourself since now you have root, then the worst it could happen is a full factory reset or you can force yourself to factory reset it.

okay got a little farther
I have installed the drivers and my nook is having the same symptoms as cybersonic_ca. Now I am trying to figure out how to utilize the command prompt, i type in adb devices and it responds with 'adb' is not recognized as an internal or external command, operable program or batch file.
please help, i am trying to root my nook and HD+ but i feel i must be forgetting something. I am sorry if i am very bothersome but i can not figure out what is going on

All these tips also help with the HD. Thanks so much!
Sent from my Nook HD using xda premium

Dopey32 said:
I have installed the drivers and my nook is having the same symptoms as cybersonic_ca. Now I am trying to figure out how to utilize the command prompt, i type in adb devices and it responds with 'adb' is not recognized as an internal or external command, operable program or batch file.
please help, i am trying to root my nook and HD+ but i feel i must be forgetting something. I am sorry if i am very bothersome but i can not figure out what is going on
Click to expand...
Click to collapse
Then you have either not installed the Android SDK (Software Development Kit) on your PC (which includes adb) per the B&N instructions or your path variable is not set to include where you installed it.
Sent from my Nook HD+ using Tapatalk

Dopey32 said:
I have installed the drivers and my nook is having the same symptoms as cybersonic_ca. Now I am trying to figure out how to utilize the command prompt, i type in adb devices and it responds with 'adb' is not recognized as an internal or external command, operable program or batch file.
please help, i am trying to root my nook and HD+ but i feel i must be forgetting something. I am sorry if i am very bothersome but i can not figure out what is going on
Click to expand...
Click to collapse
if you can't follow or understand the instructions about adding the path to adb in the environment path you can always just cd "/to the directory adb is installed/" and run adb directly from there. easy way is to just drag the folder into the command prompt window. it'll save a bit of typing - only works if you're not running cmd as admin.

You said you modded the drivers from B&N? What did you change? Just curious...

So, instead of making another thread, since this is a tips thread, I'll just post it here.
Just in case you are not familiar with a factory reset on the Nook HD+, there are two kind of factory resets. The one that you perform yourself, which is actually not a full factory reset and the one that Nook get pissed and do the full one.
A factory reset that you perform yourself, whether from the GUI or button combination will basically clean the partition /data while a full blown one will basically restore other partition such as /system.
Why do I bring this up, because as we know, we are not perfect. I make mistake and so do other. Sometime instead of trying to re-trace the step and fix our mistake, it's easier to just reset everything. Well, since we can't just do a full blown factory reset our self, at least not very easy, we can at least force the Nook to do it for us.
So, if you felt like I did something wrong, and I don't know which step to take next, I make a little tool for you to start over. You can see the attachment, reset.zip in there, there are 3 files. You only have to run reset.bat if you need a linux version, maybe you can beg the OP to do it for you. If you exam the package, you can see that this is very similar to the original root method which force itself to factory reset, so this is basically a modified version of that. Obviously you still required ADB. Well, on the other hand, if you never get ADB working in the first place, you probably can't mess up that bad that you need this tool in the first place.
Let me make it clear, this tool WILL RESET EVERYTHING. It also REBOOT MANY TIMES. And expect the whole process to take about 10 minutes.

dbh369 said:
You said you modded the drivers from B&N? What did you change? Just curious...
Click to expand...
Click to collapse
I actually modified a generic driver by putting the Nook HD+ device id in it. I was not able to download the B&N driver so I don't know if it needed modifying or not.
Sent from my Nook HD+ using Tapatalk

cybersonic_ca said:
I followed your instructions and I successfully installed the driver you provided in your zip but the following actions occur after computer reboots.
When ADB is disabled
• NOOK (G Drive appears in My Computer
When ADB is enabled
• NO NOOK (G Drive in My Computer
• BNTV600 AutoPlay windows constantly pops up
I forgot to say that I have a Samsung Galaxy Tab 7 Plus installed in this computer. The following items are what I see in Device Manager:
• Portable Devices / NOOK
• SAMSUNG Android Phone / Android Composite ADB Interface
I tried deleting all the drivers and repeat your instructions but the SAMSUNG Android Phone / Android Composite ADB Interface keeps appearing.
Click to expand...
Click to collapse
I am having the same problem as Cybersonc_ca. I did everything according to the nook developer website and when I enable ADB on my nook hd+, it does not show my BNTV600 under portable devices but I DO have Android Phone >> Android Composite ADB Interface.
If I go to command prompt, how can I make it so that it checks that folder as well?
I apologize for such noob questions. Thank you.

sayw0rd said:
I am having the same problem as Cybersonc_ca. I did everything according to the nook developer website and when I enable ADB on my nook hd+, it does not show my BNTV600 under portable devices but I DO have Android Phone >> Android Composite ADB Interface.
If I go to command prompt, how can I make it so that it checks that folder as well?
I apologize for such noob questions. Thank you.
Click to expand...
Click to collapse
Go to command prompt and type 'adb devices' and see if you have any. And the looking for bntv600 was for getting the composite to show. You have that.
Sent from my Nook HD+ using Tapatalk

Kobo Arc Development

So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)

ThunderBird2678 said:
So I was randomly flying around on Google today, and I noticed that someone had claimed to root the Kobo Arc, and gave written instructions here -- http : // www . mobileread . com / forums / showthread.php?p=2584491 (Remove the spaces, XDA won't let me post an actual link, since I don't have 10 posts yet). After running through this myself, I went on the Google Play store and used root checker. Much to my surprise, it worked, and my device now has root access. I even tested with Root Explorer, and mounted the system partition as R/W, and I can move things in and out of it. I'm currently working on trying to get a custom ROM working, but I'm worried that I will cause a brick, since Cyanogen doesn't support the Arc. (yet...)
Click to expand...
Click to collapse
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
ive attached the file but please go to that website and pay homage to whoever did this work...now to the next stop, a ROM
Device now has a working custom recovery see post 15
Sent from my Arc using xda app-developers app

dazza9075 said:
confirmed, was just going to post this but was beaten to it.
http://www.mobileread.com/forums/showthread.php?t=218928
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
i have absolutely no idea what im doing but I think I have dumped 12 partitions using
dd if=/dev/block/mmcblk0p10 of=/sdcard/p10.img
is there anyone around that fancies a challenge? im in a position where bricking this thing isn't really much of a problem so if someones up for a challenge and wants to help im willing to lend myself and the device to this

Warning : Block of Text Ahead.
dazza9075 said:
confirmed, was just going to post this but was beaten to it.
In terms of a ROM do we not need a compatible boot loader that will allow unsigned ROMs?
ive attached the file but please go to that website and pay homage to whoever did this work...now to find a man about a ROM
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Haha. As soon as I found a thread called "root the Kobo Arc" on Google, I posted it here right away. Sorry if I deprived you of the satisfaction! *troll*
Joking aside, I'm not too sure about the bootloader. I think it's pretty locked down (since I put a nexus 7's cyanogenmod onto the data partition and rebooted. It tried to updated, but said validation failed, or something of that sort). I can't install any custom recoveries either, since I have no idea how to do it in the first place, and there's none made for the Arc.
Also, I analyzed the Arc with the "Droid Examiner" App from the play store (That is a really great app, just so you know), and found that it uses a board called "zeus". The funny thing, though, is that one of Sony's Xperia phones, also has a board called "Zeus", and there's Cyanogenmod for that (albiet not the latest version). However, these two devices have nothing in common. The closest thing to an Arc that has Cyanogenmod is the Nook HD/HD+, which uses the exact same chip (OMAP TI 4470).
If someone is smart enough (not me) to analyze the Cyanogenmod files for the Nook, and see how they work, that may lead into flashing the Arc.
Anyway, I'm resetting the Arc, since I'm having weird cases where the Arc would freeze after booting it from sleep mode, and I'd have to turn it off and on again. I think that was something else I did, since it happened before the root, but neh, I might as well try this all from factory default settings.
Sorry for the block of text, guys!
P.S. Using the stock Jelly Bean boot animation on the Arc looks amazing!:laugh:

Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app

dazza9075 said:
Haha, its cool, like yourself I just happened to Google kobo arc root and for once my googe fu was up to the task and the root appeared
I've been looking at starting my own recovery mod branch but its no simple task by the looks of it, if their are similar devices we can use all their data and tweak it to ours which would help a lot!
Oh I think we have fast boot, I held vol down and pushed power on, it just sat at the kobo arc screen, I used the nexus 7 driver from the universal adb/fastboot driver I found on here and it connected up http://forum.xda-developers.com/showthread.php?t=2263822
I stumbled on some to good to be true program on Xda dev that apparently can root anything and unlock any bootloader once your in fastboot mode. I have tried that part and it said it was successful but i have no idea how to test this out yet, the program does a bunch of other stuff too, the adb stuff worked as did apk sending, and the rooting options knew i was rooted, it also has flashing functions, I'll be damed if I can find it now I'm at home though , I'll have another look.
I don't mind doing leg work but if someone can read the map it would be very helpful!
Edit, found it
http://forum.xda-developers.com/showthread.php?t=2399385
http://www.mediafire.com/?vwxpq62pa927s9c
Sent from my Arc using xda app-developers app
Click to expand...
Click to collapse
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...

ThunderBird2678 said:
Um... Okay. I've installed the drivers (I think I installed them correctly), and I booted my device using "volume down + power". I have it connected to my System, but whenever I try to use one of the options in the Android Root Toolkit, it tells me it's waiting for the device. I don't know what I did wrong, but something's clearly not working.
As far as the recovery goes, I think that looking at the Nook Tablet from TWRP would work quite nicely. It runs on a similar processor ( I believe it's a OMAP TI 4430 ), and it seems to be quite similar in specs to the Arc. If only I was a bit better at programming...
Click to expand...
Click to collapse
im usig the generic android adb driver and the bootloader driver for fast boot
im dumped all partitions and mapped them all out, see below for file system details
But again I'm blindly stabbing in the dark and most tutorials are a bit lacking in depth or not relevant to the kobo :/
Sent from my Arc using xda app-developers app

127|[email protected]:/ # blkid
/dev/block/dm-2: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-1: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/dm-0: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p4: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[email protected]:/ #

Okay, so I can't even push apps to the Arc using ADB. I think you have to boot into recovery (power + volume up). I don't know how to use the terminal at all (I'm lost, I know D: ), so I don't have that installed on the Arc. I remember being able to do ADB even with my Sony Reader (First gen, PRST1), so I'm not sure why the Arc isn't quite working. I have both drivers installed, BTW.
As for the recovery, I can't even find a method to flash it. I'm still trying everything I can, though. :\
Sent from my Arc using xda app-developers app

ive mapped out the following partitions and any info ive found about each of them, im not in a position to help at the moment, got a big day at work tomorrow, as mentioned above ive used several tools,
SuperSU,
ROM toolbox pro
busybox
remount
Below is a list of all the available partition names and numbers
/dev/block/mmcblk0p1 xloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/xloader
348KB
/dev/block/mmcblk0p2 bootloader
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootloader
1.50MB
/dev/block/mmcblk0p3 cypto
/dev/block/platform/omap/omap_hsmmc.1/by-name/crypto
Completely empty
64KB partition size
/dev/block/mmcblk0p4 EFS
Mounted as /FACTORY
/dev/block/mmcblk0p4:UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/efs /factory ext4 ro,relatime,barrier=1,data=ordered 0 0
20MB
/dev/block/mmcblk0p5 misc
/dev/block/platform/omap/omap_hsmmc.1/by-name/misc
Completely empty
128KB partition size
/dev/block/mmcblk0p6 Bootlogo
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootlogo
Contains kobo arc picture
4MB partition size
/dev/block/mmcblk0p7 Logos
/dev/block/platform/omap/omap_hsmmc.1/by-name/logos
contains the battery charge logo
28MB partition size
/dev/block/mmcblk0p8 recovery
/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as in boot
5MB of data
16MB partition size
/dev/block/mmcblk0p9 boot
/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
data contains a GZ file, when decompressed we get a 8.5MB file of unknown type, exact same as n recovery
4.5MB of data
8MB partition size
/dev/block/mmcblk0p10 CACHE
Mounted as /CACHE
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
768MB partition size
/dev/block/mmcblk0p11 SYSTEM
Mounted as /SYSTEM
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/system /system ext4
rw,relatime,barrier=1,data=ordered 0 0
910MB partition size
/dev/block/mmcblk0p12 USERDATA
Mounted as /DATA
/dev/block/mmcblk0p12: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata /data ext4
rw,nosuid,nodev,noatime,errors=panic,barrier=1,nom blk_io_submit,data=ordered 0
0
12GB partition size

Watching with interest. The root works. No frills CPU installed and working. There may be hope for this thing yet:good:

Moved to new thread and more appropriate forum - keep up the good work guys

im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.

dazza9075 said:
im not sure that's going to work you know, ive had some permission errors with adb which suggests the root isn't full, terminal on the device works fine, but adb just has some problems, adb shell and the su seems to fix them.
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
http://www.addictivetips.com/android/make-nandroid-backups-on-android-without-booting-into-recovery/
im busy today but ive found these useful
i think Clockwork Recovery should be our focus at this point or if you have dumped your partitions(?) attempt to construct a rom for later use
or this should work too
Install any Custom Recovery with flash_image:
Just like the previous method, this method also requires following advanced steps and is not recommended if the first method is working for you. flash_image is a tool for Android devices that lets you rewrite your phone’s system partitions with partition image files and installing it to your device requires ADB. If you don’t already have ADB installed, check out our guide on installing ADB. Once you have ADB installed, flash the custom recovery image as follows:
WARNING: It is very important that the recovery image that you use in this method is compatible with your device. Else it will not work and flashing it could possibly brick your device.
Download flash_image and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands: adb push c:\flash_image /sdcard/adb push c:\recovery.img /sdcard/adb shellsumount -o remount, rw /systemcp /sdcard/flash_image /system/bincd /system/binchmod 777 flash_imageflash_image recovery /sdcard/recovery.imgThis will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ thrice.
Click to expand...
Click to collapse
I've already tried that recovery method (I spent about two hours just googling), and it doesn't work with the Arc. The ADB won't let me push the image over.
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.


ThunderBird2678 said:
As for Cyanogenmod, I tried something yesterday. A person on the Mobileread forums (apparently a Kobo employee) put out an update.zip file for the Kobo Arc. The file was quite old, and it's really just the 4.1.1 update that (I hope) we're all running. He said that as long as you put it on the root of the data partition, the Arc will flash it immediately. When I tried taking a Nexus 7's Cyanogenmod file and sticking it in the same place, the Arc started flashing it, but then just said there was an error with the update. So I personally think that you do require a properly signed ROM.
However, if you open up Kobo's update.zip using Winrar, a sidebar pops up that says "signed by SignApk". I don't know too much about this, but couldn't we use this "signapk" to sign our own ROMS and flash them?
Just a thought.
Click to expand...
Click to collapse
I think there is a problem with the setup, I just flashed a CW recovery image and it worked, or didn't rather! but the concept did, transferred, flashed using adb, I had to replace it though as it was totally borked and kept restarting, apparently the touch based recovery methods can be like that, ill have some good time tomorrow night (UK time) if your about, and ill keep at it tonight if I get a chance!
copy recovery to adb location
adb push recovery.img /sdcard/
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell and type
adb reboot recovery
fixed it by holding power button and vol down to boot to fastboot recovery
then ran
fastboot flash recovery inputrecovery.img
inputrecovery being my original recovery file taken from partition 8!
ive updated the partition map on the post above with my progress, but it looks like we can flash to them my name so its probably less relevant now
oh ive ditched the drivers I was using and reinstalled the drivers from the official SDK, generic android adb for within android and android bootloader for fastboot
EDIT
Yaaas!! recovery replaced
ok, deleting or renaming /etc/install-recover.sh appears to have stopped custom recovery being changed back to stock after reboot, I used the recovery builder to make a build from partition 8, which it did without error, flashed using the above commands.
Still don't know what im doing though, but progress is progress 
ill post a link to the custom recovery ive made soon, we need to make up some fstab file listing all the mounts etc, i tried one but it must be borked as recovery couldnt see anything

ok i have a working recovery http://jenkins.cyanogenmod.com/job/recovery/35325/artifact/
its not quite done, i need to mount the sdcard, its physical location is mounted, ie /data, but its virtual mount isn't /storage/sdcard
I have asked for some help so hopefully someone can help be on this, I think it needs to be symlinked
im going to need some help soon, so if your reading this with a kobo arc, I need you! im needing a hand folks! if your stuck getting this far let me know and we can PM to get it working
oh and recovery is also now persistant by deleting or renaming /etc/install-recover.sh"

Sorted folks!
I have made a stable and thus far, a working custom recovery.
its mounting everything and backing up / restoring works as it should, unless anyone can find any issues I consider this step in building a complete ROM completed,
you must have root, download arctic.apk and install on your tablet, you will need to enable unknown sources In dev options first
you must have android and java sdk also installed, you will need to add the google usb drivers in the android sdk, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Delete or rename /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push, if you use adb push then remember to copy recovery.img to the same folder as adb
adb push recovery.img /sdcard/
The next job is to open up a command window and navigate to adb folder, type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery

Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4

cancuck said:
Thanks for your hard work. Everything works quite well.
Sent from my Arc using Tapatalk 4
Click to expand...
Click to collapse
that's the easy bit, I have a feeling I need to make a couple of changes to the recovery.img but noting major, just a couple of other mounts I may have missed
I probably would like some help with the next bit however.
im just trying to build a development platform, I have a loathing for Linux as a desktop so will need to re educate myself without throwing my laptop out of the window, after that "challenge" the ROM should be easy

Well, I've just done it, and it works. Everything seems to be in order for the time being. I'm going to muck around with the new capabilities, and see what I can do.

Database Users

welcome