Related
After a bit of stupidity, I installed the G2 Launcher2.apk on to my phone. This has apparently halted the second stage of the FRG83D update, which my phone has relentlessly attempted to install for over a week now.
I'm getting an apply_patch_check error and it appears to be failing on the hash check of Launcher2.apk.
So I rolled back to what I thought was my backup of Launcher2.apk. This went poorly. My phone wouldn't boot at all. Had to ADB and push a separate Launcher2.apk I found online.
Now I'm at an impasse. The version I now have is 5 screens, clearly an N1 Froyo L2, but it's also throwing the apply_patch_check error.
Is anyone able to provide me with a link to the FRG83 Launcher2.apk? I downloaded the signed-passion-img-FRG83_0923.zip file from HTC which I think should have it buried in the .img file, but I'm unclear how to unpack and push a file from there to my phone...
Alternatively, was Launcher2.apk updated for FRG83D? If not, I could just pull the L2 from my friend's N1 and use that... but I'm guessing it'll be more of the same checksum fun.
Finally, is there any way to tell it to ignore the patch check? Or is that impossible?
Many thanks in advance!
See attachment for FRG83 Launcher2.
If it still fails, you could try flashing the update using a custom recovery with signature checking turned off (ie. Amon_RA 2.0 or ClockworkMod)?
Sweet jesus, thank you. Finally was able to push the Launcher2 apk and odex and successfully upgraded to D. Thanks so much!
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
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.)?
Hi,
I just made my SGS boot looping by editing some settings in /data/data/com.android.providers.settings/databases/settings.db. CyanogenMod came back with FC loop of the Phone app so I deleted 2 entries from the db. Before that I (thought I) made a backup of the settings.db. After the Phone's FC was gone I replaced the edited settings.db file and rebooted (since I did not like the changes to Status Bar Widget Buttons). Now I am stuck in a boot loop. Reflashing the rom does not help.
Does anyone have a hint on this? I am trying to avoid wiping as long as I can.
Thanks a million.
Now this is a little embarassing. I just renamed the settings.db to settings.db.bak while it was boot looping. The file was immediatly recreated and the phone booted without a glitch.
I'm having the same problem. How did you get yours resolved?
Edit: I see the red writing now. I wonder how you edited the file while it was in the boot loop. Using adb maybe?
Edit #2: Using shell commands. Now I got it. Lots of google searching.
All,
I have an HD+ running 2.0.5 and its rooted. When I've turned on wifi, half the time it tries to update to 2.0.6. It always goes through its process then dies at 99% and drops back telling me that something is wrong. The first time I freaked out and thought something really WAS wrong.
Boy was I relieved to see that I still had my stock root.
I was just thinking that maybe I should update to 2.0.6 just to keep it current. I use the Nook side for reading and stuff as it is. Can I just rerun the root process like I did for 2.0.5?
Also what is the best way to make it not fail the update?
I did the white-on-white fix, but changed it back.
Please don't tell me I need to do the 8 boot factory reset.
Thanks,
-Jeff
How did you change back the white on white? I suspect that is what is wrong.
Sent from my Nook HD+ running CM10 on Hybrid SD
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
js5752 said:
Since the fix made a backup of the original file, I just renamed the original back to it's proper name.
I moved the orig to a new temp name. Then I copied the active "fixed" one to a something.bak or something like that.
Then I renamed the original one (with the temp name) back to the original/active name.
Upon renaming it crashed, and rebooted. The w-o-w fix was gone.
BTW, looking back at that description it's a bit messy. If it doesn't make sense I'll just put the commands down (as I recall them)
-Jeff
Click to expand...
Click to collapse
No, I understand what you did. You left the symlink in /system and just manipulated the files in /data. That works to get rid of white on white, but does not put framework-res.apk back in /system. And the update zip needs framework-res.apk there. That is why it was failing.
Did you do a back up of your system before you added white on white like I recommended? If so, restore that and then update. If you did not, you can try putting that original framework-res.apk back in /system/etc via ADB. Doing it with ADB prevents that crashing you experienced the first time.
As a last resort go back to 2.0.0 with my plain stock zip in my HD/HD+ CWM thread. You can flash that and it will not erase your media files. You should backup your system with CWM first. Then wipe /data, then flash the zip. Then sign on, register and it will update you to 2.0.6. Then go to CWM and do an advanced restore of /data. Then flash again the zips you want, like root or gapps. Then you should be ok.
Edit: If you want to keep 2.0.5 and not be bothered by those attempts to update, I just added to both my Tips thread and my CWM thread linked in my signature a method to stop those updates.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thanks for the reply.
I expected the crash from what I had read. I just decided that ADB was more hassle than it was worth for a quick change. That and I like to live dangerously
Ok, the symlink vs the data file makes sense. Now I understand why it wasn't working. Thank you, because I thought all was back where it should be.
As for backups, I did one before rooting, and I've done a couple since just to make sure I've got backups. That plus titanium, I figured I should be able to recover if the worst happens.
Thanks for the tips, and for all the work you've done on rooting these devices. It was the option to root that tipped me over the edge to buy one, and I'm glad I did.
-Jeff