Database Develop

Afraid I have a $250 paperweight..root issue

As I have posted in a development thread about rooting..
Alright guys, I have a problem. And there is very little info about doing this on a Mac
I have created the autonooter2 sd card using terminal.
My nookcolor is powered off, sd card inserted, nook USB cable plugged in to nook and then computer. (nook symbol lights up on cord), my mac pops up and shows a RNDIS ethernet device
-1 st problem, It says on nookdevs that this RNDIS dialog will pop up and to ignore it...does that mean ignore it, leave it there or click cancel? I have tried ignoring for a while and then clicking cancel.
- It says both here on xda and there that when the autonooter is finished the nook should reboot itself..its been 10 mins this never happens??
any help is appreciated
edit:
alright I just unplugged the USB and turned on my nook and it brought me to the Android setup screen. I skipped the tutorial and sign in and checked both location boxes and then when I clicked continue the screen flashed and it threw me into the normal B&N interface and the nook color user guide automatically popped open and starts flipping pages rapidly. I can close out of the user guide but then it auto reopens :/
edit2: restarted , everything appears to be working alright except I cannot pull up a keyboard in any instance...searching store or through books
edit3: i have tried erasing and un registering my device. my nook is now unregistered. I have been trying to get rid of root. i have cleared data ( power+ volume + nook button) but I cannot factory reset using 8 reboot method.
My device is on, has NookColor settings under extras but I have no keyboard and cannot connect to wifi or re register..
Please.... help

You should register your NC prior to rooting it. You can restore your nook to its fresh state by interrupting the reboot process 8 times or, using the Android Debug Bridge (instructions for enabling it here: nookdevs.com/NookColor_USB_ADB) by following these instructions: nookdevs.com/Flash_back_to_clean_stock_ROM. Once you're done with that, register your Nook and then follow the AutoNooter instructions (nookdevs.com/NookColor_Rooting). Note: autonooter will reboot by itself once it's done; don't interrupt it by restarting the nook by yourself!

Ok quick question..
I figured I could not do any more harm so I started the autonooter process over from start to finish remaking the sd card but this time on a PC.
Everything worked better, the nook auto restarted itself and I got the Nook Color Dev screen and then to the unlock screen. I unlocked, ready to do the next steps (skipping tutorial and skipping gmail sign in) but I was never prompted. I am just at the normal nook homescreen, I now have much more options in extra( superuser, email, etc) and also the soft keys but I still do not have a keyboard.
Since I did this autonootering from an unregistered device do I need to start completely over?
Thank you for your response

foethalove said:
Ok quick question..
I figured I could not do any more harm so I started the autonooter process over from start to finish remaking the sd card but this time on a PC.
Everything worked better, the nook auto restarted itself and I got the Nook Color Dev screen and then to the unlock screen. I unlocked, ready to do the next steps (skipping tutorial and skipping gmail sign in) but I was never prompted. I am just at the normal nook homescreen, I now have much more options in extra( superuser, email, etc) and also the soft keys but I still do not have a keyboard.
Since I did this autonootering from an unregistered device do I need to start completely over?
Thank you for your response
Click to expand...
Click to collapse
It doesn't sound like you have anything resembling a paperweight, I'm sure you'll get it to where you want it.
Did you try the steps of signing in youtube then gmail, then market? If your only problem is a missing keyboard, that can easily be remedied. Get the apk of a keyboard that's known to be working (there's a thread in the NC section on the DroidX kb), and push it via adb as system/app/LatinIME.apk. Reboot, and you should have a keyboard.
You said you can't do the 8 failed boot attempts... Why not? All you have to do is power-down 8 times during boot (hold down power for about 10 seconds, then hold down again to power on... Repeat 8x).

Hey,
I'm kind of in the same position that you were originally in. My NC's firmware is 1.0.0. I used the guide on nookdevs.com, flashed my SD card w/ the proper image, inserted the card, plugged in the USB, and... over 30 mins and nothing.
What did you do once you were in this step to continue? Did you remove the SD card?
-Taser
edit:
wvcachi, that's actually exactly what I ended up doing, and it came right up - thank you!
Also, I ended up doing this (sorry, no linking allowed - nookdevs.com/Installing_the_1.0.1_update_on_a_rooted_NC), re-rooted, and the 1.0.1 root actualy did auto-reboot.
Thanks eveyone for your help, and OP for not getting too ticked I hijacked their thread

Taser420 said:
Hey,
I'm kind of in the same position that you were originally in. My NC's firmware is 1.0.0. I used the guide on nookdevs.com, flashed my SD card w/ the proper image, inserted the card, plugged in the USB, and... over 30 mins and nothing.
What did you do once you were in this step to continue? Did you remove the SD card?
-Taser
Click to expand...
Click to collapse
Ya same issue here, except now my nook is stuck at the giant n. It was responding to my adb shell commands to to the 8x reboot for the BootCnt. But after it did the update it still sits on the giant n. I'm not sure what is screwed up on mine. I wonder if the auto-nooter just messed up some how...
I was upgrading from 1.0.0 to 1.0.1 to fix my wifi drop issues.
Edit: Just let the n sit there for a good 15 minutes. I've never been so happy to see that intro video with that girl showing you how to use the nook!
Will try to auto noot again...

I've done auto-noot several times now, and it's never rebooted on its own. After a couple minutes of it doing its thing, I just unplugged it, held down power for 10 seconds to power off (it's on even though it doesn't look like it), removed the SD, then powered on. Everything was as expected after that, it just never rebooted on its own.

Mine from 1.0.1 behaves exactly like the wiki described for me. Ran with the screen off for about 45s and then rebooted and was good to go. I followed the post instructions to set up the account and everything went exactly as they described. Only difference was it seemed to me like the instructions duplicated themselves at one point, steps in had already done were listed.
Works great, but might should revise the steps of there are duplicate ones. If I remember or root again I might do it. Adding renaming the phone apps woukdvbe a good thing to do too.

The version of Auto-nooter for 1.0.0 doesn't auto-reboot after it's done. You'll have to let it sit and reboot yourself.

I strongly recommend you upgrade to 1.0.1 before you root anyway. It's more stable, and when you eventually upgrade, you'll have to wipe your nook to do it. Better to do it while you don't have anything on it.

Thanks to everyone that helped out. I have everything up and working!

[Q] rooted OK but now it continues to try to boot

I rooted my NC yesterday using the auto-nooter 2.12.25. Things seemed OK. I DLed some apps & used them. Got ADW launcher loaded and began setting it up for my preferences. The NC went most of the way through an update cycle even though I had already updated to version 1.0.1. However this time it never got to the green "n" and then it started cycling through the part where it comes up & writes "nook color", continues until the colors quit flashing & then starts back at "nook color".
None of the buttons seem to have any effect. I tried to follow the 'solution' entitled "NookColor Fix Boot Loops". I tried both the auto-nooter SD card and then when that didn't work, I tried the original manual nooter SD card.
Anyone have another idea to fix this. I'd really appreciate some help. A PM would be great or just answer here.

I had the same problem earilier today, I held down the power button until it did a complete reset (about 8 seconds of holding). It is working great since.

Thanks. I had already tried that, several times.

restore to factory and start again?
add http : // www to front of links with out the spaces i don't have the 8 post count needed to post links and
am not going to just reply needless info to 8 post to get rights to post links to help
don't get me wrong i believe it is a very good policy
unrooting
.nookdevs.com/NookColor_UnRooting
flashback to clean stock
.nookdevs.com/Flash_back_to_clean_stock_ROM
i have not tried any of these methods no need to but i do so much messing up
i guess eventually i will with that said this might be a long way around to your solution
read both carefully

Thanks, nookroot but this is not working.
Method 1 for unrooting - Holding those 3 keys together for over 30 seconds has no effect.
Method 2 for unrooting - I can't unroot with method 2 because the NC has to boot before I can go to settings.
Any other suggestions? In fact it seems that if it ever does power off, the only way to make it power on is to plug in its USB cord & this doesn't always work. When it does it just stats cycling. Sometimes it seems to just power up on its own and start cycling.
Whatever happened, since it's rooted I can't return it to B&N and I don't seem to be able to unroot it. Effectively I have bricked it even though many people say that's impossible.
Edit: something new just happened & I was able to go through the method 1 reset. It's booting now & looks like the B&N screen is coming up. I'm not sure how it happened. I'm going to leave it unrooted until I feel adventurous (or foolish) again.
P.S. Came back with version 1.0.0 SW.

Power button won't turn on NC

I'm rooted with latest Auto-nooter as of last night. The power button on the side works fine with turning off the screen and turning it back on and with turning the device off with a long hold. However, once its off, the switch won't turn the NC back on and I have to plug in the usb cord in order to turn it on and it takes a while. Anyone have this problem and find a solution?
This is my 2nd NC and the first one didn't do this, although I might be returning this one too because the bezel is a little loose in one corner.

Read this...
http://forum.xda-developers.com/showthread.php?t=871996

epakrat75 said:
Read this...
http://forum.xda-developers.com/showthread.php?t=871996
Click to expand...
Click to collapse
Sorry please move this to the General forum

I had the same problem with my first run of autonooter. I already had youtube, su, etc when I tried autonooter, which may have been the issue.
To resolve it, follow the instructions to completely wipe nook (system and data areas). Install 1.0.1 update. Then run autonooter again. Be sure to pull the usb cord when nook reboots after autonooter has done its magic. Doing this fixed mine. Good luck!
Sent from my LogicPD Zoom2 using XDA App

Remove the autonooter card. replace it with a fresh card so that you can actually use it.
Sent from my rooted droid x

Syco54645 said:
Remove the autonooter card. replace it with a fresh card so that you can actually use it.
Sent from my rooted droid x
Click to expand...
Click to collapse
thanks I just formatted it right within the NC and now it boots up with the power button, lol. Thanks.

tomtbone said:
thanks I just formatted it right within the NC and now it boots up with the power button, lol. Thanks.
Click to expand...
Click to collapse
Are you the same tomtbone from VS?
I did it all from my Nookie...

cal3thousand said:
Are you the same tomtbone from VS?
I did it all from my Nookie...
Click to expand...
Click to collapse
why yes I am lol. moving on to Swedespeed with my S60R though. THe 855R is sitting in the driveway collecting dust.

CRAP!!!! Black screen and won't go into recovery!

I think I just messed up big time...I tried to install the revo power menu mod and my revolution only boots through the verizon logo and goes to a black screen. I had just put MTs Home-Less on my phone. I tried to start my phone by pressing the power button and volume down key and it just does the same thing....black screen.... Any help? My laptop no longer recognizes my device either....
Major Edit: OMG I can be such a stupid-brilliant-mother-effer. After pulling the battery a thousand times- so it seemed- I finally got it to hit recovery. I just did a restore and we'll see what gives.
Omg...Can I just delete this post and act like this never happened. It's back. Now I just need to figure out what I did wrong. I followed the steps. Could this happen because my battery was too low?
BTW...I'd love to thank this forum again...The info is endless and TheCubed and the Mt Guys are amazing from what I have learned thus far. Many others on here have been so amazing as well. Thank you all for "laying it out there" for others to learn. About a month and a half ago, I was so ignorant when it came to rooting and such. Now I've flashed this and that - roms that is- and I've "jacked up" my phone and "unjacked" it.... all from the help of this forum.

RootThese said:
I think I just messed up big time...I tried to install the revo power menu mod and my revolution only boots through the verizon logo and goes to a black screen. I had just put MTs Home-Less on my phone. I tried to start my phone by pressing the power button and volume down key and it just does the same thing....black screen.... Any help? My laptop no longer recognizes my device either....
Major Edit: OMG I can be such a stupid-brilliant-mother-effer. After pulling the battery a thousand times- so it seemed- I finally got it to hit recovery. I just did a restore and we'll see what gives.
Omg...Can I just delete this post and act like this never happened. It's back. Now I just need to figure out what I did wrong. I followed the steps. Could this happen because my battery was too low?
BTW...I'd love to thank this forum again...The info is endless and TheCubed and the Mt Guys are amazing from what I have learned thus far. Many others on here have been so amazing as well. Thank you all for "laying it out there" for others to learn. About a month and a half ago, I was so ignorant when it came to rooting and such. Now I've flashed this and that - roms that is- and I've "jacked up" my phone and "unjacked" it.... all from the help of this forum.
Click to expand...
Click to collapse
Are you sure you did the right one for the revo mod? There is a specific file for the home-less rom. If not, that is why you are getting the black screen because it is looking for a homescreen that isn't there. Go back into recovery, wipe, re-install, and install the correct file.
Hope this helps.

I got it now...I don't know what I did the first time. I tried it all over again with the same file after I charged my battery more and everything worked out fine...that was fun.

[Q] I think I Bricked My TP

I was following these instructions http://forum.xda-developers.com/showthread.php?t=1305891
And under step 3 section where it says create a folder called cminstall, I was unclear if that was on the TP or on my PC. I created it on my pc. I follwed the rest of the steps and when I ran novacom my TP did it's install thing and then at the very end there was a message
"no cminstall dir found, nothing to install.
Power off when ready"
I guess cminstall was supposed to be on the TP. No I can't turn it off. I tried the power button, I tried the power and volume up button, and the center button and the up button, nothing.
Am I hosed? If I can't turn it off how do I web doctor it to get back to webOS?

Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.

justfor4 said:
Try to press Power + Home for 20-30 sec. Then it should go to power off.
Afterwards start fresh.
Click to expand...
Click to collapse
Yeah I just found that button combo on the webos nation forum. Dammit I just made a useless help me thread.

Well, though that this its true, the issue is solved.
And this is thankfully a good thing...
Great

I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk

lvpre said:
I had an old palm pre and it was impossible to brick. I did the metadoctor a few times to upgrade to webos 2.0 and when something went wrong, I just used the webos doctor to fix it. Palm was really good about that. Webos is awesome, but the lack of apps killed it.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!

VGSmatt said:
Yeah lack of apps is why I went to CM7.
BTW after a TP reboot and refollowing the steps I am now on CM7!
Click to expand...
Click to collapse
Why don't u test the xronified version? U will be happier

+1 happy user of xronified version

klear72 said:
Why don't u test the xronified version? U will be happier
Click to expand...
Click to collapse
What makes xron better? After only one day, I like cm way more then webos!

Leoisright
VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
Too many..or only...Leoisright !!! I've never known anyone who works much as he did and now with the help of MiSfit it will be even better
http://forum.xda-developers.com/showthread.php?t=1321335

What makes xron better?
Click to expand...
Click to collapse
It's faster+beter games support+some fixes like wi-fi. Check benchmarks of cm a3.5 and latest xronified version

VGSmatt said:
What makes xron better? After only one day, I like cm way more then webos!
Click to expand...
Click to collapse
the rom developer leo has been so enthusiastic and has been pushing updates one after the other in a regular basis and the rom is fast. you will see it when you try it . moreover few more devs have just joined the development which in my opinion is going to make the rom rock

ok before i got to into cm7, i made the jump to xron. You guys were right, its pretty fantastic.

You can't brick your TouchPad.
It's not possible.

Yeah, I may have panicked a little when all the button combos I knew weren't working. Then I found the correct button combo on the webos forum.

I'm having an issue. I was prompted to update to webOS 3.0.4. Long story short after and hour and a half with the black HP screen coming and going I decided something probably wasn't right. I downloaded webOS doctor and am trying to run it, but for the life of me I can't get my PC to see my TP. My PC keeps making the "USB connecting" sounds. I think the problem is that it's looping between the HP logo and total black screen.
F***ing HP and their ****ty software! Anyone have any ideas on what I can do? I've tried holding menu/power and it just keeps looping
Thanks in advance
edit: got it working, here's what I did thanks to webOS support:
Hold power and press center button 15 times. This turns device into a powered off state.
Hold power and volume up to enter USB mode
Download and run webOS doctor.
After about a total of 3 hours of thinking my TP was dead, I kind of have a new found love for it, lol

btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.

VGSmatt said:
btw, why didn't i get any way to access the internet? i had to download firefox from the market to go online. did xron come with gapps or not?
also i downloaded google reader and it force closes after reading a couple posts.
Click to expand...
Click to collapse
Xron comes with Gapps but Leo replaced stock browser with Dolphin (which is better). There is a problem if random FCs but they are so much less then what I had in CM7...as Xron is also based on CM7...you will see few bugs...but overall it made my TP so useful..

i agree, this is so much better then before. i don't see dolphin in my app drawer, no matter, firefox is working fine.

yip, it is better and if you want some eye candy the SPB shell 3D is really cool