Auto-Nooter 3.0.0 (1.1 only)
- Thread starter GMPOWER
- Start date
-
- Tags
- adb auto-nooter root version 1.1
I don't think anyone knows for sure what would do that. The Sqlite update was the frontrunner but there was been at least one instance of someone reporting that didn't help. Same goes for build.prop and you can't even go for that until you know what the update is so you can spoof it.
Request a Bare Bones AutoNooter for 1.2
Hopefully there will be a very "vanilla" version of AutoNooter for the BN 1.2 Update, without changing sign-on screens, adding live wallpaper and all the clutter of apps etc that we can download ourselves and/or don't suit our personal preferences. That is to say, a version that will leave 1.2 as close to "stock" as possible.
Having migrated to a "dual-boot" NookColor, with the XDA posted version of HoneyComb, I no longer use the "stock" version of the OS for anything other than reading -- I use the HoneyComb tablet OS for all apps, web-browsing and everything else.
It also bears noting that HoneyComb solves just about all the problems of Android 2 on the NookColor that required 3rd party soft keys as the menu and status bars are not hidden and thus the operating system soft keys are always available.
Anyway keep up the good work!
Hopefully there will be a very "vanilla" version of AutoNooter for the BN 1.2 Update, without changing sign-on screens, adding live wallpaper and all the clutter of apps etc that we can download ourselves and/or don't suit our personal preferences. That is to say, a version that will leave 1.2 as close to "stock" as possible.
Having migrated to a "dual-boot" NookColor, with the XDA posted version of HoneyComb, I no longer use the "stock" version of the OS for anything other than reading -- I use the HoneyComb tablet OS for all apps, web-browsing and everything else.
It also bears noting that HoneyComb solves just about all the problems of Android 2 on the NookColor that required 3rd party soft keys as the menu and status bars are not hidden and thus the operating system soft keys are always available.
Anyway keep up the good work!
Why "Reading" and "Store" works with Autonooter 3.0
GMPOWER explained it in http://xdaforums.com/showpost.php?p=13287968&postcount=75
"I can comment on this issue, the framework.jar file that was used in AN 2.25, and earlier, was all hacked up from its original form. If you do a file by file comparison of it to the original file, you will see that a ton of files were changed that were not needed. When I put together the AN 3.0, the only hack that I did to the framework.jar file was to add the Clockworx Not Ugly Market Fix. Since I did not hack up the framework file like early versions had, the random reboot issues, in-store access, and everything else worked like stock."
GMPOWER explained it in http://xdaforums.com/showpost.php?p=13287968&postcount=75
"I can comment on this issue, the framework.jar file that was used in AN 2.25, and earlier, was all hacked up from its original form. If you do a file by file comparison of it to the original file, you will see that a ton of files were changed that were not needed. When I put together the AN 3.0, the only hack that I did to the framework.jar file was to add the Clockworx Not Ugly Market Fix. Since I did not hack up the framework file like early versions had, the random reboot issues, in-store access, and everything else worked like stock."
So far, it has been only that instance. It may have been something unique to the person's NC. For example, the field may not have survived a reboot. Right now, I have some degree of confidence that setting the db field to "manual" works.
Agreed, based on my personsl experience and pretty much everything else I've read. So far there's been one report of a SQLited Nook Color updating, and lots of reports on the other side (including users on 1.0.1 for months). At this point I'm chalking up the one counter-example to user error.
I can vouch for that "I have some degree of confidence that setting the db field to "manual" works." My auto-nootered Nook was OTA updated on the release date. It unrooted and deregistered the device. Fortunately, I had a backup and restored everything after re-rooting it. I then purchase sql lite and updated OTA to manual in the registry. It has been perfect ever since. No attempted updates.
Revert from BN1.2 to 1.1
OK, I was messing with my daughter's nook, preparing to root it, when the OTA hit, and now it's on 1.2.0 (it was originally purchased just 2 months ago at 1.1). How do I revert to BN1.1 so I can root it? Or is there another thread elsewhere indicating that a 1.2 root is imminent?
Thanks,
FreeMan
OK, I was messing with my daughter's nook, preparing to root it, when the OTA hit, and now it's on 1.2.0 (it was originally purchased just 2 months ago at 1.1). How do I revert to BN1.1 so I can root it? Or is there another thread elsewhere indicating that a 1.2 root is imminent?
Thanks,
FreeMan
11th from the top... manual nooter! Just a short look and you would have found it.
It's dead simple.
In case you want to revert, try this. If it worked coming from my CM7 setup, it'll work coming from your 1.2 stock setup.
It's dead simple.
In case you want to revert, try this. If it worked coming from my CM7 setup, it'll work coming from your 1.2 stock setup.
This is making me mad. -.-
I've written the image with WinImage 8.1 over ten times, and with WinDiskImager 7 times. No change at all. I just got this today by the way.
EDIT: Giving up for now. -.-
I've written the image with WinImage 8.1 over ten times, and with WinDiskImager 7 times. No change at all. I just got this today by the way.
EDIT: Giving up for now. -.-
Last edited:
Hi All,
I originally got my nook rooted the whole 9 yards. I decided that I wanted to try Froyo and for whatever reason CWM 3.0 ended up on there. Now that I'm trying to go back to stock and do the 8 force interupt boots, on the 8th one it goes to CWM. I'm stuck and I'm not sure what to do at this point. Any help provided is greatly appreciated.
I originally got my nook rooted the whole 9 yards. I decided that I wanted to try Froyo and for whatever reason CWM 3.0 ended up on there. Now that I'm trying to go back to stock and do the 8 force interupt boots, on the 8th one it goes to CWM. I'm stuck and I'm not sure what to do at this point. Any help provided is greatly appreciated.
If you've flashed CWM to the recovery then I don't think the 8 failed boots is going to work for you. I think you'll have to flash back to stock.
I just saw this on All About Android podcast, it looks pretty nice. I am currently running CM7. Has anyone run both? Which is best, more reliable, stable? I like the interface on the Autonooter.
help!
OK. So i got all the necessary stuff to get this done however, when i do the following step it gives me the option to choosewshere to restore the files and I choose the SD card. When i hit okay it takes me to a screen to open a file. i dont understand. any help will be greatly appreciated. Thanks
Let's get started:
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
OK. So i got all the necessary stuff to get this done however, when i do the following step it gives me the option to choosewshere to restore the files and I choose the SD card. When i hit okay it takes me to a screen to open a file. i dont understand. any help will be greatly appreciated. Thanks
Let's get started:
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
What version ROM are you running? This article seems more current for 1.2, or 1.3. The steps for 1.3 work fine.
Later in the thread are the instructions for 1.4.1.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
40*ALL THE USUAL DISCLAIMERS AND WARNINGS*
*THIS IS FOR VERSION 1.1 ONLY, DON’T TRY ON 1.0.0 OR 1.0.1*
Credit goes to: GabrialDestruir for the original auto-nooter, GLa’DOS for the boot animation, pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the “non-ugly” patch that is used to get androidID, mastapsi for testing and coding of the original auto-nooter, lewellyn for coding, [mbm] for ABI Fix, Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs and re-enable of ADB , Freenode's #nookcolor chat for code checking. A special thanks to all developers out there, without all of you this community would not be as great as it is.
Please Note: If you are the developer of an app that is included in this work, and would like me to remove it, feel free to contact me.
*I am copying the following step from the original auto-nooter, because they are tried and true, and people are already familiar with seeing them*
What it does:
Installs su and Superuser.apk
Installs Busybox with whoami
Installs Softkeys 3.0.6
Installs NookColor Tools (To Enable Non-Market Installs, and re-enable ADB)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Installs Gingerbread Keyboard
Enable ADB
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Known Problems:
With the version 1.1 update, ADB will not stay active after a reboot or unplug of the cable. To enable each time you want to use it, you will have to go into NookColor Tools /All Settings/Development/USB debugging, you will have to uncheck the box and then recheck it.
How to Use:
Before you begin:
* To update to 1.1 you must do a complete wipe.
* You must update to 1.1 to use Auto-Nooter 3.0.0 Instructions HERE.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: MultiUpload or MediaFire
*MD5 FB74865663B8D797A486A85022FAD9B2*
2 Linux: Unzip and use dd if=auto-nooter-3.0.0.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
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".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch, download the attached EVO HQ, and follow this code in adb
Code:adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system adb uninstall com.google.android.youtube adb push YouTube.apk /system/app adb reboot
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory ResetFactory Reset > Wipes /data
*You must do both of these to completely wipe clean your NOOKcolor.*
*Before anyone starts to say that I took this project away from GabrialDestruir, I posted this file in the original post, and sent the OP a PM asking to update the current project. I have yet to hear back, and the post was not updated. My post can be found HERE, dated February 2, 2011. I felt that this would be of a benefit to the community, so I am posting it now. If I am asked at some point to take it down I will do so at that time.*2
Set up Softkeys right and it works just fine.
http://nookdevs.com/index.php?title=NookColor_Default_Launcher2
I have.
You need to install clockwork mod recovery. You can do that by getting Rom Manager from the market, opening it up and flashing CWR (the top item in Rom manager). But before booting into recovery (the second choice in Rom Manager), exit out of rom manager, shut down the nook and turn it back on (reboot normally).**
Then, download the kernal you want, save on your SD card (I set up a folder in clockwork on my SD card... usually under the downloads folder I put a kernal folder using Astro). Then go into Rom Manager and boot into recovery (the 2nd choice).
Now do a nandroid backup in CWR.
after done backing up, choose the Install zip from sdcard option, and find the kernal zip and install.
You'll also need SetCPU in the market.
** - if you don't reboot after flashing CWR, and you reboot directly into recovery, you'll get into a CWR boot loop where you'll need to flash the CWR_removal zip file locted in the Monster root thread. so just do a normal reboot your nook after flashing CWR and you'll avoid this.
Editted to add: I'm in no way trying to be a thread cop (as I'm participating in it)... but a lot of this discussion is off the topic of the AN3.0. Imagine you trying to find info about how to root your nook with 3.0 and having to wade through gift card and recovery talk. [/off soap box... sprains ankle]111th from the top... manual nooter! Just a short look and you would have found it.
It's dead simple.
In case you want to revert, try this. If it worked coming from my CM7 setup, it'll work coming from your 1.2 stock setup.
