Related
Hi all,
In this thread, I will try to share the knowledge I have on deodexing, making custom ROMs, modifying initramfs, building kernel and much more.
Please check the below posts for each of these tutorials.
Hope this opens doors to many new ROM and Kernel developers.
NOTE: THESE TUTORIALS ARE WRITTEN FOR GT-I9100. WILL NOT WORK ON OTHER DEVICES. I DON'T TAKE ANY RESPONSIBILITY IF YOU MESS UP AND BRICK YOUR DEVICE OR ANYTHING ELSE. USE AT YOUR OWN RISK.
Deodexing Stock Rom
For GINGERBREAD ROMS:
What you need to have:
xUltimate v2.3.3 - you can download it HERE (Thanks and Credits to Xeudoxus for this awesome app)
Rooted kernel with busybox
JDK installed on your Windows system
If adb is not available in your windows PC, in xUltimate folder open "jar" folder. You'll find adb there.
Extract stock app & framework folders and Deodex:
Connect your device to computer.
Start xUltimate (double-click on Main.exe)
Select option 1. (Pull /system/app)
Once option is done, select option 2. (Pull /system/framework)
In the same folder, now you'll see two new folders (origi_app, origi_frame)
Select option 3 in Main menu (Deodex /system/app)
Once its done, select option 4 in Main menu (Deodex /system/framework)
DONE!!
NOTE: If any apk/odex gives issues while deodexing, remove that corresponding apk and odex from origi_app folder and deodex again. (Mostly the apps which can be downloaded from play store might give errors.. ex: Maps, Voice search etc.)
Now you'll see two new folders done_app and done_frame.
Push deodexed app and framework to device:
Connect your device to PC in USB debugging mode.
Copy done_app and done_frame folders to root of sdcard (/sdcard).
Open Windows command prompt and type the below commands.
Code:
[LIST]
[*]adb shell
[*]su
[*]stop
[*]mount -o remount,rw /dev/block/mmcblk0p9 /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/mmcblk0p9 /system
[*]sync
[*]reboot recovery
[/LIST]
In Recovery, Wipe Cache and Wipe Data/Factory reset.
Reboot.
Now you've deodexed app and framework.
For ICS ROMS:
For ICS Roms, the process is quite easy. (Thanks and Credits to jaydvn.)
Download the attached zip file.
Extract it on your windows PC.
Copy your /system/app to _app folder
Copy your /system/framework to _framework folder.
Run AutoDEOToolMain.bat
Follow the instructions.
deodexed jars and apks will be found in deodexed_APK and deodexed_JAR.
Push deodexed app and framework to device:
Connect your device to PC in USB debugging mode.
Copy deodexed_APK and deodexed_JAR folders to root of sdcard (/sdcard).
Open Windows command prompt and type the below commands.
Code:
[LIST]
[*]adb shell
[*]su
[*]stop
[*]mount -o remount,rw /dev/block/mmcblk0p9 /system
[*]rm /system/app/*.odex
[*]rm /system/framework/*.odex
[*]busybox cp /sdcard/deodexed_APK/* /system/app/
[*]busybox cp /sdcard/deodexed_JAR/* /system/framework/
[*]chmod 644 /system/app/*
[*]chmod 644 /system/framework/*
[*]mount -o remount,ro /dev/block/mmcblk0p9 /system
[*]sync
[*]reboot recovery
[/LIST]
In Recovery, Wipe Cache and Wipe Data/Factory reset.
Reboot.
Done.
Enjoy.
Building kernel
Okay. Let's learn how to build kernel for GT-I9100. There are many ways to build. I am just presenting here the way I build and make kernel.
NOTE 1: Follow the instructions exactly.
NOTE 2: Kernel is opensource. If you make any changes to it, you're expected to share your source. (Usually people share it over github )
NOTE 3: FLASHING KERNEL IS RISKY AND DANGEROUS. BE CAREFUL. BUILD AND FLASH ON YOUR OWN RISK.
What you need to have:
Ubuntu 10.04 and above (I use 10.04 )
ARM tool chain (Download HERE. Click on IA32 GNU/Linux TAR under Advanced Packages)
Samsung's opensource kernel for GT-I9100 (Download HERE. Go to Mobile->Mobile Phone-> Select I9100 (update 3 for Gingerbread and update 4 for ICS) and download the zip)
Setting up toolchain:
Extract the tar you downloaded(Suggestion: Extract to one folder where you can have everything. In my case /home/superatmos/build_kernel).
After extracting, you'll see a folder named arm-2010q1. Inside there will be many folders (ex. bin, lib and so on.)
Folder structure will be: /home/<your_name>/build_kernel/arm-2010q1
Setting up kernel:
Extract the zip you've downloaded from samsung's opensource.
You'll find two zips.
Extract GT-I9100_Kernel.tar.gz to /home/<your_name>/build_kernel/
Folder structure: /home/<your_name>/build_kernel/GT-I9100_Kernel
Setting up initramfs:
Samsung's zImage is divided into two parts: Opensource kernel (which you downloaded from samsung's website) and initramfs (which is root file system to boot up the device).
You can extract initramfs from your zImage using the below mentioned links (Credits and Thanks to Chenglu) Original Thread: HERE
To extract initramfs from Gingerbread zImage: HERE
To extract initramfs from ICS zImage: HERE
Folder structure: /home/<your_name>/build_kernel/initramfs
Now the entire setup is ready. Let's start modifying kernel configuration.
Setting up kernel config:
For Gingerbread:
Go to /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/configs folder.
Copy c1_rev02_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Rename c1_rev02_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Modify the below lines (I guess line 195 and 196).
For ICS:
Go to /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/configs folder.
Copy u1_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Rename u1_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Modify the below lines (I guess line 195 and 196).
Code:
ARCH ?= arm
CROSS_COMPILE ?= /home/<your_name>/build_kernel/arm-2010q1/bin/arm-none-linux-gnueabi-
Save and close.
Modifying kernel configuration:
Now open .config file(which you renamed). If its not seen, it might be hidden. Go to View->Show hidden files and there you go.
Do the below things:
Adding local version:
Change CONFIG_LOCALVERSION=" " to anything you like. I add this way:
CONFIG_LOCALVERSION="-I9100-superatmos"
Adding initramfs path:
You need to let kernel know the path from which it needs to take initramfs.
Change CONFIG_INITRAMFS_SOURCE=" " to ../initramfs (In this tutorial it's the path. If you had copied anywhere else, give the path properly).
Enough for now. Once you get experience, you can modify many configurations as per your liking and save. This configuration can be changed by GUI too with the command make menuconfig.
The Important part: Building the kernel:
For Gingerbread:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-I9100_Kernel/
Type make.
For ICS:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-I9100_Kernel/
Type export USE_SEC_FIPS_MODE=true
Type make.
THAT'S ALL. YOUR zImage is ready and is available in /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/boot/zImage.
Install the zImage on the device:
Go to the path where zImage is present and type the below line in command line.
Code:
tar cvf I9100_kernel.tar zImage
Flash the tar using odin.
DONE. CONGRATULATIONS. NOW YOU'VE YOUR OWN KERNEL.
Give me your feedback so that I can improve this tutorial. And post here about how your build went. All the best.
Making custom ROM
Let's move on to make a custom ROM.
Inputs/Feedback/Suggestions are more than welcome. Lets improve this tutorial together for the betterment of the android community.
Steps involved in making a custom ROM:
Getting the system dump from the device.
Deodexing app and framework folders.
Creating various mods by modifying framework and system files.
Modifying build.prop and adding tweaks.
Making META-INF folder and writing an updater-script (edify scripting).
Signing the ROM and making a flashable zip.
Folder Structure:
Before going forward, let's follow the below structure folder to make the tutorial more understandable.
Let our ROM name be CustomROM. The folder structure will be C:\Users\<your name>\CustomROM.
Let's move step by step. Are you ready??
Getting the system dump from the device
Click to expand...
Click to collapse
Make sure USB debugging is ON and connect your device to the PC.
Open command prompt on your windows PC and go to CustomROM folder path.
Type adb devices. You should be able to see the device detected. (If not check environmental variables whether adb is in system path or not. If not present, add the adb path.)
Type the below command to get the dump of system folder.
Code:
adb pull /system system/
Now inside the folder CustomROM, you should be able to see system folder with many folders like app, etc, framework etc inside.
Done with first step.
Deodexing app and framework folders
Click to expand...
Click to collapse
Look HERE how to deodex app and framework folders. Copy the app and framework folders to xUltimate folder, rename them to origi_app and origi_frame and follow the given link to deodex.
NOTE: After deodexing, merge origi_app folder with app folder under C:\Users\<your name>\CustomROM\system\app and origi_frame with framework folder under C:\Users\<your name>\CustomROM\system\framework.
Creating various mods by modifying framework and system files
Click to expand...
Click to collapse
Okay. This the section where your hardwork, innovation and talent comes in. You can use the mods available already, create your own mods, port various mods from other devices and so on.
Below is a list of various mods which can be ported on to GT-I9100. All the credits go these respective thread owners. Thanks to them.
Lidroid 14 toggle mod
Extended power menu with/without header
CRT Off Animation & SIP Over LTE/HSPA
Swipe to remove notifications
NOTE: Let me know more mods with links so that I can add here.
Modifying build.prop and adding tweaks
Click to expand...
Click to collapse
Okay. This is one of those files where you name your ROM(to be visible in settings. ) and add many tweaks.
To name your ROM (to be visible in settings), change the below code.
Code:
ro.build.display.id=CustomROM v1.0
Check the below links for many other tweaks. All credits go to respective thread owners. Thanks to them.
build.prop tweaks by TheFrankenstain
build.prop tweaks by dhlalit11
Making META-INF folder and writing an updater-script (edify scripting)
Click to expand...
Click to collapse
Once you're done with all the modifications, mods and additions, its time to create META-INF folder and make the updater script. Once the user flashes the ROM zip, this is the script that runs and does everything written inside the script. PLEASE BE CAREFUL WITH THIS. TAKE REFERENCE FROM OTHER (SAME DEVICE) ROMS' UPDATER-SCRIPT. (In this case, take reference from other GT-I9100 roms.)
Check the below links for tutorial and how-to on writing edify script and making updater script. All credits go to respective owners of the threads. Thanks to them.
Edify Scripting, Making Flashable ZIPs, ZIP Signing & Key Creation
Edify Scripting Notes
How to Write an Updater-Script with Edify Code
Edify Installation Script Syntax's
NOTE: system folders path, boot/kernel partition path, modem partition path and so on are COMPLETELY DIFFERENT for DIFFERENT DEVICES. Check the partitions for your device properly, carefully and then work on updater-script. TAKE HELP OR REFERENCE FROM OTHER ROM DEVELOPERS FOR YOUR DEVICE.
Lets move on to last step. Making a signing and making a flashable zip.
Signing the ROM and making a flashable zip
Click to expand...
Click to collapse
Make sure, now you should be able to find two folders (META-INF and system) inside C:\Users\<your name>\CustomROM.
Check in THIS thread for test signing your ROM. It WORKS with GT-I9100.
or Check THIS thread to create your own signing key and certificate.
Now you're done with making a custom ROM. Hope to see more custom ROMs from many users.
Give me your feedback so that I can improve this tutorial. And post here about how your custom ROM making went. All the best.
last one
i don't see any tutorials just links to a diff thread and a rom that won't work on i9100
buster041284 said:
i don't see any tutorials just links to a diff thread and a rom that won't work on i9100
Click to expand...
Click to collapse
You're quite fast Updated Deodexing and Building kernel section..
Great thread Superatmos. I'll definately have a go at this.
Quick question ? Am i right in assuming that although your tutorial says to connect your device this line from xUltimate seperceeds that ?
"Alright xUltimate has been updated to v2 What this means is that you do not need your phone connect to your computer to deodex. So you can just manually place the .odex files in (\origi_frame\) and (\origi_app\) and it will deodex. You can also transfer the .odex files from your phone like the last version."
where do I get the zImage to extract the initramfs from? I can't seem to find the zImage on my phone or in the source anywhere.
Great
Very useful.. Added to my favorite.
Thank's man, i'll read that
puccini said:
Great thread Superatmos. I'll definately have a go at this.
Quick question ? Am i right in assuming that although your tutorial says to connect your device this line from xUltimate seperceeds that ?
"Alright xUltimate has been updated to v2 What this means is that you do not need your phone connect to your computer to deodex. So you can just manually place the .odex files in (\origi_frame\) and (\origi_app\) and it will deodex. You can also transfer the .odex files from your phone like the last version."
Click to expand...
Click to collapse
Connect your device to the PC and double click Main.exe inside xUltimate folder. Follow the instructions you see from then. Its quite self explanatory.
If you already have origi_app and origi_frame folders, then just double click on Main Skip.bat.
dmp450 said:
where do I get the zImage to extract the initramfs from? I can't seem to find the zImage on my phone or in the source anywhere.
Click to expand...
Click to collapse
Use ktool (available on market.. compatible with I9100) and click on Dump current kernel. You'll find it on sdcard.
One more way is when you download firmware from sammobile.com, just extract the file and you'll find zImage inside it.
Nice thread,
I m waiting from long time.
Thanks for your work.
Sent from my GT-I9100 using XDA
Making custom ROM section updated
Hi all,
Please find updated custom rom section HERE.
Feedback and suggestions welcome.
Thanks for the kernel part, will come in handy
Enviado desde mi GT-I9100 usando Tapatalk 2
Good tutorial, thanks.
How do you guys sign the rom if you are on Linux (ubuntu for me)
hi superatmos
thanks for this handy thread...may i ask your for a help here?why in my every deodexing always gives error result?
I attach the screenshots.
Many thanks in advance
tks mate will try to pack my own kernel following this method
Sent from my GT-I9100 using Tapatalk 2
Follow thread http://forum.xda-developers.com/showthread.php?t=2173465
First of all , I'm not responsible for any damage..
Of course that's a rough explanation(i really need to hit the bed) but I hope you get the idea and someone will create more clearer and friendly instruction/guide/how-to/whatever.
When flashing L9 , LG App extracts files into C:\ProgramData\LGMOBILEAX\Phone ,
LGP769_AP[6].bin (contains /system partition which includes hdcp.sh) and that can be easly modified(image) and replaced during flashing process.
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push rooting.sh /data/local/tmp/
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/rooting.sh
Follow thread http://forum.xda-developers.com/showthread.php?t=2173465
Downloading 10g kdz now. Will post back after I try to work this out. Thanks alot dude.
@lelus,
I am old dos buzz, so looking at the hexediting done by you in the BIN file, I can say that I am getting some hints.
You are suggesting to quietly replace the BIN file, in the middle of flashing KDZ file (when it is extracted to following folder), right?
C:\ProgramData\LGMOBILEAX\Phone\LGP769_AP[6].bin
The question is at which point the BIN file is to be changed? I still am confused with the sequence of BIN file replacement, scripts and files pushed via ADB. When these procedures are to be done? before flashing or after flashing?
I get hint that, you have modified BIN file to bypass the script file "hdcp.sh" which is used by LG Tool while flashing and instead of that, you are instructing to push+execute modified script "/data/local/tmp/rooting.sh". This new script is added in the beginning of BIN file, does that mean it will be executed everytime we reboot the phone? I may be wrong, just wanna clarify.
I dont have P769 device (good for me ), else I would have try that by now.
You can push the files and set permissions.
Flash your phone once to copy LGP769_AP[6].bin (it goes up to [10] and takes some time to extract the files, there should be enough time) from C:\ProgramData\LGMOBILEAX\Phone\ to some location.
Modify LGP769_AP[6].bin with a hex editor
Flash you phone once again,just like before you'll see lg flash tool decompressing files into C:\ProgramData\LGMOBILEAX\Phone\, when you see it done with LGP769_AP[6].bin copy/replace original with modded file, like before there should be enough time for it. Phone should be rooted after reboot.
hdcp.sh is setuid root and is executed at boot
Re: root p769 v10g and possibly other variants
Im very new to rooting. I've only rooted one phone(lg optimus p509). I now have my fancy new p769 and want some superuser action. I've been doing a lot of reading, and frankly, im worried about bricking or screwing up my new phone! When the more indepth description of your new found genius is released, could you please include details on exactly how to keep my phone safe and unbricked..THANKS!
Sent from my LG-P769 using xda premium
matts0807 said:
Im very new to rooting. I've only rooted one phone(lg optimus p509). I now have my fancy new p769 and want some superuser action. I've been doing a lot of reading, and frankly, im worried about bricking or screwing up my new phone! When the more indepth description of your new found genius is released, could you please include details on exactly how to keep my phone safe and unbricked..THANKS!
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
As you say you are very new, I advice do not try this method at the moment. its very serious and you may brick your phone.
OK. My phone now rooted. But I only get root in adb shell only. Other root required app in phone don't popup Superuser dialog. My app cannot gain root access even I set "Automatic Response" to "Allow". Any Idea?
My phone firmware is p768f V10D, hdcp.sh is in LGP768_AP[5].bin. For other model I think your method should work if you can find proper file to edit (with hex edit).
Ha. Finally work. I replace su and Superuser from their website (After trial and error I don't know what the problem at first). I'm not sure if improper edit .bin file will brick your phone. So wait for some dev to confirm it. If you're not familiar with Hex editor I don't suggest you do this for now.
This may make me sound stupid, but could someone please post a clear set of directions to follow for this method. I think I understand it, but this is my only phone at the moment, and I don't want to screw it up because I swapped up a couple of steps.
For people who want to root LG L9 ICS Phone, please follow this guide http://forum.xda-developers.com/showthread.php?t=2173465
The method in this thread lack some steps to clean out rooting staff and script
For those who interest, below are the steps I did to root my phone from Lelus post info.
*** Please read it carefully and understand every step before you try. I cannot help you if you brick your phone. And please note that I'm not a android dev and these steps work for Lelus P769 10G and my P768f 10D. It should work in all variants but I'm not guarantee. ***
0. Find your KDZ at http://forum.xda-developers.com/showthread.php?t=2107971
1. Manually extract my kdz with LGExtract 0.2.1 from http://forum.xda-developers.com/showthread.php?t=1566532
2. Copy kdz (my file is V10D_00.kdz) and LGExtract.exe to C:\root\ , In command prompt just run
C:\root>LGExtract.exe -kdz V10D_00.kdz
3. You got V10D_00.cab
4. Extract cab with 7z or other zip program that can handle .cab (Google for it if you don't have it yet.) you got 2 files. LGP768.dll and V10D.wdb
5. Extract wdb with following command
C:\root>LGExtract.exe -wdb V10D.wdb LGP768.dll
*** don't forget my model is P768, you should change it to match the file you got ***
6. You'll found extracted files in BIN directory. After this step use your favorite Hex edit to search for hdcp.sh . I found it in LGP768_AP[5].bin. If you copy text from hex edit it look like following
# hdcp.sh
#
# [email protected], [email protected] , [email protected]
#
# HDCP sh file
#!/system/bin/sh
if ls /persist/mhl/key.bin ; then
echo "alreay exist" > /data/mhl.log
/system/xbin/hdcp-init 1 3 >> /data/mhl.log
echo "step 1 : hdcp on" >> /data/mhl.log
else
if ls /persist/en_hdcp.bin ; then
rm /persist/en_hdcp.bin
fi
echo "not exist" > /data/mhl.log
fi
7. In your hex editor, try to edit that file to following
#!/system/bin/sh
/data/local/tmp/rooting.sh
#.com , [email protected]
#
# HDCP sh file
#!/system/bin/sh
if ls /persist/mhl/key.bin ; then
echo "alreay exist" > /data/mhl.log
/system/xbin/hdcp-init 1 3 >> /data/mhl.log
echo "step 1 : hdcp on" >> /data/mhl.log
else
if ls /persist/en_hdcp.bin ; then
rm /persist/en_hdcp.bin
fi
echo "not exist" > /data/mhl.log
fi
*** for those who not familiar with Hex edit you must edit both left (HEX) and right side (TEXT) of editor because some characters is not on keyboard (ex. ENTER, just type 0a in left side editor to make ENTER key).
8. Trial and error until your copy text look like code above (you can copy your edited text from hex editor to text editor to examine it). Then save your file.
9. Next step is download all required file from Lelus link (or from my root.7z) and place them in C:\root
10. In command prompt run
cd C:\root
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push rooting.sh /data/local/tmp/
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/rooting.sh
*** You can use adb.exe from http://forum.xda-developers.com/showthread.php?t=2085344 thread if you don't install android delveloper tools
11. All files should upload to your phone. After this step try to flash your normal unextracted kdz. You should open C:\ProgramData\LGMOBILEAX\Phone while flashing your rom. After kdz flash program show about 8% progress you should see that there are extract .bin files in that directory. Just quickly copy your edited .bin file (only the file that contain hdcp.sh script) and replace extracted file with it. *** you should wait for flash program to finish extract your file before replace it. ***
Read about how to flash your phone at http://forum.xda-developers.com/showthread.php?t=2085344
12. Done. You phone reboot with Superuser app install. If you have any problem like me that Superuser app don't popup to ask permission, please download latest version from http://androidsu.com/superuser/. I also upload updated files in root.7z below.
13. From Lelus' suggestion : After rooting I would probably suggest
adb shell rm /data/local/tmp/rooting.sh
adb shell touch /data/local/tmp/rooting.sh
adb shell chmod 755 /data/local/tmp/rooting.sh
Thanks Lelus for sharing this, :good:
Edit : Add updated Su, Superuser, LGExtract.exe, hex editor image and rooting.sh
Good one artit.
Do you think all LGP768_AP[5].bin (or other variants) are the same file (so we can uploaded a modified one and everyone can use it)?
Would this be a universal way of rooting all LG phone?
Thank You Lelus!
If this works everyone should click the "Thanks" button on Lelus' post.
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
chicguy said:
Good one artit.
Do you think all LGP768_AP[5].bin (or other variants) are the same file (so we can uploaded a modified one and everyone can use it)?
Would this be a universal way of rooting all LG phone?
Click to expand...
Click to collapse
No. All bin files will be different since it holds the partitions and files that are loaded on the devices.
What I means is within the same variants, would it be the same kdz file downloaded? Then we can upload one bin file corresponding to each kdz file?
artit said:
1. Manually extract my kdz with LGExtract 0.2.1 from http://forum.xda-developers.com/showthread.php?t=1566532
2. Copy kdz (my file is V10D_00.kdz) and LGExtract.exe to C:\root\ , In command prompt just run
C:\root>LGExtract.exe -kdz V10D_00.kdz
3. You got V10D_00.cab
4. Extract cab with 7z or other zip program that can handle .cab (Google for it if you don't have it yet.) you got 2 files. LGP768.dll and V10D.wdb
5. Extract wdb with following command
C:\root>LGExtract.exe -wdb V10D.wdb LGP768.dll
*** don't forget my model is P768, you should change it to match the file you got ***
6. You'll found extracted files in BIN directory. After this step use your favorite Hex edit to search for hdcp.sh . I found it in LGP768_AP[5].bin. If you copy text from hex edit it look like following
Click to expand...
Click to collapse
Welldone! Artit! Thanks a lot.
For this same above process I have made a quick and small batch file of KDZ extraction tool and it keeps LGP768_AP
[*].bin files in single folder for further use.
By the way, when I looked for hdcp.sh in P760V10I, I found hdcp.sh in LGP760_AP[6].bin exactly as mentioned by Lelus. It seems the location of this text is different in BIN file and when extracting it goes to any piece of BINs, not always in 6th piece.
EDIT: Are you using Offline Flash method? Or online?
chicguy said:
What I means is within the same variants, would it be the same kdz file downloaded? Then we can upload one bin file corresponding to each kdz file?
Click to expand...
Click to collapse
I do not know.
I have modified .bin files for 11A and 10G on my home pc. I will upload them when I get home later if no one has already.
rooted
Thanks. Now i got P769bk us tmobile rooted.
Hash editor each hash key must match in same place. sd card removal helped.
Uploaded the V10g modded binary for P769. MD5 checksum included, but I forgot to change the directory in the file that checks it (but you can change it).
filedropper[dot]com/lgp769v10g-bin
gigasize[dot]com/get/t23b42m76yc
MD5: c2cbf3997a9ab7181c71c75d697db6f5
Where is the www[dot]zip file for the OFFLINE FOTA method of flashing (/showthread.php?t=2085344)?
EDIT: Please disregard this post. This was a result of a corrupted download. shttps.zip will include the www directory.
V11a rooted as well!
Whats sup guys?I been using dragonface to make custom roms for my android device.So i decided to make a guide showing you how to make your own.Enjoy.Make sure to thank me! alright lets get started
Basic Requirements: - Dragonface V2.2.0 V2.2.3 (download here in this Forum)
- Dragonface Tutorial, and knowledge of the basic functions (download here in this tut)
- Windows Explorer
- Notepad++ (http://notepad-plus-plus.org/download/v6.6.9.html)
- ROM you want to modify
- Phoiexcard
If additional tools are requiered, they are mentioned in the regarding Instruction.
Common Steps for all modifications: STEP 1: extract your ROM (*.img) with Dragonface
STEP 2: change to Windows Explorer
ATTENTION: don't shut down DragonFace or copy the needed directories and
files some where else if you want to work "offline" (Directories: CPFOP, fsop -
Files: sysconfig.lhs), because DragonFace erases everything while shuting
down
STEP 3: Save the modified ROM with Dragonface
ATTENTION: If you worked "offline", do first Step 1, and then replace the
created Directories/Files with your modified
STEP 4: Flash your ROM (.img) with the Onda Suite
So let`s start.
PS.: If you try your own modification, it would be good to make only one after the other, and test between two modification. This makes it easier to solve problems when it´s not working like you except it, because you know what causes the problem.
HowTo - Increase the available space for your Apps (Firmware V1.0.0 - V2.1.3 all Versions)
1. You have done Step 1&2 in the first post
2. Now navigate to the following directory with the Windows Explorer ( must be set to show hidden Files/Directories!)
c:/User/..your Username../AppData/Local/Temp
3. Find the file sysconfig.lhs
4. Open it with Notepad++
5. Navigate to the following:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 4194304
user_type = 0x8000
6. Now change the value of size to the space you want
The current value of 4194304 stands for 2GB, that means you have to multiply 2097152 by the amount of GB you want to have for your Apps
for example: 6GB = 12582912
7. Save sysconfig.lhs
8. Save .img in Dragonface
9. Flash your ROM - Done!
Her is a link to a video tutorial (in chinese): http://v.youku.com/v_show/id_XODEzODEwNzQ4.html&usg=ALkJrhhE_ACHQznY8ibrYYK7wMCYzcWCJg
Since the test version of Android 5, there is no seperat app partition in the firmware anymore.
HowTo - PreRoot your ROM (Firmware V1.0.0 - V2.0.2 all Versions)
1. You have done Step 1&2 in the first post
2. Now navigate to the following directory with the Windows Explorer
.../Dragonface_2.2.0/CPFOP/bootfs/skel
3. Find the file init.rc
4. Open it with Notepad++
5. Insert after Line 293:
su root
chown root root /system/app/superuser.apk
chown root root /system/xbin/su
chown root root /system/xbin/daemonsu
chown root root /system/bin/.ext/.su
chown root root /system/etc/.installed_su_daemon
chown root root /system/etc/install-recovery.sh
chown root root /system/etc/init.d/99SuperSUDaemon
chmod 6755 /system/xbin/su
chmod 6755 /system/xbin/daemonsu
chmod 0777 /system/bin/.ext
chmod 6755 /system/bin/.ext/.su
chmod 0644 /system/etc/.installed_su_daemon
chmod 0755 /system/etc/install-recovery.sh
chmod 0755 /system/etc/init.d
chmod 0755 /system/etc/init.d/99SuperSUDaemon
chmod 0644 /system/app/superuser.apk
chmod 0755 /system/xbin/busybox
6. Save init.rc
7. Now navigate to the following directory with the Windows Explorer
.../Dragonface_2.2.0/fsop/system
8. create the directories and place or replace the needed files if not already present (check filesize, paths and files see
Step 5)
Download needed files here: https://mega.co.nz/#!XU5EFaBK!9ZFnDrzJnlGWoMOISkzQ-dczBKUB6cM8O3aswEjI2IY
Attention: Windows Explorer is not able to create the directory /system/bin/.ext, because it doesn't like the
leading dot.
So open "Command Prompt" and type mkdir .ext to create the directory (navigate before to ..system/bin)
9. Save .img in Dragonface
10. Flash your ROM - Done!
HowTo - PreRoot your ROM (Firmware V2.1.0 - V2.1.3 all Versions)
Step 1 - 10 are the same, only change:
Step 5:
chmod 0755 /sbin/busybox (Instead of: chmod 0755 /xbin/busybox)
Important: If you reopen a prerooted ROM with Dragonface, you have to recreate the .ext folder again and place .su again in it. During the extracting the .ext folder disappears due the restrictions of Windows. Saving without recreating breaks the prerooting!
HowTo - Theming your system:
The following instructions are made for the new V2.1 Firmware and should work with all Versions.
Indroduction: now we start modifying existing APPs. In the first step there are HowTo´s which can be easy done without using any app tools. The simple reason for that is, as long as we don´t take away or add graphics inside an app, and only modify them, for Android everything is fine. When we start to add or remove files inside the app or we want to change the behaviour of an app or add Features, for example in the Settings menu, we will need to de- and recompile and sign the app, ortherwise it won´t work. But this will come later.
Change the default Wallpaper:
additional needed programs: WinRAR
1. First find a Wallpaper you like with a Resolution of 2048*2048 and .jpg format, and save it to your computer
2. Rename the Wallpaper to default_wallpaper.jpg
3. Do the steps 1&2 in the first Post
4. Navigate to fsop/system/framework and find: framework-res.apk
5. Open it with WinRar and navigate to the folder drawable-nodpi
6. Now insert your Wallpaper with drag´n drop
Attention: There is now a Window popping up and asks you what to do. Choose under "COMPRESSION
METHOD" on the left side the option "SAVE".
When you look on WinRar you see that the pictures aren´t compressed, so just leave them
uncompressed.
7. Close WinRAR and you are done!
8. Save .img in Dragonface
9. Flash your ROM - Done!
Change the Wallpaper on the LockScreen (Firmware V2.1.0 - V2.1.3 all Versions)
additional needed programs: WinRAR
1. First find a Wallpaper you like with a Resolution of 2048*2048 and .jpg format, and save it to your computer
2. Rename the Wallpaper to wallpaper_03.jpg
3. Do the steps 1&2 in the first Post
4. Navigate to fsop/system/priv-app and find: JuiKeyguard.apk
Alternativ, on a running system, copy JuiKeyguard.apk to your PC, make the changes descriped in the next
steps and copy the modified apk back to the tablet. Don't forget to set the right permissions for the apk.
5. Open it with WinRar and navigate to the folder drawable-nodpi
6. Now insert your Wallpaper with drag´n drop
Attention: There is now a Window popping up and asks you what to do. Choose under "COMPRESSION
METHOD" on the left side the option "SAVE".
When you look on WinRar you see that the pictures aren´t compressed, so just leave them
uncompressed.
7. Close WinRAR and you are done!
8. Save .img in Dragonface
9. Flash your ROM - Done!
When you chance the Lockscreen Wallpaper direct on the tablet (already running system), wipe the Dalvik Cache, otherwise the Wallpaper won't change.
Change the icons in the Statusbar
additional needed programs: WinRAR
Paint.net (optional)
1. Do the steps 1&2 in the first Post
2. Navigate to fsop/system/priv-app and find: JuiSystemUI.apk
3. Open it with WinRar and navigate to the folder drawable-xhdpi
4. Look for the icons you want to change and notice the resolution
Optional: you can edit the icons by using Paint.net
5. Replace the icons you want with drag´n drop or replace the icon with an already existing in the folder (make a duplicate and rename the duplicate to the correct filename)
THEY SHOULD HAVE THE SAME RESOLUTION AND MUST BE IN .PNG FORMAT!
DON`T ADD OR REMOVE ICONS, ONLY REPLACE THEM USING THE CORRCT FILENAME - OTHERWISE YOU
CORRUPT THE APP
IF YOU WANT TO ADD OR DELETE ICONS OR ADD NEW FEATURES YOU HAVE TO DE- AND RECOMPILE IT
Attention: There is now a Window popping up and asks you what to do. Choose under "COMPRESSION
METHOD" on the left side the option "SAVE".
When you look on WinRar you see that the pictures aren´t compressed, so just leave them
uncompressed.
6. Close WinRAR and you are done!
7. Save .img in Dragonface
8. Flash your ROM - Done!
Enjoys and press Thanks!!!!!!!!!!!!!!!!!
Dragonface software
Hello,
Are there any guides/tutorials for the Dragonface software in english anywhere please? I have googled but they are in Chinese or some other other language. Something for Dragonface v2.2.5 would be appreciated.
Thank you.
trustytrev.
Sir this is tutorial for dragonface in english
more space for apps in V989 v1
Hello,
firmware
989 Air Core8 v1.0.6_v2.img
onda v989 v1
I use dragonface to add space for apps. then i use phoenixsuite to apply img file modified... but it no works!
i need to back 989 Air Core8 v1.0.6_v2.img
this table have 2Gb for apps 2gb RAM and 32Gb more...
heeelp please
Devmountsu77 said:
Sir this is tutorial for dragonface in english
Click to expand...
Click to collapse
Hello,
Sorry I was meaning how to video tutorials of using the dragonface software in english.
I have now found something that was suitable for me as a complete novice.
Thank you.
trustytrev.
A83T
I have tried using Dragon Face for A83T image file. But looks like I am stuck.
The Software does unpacking properly. But during packing image, I am not sure what goes wrong, the initial Green Progress bar of Flashing Firmware also does not show up in the device.
I have in fact tried - unpacking stock firmware and packing the firmware without making any changes to the Image.
It fails!
Any help will be greatly appreciated.
bumping this old thread trying to root this POS irulu tablet I got the firmware image rooted and resaved
flash it but it hangs at the pre-boot splash
edit: I am pretty sure its either a int.rc or su binary problem, if I flash just the stock boot/env it boots
so there is something in the init.rc it doesn't like
here is my init rc
https://pastebin.com/NwZ9ntEB
after hours of monkeying about with it I am pretty sure its a issue with dragonface
any attempt to modify int scripts results in it hanging on splash, possibly some form of boot image checking
I can modify system all day long but I can't touch the boot partition
I don't have the capability to build a generic twrp image for the A33 so I can't even get to a decent recovery
Bringing this thread back to life, is there a way to set the default launcher through file manipulation (as with the above tutorial) rather than with ADB or in the Android Settings app? I've been searching, but haven't found any good information.
Edit: Nevermind, it was an issue with the default launcher and possibly pheonixcard. Got it resolved
Aug 28 (21 hours ago)
I have tried so many options/blogs/scripts to install GooglePlay for Emulator (running through Android Studio) but it never works. I have seen so many different errors
1. Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
2. Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
3. No space left on /system
Why is it so hard to install GooglePlay on Emulator, can someone provide steps or GApps that work with Marshmallow/Noughat.
Here's the gist of what I have tried :
1. Copy GApps from http://opengapps.org/ [ Platform: x86_64; Android: 6 & 7; Variant: full ]
2. Extract the zipped file to temporary folder and then extract following apks from it to another folder
* gsfcore-all/nodpi/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
* gsflogin-all/nodpi/priv-app/GoogleLoginService/GoogleLoginService.apk
* gmscore-x86_64/nodpi/priv-app/PrebuiltGmsCore/PrebuiltGmsCore.apk
* vending-all/nodpi/priv-app/Phonesky/Phonesky.apk
3. Try pushing these apks through this script
IMAGE_NAME=Nexus_5X_API_24 #Nexus_5X_API_23
emulator @${IMAGE_NAME} -no-boot-anim -writable-system &
adb wait-for-device
adb root
adb shell stop
adb remount
adb push PrebuiltGmsCore.apk /system/priv-app/
adb push GoogleServicesFramework.apk /system/priv-app/
adb push GoogleLoginService.apk /system/priv-app/
adb push Phonesky.apk /system/priv-app/
I would really appreciate any help !!
Hello and welcome to XDA Q&A section of the Forums.
In the .zip file you got from GApps, there should be a thing called "updater-script" located in the first folder then the subfolder of that and so on till you find it. In this script it tells your recovery what do you with the file rather than just smile at it . I guess you can say it is time for a human to do those steps manually instead (I guess you can say that).
If I helped, hit "thanks" .
Its not clear by your comments what you are suggesting, you mean to say that I should read this script "updater-script" and apply those steps manually ?
maqzee said:
Its not clear by your comments what you are suggesting, you mean to say that I should read this script "updater-script" and apply those steps manually ?
Click to expand...
Click to collapse
Yup! Use notepad++ to view it btw, good luck! At least it's not smali code.
I'm not responsible for any damage!
Tested on Galaxy A5 2017, SM-A520F, a5y17lte.
The rendering of the backlight management does not give the same result as on the original rom.
Here are more pleasant values for the user (less aggressive)
For this it is necessary to use RRO, (Android Runtime Resource Overlay Framework)
I made a request on gerrit of lineage, maybe the developer will look at this problem.
Prerequisites:
To be able to follow along, you'll need the following:
the latest version of the Android SDK.
Change the values you want to test and run makeit
Install the APK:
the apk must be installed in /system/vendor/overlay but the /system/vendor/overlay directory doesn't exist.
You must create it manually yourself!
run:
adb shell
mkdir -p /system/vendor/overlay
exit
Push the APK to the directory using adb.
run:
adb push myoverlays.apk /system/vendor/overlay
Restart your device (soft boot works too), Enjoy
WARNING
if you update lineage, this overlay is cleared.
if you start again like that you'll get a bootloop!
if you have this, restart in recovery and delete "/data/resource-cache"
To remove these changes:
1) delete "/system/vendor/overlay/myoverlays.apk"
2) delete "/data/resource-cache"
3) reboot
Download:
Github: https://github.com/f5bud/MyOverlays
myoverlays.apk: https://github.com/f5bud/MyOverlays/raw/master/myoverlays.apk