Database Users

Bricked-Unable to Re-install Packages

greetings...i've read far too many threads on not being able to boot into "recovery" and "download" and haven't found anything to fix me...
i can successfully get into "recovery" but when i try to reinstall the packages it starts to run a recovery with Clockworkmod etc...it stops and reboots into recovery...this will go on and on...
now when i try to boot into "download" i can't, i've tried many methods none work.
any help?
rooted/clockwork recovery/nandroid back up prior to trying the vibrant7

same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808

The K-Zoo Kid said:
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
Click to expand...
Click to collapse
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...

take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.

dsuycott said:
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
Click to expand...
Click to collapse
Alright i will doo... and you restored from odin after the problem started...?

I flashed the stock kernel and everything is good... Its in the OP of Eugenes rom.

98classic said:
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
Click to expand...
Click to collapse
thanks for the reply...i've done that a bazillion times...won't go, i even went to the tmobile store in my hood and no go on their end...

The K-Zoo Kid said:
Alright i will doo... and you restored from odin after the problem started...?
Click to expand...
Click to collapse
not after, i had restored from odin about two weeks ago...

Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App

The K-Zoo Kid said:
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yes(but i'm over saturated right now, i might have missed something) ...i'm dead in the water, i can't get to the point of anything seeing my device...my computer won't see it except as unknown usb device, no partitions show up, adb doesn't recognize it in any way...maybe i'm a [email protected], but i don't see anyway to flash it without at least getting in to download mode, or somehow pushing a .zip at the sd for a recovery??? technically figuring out that stuff is beyond my remaining brain cells...this seems like a dicey way for the phone to rely on when restoring to factory.... it would be nice to have the device look at All available partitions, internal/removable, for a recovery system or have an altogether different sd in the phone for a -R dedicated recovery volume....don't know, i'm a noob at this android stuff sooo....

[Resolved] Stuck in a boot loop

I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!

swampy67 said:
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
Click to expand...
Click to collapse
Would someone (aka moderator) simply sticky a bold
DO NOT REMOVE ANY FACTORY FILES, u goty plenty of room.......
to prevent this kinda stuff

Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html

dr1337 said:
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
Click to expand...
Click to collapse
but how do i reinstall when im stuck in a boot loop? is there some way to execute adb?

Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held

anubis13 said:
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
Click to expand...
Click to collapse
Thanks I'll give it a shot
Sent from my PC36100 using XDA Premium App

thanks this worked like a charm. Gotta love the XDA community.

A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!

Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.

Chaz36 said:
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Click to expand...
Click to collapse
Okay so this is what i did as directed by the guys above.
1. Download this file. have to warn you though this service is horribly slow http://api.viglink.com/api/click?fo...ww.filesonic.com/file/958397...pdate.zip.html
2. Put your external SD card into your computer, and copy over the file to the root of the card.
3. Rename the file update.zip(make sure it isn't named update.zip.zip)
4. Put the SD card back it the tab.
5. Make sure your tab is completely shut down.
6. Hold down the volume down button and press the power button.( dont let go of the volume down button till the screen turns on)
7. The recovery will boot and the update should hopefully restore your tab.
8.(optional but recommended) follow these steps in order to revert back to the latest OTA american version so that your able to upgrade to 3.1 when it comes out.http://forum.xda-developers.com/showthread.php?t=1101859
Hope this helps.

Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.

Chaz36 said:
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Click to expand...
Click to collapse
Well sorry that didn't work, i am not to experienced with development for this tab, so im fresh out of ideas. It might help to start a new thread explaining that you tried to un-brick your tab via this method and that a boot loop still occurs. Maybe some super smart devs can help you.

Crsdr37 said:
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Click to expand...
Click to collapse
yeah i did that right after i un-bricked it, but thanks for the heads up anyways.

For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.

SmittyRN said:
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
Click to expand...
Click to collapse
Dude, you just made my day.
Thanks.!!!!!

[Q] Can you help a brother out?

I will post the long version here, mainly because I have nothing better to do.
Here is the situation. I bought a NC about 6 months ago. I rooted it using Auto Nooter. I have no idea what ROM I installed to be honest. I'm very much a novice at this. And I'm quite stupid to boot, I might add. It has worked relatively ok since then. The ROM seemed a bit buggy and I had some initial troubles with constant reboots, in addition to some basic things not working and way bogging the thing down, but in general it was ok. I haven't used it much since unless I was traveling.
Today....I was traveling. Traveling to BFE. As such, I decided to bust out my trusty NC and download a new book while I was waiting for my flight. I did so, and something went a bit haywire. It seems that somehow, without prompting, the device has restored itself to the stock B&N ROM (1.1 maybe?). Yet - the Android OS is still there. For example I can click on my task manager app in the lower left corner of the homescreen and it shows that all of my apps are running and I can even switch to them. But my homescreen is defaulted to the B&N one showing my eBooks and I can't figure out how to get my Android launcher back. I have tried to reboot and it does the Droid boot up but reverts to the same B&N home screen.
I was thinking about trying to update to a new ROM since it had been awhile and I figured there must be something better/more stable out there now - Honeycomb or whatever. I guess this is the kick in the ass that I needed.
So now here I sit in a hotel room in BFE. There are no restaurants open past 9. There are no bars. There IS a Super Wal Mart but I think I'm gonna pass on that.
I figured I would look into this. Where to start? Should I re-set this thing to stock and then just pick a new ROM and re-root? Can I do any of this without having a SD card slot in my laptop - just using a USB cable? Will I lose any eBooks that I downloaded?
I await your sage advice.

rooting actually means gaining super user access to the current android rom. B&N, i believe is Froyo, so you did not install any rom so to speak. you were probably just rooted.
I think the issue is with the launcher and not that it is back to stock. What happens when you long press on the home screen?
If you plan to do anything, you will definitely need an sd card reader.

If you autonootered, then you were running stock, but rooted. With a custom launcher replacing the stock launcher, it sounds like.
At any rate, you were probably hit with the automatic update to B&N 1.2 (which is Android 2.2, iirc.) You almost certainly aren't rooted anymore, but it may allow you to run any apps that you already had downloaded, just from the stock app launcher.
When you get an SD card reader, you can check out Manual Nootering. It's basically the same as the old Auto Nooter, but for B&N 1.2. If you change the rom entirely (install CM7) or just run a different rom from an SD card, you'll avoid having B&N overwrite your root access in the future.

Thanks for the responses. I believe that you are correct. I actually was running 1.0.0. I used auto-nooter to root the thing and had it working with a custom launcher. I don't think it updated to 1.2. In fact I know that it didn't update to 1.2. I am trying to get it to do that right now.
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
I could Super Wal Mart tonight for a SD card reader if I'm feeling frisky.

I've got all kinds of problems.
I went to update to 1.2 from 1.0. I removed my SD card and erased and deregistered device. I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Any advice?

I'd do a full factory reset, then try the update to 1.2 again.
A couple of things about the 1.2 update -- do not unzip the update file or rename it. Just drop it as-is into the nook. And make sure to eject the nook from your computer and unplug it.

Thank you aka. I got it to take. I am now at 1.2. Now back to square 1(.2). Any help on this?
Baboontyme said:
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
Click to expand...
Click to collapse

Baboontyme said:
I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Click to expand...
Click to collapse
ETA: lol, congratulations! I guess just skip to that link at the end.
I'd agree with akaCat that you should do a factory reset, BUT you can only do that if you still have the stock recovery utility, and it seems possible that you do not. Try to get the NC to reset by interrupting the boot 8 times. If it doesn't work, you may have installed ClockworkMod Recovery on your Nook Color in place of the stock recovery utility. You may have done so while rooting, or later from the ROM Manager app, perhaps even by accident.
Have you attempted to boot to recovery by holding down "n" while you power on the device, and continuing to hold power + n for about six seconds (1-one-thousand, 2-one-thousand, etc), then releasing both? If so, do you get a factory reset dialog (series of yes/no options) or a longer menu including items like "mounting and storage" and "flash zip from sd card?" If you get the longer menu, then that's ClockworkMod Recovery, and neither the 8-failed-boots-reset nor the automatic update are going to work.
If you do have ClockworkMod Recovery, don't do anything yet. Hopefully somewhere on the screen it tells you the version number, in the format 3.0.x.x. Just let us know that version number and power off the NC.
If you still have the stock recovery utility, then do the factory reset, boot into the stock OS, connect USB, drop the update file straight on the Nook (not in any folders), safely remove the NC from your PC, and let it sit. Hopefully it will reboot itself.
If not, the next step is probably going to involve preparing a bootable ClockworkMod SD and manually installing a CWM-compatible version of the update, or of a different ROM. This article may help you wrap your head around the different options: http://quinxy.com/guides/how-to-pick-your-nook-color-operating-system-and-install-options/
ETA: lol, congratulations! I guess just skip to that link at the end.

Thank you, Tao. I seem to be a bit stuck, though.
I'm at 1.2 stock. I was able to reformat and erase my sd card. I went to load the .gz image onto the card (for CM7, per instructions here http://forum.xda-developers.com/showthread.php?t=1000957) and I also loaded the nightly build. Then inserted card into NC and booted. Nothing.
Any idea what I'm doing wrong? Should I unzip either file?
One thing that might/might not matter....when I went to eject the SD card from my PC, I wasn't given that option so I just pulled it.
One more thing.....the instructions at the link above instruct you to "write the image to your SD card" but then go on to say "eject the SD card" and then further "insert the uSD card into your computer"
Huh?? Isn't it all on the same card? Why do I need two different cards? What am I missing?

This blog breaks down the same process a little more step-by-step, with videos: http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html
You can skip the long preamble down to "Ready? Let's get started."
You do need to unzip the disk image, and write it to the SD using a program like Win32DiskImager or WinImage. It's also definitely a good idea to safely eject the SD card from your PC.

Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!

Can someone also tell me how to access the book I just purchased and was in the middle of reading? Do I have to go somewhere and re-download?

Baboontyme said:
Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!
Click to expand...
Click to collapse
I should add that though I can get CM7 to boot, I never get "The Power of Reading". It's just kind of a flash.

That's all normal--verygreen had to make a new uboot, which no longer shows "The Power of Reading" and also flies through a recovery boot so fast you could miss it. If gapps didn't install, just make sure the .zip is still in the boot partition and keep trying. I'm pretty sure holding power > reboot > recovery boot works now from within CM7, but I would go into Settings>Accounts and try to sign in to Google before assuming it didn't install.
If the book was a B&N purchase, once you have the market working, just install the Nook app and sign into your account, and you should be able to re-d/l the book, possibly even still synced to where you left off.

Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?

btw, you can also boot into recovery through rom manager, its easier.

Baboontyme said:
Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?
Click to expand...
Click to collapse
You can overclock: http://forum.xda-developers.com/showthread.php?t=925451
Just make sure you grab the version for SD, and install it just like gapps, then set clock speed via CyanogenMod Settings>Performance>CPU
boxcar8028 said:
btw, you can also boot into recovery through rom manager, its easier.
Click to expand...
Click to collapse
Easier than holding power a sec, poking "Reboot," then "Reboot to Recovery?"
Really, it's about the same either way, depending how handy ROM manager is on your system.

Cant get Vibrant to start help plz!

Ok i was on ICS passion then all of a sudden my phone said something about encryption an that it had failed an only option was to reset phone so i hit reset then it went to recovery mode an green android came up with chest open then error message happened an so i booted in to recovery then i try to go in sd an it would not allow me to so i then tried to odin an flashed then i powered on it gies to vibrant screen then it just shuts off so i then flashed Eugene froyo that does not brick then it takes me to stock recovery an says an i cant click on anything in recovery can only move -- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
Here are instructions i have followed an no luck http://forum.xda-developers.com/showthread.php?t=1043892
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck

Got it started
I got it booted though a very hard process an now i cant get my sd card to mount it says when i go into anything media related it says "Your phone does not have a SD card inserted" an Externel dont mount either

Which sd card isnt working... internal sd, or external sd?

kf7strng said:
Which sd card isnt working... internal sd, or external sd?
Click to expand...
Click to collapse
Both of them aren't working

Jasonhunterx said:
Both of them aren't working
Click to expand...
Click to collapse
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737

jrafael said:
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
Click to expand...
Click to collapse
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger

Jasonhunterx said:
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Click to expand...
Click to collapse
Hey Jason. I'm in the exact situation you're in. Loaded Passion for about 1 week, got the encryption screen and was forced to reset. Now my SD cards (internal and external) won't load. Have you found a work around for it yet? Cheers Mate.

nope nothing

either of you find a solution? Im having same issue

In the same boat
I am in the same boat. I was using the Euphoria ROM. Yesterday things slowed down on the phone. I rebooted a few times and it crashed. The last couple of times it told me about the encrypted data. That was when I tried to take it back to stock and it won't do anything now other than boot to the vibrant logo and shutdown. Searching for a way to odin a ROM/Kernel that has a CWM recovery so I can go in and manually format the SDcard.

Do what I did, sell it to someone as a wifi hotspot and buy yourself a hercules. You'll never look back
Sent from my SAMSUNG-SGH-T989 using XDA

BUMP
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.

webstas said:
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
Click to expand...
Click to collapse
Try this one.
http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my Vibrant using Tapatalk 2

Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.

Woodrube said:
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Click to expand...
Click to collapse
no i got up an took a shower then came back it gave me an encryption error then i odin back an more trouble odined a couple more times an now it boot loop an also wont start with eugenes froyo

I know it has been awhile but think back. Were you mounted to your PC at anytime between your last reboot and the Encryption Error? Doesn't have to be right before, the error gets throw on your "next" reboot. And as you know, reboots can happen manually or for something as simple as wrong UV settings.
Looking back in this thread, I saw that you got it to boot up. See if you can do that again and then mount your External via ADB and you should to push the proper commands then. Pretty much your internal is hosed, but me and a few others are working on that too.

Can't get it to boot it makes it to Vibrant screen an shut off an on Eugene"s froyo it gives me a couple of errors an I just can't get it to start anymore it there anyone who has encountered this an got it fixed like I really need this fix I am using a blackberry please save me

YAY
I got it fixed but now im on step 13 of that guide where you have to use ADB an i cant get the phone to show up on my PC what drivers do i need i already have Vibrant drivers but still nothing an the usb works its a samsung USB so can anyone help me with ADB

I am having a similar problem. Was running ICS 4.0.3 w/Euphoria without issue until this morning. Got a couple of errors after a normal recharge. Pulled battery and rebooted, but is stuck in boot loop. Cannot access either recovery or fastboot screen. Vibrant logo flashes and release buttons, but never enters mode. Then cycles to Android screen and would likely stay there until battery died. This is primary phone and need to put back into service quickly. Any assistance will be greatly appreciated. Thanks.
JIM in FLA

Go back to stock 2.1
Sent from my SGH-T959 using XDA

[Q] Cannot boot into anything, including CWR

Well, after a few weeks of reading posts, even opening up the hardware and taking the nook apart, here I am asking a question. I figure I would go to the source rather than those other place I was reading and tryign to get info from (mot os those places link here anyway). I know that everyone says that the nook is "unbrickable;" while I want to believe it, I may be in a place where it may be true.
I do want to add a thanks as well, since the NC "tablet" has been very handy, and my wife and I have really enjoyed it. Wouldn't have happened without you all. I wish I had more time to participate in developing, but working 80+ hours/week in a hospital limits my free time, as you can imagine.
I rooted the NC and installed Cyanogenmod 7 back in July 2011. It was a 1.1 model (if I recall correctly). I installed the mod to EMMC, along with CWM. Things ran fine for 6 months. Literally no issues. Then, one night the battery was dead, so I plugged it into the computer USB to charge while the machine was off. Didn't touch it at all. When I went to turn it on again, I was stuck in a bootloop. It would go to the cyanogenmod screen and say "Loading" then would start over again. So, I naturally made a bootable SD card, and tried going into CWR to fix things. However, the SD card had the bootloop as well. It would get to the two skulls and "Loading", flash blank, then start over again.
That went on for a while. I couldn't boot into anything, not into recovery, alternate images, literally nothing. So, I tried different images --- nothing. Finally, I did the power+n and got into the only screen that wouldn't keep resetting. It has blue text and says "Entering boot menu". The menu says "Encore U-boot Menu by j4mmr. 1.2 port+ extras by fattire." From this screen, I can navigate and change the boot options. However, once again, whatever I try does not actually boot, regardless of what I set it to. The only thing that I got from getting here was no more boot loops. After getting it to this point, I can try loading anything, and it will start, then the screen goes black/blank, and nothing happens. Left it on for hours to test.
Since that point, I have switched cards (SanDisk 2 GB class 4, Patriot 8 GB and a generic 8 GB microSD). I know that cards work correctly because I got a hold of a second nook, and they work fine on it. Below are a list of all the images I have tried to run off the SD. Again, nothing will boot, not even clockwork recovery/clockworkmod.
128 mb rootpack (IOMonster)
clockwork 3.0.2.8
clockwork 3.2.0.1 eyeballer
Nooter
Mirage_CM7_ICS_CM9_DualbootSD (this card works great on the working NC)
TWRP 2.0 RC0
Generic SD
Clockwork 0.7 -> starts boot loops again
I also tried ADB, connecting to the computer and using putty over SSH. Didn't work. 8 interrupted boots with 9th holding power+n. Nope. I even took the nook apart and disconnected the battery. Still no go.
If I recall, I think I had CWM 3.0.0.5 installed to the card and to the emmc.
If anyone has any other ideas, I could really use the help. I consider myself pretty computer literate (build my machines, coded in my spare time in the past, hacked a lot of my electronics). I have read many guides/sites and even tried the outdated stuff. Once again, I cannot get into clockwork recovery, so any guide that says to do that as the first step will not work. I also cannot boot off of the SD on cards that I know function.
Would using an older version of CWM (prior to 3.0.0.5) work? I think I remember reading a bunch of stuff about problems people were having with that version. The thing is, I wasn't installing or flashing anything new. I wish I was, because then I would know what was happening when everything got screwed up.
Thanks a bunch in advance for your guy's (gals?) time. This has been really painful.

Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP

Yeah, it has been frustrating, especially not knowing what happened in the first place. I actually did try the version from that first link (where I put 3.0.2.8). Again, the big issue I am having is that I cannot even get into the CWM. If I could, I could fix it. I also saw and read through that xda thread you kinked to (open right now in my browser), but the problem remains that I cannot even get to the point where I can flash something.
Thanks at least for responding. I'll try a few more things and see if it works, but I am running out of ideas.

In theory creating a bootable CWM card will get you into recovery even though you can't access the Recovery on the internal. Once you reach Recovery from the SD card you can flash whatever you need. It is just a matter of making a bootable recovery card that boots far enough to get you there.

In theory, yes, but as I said in my first post, I tried all the bootable cards without any luck. When I try to set the SD card as primary boot from that one screen from fattire, it locks and never restarts.

J515OP said:
Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP
Click to expand...
Click to collapse
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.

DigitalMD said:
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.
Click to expand...
Click to collapse
How did you get it to boot into CWM in the first place in order to flash? That is my current problem. Any method of fixing relies on the ability to boot into CWM from the SD card, which (for whatever reason) isn't working at the moment.
Well, tried to use the native Nook u-boot. Get the "Touch the Future of Reading" screen, then black, just like with any of the other cards. On the good nook, it boots into a linux file and runs the recovery script, so it is not the card reader or the SD card.

Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.

czarofthefrozentundra said:
Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.
Click to expand...
Click to collapse
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.

leapinlar said:
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.
Click to expand...
Click to collapse
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.

czarofthefrozentundra said:
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.
Click to expand...
Click to collapse
It goes to the boot menu when you hold n with eyeballers image burned to SD? What happens when you select SD and normal? Just a hang? With 'loading' showing?
Edit: I just thought of another reason that could be causing this. There is a flag set in /rom that tells the system to try to boot into recovery. It tries no matter what you tell it to do in the boot menu. ROM Manager uses that flag to boot to recovery when you tell it to. Then after you successfully get into recovery and exit it by telling CWM to reboot, CWM clears that flag. If your recovery is borked up, you never get that flag cleared and it's an endless loop.
There are two solutions I can think of. First, use racks dual boot SD that you already have and go into the boot menu with that. Tell it to go to SD and recovery. Hopefully his recovery will load. Then immediately exit by the menu. That should clear the flag. If that fixes it and it boots to CM7, go to ROM Manager and flash a new CWM to emmc.
If that does not fix it search xda for 'fix recovery'. There is a nook thread telling how to fix the recovery on emmc.
Edit2: I just thought of a third way to try to get it to boot. Take eyeballers 3.2.0.1 CWM SD and put it in your PC. There should be two files there named uImage and uRamdisk. Make a copy of them on the SD and rename the copies to uRecImg and uRecRam. Then put back in nook and reboot to see what you get.

Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.

czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
See my edit2 above for a third way to try to clear the flag.
Sent from my NookColor running ICS and Tapatalk

czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
Hello? Feedback?
Sent from my Nook Color running ICS and Tapatalk

Ha, I tried the quick reply function, and it didn't work. Here is what I wrote yesterday (verbatim, since I still had the window open):
"Well, so far no luck. Here is what I have tried, and the new information that I learned.
Used dual boot SD that I know works and booted into bootloader menu. Tried all different options on the SD card. What happens is that it thinks for a bit, then turns the screen black, but the boot screen never comes up (i.e. the Cyanogenmod logo that usually starts before things boot). So there must be some problem there.
If I hold down power, it will restart. Again, the screen turns black after the loading screen is on for a while (happens no matter which image I burned to the card).
I still need to try the other method (eyeballer one). I don't think the EMMC reset will work with my particular issue, as I had read that thread earlier."

czarofthefrozentundra said:
I still need to try the other method (eyeballer one).
Click to expand...
Click to collapse
If the problem is the recovery flag, the mods to the eyeballer CWM SD should work. If it does not work, it may be something else. If it does work you can flash a new CWM to emmc using another eyeballer zip. Get it here:
http://forum.xda-developers.com/showthread.php?p=21932561
You would want the first choice.
Sent from my Nook Color running ICS and Tapatalk

Cool. Will give it a try tonight and report back. Just have to find my spare SD card.

So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?

czarofthefrozentundra said:
So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?
Click to expand...
Click to collapse
I'm not sure what to tell you to do next. I guess I am going to send you to a post that tells pretty plainly how to do the 8 failed boots. I know you tried that, but timing is very critical with that procedure. Worth a try to me.
http://forum.xda-developers.com/showthread.php?p=25405429

How do you do the 8 failed boot deal with the cyanogenmod screen running. I am not sure about the timing of things. Also, which buttons? I have seen people do it with just the power button. Other places say with the power+n+vol up.