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?
Related
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.
Howdy, I am running rooted stock NC with the build.prop edit to stop the 1.1 update. This is (well finally successful due to my own errors) working out just great! However, I am unable to register my device anymore through the NC as it says there is an issue and reflashes me without any chance to stop it thus forcing me to restore it back again.
Is there a place within the com.bn.*** series of files or elsewhere that I could edit to have the device report back as being registered and such?
I thought perhaps if I did not go into the store section of the nook, I would be good to go, however when I went into magazines it threw me FOTA again.
Any ideas are greatly appreciated!
error DAD1202 in lower left corner?
nope, when i restored and managed to get the build.prop edit to work (i hadnt rebooted to finalize) the green N was there telling me I am updated, go into the about your nook and build is 1.1 as well. Everything is fun UNLESS I go into any aspect of the nook store, then I get an unregistered device and it makes me factory fresh again.
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
So I decided to root the nook this weekend and I'm having some issues that I can't get around.
I've rooted and ROM'd a few droids so far without an issue. I'm not an expert but I'm also not a noob.
I built up a bootable 1gb CWM and loaded up manualnooter-4-5-18 and manualnooter-4-6-16. CWM was pretty simple, and allowed me to load both of them up without an issue. (I've done both with and without a full wipe)
Once it reboots, it's perfect. market works, web works, rom manager permission fixes..everything works well.
The issue is once I power it off and back on, it's done. It hangs at the "Nook Color" splash screen (After the Read Everywhere and big grey N) and refuses to power up the OS. The onyl way i can get it back is to do a complete factory restore (power+vol button+N)
What am I doing wrong?
It sounds like you are suffering from the Flash / Air lockup problem. If you search the forums, there are links to download the zips that fix the issue.
I would also go to CWM 3.2.0.1 2.8 is rather old and 0.1 is a much easier experience especially on the new nooks.
I rooted two new nooks for my friend's kids Christmas presents last week. I used 3.2.0.1, Nooter 4-6-16 and used the adobe flash and air fixes and it went smooth.
Check this thread concerning the flash fix:
http://forum.xda-developers.com/showthread.php?t=1208896
Props to GMPOWER for his published answer.
Hope it works for you.
Ok cool, thanks OrionLTD. That sounds like my EXACT issue.
“jaromrnelson” continued the project, and has a more up to date version at the link below. His updated one will fix Adobe flash and Adobe Air. Once the fix has been applied, you should not have a problem whenever they update again.
LINK
Thanks GMPOWER, I'll try that one tonight.
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
el_bobbo said:
Well... I tried these methods and I'm still boot looping as soon as Adobe updates from the Market.
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Wiping and updating to 1.4.1 followed by the above should do nicely. It's working beyond expectations for me and some others.
That worked for me as well!
Although I had the old market at first after root.
I erased and deregistered and registered again and then applied the root 5-12-20 again and have newest market and so far so good, all is well
I might give that one a whirl, thanks guys.
The issue I had is that a newer version of Adobe had come out since GMPOWER's zip was released. There was another link in that thread to a newer zip (From another member) that ultimately resolved the issue.
There was one fix for boot loop involving Titanium backup, I used that one and never had the problem again.
I think that may be the one you are referring to?
I have an old NVIDIA Shield Tablet K1 that has served me very well since I bought it back in 2016.
Recently it was getting filled up and started to slow down, so I bit the bullet and restored the last factory recovery image.
That went perfectly fine except for one problem. I had zipped up my files prior to the reimage. When I unzip them back to the tablet, they wind up with current dates. This really messes things up.
After doing some searching, it seems that this is a limitation of Android 7. I've read that dates are preserved when copying to internal storage only if the device is rooted on this version of Android.
After doing some searches on rooting, I stumbled upon Magisk. Upon reading the installation instructions at https://topjohnwu.github.io/Magisk/install.html, I came away thinking that it sounds too good to be true. The instructions make it seem like rooting my device will be relatively straight forward.
Can it really be this simple to root? Is un-rooting as simple as flashing the original boot.img? I really don't need to be rooted normally. So after I restore my files with their proper dates I'd be happy to un-root. Unless there is some great things I can do with root that I've never needed to do before.
This latest version of Magisk is very new (just about a week at the time of this writing) so I imagine there hasn't been a lot of use of it on an old device like the K1. But if anyone has any experiences using this new Magisk to root older devices, I'd like to hear about it.
In case any other Shield owner stumbles upon this thread, just a quick follow up to say that it was indeed as simple and straight forward as the Magisk install instructions seemed to indicate.
I successfully rooted the Shield and was able to copy back my files with dates intact.
Now off to see if there is anything else handy that I can do with root!
Can you explain it step by step. I ttied, but nothing happened. I had to put some commands through the console, but the device was not found...I have the driver and everything...
Pudah said:
I have an old NVIDIA Shield Tablet K1 that has served me very well since I bought it back in 2016.
Recently it was getting filled up and started to slow down, so I bit the bullet and restored the last factory recovery image.
That went perfectly fine except for one problem. I had zipped up my files prior to the reimage. When I unzip them back to the tablet, they wind up with current dates. This really messes things up.
After doing some searching, it seems that this is a limitation of Android 7. I've read that dates are preserved when copying to internal storage only if the device is rooted on this version of Android.
After doing some searches on rooting, I stumbled upon Magisk. Upon reading the installation instructions at https://topjohnwu.github.io/Magisk/install.html, I came away thinking that it sounds too good to be true. The instructions make it seem like rooting my device will be relatively straight forward.
Can it really be this simple to root? Is un-rooting as simple as flashing the original boot.img? I really don't need to be rooted normally. So after I restore my files with their proper dates I'd be happy to un-root. Unless there is some great things I can do with root that I've never needed to do before.
This latest version of Magisk is very new (just about a week at the time of this writing) so I imagine there hasn't been a lot of use of it on an old device like the K1. But if anyone has any experiences using this new Magisk to root older devices, I'd like to hear about it.
Click to expand...
Click to collapse
Can you explain it step by step. I ttied, but nothing happened. I had to put some commands through the console, but the device was not found...I have the driver and everything...