Database Develop

Stupid newbie question v. fresh 1.5 to Damagecontrol

I just got my Hero last week and using fresh kitchen, flashed to fresh 1.5.
I wanted to move up to the new damagecontrol rom, but since I used fresh kitchen to upgrade the first time. I wanted to know what I had to do. Is it just a matter of draging the dc zip to my sd card, booting to recovery and then updating (or what ever the menu says) and that be it? thanks for helping a newb

pyropup55 said:
I just got my Hero last week and using fresh kitchen, flashed to fresh 1.5.
I wanted to move up to the new damagecontrol rom, but since I used fresh kitchen to upgrade the first time. I wanted to know what I had to do. Is it just a matter of draging the dc zip to my sd card, booting to recovery and then updating (or what ever the menu says) and that be it? thanks for helping a newb
Click to expand...
Click to collapse
That will update the ROM yes. But you HAVE to wipe the factory default/dalvik-cache first. Which means you'll need to back up stuff you want first.
Going from 1.5 to 2.x isn't easy. If you have the right tools (I used Titanium backup) you can get your text messages back. Contacts will fail (unless you have them synched online) and you'll likely want to reinstall your apps.
If you're going to move from 1.5 I recommend a fresh start, don't try and restore anything and reinstall. It's a whole lot easier (I did this on my wife's phone last weekend, so I'm speaking from fresh experience). I'm sure there will be a lot of people who disagree, but it's definitely going to be better to wipe and go then try and restore it.

so do i just boot up to ra, do a wipe and then re-boot and copy over the dc zip? I have all my contacts and pics stashed away via wavesecure and I can just re sync them that way. not too worried about losing the text msgs.
also, i just added swype last night, again using fresh kitchen. how do i add those using dc?
Sorry for the stupid questions.

pyropup55 said:
so do i just boot up to ra, do a wipe and then re-boot and copy over the dc zip? I have all my contacts and pics stashed away via wavesecure and I can just re sync them that way. not too worried about losing the text msgs.
also, i just added swype last night, again using fresh kitchen. how do i add those using dc?
Sorry for the stupid questions.
Click to expand...
Click to collapse
Also I had to partition the sd card cause DC went into a boot loop till I did. Just remember to partition before moving DC 2.08.1 to your sd card or you will erase the rom.

You can probably re-add swype with Fresh Kitchen on the 2.1 ROM. If not do a search for 'adb'.
Basically you would do an adb remount, followed by 'adb push nameofapplication.apk /system/app' (this is not exact commands, look it up for where swype goes, I believe /system/app is correct, though).
For the rest:
Reboot into recovery
Do a wipe factory
Do a wipe dalvik-cache
Do a wipe SD:ext (it will fail if you've never used a2sd, don't worry about the failure message).
Then select 'flash zip from sd card' and flash the ROM you put on it.
If you're flashing the latest DC roms be aware: I've seen that take anywhere from 10 minutes to 30 minutes to boot after installation. So don't freak out. Also make sure your battery's fully charged before you install it. (The minimum is 30%, but if you have it at 100% you definitely won't need to worry about the battery when flashing a ROM).

animal7296 said:
Also I had to provision the sd card cause DC went into a boot loop till I did. Just remember to provision before moving DC 2.08.1 to your sd card or you will erase the rom.
Click to expand...
Click to collapse
Partition you mean? Shouldn't have to, to install that ROM. I installed 2.0.8 on my wife's prior to re-partitioning it for a2sd and it worked fine.

smw6180 said:
Partition you mean? Shouldn't have to, to install that ROM. I installed 2.0.8 on my wife's prior to re-partitioning it for a2sd and it worked fine.
Click to expand...
Click to collapse
Thank you. I was having a brain fart and that is what I was having problems with. I flashed the rom and it went into boot loop (about 1/2 hr) removed battery wiped and boot looped again. Finally partitioned sd and booted fine.

animal7296 said:
Thank you. I was having a brain fart and that is what I was having problems with. I flashed the rom and it went into boot loop (about 1/2 hr) removed battery wiped and boot looped again. Finally partitioned sd and booted fine.
Click to expand...
Click to collapse
Odd...but yeah I just remembered reading you had that issue. I think that dconfig might not be 100% ready for prime time, which can cause that kind of issue. But that's a guess. Seems to be a random deal, though, because it doesn't happen to everyone.

[Q] I need help in the worst way! NC stuck on "n"

Hi guys, i have a Brand new Nook Color that im trying to root. I will try to explain what i've done so far:
1)updated firmware to 1.1
2) downloaded super-nooter 12.25
3) downloaded win32diskimager and winimage
---i have an 8gb fully formatted sd card-----
note* i could not for some reason "restore virtual hard disk image on virtual drive", so instead i used win32diskimager and transfered the files over to E: drive (micro sd) noticing the files on the step-by-step instructions; my files are similiar except the "u-boot.bin" file that it reads instead is a VLC file saying "u-boot" and it shows the orange cone.
i've since then installed the micro sd card into the nook, plugged in the usb, to start the boot up, i hear the nook connecting/disconnecting with the laptop, screen is black, then i eventually get to the "n" screen...... it just stays there....
What am i missing/doing wrong/not getting?
i REALLY appreciate anyones advice and help. thank you so much

Does supernooter root version 1.1?
1.1 just came out today.
Sent from my Android Nook Color Tablet via Tapatalk

i thought about that too. is there a way to get the nook back to usable condition? and if so, what should i do differently?
thanks kindly

ok so i've done the 8 interrupted boots and have successfully got the nook to default settings by following instructions "flash back to clean stock image". i am now on 1.0.1, and will retry the whole process again..... i'll keep you posted!

Yes. The current Auto-Nooter 2.12.25 only works on 1.01 and not 1.1.
It will hang your Nook if you try..
To restore it back to factory.. the the data wipe then trigger the factory restore by interrupting the boot process 8 times.
Power up the nook, then as soon as you see the text come out, press and hold the power button until it shuts down.. Do that 8 times..
You can find more instructions here :
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Good luck! And wait for a new auto-nooter..

MaccaMRP said:
i thought about that too. is there a way to get the nook back to usable condition? and if so, what should i do differently?
thanks kindly
Click to expand...
Click to collapse
To go back to 1.01 1.02. ...currently its the post right under yours
not sure if it will work if you are already upgraded to todays update. But you can do the eight salute. too.
Just an FYI it takes a while for the devs to work up roots for new versions. When a new version comes out it can break existing roots and a new exploit or variant of and old exploit needs to be discovered. Basicaly the old root methods may not work for the new versions. Always give it a few days for the dev comunity to catch up and react. Never a good idea to upgrade your firmware the day it comes out and then try to root.
Its a learning processes most of have gone through. read read read. Its all here.
Good luck.

Thanks for everybody that helped! I now have successfully rooted my NC, and am enjoying it thoroughly!
Cheers
Sent from my LogicPD Zoom2 using Tapatalk

[Q] Help with partition /media?

Could someone please help with repartitioning /media?
Earlier I tried the dual boot from eMMC. Due to errors with the stock boot, I tried to restore to stock setting.
Right now, I am on 1.0.1 rooted but my internal drive is showing 0% free storage. Everything else is fine now.
I've tried a script that was on the thread but it didn't work for me.
I also can only use adbwireless since my computer won't recognize the device.
Could someone point me in the right direction? I'm a complete newbie, this is actually my first android device so small words please.

You might want to look at THIS thread and use it to restore to stock ...
Then you can update to 1.01, .. Autonooter to root, .. install ROM Manager from the market, .. use it to install Clockwork Recovery, .. make a nandroid using Clockwork and then anything you do going forward you can always use the nandroid to restore.
You can get to 1.1 using THIS thread or go back to trying the dual boot.
Hope this helps.

I've already tried that route. Unfortunately it doesn't doesn't help with my issue.
sent from my nookcolor

brendac87 said:
I've already tried that route. Unfortunately it doesn't doesn't help with my issue.
sent from my nookcolor
Click to expand...
Click to collapse
Have a look at Divine_Madcat's post #63 on page 7 of the dual boot thread started by rookie1.
I typed that in adb shell and it fixed my /media partition back to stock so I could upgrade to 1.1 again (I had nandroided back to 1.01 first you might not have to do that though).
**IMPORTANT**I had to enter the line about partition 8 3 times before it completed successfully.
Then I reran the dual-boot.sh script (2 times) and everything works after that dual boot with 1.1 and Nookie Froyo.
If you want to stay on 1.01 stock Divine_Madcat's instructions should fix your media partition and I don't see why it wouldn't work in adbwireless as long as you are getting a shell prompt.

Thank you so much! I can't believe I didn't see that when I was looking at the script right below it!
I'm extremely grateful. Thanks

[Q] I have totally messed up my Nook Color

Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.

MentalDragon said:
Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.
Click to expand...
Click to collapse
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.

BarryR1 said:
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.
Click to expand...
Click to collapse
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838

khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Is this going to help me. My original firmware was 1.0.1.

Just grab the CWR 1.1 Recovery image from the development forum. Burn that onto an SD Card and reboot. Wipe data boot system cache and flash. done.

Find rootpack in dev section, write that to sd card, add the flashable restore to stock zip from samuelhalffs restore to stock thread in the dev section to your sdcard, boot to sdcard with the rootpack on it, flash the restore to stock zip after formatting system and data. Wala, fixed! All info can be found in my dummies guide to my nook won't boot a few threads down.

Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.

MentalDragon said:
Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.
Click to expand...
Click to collapse
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?

khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Oops. My bad. Sorry for the misinformation.

MentalDragon said:
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=949699
Try this Thread, "Dummies Guide to Fixing 'My Nook Won't Boot'""
This should work and get you back to stock so you can start all over.

[Q] Stuck at Cyanoboot screen

Hello I've had a Nook HD+ working since August beautifully, I thought to get one for my sister and picked one up over the weekend.
Today I decided make it like mine, ie take off the B&N interface and try for a most vanilla like jelly Bean.
These are the instructions I followed last time....
"1. Download leapinlar's NookHDplus-bootable-CWM-6028-for-stock-4GB-rev4-(05.15.13).zip
2. Extract the zip above and burn the img to a 4GB or larger microSD card
3. After burning, copy cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip and gapps-20130301-jb-signed.zip back to the microSD card
4. Place the microSD card back to the Nook HD+ and boot it
5. Do a backup for the stock ROM
6. After backup is done, do data wipe/factory reset
7. Flash the cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip and gapps-20130301-jb-signed.zip"
I made a mistake this time around, I used cm-10.2-20131031-UNOFFICIAL-ovation-sdcard.zip by accident instead of the EMMC version. Now when I power the unit on, with no SD card it keep rebooting at the Nook screen. With a now corrected SD card it gets stuck at the cyanoboot screen, it dims after a minute but then still just stuck there.
How do I go about fixing this? Thank you in Advance....

Ok so I rebuilt the SD card and it looks like it's kinda back to normal. I did a wipe and then wrote....
cwm-recovery-ovation-3.zip
cm-10.2-20131031-UNOFFICIAL-ovation-emmc.zip
gapps-jb-20130301-signed.zip
Rebooted and now it gets stuck at that spinning logo, the logo never goes to the correct aspect ration. Screw it I'm done for today.
Tomorrow I'll try doing a restore to factory defaults and try the same steps again, if it should fail again, then I'll restore, wipe, and try the exact same files I used on mine. Unless someone has a better guide/method to use....
Any insight would be appreciated. Thank you!

You need to get back to pure stock so that everything can be done over. Go to my HD/HD+ CWM thread linked in my signature and use your already burned CWM SD to flash a plain stock ROM from item 6. Also do a factory wipe with it.
Then start over, but use the dummies guide for CM10.1.
Edit: I did not see your second post when I wrote this. But I think the advice still holds.
Sent from my BN NookHD+ using XDA Premium HD app

OK go tit all settle! I used your stock image, booted up to normal, then went back, wiped, and did the usual files. The latest file cm-10.2-20131031-UNOFFICIAL-ovation-emmc Gave me keyboard errors, so I went back to the old file I used previously on mine, cm-10.1-20130615-UNOFFICIAL-ovation-emmc, and everything seems perfect.
Thank you for your help! You are a man among men!

leapinlar said:
You need to get back to pure stock so that everything can be done over. Go to my HD/HD+ CWM thread linked in my signature and use your already burned CWM SD to flash a plain stock ROM from item 6. Also do a factory wipe with it.
Then start over, but use the dummies guide for CM10.1.
Edit: I did not see your second post when I wrote this. But I think the advice still holds.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I'm trying to follow your method of going back to stock on emmc, but I can't get my nook into recovery. I have re-made my SD card multiple times and the times my HD+ boots off the sd card (mine is one of those thats hit or miss), it will stay stuck on the Cyanoboot screen. If I can't get into recovery somehow, I'm hosed. Any ideas? I want to avoid having to bring it in for 1 year warranty replacement.

cabbieBot said:
I'm trying to follow your method of going back to stock on emmc, but I can't get my nook into recovery. I have re-made my SD card multiple times and the times my HD+ boots off the sd card (mine is one of those thats hit or miss), it will stay stuck on the Cyanoboot screen. If I can't get into recovery somehow, I'm hosed. Any ideas? I want to avoid having to bring it in for 1 year warranty replacement.
Click to expand...
Click to collapse
Sounds similar to my situation. Can't get the tab into recovery.

chr0 said:
Sounds similar to my situation. Can't get the tab into recovery.
Click to expand...
Click to collapse
i find it hard to believe we are both just screwed. Maybe I'll try and find a different sd card and give that a try. Ugh. This is most bogus.

Hello everybody,
I have even worse problem with cyanoboot - I've bought used NOOK HD+ after someone tried to install cyanogenmod on it, and except holding cyanoboot at screen with an SD card (that I've prepared accordingly leapinlar's page), it has next issues:
1) there is absolutely no response, when I try to turn it on without an SD card;
2) when the SD was untouched by me, it had some other cyanoboot installed on it but with this version nothing in the cyanoboot menu worked: there was a menu and errors in the console every time I've done everything. But, at least, it loaded.
And I have no SD card bigger than 1 GB.
And, question ahead - is it some easy way to figure out whether my B&N is bricked?
Regards

cabbieBot said:
i find it hard to believe we are both just screwed. Maybe I'll try and find a different sd card and give that a try. Ugh. This is most bogus.
Click to expand...
Click to collapse
Good luck to you, sir.
Do you mean you are going to try another SD card by making it bootable with CWM? Or are you going to try verygreen's no-emmc build and run your tab directly off the SD? Because I have tried more than a few SD cards for the former to no effect.

chr0 said:
Good luck to you, sir.
Do you mean you are going to try another SD card by making it bootable with CWM? Or are you going to try verygreen's no-emmc build and run your tab directly off the SD? Because I have tried more than a few SD cards for the former to no effect.
Click to expand...
Click to collapse
I cried uncle and got it swapped out for a refurb. Hope you find a fix, this problem is a little nightmare, first time I've never been able to save a device.

cabbieBot said:
I cried uncle and got it swapped out for a refurb. Hope you find a fix, this problem is a little nightmare, first time I've never been able to save a device.
Click to expand...
Click to collapse
Glad you got it exchanged. Nook, after the drop in prices has been extremely good value for money.
I'm in Afghanistan, so an exchange is not happening until my next R&R. I'll probably be able to save enough for a Note 10.1 or Nexus 10 atleast by then.