Related
I created a new thread for this because the old one was for development, and there's no more development
I finally decoded all the information GPS is providing, and updated the drivers to provide full GPS support.
Rootfs link below for those running from SD or NAND
This thread is for people who want the latest and greatest! As ROM builders integrate these libraries into their ROMs, you shouldn't have to come back here. GPS 5.0 is likely to stay, as I don't foresee any bugs.
Check out the old thread as well. Shidell put some work into an ADB how-to:
http://forum.xda-developers.com/showthread.php?t=616436
Rootfs with libgps5.0already pushed in (fixed some file permissions in this version and verified libgps is in there):
http://dl.dropbox.com/u/58383/rootfs-libgps5.0.zip
NBH (thanks jamezelle!):
http://5d698f86.linkbucks.com/
zImage and libgps.so attached! Rootfs above!
INSTRUCTIONS (SD): Replace your zImage and rootfs.img with the ones provided and reboot! (Put them in the android directory).
INSTRUCTIONS (NAND): Flash the new NBH. Then either flash the new rootfs.img, or adb push the library to your /lib/donut, /lib/eclair, and /lib directories.
Bugs remaining (I don't feel like hunting them down):
* Satellite reporting is finicky (this is an issue with the gps messages themselves). Satellites disappear and come back randomly. Only way to fix this is put in a state machine that combines satellite messages over multiple seconds. Also you'd need to prune satellites that are old. I implemented one, but had crashing issues so I ditched it.
* [Fixed] After booting, the first time you try to use GPS with Google Maps/Nav, it will fail. Exit out and re-enter and it will always work from then onward.
Changes:
-2.2: Fixed 'no position in maps/nav on first try after reboot'
-5.0: Fixed issue with negative altitudes, also rebaselined versioning to match versioning inside the software
For maximum compatibility, make sure you're running a 3.42.50 radio (CDMA):
http://forum.ppcgeeks.com/showpost.php?p=389964&postcount=8
Radio-only nbh that won't mess up your NAND.
Most newer NoMoRootfs (andboot) builds should already have this cooked in!
Kaiser zImage:
http://dl.dropbox.com/u/58383/kaiser_zImage.zip
(also any of dzo's newer zImages work)
i was using the previous zimage from 1/23/10 with rootfs 1/26/10 through sd card ext2. worked great. before that, I used the 1.4 version (the one before 1.5) without any problem (pushing the libgps.so).
however, with the 2.1 zimage and rootfs, the sattelite does not appear at all, after entering and exiting maps/gpstest numerous times and rebooting. any clue? going to try a few things (maybe will try pushing the libgps instead, or the old zimage) to see if I can sort it out.
You can try this one that uses a constant accuracy like the old ones to see if that fixes it. You'll have to push it.
The new lib uses 64-bit location values, which are much more accurate than the other things (this isn't causing your issue). The new one also uses different accuracy reporting, which android may not like.
Others: The above files definitely work, please don't use the attached.
Edit: Looks like I wasn't actually pushing libgps.so into rootfs! Don't use the below, it fakes the accuracy.
[Removed file]
I may have figured out what's causing the "no position lock on first try after reboot" problem. I put a fix together, it worked, but crashed the phone. I'll debug it later.
Tatnai's problem may be related. I'm assuming AGPS isn't working on his phone and that's causing the issue.
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
JacenSolo2001 said:
So with the new zImage, just drop that, along with your rootfs into the android folder, and that's it, right?
Click to expand...
Click to collapse
Yup, just put it in the android directory.
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
JacenSolo2001 said:
ok, done, and if GPSTest just sits there and never even gets 1 bar, is there an obvious reason or something that's messed up?
Click to expand...
Click to collapse
Whoops, I think my script was never actually pushing libgps to rootfs. I just looked and the timestamp is old. It may have been storing it in data.img. This means you're probably actually using the old libgps + new kernel = does not work.
I'm removing it for now. Either:
1) Go back to an old zImage/rootfs (I'll post a new one later)
2) Push it into android using shiddell's instructions: http://forum.xda-developers.com/showthread.php?t=616436
I'd appricate it if you'd do #2, so I can get testers to work out bugs (there shouldn't be any). However, I'll be putting out a libgps-2.2 later that fixes the "failed first lock on fresh reboot" bug, so I understand if you'll want until then for a new rootfs.
I may try the push tonight when i get in from work.
LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot
Thanks again for all you're doing !
JacenSolo2001 said:
I may try the push tonight when i get in from work.
LOL, i had thought this was fairly "idiot proof", as you intended, so i was feeling like an idiot
Thanks again for all you're doing !
Click to expand...
Click to collapse
If you have ASTRO in your app tray, can you go to /lib and click-hold the libgps file. Hit details. What timestamp is it?
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
JacenSolo2001 said:
I don't have a /lib folder, i do have the file in my root directory for android, i just placed it there earlier when I got the zip file. The date for that is Jan 24
Click to expand...
Click to collapse
I'm talking about when android is booted (not /lib on the sdcard). It mounts the rootfs.img as a file system.
If you don't have a /lib directory, then it has to go in /system/lib
LD_LIBRARY_PATH usually only looks in /lib, then /system/lib
So it's possible I was pushing it into rootfs.img properly, and the modified timestamps aren't being updated.
Jan 26 2010
JacenSolo2001 said:
Jan 26 2010
Click to expand...
Click to collapse
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.
Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.
I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
jnadke said:
Did you download the rootfs.img, or just put the libgps.so in the /sdcard/android directory.
Jan 26 is yesterday's update (libgps-1.6). Today's should be Jan 27th.
I'll include clearer directions when I push out a new libgps one last time that includes the latest bugfixes.
Click to expand...
Click to collapse
im going to make nbh's for the NAND flashers which files should i use
EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
jamezelle said:
im going to make nbh's for the NAND flashers which files should i use
EDIT NVM seen your remark in post 3, im going to make nbh files with 2.1 zImage
Click to expand...
Click to collapse
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.
The zImage-2.1 should be final.
I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.
Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported. I did come out with a zImage-2.2 that checks if accuracy isn't 0 before sending a message to libgps, but this triggered random reboots (looks like it doesn't like this). Right now it just checks if a gpstime is being reported (which isn't right because it should report that even if no position lock is present).
I'm not sure what the proper method for Android GPS is to gracefully indicate GPS is lost, but the libgps-2.2 version on my phone seems to work with zImage-2.1.
jnadke said:
Thanks. This saves me from resizing my VMWare image to install Wine + LinuxPPCKitchen.
The zImage-2.1 should be final.
I'll be coming out with a libgps-2.2 which fixes the 'maps/nav no GPS first try after reboot' issue.
Apparently you need to set the HAS_ACCURACY flag all the time. I was trying to not set it if accuracy was 0.0. Apparently the flag not being there causes Maps/Nav to crash if position is reported.
Click to expand...
Click to collapse
here you go ppl use the rootfs in the first post!!! this contains all 3 resolutions for vogue only right now
NAND NBH FILES 2.1 "240 428 and 480"
btw jnadke im not getting a lock with this in 2.1(2.1 eclair btw) not sure if it is compatible
EDIT: pulled up maps and it rebooted phone ill try again
EDIT2: 10 min not one sat, so i backed out fof GPS Test and it rebooted phone
EDIT3: ok so im an idiot and didnt use your rootfs and pushed the lib to /lib and my init points to /system/lib lol so i fixed it all is well it works just fine
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
dmulligan said:
So does the rootfs.img file still need to be matched to the NBH file in some way? Is rootfs.img where the /lib directory is?
Click to expand...
Click to collapse
use the rootfs in the first post and the nbh's in my post on this page
i can confirm a lock
jamezelle said:
use the rootfs in the first post and the nbh's in my post on this page
i can confirm a lock
Click to expand...
Click to collapse
jnadke removed that file this morning.
For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you
Yes this method definitely works. I have market working now and can search for protected apps etc.
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.
I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/
Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.
LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.
Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?
Yes, it requires an edit to a file that you can only be edited when rooted
elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!
OP has been updated with original build.prop
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.
Thanks for the reply.
I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper
Very cool mod. I will try this out when I have the time!
thank you
Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?
Hey could you make me one and either PM me or post it up?
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Did not work on Modaco R9, CM7 or The Cracker builds...
nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.
I have all the files in the proper folders but it still doesn't work. Modaco R9
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.
Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t
Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks
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
I'm aware this is better suited in the android development section, however I can't post there yet.
So I'm in an area where I can only get data with data roaming turned on. Liberty lacks the option to turn it on, and that was a killer for me. So I figured out how to turn it on!
First, you'll need a program called notepad++. Google it, its free.
You'll now need liberty rom. You should know where to get it.
Once its downloaded, open the rom. I used winrar, no need to extract the zip with it. Open the system folder and you'll find the build.prop. Open it with your newly installed notepad++. Once open, add. "ro.com.android.dataroaming=true" to the build prop. I added it to the bottom but I believe it doesn't matter where you add it. Click save and your done! Just flash it like normal and enjoy that sweet, sweet data.
I tried this and I still get the "Data Connectivity Lost - Data Roaming is turned off" notification.
Any thoughts?
Did you use NotePad++? And did you wipe data? Tell me the exact process you used.
danielkuhlman said:
Did you use NotePad++? And did you wipe data? Tell me the exact process you used.
Click to expand...
Click to collapse
Wiping data made the difference!
I figured coming from the same ROM I wouldn't have to worry about that, but apparently you do. I guess I'm still a bit confused on how exactly the build.prop file is used by the OS.
Thanks for the help!!!
i know people have said they couldnt edit build.prop in liberty, but i was able to edit it with root explorer, save it, reboot and it took effect. i didnt make the changes youre describing but i changed the build name
I tried editing build.prop and rebooting without success.
I copied build.prop to my SD card.
Edited the file with Notepad++ (obviously from my computer)
renamed build.prop in the System folder to build.prop.bak
copied build.prop from my SD card to the System directory
reset build.prop permissions
rebooted
The data roaming setting never took affect when I tried this. I have no idea what I did wrong.
blkwlf said:
I tried editing build.prop and rebooting without success.
I copied build.prop to my SD card.
Edited the file with Notepad++ (obviously from my computer)
renamed build.prop in the System folder to build.prop.bak
copied build.prop from my SD card to the System directory
reset build.prop permissions
rebooted
The data roaming setting never took affect when I tried this. I have no idea what I did wrong.
Click to expand...
Click to collapse
I was running monster rom, I downloaded liberty and changed the build.prop as described and worked like a charm. Possibly, since you tried changing the build.prop without wiping data and dataroaming was already disabled, it saved it like that. Much like when you enable usb debugging. If you flash a rom with it enabled without wiping, it stays enabled...
Hmmmm... you'd think changing the build prop would automatically change any stored settings. I'll look into this
danielkuhlman said:
Hmmmm... you'd think changing the build prop would automatically change any stored settings. I'll look into this
Click to expand...
Click to collapse
Exactly! I still think I must have been doing something wrong... probably messed up one of the mundane details. I always do that
I'll try recreating the steps you went through when I've a bit more time and a fully charged phone. Maybe I can learn something else useful
is this for the CDMA radio? i need to verify GSM with Liberty 2.0
I'm not sure, there's no gsm service around here (hardly cdma). You can try and see if it works.
Sent from my DROID3 using XDA App