Database Develop

Help restoring with Nandroid after a bad .zip update

I tried to flash a theme update from zip in recovery mode and it messed something up royally. Now when I boot the phone it shows the HTC logo then just goes black and never comes back. I made a Nandroid back up right before I flashed and it said it completed it successfully, but when I go to recovery (volume down + power button) and select nand restore, it says its restoring and then restoring complete but when I reboot it still goes to the black screen. What do i need to do differently? I have never had to restore until now.
I'm on Fresh 2.3.3

Try wiping all data and dalvik and then restoring the nandroid.

doojer said:
Try wiping all data and dalvik and then restoring the nandroid.
Click to expand...
Click to collapse
Just tried that and I'm still getting the black screen after boot.

PMDColeslaw said:
Just tried that and I'm still getting the black screen after boot.
Click to expand...
Click to collapse
Do adb logcat. It might actually be booting without a bootscreen.

HeroMeng said:
Do adb logcat. It might actually be booting without a bootscreen.
Click to expand...
Click to collapse
Can you walk me through that? Sorry I haven't ever heard of it.
EDIT: Ok I let it run for a while and it eventually boots up but the boot screens/sounds never show or play. So I completely wiped the phone and reflashed Fresh 2.3.3... still no boot screens or sounds! I don't know what I could have messed up that complete wipe/flash doesnt get rid of. Any ideas? Also now Titanium is saying that it cant get root access because my phones not rooted properly. What tha?

Bump... Still having this issue. The phone is usable but the boot images and sounds are gone

nobody has mentioned this but maybe you just have a bad Nandroid. maybe something did not copy right or something in the phone internally got deleted during the backup/restore process. i saw on android forums somewhere it happened to some person using an Eris. Cant quite remember how he got it fixed but he ended up fixing it somehow.

t12icky0 said:
nobody has mentioned this but maybe you just have a bad Nandroid. maybe something did not copy right or something in the phone internally got deleted during the backup/restore process. i saw on android forums somewhere it happened to some person using an Eris. Cant quite remember how he got it fixed but he ended up fixing it somehow.
Click to expand...
Click to collapse
Well I thought it might be a bad nandroid too, so I just wiped the phone and flashed fresh without ever restoring the backup and it still has no boot images or sounds. It's the strangest thing. When I flashed the first time to 2.3.3 the re were definately boot images and I flashed from the same file this time.

You might have to just use the RUU and start over from scratch, I had to do that once and it sucked.
Sent from my Hero CDMA using XDA App

Nook color won't turn on, won't boot sd card

Well I don't know what I did but this morning when my nookie froyo emmc was at 20 percent it decided to turn off and not turn on and won't turn on when charged and will not boot any sd cards. I feel stupid but after my nook working on emmc froyo for a week and now its not even turning on I feel very stupid. All help is appreciated, thanks!
Sent from my ADR6300 using Tapatalk

Have you tried booting to the CWR card yet? And using Samuelhalff's zip that restores the stock partitions? This seems to have worked for many people experiencing the fatal Froyo crash. Take a look at the 'Easily Restore to Stock" thread found here in the Nook forums. And in the end if your device truly won't turn on, then chances are the guys down at B&N won't be able to either. *Warranty*

Well I have tried monster root pack as a card but I haven't tried stock partitioning,i dont know where the thread is. But will this let me even boot an sd card ?
Sent from my ADR6300 using Tapatalk

RileyGrant said:
Were you running froyo off emmc? If so:
http://forum.xda-developers.com/showthread.php?t=931720
I recommend flashing this ROM instead though (pre-rooted 1.1):
http://forum.xda-developers.com/showthread.php?t=932145
And yes if you insert the CWR sdcard into the nook and hold the power button, it will power on. The reason it isnt powering on currently is because your froyo boot partition is corrupted, not because of the nook itself. The CWR sdcard has a different boot partition that your nook will see and boot to when you hold the power button down with the CWR sdcard in.
Click to expand...
Click to collapse
Thats my post from an earlier thread with someone having the same issues. It worked for him, it should work for you. Just make sure you follow the steps right and especially make sure your burning the Clockwork image to your SDcard correctly that way it will boot into Clockwork instead of staying black.

I'm gonna have to give these steps a whirl. The downloads are taking foreeeever.
Also had Froyo installed with CWM and just got finished installing gapps. I went to format an SD card, had no luck, and tried to reboot. Ol' Nookie decided not to come back to life after that.
edit: wait, instead of flashing the stock rom can I flash the pre-rooted 1.1 rom?

Just read this over on android central (in a thread about flashing honeycomb). I believe it is what I did and why my nook won't boot:
****While running Honeycomb from Internal Memory NEVER choose the option to format your SD Card from within Honeycomb. The files that were altered to let HC run internally will lead the OS to actually format your boot partition instead of your SD. If you need to format an SD, do it on your computer or in an Android phone, etc.*****
Click to expand...
Click to collapse
Drat. Just got my CWM image on my sd card. Here goes nothin! Will report back

OK, I have CWM booting off the SD card, i'm formatting system and data under mounts and storage, and then i'm installing the 1.0.1 complete restore. It goes through and then I got to reboot system. Then...nothing. Back to black screen. Help please!
I can pop the SD card back in and boot back to CWM. I've tried several times now with no luck

samuelhalff has a flashable zip that restores the boot partition for situations like this. Go look for it in the development forum. you should be able to flash it using CWR and your NC ought to boot.

eyecrispy, thank you! samuelhalff's boot zip followed by his 1.0.1 complete restore zip did the trick.
RileyGrant, thank you for your post as well. Much obliged!!

Mine just shows a blank screen. All I did was boot into ClockwordMod Recovery, make a backup, then reboot. I was going to flash the Honeycomb Rom, but decided to give it some more thought first. Now All I get is the blank screen, it won't power all the way off, and it won't power on or anything
EDIT: Managed to get it to turn off, but when I turn it back on it boots into recovery. I select Reboot System now, and it reboots back into recovery. Forgive me, I'm so new to this Nook Color thing lol
EDIT AGAIN: Tried using the Monster Pack or whatever, flashed the removeclockwork.zip, followed by the installclockwork.zip, then removed the SD card, rebooted, and went right back into Clockwork Recovery. What gives?

YUP Same thing happened to me. I have read all the posts in this thread and i did try to format the card i had in my nook in the brand new phiremod froyo rom. Now it wont boot at all. I have a CRW card on hand and it wont even boot that. Idk right now, nothing is working.

Try reading through the Dummies Guide to Fixing 'My Nook Won't Boot'.
I did it last night and I'm back up and running again. Here's my post for an abridged version of what I did last night: http://forum.xda-developers.com/showpost.php?p=11374824&postcount=29

I had the same problem until I flashed the repartition fix.
Give that a try

I've got the exact same problem as the OP. Running Froyo on EMMC with no problems for a few days, then I left it for a while and now it wont turn back on or boot from uSD.
I've tried long presses on the power key, usb cable power up, but nothing works. I've tried the v4 HC image and the clockwork recovery image and neither are booting.
I verified the CWR image on my android phone and it does boot on my phone, so the image is definitely okay.
Hate to think it, but could this be a battery management issue in the 0.6.7 image and the battery is now screwed? Doesn't seem like boot partition corruption to me.
Any comments or suggestions are welcomed

ChrisAC84 said:
Mine just shows a blank screen. All I did was boot into ClockwordMod Recovery, make a backup, then reboot. I was going to flash the Honeycomb Rom, but decided to give it some more thought first. Now All I get is the blank screen, it won't power all the way off, and it won't power on or anything
EDIT: Managed to get it to turn off, but when I turn it back on it boots into recovery. I select Reboot System now, and it reboots back into recovery. Forgive me, I'm so new to this Nook Color thing lol
EDIT AGAIN: Tried using the Monster Pack or whatever, flashed the removeclockwork.zip, followed by the installclockwork.zip, then removed the SD card, rebooted, and went right back into Clockwork Recovery. What gives?
Click to expand...
Click to collapse
how did you get yours to turn off, my screen says loading... and is stuck there. any help in getting mine to shut off would be helpful

Does holding power button for a few seconds turn it off?

Same thing happened to me, this fixed my problem: http://forum.xda-developers.com/showthread.php?t=986977

Sorry for asking what's probably a silly question, but I haven't seen an answer. Is this known to the Nookie dev(s) and being addressed? Just had it happen running Nookie 0.6.8 off the SD card. I was really enjoying it and just telling the wife how I think I'll flash it to the eMMC, but I might have to reconsider if this might occur. Battery was ~80%, no goof-ups reformatting anything. Locked the screen around 1:10 this afternoon & hadn't touched it since. Got home about an hour ago to turn it on, nothing. Disappointing, Nookie is pretty good!

nook color wont turn on
so what to do if i dont have a sd card with cwr or honeycomb (what i was trying to run)ive already called for the replacement, but i would still like to know what to do.

I found this thread after suffering the same or similar problem to everyone else. I turned off the screen and set my nc aside for a few minutes, then it would no longer boot. Screen just stayed black and was completely unresponsive to any input. Working my way through some troubleshooting, I plugged the nc into my computer via USB and it booted into CM7 instantly. I have no idea why this happened, but it's working fine now.

Touch the future of reading

Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?

aposva said:
Currently I am running nookie froyo 0.6.8 from the internal rom but I am having the following problem even when I had eclair with autonooter. When I am turning off my nook for the night, in the morning I am stuck at the "Touch the future..." screen and I can only boot through clockwork recovery and choose reboot. I think that it started when I flashed clockwork for the first time, but I am not sure. Any ideas?
Click to expand...
Click to collapse
I am searching the forums to find an answer to the same problem. I am running stock eclair that has been autonootered. I don't have clockwork installed. I can always boot with the sdcard to Honeycomb.. sometimes I can then reboot back into Eclair.

i had this one time, i try the 8 failed boot's to restore, didn't restore but rebooted to eclair!

arf, i'm having the same problem after all..

I had the same thing happen to me had to reformat cache if I wanted to boot into froyo,its a great system but that one problem did me in went back to stock and rooted the NC and plan on staying this way I just give up flash.Looked all over for fix or someone to explain why but never did get an answer sorry i couldnt help you but if i find answer will let you know

ok will look forward when i have time
At this point i can boot by pressing power + n for 30s, it boot to recovery, then i choose "reboot"

Yes that's right, this is the only way I can boot too (power but. + n).

when rebooted i lower setcpu to 1ghz max. it seems to help to boot ..

There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!

I have the same problem too. Just remove the SD card on power on (reboot with software is OK)
Looking for better fix.

Taeseong said:
There are some really good unbricking//"my nook won't boot" sort of threads to be found in the developers section; but this one should be more than enough to fix your issues:
http://forum.xda-developers.com/showthread.php?t=949699
Additionally, I find that reflashing to a stock ROM or restoring a previous working backup image from CWM is the best way to go about it. Good luck!
Click to expand...
Click to collapse
Thx, I'll take a look at that if I ever have booting issues.

Think this is caused by the recovery image. Upgrade your recovery to the latest version 3.0.1.0 and see if that fixes it.
http://forum.xda-developers.com/showthread.php?t=971197

Going to try that today ..I just looked and i do have an older recovery file so maybe that is the problem will report back later on it.

Did the update, I will shut it off for the night and will check it in the morning.
Sent from my Nook Color

I also read CWR does not get along with 1.1..I just updated CWR and it still did the same thing what Im going to do now is clean restore then custom froyo then after setup go to market get rom manager install reboot into recovery and then install the remove crw with root file.

I downloaded the restore to stock zip file. Put it on the sd card. Then used the power and "n" to get to the butloader. Chose install from sd card and it installed. Back to operational!

Need help please

Hey, my buddy let me borrow his rooted NC running the Honeycomb Preview on it. He wanted to see what MIUI looked like on it, and let me put it on there for him. I guess I was dumb to assume this was running Android, so it must flash files like any android phone.
He has some program to boot the NC into clockwork mod recovery. While in CW recovery, I wiped data, but after this, it froze while in CW recovery! I've never encountered this, so I just decided to reboot the thing and go from there. It rebooted and directed me to the set-up screen with the green android dude with the persons hand telling me to press him
"Welcome to LogicPD Zoom 2"
No matter what I press, nothing responds. I read up on http://nookdevs.com/Flash_back_to_clean_stock_ROM#ixzz1AAsuy5td and tried to accomplish the 8 restart thing. I don't think I can complete that because whenever I boot up, it immediately puts on a splash screen that says "Loading.."
No part of the boot cycle does it say "Welcome to the future of reading"
Is it possible flashing this thing back to stock? I tried to tap into adb, so I could put it into bootloader from there, but my adb doesn't recognize it. Even with the "adbfix.bat" file.
Any help will help.
Thanks

First, load an image of CWR v3.2.0.1 on an SD card. Then, get a CM7 ROM and the market app .zip file and put them on the card and you should be good to go. Older versions of CWR tend to freeze up when wiping the cache....
In my opinion, no one should be running Honeycomb on the Nook unless off an SD card as a secondary "toy".

Well thanks for the suggestion. I couldn't boot into any kind of recovery mode, which made things kinda confusing.
I fixed my adb issue, so luckily, I could log into adb. I cleared data and cache through adb, and than downloaded the boot.img file and system.img file. Pushed those to the nook that way. Now I'm back to out of box status ready to put some MIUI goodness on here.

Droid 3 seems to be unbrickable

I've tried many different things in alot of the threads I've read on this forum and nothing is working. I tried using the One-Click root on my Droid and it didn't work, come to find out, it was an outdated method for the Droid 3. It messed up my phone. My apps constantly crash. My texts disappear, then sometimes reappear switching the place of the texts randomly. When I reset from settings, it restarts phone, but nothing is reset. It won't let me check my e-mails(G-mail). I can hardly do anything. I've tried flashing back using the AP Fastboot method from psouza(spelling?). On my phone it says Battery OK/Program OK/USB Connected. So I run the "CLICK HERE - Flash Verizon DROID 3 OTA 5.6.890 to phone.bat". It failed.
Then I tried ovelayers method. Everything seems to go good. And I was happy! But when it rebooted, it took me to the android triangle screen. SO I selcected reboot. And absolutely nothing changed. Am I Missing a step? I also tried doing it again, but after it went to traingle android screen, I selected the update from the SD card, installed it, rebooted, and STILL nothing. Nothing changes. Ever. Nothing is working. Please help. I tried being as descriptive as possible so that it answers most potential questions.
*Edit* I've also tried the RDS Lite method. Crashes on step 3.
Phone specs: Version: 5.7.906.XT862.Verizon.en.US
Kernel: 2.6.35.7-g5fa4155
Android 2.3.4

download full system file
http://dev-host.org/uEA
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all

Make sure you use the sbf for. 906 and not the one for. 890
http://d-h.st/mvX

niko99 said:
download full system file
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Click to expand...
Click to collapse
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.

xJolly said:
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
Click to expand...
Click to collapse
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed
http://db.tt/pi5c484a
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there

DoubleYouPee said:
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed.
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
Click to expand...
Click to collapse
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".

xJolly said:
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
Click to expand...
Click to collapse
First you need root access. Use Motofail if you haven't:
https://www.dropbox.com/s/wpl88mwm6eilhe6/motofail.exe
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there

DoubleYouPee said:
First you need root access. Use Motofail if you haven't:
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
Click to expand...
Click to collapse
Figured. My phone won't root. Like I said, nothing will change about it.

xJolly said:
Figured. My phone won't root. Like I said, nothing will change about it.
Click to expand...
Click to collapse
Ok so what about x+power?

DoubleYouPee said:
Ok so what about x+power?
Click to expand...
Click to collapse
No. It doesn't work. I've tried that.

xJolly said:
No. It doesn't work. I've tried that.
Click to expand...
Click to collapse
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore

DoubleYouPee said:
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
Click to expand...
Click to collapse
I'm going to record a video. And show you the multiple things that happens. I'll have to PM it to you though, and anyone who wants to see it.

I remember someone else having a similar issue on their device. Since I'm home sick today I'll see if I can find the thread and if it ever got solved
Sent from my XT860 using xda premium

Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.

DoubleYouPee said:
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
Click to expand...
Click to collapse
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.

xJolly said:
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
Click to expand...
Click to collapse
You're right. No way you can send it back for replacement? Your phone seems stock

DoubleYouPee said:
You're right. No way you can send it back for replacement? Your phone seems stock
Click to expand...
Click to collapse
Well, I don't have insurance on it, as I had gotten it from a friend. So, no. Not without paying an arm and a leg, at which point I'd pay for a new phone instead. I just really wish this could be fixed. I've heard no phone was unbrickable. AM I THE PRODIGY?!