Database Develop

[QUESTION] *.apk Gets overwritten on Reboot

For some reason, on the G1 with AOSP1.6_r1.2 & expansion, When i write the new maps.apk (3.2) From Here, over the origonal GoogleMaps.apk, It installs Fine. And loads fine, But Once Android is rebooted, the old file comes back... Reminds me of microsoft's shadow copy..... Anybody have a clue on how to stop it or force a particular file????

are you replacing the file in system/app? since that is where most roms store maps?

david1171 said:
are you replacing the file in system/app? since that is where most roms store maps?
Click to expand...
Click to collapse
You are correct.. thats where my GoogleMaps.apk is.

if you are replacing that file, then you could try to remove it, then install maps like a normal app onto the data partition.

david1171 said:
if you are replacing that file, then you could try to remove it, then install maps like a normal app onto the data partition.
Click to expand...
Click to collapse
Im in the middle of trying that right now.... It installed again without problems, now just waiting for the reboot to test if it got overwritten.
EDIT - Still no luck.... Just keeps getting Overwritten..... Can i change the Name of the new Google Maps so it has a new icon???

Any ideas anyone? Is this in the Wrong Forum??????

did you rm the file from /system/app/ and install it like a normal app? did you copy the .apk file from your sdcard to its location in /system/app/?
do you need commands on how to do this?

I deleted system/app/GoogleMaps.apk , and watched it disappear from the app drawer. then Moved the new GoogleMaps.apk into data/app/ . Installed it and ran it no problem... can exit and even go back into 3.2 no problem. but as soon as i reboot,the original GoogleMaps.apk is back in system/app/ ..... so im clueless.

I just installed successfully by copying the file to /system/app/Maps.apk
... not GoogleMaps.apk

Technochris1 said:
I deleted system/app/GoogleMaps.apk , and watched it disappear from the app drawer. then Moved the new GoogleMaps.apk into data/app/ . Installed it and ran it no problem... can exit and even go back into 3.2 no problem. but as soon as i reboot,the original GoogleMaps.apk is back in system/app/ ..... so im clueless.
Click to expand...
Click to collapse
how are you deleting it?
do that in the recovery console and see if that works
Code:
mount system
rm /system/app/GoogleMaps.apk
reboot

did what you said, after reboot the old googlemaps.apk is still there......

ls /system/app
remove maps.apk

david1171 said:
ls /system/app
remove maps.apk
Click to expand...
Click to collapse
in recovery or terminal?

Technochris1 said:
in recovery or terminal?
Click to expand...
Click to collapse
in terminal
Code:
su
ls /system/app/
(will give you a long list of .apk files)
(find the correct name for maps.apk)
reboot recovery
then in the recovery console
Code:
mount system
rm /system/app/-insert appname form above-.apk
reboot

I just did the above and as soon as you reboot again the old google maps is back!
Perhaps you could copy the new maps over while in recovery after deleting the old one?
The Maps apk file is named "GoogleMaps.apk" btw.
Phil

Technochris1 said:
For some reason, on the G1 with AOSP1.6_r1.2 & expansion, When i write the new maps.apk (3.2) From Here, over the origonal GoogleMaps.apk, It installs Fine. And loads fine, But Once Android is rebooted, the old file comes back... Reminds me of microsoft's shadow copy..... Anybody have a clue on how to stop it or force a particular file????
Click to expand...
Click to collapse
I see you are running Enomther's ROM. I was having the same problem - it turns out that Enomther's ROM had an easy fix all along. Run expsetup in terminal and choose Option 15 - you can delete Google Maps right there (I took advantage of deleting a few other apps that I don't use at the same time).
Then just reboot - place your new GoogleMaps.apk in the /system/app folder and you are golden.

Thanks dude. Thats the solution to my question....

I posted in the other thread...It is in the following folder
/system/sd/expstick/vsapps/GoogleMaps.apk
I am running the new app and am on Enoms latest AOSP 1.6.

Great! That worked a treat. Got it working just fine.
Phil

[FIX]Obsidian FIX Thread 11/11/2010

11/11/2010 - Ive been busy with school so I apologize for slacking in the updates with stuff found in the thread. I also believe some new bugs have appeared in V2 of Obsidian. Don't quote me on this but I do believe a V3 is in the works but it could be a while to MAKE SURE ALL THE BUGS ARE OUT. So don't ask when it will be released. I also heard there is Z4Mod and Voodoo kernels being released with V3 as well. Till this, check here for fixes.
Fixed in V2, for those having issues with sync on the calendar
http://forum.xda-developers.com/showpost.php?p=9073317&postcount=239
Fixed in V2, for those experiencing FC on acore, reboot
for those experiencing FC on com.sec.android.screencapture (what ever the apk name is) uninstall it from titanium.
Fixed in V2, Live wallpapers are fixed.
FCC, FFC DOES WORK! (still banding on the rear camera) here is the Epic Camera. FFC is at 90 degrees for some reason?!?
LagFix, Some are reporting to get it to work, others are not. I was able to get it to work in V1 with OCLF, but I can't seem to get it to work in V2. (even with a modified kernel I'm probably building it wrong) but you can check this link.
Read-Only Bookmarks, the bookmarks are locked in the browser. fix here thanks to PaiPiePia
http://forum.xda-developers.com/showpost.php?p=9081134&postcount=19
Read-Only System manual copy.
For those having problems with a read-only system try these commands to manually copy the file. (THX srqt I believe)
adb shell
su
busybox mount -o rw,remount /dev/block/stl9 /system
busybox cp /sdcard/external_sd/app.apk /system/app/
reboot
for lock-ups on mounting SD You have to turn off the usb debugging, then use the Media Player option under usb settings. If not, the internal sd card shows up as a cd drive and you can not copy files to the internal sd ~BiiGreeN
I will be adding more fixes as the appear in #teamwhiskey or this thread when I can.
Keep in mind, this is based 99.9% off the Vibrant Froyo Rom. Its the 2.2 STOCK Kernel (no OC/UV yet), that means NONE of the 2.1 Kernels will work with it. there are also no custom lock screens yet either.... that work.
Im also known as FlyingPoo on the Team Whiskey forums and chat room.

What about Bootanimation sounds?

Or maybe add a lockscreen choice like 2.2 aosp lockscreen

TheExpertNoob said:
First, for those having issues with sync on the calendar
http://forum.xda-developers.com/showpost.php?p=9073317&postcount=239
Second, for those who want a LagFix, you will need to push the playlogos and playlogos1 manually.
http://forum.xda-developers.com/showpost.php?p=9075146&postcount=345
I will be adding more fixes as the appear in #teamwhiskey.
Click to expand...
Click to collapse
...why do you have to push playlogos manually? OCLF will do it for you. It gives you the option. Just install ext 2 tools, hit the playlogos option, then enable lagfix 2.2+
OCLF is available in the market...

mikeyinid said:
...why do you have to push playlogos manually? OCLF will do it for you. It gives you the option. Just install ext 2 tools, hit the playlogos option, then enable lagfix 2.2+
OCLF is available in the market...
Click to expand...
Click to collapse
OCLF woulnt let me install the playlogos for some reason, i had to add them manually.

TheExpertNoob said:
OCLF woulnt let me install the playlogos for some reason, i had to add them manually.
Click to expand...
Click to collapse
Hmmm. I had no problems, but couldnt disable it. Had to odin

Also, for those who have screencapture FC problems, you can use root explorer or adb to delete ScreenCapture apk from /system/app.

TheExpertNoob said:
OCLF woulnt let me install the playlogos for some reason, i had to add them manually.
Click to expand...
Click to collapse
Which version are you usng? I read that only a certain version works. I have that version, Im ironing so I cant look right now

The problem with this is that we disabled the playlogos files via the kernel and we're using a custom init script called 'sombionixInit' in /bin where the playlogos would originally be.

sombionix said:
The problem with this is that we disabled the playlogos files via the kernel and we're using a custom init script called 'sombionixInit' in /bin where the playlogos would originally be.
Click to expand...
Click to collapse
bad som >.> what should we do about it? cause i did get OCLF to work with the OP above method.

I tried that for calendar but now my calendar force closes. I moved that apk into system /app
Sent from my SGH-T959 using XDA App

sombionix said:
The problem with this is that we disabled the playlogos files via the kernel and we're using a custom init script called 'sombionixInit' in /bin where the playlogos would originally be.
Click to expand...
Click to collapse
I flashed one of eugenes kernels and oclf did work. but i wasnt able to disable it.

i restored boot animation and got the lag fix option green but it fails to install.

knicks235 said:
i restored boot animation and got the lag fix option green but it fails to install.
Click to expand...
Click to collapse
try NOT restoring boot animation. transfer over the playlogos again.... because "restoring boot animation" replaces playlogos1

TheExpertNoob said:
try NOT restoring boot animation. transfer over the playlogos again.... because "restoring boot animation" replaces playlogos1
Click to expand...
Click to collapse
adb is not on this comp, can i push through astro or a root explorer?

knicks235 said:
adb is not on this comp, can i push through astro or a root explorer?
Click to expand...
Click to collapse
yes, its actually how i ended up doing it

Nice thread, good work...any idea how to fix the issue that you can not delete the bookmarks from web browser?

VICosPhi said:
Nice thread, good work...any idea how to fix the issue that you can not delete the bookmarks from web browser?
Click to expand...
Click to collapse
yea i noticed that too about the bookmarks cause it wouldn't let me edit the facebook for "m.facebook.com" cause i like it better than the touch.... ill look into it more later. it could be "hard coded" in to the browser now? part of the FS may still be locked also seeing as how those are the "default" bookmarks you get after a wipe.

Edit: VICosPhi has pin-point the reason why the bookmark can't be deleted, use his modified and down-loadable Browser.db. Credit goes to him for figuring out the exact problem!
VICosPhi said:
Hey, from the solution you provided, I was able to pinpoint the cause of "undeletable" bookmark and changed the target folder.
For other folks,
Download the attached browser.zip file and extract the "browser.db" from it and then overwrite the browser.db located in your phone's /dbdata/databases/com.android.browser/ with the extracted file from the downloaded zip package.
Now you should be able to delete the bookmarks. You will need root explorer to do this.
NOTE: Credit goes to PaiPiePia for addressing this bug.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=436351&d=1289193826
-----------------------------------------------------------------------------------------------
Here's a fix written by me, posted in the original thread too.
1) Use this open source Sqlite Editor (doesn't have to be this one, it is just a free one that I found that worked for me). It is great because it is portable version thus no installation required.
http://sourceforge.net/projects/sqlitebrowser/
2)Using Root Explorer or any other Root Capable File Manager.
3)Browse to /dbdata/data/com.android.browser
4)Scroll down until you see "browser.db"
5)Copy that file on to your desktop (Via sdcard then mount the sdcard)
6)Open the Sqlite Editor you downloaded above, and Open the Browser.db you had copied to your windows desktop
7) Select Tab "Browse Data" at the top right corner (unless you understand what you are doing, please don't edit anything else.)
8) Under Table (drop-down menu), Select Bookmarks
9) The is how the file is structured:
-At the top portion are those bookmarks that can't be deleted
-At the bottom contains your personal browser history & additional bookmarks you added manually.
if you don't care about your history and your manually added bookmarks, you can delete every entries you see there by selecting one entry and click "Delete Record at the top right", repeat until the entire table is done/blank.
10) Save the change to Browser.db
11) Copy the modified Browser.db to the original "/dbdata/data/com.android.browser"
12) Use build in Task Manager to "End" the browser
13) Restart Browser and you will have a blank Bookmark Tab!
-Note, user added bookmark can be removed without doing this method (I haven't figure out why that is yet).

sombionix said:
The problem with this is that we disabled the playlogos files via the kernel and we're using a custom init script called 'sombionixInit' in /bin where the playlogos would originally be.
Click to expand...
Click to collapse
Can you post a version of the ROM that acts normally and...doesn't do that... please

[Project] Unroot ROM

Hey guys, since I already saw it a couple of times now, that USB was broken and ppl cant unroot their phones using Smartflash then, I wanna make a ROM, that can be flashed by using CWM. Cause often ppl are able to access it still, but cant push data via USB.
What do we have to consider? I am using tantrums repack as a base http://forum.xda-developers.com/showthread.php?t=1554274.
I used the v20o version.
I think we need to remove /bin/su, /xbin/busybox, /app/superuser.apk. Also we need to remove symlinks. But I dont know which ones to remove...
Also we need the stock recovery.img, to get the original one back to the phone. ro.secure is still 1, so I think he didnt mess with the boot.img.
Did I miss anything and could anyone please mod the updater-script, so that the unnecessary symlinks are gone?
UPDATER-SCRIPT
Thanks in advance guys
P.S. if anyone has got a working updater-script without su and busybox for any other version, you can also hand it over. Cause then I ll just make a nandroid of that version, add the updater-script and binary, maybe the whole META-INF folder, the recovery.img from the according .bin file and then we also would have the perfect unroot ROM. Just hope anyone can help me

You need fresh files. Odexed. The ROM cannot be deoxed one if you're after warranty with LG.
There should be a busybox file in xbin. The original one.
All apps should be there including bloatwares.
Should be ext3 (default), not ext4. Use original boot.img cause there might be insertion of G-recovery on that ROM.
Updater-script: you can remove: symlink("/system/bin/su", "/system/xbin/su");
PS. Ask the person who would use, what was his last firmware flashed. Consider the baseband should match. Though it only shows XMM61xx, they might have a way to know.

To be a super clean rom:
More the stock build.prop since normally its changed to appear different things in "About Phone", for the rest, Gab already said everthing nedded

Both gabwerks and duarte got it covered.
Hmmm .... I think I got the unrooted, odexed v20o files in my PC. I can upload here if needed.
A recap of what to do.
1. Copy the boot.img from the stock ROM. I modified the boot.img to include g-recovery.
2. Copy the build.prop from the original stock ROM.
3. all apks were deodexed in my zip. So delete the app and framework folder from my zip and replace from the original stock ROM.
4. Edit the updater script.
a. use ext3 instead of ext4
b. remove: symlink("/system/bin/su", "/system/xbin/su");
5. compile. and i think that's it.

Does this look good then? I ll make a dutch unroot ROM, since this guy is dutch
http://pastebin.com/65tfX78H

N00BY0815 said:
Does this look good then? I ll make a dutch unroot ROM, since this guy is dutch
http://pastebin.com/65tfX78H
Click to expand...
Click to collapse
I think thats good .
Here you have the stock V20S build.prop if you want:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRJ22
ro.build.display.id=GRJ22
ro.build.version.incremental=LG-P970-V20s.47F1AEC6
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Mon Jul 2 12:55:00 IST 2012
ro.build.date.utc=1341213900
ro.build.type=user
ro.build.user=chinmay.mohapatra
ro.build.host=si-rd10-bld65
ro.build.tags=release-keys
ro.product.model=LG-P970
ro.product.brand=lge
ro.product.name=lge_bproj
ro.product.device=bproj_EUR-XXX
ro.product.board=bproj
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=GB,en
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=bproj_EUR-XXX
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lge_bproj-user 2.3.4 GRJ22 LG-P970-V20s.47F1AEC6 release-keys
ro.build.fingerprint=lge/lge_bproj/bproj_EUR-XXX:2.3.4/GRJ22/LG-P970-V20s.47F1AEC6:user/release-keys
# end build properties
rild.libargs=-d /dev/ttyspi0
alsa.mixer.playback.master=DAC2 Analog \
#
# ADDITIONAL_BUILD_PROPERTIES
#
user.feature.flex=true
user.feature.lgdrm=true
user.feature.lgresource=true
user.feature.lgsetupwizard=true
user.feature.lgpoweroff=true
user.feature.preload_so=true
user.feature.preload_del=true
user.feature.lock_sui=true
user.feature.sui=true
user.feature.cmf=true
user.feature.wapservice=true
user.feature.lgorientation=true
user.feature.toucharea=true
user.feature.velocitytracker=true
user.feature.lgscroller=true
user.feature.eventthrottle=true
ro.build.lge.version.release=LG-P970-V20s
ro.config.ringtone=22_Dazzling_Brightness.ogg
ro.config.notification_sound=01_Acoustic_Guitar.ogg
ro.config.alarm_alert=Alarm_Beep01.ogg
ro.lge.vibrator_amp=120
ro.opengles.version=131072
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=2.3_r10
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-lge
ro.com.google.clientidbase.ms=android-lge
ro.com.google.clientidbase.gmm=android-lge
ro.com.google.clientidbase.yt=android-lge
ro.com.google.clientidbase.am=android-lge
ro.com.google.clientidbase=android-lge
rild.libpath=/system/lib/lge-ril.so
ro.telephony.default_network=0
ro.sf.lcd_density=240
com.ti.omap_enhancement=true
opencore.asmd=1
ro.radio.use-ppp=yes
keyguard.no_require_sim=1
ro.config.nocheckin=yes
wifi.interface=wlan0
alsa.mixer.capture.master=Analog
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=true
dalvik.vm.heapsize=48m
dalvik.vm.dexopt-flags=m=y
jpeg.libskiahw.decoder.enable=1
jpeg.libskiahw.decoder.thresh=100000
net.dns1=208.67.222.222
net.dns2=208.67.220.220
ro.tether.denied=false
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
If you make a unrooted version of another version, just change the "V20s" to "V20(letter version)" and think thats all, can contains more differences but will not influence the warranty.

Duarte777 said:
I think thats good .
Here you have the stock V20S build.prop if you want:
If you make a unrooted version of another version, just change the "V20s" to "V20(letter version)" and think thats all, can contains more differences but will not influence the warranty.
Click to expand...
Click to collapse
Thanks bro, but I made a fresh install, took the nandroid and it's in there already, but now I get error (status 6) while flashing... Should I upload the whole ROM, so you guys can have a look at it?
-edit- found it I think, didnt close "" around redy's name...

Thanks a bunch guys, i'm looking forward for the unrooted ROM!

Ok, here is a prerelease and wessyh0 please dont yet flash it, until someone else has confirmed, that I didnt miss anything.
It's v20o from NL, as I guess you are dutch. I flashed it to my own phone, injected cwm, made a nandroid, took META-INF folder from Echelon ROM by gabz, updater-script (modified) from tantrums, extracted the bin file, took the recovery partition and added it to the repack and updater-script.
Here it is: http://d-h.st/1RM
Please anyone check, if I missed anything, or if it's fine for unrooting purpose.
Note you ll lose CWM & root, so you ll have to flash with smartflash again, if you want to regain root.
If anyone confirms, have fun with it
Dont forget to do a factory reset, cache wipe, dalvik wipe, format your sd card/take it out and remove all other kind of trace, that might tell them, that your phone has been rooted once
Plus I want a donation from you then
Consisting of:
Push the thanks button.
A big thanks.
And a kiss

N00BY0815 said:
Ok, here is a prerelease and wessyh0 please dont yet flash it, until someone else has confirmed, that I didnt miss anything.
It's v20o from NL, as I guess you are dutch. I flashed it to my own phone, injected cwm, made a nandroid, took META-INF folder from Echelon ROM by gabz, updater-script (modified) from tantrums, extracted the bin file, took the recovery partition and added it to the repack and updater-script.
Here it is: http://d-h.st/1RM
Please anyone check, if I missed anything, or if it's fine for unrooting purpose.
Note you ll lose CWM & root, so you ll have to flash with smartflash again, if you want to regain root.
If anyone confirms, have fun with it
Dont forget to do a factory reset, cache wipe, dalvik wipe, format your sd card/take it out and remove all other kind of trace, that might tell them, that your phone has been rooted once
Plus I want a donation from you then
Consisting of:
Push the thanks button.
A big thanks.
And a kiss
Click to expand...
Click to collapse
I think that is better to creat another thread here on general or in dev section, a sticky thread.

N00BY0815 said:
Ok, here is a prerelease and wessyh0 please dont yet flash it, until someone else has confirmed, that I didnt miss anything.
It's v20o from NL, as I guess you are dutch. I flashed it to my own phone, injected cwm, made a nandroid, took META-INF folder from Echelon ROM by gabz, updater-script (modified) from tantrums, extracted the bin file, took the recovery partition and added it to the repack and updater-script.
Here it is: http://d-h.st/1RM
Please anyone check, if I missed anything, or if it's fine for unrooting purpose.
Note you ll lose CWM & root, so you ll have to flash with smartflash again, if you want to regain root.
If anyone confirms, have fun with it
Dont forget to do a factory reset, cache wipe, dalvik wipe, format your sd card/take it out and remove all other kind of trace, that might tell them, that your phone has been rooted once
Plus I want a donation from you then
Consisting of:
Push the thanks button.
A big thanks.
And a kiss
Click to expand...
Click to collapse
Thanks alot man! I'll wait for it to be confirmed, but for now you are my hero! And yes, im dutch :good:
If it's confirmed will you please tell me instructions how to use it? Thanks in advance

wessyh0 said:
Thanks alot man! I'll wait for it to be confirmed, but for now you are my hero! And yes, im dutch :good:
If it's confirmed will you please tell me instructions how to use it? Thanks in advance
Click to expand...
Click to collapse
Boot to recovery, wipe data/factory reset, wipe cache, wipe dalvik. Remove sd card or format it, flash the ROM, reboot, maybe do a factory reset from within the ROM and bring it to LG service. That's all, or did I miss anything?

Duarte777 said:
I think that is better to creat another thread here on general or in dev section, a sticky thread.
Click to expand...
Click to collapse
Well we can, or I mention it in my noob how to. Dont think it's worth a sticky though, but as always CMIIW, you can also create one, if you want to and maybe add some more ROMs (like 1 for europe, asia, ...)

N00BY0815 said:
Well we can, or I mention it in my noob how to. Dont think it's worth a sticky though, but as always CMIIW, you can also create one, if you want to and maybe add some more ROMs (like 1 for europe, asia, ...)
Click to expand...
Click to collapse
Nop bro, i just giving one ideia, i think that if you add to your noob how to its enough.

N00BY0815 said:
Boot to recovery, wipe data/factory reset, wipe cache, wipe dalvik. Remove sd card or format it, flash the ROM, reboot, maybe do a factory reset from within the ROM and bring it to LG service. That's all, or did I miss anything?
Click to expand...
Click to collapse
In my view you missed the fact that you have CWM instead of the stock recovery. As last step, to those listed by you, you should flash the stock recovery from CWM.

danfizesan said:
In my view you missed the fact that you have CWM instead of the stock recovery. As last step, to those listed by you, you should flash the stock recovery from CWM.
Click to expand...
Click to collapse
Stock recovery is in the flashable zip... I am already an advanced noob
Sent from my LG-P970 using xda app-developers app

N00BY0815 said:
Stock recovery is in the flashable zip... I am already an advanced noob
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Great, wanna share it ?

danfizesan said:
Great, wanna share it ?
Click to expand...
Click to collapse
How about reading the whole thread? Only 2 pages till now and then you'll also find the link and see, that I am still waiting for an approval by the Pro's here

Can anyone please approve it? I want to bring it to the service center.

wessyh0 said:
Can anyone please approve it? I want to bring it to the service center.
Click to expand...
Click to collapse
I ll make a new version later, cause redy told me, that I forgot 2 format commands in updater-script + mount as ext3. But dont worry, then you should be just fine

[MOD] [P6800] DXMD3 Stock Jelly Bean Phabletized! [HELP WANTED - SCRIPTING PROBLEMS]

DXMD3 Stock Jelly Bean Phabletized!​
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...

Screenshots:
They're big. There are many, Unhide to see.
Mostly just showing off the Samsung apps. From my experience, most apps are a lot easier to handle on a bigger dpi. Again, if on some apps you don't like the change...go with Xposed framework.
Undoubtedly you'll notice how the fonts in the Settings app seem smaller than the rest of the rom and the alarm clock app seems bigger. You're right. They are. That's Xposed + App settings hard at work. I want the alarm clock buttons big when I'm smacking the **** out of my tab in the morning (300dpi) and don't need the big fonts when I'm fiddling with the settings (160dpi).
By the way, don't mind the "25% brightness" (I had it at -28% on some other screenshot). That's just Lux. It helps keep the display at a comfortable level in the dark. A screen filter basically. I also found this and this very helpful on a big screen and fiddly-sometimes-hard-to-press-when-your-hands-are-messy-when-cooking-and-just-need-to-look-at-the-recipe-one-more-time buttons (the other two persistent notifications).
Coming soon: Flashable zip. I'll get around to it, I promise. Having trouble scripting the thing. Take a look at the help wanted section if you think you can help. Thanks.

It is wonderful seeing someone try to create something for our Tablets...
I wish I could help in your efforts but instead I can only thank and applause you...
Good luck...

actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7

Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app

Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app

zip
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.

edan1979 said:
actually... e-robot doing the same thing that you're doing... replacing the apk from note 8.0 to 7.7 but they did alter some apk to fit their mod.
btw. you can use the keyboard from e-robot as well. but you need to find all related lib files to make it work on 7.7
Click to expand...
Click to collapse
Doesn't e-robot have some issues? I got the distinct feeling it wasn't quite so stock. I might be wrong though.
EDIT: Now I remember! I couldn't get over the flickering wifi icon in the status bar. Annoyed the **** out of me. Trivial, I know. I could live with something not working quite right if it wasn't visible most of the time.
{Diemex} said:
Conserning cwm flashable zips... I don't know the syntax either. But I just use a zip from gapps and delete all the contents and modify the outputted text. Don't use a zip from a rom because they often wipe stuff.
Sent from my GT-p6800 using xda app-developers app
Click to expand...
Click to collapse
Good tip. Thanks!
vivalamoza said:
Lemme start by giving you a well deserved thanks and excellent job.
Can you maybe post a few screenshots and maybe even a video of you have time?
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
I'll take some and post asap.
konsolen said:
You can use the app "app2zip". It shows you all installed apps, then you choose yours from your pack and
click create. This zip file is then flashable in the recovery.
Click to expand...
Click to collapse
Can this create a single zip for multiple apps or is it one app = one zip?

It creates one ZIP file. So exactly what you looking for.

Just a quick update:
I'm working on a cwm flashable zip that would back up the original apk and odex files and copy the new ones in place. Plus, I've been toying around with other versions of system apps.
I will be posting everything in the next few days - after I test it out.
Cheers

paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!​
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) Restart
13) If you have any issues with any of the apps, first try clearing their caches and data.
Click to expand...
Click to collapse
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.

obeguin said:
Concerning the point 7 & 8, wouldnt it be easier to just use LCDDensity for root ?
Using it, it is must more easy to change the density without even having to manually modify the build.prop file... And the phablet mod start for any density higher than 180..
And for people who forgot to install a second launcher, they no need to panic..
They can still go to the tablet settings using the notification bar, even if Touchwiz doesnt work.
There, they can check they are connected to internet and install a second launcher by logging on google play by using a PC.
Click to expand...
Click to collapse
Never heard of LCDDensity before, but I'll add it to the instructions.
You're correct, the phablet ui starts at 180 (176 I believe), but the navigation bar keys are off center when lcd density is not set to 213.
Sort of defeats the purpose of phablet ui for me. Personally, I changed to a smaller dpi (for a smaller status bar - 195) and removed the navigation bar with the qemu.hw.mainkeys switch. I mainly navigate thru gestures (using GMD Gesture Control) anyway.
Again, you're correct. But when starting out on a freshly flashed rom, some might happen to skip the part where they connect to the wifi or connect their google account. Besides, I've seen Play being hesitant to install and update on it's own - sometimes it requires you to launch it before you get update notifications and automated app downloads which requires a launcher. I want the instructions to be as foolproof as possible. That's why I'll be making a separate flashable zip with a custom home and keyboard, just in case.
On that topic, do you know anything about scripting? I'm having trouble with the update script. Check out the first post.

You can try this note 8 samsung keyboard, it work on both tablet and phablet ui.
http://forum.xda-developers.com/showthread.php?t=2228836
Sent from my GT-P6800 using XDA Premium 4 mobile app

paranoiadk said:
DXMD3 Stock Jelly Bean Phabletized!​
DISCLAIMER TIME:
First thing's first: I am not a chef, nor am I a developer of any sort. This was just an experiment and it worked. All I'm doing is sharing the results and the method of achieving them.
Also, I am in no way responsible if you mess up your device. That said, these modifications are mostly harmless and reversible, if you follow the instructions to the letter. (Worst case scenario: You flash stock JB again or restore a nand backup and you're safe.)
Oh and your device must be rooted. You can't go around changing things if it's not.
I do need a bit of help with some things, you can read the help wanted section at the bottom of the post,
If you're still interested, read on.
INTRO SPEECH:
I've always wanted the phablet experience on my 7.7, but all of the roms I've tried had imperfections (if ever so slight). If any developers are reading this, please do not take this as an insult. Your roms are wonderful masterpieces. I admit I couldn't even begin to understand how much knowledge and hard work is poured into them. I just wanted a 100% daily driver to have and to hold, meaning as few updates as possible (oh the irony). The closest I could find to a perfect rom was the PAC rom by @daniel_hk, but it always started acting out after a couple of weeks. Might have also been my apps or a combination of apps that did this, I don't know. The customization options on PAC are… It's simply amazing. If you're up for it, do check it out in the development thread. Out of all the roms I've tried, I liked PAC the best. That was a message from our (non)sponsors (my personal opinion). Then I tried E-Robot, which is almost stock – I'd say it's a Note 8 rom modified for our 7.7. But it still didn't feel right. I went back to the stock JB rom and started thinking I could simply alter build.prop's dpi setting and get phablet on stock JB. I was half-right. I did alter it and got phablet mode, but a lot of apps stopped working, a few of them crucial (phone, contacts, …). So I started replacing those apps with apps from the E-Robot rom. And it worked. I've identified and replaced most of the apps and the rom is very smooth. I dare say it's even smoother than E-Robot.
List of apps that need replacing:
- Accuweather
- Most mini apps
- Pen memo
- Camera
- Gallery
- Calculator
- S Planner / Calendar
- Phone
- Contacts
- TouchWiz Launcher
- Task manager
- Memo (text memo)
List of apps I haven't yet found replacements for (HELP WANTED, see below):
- Samsung keyboard
- Reader's hub
APPS YOU'LL NEED:
I like ES File Explorer the most, you can use other file managers if you like. LINK
I find it easiest to flash roms with Mobile ODIN. LINK
If you're not interested in purchasing Mobile Odin, you can look it up on XDA forums. It's available for free.
7zip. You'll need to unzip the package. LINK
APP SUBSTITUTION PACKAGE:
LINK
Please, do not mirror this as these instructions are not yet 100% complete.
INSTRUCTIONS:
Read first. Then apply.
1) Get the stock DXMD3 Jelly Bean on www.samfirmware.com
2) I can't stress this enough: Back up all of your files on your internal storage. All of them. I will not be blamed for the loss your lolcat collection.
3) Flash it with Mobile Odin and choose to root the rom and inject superuser
4) A custom recovery is probably a good idea. Use either CWM or TWRP and make a full system backup. Just in case. Easiest to flash with Odin.
5) Unzip the "PHABLETIZE!" package to your tablet internal storage.
6) Default home to a custom launcher. Just in case. I used Apex. (You'll be replacing TouchWiz, remember?) Also, Install a custom keyboard. The stock keyboard isn't happy with 213dpi. I use Jelly Bean Keyboard.
7) Turn on "Root Explorer" mode in ES File Explorer (side menu, accessible from the top left bluish globe icon)
7a) Alternatively, you can use LCDDensity from Play. I haven't tested this personally. This is a recommendation from obbeguin. Skip step 8.
8) Make a backup of your build.prop file. Edit the build.prop to be used by the system (/system/build.prop): "ro.sf.lcd_density=160" changed to "ro.sf.lcd_density=213" (the one between rild.libargs and ro.lcd_brightness)
9) Restart and marvel at the half-finished glory of phablet mode.
10) Here is where you would see TouchWiz crash and you'd be stuck if you hadn't defaulted to a custom launcher in step 6. Luckily, you did.
11) Open ES, navigate to /system/app/ and start replacing the apps from the package. Yes, manually. I don't know how to make a CWM flashable package, so again, yes, manually. (HELP WANTED) I'd also recommend backing up the original files (just copy them to a backup folder on your storage). All apps should replace just fine, since they crash when launched anyway. You should also backup and delete their odex counterparts. Do not replace those.
12) I haven't included the camera and gallery apks. The gallery wasn't working well and I found a replacement here. Not sure yet if I can hijack his files to use in my zip so I'm posting a link for the time being. Also, I've found I like the SGS4 dialer and messaging app much better than the tablet apps from Note8. Look for it here.
13) Restart
14) If you have any issues with any of the apps, first try clearing their caches and data or wiping dalvik cache and cache in recovery mode.
I'd also recommend SkyHigh's custom kernel. I like it and it allows me to use ExFat on my external SD card. It's no NTFS, but large files (>4GB) get across just fine and it works on my computer and in my tablet without a hitch.
And for that extra "Startled Android" effect, I went with Xposed framework and per-app dpi settings. Not quite paranoid but does the job ok.
If you like the Samsung keyboard, you might want to give this one a go. Suggested by @stenny
HELP WANTED SECTION:
As written before, I need some help. It would be tons easier to just flash a CWM package over the stock JB and get phablet mode. Trouble is, I can't build it. Getting around to this one. Got around to it. Now I'm having scripting problems. If anyone is script savvy, please check out the code below.
I have no clue where to find a replacement Reader's hub app – one that works on 213dpi instead of 160dpi If anyone knows where I could find it, please leave a comment.
Don't hesitate to leave your feedback in the comments.
Unhide to see the script code.
#!/sbin/sh
# remove old backup
[ -d /sdcard/phabletize/backup ] && rm -r /sdcard/phabletize/backup
# backing up original apk
echo "Backing up /system/app/"
busybox mkdir -p /sdcard/phabletize/backup/system/app
busybox mkdir -p /sdcard/phabletize/system/app
cd /sdcard/phabletize/list/
for f in $(ls)
do
echo "Processing $f"
busybox cp /system/app/$f /sdcard/phabletize/backup/system/app/
busybox rm /system/app/$f
done
echo "Backups done for system apps"
# backing up original build.prop
echo "Backing up /system/build.prop"
cp /system/build.prop /sdcard/phabletize/backup/system/build.prop
echo "Backup done for build.prop"
# delete odex files and old apk files
echo "Deleting original odex and apk files from /system/app"
cd /sdcard/phabletize/list
for f in $(ls)
do
echo "Processing $f"
busybox rm /system/app/$f
done
echo "Original odex and apk files deleted. Don't worry. You still have your backup."
# for each of the system apps needing processed
echo "Copying modified apks to /system/app"
cd /sdcard/phabletize/system/app
cp -p * /system/app
echo "Finished copying modified apks"
# copy modified build.prop
echo "Copying modified build.prop to /system"
cd /sdcard/phabletize/system
cp -p build.prop /system
echo "Finished copying modified build.prop"
# the end
echo "All done. Enjoy you Phabletized 7.7 JB"
The above left my tablet in a bootloop stuck on the bootanimation turned landscape and distorted/stretched. I was trying to accomplish the following: back up the original apks and build.prop file to a folder on the sdcard. The list of apks needing backups would be determined from the list of apks in the replacement folder. And copying the replacement apks and build.prop file to the proper folder in /system.
I hope I've proofread this enough times so that it's decent...
Click to expand...
Click to collapse
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed

vivalamoza said:
Didn't work for me, lots of apps couldn't be pasted in system/app even after R/W, I even tried to do it in TWRP and it still failed
Click to expand...
Click to collapse
My suggestions:
You sure you're rooted?
You might have free space issues. Try disabling and uninstalling the apps from titanium backup and then pasting the apps in place. Samsung roms are pretty huge and fill the available space almost to the limit.
Pasting sometimes didn't work for me when the apps were running. Try closing them from a task manager. I always did the modding after a fresh boot on a fresh rom.
I hope this is helpful.

Easier WiFi Tether Hack (No SQL Edits + Survives Factory Resets)

** Designed for stock Moto 98.72.22 and 98.72.22-based ROMs **
** FOR OTHER ROMS and updated stock, see post #7 **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default = same end result as SQL hack.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
0. Backup just in case!!
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!

tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.

Ismokel said:
tried this on stock jb.no go. fc and started reading notifications. also constant network loss and re-aquire.
Click to expand...
Click to collapse
JB 246 98.72.22? I'm assuming you used a root explorer due to the FC. I recommend using Safestrap's built-in file manager (see the updated instructions).
I could also make a flashable ZIP to mitigate user-error if there is demand for it.
The last issues you mentioned are unrelated to this. The modified APK is exactly the same as the original, except for a single byte (1 -> 0) and deodexed. Oh, and a "false" to "true" in the manifest so we could manually clear data, but that didn't work out. You can decompile and compare yourself

Same issue here as Ismokel. It might be a signing issue, as I saw the same thing occur when I tried doing the mod myself and was experimenting with the different options for signing. It worked for me when I left the existing signature.
I would post my modded version, but I need to make one with only that mod first, as mine has mods to change other defaults as well.
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
You mentioned that yours worked for you without wiping data. Did you change default_entitlement_check in the xml resources or did you change something else? I was only interested in this mod to change the default and not the existing setting, but I'm still somewhat curious.

progrockguy said:
** Designed for stock Moto 246 (JB 4.1.2) and 246-stock-based ROMs **
When you do the entitlement_check SQL hack, you are modifying a string provided by MotorolaSettingsProvider.apk. But anytime you do a factory reset, you have to repeat the SQL hack. I didn't like this, so I modified the system APK to disable entitlement by default.
I have tested this twice without issue, so I'd say it's ready for release. Of course you need to be rooted to modify /system/app.
I did the following with Safestrap file manager and upon rebooting (no need to wipe, it seems) the Mobile Hotspot launcher worked like a charm
Also did a factory reset (data, dalvik, cache) and tethering still worked just fine!
Instructions:
1. Download attached MotorolaSettingsProvider.apk
2. Reboot into Safestrap, Mount System, and then open the File Manager (under Advanced)
3. Browse to /system/app and rename MotorolaSettingsProvider.apk to *.apk.BAK (keep as a backup)
4. Browse back to the downloaded file, click it, select Move, browse to /system/app, click Select, OK
5. Browse again to /system/app, click on MotorolaSettingsProvider.apk (NOT the one ending in .BAK)
6. CHMOD permissions as 0644 (rw r- r-)
7. Rename MotorolaSettingsProvider.odex to *.odex.BAK (backup)
8. Reboot, click Thanks, and enjoy!
Click to expand...
Click to collapse
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.

dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.

ShadyDreamer said:
Also, what is this JB 246 you are referring to? Wrong number? Just from a quick search, the only 246 reference I found was ICS.
Click to expand...
Click to collapse
Whoops!! 98.72.22 is the base I used. If you took OTA updates, that could explain the boot loops. See below on how to DIY
dpcsar said:
I would like to know how you made the modifications to the apk. I would like to make the same modifications for my Atrix HD.
Click to expand...
Click to collapse
Brolzy said:
has anyone tried this with SlimKat? It's the one thing that's missing from it that I've wanted so far.
Click to expand...
Click to collapse
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
My safestrap instructions will work on your newly modified APK. (If you're going to try replacing via root file explorers, I suggest an overwriting Paste. That way you'll keep permissions in case android crashes and hot reboots. Do not delete, *then* paste. It'll likely crash before you can set the permissions.)
Good luck!

progrockguy said:
This mod is easy and should work on all ROMs. All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM.
Steps: after decompiling, open the following text file:
res/values/integers.xml
look for: def_entitlement_check
Change the 1 to a 0 and save.
Recompile and KEEP EXISTING SIGNATURE.
Click to expand...
Click to collapse
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
If you are using adb from a computer connected by USB to copy and install the apk, after using su you can use the stop command to close all apps, then you can safely move, rename, replace, or delete system apps without it crashing and rebooting. Just make sure you have it in the proper state before you reboot. If a prompt to allow su from adb comes up on the phone, be sure to allow it with no time limit in case you need to use su again before you use adb reboot to restart the phone.

ShadyDreamer said:
That's exactly what I did, so I don't know why your file didn't work for me. I'm using 98.72.22, too. A while ago when I did that exact mod myself it worked fine.
Click to expand...
Click to collapse
Curious, where did you get your APK from? Because stock is odexed.
My file also had a manifest edit (which didn't work out), but I doubt that's the issue since it works on two of my Bionics.

When I quoted the part I was replying to, I included your "All you need is a deodexed version of MotorolaSettingsProvider.apk from your current/desired ROM." line in the quote for a reason. I did that part.