Database Info

[Tutorial]Deodexing + Zipaligning Galaxy Gio GT-S5660

Advantages or disadvantages
- Odexed ROMs are slightly faster, deodexed ROMs are slightly slower
+ You can make custom themes for your ROM
+ Performance los is negligible.
Requirements
xUltimate - http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
Busybox installed
Root
Automatic deodexing - Method 1, by r33p
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. Select option #15 then "do it all".
Deodexing (little harder, but contains useful information for your future Galaxy Gio modding experience)- Method 2, by me
1. Connect phone to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate.
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
Click to expand...
Click to collapse
7. Now data and cache reset in the recovery menu...
8. reboot
If one of the commands, for example 'cp' is not found, try putting busybox in front of the command:
eg: busybox cp /sdcard/done_frame/* /system/framework/
How to odex again
This may put you in the right direction. You may need to edit some steps.
http://forum.xda-developers.com/showthread.php?t=1124034
If you like my work please donate
Paypal:
Bankaccount: in private message

Updated my tutorial. Now everything works.

What does this do to my gio?
// Thanks from the noob

why the hassle? just let xultimate do it all automatic -> select option #15 then "do it all"
yep

Thanks.. ;-)
Would it work with others samsung devices?
Gonna try with 5510
Sent from my GT-I9100 using Tapatalk

dann3_86 said:
What does this do to my gio?
// Thanks from the noob
Click to expand...
Click to collapse
I am curious to

I suggest you google deodexing and zipaligning.
Deodexing in short means that it will allow you to have custom themes.
Zipaligning improves performance of the apk/jar files when reading
There is a lot of information you might want to look up!
I just added r33p's suggestion. Thanks!

Dhuu, just google it.............
I did, but it gives no answers.
I thought it was about the holy grail, or the fountain of youth..............
But no..........
But comes close
So tell me, does it works on the fly or must you reboot to aply changes?

I tiedy this metod and it works. Tank you

I'm having a problem..
I'm on xUltimate, I go to the advanced menu (15) and I type 1 (Do everything) and then it says that I don't have files in done_app folder.
Please help
Edit: I have rooted my phone, it's on Gingerbread.xxkpo. Do I have to Un-Root my phone and then do this ? Also can I root it back when the ROM is on ?
Please reply fast :S

I'm having this issue,,, what does it mean? i pulled out all the files with the automatic process and went fine. But then in the deoxed process:
How can i solve it? Thanks :3

{TUToRIAL]HOW TO DEODEX I9001 FOR NOoBS

HOW TO DEODEX YOUR I9001
THIS IS A SIMPLE GUIDE FOR THE NOOBS SO THAT THEY CAN DEODEX THERE I9001
What you'll need:
A Windows based machine
JDK
ANDROID SDK
LATEST XULTIMATE
And A Rooted I9001
Process:
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUltIMATE should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the internal sdcard not in the external sd.
9. Now Put the phone in USB DEBUGGING mode and DON'T PUT THE PHONE IN MASS STORAGE MODE
10. Open a command prompt, and do the following:
Code:
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# cp /sdcard/done_app/* /system/app/
# cp /sdcard/done_frame/* /system/framework/
# mount -o remount ro /system
# reboot
Credits to -
Xeodoxus for xultimate
Ghostlypickel for this guide
DO THIS AT YOUR OWN RISK
IF YOU LYK MY POST THEN PLEASE PRESS THE THANKS BUTTON
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RESERVED...

RESERVED..........

For Android 2.3.x using this command
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/

Maybe a stupid question but what are the benefits when I'm deodex my i9001?
Sent from my GT-I9001 using XDA App

oudbrood said:
Maybe a stupid question but what are the benefits when I'm deodex my i9001?
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
it is easier to make themes/mods for deodexed firmware

@ oudbrood
and you will got more space in system

Thanks for the reply's.
I get smarter every day
Sent from my GT-I9001 using XDA App

Not understand something here...does the phone always on usb? No plug in n plug out usb? The commant have to type where? Pc? Like this...start-run-cmd-enter?
GT-I9001 Adrenaline Shot - powered by Instanet free edition

Lol, thread looks familiar
kkrraazzyy said:
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3
6. Now run option 4, and wait.
Click to expand...
Click to collapse
Can be done in one step (option 5 - Pull and Deodex all).
Note that deodexing (steps 3 and 4) sometimes returns errors. Just repeat the procedure and it will work a second (or third) time...
kkrraazzyy said:
10. Open a command prompt, and do the following:
Click to expand...
Click to collapse
You can also make a batch file to move files from the xUltimate folder onto your device (put this patch-file into the xUltimate folder - this will not use the sdcard and push the files directly onto the device!). Something like this:
Code:
@echo off
jar\adb -d remount
jar\adb -d push done_app /system/app
jar\adb -d push done_frame /system/framework
echo all ok? going to remove *.odex files...press a key to continue...
pause >nul
jar\adb -d shell rm /system/app/*.odex
jar\adb -d shell rm /system/framework/*.odex
jar\adb -d remount
echo rebooting...press a key to continue...
pause >nul
jar\adb -d reboot
pause
---------- Post added at 08:31 AM ---------- Previous post was at 08:29 AM ----------
pyronia said:
Not understand something here...does the phone always on usb? No plug in n plug out usb? The commant have to type where? Pc? Like this...start-run-cmd-enter?
Click to expand...
Click to collapse
Yes, running Main.exe and deodexing requires the device to be plugged into USB. Using ADB also uses USB, although you can do it from your device too with shell tools. And if you want an automated DOS script for moving the files using ADB, see above
---------- Post added at 08:42 AM ---------- Previous post was at 08:31 AM ----------
One more thing: you need BusyBox too:
https://market.android.com/details?id=stericson.busybox

do i have to flash again tweak like adrenaline shot after deodexing???

pyronia said:
do i have to flash again tweak like adrenaline shot after deodexing???
Click to expand...
Click to collapse
No, it does not touch any of those (Adrenaline, Root, CWM, etc.)

Hahaha...i just back from bootloop....i think it will not workout for me...
GT-I9001 Adrenaline Shot - powered by Instanet free edition

pyronia said:
Hahaha...i just back from bootloop....i think it will not workout for me...
GT-I9001 Adrenaline Shot - powered by Instanet free edition
Click to expand...
Click to collapse
Lol, glad you're still laughing so how did you do it? On which base-ROM? I've done it several times and never had any issues...

nikagl said:
Lol, glad you're still laughing so how did you do it? On which base-ROM? I've done it several times and never had any issues...
Click to expand...
Click to collapse
ZSKP6...it stuck when i try to use terminal modulator...all apps fc then bam!!! Mr. Bootloop came out after remove battery....
GT-I9001 Adrenaline Shot - powered by Instanet free edition

So...using shell other than adb doesn't work tx 4 testing )
Sent from my GT-I9001 using XDA App

It doesn't work with the shell on your mobile since when u type "stop" it totally freezes.. ADB SHELL IS REQUIRED. the poster might want to say that since this is just a 100% copy of the deodex I9003 tutorial
when i tried it my phone got in a bootloop tho.. but I will try later again

I used ADB and it works. No bootloop or errors

to deodex always use ADB
and be sure that you have busybox installed on your device
otherwise the commands cant be executed

Guys, what am I doing wrong?
- Rooted XXKPS
- Ran main.exe ok with all steps.
- All okay until "(busybox) cp /sdcard/done_app/* /system/app/"
It can't find my sdcard.. I'm sure I have the files placed in the root of the internal sdcard.

BlueStacks Beta 4/3 ROOTED & Play Store Guide

SEE POST 3 FOR ROOT GUIDE
Below you will find the neccesary steps needed to get Google Play to run on BlueStacks Beta
1. Install Root Explore (can be downloaded for free using bluestacks and typing in the app name)
2. Download the Vending.apk and Google Framework from this post.
http://www.androidfilehost.com/main/Misc/Bluestack/
3. Copy them to /data/bst
4. Give them these Permissions
(rwxr-xr-x) or through adb:
Code:
adb shell chmod 755 /data/bst/vending.apk
adb shell chmod 755 /data/bst/googleservicesframework.apk
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Reboot Bluestacks
6. Download ADW Launcher if you haven't (this is not a requirement but it helps as if you already have Google Play in your PC you just find it through /data/windowsdata)
7. Find Google Play and sign in with your email and password.
Step by Step Guide on how to get into root.fs and mount the system.img
Click Here
The programs that are listed in the tutorial can also be found on my site here:
http://www.androidfilehost.com/main/Misc/Bluestack/
Along with those programs you will find all the tools,apks, installers you will need to get the market on Bluestacks Beta along with the tools to modify its files.

Lost, Confused, Cant get the Market to run with the instructions above?
Alternative Way-UPDATED 4/2/2012 :
I have uploaded a modified root.fs to my site for you to download
I added the the market per the instructions in the tutorial on the blog.
Steps:
Download the root.fs and overwrite the current root.fs on your computer.
Location:
C:\ProgramData\BlueStacks\Android
Make sure to stop all instances of BlueStacks before overwriting the file. Also Please Please make a backup of your original root.fs before overwriting the file with the modified one.
Once you have copied over the new root.fs start Bluestacks and wait for it to load up.
Congrats you have the newest Market running on BlueStacks.
You might need to install ADW Launcher inorder to see the Play Store/Market. It doesnt show up in the bluestacks launcher
Files can be downloaded from here:
http://www.androidfilehost.com/main/Misc/Bluestack/
------------------------------------------------------------------------
Was going to post my own guide but someone beat me to it.
Here a guide on some of the Registry Tweaks
http://droidhackings.blogspot.com/2012/03/some-useful-registry-tweaks-to-optimize.html

---Rooting BlueStacks Beta---
DOWNLOAD LIST (assuming you already have BlueStacks installed):
Code:
1. initrd-betahack.img ***INCLUDED***
2. ramdisk.img ***INCLUDED***
3. system.img-----------------NOT INCLUDED!!!
4. su.x86 ***INCLUDED***
5. BlueRegistryMOD ***INCLUDED***
--------------------------------------------------------------------------------------------------
Download from Here:
http://www.androidfilehost.com/main/Misc/Bluestack/Rooting BlueStacks Beta/
Code:
These are the custom files needed for root and r/w
-initrd-betahack.img
-ramdisk.img
-system.img
-su.x86
FILE: initrd-betahack.img
-From Beta (modified)
-Place it in \%programdata%\BlueStacks\Android\
FILE: ramdisk.img
-From Mod-V3.zip alpha
-Place it in \%programdata%\BlueStacks\Android\
FILE: system.img
-Extracted from xRepinsSporsx Root.fs (for Google Play)
Or
-Extracted from latest BlueStacks Root.fs
-Place it in \%programdata%\BlueStacks\Android\
FILE: su.x86
-From Androidx86 build (extracted from rooted alpha)
-This is the x86 superuser binary that auto-grants superuser-rights
***This file will be pushed to android using adb later on***
-------------------------------------------------------------------------------------------------
Code:
These files are the stock Beta files and remain in place
-kernel.elf
-Data.fs
-Prebundled.fs
-SDCard.fs
FILE: kernel.elf, Data.fs, Prebundled.fs, SDCard.fs
-From Beta
-Placed in \%programdata%\BlueStacks\Android\
---------------------------------------------------------------------------------------
Changes that need to be made to the registry are contained in BlueRegistryMOD.reg
FILE: BlueRegistryMOD.reg
***WARNING***
YOU MUST ENTER YOUR SPECIFIC USER ID BEFORE RUNNING BlueRegistryMOD.reg !!!
Where the registry key says ENTER-YOUR-GUID-HERE you need to enter the number (with dashes) found here:
FIND YOUR SPECIFIC GUID HERE!!!
[HKEY_CURRENT_USER\Software\BlueStacks]
“USER_GUID”=”SOME-NUMBERS-HERE”
Example of a GUID:
“USER_GUID”=”8dfcb602-4b7d-11e1-9dc9-f3dea6cb4293”
Example of a modified “BootParameters” with correct GUID and changes made to mount /system:
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android]
"BootParameters"="root=/dev/sda1 SRC=/android DATA=/dev/sdc1 SDCARD=/dev/sdd1 GUID=8dfcb602-4b7d-11e1-9dc9-f3dea6cb4293 armApps=true GlMode=1 OEM=BlueStacks "
***ENTER-YOUR-GUID-HERE must be changed in 2(two) places in BlueRegistryMOD.reg***
-------------------------------------------------------------------------------------------
THIS IS THE PROCESS:
***Make sure to exit BlueStacks before proceeding***
1. Paying attention to the guidelines above, place the following files in their correct location – this includes initrd-betahack.img, ramdisk.img, and system.img.
2. After finding your GUID and making the appropriate changes to BlueRegistryMOD.reg in 2(two) places, run the registry file.
3. Start/restart BlueStacks – go to the Start menu>type Start Bluestacks
4. Start adb on your computer
a. Connect to bluestacks - #adb connect 127.0.0.1:5555
b. Ensure you have root access - #adb root
i. You should get message: “adbd is already running as root”
c. Mount system as read/write - #adb remount
d. Remove ‘dummy’ superuser - #adb shell rm /system/xbin/su
e. Push x86 superuser to BlueStacks - #adb push su.x86 /system/xbin/su
i. su.x86 must be in the same Windows directory you are running in the console
f. Correct the permissions for superuser - #adb shell chmod 6711 /system/xbin/su
g. Remount system read only - #adb shell mount -o ro,remount t-ext4 /dev/sdb1 /system
h. Exit adb by closing the console window
5. Restart BlueStacks – go to the Start menu>type Start BlueStacks
6. At this point you should have root and read/write access.
a. Verify root using a tool like Root Check. I suggest Root Check Pro because it will point you to what the problem is if you do NOT have root.
b. Verify read/write access using a tool like Root Explorer.
7. Enjoy.
***This is a sure-fire way to get root and read/write access. However, I find that there are still issues with GAPPS (gmail, calendar specifically)
Download from here:
http://www.androidfilehost.com/main/Misc/Bluestack/Rooting BlueStacks Beta/
Extended system.img
http://www.androidfilehost.com/main/Misc/Bluestack/Extended system.img/

Thank you!
works perfect! Great!

Can not mount r/w system, any idea, is it possible ???

I used the alternative method - with the "root.fs"
that was perfect!
I would like to get the bluestacks-alpha-fullscreen again - without the suggested apps bar etc.
Any idea?
Thanks again,
Sascha

Stapelmeister said:
I used the alternative method - with the "root.fs"
that was perfect!
I would like to get the bluestacks-alpha-fullscreen again - without the suggested apps bar etc.
Any idea?
Thanks again,
Sascha
Click to expand...
Click to collapse
We cant get the whole bar to go away yet. im still experimenting with that. I can make it black but not 100% gone.

milniko said:
Can not mount r/w system, any idea, is it possible ???
Click to expand...
Click to collapse
It is not possible yet. Still working on it

imisa2 said:
Get Maximum out of your BlueStacks Beta, Some useful Registry Hacks, tips and tricks Here:
droidhackings.blogspot.com
Click to expand...
Click to collapse
Well frick lol Was just posting my tutorial/guide on how to do those things. you beat me to it.
MOD-Please combine last 3 Posts.
Sorry

@Repin
I went through the Mod-V3.exe that chevy uploaded for the alpha build that enables r/w access to sytem.
The main changes I saw involved system.img, init-hack.img, ramdisk.img, and registry hacks.
-The registry hacks are fairly self-explanatory, except that now there is a need for a /sde1 to allow for the PrebundledApps.fs
-We already have a good system.img with Superuser to use in place of Root.fs in the /Bluestacks/Android/ folder.
-I tore into the alpha initrd.img and compared it to the alpha initrd-hack.img. The only difference inside both initrd.img and initrd-hack.img was a bash script named init. After a comparison of the scripts I found the point where the initrd-hack init script sets up the /system for r/w access. I then compared the alpha init script and init-hack script with the beta init. The only difference between the alpha init script and the beta init script is that the beta script has two extra 'insmod' entries for HD that the alphs does not. So, I made the same changes to the beta init script that are in the alpha init-hack script to enable /system with r/w. ****I'm not sure how to repackage initrd.img with my modified init script so that we can replace the original***
-The only thing I am unsure of is ramdisk.img. My question to chevy is "Did you make any modifications to ramdisk.img contained in the Mod-V3.zip that was uploaded for the alpha build?"
Sent from my BlueStacks using XDA
(Edited for spelling)

What is wrong ???
Unpack original initrd.img:
mv initrd.img initrd.gz
gunzip initrd.gz
mkdir tmp
cd tmp
cpio -id < ../initrd
Archiving without any change:
find . -depth -print | cpio -o >../initrd
cd ../
gzip initrd.gz
mv initrd.gz initrd.img
The new cpio file initrd.img does not work, even no change ???

@milniko
Exactly. I need a way to repackage initrd.img with the new init script but I don't know how.
Sent from my Droid using XDA

Can you send me the new init script. ill try and repackage it

i have ubuntu in vmware and it very simple:
rename to gz
extract the file inside
copy and past this file in vmware ubuntu from windows
when i have this file on ubuntu i extract this file in a folder
edit the file of my interest in this folder
and for repack i use this when i'm inside the folder:
find . | cpio -o -H newc | gzip > ../initrd.gz
in the final i rename initrd.gz in initrd.img
p.s.
the same thisnks for the ramdisk.img

Blue Stack Help
Hello all, How are you
Thanks for help to root, but i've question
Once I Install Blue Stack, I Get automatically downloading some applications like pulse, Talk... etc . I can not cancel those applications.
Please how to cancel all this applications to download and install automatically.
How can I Manage Start up Items, and What Thnkgs that I Can Remove after Rooting Blue Stack. Thank you
Thanks

imisa2 said:
Try this:
Click to expand...
Click to collapse
Would you mind quoting the post you are responding to next time? It helps keep the thread organized. Additionally, please stop "spamming" the link to your website and simply link to the post in which you originally shared it.
My apologies if I sound like a **** for bringing it up. I assure you it isn't my intention.
We all appreciate your having put together a site with tutorials on it! Very helpful for those looking to play with BlueStacks.

Modified init for initrd.img
This is the edited init file found in initrd.img in Bluestacks Beta. Rename the stock beta initrd.img to initrd.bak. The init file is easily read in Notepad++.
The changes that were made reflect the same changes made in the alpha init that allows for r/w access. Specifically, the changes made are in the part where Androidx86 detection takes place. The script mounts /dev/sdb1 to /mnt and then moves /mnt to /android/system.
This init assumes that the following changes have been made to the Bluestacks Beta filesystem:
-The moddified init file has been repacked into initrd-hack.img. Place it in the \%programdata%\BlueStacks\Android\ folder.
-try the ramdisk.img from Mod-V3.zip alpha as /sda1. Place it in the \%programdata%\BlueStacks\Android\ folder.
-xRepinsSporx system.img file with superuser is to be used as /sdb1. Place it in the \%programdata%\BlueStacks\Android\ folder.
-the beta Data.fs is to be used as /sdc1
-the beta SDCard.fs is to be used at /sdd1
---------------------------------------------------------------------------------------
Changes that need to be made to the registry are:
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android]
"BootParameters"="root=/dev/sda1 SRC=/android DATA=/dev/sdc1 SDCARD=/dev/sdd1 GUID= OEM=BlueStacks"
"Initrd"="C:\\ProgramData\\BlueStacks\\Android\\initrd-hack.img"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\0]
"Name"="sda1"
"Path"="C:\\ProgramData\\BlueStacks\\Android\\ramdisk.img"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\1]
"Name"="sdb1"
"Path"="C:\\ProgramData\\BlueStacks\\android\\system.img"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\2]
"Name"="sdc1"
"Path"="C:\\ProgramData\\BlueStacks\\Android\\Data.fs"
[HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android\BlockDevice\3]
"Name"="sdd1"
"Path"="C:\\ProgramData\\BlueStacks\\Android\\SDCard.fs"
*** Also, “DisableRobustness” in [HKEY_LOCAL_MACHINE\SOFTWARE\BlueStacks\Guests\Android] may need to be changed from “0” to “1” ***

zulu99;24242353
and for repack i use this when i'm inside the folder:
find . | cpio -o -H newc | gzip > ../initrd.gz
in the final i rename initrd.gz in initrd.img
[/QUOTE said:
Still does'n work for me, please share initrd.img if it works for you
Thank you
Click to expand...
Click to collapse

i can repack, but the method of tenet24 not work.
the file is this:
http://www.2shared.com/file/wm2Wcqsa/initrd-hack.html
p.s.
i used the system.img inside the original Root.fs->system.sfs and the ramdisk.img of modv3
if i put this 3 files in other folder and correct the regedit to this other folder, the bluestacks hangs on a black screen, after this with hd-adb.exe i can connect to the virtual android and i can remount in rw the /system folder, but the gui of bluestacks not work. i think the ramdisk.img is not good, we can repack also this.

@zulu99
Can you post any debug or logs from when the GUI wont load? Check the Bluestacks folder for their log, and try to use adb to get the last ten lines or so of debug.
Thanks.
Sent from my Droid using XDA

[UTIL][22/2/13]Auto Odexer Script V2.1-Mod your odex files with a breeze

NEW VERSION 2.1, it is now much easier and like a breeze...
Before u read, u should know that this thread is for themers and modders only... and this is not a tool for odexing the whole ROM.
Hello everybody
While I was working on my ROM, and releasing an odex version, I suffered alot in working on the odex files and modifying them. Every time I should use the command line and copy certain commands from a notepad, in addition I have to edit the notepad file to make the commands odex other files... that was a pain...
ok.. the odex commands that were used are taken from this thread by sicopat, big thanks to his efforts. Actually I was thinking in how to make it easier for me to odex these modified files, so I tried to make a script that easily odex files, put the files in the right folder, run the script, and then write the name of the file u want to odex, then..... Waw the file is odexed in the phone and ready to run
For anyone that want to use these scripts, I wanted to share it with you, and I hope they would be useful to you.
Update (2/22/13) v2.1:
1. bootclasspath should be put manually from now, because $BOOTCLASSPATH doesn't work when no root in recovery.
2. Fixed a mistake in extracting and archiving files, now it's ok.
3. Now you can restore the original files if you like after odexing.
4. 7zip 32 bit is used instead of 64 bit, sorry for this, now it should work with 32 bit windows too.
5. Script re-arranged, and 7zip log operations saved in 7z_log.txt. you can check this one if you suspect in 7zip operation.
6. Backup of the original files before odexing and restore them after odexing.
Update (1/4/13) v2: All things automated, no need to edit the script for bootclasspath, and even no need to drag and drop the edited files from the modded apk or jar.
Update (9/20/12) v1.4: remount using busybox, this solves some remounting problems.
update (9/18/12) v1.3: adb added to the program, to make it work independently. And now you can pull the files after odexing if u need that.
update (9/10/12) v1.2: updated and added a missed command, it should works perfect. No need to put any files in your sdcard to make the operations... and the operations are commented so you can diagnose the problem if occurred.
download from here
Before you use, make sure u r running the corresponding odex rom in your device, then read how to use this tool.
How to use:
first extract the downloaded file to a folder then:
1. Put your bootclasspath in bootclasspath.txt (follow the instruction below in Important Note 2).
2. Put the original odex and apk (or jar) file in the "original" folder.
3. Put your modded deodexed apk (or jar) file in the "mod" folder
4. Connect your phone with usb and make sure adb is working. ( and don't forget to check the USB Debugging in the settings of your device).
5. It is better that you boot in recovery mod, specially when odexing framework files.
6. Now run the script (.bat file), choose the one for apk or for the jar, according to file you want to odex.
7. after the script opens, write the name of the apk (or jar) file without the .apk (or .jar)
8. Odexing......done.
9. after finishing odexing, u can pull the odexed apk or jar file by pressing 1 then Enter, the it will be pulled in the (pulled_files) folder. Or if you want to restore the original apk (or jar) file with its odex, then press 2.
If you find this thread useful, pressing the thanks button is appreciated.
Important note: If you r using a rooted stock kernel, then u could face problem in remounting, hence a problem in the script. To solve this problem check this post.
Important note 2:To get Your BOOTCLASSPATH:
1. In adb:
adb devices
adb remount
adb shell echo $BOOTCLASSPATH
after that, you can right click and choose (mark), then mark the bootclasspath then press (enter) now you have copied the bootclasspath. go to bootclasspath.txt in the extracted folder of the script, then paste the bootclasspath and save the file.
OR
2. In the root of your device, in the init.rc file:
look for a line with (bootclasspath= ), then copy everything on the right hand of the equal mark. Go to bootclasspath.txt then paste it there, then save the file.
screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credit:
Sicopat- for his guide on odexing.
M_j_Nazari- for his guide on odexing and his written commands for the odexing operation. thread link

I keep getting this error when trying to use your script. Help please?
Code:
remounting
'adb' is not recognized as an internal or external command,
operable program or batch file.

daveyannihilation said:
I keep getting this error when trying to use your script. Help please?
Code:
remounting
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This happened cuz u didn't add the adb directory to the system variables...
Anyway I updated it and it should work now without doing that...please try it and give me a feedback..

alkhafaf said:
This happened cuz u didn't add the adb directory to the system variables...
Anyway I updated it and it should work now without doing that...please try it and give me a feedback..
Click to expand...
Click to collapse
Ok mate. I'll download it and try it when I get home. Just for future reference though, how do I add the ADB directory to system variables??

daveyannihilation said:
Ok mate. I'll download it and try it when I get home. Just for future reference though, how do I add the ADB directory to system variables??
Click to expand...
Click to collapse
Go to my computer,then properties, in advanced there is Environment Variables, press it .. then in system variables add the (path) and write the directory that leads to the adb that u have when u installed android development tools ( it should be in platform-tools folder).
Try odexer first before doing that I can not try it cuz I don't know who to delete the adb from the system variables
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Go to my computer,then properties, in advanced there is Environment Variables, press it .. then in system variables add the (path) and write the directory that leads to the adb that u have when u installed android development tools ( it should be in platform-tools folder).
Try odexer first before doing that I can not try it cuz I don't know who to delete the adb from the system variables
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
Will do when I get home from work mate. So in about 6 hours. But who's counting?

daveyannihilation said:
Will do when I get home from work mate. So in about 6 hours. But who's counting?
Click to expand...
Click to collapse
Lol.. of course not.. cuz I will sleep now... its 6 am here and didn't sleep yet... and you r living the new day
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Lol.. of course not.. cuz I will sleep now... its 6 am here and didn't sleep yet... and you r living the new day
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
Ok I tried it and it didn't work properly.
Code:
remounting
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0019295d0b1c9e device
remount failed: Operation not permitted
Enter the name of the .apk file u want to odex (without .apk): Mms
sending dexopt-wrapper to the device
failed to copy 'dexopt-wrapper' to '/system/bin/dexopt-wrapper': Read-only file
system
Unable to chmod /system/bin/dexopt-wrapper: Read-only file system
sending the deodexed file to the device
failed to copy 'mod\Mms.apk' to '/system/app/Mms.apk': Read-only file system
Odexing the file:
Unable to create '/system/app/new_Mms.odex': Read-only file system
No error found
pushing the original files to the system
failed to copy 'original\Mms.apk' to '/system/app/Mms.apk': Read-only file syste
m
failed to copy 'original\Mms.odex' to '/system/app/Mms.odex': Read-only file sys
tem
Setting permissions..
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.apk: Read-only file system
Unable to chmod /system/app/new_Mms.odex: No such file or directory
copying signature from original file:
/system/bin/sh: busybox: cannot execute - Permission denied
replacing with the new odex file
/system/bin/sh: cp: not found
settings permissions for the new odex file
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.odex: Read-only file system
deleting worked- on file
rm failed for /system/app/new_Mms.odex, No such file or directory
Finished
To odex a file again, press any key
To pull the apk file, press 1
To exit, press 0
That's the error I keep getting. What does it mean? Am I doing something wrong?

daveyannihilation said:
Ok I tried it and it didn't work properly.
Code:
remounting
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
0019295d0b1c9e device
remount failed: Operation not permitted
Enter the name of the .apk file u want to odex (without .apk): Mms
sending dexopt-wrapper to the device
failed to copy 'dexopt-wrapper' to '/system/bin/dexopt-wrapper': Read-only file
system
Unable to chmod /system/bin/dexopt-wrapper: Read-only file system
sending the deodexed file to the device
failed to copy 'mod\Mms.apk' to '/system/app/Mms.apk': Read-only file system
Odexing the file:
Unable to create '/system/app/new_Mms.odex': Read-only file system
No error found
pushing the original files to the system
failed to copy 'original\Mms.apk' to '/system/app/Mms.apk': Read-only file syste
m
failed to copy 'original\Mms.odex' to '/system/app/Mms.odex': Read-only file sys
tem
Setting permissions..
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.apk: Read-only file system
Unable to chmod /system/app/new_Mms.odex: No such file or directory
copying signature from original file:
/system/bin/sh: busybox: cannot execute - Permission denied
replacing with the new odex file
/system/bin/sh: cp: not found
settings permissions for the new odex file
Unable to chmod /system/app/Mms.odex: Read-only file system
Unable to chmod /system/app/Mms.odex: Read-only file system
deleting worked- on file
rm failed for /system/app/new_Mms.odex, No such file or directory
Finished
To odex a file again, press any key
To pull the apk file, press 1
To exit, press 0
That's the error I keep getting. What does it mean? Am I doing something wrong?
Click to expand...
Click to collapse
That's because your system isn't being set to read write. And it looks like your using an old adb
Sent from my Sensation

blahbl4hblah said:
That's because your system isn't being set to read write. And it looks like your using an old adb
Sent from my Sensation
Click to expand...
Click to collapse
Ok then. Is there a way of setting my file system to read write? And do I just need to update the SDK via Eclipse to get a newer version of adb??

daveyannihilation said:
Ok then. Is there a way of setting my file system to read write? And do I just need to update the SDK via Eclipse to get a newer version of adb??
Click to expand...
Click to collapse
You need to mount it as read write.
Ask the OP to fix the script since he made it
Sent from my Sensation

Did u boot into recovery while doing this operation ?
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Did u boot into recovery while doing this operation ?
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
No I didn't. Do I just need to be on the main screen of ClockWorkMod recovery? And do I put it into recovery before I plug it into the USB cable or half way through the process?

alkhafaf said:
Did u boot into recovery while doing this operation ?
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
You don't need to go into recovery to do this.
Just make the script to mount system as a rw
Sent from my Sensation

blahbl4hblah said:
You don't need to go into recovery to do this.
Just make the script to mount system as a rw.
Sent from my Sensation
Click to expand...
Click to collapse
But the script already include that (adb remount)
I think the problem is in the adb itself.. I put the adb with two files with it related to it for the script to use... r these the only files related to adb? Cuz I can not test it as i can not delete the adb from the system variables.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
But the script already include that (adb remount)
I think the problem is in the adb itself.. I put the adb with two files with it related to it for the script to use... r these the only files related to adb? Cuz I can not test it as i can not delete the adb from the system variables.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
Well my advice is to test this completely before releasing an update

blahbl4hblah said:
Well my advice is to test this completely before releasing an update
Click to expand...
Click to collapse
It should work for anyone who added the adb path to the system variables...I really tested it and works fine.
The only thing that I didn't test is how the script run independently (using the adb which comes with it without using the adb of the platform-tools by adding its path to the system variables )
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

daveyannihilation said:
No I didn't. Do I just need to be on the main screen of ClockWorkMod recovery? And do I put it into recovery before I plug it into the USB cable or half way through the process?
Click to expand...
Click to collapse
Bro. Did u add the adb path to the system variables and tried ?
If u want the instructions Google it and u will probably find it.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

alkhafaf said:
Bro. Did u add the adb path to the system variables and tried ?
If u want the instructions Google it and u will probably find it.
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+
Click to expand...
Click to collapse
No mate I didn't because you asked me not to so that I could test how it works independently for you. You gave me the instructions in a previous post in this thread.
If that's the only way that I can get it to work (by adding it to the system variables) then I will just have to do that. I don't mind testing it for you, but it's up to you.
Let me know what you would like me to do.

daveyannihilation said:
No mate I didn't because you asked me not to so that I could test how it works independently for you. You gave me the instructions in a previous post in this thread.
If that's the only way that I can get it to work (by adding it to the system variables) then I will just have to do that. I don't mind testing it for you, but it's up to you.
Let me know what you would like me to do.
Click to expand...
Click to collapse
I really appreciate yhat , thanks alot..
But u can try to to add The adb to the system variables, maybe the problem is not with the adb..
If it works for u then please give me a feedback about it
Sent from tapatalk using sgs i9000
[ROM][GB][JW8] MesoROM v2.0 8/27/2012 Ultra Light-Smooth-Beauty
Google+

[Tutorial] Crack Your Android LockScreen Security

This tutorial is inspired by @m.sabra thread here.
All credits are for @m.sabra and @hanaheeno for pointing out the files responsible for LockScreen Security :good:.
If you find this tutorial helpful, please go to the main thread above and thanks those people.
Disclaimer: This is for educational purpose. Neither xda, nor me or people above are responsible of any misuse of this hack tutorial.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As shown in picture above, you can now rescue your LockScreen security in case you forgot your personal pattern, password, pin, signature or even face.!!
There are different ways to do this that we are going to describe.. So, without any further words, lets start our tutorial
Tutorial toolbox:
1) ADB engine from android SDK | Here - 400+ mb | or extracted one | View attachment adb_29072013.rar - 0.4 mb |.
2) Notepad++ for editing in windows machine | Here |.
3) Flashable zip template | Here |.
4) 7-zip archiver | Here | or WinRAR | Here |.
5) Samsung USB driver to be installed. | Here for 32-bit or Here for 64-bit |.
6) Aroma file manager | Here |.
7) Any custom recovery.
The methods (choose the one you like):
Method #1 - ADB through android OS:
This needs USB debugging to be toggled (enabled) in the first place in order to get adb shell functioned.
Click to expand...
Click to collapse
- Plug your device to USB and start adb session:
Code:
adb shell
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
rm /data/system/gesture.key
rm /data/system/password.key
rm /data/system/signature.key
rm /data/system/sparepassword.key
exit
adb reboot
In between each line, don't forget to hit Enter Key
The following video is showing how is this done (credits to @melvinchng)
If you run into some access denied messages, use su binary to elevate your permission level as following:
Code:
adb shell
su
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
rm /data/system/gesture.key
rm /data/system/password.key
rm /data/system/signature.key
rm /data/system/sparepassword.key
exit
exit
adb reboot
The following video is showing how is this done using su binary (again credits to @melvinchng)
Method #2 - ADB through recovery:
This needs USB debugging to be toggled to get adb shell functioned; but no need for root access
Click to expand...
Click to collapse
- Reboot into recovery.
- Plug your device to USB and start adb session:
Code:
adb shell
mount /data
rm /data/system/locksettings.db
rm /data/system/locksettings.db-wal
rm /data/system/locksettings.db-shm
rm /data/system/gesture.key
rm /data/system/password.key
rm /data/system/signature.key
rm /data/system/sparepassword.key
umount /data
reboot
In between each line, don't forget to hit Enter Key
Note:
I don't no whether this needs busybox to be installed or not because mount and umount binaries are symlinked to toolbox and busybox
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Method #3 - updater-script flashable zip file through recovery:
The pros of this method, that you don't need USB debugging to be toggled or root access :good:
Obviously, you will need custom recovery that allow flashing zip with unrecognized signature.!!
Click to expand...
Click to collapse
- Grasp my flashable zip template (you can download it from here) and navigate to /META-INF/com/google/android folder and extract updater-script, open it by Notepad++ and change the whole script to:
Code:
ui_print(" ");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox");
run_program("/tmp/busybox", "mount", "/data");
delete("/data/system/locksettings.db");
delete("/data/system/locksettings.db-wal");
delete("/data/system/locksettings.db-shm");
delete("/data/system/gesture.key");
delete("/data/system/password.key");
delete("/data/system/signature.key");
delete("/data/system/sparepassword.key");
run_program("/tmp/busybox", "umount", "/data");
delete("/tmp/busybox");
Don't forget to leave one empty line at the end.
- Save changes, and drag/drop the updater-script inside the flashable template inside /META-INF/com/google/android folder.
- Put the flashable file on your sdcard and flash it through recovery.
Check attachment for the pre-made flashable file.
Method #4 - sh script in flashable zip file through recovery:
Also this method doesn't require the USB debugging to be toggled or root access. :victory: but you will need custom recovery.
Click to expand...
Click to collapse
- Open Notepad++ new page, and paste the following code inside it:
Code:
#!/sbin/sh
#
###############################################################
# Auto Clear LockScreen Security Script for Android Devices #
# By majdinj xda-developers.com #
# #
# Thanks To: m.sabra & hanaheeno for the primary method #
###############################################################
#
if [ -e /data/system/locksettings.db ]
then
rm /data/system/locksettings.db
fi
if [ -e /data/system/locksettings.db-wal ]
then
rm /data/system/locksettings.db-wal
fi
if [ -e /data/system/locksettings.db-shm ]
then
rm /data/system/locksettings.db-shm
fi
if [ -e /data/system/gesture.key ]
then
rm /data/system/gesture.key
fi
if [ -e /data/system/password.key ]
then
rm /data/system/password.key
fi
if [ -e /data/system/signature.key ]
then
rm /data/system/signature.key
fi
if [ -e /data/system/sparepassword.key ]
then
rm /data/system/sparepassword.key
fi
Also don't forget to leave one empty line at the end.
- Save the file as "rescue_lockscreen_security.sh" (it could be anything, but for the sake of tutorial.!!).
- Now open the flashable zip template (download it from here) and navigate to /META-INF/com/google/android folder and extract updater-script, open it by Notepad++ and change the whole script to:
Code:
ui_print(" ");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox");
run_program("/tmp/busybox", "mount", "/data");
package_extract_file("rescue_lockscreen_security.sh", "/tmp/rescue_lockscreen_security.sh");
set_perm(0, 0, 0777, "/tmp/rescue_lockscreen_security.sh");
run_program("/tmp/rescue_lockscreen_security.sh");
run_program("/tmp/busybox", "umount", "/data");
delete("/tmp/busybox");
delete("/tmp/rescue_lockscreen_security.sh");
Also here don't forget to leave one empty line at the end.
- Save changes, and drag/drop the updater-script inside the flashable template inside /META-INF/com/google/android folder.
- Drag/drop rescue_lockscreen_security.sh in the root of flashable zip template.
- Put the flashable file on your sdcard and flash it through recovery.
Check attachment for the pre-made flashable file.
Method #5 - Aroma File Manager through recovery:
Special thanks to @amarullz for this amazing tool.
Go to the main thread here and download Aroma File Manager.
- This method doesn't require the USB debugging to be toggled or root access. Some claims it works on stock Samsung e3 recovery.
- Make sure to mount data partition before starting Aroma File Manager in recovery. In stock Samsung e3 recovery, flash Aroma File Manager, click on menu option and go to settings and toggle "Automount all devices on start", then exit the Aroma File Manager and then reflash it again.
Click to expand...
Click to collapse
- As described by the developer, copy the aromafm-xx.zip into your sdcard, then reboot your device into recovery mode. Choose install from sdcard, then select the aromafm-xx.zip. The file manager will start, and you are ready to manage your system files (copy, cut, delete, make new folder, etc) while you are in recovery.
- Now in Aroma File Manager, navigate to /data/system folder and delete the following files if exist:
Code:
gesture.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
password.key
signature.key
sparepassword.key
- Exit Aroma File Manager and reboot the phone.
Pre-made flashable files
You will see bellow in the attachment pre-made flashable files made from method #3 and method #4. Download the one you want, put it on sdcard and reboot to recovery and flash it.
Again, these flashable files are only made to help those who don't have technical skills to do the method themselves. I have the right to delete them anytime I feel there is misuse of them.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Please stay safe,,

reserved

If only it was there a couple of days ago. I had to reset my note due to forgotten password.
Sent from my GT-I9500 using xda premium

nokiamodeln91 said:
If only it was there a couple of days ago. I had to reset my note due to forgotten password.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Heh.. hard luck mate.
Now you are part of our little secret :angel:

is there any way of securing a device from these hacks?

@majdinj
Hi
Somehow i have missed this thread, a week ago i made a flashable zip for this after referring a thread of some other device.
I have used simple script to delete gesture.key (for pattern) and password.key (for PIN/Password) and tested myself and working fine (Note2). In case of PIN/Password it just removes but in case of Pattern it just hack, still you will have pattern but able to unlock with any pattern you draw
I did something extra experiments to make backup and restore (dadyz eye ) to unlock and relock with same password. it getting resore PIn/PW/Pattern but you can able to unlock with any key. when time permits will try some more experiments. Btw db-wl/db-shm file restoring casing bootloop.

@majdinj
Success.
Sent you pm.
Sent from my GT-N7100 using xda premium

dr.ketan said:
@majdinj
Hi
Somehow i have missed this thread, a week ago i made a flashable zip for this after referring a thread of some other device.
I have used simple script to delete gesture.key (for pattern) and password.key (for PIN/Password) and tested myself and working fine (Note2). In case of PIN/Password it just removes but in case of Pattern it just hack, still you will have pattern but able to unlock with any pattern you draw
I did something extra experiments to make backup and restore (dadyz eye ) to unlock and relock with same password. it getting resore PIn/PW/Pattern but you can able to unlock with any key. when time permits will try some more experiments. Btw db-wl/db-shm file restoring casing bootloop.
Click to expand...
Click to collapse
It is good to see you doc here.. It is an honor to my thread
I don't think I want to backup my old pattern/pass/pin or face..!! What I want is a method how could I login into my device if I forget my pattern/pass/pin?
Refining to the procedure; you can only delete locksettings.db, locksettings.db-shm, and locksettings.db-wal and then reboot since the device will create these files again upon booting but without any LockScreen data base.
This will give clear LockScreen interface as if no security has been there before..!!

Actually it's not needed to backup pw, but i want just for fun and challenge . Also not advisable to post bcoz this will use only to spy. But yes it can be possible.
Yeah locksetting delete is clean way. What I beleive is locksetting files keeping track of action you have set like pin/pw/pattern. And it gets auto updated on changing pw/pin/pattern. That's reason deleting just key files working.
Regards.
Sent from my GT-N7100 using xda premium

dr.ketan said:
@majdinj
Success.
Sent you pm.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Mind sharing how we can protect ourselves from this...

Is disabling adb shell via USB any good?
Also, maybe a kernel without a recovery with the ability to flash zip files?
What can we do for protection??

passord protected kernell

dr.ketan said:
@majdinj
Hi
Somehow i have missed this thread, a week ago i made a flashable zip for this after referring a thread of some other device.
I have used simple script to delete gesture.key (for pattern) and password.key (for PIN/Password) and tested myself and working fine (Note2). In case of PIN/Password it just removes but in case of Pattern it just hack, still you will have pattern but able to unlock with any pattern you draw
I did something extra experiments to make backup and restore (dadyz eye ) to unlock and relock with same password. it getting resore PIn/PW/Pattern but you can able to unlock with any key. when time permits will try some more experiments. Btw db-wl/db-shm file restoring casing bootloop.
Click to expand...
Click to collapse
Dr ketan, my brother sent me his second phone which is the samsung galaxy s2 cause he forgot his password. Can u help me on this? ?
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 02:52 AM ---------- Previous post was at 02:47 AM ----------
Would appreciate if someone help me on the other thread, here is the link http://forum.xda-developers.com/showthread.php?p=50917429
Sent from my GT-N7100 using XDA Premium 4 mobile app

cruelscene said:
Dr ketan, my brother sent me his second phone which is the samsung galaxy s2 cause he forgot his password. Can u help me on this? ?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can follow what @majdinj said in OP
OR simply flash zip from here (you will need CWM)
http://forum.xda-developers.com/showthread.php?t=2437946

dr.ketan said:
You can follow what @majdinj said in OP
OR simply flash zip from here (you will need CWM)
http://forum.xda-developers.com/showthread.php?t=2437946
Click to expand...
Click to collapse
Exactly Dr Ketan, that is what I'm trying to do. Did u watch already the link of video that I provided? Would love if u see the video....
It's stock & doesn't have custom cwm....
Sent from my GT-N7100 using XDA Premium 4 mobile app

cruelscene said:
Exactly Dr Ketan, that is what I'm trying to do. Did u watch already the link of video that I provided? Would love if u see the video....
It's stock & doesn't have custom cwm....
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
why dont you :
1. backup current recovery(or just skip this)
2. install custom recovery
3. unlock it
4.revert the recovery to stock

SamantaSync said:
why dont you :
1. backup current recovery(or just skip this)
2. install custom recovery
3. unlock it
4.revert the recovery to stock
Click to expand...
Click to collapse
Did u already watch the link that I provided? If yes, can u provide me the step by step recommended by you?
Sorry but I already tried to install custom kernel, custom recovery, tried to do factory reset via stock recovery, tried use command prompt for adb shell, tried to flash flash stock rom via odin, and stuff like that but NONE OF THEM ARE WORK.
Would appreciate if u teach me more....
Sent from my GT-N7100 using XDA Premium 4 mobile app

Successfully unlocked my Phone using This!!!!!!!!!!!
Hey bro Thanks for giving this way to open a homoscreen lock. I just want to see that its working or not. So i manually put a pin password nd tried to open with this. Got success full!!!!!!!! :good::good::good:

I successfully disabled the lock pattern on a marshmallow rom by just removing the three files /data/system/locksettings.db{,-wal,-shm}

Thanks for this great tutorial! After I did the steps from method 1 the password was gone. If I go to settings and try to create a new password it asks me for the fingerprint or backup password. Any way to crack this aswell? FYI: Galaxy S6 @ Android 6.0.1