Database Develop

[MOD/HOW-TO] Remove hard key vibes via android.policy.jar

I thought I'd offer my solution to disabling the hard key vibrations on the Atrix since other people might find this useful. This method differs from the other solutions in that it doesn't tamper with your Silent Mode vibrations (like StreakVibrations does) and it's code based, so it shouldn't tamper with any themes you have installed (like the framework-res.apk method). It is firmware dependent though since it's a code modification.
You'll need an android.policy.jar modified for your firmware.
What I'm doing is I'm modifying the method called performHapticFeedbackLw, and telling it to skip triggering the vibrate pattern for all effects (there are 5) except for keyboard taps. Long press vibe, virtual key vibe, safe mode disabled vibe, and safe mode enabled vibe will no longer trigger... Incidentally, does anyone know what safe mode on this phone refers to?
To use the file, you need to be on Bell, Telstra, GingerBlur, Gladiatrix or stock ATT 1.8.3 firmware, and be deodexed. Can you copy the file to your phone without being deodexed? I don't know. I'm a programmer, but an Android newbie so just to be safe it's best if you're deodexed.
Before you try anything, obviously make sure you are backed up. At least copy your existing android.policy.jar so that you can restore it if necessary.
All you need to do is either:
a) Run the novibes.bat script packaged in the zip. There are a couple prerequisites:
1. Make sure to set your USB connection to "None" on your phone.
2. On your phone, go to Settings > Applications > Development and make sure USB debugging is turned on.
3. Plug your phone into your PC and let it install any necessary drivers.
4. Then you can run novibes.bat.
or
b) Follow the steps outlined below to do it manually:
1. Replace /system/framework/android.policy.jar with the one that I've attached.
2. Make sure the permissions of the file are set to rw-r--r-- (thanks for reminding me, Meloy and for correcting, natboy!). The easiest way is to use Root Explorer, long press the file, choose permissions, and set owner: read/write, group:read, others:read. Otherwise, use Terminal and type "chmod 644 /system/framework/android.policy.jar" without the quotations.
3. Reboot.
For those not on stock Bell, I'd be willing to modify your android.policy.jar and post it here if you provide somewhere for me to download it, and specify what firmware it comes from. It's quite quick to do once you're set up so I don't mind. Alternatively, make the change yourself:
1. Download baksmali and smali (both .jars and scripts, total 4 files).
2. Copy /system/framework/ from your phone to your computer.
3. Copy all the files from step 1 to the framework directory from step 2 on your computer.
4. Unzip android.policy.jar and copy its classes.dex file to the framework directory on your computer.
5. From the command line, navigate to the framework directory and run "./baksmali classes.dex". It will create a directory named "out".
6. Open "out/com/android/internal/policy/impl/PhoneWindowManager.smali" in a text editor.
7. Search for a method called "performHapticFeedbackLw". Go to near the bottom of that method, and you will see the Dalvik bytecode representation of a switch statement:
Code:
.sparse-switch
0x0 -> :sswitch_27 #This is for long press vibe
0x1 -> :sswitch_35 #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :sswitch_3b #This is for safemode disabled vibe
0x2711 -> :sswitch_3e #This is for safemode enabled vibe
.end sparse-switch
8. Here's an example of how you might want it to change. Basically you want to replace the original goto labels with one that causes the method to step out without triggering a vibe, and that notifies the calling method there was no vibe by returning false. The label to use is called ":cond_1d":
Code:
.sparse-switch
0x0 -> :cond_1d #This is for long press vibe
0x1 -> :cond_1d #This is for virtual key vibe
0x3 -> :sswitch_38 #This is for keyboard tap vibe
0x2710 -> :cond_1d #This is for safemode disabled vibe
0x2711 -> :cond_1d #This is for safemode enabled vibe
.end sparse-switch
9. From the command line in the framework directory, run "./smali -o classes.dex out". You now have a new classes.dex that has your modification.
10. Zip up the classes.dex with the META-INF directory from your original android.policy.jar. Rename the zip to android.policy.jar.
11. Copy the new file to your phone and reboot.
12. At this point you should be done.

Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App

n1ckr0th said:
Will this be possible on the AT&T atrix? I currently use the streak vibe method but I'd like this much better.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.

bearsfan172 said:
http://forum.xda-developers.com/showthread.php?t=1079873&page=3
Check out that thread over in general. The info for how to edit framework.res is there, but there is a flashable .zip that will disable the vibrations in either stock/rooted 1.83 or Gingerblur 3.5 for you.
Click to expand...
Click to collapse
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.

n1ckr0th said:
thank you, but i wonder if this specific method is possible on the atrix as to retain themes and such.
interesting that its in general, development may be a better home for it.
Click to expand...
Click to collapse
Yes, this would work perfectly fine on ATT. You can either follow the instructions I provided, or if you like you can post /system/framework/android.policy.jar from your phone somewhere and pm me the link so I can download it and I'll do it for you. Also mention what firmware you're on. I just don't want to download hundreds of MB of firmwares which is why I didn't set one up for all the ATT firmwares.
That other method requires editing a file that is guaranteed to change with any theme you install. That means anytime you change themes you'll need to edit that .apk yourself, or wait for someone to bring the change over. android.policy.jar is unlikely to change for themes.

Ok, I've posted a version for ATT 1.8.3 that was given to me by n1ckr0th.
n1ckr0th, let me know whether it works fine or not. There should be no problem, it looked just like the other 2 versions I modified.
Incidentally, he's using GingerBlur 3.5 so anyone on stock be careful (ie. copy your original file to somewhere else on your phone). It shouldn't matter at all because from what I see, there aren't any resources to modify in android.policy.jar so GingerBlur's should be the same as stock. At any rate, it won't brick your phone if you put the wrong one on. I put Telstra's on my phone by accident and it just messed up the the graphics on screen (maybe because the addresses were all wrong for my phone). You can still use adb, or sshdroid to copy and replace with your original android.policy.jar.

please delete

meloy said:
Don't use this on AT&T 1.83!
After the replace and reboot my phone was really laggy and some applications doesn't start anymore (camera, contacs for example). After i have replaced it with the original file i have still the same problem.
My phone config:
- SBF 1.83
- rooted (GingerBreak 1.20)
- sideloading enabled (GladEnabler)
- GladiAtrix 3 b0.2 ROM
- LauncherPRO
- GingerBread Theme only
Click to expand...
Click to collapse
What? That can't be right, if you still have the same problem after copying the original file, that means that you must have done something wrong. It's a single file change, provided you returned the file to the original, it will be back to the way it was. How did you copy the file? And also, are you deodexed? As mentioned in the original post, you have to be deodexed, because I don't know the results of using it on a non-deodexed system. Your posted config makes it sound like you might not be.

Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.

meloy said:
Sorry, my mistake. It is deodexed, I have just forgot to set the permissions to rw-r-r, you should maybe mention this in your start post. It's all working fine now. Thanks for the good work.
By the way, your mod (android.policy.att_1.8.3.zip) has added an "reboot" function to my phone, it is working well too.
Click to expand...
Click to collapse
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?

maledyris said:
Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.

meloy said:
When i go to the phone options i have now these selection:
- Silent Mode
- Airplane Mode
- Power off
- Reboot
Yes, i think it is a GingerBlur mod. But it doesn't bother me, it is a good feature.
Click to expand...
Click to collapse
Interesting, that never occurred to me. I usually go into terminal and type in reboot to reboot my phone. I think I'll add that to my phone too...

maledyris said:
Haha, that's good. Had me scared for a moment, I didn't want to break anyone's phone!
Thanks for the tip, I'll mention that in the original post. Oh, and what do you mean by the reboot function...? Where did you access that? I certainly didn't add it, so it might be a mod added to GingerBlur?
Click to expand...
Click to collapse
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.

n1ckr0th said:
the reboot function is cooked into GingerBlur. for some reason my phone wouldnt boot after i replaced the file? i used root explorer and set the permissions to whats specified.
Click to expand...
Click to collapse
Hmm, how far does it get? Do you at least get to the boot animation? I notice that it may sit at the boot animation for a really long time after changing a file sometimes. Probably updating the cache or something. It's odd that it wouldn't work for you considering it's your file and it worked for meloy. How did you copy the file over?
If you try again, delete the original file, so you can be sure it's no longer there, then try the copy again.

I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?

I have no problems with this mod. It works all fine.

Been waiting on this mod. Streakvibrations has me missing my notification vibes. Thank you

It gave me a red light on boot, stuck at Motorola logo for infinity. I booted into recovery and reflashed gb 3.5 to fix it. Ill try your idea of deleting it then moving the new one.
Sent from my MB860 using XDA App
EDIT: still didnt boot, had to flash again..

I'm getting the flashing red light and rebooting as well. I can't get into CWM though, going to have to flash a SBF. Only think I can think of is maybe the Dalvik cache needs to be wiped before rebooting?
Edit: I'm on an AT&T phone and used GB to deodex as well.. maybe it's not catching all the files..

lurchbyrep said:
I'm on AT&T 1.8.3. I followed instructions just as in OP (yes, including the proper setting of permissions), but I soon found a significant problem. Everytime I held down my power button in order to invoke the power options menu, instead of the menu popping up, my phone just freaked out (the screen quickly FADED to black and the phone rebooted). I did this about four times, and each time it happened exactly the same. So I brought back the original framework file, and now everything works fine.
Any ideas?
Click to expand...
Click to collapse
Are you on stock 1.83? Now that we know that android.policy.jar has some mods built into it for Gingerblur pseudo rom, the att 1.83 file I posted probably isn't ideal for stock users.
If you're on stock, maybe you could post your android.policy.jar somewhere and pm me the link to download. Then I could put together a pure stock att one when I get home.
Sent from my MB860 using XDA App

Avstralia Deodex Mod by ZaYAC for XT907

Australia Deodex Mod for XT907​
Preface:
In general, I'm worn out trying to make the firmware for Recavery. Made a backup for TWRP (maybe go for CWM). I'll try later to collect norms firmware for Instal in Recavery.
All at your own risk. I am not responsible. Checked up on my device.
Original theme by Russian 4pda.ru
Features:
Android: 4.1.2
Manage your music by holding down the volume keys when the display is off.
Item added to restart the Shutdown menu.
Phone.apk app redone to work with DroidRazrWidget (who do not - that is not nothing interfere).
Menu background in many places replaced with dark gray to black (on our screen looks nice and eating less).
Battery Percentage. If you do not need - there is a patch Runoff + Patchki different species in the percentage of your choice.
Full support Init.d and BusyBox.
Memory cards are swapped with each other on the new method. Who is not necessary - just delete the file "11extsd2internalsd" in the folder "\ system \ etc \ init.d"
Remotely bit rubbish.
Improved the buil.prop to return the item "Shutter Sound" in the drain chamber.
Market the latest version in black tones and multi DPI.
Applications are updated to the latest version in the store.
Added applications Solid Explorer (by default, in Australia there was not any conductor), Droid Razr Widget(Widget to switch between CDMA and GSM), Terminal Emulator and Notification Toggle.
Full Russification dialer and a strip search in contacts. You can put the patch to return to the English localization of the phone and contacts.
Installation:
Unpack the archive into a folder on the memory card to a folder backup TWRP (I \ TWRP \ BACKUPS \ 9912345679077 \). It turns \ TWRP \ BACKUPS \ 9912345679077 \ Avst_ZaYAC_MOD. And it four files.
We go into TWRP Recowery.
Do Wipe Data, Cache (Factory Reset) and Davlik Cache.
We go in and choose Restore Avst_ZaYAC_MOD
Put a check mark in the "System" and "Boot" and swipe to recover.
Fix Put Batteries. Recovery / Install.
Reboot and done.
Download:
Backup "Avst_ZaYAC_MOD"
Fix battery: http://forum.xda-developers.com/attachment.php?attachmentid=1902860&stc=1&d=1366652172
Original battery(no %) for those who need to:http://forum.xda-developers.com/attachment.php?attachmentid=1902873&stc=1&d=1366652226
Patch cleaning soft keys(For those who are using LMT Launcher):http://forum.xda-developers.com/attachment.php?attachmentid=1902891&stc=1&d=1366652505
English dialer and search contacts: http://forum.xda-developers.com/attachment.php?attachmentid=1902919&stc=1&d=1366652851
For reference:
In the Notification Togglemozhno adjust double-click to enter the Wi-Fi settings, and more.
To work Intertelekoma (CDMA NV Only) use of radio 4.0.4 XT907 (Veryzone). Do not need to edit the registry. Network settings is switching to NV Only.
Fashion battery as original battery put through Instal in Recovery. If not deliver patch battery will Percentage but step "100", then "85" and so on as stock.
Patchka loops of soft Clavey via Istall in Recovery. Do not forget to first install LMT Launcher.
Screenshots:

Various modes of batteries in the "%" for this mod​
Mod 47
Mod 77
Mod 84
Mod 90
Mod 125
Mod 147
Mod 148
Mod 150
Mod 151
Thank you, furniel, for providing images. His collection of animations batteries here.

I just got my RAZR M so this is great! Good so see that this forum is actually active... For this one I will wait for a non-backup flashable zip file.
LOOKS great! thanks!

Translate this please - "Различные моды батареек в "%" для этого мода:"
Somebody can`t understand this! )
P.S. Моди дійсно хороші! ))

St.Noigel said:
Translate this please - "Различные моды батареек в "%" для этого мода:"
Somebody can`t understand this! )
P.S. Моди дійсно хороші! ))
Click to expand...
Click to collapse
"Various modes of batteries in the "%" for this mod"
and your PS is "Fashion is really good!" if you needed that translated also.

Is this for the XT907 or XT905? Subject says XT907 but the screen shots look a hell of a lot like Aussie XT905.

pjcons said:
Is this for the XT907 or XT905? Subject says XT907 but the screen shots look a hell of a lot like Aussie XT905.
Click to expand...
Click to collapse
It works nice in XT907.

How do you get the word in the top left corner to say life... and how did u get it there
Sent from my Xoom using xda app-developers app

UpDate: http://forum.xda-developers.com/showpost.php?p=44946498&postcount=17
The following can still be useful.
AS I deal with this ROM: I have had some problems with the SD swap. I have learned to never let CWMR protect custom recovery for this particular rom by choosing yes on reboot. It zeros out the permissions for install-recovery.sh and the Avsi rom needs that script for the swap.
I think TWRP changes the same to ...bak and you have no choice & this behavior depends on your version.
USE CWMR AND ALWAYS CHOOSE ANY NO ON REBOOT.
Thanks for the "Recavery". I wish there were more of these and Devs were not so offended (?) by this technique.
ZaYAC-ua, I am willing to believe, should not mind some loving care applied to this TWRP Recavery based ROM.
Note here a bootup of the bare system with google login etc... I could never get to work for phone and 4g service. So all my talk here is about a simple work around for Vzw users.
Edit fixed! http://forum.xda-developers.com/showpost.php?p=44946498&postcount=17
All the following is just a method to activate the rom on Vzw.
In my case it was DeadCalm http://www.droidrzr.com/index.php/topic/17778-romretail-deadcalm-v14-7172013-412-base/
But other deodexed stock bases should work:
http://droid-hive.com/index.php?/topic/1768-fxz-412-98161-dst/ DST remix
http://forum.xda-developers.com/showthread.php?t=2307254 CleanROM
http://www.droidrzr.com/index.php/t...unofficial-dst-wmods-unlocked-bootlader-only/ DST (not deodexed) Not sure.
New steps http://forum.xda-developers.com/showpost.php?p=44946498&postcount=17
The Telstra rom has the same radio and a newer kernel. With the DroidRazrWidget you can use it anywhere in the world. But stay away from them on Vzw.
Warning: NEVER TOUCH THE "BAND" IN THE 3 DOT MENU in phone info (*#*#4636#*#*) IT WILL BREAK YOUR BASEBAND (RADIO). The result on the M (and other phones?) is no 4G, spotty 3G and mostly 1x. The only fix is to restore w RSD or Matts util.
The The english dialer is a must for most of of us.
Edit the following will disable the task killer in the recent apps.
I really like this mod :"Center Clock, Honeycomb Battery, Menu Nav Key mod" at
http://www.droidrzr.com/index.php/topic/18798-deadrage-mods/
Use this to get readable white buttons.
https://play.google.com/store/apps/details?id=com.janis605.softkeyz
Then I found this.
http://d-h.st/users/s.dubs
This implementation of the initd SD swap is the best I have used. NO PROBLEMS if you boot w/o the external card. It works great. Like a permanent "FolderMount.apk". Just get a BIG SDcard. Basically internal SD memory is disabled (rather now used by your apps). And Storage info is skewed. The Op's swap thread http://forum.xda-developers.com/showthread.php?t=2229848
Or delete the initd mod from its folder.
More from The RU http://translate.googleusercontent.com/translate_c?depth=1&hl=en&prev=/search%3Fq%3DAustralia%2BDeodex%2BMod%2Bfor%2BXT907%26num%3D100%26newwindow%3D1%26safe%3Doff%26client%3Dfirefox-a%26hs%3DwRv%26rls%3Dorg.mozilla:en-USfficial%26channel%3Drcs&rurl=translate.google.com&sl=ru&u=http://4pda.ru/forum/index.php%3Fshowtopic%3D403669%26st%3D1120&usg=ALkJrhhUACxh-NqnZkUt0aMW2gRC1w-PFg#entry21438847
Scroll down to see the OP's post.

Nevermind see previous post.

Next post

Next post

Anyone has that color wallpaper in the screenshots? Looks amazing
Sent from my SPH-L720 using xda app-developers app

Next post

Is there anyway I can flash JUST the battery zips on a deodexed/debloated STock Rom? Without having to restore this backup?

CamoCustom said:
Is there anyway I can flash JUST the battery zips on a deodexed/debloated STock Rom? Without having to restore this backup?
Click to expand...
Click to collapse
This has one step newer kernel then our newest so who knows. Backup & try.

News
Update: I mistakenly wiped data while on Philz 6. I Booted to the start screen. I knew this would break 4g & it did. Rsd restore is the only fix. Be warned. Even after a cwmr restore, no 4g.
So I updated my restore thread to ...94.
Note here a bootup of the bare system with google login etc... I could never get to work for phone and 4g service. So all my talk here is about a simple work around for Vzw users.
The first rom you flash is just a facilitator that alters your data in a way that Telstra needs to boot on your vzw data partition.
I found a path for all unlocked stock'ers, on 98.18.78 (same as 9.8.1Q-78) OR 98.18.94, to upgrade to a newer kernel and have a built in SD swap.
Don't want to stay on this rom. Restore your former system & boot of any of the previous ones & keep your current data! That is right do not wipe data coming or going!
Note here: Many think this is somehow a less than a Real Rom. http://forum.xda-developers.com/showpost.php?p=40584507&postcount=3 (I am not picking on him)
Yet NOBODY HAS EVER FLASHED A XT905 PARTITION TO A XT907 WITHOUT A BRICK BEING FORMED!
So the Restore-a-Backup Rom method brings us what NOBODY has done before.
Start on the newest ...94 or the one before ...78.
Start with your activated & rooted (vzw) stock (unlocked bootloader only)
Make sure you have booted up done google login & used the stock messaging.
Go CWMR. (see goodies for flashables)
Backup!
Wipe Cache & Dalvik
Mount system (& keep data- do not wipe data)
Flash (install) http://d-h.st/users/Moparman371/?fld_id=23066#files
Reboot system
Go cwmr
Wipe Cache & Dalvik
Flash/install the Avst_ZaYAC_MODsmXBIN.cwmr.zip from next post.
Flash the Op's options: english dialer fix & battery fix & as you desire....
Reboot
TWRP will not install the Avst_ZaYAC_MODsmXBIN.cwmr.zip.
twrp v2.6+: will not messed w/ the install-recovery.sh.
cwmr: always choose NO about protect recovery flash.
Never protect recovery on reboot except when on our official rom-yes.
DO NOT try activate this system with Google login as you would a normal Rom.
It must be activated via your currently activated data partition.
Vzw users: You will never be able to do a privacy > factory data reset OR a recovery data wipe on this rom. Doing so & then rebooting will bork your radio partition OR result is 3g only, but this thread:
http://forum.xda-developers.com/showthread.php?t=2391641
is the fix if you do.
The Razr data widget when on vzw is not needed & untested by me..
The stock mms/sms can sometimes get borked on vzw just use Handsent.

I am back on this as I still find it superior to even 98.30.1 for many things but Bluetooth in particular- connectivity & audio volume.
Update: Avsitralia.Xposed.mod2 coming. Lenovo cam & gallery up. Use only as a data app, will bomb if a sys app.
Flashing Moparmans...98.16.3 on top of 98.18.94 Data works!!!!!!!!!!!!!!!!!!
Go back one post for VZW users: keep your data + install/upgrade.
I have updated the Op's restore "rom". As it was, it's xbin would result in a 447 mb larger backup file when you made your first backup. 584 mb vs 137 mb. Edit, I did previously get a much larger BU file but not with the newer Philz .
I just deleted all of xbin but the two su files & installed xbin via this https://play.google.com/store/apps/details?id=stericson.busybox
This is an "update".zip created with Philz. Use it in place of the original. Install it rather than restore. All other steps will be the same. Untested with Droid razr data widget, which may be the Rabbit's need of such big xbin.
I can up a twrp version too.
Click on the attachment, copy & paste to Chrome or get Mega.

All current Vzw 98.18.94 OR 98.18.78 unlocked boots may flash this Telstra rom & keep their apps & data. See post 18 & 17.
After being on Mhous33's DST build of 98.30.1 for weeks, I realize how much better this Telstra version is. See previous post.

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!

This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.

What is write enabler?

Keeps aborting for me

THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.

@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.

To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.

What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516

So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2

jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?

ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.

lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.

O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2

ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.

I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.

I reinstalled the stock odex ROM and flashed this again and it worked.

Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.

Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.

ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app

fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

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.

[TUTORIAL] Manually port T-Mobile Alliance ROM 5.0.1 to Verizon Dev Edition (12/8/15)

** Got Verizon Note 4 Dev Edition to work with Alliance T-Mobile ROM!! Data, calling, sms, mms work ! I smell a daily driver! I am not a developer, but this manual port taught me a lot. This was a personal project of trial and error, and research that turned into a stable ROM. Thought I'd share how I did it. I do not take credit for this ROM or kernel**
DISCLAIMER: Your warranty is now void. Please be careful make a nandroid of your current Verizon ROM. I am not responsible if you break your phone or lose data on your device! Read this whole OP!
**This is using the BETA version of Alliance ROM for T-Mobile Note 4. Download the Alliance BETA and read the thread: http://forum.xda-developers.com/not...-0-1-allianceromn910t-18-themes-huge-t3085560 to get an idea of the features of this ROM. Give lacoursiere18 and hsbadr a thanks and donate to them for making this great ROM and kernel.
Follow these steps one after the other and don't stop**
1. Make sure you are on a OAF Lollipop ROM without xposed installed. I think I used Rick's OAF Lollipop ROM originally. Download the most recent multisystem kernel. I am on BOG modem so I'm pretty sure any Lollipop modem will work with this.
2. On your Verizon Lollipop ROM make copies on your SD card of:
- system/buildprop.xml & cscversion.txt
- system/etc/apns-config.xml
- system/etc/permissions/verizon_net_sip_library.xml & vzwapnlib.xml
- system/lib/libril.so & libsec-ril.so
- system/apps/VzwActivationAgent, vzwapnpermission & **SecSetupWizard2013**
- system/framework/VZWAPNLib.apk
- system/privapp/VZWAPNService & secmms_candy folders
- system/csc folder
4. Reboot into recovery and make a TWRP backup of everything except SD card.
5. While in recovery dirty flash Alliance ROM BETA on top of your lollipop ROM OAF (Wipe everything EXCEPT data, internal storage, and SD). Then flash the most recent multisystem kernel.
6. Once booted up and apps are optimized wait until the screen turns off by itself. Download root browser and delete system/privapp/diagmonagent.apk and system/lib/libdiagmonagent.so because at startup it was sending some kind of diagnostics and thought it was messing with the data drop. Ever since these changes and a reboot data has been stable!
Reboot
7. Using root browser, swap those copied files in the appropriate file location. Change them to the correct permissions (the folders get 0755 and the files 0644, compare with other files and folders that are in place already. Make sure you change the permissions on all folders copied over and their contents. If a permission is incorrect or you leave a file out there can be issues and a restore might be needed.). Let apps optimize. **Longest Step**
Reboot
8. Edit feature.xml in the system/csc folder and add:
<CscFeature_RIL_ForceConnectMMS>true
</CscFeature_RIL_ForceConnectMMS>
Above the two bottom tags:
</FeatureSet>
</SamsungMobileFeature>
This enables auto download mms when data is toggled off !
Reboot
9. Perform a factory reset within the settings. Let phone relax for like 10 mins after it boots. Go through the setup wizard and then reboot.
Reboot into recovery
10. Make an backup in TWRP and you have your own custom ROM
I'm pretty sure this ROM is not compatible with xposed but it is very customizable, smooth, and it comes with a lot of features built in.
**READ ME**
Bugs:
- Silent mode is only available using the toggle. Volume down only goes to vibrate.
**
- Battery section in settings is missing
- No way to remove battery percentage in status bar
(Workaround: Download "Battery Usage Shortcut" from the Playstore to access the battery section and to remove battery percentage)
**
- No way to uninstall 3mint battery mod without messing the systemui up **(see update at the bottom)**
- Now that the mobile network settings are correct the advanced calling option is avaliable but it force closes and messes up your data connection. A reflash of everything will be needed so don't click on it! (I have a feeling a Verizon app is missing)
- My volume titles are not correct (Ringtone, media, notifications, and system.) when I press the volume buttons. (**Workaround download Noyze Volume Panel for free from the developer
http://forum.xda-developers.com/android/apps-games/app-noyze-volume-panel-replacement-t2875501
Give Tombarr a thanks for developing such a slick and customizable app**)
11/18/15:
- Just started using voicemail for the first time in 6 years. Good thing because today I experienced a glitch that it would not let me hang up the phone after listening to voicemails for some reason, but it didn't do that when I was clearing voicemails. (Hangs up automatically after a certain amount of time) Maybe it happens to new voicemails. Also I'm assuming since the verizon voice mail app isn't installed I get a weird unreadable verizon text when I get a new voicemail.
- One hand mode is not in the settings. Not sure why
Any suggestions or thoughts about these current bugs would be helpful.
I cannot guarantee all Alliance settings will work (stay away from performance), but most does work and it's awesome!
This manual port is now stable and buttery smooth! All basic phone functions work. Let me know if you come across any bugs or issues not related to Alliance settings. I will try to help fix it.
Thanks Stedrocklp for taking the time to try and get this working. Jal3223 thanks for sharing that key porting info!!! Wouldn't be possible without your help! Thanks hsbadr for developing Multisystem kernel ! Thanks lacoursiere18 for creating this ROM !
UPDATE:
To update Alliance settings to the most recent version and remove 3mintbattery mod download the newest T-Mobile Alliance ROM v1.1
1. Use ES File Explorer and click on the Alliance ROM you just downloaded to open the archive.
2.
- Extract system/privapp/SystemUI/SYSTEMUI.apk
- In the system/app folder extract AllianceControl folder (towards the top) and all the loose apps without folders at the bottom to a folder on your sd card.
3. Make a system and data backup in TWRP just in case things go wrong. Reboot system
4. Swap all those files and folders in their appropriate file locations and change the folder permissions to 755 and files to 644. Take this step slow and make sure the old files are renamed to .old or overwritten. If a permission is incorrect or you leave a file out there can be issues and a restore might be needed.
5. In system/app folder delete the old loose Alliancecontrol.apk, and delete 3mintbattery.apk
6. Reboot and enjoy!
This is the final release of this ROM so we are all up to date ! :good:

Wondering if this will work for sprint or any rom

dyra502 said:
Wondering if this will work for sprint or any rom
Click to expand...
Click to collapse
I'm pretty sure it would but you need to figure out the sprint specific apps to make the system happy. And flash your sprint kernel after you dirty flash. The dirty flash skips the setup which makes it possible to boot correctly.

Would you mind sharing the Rick's ROM that you used? I looked at his thread, but the download links are no longer available. Thank you in advance for your help!

Romans8vs1 said:
Would you mind sharing the Rick's ROM that you used? I looked at his thread, but the download links are no longer available. Thank you in advance for your help!
Click to expand...
Click to collapse
Damn thats not good. I do not think I am allowed to share the ROM, as it's not mine. But I do not know how to share it anyways. I would just odin back to 4.4.4. and go through the upgrade process to OAF. Or you can try to de-xpose MoRom after a clean flash. I think there are two things you need to remove one being the xposed installer and the other I don't know the exact name but use root browser, search for xposed in the system folder, delete it, and reboot. No sure if it will messed anything up but I don't think it will. Then dirty flash the alliance beta and continue from there. Let me know how it goes!

jcip17 said:
Damn thats not good. I do not think I am allowed to share the ROM, as it's not mine. But I do not know how to share it anyways. I would just odin back to 4.4.4. and go through the upgrade process to OAF. Or you can try to de-xpose MoRom after a clean flash. I think there are two things you need to remove one being the xposed installer and the other I don't know the exact name but use root browser, search for xposed in the system folder, delete it, and reboot. No sure if it will messed anything up but I don't think it will. Then dirty flash the alliance beta and continue from there. Let me know how it goes!
Click to expand...
Click to collapse
Thank you for your response. I ODIN'd back to OAF and went through the steps in your tutorial. My phone booted up and I then proceeded to replace the files/folders and set permissions. I thought I was careful, but once I tried to reboot, the phone would not come back up.
Is there a way to make the changes (file permissions and replacing them in the ROM) on a PC?
Is there a way to share your edited files so that we could simply paste them into the ROM?
Just thought I would ask. Thank you in advance for your assistance!

Romans8vs1 said:
Thank you for your response. I ODIN'd back to OAF and went through the steps in your tutorial. My phone booted up and I then proceeded to replace the files/folders and set permissions. I thought I was careful, but once I tried to reboot, the phone would not come back up.
Is there a way to make the changes (file permissions and replacing them in the ROM) on a PC?
Is there a way to share your edited files so that we could simply paste them into the ROM?
Just thought I would ask. Thank you in advance for your assistance!
Click to expand...
Click to collapse
Damn thats a bummer. Even if I shared the files you would still need to change the permissions. I think it is possible unzip a verizon ROM and unzip Alliance rom and replace the files and then zip it back up on the computer and then dirty flash that but everytime I zip it back up it never flashes. It seems that when I zip it back up it adds an extra folder that makes it unflashable but haven't taken the time to figure out how to make it work. Try starting over and getting the ROM to boot then make a nandroid of that so you have something to restore. This is what I did when I was trying to get everything working. Next time try not adding the camera files and .jar file and add them after a reboot. Let me know how it goes.

Added the setup as one of the files to copy over so a factory reset can be performed to make sure you're starting with a fresh system. This is the first day I did this and I had to pull the battery twice due to freezes after I factory reset. I didn't let the phone sit and let it settle. I would recommend you let it sit and relax for like 10 mins. I have not had any lock ups since this morning. Lemmi know how it goes!

After the factory reset the ROM is flying. As for the battery I cannot say yet but I know I did not have the best battery life on this ROM before. It did get me through the day so I was happy about that. I calibrated the battery but that is about it. If any devs knows any battery optimizations that can be made to the system without xposed please share!

I heard from a user that Xposed works on this ROM. I personally do not use it though. As for battery life I've noticed better results after I disabled automatic check for updates in the settings. Settings > About device > Software Updates and uncheck auto check for updates. This ROM for some reason does not have the audio issues that I experienced on MoROMs ROM. I am happy about that. Now that we finally have the 5.1.1. update I am going to try and port a ROM that looks good. If anybody wants to give this a stab with me that would be great to test multiple ROMs from different carriers and see which one gives us the best results. Thanks

Got something amazing in the works!

Nandroid backup
Can someone send me a nandroid backup of this I'm worried about messing up my phone up

Is there a way to install this rom in the same manner as the kyobi note 5 port? I'm running that now, but would like to try this one out. I've tried a few times but just can't seem to get this one up and running.
Thanks in advance and have a blessed day!
Sent from my SM-N920F using Tapatalk

TheRock40359 said:
Can someone send me a nandroid backup of this I'm worried about messing up my phone up
Click to expand...
Click to collapse
That's a big file idk how I would be able to distribute that lol

Romans8vs1 said:
Is there a way to install this rom in the same manner as the kyobi note 5 port? I'm running that now, but would like to try this one out. I've tried a few times but just can't seem to get this one up and running.
Thanks in advance and have a blessed day!
Sent from my SM-N920F using Tapatalk
Click to expand...
Click to collapse
It's not that simple. A data fix would need to be made and that is out of the scope of my knowledge. But when I have some free time, possibly this weekend, I can attempt to come up with something for you to try.

jcip17 said:
That's a big file idk how I would be able to distribute that lol
Click to expand...
Click to collapse
Could upload it to dropbox

Anyone with a Developer addition phone willing to help us none developers get root/unlocked bootloader? New exploit found but we need an .aboot from a developer phone: http://forum.xda-developers.com/note...ition-t3346422

Since I am currently on BPA1 5.1.1 running the Kyubi ported ROM and this is a 5.0.1 ROM, will I have to do downgrade my device or anything or will I be good to go to dirty flash? Thanks in advance.

stajam said:
Since I am currently on BPA1 5.1.1 running the Kyubi ported ROM and this is a 5.0.1 ROM, will I have to do downgrade my device or anything or will I be good to go to dirty flash? Thanks in advance.
Click to expand...
Click to collapse
I don't recommend dirty flashing from Kyubi. You should try clean flashing MoRom then copying those files from the system. Then dirty flash Alliance, then multisystem kernel:
http://forum.xda-developers.com/not...opment/kernel-multiystem-kernel-v1-0-t3105603
And just follow the OP instructions.

jcip17 said:
I don't recommend dirty flashing from Kyubi. You should try clean flashing MoRom then copying those files from the system. Then dirty flash Alliance, then multisystem kernel:
http://forum.xda-developers.com/not...opment/kernel-multiystem-kernel-v1-0-t3105603
And just follow the OP instructions.
Click to expand...
Click to collapse
Yeah ,I am trying to pull the files I need from my stock ROM backup that I just freshly installed on my device. I stumbled upon a forum here today called Guides There seems to be ALOT of usefull stuff in here about Porting and Building ROM's. I don't know if you have ever come across it or not.