Related
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
johann718 said:
I am having problem updating to 2.340.
I just got a replacement DX from Verizon few days ago. As soon as I received it, I tried to do an update but the system said that I was up to date even though my software showed 2.315 so I decided to mod my DX right away since most people did not have problem updating with rooted DX.
Initially, I rooted my phone with Z4ROOT, reinstalled all the apps using Titanium Backup which i had on previous phone since I all the backups on my
SD card than I back up the stock ROM with Rom Manager. After that, I installed Bazinga2.1 Rom. Installed my apps again using titanium back up and back it up again using ROM Manager. After this, I installed BigDX blue theme. Couple a days ago, I got a notification that I have an update from Verizon which was 2.34 so I went back to recovery, restored back the Stock, using Z4Root, unrooted and download the 2.34 update and tried to install but the update failed. So I did a factory reset and put every thing back to stock and tried to update again and it still fails.
Once the update is down loaded, I try to install and its turns off the phone, than it shows a box with android next to it and it shows triangle with Exclamation and just reboots. Than it goes to clockwork mod recovery.
Why does my phone go to clockwork recovery even though I am UNROOTED?
Any help or input will be greatly appreciate it.
Thanks
Click to expand...
Click to collapse
Root and the bootstrapper are separate entities. Removing root, and removing the boostrapper manually (by renaming files in the system) will not fix your issue either.
The reason I know this is because I went through a number of ways to try to get the OTA, but could not.
I would suggest you hit MDW and get all of the latest files for the update, and do it that way.
You'll sbf, flash the leak for .320, then sbf .320, then flash the system for .340, then update the kernel, and radio afterwards. After that, you'll be back on the normal track.
It's a lot of steps, I guess, but it really doesn't take long.
Go grab the files ASAP, in case they get pulled, and follow all of the instructions carefully.
Whats MDW and why am I having this problem when everyone else is not. also, I removed Boostraper and it still go into recoverymod? I am just going to SBF reflash to 2.315 and see if it will work.
Here we go again!!!
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
I'm in a bit of a hurry so I haven't read the whole thread thoroughly, but if you're just trying to get it to stop booting into CWM, go to terminal emulator
Run "su"
Run "mount -o remount,rw /dev/block/mmcblk1p21 /system"
Run "cp /system/bin/logwrapper.bin /system/bin/logwrapper"
Reboot
bladebarrier said:
Lots of people had that issue.
Mdw is mydroidworld.com
Sbf all you like. I stand behind the advice I gave.
Also, if you had actually removed the bootstrap correctly, you couldn't possibly still end up in clockwork.
Either way, in about the time it took you to post, you could have used the steps I suggested and have been done.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice but I SBF my phone back to 2.315, than tried to do update again and it worked.
When I bought my used Nook Color, I used the 8 re-boot method to flash back to 1.0.0 ... de-registered... registered... updated to 1.1.0 ... then used Auto-Nooter 3.0 to get my perfect device.... Everything has worked great until the BN 1.2 update totally ruined by device!! I have tried booting off the uSD card for AutoNooter3.0 but doesn't work... I tried using 8 re-boots to get back to 1.0 (to start over)... doesn't work... i get the Android screen and it stays stuck on that screen no matter what I do!!! Please somebody help me!! I want to go back to stock 1.0 ... then 1.1 then Auto-Nooter 3.0... restore my Titanium... and turn off Auto-Updates (which I've just found instructions for.)
Thanks,
Kevin
Do you want to stay on eclair? I would highly recommend using one of the modified stock froyo (modified 1.2 update) roms from this site and flash it per site instructions. Then you could manual nooter it. Then due to cuurent limits on the root of 1.2, I would go to the dual boot thead and set up dual boot with froyo (1.2) on the second boot and cm7 on the first. Nothing beats cm7, especially if you add dalgrin's overclock to the works. If you end up not liking the setup, it's very easy to recover to stock.
No, I really just want to get back to my 1.1.0 ... with Auto-Nooter 3.0... restore my apps... and then turn off Auto Updates.
Actually, my problem right now is that I cannot seem to flash back to stock at all!!
You could try this if you have not already.
http://forum.xda-developers.com/showthread.php?t=945838
If you already tried to install a stock rom over the mess that B & N made, all you may need to do is a wipe data/factory reset from ClockworkMod Recovery. That might clear up some boot issues for you.
dapazz238 said:
.... and turn off Auto-Updates (which I've just found instructions for.)
Click to expand...
Click to collapse
Is there a confirmed method to prevent auto updating? <Link please?>
Look for the Pre-rooted 1.1 upgrade and flash that. I am not sure if it blocks automatic update.
This worked!!!
bonez318ti said:
Is there a confirmed method to prevent auto updating? <Link please?>
Click to expand...
Click to collapse
This is what I've used:
http://forum.xda-developers.com/showthread.php?t=946969
So far so good. No OTA and I've been on autonootered 1.1.0 since before the 1.2 update, and WiFi always on for the past couple of weeks.
Let me preface my question with some info:
I have tried the limited viability market fix detailed in the ManualNooter 4.5.6 no less than 10 times.
I have gone back to stock, side loaded 1.2, and did a complete redo of manualnooter (I followed every single word in every single step to a "T", BOTH times.
I saved, then uninstalled, and reloaded the market from Titanium.
I am not a complete noob (and by that I mean, I am not a natural at adb commands).
I have rooted an Eris, I have used autonooter, I have rooted my Incredible.
I have been reading through posts on XDA and other sites for 3 days.
I absolutely positively cannot fix the limited visibility problem with the Market.
Can anyone give me any guidance?
Is anyone else having this problem but me?
Thanks for your time!
lcoughlin said:
Let me preface my question with some info:
I have tried the limited viability market fix detailed in the ManualNooter 4.5.6 no less than 10 times.
I have gone back to stock, side loaded 1.2, and did a complete redo of manualnooter (I followed every single word in every single step to a "T", BOTH times.
I saved, then uninstalled, and reloaded the market from Titanium.
I am not a complete noob (and by that I mean, I am not a natural at adb commands).
I have rooted an Eris, I have used autonooter, I have rooted my Incredible.
I have been reading through posts on XDA and other sites for 3 days.
I absolutely positively cannot fix the limited visibility problem with the Market.
Can anyone give me any guidance?
Is anyone else having this problem but me?!
Click to expand...
Click to collapse
I did the same and had no problems. Try the new MN 4.5.18 and post your results. Did you add any apps, kernels? What was installed prior to going back to stock BN and which version of BN? Did you overclock or dual boot?
fpga_guy said:
I did the same and had no problems. Try the new MN 4.5.18 and post your results. Did you add any apps, kernels? What was installed prior to going back to stock BN and which version of BN? Did you overclock or dual boot?
Click to expand...
Click to collapse
Before doing Manualnooter, I wiped the device as per the directions (8 failed reboots, and factory reset, in that order...again, as per directions)
I did not add any apps (aside what was loaded natively via the manualnooter process before trying the market either time.
I have never overclocked, or dual booted my Nook.
From stock 1.1, I used autonooter to root. I never installed any ROMs. From that state, I unrooted, and rerooted with Manualnooter following ALL of the directions (including making the bootable sd with CM), and again, never loaded any custom ROMs.
Before I rooted, I had a pretty good number of apps loaded both from the market, and side loading. I never messed with the Nook too much (no tasker, no tether, never tried to get bluetooth working, and nothing where I had to alter any lines of code.
I'm at work right now, so unable to try 4.5.18 at the moment. When I have a chunk of time, I will try the entire process over again with 4.5.18 from complete scratch (including redoing the bootable sd, wiping with 8 interrupted boots, and factory reset, etc)
I will report back.
Thanks!
Lynn
Did you remember to register the device following the wipe? Seems the device needs to be registered prior to rooting.
I started with a stock Nook and rooted it, then 1.2 came out.
My sequence was to flash with 1.2 with CWM peinstalled. Then I rebooted and registered the device on gmail and Youtube.
Next I downloaded manual nooter and put in root of sd.
Rebooted to recovery and flashed manual nooter. booted and tested, installed Nook apps, then rebooted into recovery.
From recovery I flashed the kernal fix to allow moving apps to SD. Tested Works!
The ONLY remaining issue I have is that some large apps are not found in market.
Market was fixed!, had to clear market cache, then kill it, then cleared data for the google frame work part and killed it. Rebooted and now see many more apps, especially the larger ones. This info is near end of first post; http://forum.xda-developers.com/showthread.php?t=1054027
framitz said:
Did you remember to register the device following the wipe? Seems the device needs to be registered prior to rooting.
I started with a stock Nook and rooted it, then 1.2 came out.
My sequence was to flash with 1.2 with CWM peinstalled. Then I rebooted and registered the device on gmail and Youtube.
Next I downloaded manual nooter and put in root of sd.
Rebooted to recovery and flashed manual nooter. booted and tested, installed Nook apps, then rebooted into recovery.
From recovery I flashed the kernal fix to allow moving apps to SD. Tested Works!
The ONLY remaining issue I have is that some large apps are not found in market.
Click to expand...
Click to collapse
framitz,
I don't think I did. I don't remember doing that step at that point. And, I looked back over the directions I followed, and I didn't see that as a step. And I followed those directions like I needed to diffuse a bomb.
I'll follow your instructions when I get home, and let you know!
Thanks!!
lcoughlin said:
From stock 1.1, I used autonooter to root. I never installed any ROMs. From that state, I unrooted, and rerooted with Manualnooter following ALL of the directions (including making the bootable sd with CM), and again, never loaded any custom ROMs.
Click to expand...
Click to collapse
Instead of unrooting, etc.. just install BN1.2 from http://forum.xda-developers.com/showthread.php?t=1050520. I suggest using update-nc-stock-1.2-signed.zip.
From there MN should work fine...
My first MN followed the same process as yours (restore to stock, side load BN1.2). Subsequently, I used the nemith method.
fpga_guy said:
Instead of unrooting, etc.. just install BN1.2 from http://forum.xda-developers.com/showthread.php?t=1050520. I suggest using update-nc-stock-1.2-signed.zip.
From there MN should work fine...
My first MN followed the same process as yours (restore to stock, side load BN1.2). Subsequently, I used the nemith method.
Click to expand...
Click to collapse
I used update-nc-stock-1.2-keepcwm-signed.zip, which has the advantage of not needing to set up a bootable SD because CWM is already available.
To flash a new rom I just boot into recover, locate and install the zip file.
Battling Market Downloads with MN 4.5.6
Originally Posted by framitz>
My first MN followed the same process as yours (restore to stock, side load BN1.2). Subsequently, I used the nemith method.
I used update-nc-stock-1.2-keepcwm-signed.zip, which has the advantage of not needing to set up a bootable SD because CWM is already available.
To flash a new rom I just boot into recover, locate and install the zip file.
Click to expand...
Click to collapse
I did exactly this, then used MN 4.5.6 and had the same problem with "download unsuccessful" with the market. I was able to fix the limited market problem easily, but couldn't find a solution to the Market download problem.
Tired of beating my head against the wall at this point. Reverting back to my original ROM.
Update 20111117: Updated .zip file to Adobe Flash 11.1 and AIR 3.1.
Update 20111020: Updated .zip file to reinstall Flash and AIR, previous version didn't properly fix AIR.
Steps I used to update Adobe Flash (to version 11.0) and AIR (version 3.0) so it doesn't update automatically and thus get me back into the boot loop cycle (again):
Go to Titanium Backup ( Pro )
You need to uninstall with this since these are system apps
Buy a Pro key and keep it on your SD card root, since this app will save your bacon
Uninstall Adobe AIR and Adobe Flash Player from Titanium Backup
It will warn you that you are uninstalling a system app, that's OK
I think that is why the update through Market isn't working
Open Market, Install Adobe Air (3.1.0.488 as of this post) and Adobe Flash Player (version 11.1 11.1.102.59 as of this post)
Nook seems to be working after several reboots. Also, note that Adobe updated their apps. After following the procedure above, I was able to update via Market without any problems with bootlooping.
Obviously, the above steps only work BEFORE Adobe gets auto-updated and you get in the boot loop cycle. If you are already in the boot loop cycle, download this file (Updated link, should work better this time):
FlashPlayer11.1_AIR3.1_Update_Fix_20111117
and install it using a ClockworkMod Recovery SD card.
Get a ClockworkMod Recovery SD card
http://forum.xda-developers.com/showthread.php?p=11987469
Put the zip from the above post on the SD card
Reboot your Nook with the SD card inserted
Install from Zip, Select zip from SD card, select the flash update
This basically will uninstall flash and air as system apps and install as a user apps. This is based on the zip from GMPOWER which updated flash to 10.3, which worked for some but not others, perhaps because it didn't touch Air:
http://forum.xda-developers.com/showpost.php?p=16526691&postcount=7
Also note, I have been through several cycles of restoring backups, restoring to factory, re-rooting, etc. this last week, so I was getting very annoyed and cautious. I think I was able narrow it down to just the Adobe updates causing my problems. I have been able to update ROM Manager, Superuser, and just about everything else with updates; and besides the Adobe updates, everthing worked, and I don't currently have a boot loop problem.
Note, I didn't update Superuser or ROM Manager until after I applied the above updates to Flash and AIR. After several reboots, my Nook is still working fine.
For those of you who are still having trouble getting your Nook back, and the attached zip doesn't work for you, you can do the following. Using the instructions on this site, I got my Nook back up and running to factory new condition:
http://mrm3.net/nook-color-recover-any-bricked-device/
(Quick method at top, not older methods below; instructions slimmed down from several posts here at XDA, updated for stock 1.2) also here on XDA:
http://forum.xda-developers.com/showthread.php?t=914690 (original restore to stock post)
http://forum.xda-developers.com/showthread.php?t=1050520 (update for stock rom 1.2)
Then, I registered my Nook (again).
At this point, I could have tried to update to 1.3, but my patience was a bit low, so I didn't go for it. If you do, be sure to follow the appropriate ManualNooter instructions here:
http://forum.xda-developers.com/showthread.php?t=1054027
Since I was still on Stock 1.2, I rooted using ManualNooter 4.6.16
(while in CMR, after running ManualNooter, I also applied update-Froyo1.2-dalingrin-OC-emmc-090111.zip, and that seemed to work without a hitch)
Then I reinstalled all the other apps I wanted on my Nook,
=== BUT DID NOT YET UPDATE ADOBE FLASH OR AIR ===
Flashed ClockworkMod Recovery, updated a lot of my apps using Market and Amazon Appstore, restored data and other apps from Titanium Backup,
Then I made a full backup of my Nook using CMR. (still booting normal, running fast and clean)
After confirming my Nook was as I wanted it, and that I had a good backup, I did the steps at the top of this post to update Adobe Flash and AIR.
After confirming that was working, and getting another backup on my SD. I then did the updates to ROM Manager and Superuser. It seemed like those updates happened at the same time as the boot loop, so I was cautious. My Nook is still working well without boot loops as of yet.
Results:
Kernel: Stock 1.2
Rooted with: ManualNooter 4.6.16
Additional Mods:
update-Froyo1.2-dalingrin-OC-emmc-090111.zip,
ClockworkMod Recovery 3.2.0.1,
ROM Manager 4.5.0.1, Titanium Backup 4.5.2,
Adobe Flash 11.1, Adobe AIR 3.1 (uninstalled system app, reinstalled via Market, updated via Market)
[Update Zip] CMR zip to update Flash Player and Air
I updated the original post with a link to the zip to fix the FlashPlayer and Air apps. I had intended to post it here, but since I'm new, I can't link externally in a reply.
Please let me know if there are any problems with the zip and I will get it updated. It worked on my Nook.
I updated the zip file 20111020 to fix a problem with the AIR reinstall.
Wow, thank you so much for this! I wish I had known this on the weekend when I was gong crazy trying to figure out why I was getting bootloops over and over. I can't seem to give you thanks though (probably because I never post, just lurk).
So far I haven't done the uninstall/re-install with TB. I am just making sure my Adobe air and Flash don't update, and when Air did I went into Nook Color Tools and uninstalled the update to set it back to what it was originally. That worked but it is a pain if it keeps happening. I will try the TB to uninsall the programs.
I too did a update on ROM Manager and Superuser (and a binary update), and all is still well. No bootloops. I hold my breath though every time my NC gets to the "color" part until the N appears and it all disolves.
thanks for this!!! this was really getting very frustrating.
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Thanks for this information. My nc is currently in a bootloop and won't load CWR. It shuts off before getting to that point (my bootloop is adobe air related). None of the restore to stock via SD card have worked for me. I'm now looking at ADB options, the post you referenced with the fix has some instructions for that. Did you use the ADB or the SD card instructions? I was actually rooted with CM7 before the bootloop.
Thanks,
shy guy1 said:
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Click to expand...
Click to collapse
I realized that my zip was not working to uninstall and reinstall Air properly. Try the updated zip file in the post.
shelly29 said:
Did you use the ADB or the SD card instructions?
Click to expand...
Click to collapse
I used the SD card instructions. Unless you have done something strange to your nook (not sure what), it should always boot from the SD card first, so you should never have problems booting into CMR from an SD card.
If the link in the original post doesn't work for you to get a CMR SD card, try the instructions here:
http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
If you have a newer Nook, you may need to repartition your Nook's internal memory and use CMR version 3.2.0.1. See details here (this guy just condenses the instructions you can find on various posts on XDA, and tries to keep it up-to-date)
http://mrm3.net/nook-color-how-to-blue-dot-nook-color/
Also note that I updated the zip file in the post to correctly uninstall and reinstall Flash. I re=bootlooped my nook, and after applying the new zip, my nook was working.
Just an update....
I wanted to let U guys know that I had updated Adobe Flash, Air and Super Users and this has worked for me. I also went to double check the versions of both Flash an Air and they are the newest versions!? I still went to uncheck the "Update Automatically" setting in the market for them both just in case for future updates for the time being. Back up and Running! Thanks Again to ALL involved who put contributions to this
This may have worked for me
I tried the updated fix posted here, and the Nook booted properly. Thank you for this fix; I hope it continues to work for me.
I will have to locate the automated back up mentioned here (Titanium), and I will see how this works. I had been leaving my Nook on at all times to avoid the reboot until I turned it off yesterday, forgetting that I did not want to do that.
Awesome post.
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Thanks!!!! You are my new best friend. XD I ended up reflashing several times before I found this post. Followed the instructions and my Nook is happily running Android again without reinstalling (again!). I thank you. My Nook thanks you. And the Angry Birds who would have had to start from scratch thank you.
Thank you! It appears to work now. I've restarted a few times with success!
Took me about an hour to find this thead. I knew there would be an easier fix than starting from scratch. The zip worked on my rooted 1.2
Thanks! Keep up the good work
Thanks! That worked for me.
Stagnation1 said:
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Click to expand...
Click to collapse
From my previous searches, it seems the boot loop is usually caused by either an incompatible installation of Adobe flash, or an incompatible kernel (central part of the ROM). Hopefully the OP zip will fix the first, but I'm not sure of another way to fix the second, other than reflashing and rerooting. How far in the reflash/reroot process do you get before it boot loops again?
mastigia said:
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
Click to expand...
Click to collapse
Hmm, haven't seen that error. I'm not sure whether its related to the same problem. It sounds like you might need to re-register your nook with B&N. I'm not sure if you can do this without restoring to stock. Not much help, sorry.
I can't post a reply to this ([NC][1.2][1.3] ManualNooter 4.6.16) thread yet - Still new to these forums... I was one of the many in that thread who had installed ManualNooter 4.6.16 on Nook Stock 1.3 only to end up with a boot loop.
Wish I had found this thread last week - would have saved me a lot of headaches!
It's okay though - every boot loop is another opportunity to learn something new.
Thanks much for the easy walkthrough and I hope others find their way here too.
Just saw another new update for Flash & Air .. released yesterday I believe. Has anyone try them yet ? Just don't want to was my time getting into a boot loop again by updating it.
--
Just read there is a new update for stock Nooks... basically gives more comic-reading options.
I currently have a rooted Nook color and don't really see any real reason to want the latest Nook update, but did want to ask: What would happen if i did update? Would I need to root again afterwards?
I know there's guides on previous versions of Nook, but was wondering if anyone had experience yet w/ the latest update.
I just downloaded it to look at it. It is a complete reflash of your ROM. So my guess is it will undo root. And this from B&N:
The NOOK Color Ver1.4.3 update contains new features and enhancements, including:
• Zoom view in comics and graphic novels
• 2-Page mode in landscape for viewing PagePerfect™ and PDF documents
• Other minor system enhancements
Sent from my Nook Color running ICS and Tapatalk
Thanks for the reply, very helpful!
Mine just automatically updated to 1.4.3. When I boot up it asks if I want to go to the normal home or the rooted home. I can go to the rooted home and my apps are there but I can't launch Google Play. Also, if I select the N button and then Home it just goes back to the default Nook home and I can't switch back to the rooted home. I have to restart the Nook to get back.
I'm going to try nooting it again to see if that corrects the issue.
thegraak said:
Mine just automatically updated to 1.4.3. When I boot up it asks if I want to go to the normal home or the rooted home. I can go to the rooted home and my apps are there but I can't launch Google Play. Also, if I select the N button and then Home it just goes back to the default Nook home and I can't switch back to the rooted home. I have to restart the Nook to get back.
I'm going to try nooting it again to see if that corrects the issue.
Click to expand...
Click to collapse
I'm in the same state. One of my two Nook Colors auto-updated to 1.4.3 and I'm having the exact same symptoms. The other hasn't yet updated and still works fine. Please share your results
Update:
I used clockworkmod 3.2.0.1 and manualnooter 5.02.19. I reinstalled manualnooter without wiping the Nook and I am back in business on both of them
"back in business on both of them"
Including the google app marketplace? Super cool - the market (and gapps in general) require some things to be in /system to hook into to handshake with the Google servers.
I threw together a super minimal "install su and busybox" rooting tool that lets all of my apps run as I prefer but doesn't include the Market. Nice to know I'll be able to get the Market back as soon as I like.
thegraak said:
Mine just automatically updated to 1.4.3. When I boot up it asks if I want to go to the normal home or the rooted home. I can go to the rooted home and my apps are there but I can't launch Google Play. Also, if I select the N button and then Home it just goes back to the default Nook home and I can't switch back to the rooted home. I have to restart the Nook to get back.
I'm going to try nooting it again to see if that corrects the issue.
Click to expand...
Click to collapse
This is why you're supposed to disable OTA updates when you Root a Device. Otherwise your device will update without your permission or foreknowledge. Usually it'll reset everything in System so you'll loose things like Root and Gapps.
Personally I just run CM9 off my 16gb class 10 SDcard. No OTAs to worry about and I get pure Android, all without modifying any of the Nook's Internal Memory.
roustabout said:
"back in business on both of them"
Including the google app marketplace? Super cool - the market (and gapps in general) require some things to be in /system to hook into to handshake with the Google servers.
I threw together a super minimal "install su and busybox" rooting tool that lets all of my apps run as I prefer but doesn't include the Market. Nice to know I'll be able to get the Market back as soon as I like.
Click to expand...
Click to collapse
Yup, everything works fine. I was able to install a new app after the update from the Play store
I've been out of the loop for awhile but need to restore my NC to stock to sell it. What's the easiest way to do it? I'm currently running an older version of ICS from cyanogen. Help?
eyecrispy said:
I've been out of the loop for awhile but need to restore my NC to stock to sell it. What's the easiest way to do it? I'm currently running an older version of ICS from cyanogen. Help?
Click to expand...
Click to collapse
Download the latest update from B&N, download the CWM 3.2.0.1 SD Card Image from here, create a CWM uSD Bootable using Win32 Image Writer, link here, load the downloaded Update file from B&N into the uSD, turn on/reboot NC, clear System, Data, Cache, install the update.
thewaywardgeek013 said:
Download the latest update from B&N, download the CWM 3.2.0.1 SD Card Image from here, create a CWM uSD Bootable using Win32 Image Writer, link here, load the downloaded Update file from B&N into the uSD, turn on/reboot NC, clear System, Data, Cache, install the update.
Click to expand...
Click to collapse
You forgot a very important part... follow the first portion of the Customize ROMs thread in my signature... B&N stock is not CWM flashable until the first edit in that thread is made.
DizzyDen said:
You forgot a very important part... follow the first portion of the Customize ROMs thread in my signature... B&N stock is not CWM flashable until the first edit in that thread is made.
Click to expand...
Click to collapse
Thanks for correcting me there, thought that it was possible already to install it thru CWM…
bigdweeb said:
Update:
I used clockworkmod 3.2.0.1 and manualnooter 5.02.19. I reinstalled manualnooter without wiping the Nook and I am back in business on both of them
Click to expand...
Click to collapse
I tried this and I cannot access the market. I had a stock unrooted 1.4.2 and then rooted using mn 5.02.19 on CWM 3.2.0.1
My device is rooted but the Market will not download apps. I have followed the guides to clearing the Vending.apk cache and Google Framework Services here: http://forum.xda-developers.com/showthread.php?t=1494901 but Market is not updating and I cannot install apps.
Even after flashing the two files here: http://bookclubs.barnesandnoble.com...tock/m-p/1356004/message-uid/1356004#U1356004 and then re-flashing MN 5.02.19 I just have root.
Currently I have the standard/stock build.prop. I can push files to /system/app and /data/app but that is getting old. And so far no combination of checking or unchecking the NookTools toolbox is letting me install apps via Market.
Any help would be greatly appreciated!
tigger2u said:
I tried this and I cannot access the market. I had a stock unrooted 1.4.2 and then rooted using mn 5.02.19 on CWM 3.2.0.1
My device is rooted but the Market will not download apps. I have followed the guides to clearing the Vending.apk cache and Google Framework Services here: http://forum.xda-developers.com/showthread.php?t=1494901 but Market is not updating and I cannot install apps.
Even after flashing the two files here: http://bookclubs.barnesandnoble.com...tock/m-p/1356004/message-uid/1356004#U1356004 and then re-flashing MN 5.02.19 I just have root.
Currently I have the standard/stock build.prop. I can push files to /system/app and /data/app but that is getting old. And so far no combination of checking or unchecking the NookTools toolbox is letting me install apps via Market.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Under the "Let's get started:' section in the MN 5.2.19 OP thread, perform step #14, let Market update by waiting patiently for some time.
Check comment #216 in that thread from reebz which he resolved a problem like yours.
8GB 1.4.3 Nook Tablet Root?
So I am really new to this whole idea of rooting but I was wondering if anyone has found a reliable way to root the new (1.4.3) nook tablet? PLEASE!
Error message
DizzyDen said:
You forgot a very important part... follow the first portion of the Customize ROMs thread in my signature... B&N stock is not CWM flashable until the first edit in that thread is made.
Click to expand...
Click to collapse
I have downloaded the update twice from B&N and copied it to the sd card root. Keep getting a message when I try to install the update, using your instructions, that it can't open the archive (bad).
I am trying your method because I can't get the Nook to update normally. I even followed the default NookColor reset instructions then tried to install the update. The update would never even start. Currently sitting at 1.3.0. So I decided to try this CW mod route. More problems...
This update process is getting so frustrating...... I must assume at this point that the archive is bad again. Tried using both IE and Firefox (heard FF causes problems). The CW boot process worked fine so that's not it.
Not sure what more I can do.
Psyphurr said:
I have downloaded the update twice from B&N and copied it to the sd card root. Keep getting a message when I try to install the update, using your instructions, that it can't open the archive (bad).
I am trying your method because I can't get the Nook to update normally. I even followed the default NookColor reset instructions then tried to install the update. The update would never even start. Currently sitting at 1.3.0. So I decided to try this CW mod route. More problems...
This update process is getting so frustrating...... I must assume at this point that the archive is bad again. Tried using both IE and Firefox (heard FF causes problems). The CW boot process worked fine so that's not it.
Not sure what more I can do.
Click to expand...
Click to collapse
You can't edit the zip with archive software. You must entirely extract it, then edit the files, then rezip and re-sign the zip.
To save you the effort, I made a version of 1.4.3 that is CWM flashable and posted it. See my tips thread linked in my signature. See item A12.
I'm using CM10 internally. Do I need to update to firmware v1.43 or not needed anymore?
carlo.edmon said:
I'm using CM10 internally. Do I need to update to firmware v1.43 or not needed anymore?
Click to expand...
Click to collapse
Not needed.