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.
I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!
Try reflashing your recovery image.
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/
Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
ok thanks, i'll try it when I get back home
jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.
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.
I rooted my NC ages ago, first on 1.1 then on 1.2. When I updated to 1.3 (from reverted stock) I used the manual nooter to root it and that's where I've been for awhile.
I finally decided to update to 1.4.1, so I used the erase & deregister function, rebooted it, reregistered, and it's working fine, looking like a stock 1.3 device.
However, I can't get it to update to 1.4.1. First I tried using the manually downloaded update file from B&N's website. It didn't do its thing automagically when I followed the instructions on their site, so I searched various forums and found all sorts of suggestions on what to do.
None of them worked, including redownloading it from the NC itself and moving it to root, and renaming it to the old format "Sideload_update.zip".
Then I tried to just leave it on wifi for a couple hours and see if it would update that way. So far no luck.
Any suggestions on why it's not updating?
Do you have clockwork installed? It will block the update.
Sent from space
koopakid08 said:
Do you have clockwork installed? It will block the update.
Click to expand...
Click to collapse
I did at one time, but I thought I got rid of it with one of the erase/deregisters. If that's not the case, how do I get rid of it?
Philomorph said:
I did at one time, but I thought I got rid of it with one of the erase/deregisters. If that's not the case, how do I get rid of it?
Click to expand...
Click to collapse
Do you see CWR on your screen when you boot into recovery? If you do, you still have it on there and stock updates will not work whether you side load or wait for the OTA update (which has maybe just started now depending on how low your serial number is).
For a full recovery you could create a bootable card with CWR on it and after wiping everything install the stock 1.3 ROM found here: http://www.multiupload.com/3Y5MWE773D
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.