Related
I have CM7 installed... I know there are settings for screen timeout under display, and CM7 settings allow you to specify the delay for the screen to actually lock. But what about when the screen is locked, you turn it on to check the time and it shuts off after 5 secs. Can this be changed?
Edit: Here's a list of important posts so people don't have to read the entire thread...
Background Info
Step-by-step guide for windows
Allow .jar files to be seen in APK Manager
How-to deODEX android.policy.jar for ODEXed ROMs
How-to for linux/mac(will make a better guide once I finish porting the APK Manager tool from Windows)
Old Stuff:There's not a setting to change the lock screen timeout but I got to looking around and think I found where it can be changed. The stuff I found pointed to android.policy.jar which is located in /system/framework so I adb pulled it and then decoded it using apktool. Some smali files contain hex values of 0x1388 equals 5000 in decimal where 5000ms = 5s. So one of those should be what we want to change. I'm going to try figuring out which one to change, set it to 10s = 10000ms = 0x2710. If it works for me, I can describe how to do it yourself in better detail and/or post a modified android.policy.jar with the timeout you would like.
Edit: I started a thread about this in the Eris dev forum and removed the attached files from here. PM me or post in one of these two threads if you have questions or would like me to modify and send you a custom android.policy.jar
http://forum.xda-developers.com/showthread.php?t=1079844
I successfully increased the default 5s timeout when you wake the phone but don't unlock. If you want to test it out, download one of the attached zip files corresponding to the timeout you would like to have(10s or 30s). Extract android.policy.jar from the zip file and follow either the ADB or Root Explorer or Terminal Emulator instructions below.
If using ADB:
Code:
adb remount
adb shell
cd /system/framework
mv android.policy.jar android.policy.jar.bak
exit
adb push android.policy.jar /system/framework
adb shell
cd /system/framework
chown 0:0 android.policy.jar
chmod 644 android.policy.jar
#reboot to recovery#
#wipe both cache and dalvik-cache#
#reboot#
If using Root Explorer on phone:
mount system as r/w
rename original android.policy.jar in /system/framework to android.policy.jar.bak
move modified android.policy.jar to /system/framework
change owner: owner = 0 - root & group = 0 - root
change permissions: rw-r--r--
#reboot to recovery#
#wipe both cache and dalvik-cache#
#reboot#
Click to expand...
Click to collapse
If using Terminal Emulator on phone:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/framework/android.policy.jar /system/framework/android.policy.jar.bak
mv /PATH/TO/NEW/android.policy.jar /system/framework
cd /system/framework
chown 0:0 android.policy.jar
chmod 644 android.policy.jar
#reboot to recovery#
#wipe both cache and dalvik-cache#
#reboot#
Later tonight or tomorrow I will post a how-to so anyone can make the necessary modifications themselves. That should allow for other devices/ROMs to modify theirs as well since it will be customized to their phone.
I've only tested this on my Eris running GSB v3.1 - Gingerbread 2.3.4 - CM 7.1.0 RC0. Be sure to make a NAND backup and a backup of android.policy.jar as I can't guarantee this will work for you. If you have problems or just want to switch back to the original 5s timeout, replace the modified android.policy.jar with the android.policy.jar backup, wipe cache & dalvik-cache, and reboot or restore from the NAND backup you created.
I'm really surprised no one has brought this idea up before..well glad I had a chance to give you something to dig into and explore some more. I haven't done any editing to system files like this before so I might be posting back with some questions. Thanks for the info..I'll let you know how it goes!
When I plug my phone in it doesnt seem to be going into debugging mode. I have that option checked for it to enable when USB is plugged in but the only icon showing is the USB icon.
I say this because when I run adb devices its not listing my device..also running adb shell it says error: device not found
I havent tried running the adb shell since I flashed to CM7..is there something I need to do differently with this ROM?
thetornado said:
When I plug my phone in it doesnt seem to be going into debugging mode. I have that option checked for it to enable when USB is plugged in but the only icon showing is the USB icon.
I say this because when I run adb devices its not listing my device..also running adb shell it says error: device not found
I havent tried running the adb shell since I flashed to CM7..is there something I need to do differently with this ROM?
Click to expand...
Click to collapse
The debugging notification will only show up if the option for "USB debugging notify" is also checked in Settings->Applications->Development. Not sure why it wouldn't be able to find your phone especially since it sounds like you had it working fine before. What version of adb do you have? I'm using v1.0.26 and never had any problem. You can check the version with the command "adb version". You could also try using adbWireless which would allow you to not have it hooked to your computer with the USB cable.
Scratch that last post..I got it working in ADB Shell
I downloaded the APK tool and moved the files to C:\Windows
Ran this successful: adb pull /system/framework/android.policy.jar
Problem with: apktool d android.policy.jar out - error saying it couldn't find apktool. I went to restart my phone to see if that was an issue and now its hung on the white android screen and wont boot up
Thoughts?
You didn't actually modify anything on the phone right? And didn't push anything to it either? If not, nothing would have changed and it shouldn't be having a problem booting. Try "adb reboot recovery", wipe cache & dalvik-cache then reboot. If you can't run adb commands...pull the battery, put it back in, power it on and hold volume up + power to get into recovery. If something was modified, use adb to revert the modded files back to the originals or restore with a NAND backup if you made one.
Edit: As for apktool not being found, it sounds like apktool is not in your PATH. The Windows folder should be part of your PATH by default. You could check your PATH variable by following these instructions and modify it if needed or you try moving the unpacked apktool files to the same location as the adb command which is most likely /PATH/TO/ANDROID_SDK/platform-tools OR /PATH/TO/ANDROID_SDK/tools
Sorry for the delay..got back to trying this mod. I got an error..
C:\Users\ME\apktool d android.policy.jar out
Unable to access jarfile C:\Windows\\apktool.jar
Did I put these 3 files in the wrong location?
I just saw your comment about putting these files into where adb.exe is located. I moved these files there..also checked my path and its set up for:
Variable: path
Value: C:\android-sdk\platform-tools
The error I got now is: Unable to access jarfile C:\android-sdk\platform-tools\\apktool.jar
I'm not all that familiar with how Windows handles things but something it should be able to find apktool.jar if it's the same directory as apktool.bat. What is the contents of apktool.bat? A workaround would be manually doing the .bat file's job and run "apktool" using this command instead:
Code:
"java -jar /LOCATION/OF/apktool.jar"
Typing that in a cmd window should give you the usage output for apktool. If that works, you could then use that format to decode and build apk/jar files.
I have everything in the folder: C:\android-sdk\platform-tools
Contents of 'apktool.bat':
@echo off
java -jar "%~dp0\apktool.jar" %1 %2 %3 %4 %5 %6 %7 %8 %9
I am getting this error:
C:\Users\ME>java -jar C:\android-sdk\platform-tools\apktool.jar
Unable to access jarfile C:\android-sdk\platform-tools\apktool.jar
Ok...two more things to try.
Add the location of the java commands to the PATH variable. Probably somewhere like C:\jdk1.6.0_##\bin OR C:\Program Files\Java\jdk1.6.0_##\bin. The PATH variable as a whole would now be something like this: C:\LOCATION\OF\jdk1.6.0_##\bin;C:\WINDOWS\system32;C:\WINDOWS
If that doesn't help: change directory(cd) to C:\android-sdk\platform-tools in the cmd prompt, then run "java -jar apktool.jar"
Sorry it's being such a PITA to just get apktool to run.
1. The location of my Java program is: C:\Program Files\Java - There are 3 folders in there: jdk1.6.0_25, jre1.6.0_22, jre6 - I currently have a user variable 'path' with the value 'C:\android-sdk\platform-tools' - should it be added after this? ..if so, could you explain from what I gave about java what I need to add?
2. Tried cd - same thing..Unable to access jarfile
What does the following command give as output?
Code:
echo %PATH%
I'd set your system environment variable PATH like so:
right-click my computer -> properties -> advanced system settings -> Environment Variables...
under system variables, select Path, and Edit...
add the following(without the quotes) to the end of what's already there: ";C:\Program Files\Java\jdk1.6.0_25\bin;C:\android-sdk\platform-tools;C:\android-sdk\tools"
Also, since you are running Windows...it might make things easier on you to use APK Manager. Here's the thread for it: http://forum.xda-developers.com/showthread.php?t=695701
Here is what I have from the echo %PATH%
{
"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"
}
I installed the APK manager..I have it up and running. So I pulled the 'android.policy.jar' - Now what do I do to edit this file?
With all the storms, a power outage, and being busy I'm just now able to get back to you. I'm going to try going through the process using APK Manager on a Windows desktop I have access to. Step-by-step instructions will be in the post below.
Step-by-Step for Windows
You will need the java jdk installed and ADB set up for this to work.
download APK Manager and extract it to you preferred location
this guide will use C:\apk_manager_4.9
run C:\apk_manager_4.9\Script.bat
select option 0 to adb pull
where = /system/framework/android.policy.jar
stored name = android.policy.jar
current project = y
select option 9 to decompile
minimize Script.bat window
use Notepad++(or your preferred editor) to open:
Code:
C:\apk_manager_4.9\projects\android.policy.jar\smali\com\android\internal\policy\KeyguardViewMediator.smali
find ".method public pokeWakelock()V" NOT ".method public pokeWakelock(I)V"
inside the method, find the two lines starting with "const/16 v#" followed by a hex value(0x####)
the second(0x1388=5000ms=5s) is the default timeout unless a hardware keyboard is open, in which case the first(0x2710=10000ms=10s) is used
the values are 16-bit signed integers so the highest either can be set is 0x7FFF=32767ms=32.767s (Your screen will not wake up if set higher)
use this dec->hex convertor to determine the hex equivalent of your desired ms timeout
modify the hex values to your liking, save the file, and close Notepad++
return to the Script.bat window
select option 11 to compile
system apk = y
additional files = n
select option 8 to adb push
where&name = /system/framework/android.policy.jar
select option 24 to quit
open a command prompt to run these commands:
Code:
adb shell chmod 644 /system/framework/android.policy.jar
adb reboot recovery
in recovery,wipe dalvik-cache & cache, then reboot
Done!
All GOOD! Thanks for your hard work on figuring all this out for windows..it really wasn't hard at all once I had the right set of instructions haha
The only thing I've noticed is that the "screen off animation" does not work now - I have checked and unchecked it and its still not working..its really no biggie but just thought I'd say in case you want to play around with this mod more.
thetornado said:
All GOOD! Thanks for your hard work on figuring all this out for windows..it really wasn't hard at all once I had the right set of instructions haha
The only thing I've noticed is that the "screen off animation" does not work now - I have checked and unchecked it and its still not working..its really no biggie but just thought I'd say in case you want to play around with this mod more.
Click to expand...
Click to collapse
I'm glad we finally got it figured out for you. I have the screen animation turned off on my Eris so I didn't notice this broke it. I'll look into it and see if I can figure anything out. The first thing that comes to mind is that the screen off animation could somehow be dependent on the AWAKE_INTERVAL_DEFAULT_MS variable. As I found when first looking at this mod, changing the variable won't actually affect the value wherever it is used since the package is already compiled. So if the animation does use that variable in some way, we'll need to find where that happens and change the value there.
This probably belongs in the developer section, but I don't have permission to post there yet)
This work is very preliminary. It isn't really anything more than a starting point right now. It DOES NOT yet provide a faithful representation of a custom ROM in the emulator.
Current status:
emulator running 2.6.29 kernel with a combination of frankenstein of the emulator and devoid-franco system image.
I've been working to get a custom ROM working in the Android SDK emulator. There are several reasons for this, but in the end, it makes it a lot easier to test out different tweaks to get the ROM working as I'd like (I need some functions provided on the P509 ROM that aren't provided on any custom ROMS, and reinstalling the APKs isn't sufficient). I spent a lot of time looking for a thread about this, but nothing I could find discusses the specifics of working with a P500 based device
Things I've learned:
a) you need a kernel specifically compiled for the emulator, and the ramdisk image needs to be built to work with an emulator. For the moment i am using the SDK kernel (2.6.29) and ramdisk image to get going
b) the p509 libraries aren't compatible with the emulator, I needed to copy the libraries from the supplied emulator image
Here are some notes I took. I'll try to flush this out more as I make further progress:
Tools you will need:
Android SDK and 2.2 platform files (android-8)
unyaffs
mkfs.yaffs2.x86
a copy of the ROM image to install (devoid.franco.v5 in my case)
before beginning you should build a stock 2.2 emulator env to ensure everything is working (from sdk/tools run):
android list targets
find the id for 2.2 (was '4' for me)
android create avd -n test-froyo -t 4
(I used all defaults, except I set the RAM to 512MB and screen to HVGA)
emulator -avd test-froyo -show-kernel
(this should eventually bring up a running froyo)
you'll need to know where the avd lives. In linux, it should be in ~/.android/avd/test-froyo
I'm working on linux, but this should work in Windows if you can find a compiled version of mkfs.yaffs2 for windows (I've seen a compiled unyaffs version out there)
1) unzip the rom image. it should create a system/ directory.
We should execute the updater-script here, but we'll take a short-cut:
chmod -R 655 system/
2) uncompress the platfrom system image:
in a new dir:
unyaffs <sdk path>/platforms/android-8/images/system.img
3) copy all files from system/ in step-2 to system/ in step-1
we should really need to do this, it is probably sufficient to run the updater-script and then copy the framework/, lib/ and a couple qemu files, but this is just to get things going.
4) make dbus.conf readable:
chmod 644 system/etc/dbus.conf
5) remove system/app/LGSetupWizard.apk
This app relies on custom classes in the firmware that aren't present in the emulator base system. I'm still trying to build a custom firmware.jar that has both.
6) build a new system.img
mkfs.yaffs2.x86 system system.img
7) copy the system image to your avd dir:
cp system.img ~/.android/avd/test-froyo
If everything has gone well, you can now startup the emulator and boot into franco's rom:
emulator -avd test-froyo -show-kernel
Because we copied too much stuff from the default system.img, we've lost his themes and mst of his tweaks, so it isn't really a faithful representation of the ROM at all, but we've cleared the 1st milestone of being able to boot up.
I also booted a stock P509 kernel this way with a few changes:
a) I used nandroid to get the system image, and then unyaffs2 to extract it)
b) I removed all odex files:
find system -name "*.odex" | xargs rm
Again, this isn't really a custom ROM, it is actually the emulator rom with additional apps and customizations. The goal is to get to as close as possible to running a true custom ROM
A few other notes:
the following framework files can be preserved from the custom ROM (no need to overwrite):
Code:
am.jari : ok
android.policy.jar : not ok
android.test.runner.jar : ok
bmgr.jar : ok
core.jar : ok
ext.jar : ok
framework.jar : not ok
framework-res.apk : not ok
framework-tests.jar : ok
ime.jar : ok
input.jar : ok
javax.obex.jar : ok
monkey.jar : ok
pm.jar : ok
services.jar : not ok
svc.jar : ok
framework.jar is the most important of the 'not-ok' ones as far as I can tell, and is missing several classes. I am currently working to build a services.jar that is a merge of the P500 and emulator classes.
Installing the p500 framework,.jar requires many files from system/lib, but once all dependencies are solved, you eventually end up with a segfault. I've been unable to debug that, and am not sure I want to. The goal is to get a running dalvik VM with all classes needed to run P500 apps.
First blood!!!
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.
Hi, All, Latest I want to modify other apps in unrooted device, so I wrote a tool to do this. I just called it Xpatch.
The basic principle of this tool is very simple. It just modify the target apk, inserting some codes in the Application. These codes's main purpose is loading the xposed modules. So any Xposed modules installed in the device can be loaded by the target app.
Note: It is very safe.
Github repository: Open Github and search Xpatch, or just search my name: WindySha. (Because I'm new here, I have no permission to add links in this thread)
The following is the detailed introduction：
What is Xpatch
Xpatch is a jar tool which is used to repackage the apk file. Then, the new apk can load any Xposed modules installed in the android system.
This is a way to use Xposed modules without root your device.
It is easy way to modify one app using xposed module. And any apps changed by Xpatch can load every modules downloaded in the Xposed Module Repository.
Benefits
1. Use xposed modules without your device;
2. Modify any apps without root your device.
How to use
1. Download the latest jar file from the my github release page.
2. Run this command in the Windows/Mac console:
$ java -jar ../../xpatch.jar ../../source.apk
Then, a new apk named `source-xposed-signed.apk` in the same folder as `source.apk`.
More commands
1. You can specify the output apk path by add `-o` parameter, eg:
$ java -jar ../../xpatch.jar ../../source.apk -o ../../dst.apk
2. Show all the building new apk logs, just add `-l`, eg:
$ java -jar ../../xpatch.jar ../../source.apk -l
3. After the version 1.2, craching app signature verifying is added, if you won't need the function, just add '-c', eg:
$ java -jar ../../xpatch.jar ../../source.apk -c
Todo list
1. Support packaging the xposed modules into the source apk;
2. Support loading so library in the xposed modules;
3. Crach apk protections.
Issues
1. If the apk dex files are protected, dex2jar can not effect on the dexs, then this tool will not work;
2. The hook framework is using whale, this framework is not very stable, some hooks may fail;
3. Do not support Davlik VM;
4. Do not support resource hook;