[Q] auto-nooter 3.0.0 question - Nook Color Q&A, Help & Troubleshooting

complete noob here, so sorry if i am posting i the wrong place. I tried rooting my nc 1.2.0 but it didnt take, i think i unplugged it too soon. so I did a complete wipe and afterwords the nc was showing my software rev as 1.1.0. I then followed the instructions for auto-nooter 3.0.0 and i got to this point:
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
so here is my problem. After enabling location services(step 9), when i hit next I get a prompt saying:
complete action using
home
softkeys
home simply takes me to the normal nc home screen and softkeys asks for superuser permission the first time and afterwards also goes to the nc home sceen. i have wiped and re-rooted 3 times now with exactly the same results. am i missing something or doing something wrong? is there a different method for rooting that I should be using instead? should i attempt to go back to vers. 1.2.0(not sure how I would do this)? any help anyone could give me would be greatly appreciated as my kids are dying to use the nook and for me to be done "hogging it" thanks in advance

its fixed
ok not sure what gives, but i rebooted again and it seems to work fine now, other than not many apps in the market. I dont know how to delete this post so i just replied. mods feel free to delete

Related

[Q] How do i get back to stock

Alright so im a first time "poster" long time "reader" ran into my first problem i cant figure out on my own...
My NC was rooted working fine except for limited visibility in the market place so i tried numerous things to make the market place work correctly eventually upgraded from MN 4.5.6 to MN 4.6.16 in one jump and everything worked fine except marketplace auto closed after starting it.
So i followed a post about how to fix this issue and this lead me to the current situation i am in now where my NC is hanging at the N logo when booting.
Basically id love to get back to stock and start over but ive followed http://forum.xda-developers.com/showthread.php?t=914690&highlight=cwm
and i still get stuck at the N logo.
Not sure what else to try.
Any help would be much appreciated.
Thank you,
Vatel
anyone?
anyone?
please.
Do you have CWR installed? If yes you can follow this http://forum.xda-developers.com/showthread.php?t=945838
Do pay attention to all details, including formatting...
If you don't have CWR installed, did you tried the 8 failed boots method?

[Q] After unrooting I can not get though the initial setup section

Hi.
I have a serious problem using my Nook Touch.
I imported my Nook the last November.
As soon as it arrived at my house I rooted it and then after using it for a week I decided to make it back to the default factory state using the backup I had made before rooting.
I think the unrooting itself was successfully done but when I try to boot my Nook up, I can not get though the initial setup section (the sign part), it says,
Sign in
Error
Sorry we're having trouble setting up your Nook. Please shutdown the device and try again.
If the problem persists, contact Customer Support at 1-800-THE-BOOK (1-800-843-2665).
DAD1202
Then I have no choice but to power it off which doesn't do anything to solve the problem.
Now I have a Nook which is completely unusable in my hands.
I have not read a single book yet after I paid an extra money to import it and waited for it to arrive for 3 weeks...
I am at a loss as to what to do now, so if you can help me in any way I would be really grateful for it.
Force reset it by shutting it down, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds.
This will resolve the problem, if not:
Use nookRestore to restore /system (http://forum.xda-developers.com/show....php?t=1289233)
and then:
Update to 1.1 (http://www.barnesandnoble.com/u/Soft...uch/379003175/)
eded333
Thank you for the reply.
I am sorry, I forgot to mention that I used both the forcefully reset option and the nook restore software, both of them did not change anything.
And it seems that you can not update your firmware unless you completed the initial setup.
So virtually I can not do anything right now.
Just do a data reset (the forced one) without the restore and try it.
I think you can update to the 1.1 not registering, getting into the factory mode:
http://forum.xda-developers.com/showpost.php?p=20121721&postcount=17
and copying the 1.1 update the Nooks flash (not sdcard)
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
Thank you for the advise!
Now I can go to the Home screen and at least can read something which I put into my Nook.
I am pretty relieved that my Nook is not complete useless.
But I still have that problem of not being able to sign in.
The same message appears every time I try to sign in or create a new account.
It would be great if I could get rid of this problem...
Threekei said:
Sign in
Error
Sorry we're having trouble setting up your Nook. Please shutdown the device and try again.
If the problem persists, contact Customer Support at 1-800-THE-BOOK (1-800-843-2665).
DAD1202
Click to expand...
Click to collapse
Try this:
Log onto the B&N website with your account (same as you try to sign in on)
Go to My Nook hover the picture and select "Erase and Deregister Device".
Now try to register from the NST again.

[Q] problem with apps

Hi!
Im new with this of craking, and im not a native english speaker so forgive me if i dont explain well my self.
I just root my NookSimple Touch (version 1.0.1), with touchnooter-1-6-24, during the hacking every thing was going fine, the "root forever" logo showed up, and then it got stuck in the barnes and Noble loading screen, so i waited like for 20 minutes and nothing! it remains in the same loading screen. So i took out the SD card, and re boot the nook, it started up well and i could complete all the steps of the rooting procedure normally.
Now im having troubles with some apps, cant use the browser, and cant use well the wallpaper app, it dont allow me to select any of the images, and even worst when i select one of the Live Wallpapers (only one live wall paper was working), the next time i turn on the nook it got stuck again, but this time on a diferent screen, on the unlock screen at the starting up. After many rebootings could use the nook again and close the Livewallpaper app. Now is working fine.
Now im scare of using other apps and crash the system again. So i have some questions:
Is it normal that the apps that i mention dont work well on the rooted nook? Or is it concecuence of the failure i mentioned during the hacking procedure? Do i have to root again the nook?
I didnĀ“t do a backup, does it worth to do one now? Or just save some information of the system that could be use in the future for an emergency?
last question, when one uses the set fabric settings option, does the nook goes to original version (with out the root)?
thanks a lot in advance for the soon answer
Juan
Do a backup, if you screw up, its the best way to have a copy of the unique information on the factory partition of your NST.
You need to do a Reset and a Restore to get rid of root+Gapps+Apps, use this:
http://forum.xda-developers.com/showthread.php?t=1289233
+
"set fabric settings option"
or use this:
http://forum.xda-developers.com/showthread.php?t=1475613

[solved] Possibly bricked only the recovery partiton?!

okay so after trying some other options i was able to solve this problem, here is the how to in case this has happened to anyone else. my original post is below the how to.
1.flash the sbf that returns your defy to stock eclair using a different T-Mobile sim, after it is done flashing you will seem to still have the problem, except it will say no sim emergency calls only.
2.power off the device and install your original sim from T-mobile.
3.reboot the device and you will not be prompted to setup motoblur, because you device is in soft brick limbo still, but you will have laggy touch responses, be patient with your device as you navigate to settings>privacy>factory reset and confirm. ( this process will take much longer than usual and the progress bar will not show any progress but it will shutdown and reboot as it normally would with a factory reset)
4. you will now be prompted to setup your motoblur account ( if you are not restart the steps until this happens, if it does not happen your device did not actually do a factory reset you will need to try again until it does ask you to setup blur, this is your sign from the moto gods that your device is no longer in softbrick limbo)
5. setup your blur account ( you will still have no recovery menu at this time so don't try and check or you will have to start back over at step one)
6. now navigate to settings>about phone> check for updates
7.download and install the update to froyo ( durring downloading you phone may shut off several times, however if you reboot it will automatically pick up the update where it left off as if your device never powered off to begin with)
8. once you have installed the update you device will be back to froyo stock and your recovery partition will no longer be bricked
9. enjoy your defy once again, and be more careful with your device in future ROOT mods and tweaks, cheers!
10. If this helped you recover your device please thank me for this solution.
okay so i am new to posting on XDA and i will try to organize my problem as best as possible, but i may need much guidance on if i am posting in the proper forum.
here are my details of my device and the problems i am facing with my device currently.
Motorola Defy
MB525
T-mobile US
stock Froyo rom 2.2.1 ROOTED overclocked with milestone overclock to 1224 mhz @ 85% voltage /V6 SUPERCHARGER SCRIPTS. MODDED BUILD.PROP TO REFLECT THE MAX HSUPA CATEGORY 34/MAX HSDPA CATEGORY 36/ GPRS CLASS 10/ HSXPA=2/RO.RIL.VIDEO_MODES=TRUE EVERYTHING ELSE IN BUILD.PROP WAS STOCK EXCEPT WHAT THE V6 SUPERCHARGER SCRIPTS CHANGES. I was running a custom bootscreen that i placed in the location of the old one using ES file explorer with root browsing rights, i had defy Recovery installed but only used it basically as a system restore app ( context of previous statement is relating to system restore if you were talking about a windows machine) used Avast anti virus as root installation w/antitheft installed used system tuner to manage startups down to core services or other services i did want to run at boot i.e. stuff like facebook and weather channel.
DEVICE WAS ALSO SUBSIDY UNLOCKED
SBF started with and reflashed to try to correct problems was JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.OR_JORDANTMO_PO22_HWp3_SERVICE1FF.sbf
****NOW TO THE PROBLEMS****
I was starting to think that maybe the v6 supercharger scripts were not really doing anything performance wise for me as it would disable my overclock settings at boot and i would have to manually invoke them after everything had requested its SU rights at boot. so i decided to get rid of the v6 supercharger scripts and all other softwares pertaining to managing and running the scripts, I decided the best way to do this was to do as i had always done in the past when wanting to re-tweak my phone and use the stock recovery to start fresh with 0 tweaks and only apply the ones i wanted after restoring to stock, when i used the stock recovery this time it didn't work, i booted the phone back up after wiping data/ factory data reset and to my surprise the recovery did nothing but delete the SU.apk the custom boot was still in tact, everything else listed above still in tact except for the phone was obviously throwing errors left and right because there was no SU for apps to request permissions from, so i reinstalled the SU.apk just to make sure i didn't have to deal with the device being slow while restarting the process of doing a full wipe. this time i used the DefySDrecovery.apk i mentioned above to do the same steps and while adding wiping the dalvik cache after wiping data and before invoking the recovery, it then gave me the same error i have always gotten when wiping the cache which is
e:\ cant mount cache partition
e:\ cant find /recovery/caller
e:\ cant find/recovery/cache
(this has never caused problems with the device once recovery was finished)
this time however I was only able to boot(loop) to the moto logo
so i reflashed The above mentioned SBF and the device booted normally i went through the entire setup like it was a new device with blur and google and it finished. when I got to the home screen it was frozen and would not respond to touch it also showed to have no cellular signal, i turned it of and back on and it made me go through blur and gmail setup again, went to home screen same thing frozen with no signal.
i reflashed the SBF again thinking maybe something went wrong as they do sometimes with RSD yet still finished and passed on everything
the above description repeated except for this time it responded to touch for the first few seconds before it froze completely ( oops! sorry one detail to add when i say it froze i mean froze like would respond to nothing, touch, hardware buttons, nothing) i had to pull the battery in both instances to try and start over, after many attempts of getting in the phone and trying to turn on usb debugging before it froze i finally was able to complete the finger olympics and get usb debugging turned on, i was able to root it using superoneclick so that i could have a look at the logcat in ADB. now in my experiences with ADB normally when you run a logcat command it will print to the screen for about two to three hundred lines and then slow down and only print one to six lines at a time as the server is calling actions when i ran a logcat on this device it runs two to three hundred lines slows down and then runs lines until you close the ADB window i let it run a logcat overnight and it was still running lines the next morning with no sign of stopping where you could freeze the window and read over all the crap it was calling to action, looking at the device durring this process i saw force close windows a few times saying the com.android.process has stopped but the home screen never crashed and the phone didn't do a random reboot. so to sum it all up ( so sorry for the lengthy explaination but i wanted you to have the whole problem fully explained in hopes you wouldn't have to ask for more detail)
it freezes and has no service with my T-mobile sim in it ( if i put my at&t sim in it has service but still freezes)
flashing a new SBF doesn't fix the problem as it should
and there is no way to enter the Recovery Menu now its gone, non existant, cant find it, cant fix it, i'm F***** right now Please help if you know how, and if i totally screwed the phone i'm cool with you saying so but it can still be in a respectful way i already feel like an idiot for not being able to correct this with all the knowledge i have of this phone, a negative attitude insinuated is not going to help me in either direction, thanks in advance for any help you may be able to provide.

[Q] Tried to update to cm10, couldn't boot, tried to restore to mnooter or cm7, help?

Hi all. I used to mess with my Nook Color a lot around a year and a half ago but recently was just using it to read and occasionally browse. I'm 99% sure I was working with just a nook which was used with manual nooter, so that I had the Google Play store and Zeam launcher with stock B&N as well. I was having issues with things "not being able to update" so I tried to mess around, only realizing too late that I wasn't really interested in cm10 and wanted to stick with zeam. Since then I've been trying to get back to how I started but I'm failing miserably. I've so far tried wiping/factory resetting my device. Installing cm7 from zip, resetting everything using the guide here and installing 1-4-1 cam oc zip from here and still I fail. I can get into the set up screen, but when the device will not find any wifi signal and then freeze without allowing me to type it in under "other". Honestly I'm not sure what else to do now. I just want my nooted device back -__-.
Please let me know if I can submit any more information that can help solve this problem. Thank you for your time.
I'm literally infinitely stuck staring at this screen.
Managed to fix everything. Used section A15. Enjoy anyone who ran into similar trouble.

Categories

Resources