Okay, if you have received the 1.3 update or you want to get it, this has worked for a few people now (thanks to billingdl for figuring our walking this path first!). This has only been tested for going from rooted 1.2 to 1.3. No idea on how it will fare with other changes.
You will need a bootable CWM card for this procedure. Look here for that. Then put these files on it:
manualnooter-4-5-18.zip
manualnooter-4-6-16a.zip
Note: Rom Manager is included as part of MN.
You'll notice that MN has an 'a' on it. I added two things there: the final fix for build.prop that was never updated and I also added a script to update the database to block OTA updates (this has worked for me) as found here.
Okay, so here we go...
1. Get the 1.3 update. YOU WILL LOSE ROOT! But don't fret - you shouldn't lose anything else.
2. Shut down your nook and boot with the bootable card.
3. Install manualnooter-4-5-18.zip and then reboot.
4. You have root now, so go launch the market and sign in.
5. Shut down your nook again and boot with the bootable card.
6. This time install manualnooter-4-6-16a.zip.
6a. If you want to, you can also install Dalingrin's OC kernel while you're here, which he recently updated with the 1.3 source. Your choice, but the file is here.
7. Reboot again.
8. Put your regular "data" SD card in for this step - Go into Rom Manager and run the 'Fix Permissions' option.
9. Go into Nook Color Tools and note the check box at the top. After 1.3 for most (if not all) people, the label is missing now. Uncheck and check the box anyway and close NCT.
10. Reboot
and Voila! All should be working!
root seems to be back after step four, but I wasn't unable to open the market until loading up 16a. Looks good so far though!
Your instructions didn't work for me
I purchased a Nook Color in July. It came with Froyo 1.2. I rooted it using Manual Nooter 4.6.16 shortly afterwards and was loving it!
Then last night, the Nook OTA auto-updated me to the Nook 1.3 firmware.
This morning when I picked up my Nook, I noticed that my Android Market, Google Email and Calendar apps icons had changed. When I tried to start them, I got a "App not found" error message. Then after some exploration, I discovered that I had I had lost Root access.
I followed your instructions. After installing Manual Nooter 4.5.18 and rebooting my Nook, I had root access again. However, when I tried to run the Android Market app I got a prompt saying "loading...", then the app closed.
I tried a couple of times with the same outcome. I then ran Rom Manager, was prompted for super user access and allowed it. I then selected the fix permissions option and rebooted the Nook, but the Android Market app still had the same issue as above.
I then figured I move ahead and install Manual Nooter 4.6.16a in hopes it would fix the problem. After applying it and rebooting my Nook, I again tried to start the Android Market app. This time, on the first attempt to run it, I was prompted to set up a Google account. I selected the existing account option and provided my account name and password. I received a confirmation that my android device was now associated with my Google account.
When I attempted to run the Google Market app again, I experienced the same issue as above. I got a prompt saying "loading...", then the app closed.
I again used Rom Manager and selected the Fix Permissions option and rebooted my Nook again. After rebooting I still have the same problem with Android Market app - starts to load then closes.
Now I'm stuck...
Anyone else experiencing the same behavior? Anyone have suggestions for how I might fix the issue?
For those of you who have been lucky enough to dodge the Nook OTA 1.3 firmware auto-update, I'd highly recommend you disable your wireless until you are able to turn off the auto-upgrade to avoid this unpleasant experience.
I'd be very happy to return to Nook 1.2 firmware with Manual Nooter 4.6.16. It was working perfectly for me and allowed me to access, load and run Android Market apps without any problem.
...Steve
ManualNooter was never about blocking updates, it's about keeping the device as fully functional as possible INCLUDING updates while adding more to the device such as a proper Android Market. Unrooting was always going to be a side effect of the update, which should of easily been fixed by by just reapplying 4.6.16. As for the build.prop "final fix", what exactly is that?
Also any indication on WHY this works would be more helpful than you repackaging 4.6.16 with stuff it wasn't designed to have.
GabrialDestruir said:
ManualNooter was never about blocking updates, it's about keeping the device as fully functional as possible INCLUDING updates while adding more to the device such as a proper Android Market. Unrooting was always going to be a side effect of the update, which should of easily been fixed by by just reapplying 4.6.16. As for the build.prop "final fix", what exactly is that?
Also any indication on WHY this works would be more helpful than you repackaging 4.6.16 with stuff it wasn't designed to have.
Click to expand...
Click to collapse
Wish I could say why it works. Like I said, the only thing I did with it was put the build.prop fix in and add the ota change. But others had it work using the last published MN of 4.6.16. I'd love to be able to say it was something I did, but it's not. I was just trying to pull everything together for folks...
sbrack01 said:
I purchased a Nook Color in July. It came with Froyo 1.2. I rooted it using Manual Nooter 4.6.16 shortly afterwards and was loving it!
Then last night, the Nook OTA auto-updated me to the Nook 1.3 firmware.
This morning when I picked up my Nook, I noticed that my Android Market, Google Email and Calendar apps icons had changed. When I tried to start them, I got a "App not found" error message. Then after some exploration, I discovered that I had I had lost Root access.
I followed your instructions. After installing Manual Nooter 4.5.18 and rebooting my Nook, I had root access again. However, when I tried to run the Android Market app I got a prompt saying "loading...", then the app closed.
I tried a couple of times with the same outcome. I then ran Rom Manager, was prompted for super user access and allowed it. I then selected the fix permissions option and rebooted the Nook, but the Android Market app still had the same issue as above.
I then figured I move ahead and install Manual Nooter 4.6.16a in hopes it would fix the problem. After applying it and rebooting my Nook, I again tried to start the Android Market app. This time, on the first attempt to run it, I was prompted to set up a Google account. I selected the existing account option and provided my account name and password. I received a confirmation that my android device was now associated with my Google account.
When I attempted to run the Google Market app again, I experienced the same issue as above. I got a prompt saying "loading...", then the app closed.
I again used Rom Manager and selected the Fix Permissions option and rebooted my Nook again. After rebooting I still have the same problem with Android Market app - starts to load then closes.
Now I'm stuck...
Anyone else experiencing the same behavior? Anyone have suggestions for how I might fix the issue?
For those of you who have been lucky enough to dodge the Nook OTA 1.3 firmware auto-update, I'd highly recommend you disable your wireless until you are able to turn off the auto-upgrade to avoid this unpleasant experience.
I'd be very happy to return to Nook 1.2 firmware with Manual Nooter 4.6.16. It was working perfectly for me and allowed me to access, load and run Android Market apps without any problem.
...Steve
Click to expand...
Click to collapse
I decided to go back and give it a try again from the top. (I had nothing to lose).
The second time I applied MN 4.5.18 and rebooted, the Android Market started working. I was able to connect and I tested installing an app just to make sure it was fully functional.
Great - Then I figured I try to move forward and re-apply MN 4.6.16a. After doing so and rebooting, the issue with Android Market app NOT working returned, ("loading..." message followed by a shutdown of the app). I then realized that wifi wasn't working properly after applying MN 4.6.16a. Checking the settings panel revealed that wifi was off. Every attempt to turning on wifi resulted in a wifi error. Tried applying ROM Manager 'Fix Permissions' again just in case - but wifi problem persisted.
So, I decided to go back and reapply MN 4.5.18 once more. Voila - the wifi and the Android Market started working again.
So I'm now running with MN 4.5.18 and Nook firmware 1.3
I should note that I did apply the optional over-clocking update that you included in your instructions above after applying MN 4.6.16a. Don't know if that is related to the wifi problems I experienced.
Anyway - I've got my Nook Rooted again and running Android Market so I'm happy.
Hope the above info is useful to others who might have the same experience I did.
...Steve
FYI... Did some more follow-up. Tried another version of MN 4.6.16...
Seems that MN 4.6.16 with Nook firmware 1.3 breaks wifi. After applying it, checking the settings panel shows "error" under wifi and wifi is off. Attempts to enable it result in a wifi error. Checking the Nook device info shows an empty MAC address.
So on my Nook there's definitely something incompatible between MN 4.6.16 and Nook firmware 1.3. On doing some googling, wifi improvements are mentioned as one of the optimizations included with firmware 1.3. So maybe that's where the issue lies.
Anyway it's easy to re-apply MN 4.5.18 and once that's done things seem to work fine with firmware 1.3.
...Steve
Try removing the Kernel from 6.16 and see if that works.
sbrack01 said:
FYI... Did some more follow-up. Tried another version of MN 4.6.16...
Seems that MN 4.6.16 with Nook firmware 1.3 breaks wifi. After applying it, checking the settings panel shows "error" under wifi and wifi is off. Attempts to enable it result in a wifi error. Checking the Nook device info shows an empty MAC address.
So on my Nook there's definitely something incompatible between MN 4.6.16 and Nook firmware 1.3. On doing some googling, wifi improvements are mentioned as one of the optimizations included with firmware 1.3. So maybe that's where the issue lies.
Anyway it's easy to re-apply MN 4.5.18 and once that's done things seem to work fine with firmware 1.3.
...Steve
Click to expand...
Click to collapse
There are many variables in getting BN1.3 to be rooted and functional:
1. the method to get to BN1.2: upgrading to BN1.2 via wifi or restoring to BN1.2 via Nemith's zip file.
2. whether CWM is installed on emmc or not.
3. green dot NC or not?
Thanks to OP, i have my NC 1.3 rooted and functional. By the, Flash 10.3 is part of NC 1.3. This is how I got there:
- restore to stock BN1.2 via Nemith's zip file with no CWM on emmc.
-apply MN4.5.18
- get NC working with gmail, apks', etc... still on BN1.2 but rooted
- side load BN1.3 update
- apply MN 4.5.18 - but be sure to wait until it's done 10-15 minutes
- apply MN 4.6.16a
- fix permissions
- install Dalingren's updated OC kernel
Everything works like a champ.
Thanks don caruana! I followed your instructions exactly and they worked perfectly! Like another poster, I didn't have the market back until after I uploaded MN 4-6-16a but everything is back to normal now. Yay!
If I am running cm7 off emmc, i should not even get prompted for this update, correct?
I am not dual booting, just straight cm7!
I'm having a problem.
I was on 1.2 w/MN 4.6.16 and get the OTA to 1.3.
I just flashed MN 4.5.18 and rebooted.
When I launch market, I get a message saying "you must add an account to the device to continue. Do you want to add one now"? If I select either yes or no, it takes me back to my home screen.
What do I do now?
lexluthor said:
I'm having a problem.
I was on 1.2 w/MN 4.6.16 and get the OTA to 1.3.
I just flashed MN 4.5.18 and rebooted.
When I launch market, I get a message saying "you must add an account to the device to continue. Do you want to add one now"? If I select either yes or no, it takes me back to my home screen.
What do I do now?
Click to expand...
Click to collapse
Try going in to gmail and setting up your account there, then go back to the market. You could also clear data for the market and see if that helps.
doncaruana said:
Try going in to gmail and setting up your account there, then go back to the market. You could also clear data for the market and see if that helps.
Click to expand...
Click to collapse
Gmail and Talk both automatically close immediately, clearing data for market doesn't change anything. I got into youtube, chose my channel and it took me to an add account option and when I click that it says "there was a problem authenticating."
Now what?
lexluthor said:
Gmail automatically closes immediately, clearing data for market doesn't change anything. I got into youtube, chose my channel and it took me to an add account option and when I click that it says "there was a problem authenticating."
Now what?
Click to expand...
Click to collapse
That kinda sounds like a network issue of some sort. Try logging into your account from your pc. Also, can you browse the internet with the nook?
doncaruana said:
That kinda sounds like a network issue of some sort. Try logging into your account from your pc. Also, can you browse the internet with the nook?
Click to expand...
Click to collapse
Account works fine on the PC. Nook can browse the internet.
Any other ideas? Argh.
lexluthor said:
Account works fine on the PC. Nook can browse the internet.
Any other ideas? Argh.
Click to expand...
Click to collapse
You know, I had the issue where the market closed immediately on me when I tried to put mn4.6.16 on first. You could try a few things here...
Try going ahead with 6.16 and see if that works
or
Reapply 5.18
or
Reapply the 1.3 update and start over with the process
Unfortunately this thing seems to be a bit of a mystery (no one even knows why 5.18 first works for some), so just keep plugging at it and report back in case anything inspires someone more knowledgeable than me.
I reapplied 5.18 and then rebooted, same thing.
I then applied 6.16a and rebooted. This time I got the same thing about needing to added an account, but when I said yes, it let me add the account.
I then ran fix permissions and rebooted one more time for good measure.
Things all look good now!
Thanks so much.
Hopefully this helps anyone else with the same issue.
I guess I don't have to worry about a future OTA forced upon me now since I used the "a" version. What exactly does the "final fix for build.prop" do though?
lexluthor said:
I reapplied 5.18 and then rebooted, same thing.
I then applied 6.16a and rebooted. This time I got the same thing about needing to added an account, but when I said yes, it let me add the account.
I then ran fix permissions and rebooted one more time for good measure.
Things all look good now!
Thanks so much.
Hopefully this helps anyone else with the same issue.
I guess I don't have to worry about a future OTA forced upon me now since I used the "a" version. What exactly does the "final fix for build.prop" do though?
Click to expand...
Click to collapse
Glad that worked for you!
The build.prop thing is an issue where the original intent of MN was to change the fingerprint of the device for improved market visibility. It was supposed to change to "samsung/GT-P1000/GT-P1000/GT-P1000", but the script had an error and it just got left at zoom2. I can't tell you what the difference in visibility is, but it was a fix that never got implemented, so I slapped it in there.
BTW, I'm sure you're skittish at this point, but you might want to look at Dalingrin's OC kernel, if you haven't already. Although the first thing I'd do is take a full backup with CWM!!
Happy "Nook"ing!
Thanks doncaruana!
This worked for me too, however, I had the same initial problem with Market as two other posters where it would FC when fired up as per your instructions. But after applying the MN 4.6.16a, it fired up fine. I'm wondering if it had to do with my SD card though. I did not have my "normal" SD card installed when I first fired up Market, but I did have it in once I had applied MN 4.6.16a, so no big deal. Just successfully downloaded/updated a dozen apps. from the Market with no problem and definitely have root again. System reports BN software version 1.3.0. Thanks again for all of your work on this, esp. regarding no OTA updates; obviously the otacerts.zip rename doesn't work since that's what I had in place and I still got 1.3 pushed!
One question for you though - does the DB OTA fix disable any BN features other than OTA updates (e.g. in store stuff, etc.)?
Related
Hey everyone, I'll up front say I'm more a user than a tweaker, so right now my NC (and my wifes) work awesome. I am currently on CM7, but my wife and many folks need to use the stock ROM and until a clean way to update with autonoot and such comes out, hopefully this is useful.
Clockwork Mod won't install an OTA, but I have a feeling that it'll still download it and try to install it, and I'm afraid it will try to install it over and over as long as the file is there. So moving to CWM to avoid the OTA is out.
Renaming otacerts doesn't work, lots of accounts of that.
But in my experience, OTAs always compare the build prop to see if they need to OTA, so what I'm going to do to my NC and my wifes NC is modify the build prop to the new settings and see if that avoids the OTA.
BTW, I know Nookie Froyo, CM7 etc won't OTA, etc, so now that's out of the way....
Due to multiple reports that using Root Explorer has somehow screwed up the system requiring users to manually re-copy their old build.prop back, I suggest you DO NOT use Root Explorer to do this.
First thing is look in /media for the uploader, in case it's already downloaded. Delete it if it's there! If you're paranoid, check when you're done with the following too, just in case it snuck in while you were editing
Get the new build.prop from here:
If you're still on Eclair: http://dl.dropbox.com/u/334233/build.prop-1.3.0-eclair
If you're on Froyo: http://dl.dropbox.com/u/334233/build.prop-1.3.0-froyo
Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system
Push the new build.prop to your system
Code:
adb push build.prop-1.3.0-[COLOR="Red"]YOURBUILD[/COLOR] /system/build.prop
Note you need to replace YOURBUILD with the appropriate build, Froyo or Eclair, or whatever you named the build.prop..
Now your NC should have thew new build.prop, so now reboot. When you reboot, you should get a pop-up message with a green N saying you've updated to 1.3, but you should not see any update progress dialogs or any indication there was an actual update. Hopefully this makes it not try to OTA to 1.3.0! Please report back! It worked for 1.0.1 with the 1.1.0, as well as the 1.2.0 update out there, and it should work for 1.3.0.
Below is for old 1.2.0 information, don't use this unless you're sure you need to!
Get the new build.prop from here: http://dl.dropbox.com/u/334233/build.prop-1.2.0
Remount the system r/w
Code:
adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system
Push the new build.prop to your system
Code:
adb push build.prop-1.2.0 /system/build.prop
Once I get a little feedback on this, I'm going to move it to the NookDevs wiki, just don't want to put nonsense there if that's what it is I've done this to both my NC and my wifes, no problem so far, and hopefully it avoids the OTA.
done - we'll see what happens next ....
newbie
Hello
I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise
JF-WS6 said:
Hello
I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise
Click to expand...
Click to collapse
I'll keep revising the instructions in the first post, but that's so far the only theory that hasn't failed yet... So get adb to work and follow the instructions. You can do it over Wifi, so even if USB isn't working out for you due to your OS, the Wifi ADB widget on the Market will work.
How to use ADB itself, you can google.. It's fairly straightforward. Basically you'll just need to adb connect ip : port once you know it, the Wifi ADB widget tells you when it sets up.
FYI, I just did all of this from Root Explorer on the device. I snagged yer file from your dl.dropbox link, copy it over via root explorer, and set the rights. When I restarted, the little green n told me I had recently updated.
Maybe we can bypass optional future updates by changing our version to something really high like 1.99?
Yes I know I never say anything on here but will now. I have used something like this on before I I do think this will work just fine as the Nook already things it's updated so when it checks it's going to see that it is already updated.
Now as to what BN will do in a week or so who knows. We just need some more support for roms and so on for the nook and we will be good to go.
ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.
Used your download link to install it. Says I updated to 1.1.0. Thanks
danguyf said:
ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.
Click to expand...
Click to collapse
Um, yeah... Let me explain further I guess?
B&N Components decide it needs an update, downloads it
B&N components see the update is downloaded, sets up the OTA update, reboots
Clockwork Recovery does NOT update
System boots
Repeat step 2 - 5 forever?
That's what I meant by "Clockwork won't install an OTA" and such.
MattJ951 said:
Used your download link to install it. Says I updated to 1.1.0. Thanks
Click to expand...
Click to collapse
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.
khaytsus said:
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.
Click to expand...
Click to collapse
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.
bdcrim said:
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.
Click to expand...
Click to collapse
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
khaytsus said:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
Click to expand...
Click to collapse
Thanks again.
khaytsus said:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that
Click to expand...
Click to collapse
I just checked the about settings and it also says 1.1.0 . If im on 1.1.0 I don't really mind since my device is still rooted and works identically to how it did a day ago. I'm guessing it pulls the about settings pulls the data from the build.prop every reboot
Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).
skaman77 said:
Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).
Click to expand...
Click to collapse
Good thought. Do you want to flip a coin or draw straws?
As soon as I saw the thread about the 1.1.0 update today, I turned my WiFi off. There was no zip file in my /media folder or on root when I made the changes to the build.prop file. When I rebooted, I received a notice in the bar that my Nook Color software had been updated. WiFi is still off, but I am going to turn it back on and see what happens.
i also updated file lines thru root explorer and gave me massage that i had been updated. crossing fingers
First off, I'd like to thank everyone for their feedback in my previous thread (http://forum.xda-developers.com/showthread.php?t=958319).
So...I'm running Nookie Froyo on my NC and loving it. I followed the instructions at NookDevs and got youtube, flash, and the market working.....for the most part. I can't see all the apps in the market that I should be able to. Like I said, I followed the NookDevs instructions (twice) for removing the geographic restrictions on the market, but certain apps still aren't showing up. For example, I can see Angry Birds Seasons, but not regular Angry Birds. Another one that springs to mind that I couldn't find was OneClick Widgets. I know there were a few more that don't come to mind now.
Any ideas on why this might be happening? Thanks in advance for any help!
--Adam
I got this too running 1.1 and did auto nooter. I just got my nook 2 days ago so Im reading up on everything still. I was thinking about jumping to at least froyo soon.
No offense, but this should be in general.
niphoet said:
...I can't see all the apps in the market that I should be able to. Like I said, I followed the NookDevs instructions (twice) for removing the geographic restrictions on the market, but certain apps still aren't showing up. For example, I can see Angry Birds Seasons, but not regular Angry Birds. Another one that springs to mind that I couldn't find was OneClick Widgets. I know there were a few more that don't come to mind now.
Any ideas on why this might be happening? Thanks in advance for any help!
Click to expand...
Click to collapse
After installing Nookie Froyo to SD, getting the Gapps, market, etc... I could see all the apps I use on my HTC incredible or Droid X.. I followed the instrutions at -> http://nookdevs.com/NookColor:_Nookie_Froyo_Tips for editig the fingerprint in build.prop, using the string they had, but still I couldn't find apps like FancyWidget MSNBC, Fandango, Cardstar, and a few others.
I just did it again, this time using the fingerprint of my X...
ro.build.fingerprint=verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys
Now, when I search, I can find/install each of the apps I was looking for.
one other note.. it does try to update Youtube and google maps. I'm not sure if that is safe with this NookieFroyo or not!
KidJoe said:
I just did it again, this time using the fingerprint of my X...
ro.build.fingerprint=verizon/shadow_vzw/cdma_shadow/shadow:2.2.1/VZW/23.340:user/ota-rel-keys,release-keys
Now, when I search, I can find/install each of the apps I was looking for.
one other note.. it does try to update Youtube and google maps. I'm not sure if that is safe with this NookieFroyo or not!
Click to expand...
Click to collapse
No luck with your fingerprint, I might try the one from my EVO.
niphoet said:
No luck with your fingerprint, I might try the one from my EVO.
Click to expand...
Click to collapse
same here (10 chars)
The fingerprint isn't the only thing that needs changing on the Nook. You'll need to make sure the Market "believe" you have a certain amount of software and the permissions to go with it.
I won't give you a precise answer, but you could for example compare your system/etc/permissions folder with another "working" android device. You'll see that permissions are often very limited on the nook.
So if you don't care about getting your hands dirty, try copying your permissions from one device to your nook.
Just some ideas.
Sam
Oh, I forgot.. one other thing, because I had problems adding a google account and accessing the market originally, I also did what was listed in -> http://forum.xda-developers.com/showpost.php?p=11377098&postcount=14
I am aware i will receive crap for asking. I am a noob and i am having a hard time gaining access to all of the wonderful apps in the marketplace. I have appbrain and it helps. But i would like as much as i could get. Even if someone has a little patience to spend some time with me so that i can become familiar with such would be awesome. If not, oh well. Still a cool tablet.
Sent from my LogicPD Zoom2 using XDA App
Re: SOLVED - New2b Step by Step
For those of you having trouble with the market on the 0.6.8 by Brian here is the newb step by step. Mine works great. These are Brian's instructions with my additions. Very simple and has worked on all 3 of my Nooks. Flawlessly!!!
Instructions:
Download the zip file
Unzip the image file
Burn the image to sdcard
Shutoff your nook and insert the sdcard you just created
Boot your nook to sdcard
Under the "mounts and storage" menu, choose "format cache"
Press the power button to go back to the main menu
Choose "install zip from sdcard"
Choose "choose zip from sdcard"
Choose the zip file
After the image is installed, remove the sdcard
Press the power button to go back to the main menu
Choose "reboot system now"
Go into applications
Manage applications
Chose market
Clear cache not data
Now reboot with the 3.0.0.5 Version of clockwork
Choose mount
Reformat cache
Reboot again
After the nook has reboot
Configure the wireless, setup your google account
The market will now work
Install Flash and YouTube
BTW Brian FTW Great work, I like your setup the best
Lopht said:
For those of you having trouble with the market on the 0.6.8 by Brian here is the newb step by step. Mine works great. These are Brian's instructions with my additions. Very simple and has worked on all 3 of my Nooks. Flawlessly!!!....
Click to expand...
Click to collapse
that looks like the guide for installing Froyo onto eMMC..
What about for those running on bootable MicroSD?
I am still having issues. However, when I connect USB, I can download Market apps. Very strange. Any ideas?
Nookie Froyo Market Won't Download
The easy fix for me . . .after installing the 8gb customized nookie froyo rom was to pull my sd as booting, or as shutting down. This enabled me to finally boot into recovery. Once you do get booted into recovery RE-INSERT THE SD CARD, then FORMAT CACHE (scroll through the various options and you'll find it) Do this, and your market should start working again . . .forget about the clear data, clear cache, force stop, reboot steps. Just format the cache when you figure out how to boot into recovery, as the rom i used didn't boot into recovery when the option was selected from Clockwork. Btw, I am booting from sd with Nookie Froyo, stock nook is untouched.
To summarize
Find a way to boot into recovery
Make sure your sd card is inserted
Format cache and reboot
Customized Nookie Froyo - Can't see market apps
Sorry all, I'm very new to the nook. I did my best to try to look around for an answer to this question, please forgive me if I overlooked something.
Anyway, I put the customized Nookie Froyo on an 8GB SD card and everything has been working great. However, some of the apps wont show up at all in the market. For instance, google maps is not installed, nor will it show up via a query in the market. If I go to market.android.com, it tells me my device is unsupported for the map application.
Can anyone give me a tip to get me started on fixing the issue?
Thanks everyone!
EDIT
Nevermind, I followed the directions on the nookdevs.com tips section and got it working...I just needed to dig a bit further.
Thanks everyone!
So I managed to get CM7 on my nook fairly easily just now (latest versions for everything) however when I was up and running it asked me to upgrade my cm7 version in the notification area. I did but now I have no access to the market. I see the icon but nothing happens when I press it. If I goto manage applications, the market doesn't appear there either. Did I miss something?
The market worked previously, although it was the old school android market, not the new one. I thought that was odd, but after the cm7 update, the market doesnt open.
Reflash gapps
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Will do. Wiped the SD card to use as storage so ill have to readd the zip.
Thanks and ill report back.
Bingo. I got a different version of gapps and flashed that, everything works and I have the new market as well.
+1 on thanks.
Wiped the SD card to use as storage so ill have to readd the zip.
Click to expand...
Click to collapse
You didn't really have to do that if you are running CM7 and CWR off the internal eMMC. Just put the .zip on the card, boot into CWR and install .zip from card.
But since you are up and running I guess the point is moot for you.
So I've come across a different problem. I'm trying to get netflix to work but the market tells me "Your device is not compatible with this item".
I looked around and I think I found a fix but I needed to install ES File Explorer..I went to download that and...
"Your device is not compatible with this item".
Thought maybe I could do it through Astro, but same message.
How do I get around this? Especially sicne any of the tricks I found to do it are unavailable to me because of the very same problem.
Thanks!
Reply
I redownload the GAPP's file from the CM7 Wiki and then try reflashing it. I dont know what could've happened but I would try that first. As for the file explorer issue, I would download the Dropbox app on your NC and then on your computer, search for the Root Explorer/ES APK and upload it to Dropbox on your computer and then istall it on your Nook Color. Although, I am running Nightly 202 and the entire Market is working for me with no modifications or anything. I think the fact that one of the nightly's changed the DPI to 160, either way, I still have access to the entire Market without modifications.
Tapiozona said:
So I've come across a different problem. I'm trying to get netflix to work but the market tells me "Your device is not compatible with this item".
I looked around and I think I found a fix but I needed to install ES File Explorer..I went to download that and...
"Your device is not compatible with this item".
Thought maybe I could do it through Astro, but same message.
How do I get around this? Especially sicne any of the tricks I found to do it are unavailable to me because of the very same problem.
Thanks!
Click to expand...
Click to collapse
I had the same issue. What I did was upgrade to latest via ROM mgr pp WITHOUT checking 'load gapps' option which rebooted into latest CM7 nightly without gapps. Then rebooted into recovery, with gapps 0828 loaded on my sdcard, chose wipe cache option then loaded gapps. rebooted, had to reinit gapps but then it all worked.
Tapiozona said:
So I've come across a different problem. I'm trying to get netflix to work but the market tells me "Your device is not compatible with this item".
I looked around and I think I found a fix but I needed to install ES File Explorer..I went to download that and...
"Your device is not compatible with this item".
Thought maybe I could do it through Astro, but same message.
How do I get around this? Especially sicne any of the tricks I found to do it are unavailable to me because of the very same problem.
Thanks!
Click to expand...
Click to collapse
You never mentioned what version of CM7 you are running. If it is older than nightly 200, install a newer nightly.
Tapiozona said:
So I've come across a different problem. I'm trying to get netflix to work but the market tells me "Your device is not compatible with this item".
I looked around and I think I found a fix but I needed to install ES File Explorer..I went to download that and...
"Your device is not compatible with this item".
Thought maybe I could do it through Astro, but same message.
How do I get around this? Especially sicne any of the tricks I found to do it are unavailable to me because of the very same problem.
Thanks!
Click to expand...
Click to collapse
You need to download and flash a nightly above 200.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
A few folks have asked for a step-by-step, so I thought it might be helpful to have a copy here on XDA. GMPOWER has recently created a thread on his ManualNooter for NC 1.4.1 which should be considered the authoritative source on the basic rooting process. I'm going to leave this post here to collect other tips & tricks that can be done post-root.
I want to emphasize that I did none of the original work required for this effort to succeed. I only seem to follow instructions carefully, and know just enough to figure out what instructions to ignore. I'm posting this here because I'm hoping other will benefit from skipping a few of the painful steps I went through to get this working. All credit goes to GMPOWER, Dalingrin, Roustabout and the wonderful crew at XDA that create these tools to let us get more out of our devices!
TARGET AUDIENCE
This guide is for anybody wanting to root the stock Barnes and Noble 1.4.1 firmware. Is it worth it? Probably not. With all the options available today, reverting to B&N makes sense if, and only if, if you want to use any of the following B&N capabilities:
Read to me (mostly children's book)
Enhanced content (e.g. Conde Nast magazines such as Wired, New Yorker, though some of these are becoming available via 3rd party sources.)
Newpaper or magazine subscriptions (auto-update)
B&N Free in-store reading
Support from friends with stock Nooks or B&N (conditional upon being rooted)
The B&N reader experience and shell. The B&N Android Nook app is not the same thing as their firmware experience, at least not yet. Someday, they may update the B&N Nook Android app, but it is pretty poor right now. If you want to read B&N stuff, then 1.4.1 is a big deal.
If these apply, consider keeping your NC at B&N 1.4.1. If you want 3rd party content (e.g. Kindle), then root it, but make sure you've got it configured NOT to auto-update, since B&N has killed sideloading with OTA updates.
If you will not be using B&N content, then go with Cyanogenmod or similar. The B&N firmware suffers a lot of shortcomings compared to the "full tablet" experience:
Lots of settings are missing.
Getting a 3rd party keyboard to work is possible, but very kludgy at present. I had luck with SwiftKey by copying the apk from /data/app to /system/app as directed in NookColor Tools.
If you're looking to install CyanogenMod or other firmware, check out Koopakid08's A Noobs Guide to Getting Started with a Custom Rom on the Nook Color.
BACKGROUND
I started out reading and trying the procedure described the XDA thread on rooting 1.2 and 1.3:
[NC][1.2][1.3] ManualNooter 4.6.16 - xda-developers
However, it is critical to realize that the directions early on in that thread do not work for 1.4.1. The magic starts at about page 160. Below is my distillation of this information in easy-to-digest form (hopefully).
PROCESS
You need to create a ClockworkMod (CWM) bootable SD card to reset your device back to standard B&N firmware, and to install the "manualnooter" root kit. Colchiro has posted a nice summary over at Androidforums. His guide includes the latest (3.2.0.1) CWM versions.
Restore to stock B&N ROM. I'd been running CM7.1 on emmc, so had to go through the process of restoring to a stock B&N 1.3 ROM. Depending on the age of the article you read on how to do this, you may have problems either formatting /data or get into a boot loop at the 'n' logo. You need a current CWM to be able to successfully format /data. If /data is not properly formatted, you will get a bootloop at the B&N splash screen when you restart. Not a big deal to fix, but you can waste a lot of time on this. As of this writing, CWM 3.2.0.1 is the latest, and should allow you to format partitions without problems.
After restoring to B&N 1.3, I re-registered my device to make sure B&N functionality would work. After all, the only reason to bother with 1.4.1 is if you intend to use B&N content. Otherwise, save yourself the trouble. NOTE: We are not root yet.
Update to 1.4.1. I got my copy of 1.4.1 directly from B&N [EDIT 01162012: I have verified that the latest as of this date still works as described here.] Your Nook Color will also update to the latest if you just let 1.3 unrooted go to sleep if you don't have ClockWorkMod installed to eMMC. I have confirmed that this procedure works with the following nookcolor_1_4_1_update.zip md5sum: 2a27f54b65431a096af4f07967bcd6b5 (post-Christmas 2011)
Once 1.4.1 was running unrooted, I then followed GMPOWER's efforts over at XDA. The key is to run an updated version of manualnooter that does not make the database updates. As of this writing, his latest 5.01.24 can be found in post 1745. So far as I know, the official manualnooter repositories have not been updated.
Copy manualnooter-5.01.24.zip (or whatever the latest is) to your bootable SD recovery card.
Boot the recovery SD card.
Install manualnooter-5.01.21.zip.
Remove the recovery SD card and reboot your NC. It boots any card present, so this is kinda important. Behold the pretty startup screens. You should have root at this point.
Be sure to select Zeam as your initial launcher. Note that if you press the 'n' key at this point, you'll be taken back to the B&N interface, and not have ready access to anything non-standard. This is not a big deal. Simply press 'n'->Search and enter zeam in the search box. It should locate zeam. Select it to launch.
To enable 3rd party apps to load, you must open the NookColor Tools program. There's a magic check box that enables 3rd party apps at the top. By default, the text is white on white, so impossible to see. Select that box twice - to uncheck then recheck (toggle) it. When you are done, it should be checked.
To get 3rd party apps to show up in the Nook interface, download Nook Color App Manager from the Market. HINT: Don't go overboard and select everything. Select only those things you really want to see in the B&N Walled Garden. You might also want to select the HomeCatcher app (included in ManualNooter) to allow using the 'n' button to go to your launcher of choice, but I do not. My philosophy is to keep the B&N interface as much as possible, or I wouldn't have gone to all this effort. When I need "power user" functions, I just launch zeam using the search procedure listed above.
Disable OTA updates. B&N auto over-the-air (OTA) updates apparently break root, and lately, sideloading. There seems to be some debate about what works best for this, but I've gone for modifying the devicemanager.db using SQLite Editor to open devicemanager.db and change registry->com.bn.device.fota.mode from "auto" to "manual". You can use an alternate method with a free sqlite3 binary from the command line. So far, no nasty OTA surprises.
COMMON PROBLEMS
Here are some common problems and what to do about them:
Can't overclock. GMPOWER has indicated that an overclocked kernel is not provided as of manualnooter-5.1.24. You need to install Dalingrin's overclocked kernel for B&N 1.3 (NOTE: Dalingrin's hosting site for these files seems to be offline. Doncarauana has posted a set of temporary links to the kernel files you can try. You will also need a copy of Dalingrin's Nook Color Tweaks installed.
Can't format /data when restoring to stock firmware. You probably followed an old guide on how to do this. Depending on the age of your NC, the version of CWM you're using may not handle partition changes. You need to update CWM. See Step 1, above.
Bootloop at the 'n' logo when trying to restore B&N firmware.You probably goofed. Hard as it is to believe, it's very easy to miss the fact that /data wasn't formatted. This is the same problem as the preceding problem. Just follow Step 1, above, and be sure /data actually gets formatted.
1.4.1 is rooted, but unable to install anything from Android Market or Amazon App Store. When this happens, everything appears to be working, but after downloading, apps will fail to install. They key is to use GMPOWER's latest manualnooter and do not ever, even once, install one of the older versions. Refer to Steps 4 and 10, above. I had to restart from scratch to make up for not paying attention and running the old manualnooter versions. Something to do with a database patch that causes problems.
Facebook and other apps are missing from Android Market. UPDATE: This is fixed with GMPOWER's manualnooter-5.01.24.zip. (For other apps: A simple workaround is to install the app onto another Android device, then use Android Assistant to make a backup .apk and copy that to the Nook Color. If you only have a Nook Color Android device, you can create a bootable SD with CyanogenMod (see above) and install to that, then use this procedure to copy the .apk over.)
UPDATES
2/14/2012: Updated to add link to manual procedure for blocking OTA updates using sqlite3.
2/13/2012: Updated to include link to GMPOWER's thread on his ManualNooter for NC 1.4.1.
2/6/2012: Updated links for Dalingrin's overclocked kernel to include Doncarauna's temporary links.
1/24/2012: Updated to reference GMPOWER's manualnooter-5.01.24, restored references to Dalingrin's OC'ed 1.3 kernel.
1/22/2012: Updated to reference GMPOWER's manualnooter-5.01.21, remove references to APPS2SD not working. It's working now! Removed overclock kernel as a concern. GMPOWER's latest MN includes it. Added link to Colchiro's SD HOWTO at Androidforums.
1/16/2012: Updated description of 1.4.1 update now that I've verified this procedure works with the latest, and added link to SQlite OTA blocking procedure.
1/11/2012: Updated link to GMPOWER's ManualNooter update to be more concise.
Thanks, This really helped me to get my nook rooted.
So running CM7.1 off a sd card is another way in a good way or is there a better way to root a NC. The reason I ask is because I am running of a SD and it stalls on me when i go to turn it off and back on. Is there something I need still to download.
ciscom25 said:
So running CM7.1 off a sd card is another way in a good way or is there a better way to root a NC. The reason I ask is because I am running of a SD and it stalls on me when i go to turn it off and back on. Is there something I need still to download.
Click to expand...
Click to collapse
Sounds like your CM install is screwed up. It should have no problems powering on and off. However, if you don't care about the B&N stuff, you'll be better off installing CM to internal (eMMC) storage so you're not dependent on the SD card and can use it freely.
This guide is only about rooting the stock firmware if you decide you do want the B&N stuff. Koopkakid08 has a great summary on alternate firmware strategies.
Your link for the MN 5.x.x post needs to point here: http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Taosaur said:
Your link for the MN 5.x.x post needs to point here: http://forum.xda-developers.com/showpost.php?p=20456719&postcount=1631
Click to expand...
Click to collapse
I'll update to include the single post you pointed to, and move the full-thread discussion to a separate APPS2SD issue at the bottom. I think that will make the step-by-step clearer, while still pointing to the ongoing efforts GMPOWER is working on.
I urge anybody rooting 1.4.1 to track the ongoing discussion and GMPOWER's updates.
Thanks!
Bumpity bump
Do these instructions assume you have CWM already installed? Sorry I got lost at "Copy manualnooter-5.12.XX.zip, or whatever the latest is, to your bootable SD recovery card." because I have no idea what you mean by "bootable SD recovery card". Do I need to create this?
Followed directions
Am rooted but none of the nook tools apps are present when launching zeam
Neither are Gapps.
Must they be flashed separately or were they supposed to bepart of the flashing procedure for manual nooter
Looking at manualnooter-5.12.20, you should have an older version of the Android Market app, gmail, calendar, contacts, maps, homecatcher, rom manager, superuser, talk, YouTube and SoftKeys. What are you missing?
wasnt said:
Do these instructions assume you have CWM already installed? Sorry I got lost at "Copy manualnooter-5.12.XX.zip, or whatever the latest is, to your bootable SD recovery card." because I have no idea what you mean by "bootable SD recovery card". Do I need to create this?
Click to expand...
Click to collapse
the bootable SD recovery card is where you install the CWM. creating this recovery card is the first step you to root the nookcolor. Not only you need it to install the manualnooter (MN), it also allows you to reset to stock setting and other good stuffs.
Good catch, guys. I've inserted a new step 1 which points to a guide for creating a bootable CWM card. Thanks for pointing out that omission.
"Updated to reference GMPOWER's manualnooter-5.01.21, remove references to APPS2SD not working. It's working now! Removed overclock kernel as a concern. GMPOWER's latest MN includes it."
Thanks for this thread.
Does this mean you are able to use Nook Color Tweaks to overclock? I upgraded to MN 5.0.1.21 but I still get an error message in Nook Color Tweaks
" Kernel is not compatible with Audio settings. A newer build of CM7 or Dalingrin's overclock kernel is required"
Also, any idea where I can obtain the kernel other than somehow pulling it from a CM7 build?
Thanks,
Ken
Help! I really messed up this time.
I followed the instructions to install 1.3.0 but did not update to 1.4.1 and then I completed the root. I see the Android Market and can actually buy an app. However, installation hangs at "authorizing" because, according to Android Market support, the Nook is not authorized to load apps from the Android Market. So, clearly something is wrong. Either nobody can run those apps, which I doubt, or I messed up.
To compound the problem, I default to Zeam Launcher and cannot boot into B & N. I have also tried to force a reset by 8 failed starts but that did not work. This Noob could really use some help to fix the problem.
chengka said:
"Updated to reference GMPOWER's manualnooter-5.01.21, remove references to APPS2SD not working. It's working now! Removed overclock kernel as a concern. GMPOWER's latest MN includes it."
Thanks for this thread.
Does this mean you are able to use Nook Color Tweaks to overclock? I upgraded to MN 5.0.1.21 but I still get an error message in Nook Color Tweaks
" Kernel is not compatible with Audio settings. A newer build of CM7 or Dalingrin's overclock kernel is required"
Also, any idea where I can obtain the kernel other than somehow pulling it from a CM7 build?
Thanks,
Ken
Click to expand...
Click to collapse
A kernel was not included in any of the MN releases for 1.4.1, you will need to download the Dalingrin kernel to use Nook Color Tweaks, LINK
rkulp said:
I followed the instructions to install 1.3.0 but did not update to 1.4.1 and then I completed the root. I see the Android Market and can actually buy an app. However, installation hangs at "authorizing" because, according to Android Market support, the Nook is not authorized to load apps from the Android Market. So, clearly something is wrong. Either nobody can run those apps, which I doubt, or I messed up.
To compound the problem, I default to Zeam Launcher and cannot boot into B & N. I have also tried to force a reset by 8 failed starts but that did not work. This Noob could really use some help to fix the problem.
Click to expand...
Click to collapse
The direction were for firmware 1.4.1, since you have firmware 1.3 you can update to 1.4.1, or follow these directions, LINK
Thanks! I have CM7 on way too many devices, tee hee, so I wanted to go back to stock on the reader to compare battery life.
Download Dalingrin's OC Kernel
Thanks for the guide! Working great but I can't seem to find a functioning download link for Dalingrin's kernel. Anyone have one?
I found Dalingrin's kernel here:
http://forum.xda-developers.com/showthread.php?t=925451
Some folks are having problems with some of the links, though.
Great guide, I tried CM7 on the SD Card, but I just found that I like the plain look of the B&N interface. Using your guide as a template I nootered my Nook, and will be doing my wife's later. I am also looking for Dalingrin's OC Kernel, I have had it from previous nooters, but my hard drive crashed, and I had erased all of my microsd cards, because I had all the files on my hard drive . So if anyone has a working link, or could send me the file I would greatly appreciate it.
Thanks, RDRANGER
Downloading binaries of any sort from an unknown source makes me queasy, but if you're feeling daring, there's a post in the Dalingrin 1.3 kernel thread to a copy. Use at your own risk, etc.
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Version 7.3.0 is out. Here are the specs from the Amazon page:
"Support for X-Ray for Textbooks
Explore the “bones” of your textbook, and access all the most important terms and concepts, with glossary definitions and links to relevant textbook pages.
Simplified Chinese Support
In addition to the other languages offered, you can now change your device language to Simplified Chinese.
Track your reading progress with Time To Read
Kindle Fire HD 7” calculates your reading speed to let you know when you’ll finish a chapter or book.
Support for Kindle Editions with Audio/Video
You can now read books that contain audio and/or video clips.
Print Replica Textbook Enhancements
Scroll through thumbnails at the bottom of the screen to preview pages and jump quickly between chapters, and mark important notes and highlights in your Notebook for easy reference."
None of this seems overly important, but then again I do like to have the latest version as long as there is no harm to the root.
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Anything you install as a system apk will be deleted. When amazon sends an update it typically sends system.img, recovery.img and boot.img.
That is why the lmt launcher will not work because it has to be installed as a system.apk to work, same with root access since su binary is placed within the system files.
if you want to install the 2nd bootloader, you should not update. Amazon have fixed the bootloade with the update and so it dosn't work for now. i don't know, if it perhaps work with soupkit, because the insallation is a little bit different, but the resultat is the same (I could install kinelogy 1.1 after doing that).
I'm still on 7.2.1, found Wi-Fi performance/range considerably better than on 7.2.3, unless 7.3.0 improves it I won't be updating for quite some time.
This explains why I lost root and Go Launcher HD yesterday. Regained root with the same Noob Simple guide here with little more than annoyance. The file to prevent the OTA update had been moved per the guide (otacerts.zip) but think I deleted it in a cache cleaning frenzy... that will learn me
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
EDIT: OK, I was able to re-root the same way I did before (used the tools in prokennexusa noob threads!) All back to normal!
markbc01 said:
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
Click to expand...
Click to collapse
Same root method worked, system feels about the same with tweaks installed and benchmarked similarly (7344 vs 7444 with AnTuTu)
I just can't get my launcher off of the stock one. Nothing will take.
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
macbranson said:
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
Click to expand...
Click to collapse
Which method did you use to root again ?
Nop update here istill in 7.2.3
Damn just got the damn update like 5 min go
Sent from my Nexus 7 using Tapatalk 2
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
geeibara said:
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
Click to expand...
Click to collapse
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
quan_1986 said:
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
Click to expand...
Click to collapse
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
geeibara said:
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
Click to expand...
Click to collapse
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
#3Clara said:
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
Click to expand...
Click to collapse
haha yah I noticed that too, I had files like appappappappappappapplauncher lol. Thanks this helped a lot
modmyphone said:
I just can't get my launcher off of the stock one. Nothing will take.
Click to expand...
Click to collapse
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Gah.. I actually tried to deactivating the manual update and some how the update still pushed through.. which really sucks cause I hard my set up perfect..hope all I have to do is reroot.. ..all that time spend for nothing
Sent from my KFTT using xda app-developers app
BmanCV-60 said:
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Click to expand...
Click to collapse
Actually, I tried 3 different ways.
1) I reluctantly attempted ProKennexusa's method via the KFFFirstAide tool. I say reluctantly since I'm pretty much a Nova snob. I guess luckily for me, it wouldn't take.
2) I then moved onto downloading Nova from the store. The store claimed that both installs went good, but had no option to change my launcher. Upon inspection, the Nova launcher file was nowhere to be found on the device. The pro unlocker could be found, but no the launcher.
3) Since I had a couple of older copies in Dropbox, I figured I'd try those. Usually I could install straight from Dropbox. Not last night. I could launch the install, but the Kindle wouldn't allow me to press the install button. I then just saved the file to the device and still couldn't get it to install. It wasn't until moving it to system/app that I was able to actually install it. But still, no option to set it as my launcher.
This morning, in a bit of Kindle rage, I literally rebooted the device 23 straight times pausing between boots to see what happened. On the 23rd reboot, it finally asked me which launcher to set as default. So now I finally have gotten away from the freakish kindle launcher and am back at home with Nova.