My first post, long time reader and have learned alot but I am stumped...
My situation: Nook Color rooted way back in Decemeber, has worked like a champ. Yesterday I was reading and found the overclocking process. It mentioned downloading and installing the ROM Manager, which I did. Got the overclocking zip and tried to set up to install. Upon reboot, my screen flashed white and went directly to "Touch the future of Reading". I have tried everything suggested here and everywhere else on the internet. I have burned, formatted, reburned and still I don't see anything that would tell me it is even looking at the sdcard.
I am really disappointed in myself for not doing some more reading. But I am hopeful someone here can direct me in a good direction to get the damn SD to boot.
I have no data or software that I can't reload or reinstall later. I just want the thing to work.
Related
I'm not a total noob to rooting as I've already rooted my G1 and am running cyanogen's mods for months now. My problem is on a different phone.
This dream was dropped in water months ago (that's when I purchased my 2nd on craigslist). The touchscreen wouldn't work so I was stuck at the setup screen. I read on many forums, xda included that it might eventually dry out and today I found that it was indeed working fine.
It works fine on stock 1.5 ota update crc1 but now that I rooted one I want this one rooted as well. This is where my problem starts. I'm trying to rollback using the dreaim.nbh found inthe latest "how to root" thread in the dev forum. Problem is I can't load the image. I powe up holding camera and power button, get to the multicolored bootloader, insstructions on the grey/whitish screen say press power button to load, and then I am stuck.
Power button does nothing and the phone is stuck on that screen until I pull the battery. Been through this process 5+ times, with redownloaded image (file is not corrupt) My concern is Ill end up bricking but I really want root. I'm think their might be water damage on the phone but everything else works fine.
Any suggestions for a workaround or a way to troubleshoot the problem? Thanks in advance!
-Air
nbh
heres a link to where you can get the nbh dwnload this one nd try agian.
http://coolpstuts.blogspot.com/2009/07/all-download-links.html
no dice
pistol thanks for the try but it didn't work. same 87.3mb file, rc29, same result.
the greyish white screen loads, but the update (rollback) never starts. Does anyone know of another way to load the dreaim.nbh image? or heard a similar issue?
are you sure you grabbed the t-mo image?? go to the original how to root your phone thread and grab the t-mo image, nothing has changed so there is no reason for us to have an updated thread other than to confuse people even more
my problem is not the rc29 image
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Was not implying that this thread would be a how-to and confuse people, merely that we have so many and people are constantly asking how to do something even though the steps didn't change. The physical abuse your phone has sustained "should" have no effect on the image flashing. I would suggest you format your card again(not in windows as windows seems to screw up a lot), so long as you are using the correct image and a fat32 formatted card you shouldn't have any problems, does the screen pop up and say "no image found"
airmaxx said:
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Click to expand...
Click to collapse
hmmm, have you tried re-formatting your card?
trying it now
reformatted at home using gparted but I'll try paragon now that I'm at the office.
tubaking, thanks for the advice and willingness to help. it does not say no image found. It actually shows the steps that it needs to install including, radio_vz, and a few other things i cant recall right now...
hopefully the reformat will do the trick. I will try to format the entire card fat32 for now and then add my ext3 after. reporting back shortly....
still not working
so reformatted again to fat32, used paragon, gparted, and built in format on the G1 still the same result
grey white screen, reads the image.... then stuck at:
Code:
DREAIMG.nbh -
BOOTLOADER -
RECOVERY -
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_VZ -
Press power button
to start update image
Press action button
to cancel update image
and then I'm stuck
So even after you press the power button to start the update, it just stays at that one screen and never gives any "ok"s next to any of the listings?
exactly
no oks, just hangs there
I've been letting it sit since before my last post, about 45 mins so far and still nothing. I may have imagined it but when i did this process last week it felt like it was getting hotter, but still nothing happened
also I remember doing this on my other G1 that is already rooted, so I know how easy this step should be
Stupid question, but are you making sure not to rename the original DREAIMG.nbh to anything else other than what it is? Some people make the mistake of thinking they have to rename it to update.zip or make the mistake of not leaving it in capital letters (although I don't know if that matters). You have said you have downloaded the file multiple times so I doubt this is the case but I'm just spitballing here
no rename
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
airmaxx said:
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
Click to expand...
Click to collapse
I wasn't suggesting to rename it, I just wanted to make sure that you never had renamed it to anything but the original filename DREAIMG.nbh
its all good
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
airmaxx said:
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
Click to expand...
Click to collapse
I re-read your original post and was curious as to whether the power button could be the culprit considering that its needed to flash the image. Perhaps the water may have damaged the power button interface. I can't imagine that it would be the problem considering your able to get into the rainbow screen via power+camera. Have you tried pushing it harder, many times, on the side etc?
i did, tried holding it for a 10 count, multiple presses, long press. I'm pretty sure the problem is not with the button itself because it works fine when I have the phone booted up and press power to turn it off.
When I first posted I was hoping someone might know of an alternative button combo that might have the same effect of loading the image from that greyish white screen
there is no way to write the image through adb right?
Hi guys! Loving the autonooter - awesome work! I successfully rooted and am loving a 1.0.1 NC.
But, I tried to do the same for a friend with the same SD card with the 1.0.1 version of autonooter, stuck it in without thinking - and it turns out he had 1.0.0. I tried to reset the device - first with the power+volume+N - but this left softkeys on there and no way to uninstall it. So, I did the 8x reboot deal and it started doing the rom flash: "New updates are being installed. This may take a few minutes." All looked good...
Except it rebooted right back to the install screen again. And keeps doing so. I read a post from someone who had this problem and theirs snapped out of it. This NC doesn't seem to want to
Any help would be really appreciated
You might try making an sdcard with the autonooter for 1.0.0 on it and then sticking that in the NC. Then plug in the usb cable and see if it will boot with that. Wait and then follow the directions for the 12.15 autonooter (isn't that the one for 1.0.0?).
I just read a post about someone getting out of a tough boot loop by making a Nookie Froyo card and booting that. Here's the link: http://forum.xda-developers.com/showthread.php?p=10358375#post10358375
Good luck.
Thanks! I did try the -15 (1.0.0 autonooter) ...but it seems to just get stuck at a black screen (waited ~15-20min).
The Nookie Froyo card might be a good bet if I can't get it to work with the putty.exe boot fix...I just realized that's based off a nooter0.2 card so I made one. Here goes nothing!
Thanks for the input though, I really appreciate it - I'd hate to brick my friend's NC.
*Update* nooter0.2 and putty.exe didn't work - getting a "network connection timed out" error
Going to try the Nookie Froyo 0.5.6 card *crosses fingers*
Success!!
Using Froyo on the card allowed ADB access - from there, reset the boot counter. Powered off the NC, powered it back on - install screen came up again, so a little worried loop would continue - *sigh of relief* Barnes and Noble name popped up.
Back to stock! And now updating to root Thank you thank you!
Hi tarheeldan,
I think i am having similar problem as you did before. Could you elaborate a bit more, so i could follow your steps. I am not very good with ADB comment. After making Froyo Card, What's do you need to do. Thank you for the help.
"Using Froyo on the card allowed ADB access - from there, reset the boot counter. Powered off the NC, powered it back on - install screen came up again, so a little worried loop would continue - *sigh of relief* Barnes and Noble name popped up."
I followed the instructions in forum.xda-developers.com/showthread.php?t=938200 and everything worked great. I took out the SD card and I rebooted a few times and it was working perfect.
The problem came when I reinserted the SD card and it wouldn't read from it. So I tried to format it in the NC and realized that wasn't working either. So I shut down my NC, formatted the SD card on my PC and when I attempted to turn it back on.... it is as if there is no battery installed.
I can't get any sign of life from my NC and am getting frustrated. I can't even get it to be recognized in adb because it is completely dead to the world.
Help!
don't worry. Just put another bootable image onto you SD card, and boot from you
SD card. It should work. NC is very hardy because the priority boot is from SD card.
Thanks for the quick reply.
I don't know why but I finally realized that I can only get it to boot from the SD by pressing the N button + power at the same time.Now I am following the instructions to return it to stock
Wish me luck
Or flash my boot repartition file found on my froyo on emmc thread. If you had read the thread, you would know that formatting the SD with your NC with froyo/emmc distroys your boot partition. Only way to boot again is to flash the boot file......
Please, read threads. Don't use stuff boldly without having a clue and then ask for help when questions have been answered several times... this is getting annoying...
Sorry, it is.
Sam
Sent from my HTC Desire using XDA App
Sam, please don't give us the "this is getting annoying" thing. Your directions may be "perfect" but I rarely see directions here or anywhere else that exactly match what I am looking at on my screen. If you've never had a problem trying these types of things you aren't trying hard enough :^). Circumstances vary for each of us.
My NC is dead and pressing the power + N don't work for me. Any other ideas?
Don't worry, been there, done that. I just take time to read threads before asking questions.. So far, I've only seen one "bricked" nook. And technically, it wasn't bricked, as you could still boot off a bootable SD..
Read the threads around in general and dev about bricked/not booting NC's. I'de be very suprized if you didn't find a way out..
Still. It is anoying. Every thread on Froyo/eMMC mentions specifically the problem with Android format and boot corruptions.... So if people did read, no threads like this one would even exist... Plus, there are tons of threads on "bricked" nooks..
PLEASE, take time to read. It's a win/win choice I can promise you..
And please don't tell me what I should or shouldn't "give you". Look around, though I sometimes get tired, I'm always around helping others, and always have been for a few months now..
Thank you.
Sam
No good deed goes unpunished
I have found that when I help people they always ask for more. Have a great day.
One of my friends used to give people an immediate answer to their problems and they never were happy. So he said, "This is a real tough problem, let me research it", and then gave them the answer two weeks later. They were much happier thinking that they really had a tough problem.
just got nookie froyo installed, but am having a problem. I can't install anything from the market...and am also getting google talk authentication failed?
When I try to install youtube for example. "Download error, download was unsuccessful, please try again" and same thing with flash. using the latest nookie froyo and i followed directions in the OP. Thoughts?
coreyjohnson711 said:
just got nookie froyo installed, but am having a problem. I can't install anything from the market...and am also getting google talk authentication failed?
When I try to install youtube for example. "Download error, download was unsuccessful, please try again" and same thing with flash. using the latest nookie froyo and i followed directions in the OP. Thoughts?
Click to expand...
Click to collapse
Go to settings/applications/manage application (choose all). Scroll to google services framework, press on it and select clear data/force stop. Then go to market and clear cache. Reboot, all should be well.
thank you, that is why i love the xda community =)
hi everyone. i've been following the forum here for awhile and finally decided to root my brand new NC. i autorooted from 1.1. i saw some things weren't working so i quickly decided to unroot back to factory settings. i unrooted by unregistering the device and turning off the power 8 times. my NC boots up fine, but it gets stuck on the "Registering your Device" page and just remains there with the circle spinning. i think i left it there for more than 30 minutes and nothing happens. has anyone experienced this before? if so, how did you fix it? any help would be appreciated.
sorry if this topic has already been asked - i tried searching but didn't find anything on this specific issue. if there's already a thread, please feel free to share the link with me. thank you!
EDIT: really need some help here... i tried to fix it myself (i know i shouldn't have) and might have made it even worse. i tried to re-autoroot my NC but just completely failed. it was not loading anything anymore, so i tried to unroot again by powering off 8 times. when i restarted, everything looked normal, except the bootloader screen was not stock. it brought me back through the normal tutorial and same thing with it getting stuck on "registering your device". could someone please provide a thorough walkthrough on how to reset to factory settings? i'm seeing all these threads throwing around all these acronyms that i don't understand. seems like i need to try running some clockwork rom but not even sure how to do that. please help!!
Bump, i have just encountered this problem and i need help as well.
Update:
actually just figured it out and heres what fixed my problem, i wasn't doing the factory reset part only the 8 reboot interruptions.
hxxp://nookdevs.com/Flash_back_to_clean_stock_ROM
Thanks for your post, even though no one ever helped. I was having the same problem and doing a clear data/factory reset from Clockwork Recover booted from an SD card did the trick for me.
Hello All,
I'm fairly certain there isn't another thread asking this question, if I overlooked it I apologize in advance. Now to the point, I have a dell streak 7 and I have been having some stability issues with it for about the last week. What was happening is I was running Android 2.2.2 and my system would crash randomly eventually it wouldn't start back up. I tried doing a factory restore several times this didn't work so I re-flashed to restore the original file system and I installed the T-mobile system by mistake. I played around with this for a little bit and every thing seemed fine. So I decided to upgrade to 3.2 honeycomb, I flashed the DS7 did all of the set up steps and started reading about rooting the device (I didn't start any of the steps). While it was sitting next to me in sleep mode I noticed it just randomly reset itself and started booting up. I looked around in it and nothing seemed to be changed, so I powered it off and powered it back on to see if it would freeze up and crash again. it didn't so I put it back in sleep mode and kept reading. then the side lights came on and it froze up. I was able to get it to boot by going into recovery mode and then selecting boot normally. So my question is, is this some sort of hardware issue or something that I am doing wrong? I don't think it's hardware but I could be mistaken. Also, has anyone else had an issue like this and if so is there a known fix? I am going to try re-flashing to the original file system again and replace the restore .img and see if this helps. Also, I'm not sure if my DS7 is the mobile version or wifi only version. I entered the service tag at DELL's website and it said I had the mobile version, however it didn't have the t-mobile start up animation before I flashed it the first time and in the sim card slot there is a black piece of plastic or card (IDK which) lodged in there and it wont come out. Any help or advice on this would be greatly appreciated .
Thanks in advance-Woulfenstien
OK I'm pretty sure i got it solved. what I did was I re-flashed everything. I re-flashed the boot.img, the system.img, and the recovery.img using fastboot and then i re-flashed whole system with nvflash. It's been a couple of hrs. and this has seemed to work so far. I upgraded back to 3.2 honeycomb and rooted the device with no problems so far. If any other issues arise I will post them here along with what i did to fix it. I would also like to thank everyone on this forum who has posted the tutorials, it was a huge help I wouldn't have been able to fix my DS7 with out all of your help.
Thanks again-Woulfenstien