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."
Related
Background on the bootloop issue first posted here:
http://forum.xda-developers.com/showthread.php?t=897683
Gist:
1.0.1 - Autonootered and auto config'd with SetCPU running and some other apps Market loaded and side-loaded.
Came home to see it bootlooping. Tried 8X reboots and 3 Finger Salute (VOL+,N, PWR) on separate boots, both didn't change the situation.
Autonooter nor Nooter0.2 will allow PuTTy to SSH in (maybe I'm doing it wrong)
ADB shows nothing
CURRENT state of effedness:
The battery has exhausted itself. It won't boot on due to low battery. After plugging it in... it keeps trying to boot instead of building enough surplus. Now, I'm in a cycle of bootloops mixed with not enough juice errors. This is the most bricked state I've ever had a device, but I think I can recover somehow.
Problem:
I can't return it because the person at the store will see that its rooted. I could try to kill the battery and return it late at night hoping they won't be able to boot it to even check its rootedness.
As I posted in your other thread, try putting in an autonooter sdcard and then plug into usb and see if it will boot from that card.
Good luck.
It still doesn't meet the correct definition of "bricked"
I had the same problem after monkeying with /rom/devconf/BootCnt.
I ended up booting off the Froyo SD card and fixed BootCnt via ADB.
Pinesal said:
It still doesn't meet the correct definition of "bricked"
Click to expand...
Click to collapse
technically... most likely not... but currently i have nothing more than a paper weight with a usb port. No recovery, no bootloader, no adb...
I just put an autonooter card in there and its sitting at the 'N' screen
but PuTTy times out... and I can't ping 192.168.2.2 ...
what should I see in Device Manager (win7) for the RNDIS device?
edison said:
I had the same problem after monkeying with /rom/devconf/BootCnt.
I ended up booting off the Froyo SD card and fixed BootCnt via ADB.
Click to expand...
Click to collapse
I thought about this... but was afraid of it not working / putting me in a deeper hole...
*looking into making a Froyo card now*
Last post before I leave work
Before I go and make a Froyo card, (All my 2+GB cards are at home) I see that there is an update that I needed to do before getting RNDIS working on my Win 7 machine... so I updated per these instructions: http://nookdevs.com/NookColor_USB_RNDIS
but no RNDIS device is showing with the Autonooter card in there.
Any ideas? Gonna try a few things when I get home... hopefully will have this thing put to rest by tonight.
Brick level reduced
Nookie Froyo boots... now how do I edit the BootCnt?
with terminal?
cal3thousand said:
Nookie Froyo boots... now how do I edit the BootCnt?
with terminal?
Click to expand...
Click to collapse
Some good reading here about Bootcnt: http://nookdevs.com/NookColor_Fix_Boot_Loops
Have you tried this Full OS boot from SD
http://forum.xda-developers.com/showthread.php?t=873243
cal3thousand said:
Background on the bootloop issue first posted here:
http://forum.xda-developers.com/showthread.php?t=897683
Problem:
I can't return it because the person at the store will see that its rooted. I could try to kill the battery and return it late at night hoping they won't be able to boot it to even check its rootedness.
Click to expand...
Click to collapse
Why can't you return it? If it doesn't boot, how will they ever know unless you mean the animation is still visible...
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 =)
First and formost Ive searched the forum and can not find a problem like the one i'm having. This is time sensitive because i sold my nook and am supposed to ship today.
I was running CM7 on internal no O/C. I also had CWM installed and working great. I was running on nightly 33. Well in an attempt to clean the device out i couldn't get my google email address to go away. So i decided to do a fresh install. Well In hast after a google search for encore cyanogen mod I saw RC1 pop up. OK great i didn't know there was any release candidate, i'll install that. So i made a bootable SD card, copied this RC1 and G apps. Threw it in, boot into cwm, installed both files, loaded into CM7. Success so i thought. Untill i notice all the things that werent working. No problem i'm a dumbass i'll download the latest nightly and flash all over again.
I shut the device down, and now it will not turn back on.
(I've think i've tried every combo of buttons and its fully charged)
PLEASE PLEASE PLEASE HELP I HAVE TO SHIP THIS TODAY!!!
UPDATE: When the NC is pluged in the computer and i press power the computer makes a noise as if its discovering a device. I don't know if this helps.
UPDATE 2: I think I know what i did but do not know how to fix it. In CWM i wiped data/cache.
Did you read the very first post pinned at the top of this forum?
Please delete thread!
Wow, no i did not!
MOD: Please delete thread!
Long story short, went to Thailand, NookColor battery died, was dead for around a week, when I charged it and tried to turn it off I am stuck on "Touch the Future of Reading."
Running Nookie Froyo emmc, everything was fine before.
Tried removing the SD card to boot as I read in another thread but that hasn't changed anything.
I haven't run that particular ROM, but I would just try to reflash the ROM without clearing data.
MikeRukas,
I've got the same problem. Did you ever get it resolved? I'm desperate.
Thanks!
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.