Database Develop

[MOD] Stock lockscreen

Ok i managed to get the stock lockscreen if you all want to use it.
There is a possibility that the file i signed has a different signature, but i dont think it will.
Remember make a backup! always.
If your phone gets messed up it is not my fault.
I have warned you, so here you are. EDIT: Unzip the file then push the one inside of the zip.
put the file i uploaded in /system/framework ............. let me know what you think!
Thank to : Ateisti for giving the info on how to modify it.
If you want to go back to your old lockscreen download the enable_glass_lock.zip, unzip it, and push the enable_glass_lock to /data/local
If your signature is different it will get stuck on the samsung, you can then restore your backup.
and if you want it then run these instructions:
You need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.

You are the ****ing man!

How well does this work with the alarm silencing and incoming calls? Thanks!!!
EDIT: Never mind...testing it out.

wasupwithuman said:
Ok i managed to get the stock lockscreen if you all want to use it.
There is a possibility that the file i signed has a different signature, but i dont think it will.
Remember make a backup! always.
If your phone gets messed up it is not my fault.
I have warned you, so here you are.
put the file i uploaded in /system/framework ............. let me know what you think!
Thank to : Ateisti for giving the info on how to modify it.
Click to expand...
Click to collapse
I'm a little confused... do we need to just change the file to android.policy.jar or leave it the name that it is and just move it to /system/framework
thanks!

taypotts said:
I'm a little confused... do we need to just change the file to android.policy.jar or leave it the name that it is and just move it to /system/framework
thanks!
Click to expand...
Click to collapse
Keep the name and adb push it to /system/framework (you might want to backup your old one) you can backup by "adb pull /system/framework/android.policy.jar"
You can also install it using root explorer if you want.

wasupwithuman said:
Keep the name and adb push it to /system/framework (you might want to backup your old one) you can backup by "adb pull /system/framework/android.policy.jar"
You can also install it using root explorer if you want.
Click to expand...
Click to collapse
See I'm still confused, cause there is no file named android.policy (samsung fascinate) in the folder "framework" but there is android.policy.jar
Should I unzip the downloaded file then push that?

taypotts said:
See I'm still confused, cause there is no file named android.policy (samsung fascinate) in the folder "framework" but there is android.policy.jar
Should I unzip the downloaded file then push that?
Click to expand...
Click to collapse
yep, unzip first...

Quick question, does this take away the option for the other two lockscreens, ie glass and puzzle? If not I can throw this in my theme port (with your permission of course) and also theme this lockscreen as well.

frostman89 said:
Quick question, does this take away the option for the other two lockscreens, ie glass and puzzle? If not I can throw this in my theme port (with your permission of course) and also theme this lockscreen as well.
Click to expand...
Click to collapse
Your more then welcome to use it, but It does not give an option. So you would have to create a seperate theme for people who would just want the stock lockscreen.

I've tried installing this twice with root explorer, and both times my phone gets stuck on the Samsung logo when I reboot.
To install the file, I unzip the download and then place the .odex file in /system/framework. Any ideas on what I'm doing wrong?
Sent from my Fascinate using XDA App

tiger4life said:
I've tried installing this twice with root explorer, and both times my phone gets stuck on the Samsung logo when I reboot.
To install the file, I unzip the download and then place the .odex file in /system/framework. Any ideas on what I'm doing wrong?
Sent from my Fascinate using XDA App
Click to expand...
Click to collapse
your signature isnt the same as my file. you can try to do this but you need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.

hey man, i'm new to all this i've done all that u said, but what is the command to pull the android.policy.odex from the phone? I think i'm putting the wrong directory in the command because I keep getting "remote object '......android.policy.odex' does not exist" thanks for this, btw i really dislike that puzzle piece unlock bs.
nevermind, I wasn't in cwm when doing it the first time. Thanks again.

I like this, can't wait to try it.

wasupwithuman said:
your signature isnt the same as my file. you can try to do this but you need to use adb not rootexplorer
DO this while in cwm recovery
1. Rename the file you downloaded to patched.odex
2. adb push it to your /system/framework
3. adb shell then cd into /system/framework
4. run this
dd if=android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
5. exit shell
6. adb pull the android.policy.odex for backup
7. adb shell cd /system/framework
8. rm android.policy.odex
9. mv patched.odex android.policy.odex
reboot and you should have stock lockscreen.
Click to expand...
Click to collapse
That did the trick. Thanks for the help!

Sweet, put that file in the xultimate and deodex'ed and got it working.. Thanks

Followed step by step from adb, and got stuck with the Samsung screen.

DUNC4N said:
Followed step by step from adb, and got stuck with the Samsung screen.
Click to expand...
Click to collapse
hmm... you used the file i attached and did eveything in adb? try again, i'd like to help more, but if you did everything step by idk...
You did it in cwm recovery right?

Thanks for the reply.
Yes I did it in clockwork recovery. I may of had some confusion on the second to last step. I'll try again when I get home.
Two questions: Is the silent slide functional, and are the last two steps verbatim.
Thanks again.
Sent from my SCH-I500 using XDA App

DUNC4N said:
Thanks for the reply.
Yes I did it in clockwork recovery. I may of had some confusion on the second to last step. I'll try again when I get home.
Two questions: Is the silent slide functional, and are the last two steps verbatim.
Thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
not sure about the silent slide....i don't use this lockscreen. i just made it for you guys... and yes follow the last two steps exactly how i have them.

Silent mode is functional.

Deodexed stock Telus/Koodo rom

I'm looking for a deodexed version of the stock Telus/Koodo (Canada) rom for Galaxy Ace. I have the odexed version, but I'm not sure how to deodex. If anyone knows where I can get the deodexed version, or can help me with deodexing, it would be greatly appreciated.

Quietly, THIS IS DEVELOPMENT SECTION and not Q&A or GENERAL, POST IT THERE, here will be posted roms! READ THE XDA RULES BEFORE POSTING -.-

I only know how to deodex on Windows.
First have/download your SG Ace firmware (Canada)
Extract your firmware contents using MagicISO to: firmware_name\system
Download AutoDEOTool1.0.4 (Just a modified version of the tool, including updated binaries)
Unzip it to a directory without spaces e.g: C:\
Move/Copy your firmware's apps and framework files to: _app & _framework
Run AutoDEOToolMain.bat
Hit 2 to be specific.
To find your bootclasspath, just download Terminal Emulator on your Android phone
Run the command: echo $BOOTCLASSPATH
To save it in your sdcard, run: echo $BOOTCLASSPATH>>/sdcard/bootclasspath.txt​
Open the bootclasspath.txt, remove any "/system/framework/" codes (without the quotes) then save it
Now copy everything in bootclasspath.txt
Then in the AutoDEOToolMain windows, paste your bootclasspath & hit enter
This will deodex all files in _app & _framework
NOTE: If there are still some odexed files left, then use dsixda's kitchen to deodex the remaining files.​
Now copy/move all files in _app to your firmware's /system/app folder
Copy/move all files in _framework to your firmware's /system/framework folder
Now you have a deodexed Canada firmware!
Download these rom_tools and extract it to the root of the extracted firmware (firmware_name)
Now add the boot.img
Zip it and to flash it!

Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?

sauron82 said:
Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?
Click to expand...
Click to collapse
data folder is optional to include
META-INF folder is to flash the ROM
format.sh formats your Ace/Gio
installbusybox.sh installs busybox
mkfs.ext4 is the tool that format.sh uses

SuperSu binary manual update?

Does anyone know what files to replace/permissions to set in the system image when updating SuperSU and busybox, and where to get these files?

Yes.
644
root:root
You extract them out of the SuperSU package.
Have a look at my attachment, this unzip to /system/xbin/

arohrmann said:
Yes.
644
root:root
You extract them out of the SuperSU package.
Have a look at my attachment, this unzip to /system/xbin/
Click to expand...
Click to collapse
Thank you! I had to place the busybox file into both bin and xbin in order for busybox installer to recognize the updated version, but other than that, I followed your instructions exactly. So now my question is if I just updated the supersu binary to the latest version, why is supersu still telling me that I need to update the binary? Did you extract these from 2.46?
Two more questions: how did you extract them, and where did you get the version of busybox that you included in your previous post?

busybox is just in priv-app not in app - it works.
I don't know, why that update message comes up. It's the latests SU
You can open apk's like ZIP to extract. But you can find Update-ZIP to flash with recovery, to extract
That's the latest busybox I installed on an other android. Just moved to the System-Images.

[Help] Xposed Modification, All Exparts & Developers, Must Read And Give Me Some Advi

[Help] Xposed Modification, All Exparts & Developers, Must Read And Give Me Some Advi
Hello, Exparts & Developers
I need your help!! Can anyone tell me if i use this type of modification in mobile can i run successfully "Xposed Framework" in my mobile.
My mobile name is "WALTON PRIMO GF4" SDK=22, Lollipop 5.1, MTK6580, Rooted!
Note: I'm doing this modification, because i haven't any custom recovery img for this mobile and still i didn't find any recovery img for my mobile.
Here is my modification steps:
Requirements:
- Root Explorar.apk
- Xposed Installer Alpha.apk
- Xposed Flashable Zip
- Note Permission of those kind of file.
- Backup original file by (Copy Past to SD Card)
- Little brain and patience to understand all kind of file, what should i need to do.
1. So, First i need to do install Xposed Installer Alpha version and extract xposed flashable zip file and get those files
2. now it's time to backup original file from mobile and keep them safe place.
3. What i got in Xposed flashable zip to..
*System /bin (rwxr-xr-x)
/app_process32_xposed
/dex2oat
/oatdump
/patchoat
*System /framework (rw-r-r)
/XposedBridge.jar
*System /lib (rw-r-r)
/libart-compiler.so
/libart-disassembler.so
/libart.so
/libsignchain.so
/libxposed-ant.so
*System/ xposed.prop (rw-r-r)
and below files i need to backup first..
*System /bin (rwxr-xr-x)
/dex2oat
/oatdump
/patchoat
*System /lib (rw-r-r)
/libart-compiler.so
/libart-disassembler.so
/libart.so
/libsignchain.so
4. Final step replace them all and set the permission.. done now reboot..
Upper all kind of modifications to can i run successfully Xposed Framework??
Is this way work for me??
Please tell me, If yes than i will do this.
Thank You!
Tauhidur Rashid

I will donate money to anyone who helps me edit TabletSettings.odex app

thnx

PRInCEI7 said:
Hi .. I will donate money to anyone who helps me
.. I want to edit amazon fire 7 9gen system the TabletSettings.odex and TabletSettings.apk but the problem is
The modification does not accept.. Is there a way .
Click to expand...
Click to collapse
You can use APKTOOL:
https://ibotpeaches.github.io/Apktool/
Before nothing, you need to extract framework-res.apk and SystemUI.apk and then install them as frameworks:
Code:
apktool if framework-res.apk
Code:
apktool if SystemUI.apk
And then extract it:
Code:
apktool d TabletSettings.apk
Now edit whatever you want and when you finish repack it:
Code:
apktool b TabletSettings
Then go to dist and extract the apk.
Now go to original and copy all folders and files to unpacked apk from dist (overwrite all files)
And finally, repack unpacked dist apk with WinRar (extension .zip and then rename to .apk).
Now install the apk to the tablet:
Code:
adb reboot recovery
Code:
adb push TabletSettings.apk /sdcard
Code:
adb shell
Code:
mount system
Code:
mv /sdcard/TabletSettings.apk /system/priv-app/TabletSettings/TabletSettings.apk
Code:
chmod 664 /system/priv-app/TabletSettings/TabletSettings.apk
And reboot to system.
BTW: What modifications you want to do?

Rortiz2 said:
You can use APKTOOL:
https://ibotpeaches.github.io/Apktool/
Before nothing, you need to extract framework-res.apk and SystemUI.apk and then install them as frameworks:
Code:
apktool if framework-res.apk
Code:
apktool if SystemUI.apk
And then extract it:
Code:
apktool d TabletSettings.apk
Now edit whatever you want and when you finish repack it:
Code:
apktool b TabletSettings
Then go to dist and extract the apk.
Now go to original and copy all folders and files to unpacked apk from dist (overwrite all files)
And finally, repack unpacked dist apk with WinRar (extension .zip and then rename to .apk).
Now install the apk to the tablet:
Code:
adb reboot recovery
Code:
adb push TabletSettings.apk /sdcard
Code:
adb shell
Code:
mount system
Code:
mv /sdcard/TabletSettings.apk /system/priv-app/TabletSettings/TabletSettings.apk
Code:
chmod 664 /system/priv-app/TabletSettings/TabletSettings.apk
And reboot to system.
BTW: What modifications you want to do?
Click to expand...
Click to collapse
thanks for replying
Unfortunately this method does not work
I imagine because of a odex file
I want to add the language to the system
All devices accept except this type AMAZON FIRE 7 9gen does not accept

@PRInCEI7
@Rortiz2
You would first need to de-odex the rom, however this as far i know is not possible at the moment.
A few years ago at the time of the HDX devices amazon introduced a customised odex format.

ggow said:
@PRInCEI7
@Rortiz2
You would first need to de-odex the rom, however this as far i know is not possible at the moment.
A few years ago at the time of the HDX devices amazon introduced a customised odex format.
Click to expand...
Click to collapse
I have a tool for deodex the ROM but IDK if it will work. I'll give it a try.
Thanks for the info.

Rortiz2 said:
I have a tool for deodex the ROM but IDK if it will work. I'll give it a try.
Thanks for the info.
Click to expand...
Click to collapse
That's my point it won't work. There is no way to do what you want with any tool.

@Rortiz2 @ggow
I found this
When I root the device
Directly the application com.amazon.kindle.otter.oobe.apk stops working
When I change any file or put any file inside /System/priv-app/
When removing the root or flashing file too boot.img stock
Directly deletes any file or modification from this folder and returns the primary file ...
Why returns the original file when flashing a boot.img file
When I return flash boot.img root file returns my file .

@DragonFire1024
Do you have an idea to solve the problem

ggow said:
@PRInCEI7
@Rortiz2
You would first need to de-odex the rom, however this as far i know is not possible at the moment.
A few years ago at the time of the HDX devices amazon introduced a customised odex format.
Click to expand...
Click to collapse
You can use superr's tool to deodex if you have twrp. It requires rebuilding the firmware.
Sent from my Motorola Droid Razr M using XDA Labs
---------- Post added at 10:29 AM ---------- Previous post was at 10:26 AM ----------
PRInCEI7 said:
@DragonFire1024
Do you have an idea to solve the problem
Click to expand...
Click to collapse
If you are unlocked you can use superr's tool to deodex the firmware .bin package and rebuild it then flash in twrp. Requires Linux https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
Sent from my Motorola Droid Razr M using XDA Labs

thx