Database Develop

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

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.

[MOD] Hulu mod and Webtop/Hotspot Tether for 4.1.57

I was able to get the hulu mod to work inside dolphin browser HD, and also the tethering option in the laptop dock to work, I used Ririal's script to root the phone on the latest 4.1.57 and then ran these commands in a adb shell as ROOT :
for hulu please updated flash player to 10.2 first in the market then apply the libflashplayer.so (can be found in the latest gingerblur package) file to lib folder of the flash player ::>
cp -f libflashplayer.so /data/data/com.adobe.flashplayer/lib
then we go on to unlocking the APN's and borrow some of the code from gingerblur mod from the addons batch file ::>
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f sqlite3 /system/bin/sqlite3
chmod 755 /system/bin/sqlite3
sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db "UPDATE carriers set preloaded='false';"
/system/bin/sqlite3 /data/data/com.android.providers.telephony/databases/telephony.db "INSERT INTO carriers (name, numeric, mcc, mnc, apn, user, server, password, proxy, port, mmsproxy, mmsport, mmsc, mmsc2, authtype, type, current, preloaded) VALUES ('AT&T (FREE TETHER)','310410','310','410','wap.cingular','[email protected]','','CINGULAR1','','80','wireless.cingular.com ','80','http://mmsc.cingular.com ','','-1','','1','false');"
reboot
and now you are done, next go to the APN's and check they are unlocked then change the AT$T US tether APN type to nothing, then add the "tether" with a comma at the end of the APN type of AT$T US HSDPA , then reboot the phone, once in webtop you can change from the free tether to hdspa then the verification nag will go away and you will be able use the laptop dock.
If anyone can put all this in a script as i got no brains to do a script right now
DO THIS AT YOUR OWN RISK, I AM NOT RESPONSIBLE IN ANY WAY IF YOU BRICK YOUR PHONE OR ANYTHING THAT RELATES TO THIS POST, THIS IS FOR INFORMATIONAL PURPOSES ONLY !
With that being said have fun
EDIT :
And confirmed sideloading working, issue this command in adb shell as ROOT ::>
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE secure SET value=1 WHERE name='install_non_market_apps';"
Then reboot, now you can install apps direct from the sd card.
EDIT 2:
Commands corrected now.

Does the mod retain the tegra specific version of flashplayer?

Well I used the .so file from the gingerblur 7.7 package and the flash player 10.2 from the android market, so does this make it non specific to the tegra chip?
Sent from my MB860 using XDA App

molotof said:
Well I used the .so file from the gingerblur 7.7 package and the flash player 10.2 from the android market, so does this make it non specific to the tegra chip?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I used the Market Flash 10.2 and Gungerblur RC1 .so,
Hulu works in Dolphin HD, had to set the user agent to desktop and plugins to always on.
Going to try the webtop over cellular.

How to enable The Hotspot Tether for 4.1.57？

joojle said:
How to enable The Hotspot Tether for 4.1.57？
Click to expand...
Click to collapse
Just follow the tethering steps and you are set to turn on hotspot from the settings under wifi.
Sent from my MB860 using XDA App

molotof said:
Just follow the tethering steps and you are set to turn on hotspot from the settings under wifi.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I get a syntax error on your first sqlite3 command, something along the lines that it's expecting a ")" ??

http://forum.xda-developers.com/showthread.php?t=1017373
Not to detract from the thread, but this enabler is a simpler way of getting sideloading/tethering APNs installed. No need for manual commands assuming you used the correct tools to root in the first place (i.e. sqlite3 is installed.).

Yeah better off using the scripts now as all is well in gingerblur land

molotof said:
Yeah better off using the scripts now as all is well in gingerblur land
Click to expand...
Click to collapse
Thanks for the effort though!

All the thanks go to you and other devs here in xda for such a great job in working on these things and making our lives easier
Sent from my MB860 using XDA App

Will THis Mod Work without Gingerblur
I've been too lazy to install Gingerblur but wanted to see if this mod will work without it. Thanks!

Couldn't you just use the zip files
(hulu,webtop,hdmi etc) included separately in the kennethpenns gingerblur thread? Wouldnt that work through tenfars cwm without actually installing gingerblur itself or are those specific to gingerblur only?
Edit: Actually I just answered my own question! lol the zips all install fine on stock 4.1.57 with root but do they work? I'll find out soon enough...

Gutterball said:
Couldn't you just use the zip files
(hulu,webtop,hdmi etc) included separately in the kennethpenns gingerblur thread? Wouldnt that work through tenfars cwm without actually installing gingerblur itself or are those specific to gingerblur only?
Edit: Actually I just answered my own question! lol the zips all install fine on stock 4.1.57 with root but do they work? I'll find out soon enough...
Click to expand...
Click to collapse
That i have no idea if it is possible or not, as these commands are for the purists that want CrapyBlur on and the original look without doing anything else to the file system.
I think it is in gingerblur add on packages BUT you would need the sqlite from the main package, so i guess this is the best bet for now !

molotof said:
That i have no idea if it is possible or not, as these commands are for the purists that want CrapyBlur on and the original look without doing anything else to the file system.
I think it is in gingerblur add on packages BUT you would need the sqlite from the main package, so i guess this is the best bet for now !
Click to expand...
Click to collapse
Actually installing those zips on stock work through cwm! So thats good enough for me! Thats cool! Because I like gingerblur but for some damn reason whenever I install it? my wifi is weak and disconnects alot... I have no idea why??

Indeed got it working
Although, what have you guys seen in terms of how well HULU works? For me it's a little buggy. The video has issues with commercials not loading properly. I assume this is normal.
But all the other video controls seem to be fickle

mattyv said:
Although, what have you guys seen in terms of how well HULU works? For me it's a little buggy. The video has issues with commercials not loading properly. I assume this is normal.
But all the other video controls seem to be fickle
Click to expand...
Click to collapse
The reason ads wont play is probably because you have ad blocking setup on your phone. What rom and root did you use? The regular vids will still play but commercials wont come through. LOL big loss!

thanks
you are right. it does work without the ads working. one thing i noticed is that the speed is a little slow on hulu using the webtop. i.e. the video is choppy. has anyone had any experiemce with that? is it something that can be sped up?

mattyv said:
you are right. it does work without the ads working. one thing i noticed is that the speed is a little slow on hulu using the webtop. i.e. the video is choppy. has anyone had any experiemce with that? is it something that can be sped up?
Click to expand...
Click to collapse
I noticed that too. Honestly gingerblur somehow, someway was having an adverse reaction on my wifi(though I seem to be the only one with this problem) I flashed back to stock, rooted, installed all the seperate zips from gingerblur without installing gingerblur itself using tenfars cwm recovery. Then I flashed gladiatrix rom also and my wifi has been perfect and hulu is running at normal speed with no choppiness.
The only thing with hulu is you gotta uninstall flash player 10.2 and grab the one from the market. Then grab a file called libflashplayer.so and copy it to data/data/com.adobeflashplayer/lib put it inside that folder using root explorer and it should ask you to overwrite click yes. Then open dolphin hd in settings make sure flash plugin is set to always on and that the agent is set as desktop. Then go to hulu.com click a video and it should play fine and with sound cause I was having a problem with no sound but this fixes it!
As far as the webtop is concerned?I think the webtop in general is buggy and laggy but still an awesome feature to have it probably will get better with more updates.

just wanna be sure here the only line i need to enable the hulu mod is this?
cp -f libflashplayer.so /data/data/com.adobe.flashplayer/lib

[MOD][Comrom]How-to update to swype beta 3.0 with installer link[6/25]Updated

1. Change input method to any other keyboard.
2. In the /system/app folder, delete Swype.apk
3. In the /system/lib folder, delete libSwypeCore.so
4. In the /data/data folder, delete the com.swype.xxx folder
5. In the /data/dalvik-cache folder, delete the [email protected]@swype.... file.
6. REBOOT OR IT WON't INSTALL PROPERLY
7. Install and run the swype beta installer and follow the on-screen instructions. Installer link here http://db.tt/cD8HXlI
You also can rename the files to .xx.bak so you have a backup. This works 100% for me on Com Rom 2 after just installing today so I don't know how this will work on systems that have been used daily for a while.
I take no part if none of this works and permanently deletes swype from your phone. Your own fault.
Credit to google leading to this post by Snow02 on droid x forums

What exactly is it?
Sent from my SCH-I500 using XDA Premium App

A keyboard
Sent from my SCH-I500 using XDA Premium App

Its the newest version of swype. I was running it when I was using JTs CM7 but I thought it was worse then our TW swype.
Sent from my SCH-I500 using Tapatalk

representingcochran said:
Its the newest version of swype. I was running it when I was using JTs CM7 but I thought it was worse then our TW swype.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
How is it worse?

Its not I just swyped this from 3.0 I personally think its better I didn't make a single mistake while writing this when I usually do with older versions.
Sent from my SCH-I500 using Tapatalk

tonu42 said:
Its not I just swyped this from 3.0 I personally think its better I didn't make a single mistake while writing this when I usually do with older versions.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I completely agree with you, its a complete improvement from the last version. The word suggestion window is gone and moved to a frame above the keyboard, word prediction is way more accurate, swyping is more accurate, etc.

I'm a big swype user, so thanks for the instructions...may give this a whirl.

Where can I find the swype beta installer?
Sent from my SCH-I500 using XDA Premium App

http://beta.swype.com
The biggest change (other than tablet support) with Swype 3 isn't even the much improved suggestion window or the faster and more accurate swiping: it's that Swype now does predictive tapping too.
No more need to switch between Swype and the stock keyboard or SwiftKey if you aren't in a swiping mood. That's why their tagline for 3.0 is - and I'm not making this up, just watch their promo videos - "Stroke it AND poke it."

So what color is the new swype?
Edit: My sywpe expired so im being forced to update. Instructions worked perfectly thnx.

Thanks for the instructions. Worked perfectly. Now to get used to the slightly different interface...

Thanks for putting this little tutorial out there cuz after updating to UKB2.1 the swype keyboard stopped working
I admit I might not the most brainy person when it comes to this
Had a heck of a time figuring out how to remove those system files... finally resorted to Root Explorer (paid app) to remove these files (I am sure there was a way to do it without, but I refer you to the above comment)
For some reason the swype beta likes to be authenticated twice...
and after the second authentication process, I made sure to reboot before using the keyboard...
so far it is working and I like the new keyboard... (I had better since it would take me another whole afternoon to figure out how to install the old swype keyboard)
thanks again and keep up the good work

jabberjaw said:
Thanks for putting this little tutorial out there
Click to expand...
Click to collapse
+ 1 - thanks button was hit
jabberjaw said:
Had a heck of a time figuring out how to remove those system files... finally resorted to Root Explorer (paid app) to remove these files (I am sure there was a way to do it without, but I refer you to the above comment)
Click to expand...
Click to collapse
Glad you got it worked out, but wanted to let you know not to feel bad about going to root explorer. You will likely find that you have a lot of uses for it - there is a LOT that goes on round here that having root explorer makes life a lot easier to follow...
Enjoy!

I just updated to 2.1 and my swype crapped out on me too. I've tried everything to get it working, but nothing works.
I've been trying to delete the swype.apk and other files instructed here, but they won't delete. 'don't have permission," "read only" or "Cannot Delete." I'm using Root Explorer too, and trying to switch Mount r/o to r/w, and it won't change! Someone help me! I'm going through Swype withdrawls already!
What program is everyone using to locate and delete files?
BTW, I've switched keyboards before I try to delete, still no luck.

neotrixy,
i remember having similar difficulty
try changing [mount r/o] button before you select the app you want to delete,
couldn't find a another protected system app to delete to try this again, but I was able to switch the mount button back and forth by pressing the grey button at the top of the screen
hope this helps
ps- i did find that someone posted a swype fix in the UKB thread (not sure if it works)... it is way back in the thread... but i had already switched to beta before i found it

No, i think already mentioned, for whatever reason, the button won't change to r/w. It's stuck on r/o. I don't know what the problem is, I've never had a problem like this before.
Thanks for the help though!
Any other ideas?

I think i got it fixed...I downloaded a newer version of Root Explorer, and it let me change the r/w.
Thanks guys!

ok,
It sounds like your Root Explorer program has not been granted superuser permissions yet.
I can't remember when it asked for those permissions, check in your superuser icon to see if Root Explorer is listed in there and has a green circle next to it.
I have been looking in looking around in the Root Explorer menus but don't see anything
I hope it is as easy as clicking the allow button in superuser, if not my other thought would be to uninstall and reinstall Root Explorer to see if it will ask for superuser permissions when you open it up.
good luck

Yes
Thanks for your help. I was so frustrated with Verizon having made that (or so they thought) permanent. That is so stupid they want their people stuck with an old version. Appreciate all your help. God bless in Jesus' Name.

[MOD] Enable Tethering on 4.5.91

Been Busy building, but thought id quickly help those of us that can not live with out mobile hotspot and decided to upgrade to 4.5.91. Here is the easiest way....
* prerequisites*
1. Root
2. SQlite editor from market
*Steps*
1. open SQlite editor and scroll to Settings Storage (com.motorola.android.provider.settings
2. click settings.db
3. click settings
4. go to Line 156 labled Entitlement Check with a value of 1 *EDIT* People are reporting different line numbers based off build etc, JUST Find "entitlement check"
5. Change value from 1 to "disabled" (without quotes)
6. reboot
7. enjoy

t0dbld said:
Been Busy building, but thought id quickly help those of us that can not live with out mobile hotspot and decided to upgrade to 4.5.91. Here is the easiest way....
* prerequisites*
1. Root
2. SQlite editor from market
*Steps*
1. open SQlite editor and scroll to Settings Storage (com.motorola.android.provider.settings
2. click settings.db
3. click settings
4. go to Line 156 labled Entitlement Check with a value of 1
5. Change value from 1 to "disabled" (without quotes)
6. reboot
7. enjoy
Click to expand...
Click to collapse
I am on kens 4.5.91 based rom and there is no line 156, any ideas.

kens rom did not come with it pre enabled ?... well I have never ran it so i wouldnt know but if its failing due to start and saying not authorized, than you need to find the entitlement check it should be in the motorola settings one some where , I am sorry i cant be more help but if it is indeed different from some reason it is hard for me to know with out using it or having it here to search for it

t0dbld said:
kens rom did not come with it pre enabled ?... well I have never ran it so i wouldnt know but if its failing due to start and saying not authorized, than you need to find the entitlement check it should be in the motorola settings one some where , I am sorry i cant be more help but if it is indeed different from some reason it is hard for me to know with out using it or having it here to search for it
Click to expand...
Click to collapse
No, it was not pre-enabled. When attempting to use mobile hotspot you get the message about the account not being authorized, because well, it really isnt.
I found the entitlement check on line 118 set to 1. Changed it to disabled, will post back with results after reboot.
[edit] Works like a charm!

I found the "entitlement check" at line 153. changed it to "disabled" and it's working. I guess it's handset dependent. Filter under "entitlement" and you'll find it.

pyro254750 said:
No, it was not pre-enabled. When attempting to use mobile hotspot you get the message about the account not being authorized, because well, it really isnt.
I found the entitlement check on line 118 set to 1. Changed it to disabled, will post back with results after reboot.
[edit] Works like a charm!
Click to expand...
Click to collapse
did it work?

seattleboi1982 said:
did it work?
Click to expand...
Click to collapse
yep, posting this on my laptop via hotspot.

well, like i said im on stock build right now between my stuff as long as you find entitlement and turn to disabled you be good , never the less im glad i was able to help

line 164 here, will post results

its intersting how it seems to be a different line for everybody, lol

Datblkbro said:
line 164 here, will post results
Click to expand...
Click to collapse
Well im not getting the att message, but for some reason Im not getting a connection
Limited connection/no connection

Awesome, ive been looking for something like this for a while now. Worded perfectly.
Sent from my Xoom using Tapatalk

i get an error saying turn off wifi and try again. tried it with both wifi on and off with no luck. im on Fido network in canada with ATT atrix if that makes a difference.

118 for me on beta #4.5

Line 118 here for me too... works perfectly.

Seems to work ok as per the other ROMS which is good because i dont live in the USA and therefore couldnt pay for tethering if i wanted

couldn't find settings in settings.db any idea?

kumar_r100 said:
couldn't find settings in settings.db any idea?
Click to expand...
Click to collapse
Press settings.db and it will open using sqlite.
sent from my unlocked MB860 via Tapatalk

Thanks! Line 118 for me on Kenneth's 4.5
sent from my unlocked MB860 via Tapatalk

Worked here but clients can't get internet access on wifi tether neither wired.

[Q] Creating a back door

Some of the recent posts have suggested that we may soon see a patch for the root exploit we currently have.
Being that we have root now is there some place we could hide SU where we could access it later should root be closed on us, allowing re-rooting of the device? It would have to be some place that does not get overwritten when an update is pushed...and I am not sure if that even exists on Android.

Not easily, since system is one of two partitions that doesn't have nosuid or noexec set.
Sent from my DROID3 using xda premium

Dunno about that, but I've been told there are a couple root methods being saved for later....

So I guess I am correct in assuming that the entire /system gets overwritten during an update?
I just played a bit with /root but cannot get anything to run with the current permissions of the mount.
For my understanding am I correct in the belief that all system directories get overwritten "/sys/ /system/"?

slow88lx said:
Dunno about that, but I've been told there are a couple root methods being saved for later....
Click to expand...
Click to collapse
Thank god for this!
Sent from my DROID3 using XDA App

calash said:
So I guess I am correct in assuming that the entire /system gets overwritten during an update?
I just played a bit with /root but cannot get anything to run with the current permissions of the mount.
For my understanding am I correct in the belief that all system directories get overwritten "/sys/ /system/"?
Click to expand...
Click to collapse
It doesn't get overwritten, but the update does reset all permissions. Thus, the su executable will still be there after the update, but will be chmodded 0755.

Just brainstorming so feel free to tell me I'm wrong
What about replacing a suid binary. Ping is the one I am thinking of right now. Would the update replace that file?
Sent from my DROID3 using Tapatalk

calash said:
Just brainstorming so feel free to tell me I'm wrong
What about replacing a suid binary. Ping is the one I am thinking of right now. Would the update replace that file?
Click to expand...
Click to collapse
Looking at the permissions set in the update's script, it doesn't look feasible. If I'm reading them right, PING's permissions only allow it access to the NET_RAW group, which doesn't give us anything useful. Everything else is just as unhelpful.
Anyone know if it would be possible to fastboot flash an older recovery to a device with a newer bootloader, then temproot that and use it to permroot the device?

Xenoproctologist said:
Looking at the permissions set in the update's script, it doesn't look feasible. If I'm reading them right, PING's permissions only allow it access to the NET_RAW group, which doesn't give us anything useful. Everything else is just as unhelpful.
Anyone know if it would be possible to fastboot flash an older recovery to a device with a newer bootloader, then temproot that and use it to permroot the device?
Click to expand...
Click to collapse
Sorry to go off topic, but am I the only one who's wondering how ironic it is that a user named "xenoproctologist" is responding to a thread titled "Creating a Back Door"?
Freud would have a goddamn field day with this!

rynosaur said:
Sorry to go off topic, but am I the only one who's wondering how ironic it is that a user named "xenoproctologist" is responding to a thread titled "Creating a Back Door"?
Freud would have a goddamn field day with this!
Click to expand...
Click to collapse
No, no... I only use pre-existing back doors. ^_^

I would rather have bugs than no root. I sat on my droid3 until root was available rather than activating it.
Would it be possible in that case to run FOTAkill on a rooted d3? If so, would it help?
I noticed a couple of OTA/update related apks while noodling with Titanium.... could those be frozen to prevent updates?

hiddenhandgun said:
I would rather have bugs than no root. I sat on my droid3 until root was available rather than activating it.
Would it be possible in that case to run FOTAkill on a rooted d3? If so, would it help?
I noticed a couple of OTA/update related apks while noodling with Titanium.... could those be frozen to prevent updates?
Click to expand...
Click to collapse
There are only one or two lines in build.prop that need to be changed to prevent receiving OTAs or update notifications. Search on the DroidX forums and you'll find these values.

Editing the build.prop is not the best way to prevent OTA updates.
It will cause issues with Market and other functions that read those strings for various reasons.
Disabling by freezing or renaming BlurUpdater_VZW.apk and FOTA.apk is safer and will not affect anything else adversely.

cellzealot said:
Editing the build.prop is not the best way to prevent OTA updates.
It will cause issues with Market and other functions that read those strings for various reasons.
Disabling by freezing or renaming BlurUpdater_VZW.apk and FOTA.apk is safer and will not affect anything else adversely.
Click to expand...
Click to collapse
Thanks. I'll give that a go.

There is always something being worked on to retain/get root again after a patch. There is also a good reason it doesn't get talked about in any kind of detail.