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, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.
Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.
Required Apps:
- Root Explorer (in market)
- SQLite Editor (in market)
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. Hope this helps!
RootNewbie said:
First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development...
Click to expand...
Click to collapse
Really? Or push a modified build.prop, done... *shrug*
Thats actually a good find because for a minute we were all sweating losing root over the 1.1.0 update.
khaytsus said:
Really? Or push a modified build.prop, done... *shrug*
Click to expand...
Click to collapse
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
RootNewbie said:
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
Click to expand...
Click to collapse
Nobody I'm aware of, including my two NC's. Perhaps you're confusing updating the build.prop with renaming the otacerts file?
http://forum.xda-developers.com/showthread.php?t=930382
RootNewbie said:
First, I'm sorry if this is posted somewhere already. I spent numerous hours trying to block OTA updates following a post under Android Development... Link to post.
Having played with adb for hours and not being able to get sqlite working in cmd. I tried browsing to the file the script in the above post appeared to be editing with Root Explorer. To my surprise, when you click on the devicemanager.db file, Root Explorer gives you an option to buy SQLite Editor. Which I did.
Required Apps:
- Root Explorer (in market)
- SQLite Editor (in market)
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Assuming this is what the scripts are doing, your nook color should now be blocking BN OTA updates. The best part is that you can do all of this from your nook color. Hope this helps!
Click to expand...
Click to collapse
Thanks for posting this. I'm sure it will help someone out. It would have been me a week or two ago. I was trying to figure out how to change this value to avoid the OTA and really didnt understand ADB, SDK, Sqlite or any of that then. when i first opened Root explorer i remember it asking me if i would like to purchase it and i declined, now if i only would have known how easy it could have been.
RootNewbie said:
Correct me if I'm wrong. I'm still a beginner. I thought I read threads where people were still getting the OTA update after editing/replacing the build.prop ... Plus, what happens when BN decides to release a new update? You would then have to change the build.prop again? Editing the registry value should prevent the device from ever checking for new updates. Seems like a cleaner fix to me.
Click to expand...
Click to collapse
I agree. Changing the setting in devicemanager.db is A LOT cleaner than the build.prop fix.
I just use a task killer and kill the B&N stuff... No updates here..
redking79 said:
I agree. Changing the setting in devicemanager.db is A LOT cleaner than the build.prop fix.
Click to expand...
Click to collapse
Considering this is how all Android OTAs are determined.... eh, whatever floats your boat
Slightly off-topic: I made this change (in devicemanager.db) to disable B&N updates. Whilst in the database, I noticed a table called Tasks that has 5 entries with types 100, 101, 102, 3, 2. The types 100 & 2 are tagged as enabled, the others are disabled. They have a date_next_run column. I imagine this is some kind of scheduling. I haven't worked out the date format. Does anyone know what these tasks will do - I would imagine one of them forces a B&N update?
RootNewbie said:
Process:
1. Open Root Explorer
2. Open devicemanager.db from (/data/data/com.bn.devicemanager/databases/devicemanager.db)
3. Select "registry" - this should open up a spreadsheet looking file
4. Find row: com.bn.device.fota.mode
5. Drag over to the column labeled "value"
6. Press and hold "auto" until the "Actions" window pops up
7. Select "Edit Field"
8. Replace auto with manual
9. Select "Save"
Click to expand...
Click to collapse
Thank you for this- It's nice to find a nice, easy, self-contained way to ensure my NC will stay the way I have set it up 'til I decide otherwise.
One question though- to make it stick shouldn't there be one more step-
10. Reboot?
Block OTA updates
Xboxexpert has posted a bat file for download in a zip file Block updates.zip. Has anyone used this?
I need instructions regarding running the bat file.
Do I load the contents of the zip file on my SD card or do I open a command prompt box?
What do I do to run this bat file?
Thank you.
I can't get the "actions" window to pop up.
Wow this is an awesome find. Can anyone verify that this did indeed work for them? I have my rooted NC running 1.1 smoothly with all apps running perfectly. My final task is to stop OTA's from triggering. I don't feel confident doing this via ADB but using this method on the NC seems easy. Does this sound the same thing as the bat file does from the other thread? Thank you all for your amazing help!
Followed the process listed here... so far so good, no resets.
I have been through this 4 times so far and have been unable to get it to stick. I have backed up the rom after installing sqllite and root explorer, modded the registry, rebooted and still getting the damn OTA. Anyone else having this issue or has figured out if there is another entry that needs to be edited to defeat this?
Nm, I edited the url that the fota uses to check for updates so it is "dead"
backedup the rom again and have yet to see fota from BN. *fingers crossed as this is annoying*
****NM this didnt work either****
http://forum.xda-developers.com/showthread.php?t=930382
Thanks khaytsus! I do believe that has done the trick. I went ahead and edited the build.prop versus pushing it but we will see how it fairs now that i have hit wifi back on
Does this method still works to prevent 1.2 ota update? it surely looks the easiest method of all.
Yes or no?
I cannot get my new Nook Color which is at 1.0.0 to update to BN's 1.1.0 (I tried all the suggestions in the threads I read), so I thought that perhaps it might work better to try 1.0.1 and then 1.1.0 (admittedly grasping at straws).
Is there currently a link to 1.0.1 anywhere (for sideloading)?
EDIT - Found it ! For those in the future looking for it, nookdevs.com has a link to it on the BN site,
Were you able to upgrade to 1.1.0?
I ask because I am unable to go from 1.0.1 to 1.1.0. I have tried side loading the file downloaded from BN, I have tried deregistering the device, I have tried boot interrupt x 8, I have tried power-n, I have tried reloading boot.img and system.img via a honeycomb sdcard. The same thing happens every time. The file downloads to the proper place on the nook's drive, I disconnect it from the computer (I have tried a mac and a win7 pc), it goes to sleep and nothing happens. I go to look for the update file in the main folder on the nook and it disappears. If I go to look for it before it sleeps, it is there. If I tap on refresh - it disappears. I have called BN 3 times - they are stumped.
Any ideas? I may repost this to its own thread...
Try downloading 1.1.0 again.
Some time on Thursday, they replaced the corrupted file on the B&N site with a good one. The good one has the following MD5:
Sideload_update.zip
md5: 2F533C63FCFDB4F655C684BD9A95A298
EDIT: SOLUTION FOUND!!! HERE (see also the P.S.: Disabling Fast Dormancy on v20s stock)! and file download HERE (Keep in mind this file was for v10E Europe Open)!
After I made the upgrade on the new 10E European Open, the browser keeps getting it's homepage to live.vodafone.com, and a bunch of vodafone bookmarks keep appearing after every phone reset.
I managed to delete them with "Bookmarks Manager", but they keep appearing on reboot, what's worse, they don't work, the pages are not loading and is driving me crazy.
I tried deleting browser.db, setting read only flag to 0 in browser.db for the selected bookmarks with sqlite editor and then deleting, everything, I just can't get rid of these bookmarks once and for all!
Please help!
Maybe if I do some wipe data on some system APP will solve the problem (with Titanium Backup), but wiping the data for the browser doesn't do the trick (only temporary fix)
P.S. Bookmarks Manager was a very good solution for Orange Bookmarks on older firmware, but these VODAFONE ones are very persistent! I tryed an ORANGE sim and the same situation happens but with Orange Bookmarks, once phone reboots, the damn bookmarks get resurrected!
I think these bookmarks are stored somewhere in a file and once phone reboots are read and automatically created... It's very annoying because even my homepage gets changed everytime phone reboots...
Some more info:
I don't want to let this die, here is my experience:
Before I used 10B Orange Romania, and once the bookmarks were deleted, they dissapeared forefer, but maybe because that firmware is (was) intended only for orange phones, so, in truth the phone didn't needed to "PUSH" new bookmarks on reboot.
This only happens with 10E European - OPEN, because, probably being a OPEN firmware it's actually supposed to support all carriers, so maybe the phone scans the sim for carrier name and automatically PUSHES the HOMEPAGE and BOOKMARKS...
I'm in the process of testing this theory with NO SIM, it should NOT push any bookmarks in this case... And what do you know... I'm right, with no SIM, there are no bookmarks loaded! Insert a phone sim and that carriers bookmarks get pushed on the phone! Even the homepage stays untouched!
Could we use this info to trace the program that does this??? if yes HOW?
Try bookmarkymark (free in Market), it got rid of my preinstalled bookmarks, too.
HTH!
I can delete them, the problem is how to make them stay deleted... They come back on every reboot!
Same problem with my P970 on a Red Bull Mobile contract.
NEW INFO and SOLUTION!!!
quyTam said:
@valakinaki & @mihaiolimpiu
and all those who have problem with operator bookmark.
I've got the same problem with a previous rom version, LG black loads operator bookmark from sim card ! è.é
finally (after trying frezing all services), I've found the service who cause that !!
"FlexProvider"
After freezing this service, the problem is solved (but freezing this service crash the default SMS app, so I have to use Handcent)
Click to expand...
Click to collapse
Ok, so I found this service resides in:
/data/data/com.lge.providers.flex/
/lib/ dir is empty
/databases/ has two files:
error_report.txt and flex.db !!!Every info for this is stored in that file and by editing this file we might find the answer!!
EDIT:
Yes, indeed the database has all the bookmarks and nasty homepage stored, the problem is that every modification to the file brings flexproviders service to FORCE CLOSE...
PROBLEM FIXED!!! JUST SET read/write for Owner/Group/ALL after you copy the file over!
You will need to have ROOT access to copy the file!
I used http://sqliteman.com/ to edit the file, the info needed is in the table flexinfo:
BRW_SETTINGDB_HOME_URL_I: browser homepage <-SET TO WHATEVER YOU WANT!
BRW_SETTINGDB_CURRENT_HOME_URL_I: current browser homepage <-SET TO WHATEVER YOU WANT!
BOOKMARKDB_CNT: how many bookmarks are loaded from database <-SET TO 0!!! YAY!!!!
BOOKMARKDB_NAME_1_I: name of bookmark <-just ignore if BOOKMARKDB_CNT is set to 0
BOOKMARKDB_URL_1_I: url of bookmark <-just ignore if BOOKMARKDB_CNT is set to 0
FIRST you have to go to the table flexoperator, and find your operator index - OPERATORKEY, for example ORANGE RO is 115!
Then go to flexinfo to operator index you want and find above fields and modify accordingly!
THANKS quyTam for the hint... I couldn't do it without the info you provided!!!
P.S.: Flex.db can be used to disable Fast Dormancy on Gingerbread 20s stock rom, and maybe other Roms:
On v20s, add the requested line to build.prop ro.ril.fast.dormancy.rule=0 and editing flex.db in /data/data/com.lge.providers.flex/ and setting datacom_fastdormancy from 10 to 0 for your operator... tested, fully working, phone now is taking 36-48 hours to fully discharge in stand by mode, from 16-24 hours MAX!
Keep in mind that I had two operators, and with one of them the fix was not needed, the battery problem only occured when I changed Networks!
Or you could use this SQL commands to alter the entire file:
SELECT flex_name, operator_index, user_values, default_values FROM "main"."flexinfo" WHERE flex_name LIKE '%BRW_SETTINGDB_CURRENT_HOME_URL_I%' OR flex_name LIKE '%BRW_SETTINGDB_HOME_URL_I%';
update "main"."flexinfo" SET user_values = "http://www.google.com" where flex_name LIKE '%BRW_SETTINGDB_CURRENT_HOME_URL_I%' OR flex_name LIKE '%BRW_SETTINGDB_HOME_URL_I%';
update "main"."flexinfo" SET default_values = "http://www.google.com" where flex_name LIKE '%BRW_SETTINGDB_CURRENT_HOME_URL_I%' OR flex_name LIKE '%BRW_SETTINGDB_HOME_URL_I%';
SELECT flex_name, operator_index, user_values, default_values FROM "main"."flexinfo" WHERE flex_name LIKE '%BOOKMARKDB_CNT%';
update "main"."flexinfo" SET user_values = 0 WHERE flex_name LIKE '%BOOKMARKDB_CNT%';
update "main"."flexinfo" SET default_values = 0 WHERE flex_name LIKE '%BOOKMARKDB_CNT%';
or download this already edited file and copy over yours (every operator has no bookmarks, and every homepage set to google.com )! I didn't tested the file but it looks ok... I tested only the file I edited for myself! I grabbed the file from EUROPEAN v10E OPEN.
Copy the file over to /data/data/com.lge.providers.flex/databases/flex.db
Don't forget to change permissions on the copied file or you will get a Force Close bonanza!
cool, thank you for analysing it (my method was a little bit "rough" ^^')
I'll try your file.
Please post feedback, I searched the web high and low for a solution to this problem, I'm so excited I finally got my phone back clean and tidy ...
Permissions?
I'm an Android noob...how do you set 'permissions' and what should they be set to for this?
With file manager of choice
Use your file manager of choice to set the right file permissions, I use file expert (search for it on market) which is free, has root support and overall is a g great alternative to astro or root explorer...
The permissions need to be set so that the file sistem has read/write permission to the file, when you copy the file on sd card (like me) the permissions are all screwed up...
Remember, that to do this hack, your phone has to be rooted to have write access to system partition...
mihaiolimpiu said:
Ok, so I found this service resides in:
/data/data/com.lge.providers.flex/
/lib/ dir is empty
/databases/ has two files:
error_report.txt and flex.db !!!Every info for this is stored in that file and by editing this file we might find the answer!!
...
Click to expand...
Click to collapse
Thanks for the solution, I copied your flex.db file to my phone. However I only see /data/ not /data/data/ .
Do I need to be rooted to do this? Sorry but this is my first android phone...
Edit: only see now that it has to be rooted.. thanks.
Yeah it's my second android HOWTO, and I'm learning how to write it along you... I think I made pretty good explanations, but at the moment it's all scattered around, I'll try to make a point by point tutorial, and will edit one of the posts to make it easier to understand and apply on your phone!
Yeah, the phone has to be ROOTED, and if you try to apply this patch to another phone (other than LG O Black) first you have to find your flex service, on motorola I think the database is stored in /data/bla bla flex or something, other manufacturers have different names for the flex service, or they didn't made the bookmarks permanent and you simply don't need this hack!
The /data/data/com.lge.providers.flex/databases/ dir is on system partition, that you normally don't even see if your phone isn't rooted!
BE CAREFULL, this flex database has other info stored in there, practically it configures your whole network, and if you encounter problems , maybe it's better do edit the database by hand, I provided the full SQL command to do that on your PC...
mihaiolimpiu said:
Yeah it's my second android HOWTO, and I'm learning how to write it along you... I think I made pretty good explanations, but at the moment it's all scattered around, I'll try to make a point by point tutorial, and will edit one of the posts to make it easier to understand and apply on your phone!
Yeah, the phone has to be ROOTED, and if you try to apply this patch to another phone (other than LG O Black) first you have to find your flex service, on motorola I think the database is stored in /data/bla bla flex or something, other manufacturers have different names for the flex service, or they didn't made the bookmarks permanent and you simply don't need this hack!
The /data/data/com.lge.providers.flex/databases/ dir is on system partition, that you normally don't even see if your phone isn't rooted!
BE CAREFULL, this flex database has other info stored in there, practically it configures your whole network, and if you encounter problems , maybe it's better do edit the database by hand, I provided the full SQL command to do that on your PC...
Click to expand...
Click to collapse
Hi, okay so I've just rooted and verified that it is rooted. I would rather want to use the file you provided.
I installed file expert, renamed my flex.db to "flex.db old" (so I have a backup) and copied your flex.db into /data/data/com.lge.providers.flex/databases/ then changed the permissions to read and write for owner and group.
But when I open the browser it still opens the default home page, I thought it should open google.com.
Am I missing something? Thanks for the help so far.
You are right, it should open www.google.com!
Restart your phone... and the new file should be loaded! or maybe you could have that page open in a new window in browser (Navigator), try closing all browser windows to auto load homepage.
Oh, I remembered, some Operators, don't make their homepages PERMANENT, so maybe it's enough to change the homepage??? I don't know yet hot to remove PERMANENT HOMEPAGE... this is why I set them all to www.google.com!
Q: What about perma - bookmarks are they gone?
If it still opens default page please post feedback with country and operator, and I'll check the file for errors! or if it needs adding some setting if let's say your operator isn't listed!
YOUR FEEDBACK is very, very, very important, because I can only test 2 networks, and from my tests this is all I can do, maybe a setting is different for your operator, I didn't changed anything else (things I don't know what they do - that would be stupid no?).
I rebooted shortly after my previews post but to my horror the "force close" message appeared and I had to keep on dismissing it.
I managed to get into the file manager and delete your flex.db that I copied. It seems like it created a new flex.db when I rebooted again.
The "force close" problem is gone now but I am still stuck on the default home page.
The "force close" issue has something to do with permissions right?
I used the same permissions as the flex.db file that was there in the first place:
read and write for owner and group...
The "force close" thing scared me, it just kept on popping up again and again. I almost thought I bricked my phone.
Edit:
perma links? don't think I have any.
Yeah, the force close message appears if permissions are not set right... It needs read/write for Owner/Group/ALL!!!
I will test the file myself right now to make shure it all works OK! just wait a few sec and I'll post the test result!
Ok, I tested the file, checked all permissions -> phone rebooted, everything works as it should! Homepage set to google.com, no bookmarks anywhere!
Keep in mind I have V10E Europe Open, maybe if you have another firmware you need to manually modify your file... I'm not going to do a reflash just to test ... but, if you still get that FC message, just delete the file and it will go away.. Yeah, I know it's scary but keep it cool and you can fix it quickly by deleting the file!
If you want just open the file on your PC side and see how yours and mine looks.. or check for a VERY different size of the file, if there is a VERY BIG difference, chances are that your service loads a different kind of file and then only solution is to do it manually!
I uploaded a screenshot, see the homepage set to google.com, and only my bookmarks, not even one operator bookmark in sight!
mihaiolimpiu said:
Yeah, the force close message appears if permissions are not set right... It needs read/write for Owner/Group/ALL!!!
...
Click to expand...
Click to collapse
Success! I just needed to add permissions to ALL.
Thanks for the help. I am running Android 2.2.2 V10a.
I just test your DB, it works perfectly !
I think I'm on v10c (Nova Rom), with Belgian provider.
And I don't have given permission to "All", only to "Owner" and "Group" (as the original file).
Thank you very much !
I'm very happy to hear this! Thank you!
I also found out, that every carrier pushes 4 or more RSS adresses for an RSS reader??? have you been bothered by this?? does it need changing?
I think the most common are Engadget, CNN, and 2 more...
More detail on my work:
I searched the database, there are two values regarding browser homepage per carrier, (FROM MEMORY) browserdb_homepage_default_i and browserdb_homepage_current_i, I tried putting {NULL} there, deleting the value, a space, anything, it just doesn't let you change the homepage permanently. On boot it gets overwritten by some default android address (still google.com but more chars), so I decided to give it a rest for the moment.
I'm pretty happy with the results, this would of been great, but, in whole sincerity, who uses a different page different from a good search engine?
So, just consider the file I provided version 1.0!
The first tweak/fix is for a GPS update/change.
Starting with Android 5.0, GPS has been flaky for a lot of people. The device picks up satellites, gets a lock, but then loses the lock. Sometimes it then gets a lock again and holds it, sometimes it just drops it again.
This was not fixed with 5.0.1, 6.0, or 6.0.1. It took Google over a year to even acknowledge it was an issue.
A user suggested a fix in the official bug report thread:
https://code.google.com/p/android/issues/detail?id=81140#c695
They suggest telling the device to not attempt a Mobile Station Based update of GPS information.
This can be done by changing the "CAPABILITIES" value in /system/etc/gps.conf.
I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_GPS_Update_0.1.zip changes /system/etc/gps.conf to not use "MSB" updates.
Nexus_5_GPS_Restore_0.1.zip changes /system/etc/gps.conf back to the default of using "MSB" updates.
-----
The second tweak/fix is for CDMA users. I use my Nexus 5 on FreedomPop (a Sprint MVNO), and on almost every boot I'm greeted with this lovely message:
"Unfortunately, Update Device has stopped."
Its crash message mentions this:
java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
From what I've read, moving an app from /system/app to /system/priv-app is supposed to fix this. The two problem files (OmaClient.apk and UpdateSetting.apk) are both located in /system/app, not /system/priv-app.
I figured, "why not move them to priv-app?"
So I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_Sprint_Update_0.1.zip moves the apps from /system/app to /system/priv-app
Nexus_5_Sprint_Restore_0.1.zip moves the apps back from /system/priv-app to /system/app
-----
I tested these on CyanogenMod 13 (May 10th nightly build). There is no binary in the zip, each just contains a script to update the system, so you can easily view them in plain-text. Since both of the issues experienced seem to be impossible to purposely reproduce, I cannot say for sure if these fix the issue.
That's why I wanted to see if the files work or help others.
You can boot to TWRP and flash the zip files there. If you use something like CM Downloader, you can add them as additional zips to flash after any ROM update.
Let me know!
My GPS has been really useless these days. I guess I have to root my phone to try this out..
If I want to do it manually, what do I have to change it to?
ashirviskas said:
If I want to do it manually, what do I have to change it to?
Click to expand...
Click to collapse
Open /system/etc/gps.conf
Change this:
CAPABILITIES=0x33
To this:
CAPABILITIES=0x31