[Q] Autonooter for 1.2? - Nook Color General

Any word on an autonooter for 1.2? Or maybe a rough time frame as to when there will be one? All I can find is manualnooter...

No real time frame as of right now. When the network location stuff is ironed out in a safe way, then an autonooter version might come out. The autonooter format seams to do a better job of implementing everything that it is written to do. ManualNooter is still a great safe product that can be used right now, it is just lacking the network location information.

ManualNooter for all intents and purposes is AutoNooter.
The only thing stopping MN from becoming an AN is before I started school I had been looking for a viable way to make CWM flashable cards Auto-run compatible. I have a method of getting the cards to run the updates automatically but for CWM to do it based on an auto-run script it has to be modified to run the script and therefore the "AutoNooter" update.zip. While I have done this to a couple of versions I started school before I could hammer out the best way to implement this in such a way that other users wouldn't have to reflash for an auto-run capable card and therefore an AN capable card.
The old method of AutoNooter that was used for all pre 1.2 versions is a deprecated method and honestly no one should be trying to recreate that method for new B&N version updates. With ManualNooter and when I can put some time into it, AutoNooter, users have a way of actually seeing when the process is done as opposed having to wait for that reboot or just randomly turning it off cause they thought 30 seconds was too long to wait.

GabrialDestruir said:
ManualNooter for all intents and purposes is AutoNooter.
The only thing stopping MN from becoming an AN is before I started school I had been looking for a viable way to make CWM flashable cards Auto-run compatible. I have a method of getting the cards to run the updates automatically but for CWM to do it based on an auto-run script it has to be modified to run the script and therefore the "AutoNooter" update.zip. While I have done this to a couple of versions I started school before I could hammer out the best way to implement this in such a way that other users wouldn't have to reflash for an auto-run capable card and therefore an AN capable card.
The old method of AutoNooter that was used for all pre 1.2 versions is a deprecated method and honestly no one should be trying to recreate that method for new B&N version updates. With ManualNooter and when I can put some time into it, AutoNooter, users have a way of actually seeing when the process is done as opposed having to wait for that reboot or just randomly turning it off cause they thought 30 seconds was too long to wait.
Click to expand...
Click to collapse
One of the two remaining issues for MN is IMEI apps force closing. Has anyone gotten the [Beta] IMEI generator... to help with this issue in MN roms?

lschroeder said:
One of the two remaining issues for MN is IMEI apps force closing. Has anyone gotten the [Beta] IMEI generator... to help with this issue in MN roms?
Click to expand...
Click to collapse
I don't believe DizzyDen's IMEI program will work with the ManualNooter flash. It should however work to patch the full stock 1.2 ROMs but obviously this is undesirable unless you wish to go back to bone stock.
Dizzy's latest betas however have a feature to pull the framework.jar and your S/N via ADB (or ADB wireless), patch the framework.jar with a psuedo IMEI based on your S/N, and push the modified framework.jar back to your device via ADB. I see no reason why this method wouldn't work with rooted stock.
If you try it be sure to post in Dizzy's thread and let him know what happed.
Martian21

Related

Disabling otacerts on 1.0.1 + using shop

Let's get some user experiences here to try to prove or disprove what, to me, seems like a gray area that many have jumped to conclusions about:
There was recently a post in a thread about someone who, after renaming etc/security/otacerts.zip while on 1.0.1 firmware (to disable auto updates), opened the B&N Shop and had all of his/her data wiped/restored. This poster claimed to have repeated it several times, all with the same result.
Afterwards, I didn't hear many others say much about it (I'm assuming if this were widespread it would be everywhere). Plus someone in the same thread even mentioned here that he got the reset WITHOUT having disabled the otacerts . . .
... Yet I keep hearing mentions in various threads about that one original incident as if it's a sure-fire thing that's bound to happen when you disable otacerts on 1.0.1.
So if you:
a) are on 1.0.1 firmware
b) renamed the otacerts.zip file to something else
c) have used the B&N Shop
... Please let us know what happened, so we can attempt to get a clearer view on this.
a) I'm on 1.0.1 auto-nootered
b) renamed otacerts.zip to otacerts.zip.disabled
c) B&N Shop works fine
@wvcachi, you mentioned in a different thread that you're on 1.0.0 right now. Did you disable the otacerts? If so, does shop work for you?
eyecrispy said:
@wvcachi, you mentioned in a different thread that you're on 1.0.0 right now. Did you disable the otacerts? If so, does shop work for you?
Click to expand...
Click to collapse
Yes, shop works fine for me on 1.0 after disabling otacerts (stayed on 1.0 because all but one Dolphin User Agents work properly on 1.0).
wvcachi said:
Yes, shop works fine for me on 1.0 after disabling otacerts (stayed on 1.0 because all but one Dolphin User Agents work properly on 1.0).
Click to expand...
Click to collapse
Ok cool. I'm gonna go ahead and disable mine tonight then. Have you experienced any other side effects on 1.0 since disabling certs?
Sent from my XDA app on my Nook Color
I'm with MkFly
1.01
Renamed
No problem
//from the nook COLOR
eyecrispy said:
Ok cool. I'm gonna go ahead and disable mine tonight then. Have you experienced any other side effects on 1.0 since disabling certs?
Sent from my XDA app on my Nook Color
Click to expand...
Click to collapse
None at all.
That post was mine and I later clarified that it was false.
The authorization errors/reseting turned out to be a recovery of data from using Titanium. You can recover apps, but not the data that associates itself with B&N apps otherwise you get the authorization error.
Disabling OTA certs will NOT break your BN shop.
leeh41 said:
That post was mine and I later clarified that it was false.
The authorization errors/reseting turned out to be a recovery of data from using Titanium. You can recover apps, but not the data that associates itself with B&N apps otherwise you get the authorization error.
Disabling OTA certs will NOT break your BN shop.
Click to expand...
Click to collapse
Haha cool, thanks for the clarification. Hope this thread has helped dispel some myths on the subject.
I'm a bit in the dark on this topic. Is there a thread somewhere that will show me how to disable otacerts properly? Can I do it with Root Explorer? What would/could happen if B&N rolls out an update and it's applied to a rooted Nookie?
See my sig for Nook info [1.01 A-n (2.12.25)] ... I renamed otacerts.zip to otacerts.OLD with no ill effects. I did get an authentication error after redoing A-n but I'm 99% sure that was from restoring system apps/data with Titanium Backup. I have stuck to just user apps/data and have had no issues.
Homer
supersoulfly said:
I'm a bit in the dark on this topic. Is there a thread somewhere that will show me how to disable otacerts properly? Can I do it with Root Explorer? What would/could happen if B&N rolls out an update and it's applied to a rooted Nookie?
Click to expand...
Click to collapse
All you're doing is renaming etc/security/otacerts.zip to something else. Root Explorer works just fine.
I may have misunderstood. I never allowed the update (by not going online) and I renamed etc/security/otacerts.zip to etc/security/otacerts.zip.old and it updated.
Sigh. I'm now on 1.0.1.
My side-loaded apps are there, but none will run. I tried to avoid this but I guess I have to do the autonooter thing.
Do I really have to wipe it or can I just run the autonooter as is?
But I'll start reading.
I would recommend wiping it (both system and app), loading 1.0.1 again from a file, then auto-nooter it. I had issues when I auto-nootered 1.0.1 with existing apps from 1.0.
sark666 said:
I may have misunderstood. I never allowed the update (by not going online) and I renamed etc/security/otacerts.zip to etc/security/otacerts.zip.old and it updated.
Sigh. I'm now on 1.0.1.
My side-loaded apps are there, but none will run. I tried to avoid this but I guess I have to do the autonooter thing.
Do I really have to wipe it or can I just run the autonooter as is?
But I'll start reading.
Click to expand...
Click to collapse
If you never went online, how did the update get on your NC? or do you mean you didn't go to B&N? Other people have mentioned just re-running Auto-nooter but YMMV.
Homer
supersoulfly said:
... What would/could happen if B&N rolls out an update and it's applied to a rooted Nookie?
Click to expand...
Click to collapse
Can anyone speak to this issue. Is there any danger of an OTA update bricking the NC? I assume it would just fail, but you know what they say about assumptions....
jerrykur said:
Can anyone speak to this issue. Is there any danger of an OTA update bricking the NC? I assume it would just fail, but you know what they say about assumptions....
Click to expand...
Click to collapse
It didn't brick mine. I was on 1.0 and was nootered (but didn't have the otacert.zip renamed). Got the update late December. Didn't have any issues until I auto-nootered over it. Then it started doing strange things, which I don't remember the specifics now. So I did a clean wipe and redid everything. All is well now.
Homer_S_xda, Sorry reading it again I see my post wasn't clear. I was happy with 1.0.0 and thought that renaming otacerts would prevent wifi updates.
I didn't have my nc online since the update came out, just using apps and as a reader. Previously my nc was rooted. Nookdevs says the 1.0.1 will fail on a rooted 1.0.0 nc but once I finally brought it online, it did update for me. My side loaded apps were there, but none would run. I believe nookdevs guide means downloading the 1.0.1 update and copying over will fail on a rooted nook but it seems the OTA update will install on a rooted 1.0.0.
So just wanted to say, renaming autocerts does not prevent updates (not from 1.0.0. -> 1.0.1 anyway). But if it failed for 1.0.0 I don't see why it would work for 1.0.1.
So I reset to factory defaults, reinstalled 1.0.1 and used autonooter. I was going to just run autonooter and not bother with reseting, but people advised I would be just asking for trouble.
From what I understand, there isn't a reliable way to prevent OTA updates. I thought android devices have a hosts file. I would have thought someone by now would have used wireshark to see where it's grabbing the updates and redirect that.
I'd rather dodge this again when the next update comes out (unless the next update provides something really useful or whatever)
But again, maybe I misunderstood the whole point of this thread. Is there another reason to disable otacerts? Cause it doesn't stop updates.

Nook won't root

I don't understand what's going on. I am not a noob; I've rooted 10+ android devices and have been in the mobile game since windows mobile 5.
I follow all instructions to the T from here
http://nookdevs.com/NookColor_Rooting
Everything goes as it should until it is time for the final reboot. Instead of displaying a new boot animation, it simply gets stuck at the screen with the lowercase "n" that says the blurb about adobe at the bottom.
Same both with the SD card in, and without it.
I am able to salvage the situation by doing the 8 interrupted boot plus the homescreen and power key. Started from scratch again - updated to 1.01, reflashed the sd card, etc.
Same result. This is a brand new device, just bought today.
Any ideas? You don't think they killed the root exploit, do you?
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Those instructions worked for me. It sounds as if your boot partition is completely empty. Are you using Auto-nooter 2.12.25? That is the version you need to use if your NC is already running 1.0.1.
edit:
Just saw your update. In that case in the B&N link replace 1.1.0 with 1.0.1 eg:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.1/Sideload_update.zip
should be:
http://images.barnesandnoble.com/presources/download/nookcolor/v1.0.1/Sideload_update.zip
otherwise there are a couple other threads where people have thrown up the 1.0.1 sideload update.
computerpro3 said:
I believe I just figured out the problem. The link in the WIKI to the B&N 1.01 update is outdated and incorrect - it links to the incompatible 1.1 update instead, which is not autonooter supported.
Click to expand...
Click to collapse
The link has not changed, the B&N reference within it has. But perhaps something should be tweaked on the URL for now, or the instructions. Done.

[Q] rooter stock with updated kernel

Howdy, I have been all over this nook lately and what not.
What I have right now as a backup is a rooted 1.0 nook with a modified build.prop and devicemanager.db to stop the 1.1 update. I have everything I have been using and currently will probably use EXCEPT I don't have iptables/netfilters in order to get asproxy working so I can setup Orbot (TOR client)
I am quite willing to restore the nook back to original and start from ground zero if that is what is needed for me to be able to use the current backup I have but have an updated kernel with OC and iptables/netfilters enabled.
Can anyone tell me if it is possible to replace the kernel AND use my current nandroid backup (possibly in sections) and not overwrite the kernel?
My next route will be to restore to stock, root, edit devicemanager.db to avoid the 1.1, update the kernel and then just reinstall the apps. either scenario does not have me re-registering my device.
Or I can update to 1.1 and then block any further updates and such but ultimately I need to get the updated kernel for iptables/netfilters. as you surmise I am fairly obsessed with this...
Thanks for any suggestions!!
I am also open to using a very clean install without a lot of fluff, I just put CM7 on the emmc and have phiremod rom running atm but am not overly excited by it. I tend to like very clean minimalist things.
So I am open to that as well but have not heard much promise on the battery life with the current builds.
bump it bump it good
It may be good but its beyond me.
While I do still have select backups of stock with root and a few points along the way, I have no intention of using them except for emergency recovery purposes-
and starting over would probably be easier anyway.
I have little interest in the stock B&N apps either so nothing that needs saving- except what I have on there from the last week or so. Ok, not really that either.
Do you really have stuff on there that you NEED to preserve or is it just settings and preferences?

[Q] Help! Massive Problems After Rooting and "unrooting"!

Alright I rooted my Nook a few days ago. I have a 1.2.0 so unfortunately I used an older version of ManualNooter and then installed the latest version on top of it. It worked fine until I downloaded Angry birds from the market, after that NO GOOGLE apps worked, such as Gmail, market, etc.
So I unrooted my Nook. Unfortunately the only apparent stock image out there for unrooting is 1.0.1....but I did it anyway.
It seemed to work but when I looked for the storage on my Nook, it said 0B of 0B used. So it seems that my internal storage has disappeared!
Aside from that....nothing will download and I can't hook my Nook to my computer, it just doesn't recognize it. (believe me I tried everything, I even called support, they just wanted to give me a new USB, but that's not the problem)
I was trying to update it back to 1.2.0 but clearly I can't if I can't even download it on my Nook! What is going on? I never hooked it to my computer before I rooted it, so I don't know if it truly couldn't connect beforehand (but I've heard its a common problem)
Anyone have these issues? I just want to get the storage found, hook up to my computer so I can properly re-root my nook to hopefully cm7 this time because I've heard that is much more stable than ManualNooter.
I'm at the end of my wits, I got this a few days ago, so I'm thinking of trying to exchange or return it if I can't fix it.
Any suggestions?
It appears you are having a similar issue to this user:
http://forum.xda-developers.com/showthread.php?t=1184458&page=2
Did you start with a "blue dot" Nook with the new partition sizes? If so, I don't know how trying to restore with a 1.0.1 image made for the old partitions affects your device. That may be the problem. This would require you to repartition your device (see thread in this forum) and restore again with 1.0.1. Just a thought. Maybe someone else will chime in. Might be something very simple that we are not thinking about.
Edit: What version of CWR are you using?

[Q] Plan for Bionic root/unroot for ICS, PLEASE REVIEW

I'm hoping to get some eyes on this plan I've made for hacking my new Droid so I can avoid bricking it at all costs.
I bricked my old Bionic 2 days ago due a combination of problems with Clockword Recovery Mod and the leaked ICS update, as well as my battery frying for some reason. Thankfully Verizon was none the wiser and they are sending me a new phone and battery in a few days. Although I'm cautious about hacking now, I still plan on rooting the new phone so I can recover my apps and data from the old phone's SD card.
Here are my plans for the new phone. If anyone could tell me if it makes sense or if they see any issues that will arise from following these steps, please let me know:
1. Root new Bionic with Motofail.exe root
2. Restore apps and such with Titanium Backup (restoring individual apps so I don't get any old clockwork garbage or other random stuff)
3. Download Voodoo Root OTA Rootkeeper.
4. Wait for official ICS OTA (don't want to mess around with the leaks anymore) and backup root with voodoo
5. Unroot with voodoo, install ICS and re-root after update (I've read on some posts that Voodoo works with the ICS OTA but I'm not 100% sure)
I'm more concerned with the OTA installing properly than keeping the root after ICS, though while it would be simpler just to not root, I really want to restore the TiBu backup from my old phone.
If anyone sees any flaws with this plan or if you think it sounds like there won't be any problems, please respond! I really don't want to brick a second phone so any help would be invaluable.
No one can say for sure if this will work since no one has the official OTA yet.
That sounds like a plan that may work. Even if OTA Root keeper fails I see a thread with a root method that is working on ICS leaks so it should
[should being the operative word here as stated this is all subjective reasoning from my time and use of Android and many different devices there is NEVER 100% certainty EVEN IF we had access to the OTA and had a method there is no accounting for any errors caused by a multitude of things [download corruption, bad blocks in memory during flash, you missing a step and borking the whole process, etc.] so no one will ever be able to say with 100% certainty that you will not have some rare issue and have a problem even with a tested method [and if someone does try to tell you something is 100% they have not dealt with technology and computers long enough to realize nothing is ever guaranteed even fully certified OTAs have caused bugs not accounted for and been stopped, recalled, or otherwise modified when users try to apply them and have issues ]
Anyways, I did read where you flashed the ICS leak via CWM recovery and everything I have been reading about flashing ICS on a Bionic involves the STOCK recovery and not CWM [most postings even SPECIFICALLY state to NOT USE CWM AND ONLY USE STOCK Recovery [but then again I read a lot] so if I had to trace the issue you had the with the limited information you have provided about your specific experience I would prolly point to that as prolly causing the problem. See the ICS with files thread here and that is again specified as part of procedure [basically format EVERYTHING restore it back to out of the box 902 then using STOCK recoveries to apply .905 then the ICS leak THEN after ICS is running they have a rooting batch file in there as well [so no worries about rooting in .902 and using OTA Rootkeeper to sustain it in .905 and on just get stock .905 unrooted to the phone then flash ICS with stock and root once it is fully completed and drivers and all on computer side are good [dont forget to enable USB Debugging [and in ICS there is an option to allow SU to apps only OR APPS AND ADB and after rooting you may need to enable the ADB side for any super user root checks if checking via ADB] but dunno if that is CM9 only option, but seems to be stock ICS setting in developer [it protects you if you use and leave enabled the ADB over the network function from others who may find your device over a network and getting SU access].
Sorry, I digress, all to say sorry to here you had the issue, but I think you may have missed something in the install process and here's how to address it, and your methodology seems sound in theory, but there is other information already available to augment your procedure and make it easier on you, my bad.
Hope all the info helps....
Here is that thread mentioned above that seems to distill what I have read on numerous boards in to one easy to download pack with instructions that has users replying that they have had great success with it: [Guide} Bionic to ICS w/Files

Categories

Resources