Database Develop

Can only boot into CWM from SD Card?

So if I goto ROM Manager, I can successfully install CWM. I goto "Reboot into CWM" and I get a install error when it tries to boot. I am able to boot into CWM via MicroSD card but NOT from just my Nook device. I had some issues a few days ago where I accidentally whiped the /system and /data. I've since fixed it (i thought) but I cant help but think this issue is related.
Any ideas...?

DroidHam said:
So if I goto ROM Manager, I can successfully install CWM. I goto "Reboot into CWM" and I get a install error when it tries to boot. I am able to boot into CWM via MicroSD card but NOT from just my Nook device. I had some issues a few days ago where I accidentally whiped the /system and /data. I've since fixed it (i thought) but I cant help but think this issue is related.
Any ideas...?
Click to expand...
Click to collapse
I had this problem too. It happened to me, because I had screwed up the boot partition. I had to restore to stock, and then re-nooter to fix it.

I have the same problem running nookie froyo from emmc. I've tried a bunch of different things but have never been successful.
I was able to get it working on stock rooted fine thouhh. Has anyone successfully gotten clockwork running with nookie froyo without using the clockwork sd boot?

philburkhardt said:
I had this problem too. It happened to me, because I had screwed up the boot partition. I had to restore to stock, and then re-nooter to fix it.
Click to expand...
Click to collapse
Was it easy to restore to stock?

I would download the repartition boot from http://forum.xda-developers.com/showthread.php?t=929670 , put it on the micro sd along with CWR and flash. This should fix your boot partition, which you then can reinstall CWR if you so desire.
If that doesnt fix boot then use http://forum.xda-developers.com/showthread.php?t=931720

volwrath said:
I would download the repartition boot from http://forum.xda-developers.com/showthread.php?t=929670 , put it on the micro sd along with CWR and flash. This should fix your boot partition, which you then can reinstall CWR if you so desire.
If that doesnt fix boot then use http://forum.xda-developers.com/showthread.php?t=931720
Click to expand...
Click to collapse
will this work on my Nookie froyo on emmc?? without wiping my data?

I am struggling with the exact same issue. I used the Monster Root Pack to restore my messed up NC 1.1 this weekend. After i got everything back to 1.0.1, I have been unable to do a nandroid from CWM. It kept failing. After some searching on this forum, I found that the CWM zip that is included in Monster Root Pack isn't working. So I tried to flash the zip from CWM thread. That errored out, too! I'm glad I found this thread.
So, what does the repartitioning boot do? How would that fix the issue of CWM not flashing? Also, does flashing the repartition force me to have to go back to stock?

Anyone have any success with this?
Preston

Can't boot from emmc

I rooted my 1.0.0 NC, worked great. Overclocked it using the 1000mhz kernel, worked great. Installed Rom Manager using adb, clockwork recovery, and sideloaded 1.1 update, still worked great. Decided to try out Froyo...I was a big dummy and didn't create a backup...it installed, then I felt it was slow so decided to try an updated froyo (nookie-froyo 5) works great. But now I'm having a problem where it is only booting from the SD card. I tried everything but nothing is working. I tried doing the copy2emmc.sh, didn't work. Tried running CWR and flashing the stock 1.0.0, doesn't boot up when I remove the SD card and click reboot now. Any ideas? Please help. I would like to boot from the emmc so if I can either get froyo installed on it or go back to stock and just stick with the 1.1 I'll be happy either way.

have you tried these methods?:
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Sorry for the hxxp, don't have enough posts to link yet.

Good news, I flashed it with the repartition-boot-with-stock.zip and now it boots up but just stuck in a loop. I tried doing the 8 boot step but can't get the timing down...

Finally restored!
So I tried to do the restore again but this time I tried the 1.0.1 instead of the 1.0.0 and it worked!! Thanks everyone!

[Q] After CWM backup system reboots back into CWM

I booted into Clockworkmod Recovery (3.0.0.5) and did a successful backup but when I REBOOT after it is complete it keeps going back into the recovery screen again.
This is driving me nuts. This was a brand new (received today) NC rooted with Auto-Nooter 3.0. I set it up the way I wanted it then did a full backup. Now I can't get out of the backup screen after a reboot.
How can I fix this so I can get back into the O/S?

This happened to me too. I'm still new and dont know why there are specific versions of CWR for specific ROMs... Or why the same version of CWR cannot restore its own backup.
But reinstalling http://forum.xda-developers.com/showthread.php?t=947071 via a sdcard image worked. If your nandroid/cwr backup does not work I hope you have a titanium backup.

MisterEdF said:
I booted into Clockworkmod Recovery (3.0.0.5) and did a successful backup but when I REBOOT after it is complete it keeps going back into the recovery screen again.
This is driving me nuts. This was a brand new (received today) NC rooted with Auto-Nooter 3.0. I set it up the way I wanted it then did a full backup. Now I can't get out of the backup screen after a reboot.
How can I fix this so I can get back into the O/S?
Click to expand...
Click to collapse
Place the file I attached in root of your SDCard and run it from CWR and it will remove CWR and restore you to Autonooter 3.0.0
Apparently CWR has issues with 1.1.0 ROM. This worked for me, when I had the very same issue. I wish I could find the original post I got this from so I could give them the credit.

http://forum.xda-developers.com/showthread.php?t=914690
Ok, this is where I originally got the cwr-removal.zip file, author was samuelhalff
migrax

Same thing happened to mine i ended usinthe removal tool and clearing the cach and then reinstalling the stock zip. I probably spent a good 3 hours figuring it out.
Sent from my LogicPD Zoom2 using XDA App

[Q] How to get 1.3 update on rooted 1.2?

I got a used nook that had CM7 on it. Seeing that there were issues a week ago with the 1.3 root, I put 1.2 on it and rooted it. Now 1.3 is successfully rooted and all seems a go ... so I want it.
But how the heck do I get a rooted 1.2 Nook to get the update?
It's been on wifi with the B&N Shop and/or Home open for three days, nothing. I followed the steps on B&N's site to try to sideload the update. Nothing. I don't see a CWM flashable version out yet. Frustrating.
I could also factory reset back to 1.2 and try to let it load the 1.3 update - I assume that the MN still works with a stock 1.3 as well.

nloding said:
I followed the steps on B&N's site to try to sideload the update. Nothing.
I could also factory reset back to 1.2 and try to let it load the 1.3 update - I assume that the MN still works with a stock 1.3 as well.
Click to expand...
Click to collapse
Sideloading BN1.3 works for me. Describing EXACTLY how you sideload the update. The update needs to be copied to emmc.

I followed the instructions on B&N's site. I put the nookcolor_1_3_update.zip file and put it right on the root of the emmc (at least, the highest up directory the USB interface would let me place it on).

Having CWM on your internal recovery blocks the update. You can flash this file to get back to 100% stock (internal CWM or CWM card, doesn't matter):
update-nc-stock-1.2-signed.zip
Format /system and /data before you flash it. If you have apps and settings you want to restore after you update and root, make a backup first (you should anyway) and once you have CWM back, Advanced Restore /data only.

CWM is not installed on the emmc. I use bootable sdcard with CWM burned on it to do my flashing. I doubt this is the issue but if MN will work on a stock 1.3 install, it's easy enough to do.

I had also encountered a problem, but had worked around it.
It turned out that I had at one point flashed CWM to my emmc even though I was using an SD card to boot.
The update was failing each time, but I eventually noticed that it was going into clockwork during the restart and the install would fail.
I'd completely nuked the Nook (deleted boot, system, etc) while in CWM and restored a Nook 1.1 image I had.
This allowed me to then install the 1.3 update and have it reboot into the BN recovery instead of the CWM recovery.
Note, if you format boot, system and so on, you'll render the Nook unbootable without an SD card, so be sure to have the image ready to restore BEFORE you reboot it.

I ended up doing a factory reset and putting the nookcolor_1_3_update.zip on the root of the emmc. It updated immediately, but I of course lost my data. Oh well.
MN didn't really work, I fought with it over and over again, but finally got it working. I'm posted in the MN thread about it.

Need of help with errors in Clockworkmod Recovery

I am trying to create a back up of my system and the backup errors out in the data portion. It does not say why. Just says error when backing up on /data. I am currently on a rooted stock rom. I have tried using older versions of clockworkmod recovery with no success. Any help would be greatly appreciated. THANKS!
Sent from my DROID3 using XDA App

Are you using Koush's or Hashcode's versions specifically for the d3? Im asking because I thought there was only 2 versions and you said you tried older versions.
Sent from my DROID3 using XDA App

I used them both. Koush offers to flash older recoveries which is only 2 so far. I currently have hashcodes version and the same thing it going on.

I flashed the stock deodex via clockworkmod recovery and it worked like a charm. I then downloaded another zip and tried to flash it then i could no longer boot into clockwork recovery. So to solve that i deleted the d3 bootstrap then redownloaded it and i could boot into it again. So maybe try that then try a backup again? Im not sure why you would be getting an error
Sent from my DROID3 using XDA App

Well, you have to redo the bootstrap on droid 3 after every fresh install of a new ROM. I have tried deleting the bootstrap and reinstalling it with no success. It still errors out on the backup of the data portion. Maybe I might take a risky move and flash a new ROM without a backup and see if it is able to backup the data after the install. I hope I just don't brick my phone or get a bootloop. I would be screwed!

Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!

mothman57 said:
Installed Steel Droid v2 successfully but I tried a backup and it still had an error while back-up up of the data portion. I am at a loss of ideas on what to do next. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Maybe you have a corrupt fat filesystem on the backup destination...
Have you tried to do a checkdisk when connected to the pc ?

I just completed a checkdisk and I even formatted the SD Card yet still the same issue! I then tried to checkdisk the partition of the internal memory yet no success. Thanks for the help though. It is greatly appreciated.

Steel Droid 3 came out today. I installed the new ROM and still it errors out on the /data portion of the backup. Hopefully someone can help me here. Last resort is a full factory reset of the device. I am waiting before I do that.

Is anyone else experiencing these same issues?

Try SBFing, re-rooting and then using the tweaked boot-strapper. When all else fails, start from scratch. If that's still not working, I would venture to guess that your /data partition has issues (which SBFing should fix).

What OS are you using?

I'm having a different problem that maybe some can help with. I just flashed the sbf again, and I've rerooted stock, and now I'm trying to reflash SteelDroid3.
I'm running into an error I haven't had before with CWR. Everytime I try to flash any ROM (from internal or external) it fails - E:Can't open "location" (bad)
I've checked MD5 sums and tried muliple roms, all give the same error.
I started with Hashcodes tweaked Bootstrap, then uninstalled and tried koush's. Neither made a difference. I even tried CWR 5.0.2.5 vs 5.0.2.6 to see if that would make a difference. No luck there either. Even tried reflashing the SBF, still no go after getting reset up.
I can make nandroids, and I can restore nandroids, (restored a debloated I had made earlier no problem) So the only issue is flashing a new rom.
Any idea's
Thanks

I have windows 7 64bit on my computer. Android phone is the 2.3.4 with steel droid v3 ROM. As far as SBF goes, should I use the example on the android development section of RSDlite? And if I preform this, will it delete all my data/apps and restore it to like a factory reset?

Im having similar issues. Backups are not being created properly - the zip files only contain 2 files:
data.ext3
system.ext3
I have one backup that works from a week ago - it contains the following files:
.android_secure.vfat
cache.ext3
data.ext3
nandroid.md5
system.ext3
any ideas why backups wouldn't be created properly? (using the modified bootstrap and CWM)

That is exactly what I am experiencing as well. Just the system and data are being preformed, but the data is not properly finishing.

I think we just need more room on our SD cards. I cleared up a few gigs of info, and now its working just fine. give it a shot.

I dont think that is the issue. I have 14.6gb worth of free storage on my card. It has to be an issue with my internal storage or clockworkmod. I am guessing it is my internal storage.
Sent from my DROID3 using XDA App

Well, I decided to do it. I flashed the original unrooted ROM back on the phone. I have to say it sucked redoing all my phone tweaks, but it did fix the issue. I can now preform back-ups in full! Thanks for all who replied in this forum.