Got my HTC Desire Z flashed to CM10.1 and have some tweaked but after I take two optimized commands into the file
/system/etc/init.d/00banner
Commands are about to boost up the reading speed of SDcard, type like
/system/xbin/echo "4096" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
/system/xbin/echo "4096" > /sys/devices/virtual/bdi/default/read_ahead_kb;
Actually I modified these files with RecoveryFileManager at first but I found that was failed after I reboot the device, so I just type these commands into the init.d, but after that, I just find my status bar and notification bar was lost and disappeared, not only home screen but also all around the surface in the system.
Is anyone could help here? Thank you very much!
Best.
take the systemui.apk and the frameworkres.apk and also the init folder from your cm10.1 zip and replace the current ones in your rom using root explorer.
these are located in system/app folder and the init folder is in system/etc
do not remember to ser the permission after replacing.
if this doesnt work just flash your cm10 zip again without wiping anything you will get your statusbar back.
hit thanx that means a lot to me.
Sent from my K-ONE using xda app-developers app
Related
Can anyone guide me how to enable CRT animation for stock android 2.3.3 on galaxy ace?
codestudent said:
Can anyone guide me how to enable CRT animation for stock android 2.3.3 on galaxy ace?
Click to expand...
Click to collapse
I think you should have posted this in themes and apps section but nevertheless this is your answer-
You will need-
a)APK Manager from here http://forum.xda-developers.com/showthread.php?t=695701
b) .zip manager (I suggest 7-zip or winrar for windows and archive manager for linux)
c) text editor ( Notepad++ in windows or gedit/write in linux )
d) framework-res.apk from /system/framework that you want to modify and build.prop from /system.
e)Root explorer/Fileexpert or adb to pull framework-res.apk and build.prop
First thing using root explorer or adb pull the above files to your computer.Then do the following..
1) Once you extract APKManager you should have a folder called "APKManager," somewhere.
2) Within that folder there's another folder called "place-apk-here-for-modding". Place you desired framework-res.apk into that folder.
3) Navigate back to the root of "APKManager", and double-click "Script.bat"in windows or "Script.sh" in linux
4) Press option 9 to decompile the apk. (It may take some time)
5) Once finished, navigate to "APKManager\projects\framework-res.apk\res\values".
6) Inside look for a file called "bool.xml". Open it using your notepad++ or gedit
and find and change the
"<bool name="config_animateScreenLights">true</bool>" to "<bool name="config_animateScreenLights">false</bool>"
7) Remember to save! Not "save as," but save.
8) Doubl-click "Script.bat" or "Script.sh"again, and choose option 11 to sign the apk
9) Say "y" to first option.
10) When that is done, a new folder called "keep" will be created. Open that folder, and delete resource.arsc.
11) Say "y" to the last option.
12) It will ask you to press any key, do that, and it will finish.
13) Navigate to the "place-apk-here-for-modding" folder, and you'll see a new file called, "unsignedframework-res.apk" open it with a .zip manager, and take the resource.arsc file from it, and transfer it to your original framework-res.apk (Which should be in the same folder)
14) Now push the modified original framework-res.apk(with new resource.arsc) onto your phone /system/framework using adb or copy by root explorer/fileexpert, and set permissions using root explorer to -rw -r -r or use chmod 644 framework-res.apk using adb. There wil be force-closes using root explorer when copying..just ignore that and set permissions and reboot.
15) Now pull build.prop from /system to your computer
16) Open build.prop and modify the line.
'debug.sf.hw=1' is the line in the file. Replace it by '#debug.sf.hw=1'. Indirectly you are just changing the line into a comment by adding a #
17) Now take this file and replace your original build.prop. You can do this by using adb or root explorer and set permssions similarly as in above.
18)Reboot and go to settings>>display>>animations and choose all animations. Enjoy your crt screenoff animation.
Added the guide in themes section http://forum.xda-developers.com/showthread.php?p=15976400
did as told but no luck. I'm using S5830XEKPH 2.3.4 firmware (Booted)
I have just noted that root explorer is not replacing framework file with the new one.
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
Hi! I have a very odd problem: somehow my SystemUI.apk mods won't keep (i.e. after pushing, the XML edits are reversed to stock). I'm attempting to remove the brightness slider. It should be a simple edit to the tw_status_bar_expanded.xml: add the red code; many others have used this edit successfully (Verizon GS3, international GS3, etc.):
Code:
<LinearLayout android:orientation="vertical" android:id="@id/brightness_controller" [B][COLOR="Red"]android:visibility="gone"[/COLOR][/B] android:background="#ff000000" android:layout_width="fill_parent" android:layout_height="56.0dip">
However, it didn't work on my phone, even after three attempts. So, on a hunch, I edited something totally different:
Code:
android:background="ff000000"
to
Code:
android:background="00000000"
-- which should make the brightness bar transparent: that didn't work after pushing, either! Frustrated, I pulled the SystemUI.apk back and saw that...somehow...the XML had "reverted" back to stock, showing
Code:
[B]android:background="ff000000"[/B]
Here's my "flow," if anyone can diagnose this wacky issue:
1. Use Virtual Ten Studios (an IDE, integrated development environment) to pull SystemUI.apk (after installing framework-res.apk resources).
2. Create backup of SystemUI.apk
3. Edit XML in SystemUI.apk -> save -> recompile and zipalign.
4. Copy AndroidManifest.xml and META-INF folder from backup apk to modded apk.
5. Boot phone into recovery -> push modded SystemUI.apk to /system/app [states that it pushed correctly] (I do recovery because, as I just learned, you can't push to a phone that's on, if it has a secure kernel; adb remount or adb shell mount still yield permission denied, but recovery doesn't!).
6. Reboot.
I thought it was just a fluke, but I ran the experiment again, this time changing the color of the bar: ff000000 -> ff000001 (left is XML before pushing; right is XML after pulling): http://prntscr.com/qoqcx
Thought it could be a permissions issue, but I ran adb shell -> chmod 644 /system/app/SystemUI.apk from recovery. Still doesn't work! I pulled the just-modded pushed APK and, boom, there it lies with none of my edits. :/
Any thoughts out there?
There's got to be a reason... My phone can't be a demon. Right?
For what it's worth, I've successfully flashed a SystemUI.apk as a flashable zip, so my phone isn't immune. There's just something wrong with my process....
A friendly bump because of subforum change!
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
hi Everyone,
I'm sticked with the common issue of how to make writable the external SD.
I've read topics on the forum:
http://forum.xda-developers.com/desire-601/help/how-to-writable-external-sd-kitkat-t2877686
http://forum.xda-developers.com/desire-601/help/sd-card-permissions-off-t2833195
http://forum.xda-developers.com/showthread.php?t=2687734
Well ok, but I'm a noob so sometimes it's not clear, sometimes it's not working for me.
So let's explain:
- My device is rooted (it was made by a tech using TWRP if I'm right)
- SuperSU is installed
1/ I tried some apps like SDfix and Int-SDCard Write fix
> Result = KO
2/ I tried to manually modify the platform.xml file > sometimes the editor does not want to save the modification, sometimes it says OK but the file don't seem to be modified (the last modification date is still 2014). Permissions are: rw-r--r--
a. Using Rom Toolbox, I go the file and edit it with:
-FX TextEdit > Get a Warning = "This file is on read-only filesystem. You will not be able to save any changes unless you first remount it as read/write'
> Result = KO
- RB Text Editor: it seems i can edit it. Save the file without warning message 'Saved'. But once back on the /system/etc/permissions folder, nothing looks modified (not today's date). I can reopen the file and see the modification by the way. But once I reboot, I go back the my original issue.
> Result = KO
- ES Text editor: can't even save the file
> Result = KO
So what ?
I've seen this message coming along:
"if you are rooted then you doing something wrong (did you maybe forgot to mount system as R/W ?).
If you are unable to do modify platform.xml then you doing something wrong or yours device isnt rooted."
> At what moment is it possible to mount the system with R/W grants ?
I'm fed up with not being able to write on SD card....................
Thx in advance !!!!!
Opening a terminal on my phone:
- i can't 'cp file1.xml file2.xml' in /system/etc/permissions
- i can't 'chmod 644 file1.xml'
Each I get "Read-only file system"
Flash your stock kernel with insertcoin or kofilakernel