I'm currently using Android Oreo (RevolutionRemix) and I really don't like the circular TimePicker dialog that's presented to me when I create an alarm in the default clock or when I make a new event in my calendar (Nine).
Currently I get a dialog like this:
{
"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"
}
But I really would like it more like this:
I found this link https://android--code.blogspot.com/2015/08/android-timepickerdialog-theme.html (where I got the above screenshots), and it seems like this is something that can be changed with a theme.
Is this a default that can be changed (or forced) system-wide? If so, how? FYI, I have root and I'd rather edit an XML file somewhere to get this done than download a whole theming app or something.
Thanks in advance!
raphidae said:
I'm currently using Android Oreo (RevolutionRemix) and I really don't like the circular TimePicker dialog that's presented to me when I create an alarm in the default clock or when I make a new event in my calendar (Nine).
Currently I get a dialog like this:
But I really would like it more like this:
I found this link https://android--code.blogspot.com/2015/08/android-timepickerdialog-theme.html (where I got the above screenshots), and it seems like this is something that can be changed with a theme.
Is this a default that can be changed (or forced) system-wide? If so, how? FYI, I have root and I'd rather edit an XML file somewhere to get this done than download a whole theming app or something.
Thanks in advance!
Click to expand...
Click to collapse
You should be able to do this easily by editing the theme in res/values/styles.xml. If you know how to decompile apps with apktool, this should be an easy ordeal. You will need to decompile framework-res.apk and edit Theme. Material.Light and Theme.Material
To avoid bootloop, do not resign the app once edited and recompiled! Open the new apk with winrar or 7zip and add in the original manifest and meta folder located in the "originals" folder when using apktool.
Sent from my LG-Q710AL using Tapatalk
RealWelder said:
You should be able to do this easily by editing the theme in res/values/styles.xml. If you know how to decompile apps with apktool, this should be an easy ordeal. You will need to decompile framework-res.apk and edit Theme. Material.Light and Theme.Material
To avoid bootloop, do not resign the app once edited and recompiled! Open the new apk with winrar or 7zip and add in the original manifest and meta folder located in the "originals" folder when using apktool.
Click to expand...
Click to collapse
I don't know how, but I'm going to learn it Where is this apk normally in the filesystem, in the same location as installed apps? And would it be in the same location on a custom ROM as RR, or would it possibly be a custom theme with a different apk? Also, I thought apk files were just renamed zip files, what needs to be decompiled exactly (if that has an easy answer, otherwise I'll google it)? Thanks!
You will need some tools. Apk files are similar to zip files, but there are some things that are hidden. You will need apktool, adb, Notepad++, and java jdk installed. Adb and apktool are simple files that I can provide for you. They run on the command line in windows. What I do is put the files associated with adb and apktool in the C:\Windows directory so that they are installed system wide, meaning you can open the command prompt from anywhere and use the tools. Java jdk you will have to download and install.
I'm pretty sure on remix it will be framework-res.apk and it will be located in /system/framework/ directory. Apktool you will use to decompile and recompile the app. Adb is just to make things faster. You can use it to push or pull files from computer to phone and vice versa, reboot the phone, etc. You will have to enable USB Debugging in the developer options. You can also use adb to open a shell. (Like terminal in linux) but for our purposes we probably won't get into that.
Here is a link to my basic modding tools. Extract the files out and copy them to C:\Windows\.
https://drive.google.com/file/d/1Ywa3SWd_420uO-nyi2-iqVWp1vu0V_D9/view?usp=drivesdk
You'll need to copy any app that might be in /system/framework. I'm not super familiar with remix but we will get through it. Most likely it will be framework-res.apk unless remix uses something like RRframework-res or something. You can check that out with a root file manager. You may also need your SystemUI.apk located in /system/priv-app/. This is just to install the frameworks into the apktool.
Once you get all of your tools in place, create a folder named workspace on your desktop or somewhere easy to get to. Copy the above mentioned apk files into that folder. Next hold shift and right click the mouse. You want to open a command window here. In the command window type
apktool if framework-res.apk (then hit enter)
This is how you install the frameworks for apktool the if means install framework. You may also have to do this with SystemUI.apk.
Now were ready to decompile our framework! Lol. In cmd type
apktool d framework-res.apk
This will decompile the app. After you make your edits, you will use
apktool b framework-res
To build the app. (If you have any errors decompiling/recompiling report here)
At this point hopefully your app is decompiled and we can make our edit. Open /res/values/styles.xml with Notepad++ (a great computer program for coding) You will want to scroll down to Theme.Material.Light and find the TimePickerDialog. Then scroll down to Theme.Holo.Light and find TimePickerDialog. Copy the attribute from Holo theme to Material theme. Save. Recompile app. The new app will be located in the "dist" folder. Open the app with 7zip and add in the AndroidManfiest.xml and meta folder from the originals folder to retain the app's stock signature. Now we need to move our new apk to the phone. Type
adb push (drag and drop apk into cmd window) /sdcard/
This should push the app to the phone.
You can also use
adb pull (path and file)
to pull files from the phone to your workspace.
Once you get your new apk file ready and pushed onto the /sdcard/, open root file explorer and rename it to framework-res1.apk. This is so we can copy it into /system/framework/ without immediately overwriting the original. Next use root file explorer to change app's permissions to 0644. Once the permissions are changed correctly you can rename it to framework-res.apk and overwrite the original. Then reboot and enjoy.
Sent from my LG-Q710AL using Tapatalk
RealWelder said:
(snip instructions)
Click to expand...
Click to collapse
Thanks for the detailed instructions, really appreciated! Seems clear enough that I won't have any problems, I'll try it tomorrow or so and report back.
Just one question remaining: how can one retain the original signature by copying manifest files back into the apk? Isn't the whole idea of a signature to prevent changes to the files in the package? Or is it a different kind of "signature"?
raphidae said:
Thanks for the detailed instructions, really appreciated! Seems clear enough that I won't have any problems, I'll try it tomorrow or so and report back.
Just one question remaining: how can one retain the original signature by copying manifest files back into the apk? Isn't the whole idea of a signature to prevent changes to the files in the package? Or is it a different kind of "signature"?
Click to expand...
Click to collapse
It prevents you from modifying the AndroidManifest.xml. If you changed anything in it you would have to resign... But then it's signature won't match the rest of the signatures in the OS, which causes bootloop. Copying the original manifest and meta folder is just a workaround to keep it's signature in tact.
Sent from my LG-Q710AL using Tapatalk
RealWelder said:
It prevents you from modifying the AndroidManifest.xml. If you changed anything in it you would have to resign... But then it's signature won't match the rest of the signatures in the OS, which causes bootloop. Copying the original manifest and meta folder is just a workaround to keep it's signature in tact.
Click to expand...
Click to collapse
OK, that makes sense, thanks! I noticed that a wrong signature can cause a boot loop, I'm guessing that other problems with this file can also cause a boot loop? If so, is there an easy way to bypass this file should that happen (safe more or something)?
Just FYI, I'm using full-disk encryption and TWRP can't decrypt the data partition, but I assume I can just put the original file back to the /system filesystem if necessary?
raphidae said:
OK, that makes sense, thanks! I noticed that a wrong signature can cause a boot loop, I'm guessing that other problems with this file can also cause a boot loop? If so, is there an easy way to bypass this file should that happen (safe more or something)?
Just FYI, I'm using full-disk encryption and TWRP can't decrypt the data partition, but I assume I can just put the original file back to the /system filesystem if necessary?
Click to expand...
Click to collapse
It could, but generally the signature issue is the main reason for bootloop. The xmls and png images are safe to edit. Be careful with images, if one has a .9.png extension it is a nine-patch file. They have a one pixel border around the image that lets android know where to stretch said image. They are black dots/lines. Make sure they stay black and not opaque at all.
Sent from my LG-Q710AL using Tapatalk
raphidae said:
OK, that makes sense, thanks! I noticed that a wrong signature can cause a boot loop, I'm guessing that other problems with this file can also cause a boot loop? If so, is there an easy way to bypass this file should that happen (safe more or something)?
Just FYI, I'm using full-disk encryption and TWRP can't decrypt the data partition, but I assume I can just put the original file back to the /system filesystem if necessary?
Click to expand...
Click to collapse
I would make a fresh backup with TWRP before doing any of this, just in case. It is pretty safe though. I've been tinkering with rooted phones for a few years doing this. My latest venture is in a way even more impressive. With the newer LG phones, they have a built in theme system. I've been able to create my own theme and apply it to the phone all without root.
Sent from my LG-Q710AL using Tapatalk
Related
Hi,
This is a tutorial to explain how to make a theme with some APKs modified.
Note : This HOWTO is for people who have a minimum knowledge in informatic, i will not answer to questions like "what's a CMD?" etc.
FACULTATIVE STEP
The first thing we have to do, it's set up a working folder, this will help you to make your theme easily
Create a folder "Skin blabla", like you want.
After, create 3 folders like this screen :
{
"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"
}
We will make a backup of ALL APKs of your tattoo (if you do a wrong modification & you brick), make a copy of this backup into "Modded APKs" (there will be the modified APKs), and "Decompressed" will be the folder which has all PNGs.
SOME EXPLICATIONS
The only risk is Android, all APKs which are using on android have to be signed, if one of your APKs isn't signed, you will semi-brick your Tattoo and have to go on recovery and push the original APK.
Note : You have to have (woh) a custom recovery, if you don't and you semi-brick your tattoo, the only way to restart it is the GOLDCARD.
So, the only way to keep your APK signed is to use the drag&drop.
FIRST STEP : Backup
Connect your device. (with USB debug)
Open a CMD.
(We say your skin's folder is on c:\Skin to make it simple, if you choose an other destination, change what i have writed after)
adb shell pull /system/app/*.apk "c:\Skin\Original APK"
adb shell pull /system/framework/*.apk "c:\Skin\Original APK"
copy "c:\Skin\Original APK\*.apk" "c:\Skin\Modded APK"
You can delete the APKs you will never modify on Modded.
It's finished, we can start
SECOND STEP : Drag & Drop
I'm using WinRAR.
Like i said before, we have to keep our APKs signed.
Select which APKs you want to modify of "Modded" folder, right click, and select "extract...".
Select "Decompressed" folder, and extract all APKs.
You will have many folders with the name of which APK. (Rosie, framework-res, etc etc)
Modify all PNGs you want to modify on which folder. (Note : All images are on res/drawable*)
Then, return on modded folder, open which APKs you modified on the other folder, and open framework-res.apk for example, let the APK open with WinRAR. Open "Decompressed"s folder, select some folders/PNGs you have modified (we will select "drawable" for example), drag&drop it in WinRAR. (of course, you have to be on /res folder in winRAR, the folder have to match...)
Copy the modified APK with : adb push blabla.apk /system/originaldirectoryoftheapk
Some advices
- All notifications icons are on framework-res.apk & com.htc.resources.apk.
- The only APKs which are on /system/framework/ are the both APKs one line before. All others are on /system/app/.
- Rosie.apk is HTC Sense.
- Some notifications icons are on Calendar.apk (1), HtcContacts.apk (1), HtcLocationService.apk (1), HtcMusic.apk (2+), HtcTwitter.apk (1), Mail.apk (1), Mms.apk (1+), Talk.apk (1).
- If you modify Rosie.apk, or some others APKs, Sense will be strange, wait or reboot the device.
- ...
Hi JoOoSs
I have modified Browser.apk, but when I try
Code:
adb push Browser.apk /system/app/Browser.apk
I receive the next message:
Code:
failed to copy 'Browser.apk' to '/system/app/Browser.apk': Out of memory
Also, before this I was receiving this message:
Code:
failed to copy 'Browser.apk' to '/system/app/Browser.apk': Directory not empty
Any ideas about what could be the problem?
Thanks!
It's a problem with your ROM.
Modaco ? Fyodor ? Stock ?
I have the MoDaCo ROM, the weird thing is that yesterday I installed your Black skin, and today I tried to do it again and have the above errors.
At each reboot you have to do:
adb shell
insmod /system/lib/modules/tattoo-hack.ko
mount -o rw,remount /dev/block/mtdblock3 /system
JoOoSs said:
At each reboot you have to do:
adb shell
insmod /system/lib/modules/tattoo-hack.ko
mount -o rw,remount /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Actually, I did it.
I've noticed something really weird. I flashed a fresh ROM (MoDaCo), then I pushed your files (from Black Skin) and some mine, everything worked perfect. But, later, when I try to push another file (yours or mine), I get this error:
Code:
adb push WorldClock.apk /system/app/WorldClock.apk
failed to copy 'WorldClock.apk' to '/system/app/WorldClock.apk': Directory not empty
I don't know what is happening
I think you lose the RW when you exit your CMD, did you retry to mount /system ?
If it's yes, i don't know it works in my Modaco Oo
Thanks JoOoSs
I don't know why this was happening, but I installed the stock ROM and everything works perfect know! Regards!
It would be nice to have default android skin on our tattoo. Do you think is it possible?
Yep, you have to flash 2.1 ROM which is on Dev forum, backup all PNG from his ROM & re-insert them on an other ROM.
JoOoSs said:
Yep, you have to flash 2.1 ROM which is on Dev forum, backup all PNG from his ROM & re-insert them on an other ROM.
Click to expand...
Click to collapse
Actually, you don't need to flash the 2.1 rom, remember that is a .zip, so just extract the apps from /system/app directory and then extract the pngs...
In the zip there are only the *.img ?
We have to uncompress boot.img etc it's more long!
So...what we could do to have a default 2.1 lock screen and skin and nothing else?
Please help us poor noobs
JoOoSs said:
In the zip there are only the *.img ?
We have to uncompress boot.img etc it's more long!
Click to expand...
Click to collapse
Not really, I downloaded the update.zip file from the 2.1, and it doesn't have .img files... I've changed all my apps icons using the 2.1 version.
Is there anyone that can answer to my ask?
HTCDevil said:
Is there anyone that can answer to my ask?
Click to expand...
Click to collapse
Hi, actually, change all the skin and the lock screen is going to be almost impossible, I changed all the main apps icons, but the skin itself is more complex, we have to go through all system APKs and find the png files related with the skin, but even doing that the change is complex.
This is how my icons looks like:
Can you upload icons & the wallpaper ?
yes, wallpaper please
Thank you arturo
I'd like also the only white bar rather than black
APKs with eclair icons and wallpaper
Hello all,
Here are the modified apk files with the eclair icons and also a nice wallpaper.
I highly recommend to do a nandroid backup before replace the apk files (we never know ).
APKs: http://www.megaupload.com/?d=GG7LPC9C
Enjoy it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As all of you well know, Android is an open source operating system and as such the development and modding are the bread and butter for devices with this OS.
In this thread I'll explain how to extract the firmware partition containing the operating system and programs with a Windows PC.
The purpose of this thread is to share knowledge, so feel free to help me to dump device such as Acer, Samsung and Sony Ericsson, expecially I need someone that help me with Acer's .bin
1. Unpack the system partition from an HTC ROM
What you need:
UniExtract: http://legroom.net/software/uniextract (freeware)
ZipScan: http://www.zipscan.co.uk/ (shareware)
Cygwin: http://cygwin.org/setup.exe (freeware)
Unyaffs for Windows: http://goo.gl/z6yI
Download and install all the tools (Unyaffs it's a prompt executable, so it isn't installable)
Now you need an HTC ROM, download one at your pleasure from Conflipper's site: http://www.shipped-roms.com/shipped/
Once you have downloaded it, right click on the ROM executable and select Extract with UniExtract in the subfolder (v.fig1), select Isxunpack extraction and then clik on the OK button (v. fig2)
Now in the subfolder you have the various files which make up the executable, including data1.cab which is the file that we are more interested in (do not delete other files).
Open ZipScan, go to File -> Open Archive File... and browse until select the data1.cab. You should see something like this:
Extract from the cab only the ROM.zip and open this file with any archives extraction software (eg WinRAR or the same ZipScan). Inside you have various .img files which make up the ROM, but for the purposes of this guide, we need only the system.img.
Copy in a blank folder this file, unyaffs.exe and cygwin1.dll (you'll find it in C:\Cygwin\Bin).
Now open Cygwin from Start -> All Programs to ensure that its functions are integrated to the Windows Prompt and close it.
Open the Windows Prompt (Start -> All Programs -> Accessories) and position yourself in the folder containing the files using the cd command or alternatively install this .reg which allow you to open the Windows Prompt in the chosen folder by command in the context menu (Right click on the folder -> Command Prompt Here).
Now the last thing that you have to do is to give the extraction command: unyaffs system.img
Et voilà, now you have the folders containing the extracted system.
Enjoy
2. Unpack the system partition from a Motorola ROM
°°°Coming Soon°°°
°°°reserved°°°
°°°2nd reserved°°°
°°°3rd reserved°°°
Thank you! I had found a different way but this will save some steps.
mark
i will see
!!!!!!!!!!!!!!!!111
Someone once told me you can just run the .exe file, let it open, use windows to search for the rom.zip that would have been extracted into a temp folder, drag&drop to another location, then cancel the .exe again.
Haven't tried this myself though.
What else can you show us in windows?... Is it at all possible to extract ramdisc thingies from kernels so we can apply one custom kernel to other roms ourself?
... or should I bite the bullet and install/learn how to use ubuntu?
Nice initiative. Finish the guides and I'll see to it that it's stickied.
ddotpatel said:
Is it at all possible to extract ramdisc thingies from kernels so we can apply one custom kernel to other roms ourself?
... or should I bite the bullet and install/learn how to use ubuntu?
Click to expand...
Click to collapse
There are simple perl scripts kicking about to unpack/pack boot.img, so you can use them on Windows as long as you install perl first - say either via Cygwin or Active State.
I just used WinRAR to do everything that UniExtract and ZipScan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility UnYaffs.exe, which can be run through CygWin. Thanks.
Why doesn't someone make a UnYaffs.exe for windows command line?
After I change things, how to I ReYaffs it to system.img? ...and when I re-zip it don't I have to sign it or something? If I modify an apk do I have to deODEX it first? Do I reODEX after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [ROM], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [ROM] to be shared with all.
rpmccormick said:
I just used WinRAR to do everything that UniExtract and ZipScan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility UnYaffs.exe, which can be run through CygWin. Thanks.
Why doesn't someone make a UnYaffs.exe for windows command line?
After I change things, how to I ReYaffs it to system.img? ...and when I re-zip it don't I have to sign it or something? If I modify an apk do I have to deODEX it first? Do I reODEX after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [ROM], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [ROM] to be shared with all.
Click to expand...
Click to collapse
No ****... I was wondering why he's making it all so complicated with all these extra tools when I can click the file in Winrar (extract to...) and be done. All in ONE step for me.. LOL
For me it was more than one step because using WinRAR on system.img didn't get all the files out. Using unyaffs did. But now I have a system.img from a new Android tablet and I can't get anything out of it other then the META-INF directory using WinRAR, Unyaffs, or UniExtract. Anyone have any clue how to get in to those?
...and I still want an easy tutorial on how to re-assemble a flashable system.img / update.zip once I change some stuff in there.
I really hope one of those reserved spots is for the newer Samsung phones. What really cheeses me, though, is that I had that explained to me once, and I can't find it, and didn't write it down
I've compiled both unyaffs.exe, mkyaffsimage and mkyaffs2image for cygwin, with the DLL you can use them on Windows too. Sadly, I don't know too much about C and C++, so I can't make it work, but maybe I will try to compile them for Windows, and with some bugfixing, MAYBE it will run.
Samsung did not use the usual yaffs image (for Galaxy S at least), but their own format, what can be easily extracted. I will post some more about it as soon as I get back to windows, recompile the executables and upload them.
i wana extract boot.img , but i have some error
$ gunzip -c boot.img | cpio -i
bash: cpio: command not found
gzip: boot.img: not in gzip format
Click to expand...
Click to collapse
I had some problems with unyaffs. This version posted on 1st page is bugy, if you have same problem try...
hmmm i have i more problem: To prevent spam to the forums, new users are not permitted to post outside links in their messages.
so sry guys i can't help you right now
rpmccormick said:
i just used winrar to do everything that uniextract and zipscan can do.
...so basically you showed me that system.img can be unpacked using the linux command-line utility unyaffs.exe, which can be run through cygwin. Thanks.
Why doesn't someone make a unyaffs.exe for windows command line?
After i change things, how to i reyaffs it to system.img? ...and when i re-zip it don't i have to sign it or something? If i modify an apk do i have to deodex it first? Do i reodex after?
I would love a quick tutorial on, say, how to change an icon for an app. Something that shows people who already know how to do this type of stuff a brief step-by-step guide to taking a [rom], adding and deleting a few apks inside it, making a graphical change to an apk inside it (skinning), and then recooking those changes in to a new [rom] to be shared with all.
Click to expand...
Click to collapse
+1000
.
WinImage can extract the .img.
Unfortunately, I don't think it can repack them properly.
I know what I want but haven't yet figured out how to make it work. I read that you can simply open an existing theme, with 7zip for example, and replace what you want, but when I tried this the entire status bar disappeared.
I am basically looking to add elements of Galaxy Green to the stock GSB system app and also add some different colored notification icons, such as a blue icon for bluetooth on but not connected and a different shade for on and connected.
If someone could point me to some directions that work, some software to create themes, or if someone would be willing to take on the task I would greatly appreciate it.
http://forum.xda-developers.com/showthread.php?t=916814
PieceKeepr said:
I know what I want but haven't yet figured out how to make it work. I read that you can simply open an existing theme, with 7zip for example, and replace what you want, but when I tried this the entire status bar disappeared.
I am basically looking to add elements of Galaxy Green to the stock GSB system app and also add some different colored notification icons, such as a blue icon for bluetooth on but not connected and a different shade for on and connected.
If someone could point me to some directions that work, some software to create themes, or if someone would be willing to take on the task I would greatly appreciate it.
Click to expand...
Click to collapse
Yes.. You can open an apk and replace the png's within 7zip or winrar without extracting anything. Part of the problem I've had with doing that on th CM7 roms was status bar problems like you've said though. Also sometimes getting fc's on some things with the status bar and notification area. If you have the images you want to use I could help you out or if you want to put them in a zip and send them to me and I can throw them into a theme chooser apk for you. That so far has been the best way I've found to avoid issues on CM7.
@playpolo4life Thanks a lot. There is a lot to read there and hopefully I'll make it work in a few days.
CondemnedSoul said:
If you have the images you want to use I could help you out or if you want to put them in a zip and send them to me and I can throw them into a theme chooser apk for you. That so far has been the best way I've found to avoid issues on CM7.
Click to expand...
Click to collapse
I might just do that. I read some of the material linked above tonight while I was at worka dn on my next off days I'm gonna try to theme it myself. If I don't have any success I'll PM or shoot you an email. Thanks much for the offer.
Haha yeah its definitely a lot. I've tried to read it in one sitting and comprehend everything, but just couldn't do it. I don't think I have the patience for most of the theming requirements. I gave up when I got to the xml editing and hex editing parts lol.
Well I tried apk manager and followed the video instructions on how to set up the java path but since it's a WinXP video it gave me an error because I'm on Vista 64. I got apktool installed and working but after more videos and reading I have a headache and I still have no idea what I'm doing.
PieceKeepr said:
Well I tried apk manager and followed the video instructions on how to set up the java path but since it's a WinXP video it gave me an error because I'm on Vista 64. I got apktool installed and working but after more videos and reading I have a headache and I still have no idea what I'm doing.
Click to expand...
Click to collapse
I'm on Win 7 64. I use apk manager. What kind of error are you getting though?
CondemnedSoul said:
I'm on Win 7 64. I use apk manager. What kind of error are you getting though?
Click to expand...
Click to collapse
I could have misunderstood the directions but when I click the script.bat file a window opens with the message that reads, "Java was not found, you will not be able to sign apks or use apktool
Press any key to continue ..."
Hit enter and a lists of tasks pops up. Try any task and it wants to know what project you want to work on (option 22). I type "22" and it says to choose the app to be set as current project and says enter it's number. If this is working correctly then I clearly have absolutely no idea what I doing (always an option) since I don't know how to obtain project numbers, but I thought it might be related to the java not found message.
I do have the latest Java and Java SE DK installed. I'm getting really close to taking you up on the offer but what I want is extensive, at least I think it is.
PieceKeepr said:
I could have misunderstood the directions but when I click the script.bat file a window opens with the message that reads, "Java was not found, you will not be able to sign apks or use apktool
Press any key to continue ..."
Hit enter and a lists of tasks pops up. Try any task and it wants to know what project you want to work on (option 22). I type "22" and it says to choose the app to be set as current project and says enter it's number. If this is working correctly then I clearly have absolutely no idea what I doing (always an option) since I don't know how to obtain project numbers, but I thought it might be related to the java not found message.
I do have the latest Java and Java SE DK installed. I'm getting really close to taking you up on the offer but what I want is extensive, at least I think it is.
Click to expand...
Click to collapse
You have the latest version of Java JDK? you shouldn't get that error. But for your project numbers... When you type option 22 it will bring up a list of all the apk's in the place-apk-here-for-modding folder. Type they number that corresponds to the apk you want to work on. Then hit option 9 to decompile the apk and go to your projects folder and you will see a folder with the name of the apk you just decompiled. everything will be in there
I uninstalled JDK and downloaded it again from the Java site although it was the same version I already had. I reinstalled it and tried apk manager again. This is the same message I was getting before ...
{
"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 went ahead and tried it anyway and when I selected a project to work on I got this message ...
Check out this thread and look at post #7... I have a feeling this is your missing piece
http://forum.xda-developers.com/showthread.php?t=988959
Well, I tried that "path" update and it didn't work but I noticed the post right below the one you're talking about said you have to have a 64 bit Java version.
I had installed the 32 bit version because AndroidSDK didn't want to work with the 64 bit version. After installing hte 64 bit Java the first error message went away but then it said ADB was not found. I only see one SDK download for Windows.
I also tried the method of opening the apk with 7-zip, dropping in the new image files and closing 7-zip. I moved the apk to system\apps and rebooted but it wasn't recognized so I deleted the file. I then tried to install my modified/renamed apk from the SD card and it went through the steps but then said app not installed.
PieceKeepr said:
Well, I tried that "path" update and it didn't work but I noticed the post right below the one you're talking about said you have to have a 64 bit Java version.
I had installed the 32 bit version because AndroidSDK didn't want to work with the 64 bit version. After installing hte 64 bit Java the first error message went away but then it said ADB was not found. I only see one SDK download for Windows.
I also tried the method of opening the apk with 7-zip, dropping in the new image files and closing 7-zip. I moved the apk to system\apps and rebooted but it wasn't recognized so I deleted the file. I then tried to install my modified/renamed apk from the SD card and it went through the steps but then said app not installed.
Click to expand...
Click to collapse
Something sounds strange there then... I always get the adb not found when I use apk manager because I don't have it in the sdk with adb. It's ok to get that message you just won't be able to use the adb portion of apk manager is all. the one you modified and renamed... you decompiled it, replaced what you wanted then compiled it and signed it?
Decompiled, replaced files, recompiled ... it asked if it was a system file and I said yes. It created a new folder and told me to remove everything I changed and then press enter. Did that and it created an unsignedSystemUI.apk but when I open it all of the changed files were missing. The stock ones were not present either, they were just gone.
I have a headache again from this crap. I quit for the night.
PieceKeepr said:
Decompiled, replaced files, recompiled ... it asked if it was a system file and I said yes. It created a new folder and told me to remove everything I changed and then press enter. Did that and it created an unsignedSystemUI.apk but when I open it all of the changed files were missing. The stock ones were not present either, they were just gone.
I have a headache again from this crap. I quit for the night.
Click to expand...
Click to collapse
nothing was there? That doesn't make sense Try doing it as a non-system file. It won't tell you to delete everything then. You'll just have to move it to system app because it will install to data app... one other question... Did you say yes to it copying stuff from the original doing it as a system file? If so try saying no when it asks that and it should compile with everything from the project folder instead of telling you to delete the things you changed.
Yes I did say it was a system app and yes I did say I wanted to keep stuff.
Not everything was gone, just all of my changes. I'll try it as a non-system app when I have time on my next off days.
Sent from my Eris ADR6200 using XDA Premium App
This has got to be part of my problem. When I try to decompile the systemui.apk using option 9 I get this ...
I tried using option 10 since it is a system file and I get this ...
I thought framework-res.apk was the dependency but when I try that it tells me that is not the dependee apk. Is there a way to tell what the correct file is?
Have I mentioned lately that this is really aggravating?!
GSB 2.9 Themes won't load
Starting with GSB 2.7, I have't been able to set themes. Still having the problem with 2.9. When I try to load one it goes through the motions but all it does is change the color of notification icons. Anyone know of a fix? Other than that 2.9 is great, very fast and no other issues at the moment.
I've done a heavy search on the problem and can't seem to find a solution so here goes. I created a file through Adobe Photoshop for the status_bar_close_on.9.png. Pictured below. I created it in the exact dimensions the file was which is 480 x 48. I then ran cmd for draw9patch. I dropped my .png file into draw9patch to make it a .9.png.(Also, made a border on the bottom and right side even though there's no words in the final .9.png.)
I then placed the file into SystemUI.apk>deleted META-INF> then resigned the apk. Placed the APK back into a flashable zip> Flashed.
My problem is a white border shows around my image now. From the recommendation of another forum member, I tried putting the apk into apkTools and ran unPack.bat and quickPack.bat which didn't work either.
What am I doing wrong?
{
"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"
}
EDIT: I think I may have found my problem. I wasn't using Eclipse to compile the image.
Reference: http://www.nexus-nation.com/root-your-nexus-one/9pngs-figured-out
EDIT: This wasn't easy to figure out. I don't want anyone to go through what I went through so I've added what I've found and posted some nice pictures for you visual people.
*You first need to read the page I referenced above. After you have installed Eclipse, you'll need to install the google plugin shown below.
Possible errors you'll run into when starting an Eclipse Project
When you start a new project>File>New Project>Android>Android Project> and the build target is not listed you'll need to do the following on Eclipse. You'll know you have to do this if it says, "An SDK project must be specified."
If your screen looks like this, it means you haven't specified your SDK directory for Eclipse.
Step 1. Open Eclipse>Windows>Preferences
Step 2. Find the location of your SDK
Your Eclipse should then look like the following image, which now displays your build target.
Possible Error 2: While setting up a new project in Eclipse, you get the error: "
Package Name must have at least two identifiers
Click to expand...
Click to collapse
You need to enter the package name as: com.android.newproject and the project name must be one word only.
Reference:http://blog.gbinghan.com/2010/05/android-eclipse-package-name-must-have.html
Reference:http://www.nexus-nation.com/root-your-nexus-one/9pngs-figured-out
Quote:
When you open a .9.png you do not see the guides, that is because they are hidden. When you want to add the guides to an image, you have to drag it into the draw9patch tool. Now the tool has a hidden secret i figured out.(not really hidden, but not well described) If you open an image with the .9.png extension it just opens it. But if you open an image without the .9.png extension, it adds 2 pixels to its width and height. These 2 pixels are for the hidden guides. For example the btn_default_normal_disable.9.png in framework is 44x48. But if you remove the .9 from the file name and drag it into the draw9patch tool it changes to 46x50. Which you will notice after you save the image from the draw9patch tool. Also it will add the .9 to the file name.
Howto: draw9patch
The idea of the draw9patch tool is very simple, you drag an image into it you create the guides and you save the image. But the guides are very specific and if you do not do them properly your image will look strange. So follow these few rules about the tool.
Remove the .9 from image name before you drag it into the tool.
The top and left side guides set where the image can be stretched. Where ever you put a guide is where the image will stretch. Do not put more then 2 next to each other.
The bottom and right side guides set the content area(where the text will go). Now you can only put the guides in the outer border, once the image is compiled this border will be hidden. The tool will not let you put any guides anywhere but the outside border. Now usually you will put a 1x1 guide on the top and left sides, on the right and bottom you want to draw a full line. I have tried putting multiple guides on the top and left but the aapt tool seems to stress out and crash before compiling.
Once you save the image the draw9patch tool should of added the .9 to the name. That is all to adding the guides to the image.
So now your saying ok, i have the image and i still see the guides. To get rid of these lines we need to compile them with Eclipse. Basically we add them to a project in Eclipse and create an apk. During the compile the aapt tool from the sdk will set the image back to its original resolution and hide the guides.
(I am hoping to figure out some command lines for the aapt tool so we can skip this step. But until then editing these .9s are a big pain in the arse!)
Howto: Compiling in Eclipse.
I am assuming you followed the link above for setting up Eclipse and can create a new Android project.
Once Eclipse is open you want to go to "File\New\Android project". Select "Create project from existing source". It should default to the path of the samples in your SDK directory, but if it doesn't just browse to them. I have been using my own project but any sample should be fine. Choose "Finish" and on the left hand side under Project Explorer, you will see the name of the project you opened. Expand the project, then Res and you will see the Drawable folder. You will want to drag your edited .9s here. Once all of the images are in the drawable folder you want to right click the top level folder(Project name) for your project and choose "Android Tools"(second from botom) then "Export Unsigned Application Package..." Save the apk where ever you'd like, just remember where you put it. Cause you will want to open it and take the images out of the drawable folder. You will notice now that the guides are gone and the resolution is back to the normal size. Drag the images into your theme and you are done.
Click to expand...
Click to collapse
What's unPack.bat and quickPack.bat? As I told you on a PM, you have to compile that 9.png file. You can do that:
using apktool: decode apk using apktool, then add your 9.png and build apk back
creating new Android project: create it, add your 9.png, build, unpack, copy compiled 9.png - that method was described in a guide quoted by you.
or using aapt tool directly
Brut.all said:
What's unPack.bat and quickPack.bat? As I told you on a PM, you have to compile that 9.png file. You can do that:
using apktool: decode apk using apktool, then add your 9.png and build apk back
creating new Android project: create it, add your 9.png, build, unpack, copy compiled 9.png - that method was described in a guide quoted by you.
or using aapt tool directly
Click to expand...
Click to collapse
The aapt came with the unpack and quickpack.bat. Which were in the apktool kit. Unpack.bat. From what it said, decodes the apk file. It looks like it extracts it. Quickpack.bat puts the file back into an apk. Correct me if I'm wrong.
I ran the aapt.exe but it quickly ran cmd then exited before I was able to see what was done. There were no guides I could find on how to use it, which didn't help.
I'd really like to know how to use aapt. I'm sure that's much easier and faster than running Eclipse. Please advise.
**This link is the download page from which you sent me regarding the apktool. Inside it includes those bat files along with aapt.exe.
http://code.google.com/p/android-apktool/wiki/9PatchImages
http://code.google.com/p/android-apktool/downloads/list
raider3bravo said:
The aapt came with the unpack and quickpack.bat. Which were in the apktool kit.
Click to expand...
Click to collapse
Errr.. what? ;-D I'm an author of apktool and I'm pretty sure there are no such files ;-) For Windows there should be: apktool.jar, apktool.bat and aapt.exe .
raider3bravo said:
I ran the aapt.exe but it quickly ran cmd then exited before I was able to see what was done. There were no guides I could find on how to use it, which didn't help.
Click to expand...
Click to collapse
aapt is more advanced tool, but you could try it if you want. Do:
fake AndroidManifest.xml file - simplest manifest is: http://pastebin.com/ck2EPh6U , you can copy it.
create file structure:
Code:
AndroidManifest.xml
res/
drawable/
1.9.png
2.9.png
3.9.png
...
open terminal, cd to a directory with above files
run "aapt p -f -F out.apk -M AndroidManifest.xml -S res"
unpack out.apk and copy *.9.png files to your apk.
Thanks. I'll have to try this out and see if it's faster than Eclipse. You were right on the files not being in the link provided. I somehow got them mixed up. Here's where I downloaded that apktool that included the quickpack.bat and unpack.bat files.
http://forum.xda-developers.com/showthread.php?t=882742
Brut.all said:
Errr.. what? ;-D I'm an author of apktool and I'm pretty sure there are no such files ;-) For Windows there should be: apktool.jar, apktool.bat and aapt.exe .
aapt is more advanced tool, but you could try it if you want. Do:
fake AndroidManifest.xml file - simplest manifest is: http://pastebin.com/ck2EPh6U , you can copy it.
create file structure:
Code:
AndroidManifest.xml
res/
drawable/
1.9.png
2.9.png
3.9.png
...
open terminal, cd to a directory with above files
run "aapt p -f -F out.apk -M AndroidManifest.xml -S res"
unpack out.apk and copy *.9.png files to your apk.
Click to expand...
Click to collapse
I will definitely be putting this thread to use, I am just learning this stuff, so this will be very helpful. Thanks raider, you have been a wonderful help to me so far
{
"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"
}
吨wrp root
Hi, it seems like this version of Magisk doesn't let you enable Magiskhide, am I right ?
(I'm on Realme UI 2.0 - Android 11) , is there a way to use my banking apps, Google Pay, etc.?
Thanks
This worked well.
Didn't work first time, but then I updated magisk to the latest version and it worked perfectly, whereas it was stopping before that.
Hey guys! Last root I did was on android 4.1 and I don't really know how to do it. I have Realme with C.05 soft. Will someone guide me?
Hi guys
This root is worked on europe version? Im from Slovakia. Rmx2202gdpr 11.a.17 .Thank you
qiurigao said:
View attachment 5486671
Click to expand...
Click to collapse
Hello. Is it possible to install this driver on Linux?
I could root a European RMX2202_11_a.17 this way.
First I checked OEM unlock in developer options.
The most difficult part is getting into bootloader. I used a program DeepTesting_realme-release_20210426_newID_signed.apk for this, which I had from https://forum.xda-developers.com/t/...-twrp-2022-02-21.4381727/page-3#post-86279181, I believe.
Hereafter I did under Linux the same as the batch files:
Code:
fastboot flashing unlock
Hereafter an automatic reinstall
Reenabling development options and USB debugging.
Code:
adb reboot bootloader
In bootloader:
Code:
fastboot boot twrp/twrp11.img
Change the language.
Uploaded a recent version of magisk renamed to zip to tmp
Code:
adb push Magisk-v24.3.zip /tmp
Pressed install in twrp and selected this file.
Hereafter reboot to system.
EDIT:
After the update to Android12 RMX2202_11_C.05, I could root it the same way using twrp/twrp12.img.
You can just press Cancel when asked for a password.
EDIT2:
After the last update RMX2202_11.C.16_1160_202204192320.44.7636e18c (for which I didn't remove root), the above method didn't work anymore.
fastboot boot twrp/twrp12.img
resulted in a black screen. I could adb in to recovery, but
/bin/twrp install /sbin/Magisk.zip
gave the following message:
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
EDIT3:
Booting the same way from the recovery I found here https://droidfilehost.com/download/download-realme-gt-5g-rmx2202-twrp-recovery-file/ worked. The only problem is that it is Chinese so you have to guess what to do.
EDIT4:
After the update to RMX2202_11.C.20_1200_202207201946.44.84bc864c, this method still works (when the bootloader is unlocked):
adb reboot bootloader
#WAIT
fastboot boot recovery.img
#WAIT
adb push Magisk-v25.2.zip /tmp
adb shell /bin/twrp install /tmp/Magisk-v25.2.zip
adb reboot
EDIT5:
Also works with RMX2202_11.C.27.
Rooted my device successfully but the banking apps not working. Is there any way to make it work magisk hide??
If you are using Magisk 24.3, you have to add the banking app to the DenyList. Go to Magisk settings. Turn on Zygisk and Enforce DenyList and add banking app to Configure DenyList.
Can someone fix systeam read only
Kabid0033 said:
Can someone fix systeam read only
Click to expand...
Click to collapse
there are somethings here and here but i didnt try yet
Kabid0033 said:
Can someone fix systeam read only
Click to expand...
Click to collapse
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
jkaltes said:
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
Click to expand...
Click to collapse
Thanxx I will try this
grown_man said:
there are somethings here and here but i didnt try yet
Click to expand...
Click to collapse
thnx for your concern buddy
jkaltes said:
Magisk is made so that it leaves /system intact and can be better hidden, but you can create files that replace existing ones. If in Magisk setting you check 'Systemless hosts', such a replacement file is created (which takes effect after reboot). How this is done you can see in /data/adb/modules
If you want to change more files, you can imitate this.
To change /etc/mkshrc I have created:
/data/adb/modules/mkshrc/system/etc/mkshrc
/data/adb/modules/mkshrc/module.prop
mkshrc is the replacement file
In module.prop I put:
id=mkshrc
name=mkshrc
version=1.0
versionCode=1
author=I
description=mkshrc edit
Click to expand...
Click to collapse
Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??
Kabid0033 said:
Hey if I want to edit in build.prop so I have to write all the values or only the values which I have to add??
Click to expand...
Click to collapse
The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.
So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.
I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.
jkaltes said:
The files in /data/adb/modules are taken in place of the original files. So if you open /system/etc/mkshrc, /data/adb/modules/mkshrc/system/etc/mkshrc is opened instead.
So if you want to edit /etc/mkshrc you copy /etc/mkshrc to /data/adb/modules/mkshrc/system/etc/mkshrc and then you edit it. If you have rebooted after it's creation, you can edit /etc/mkshrc. In reality, you will be editing /data/adb/modules/mkshrc/system/etc/mkshrc because if you open /etc/mkshrc, in reality /data/adb/modules/mkshrc/system/etc/mkshrc will be opened. Without much consequences you can try it out with /etc/mkshrc.
I have never modified /system/build.prop, but you should probably do the same.
Copy the original /system/build.prop to /data/adb/modules/amodulename/system/build.prop
After reboot, you can edit /system/build.prop because /data/adb/modules/amodulename/system/build.prop is opened instead of the original file.
Click to expand...
Click to collapse
Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc
Can you help me fix this
Kabid0033 said:
Hey I tried to send one app to system but it didn’t work so I remove that module but after that my most of the system apps not working
Like: camera, gmail, clock, calculator etc
Can you help me fix this
Click to expand...
Click to collapse
You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.
I don't understand you problem after removing the module. Did you reboot afterwards?
You can always reinstall Magisk.
jkaltes said:
You can't add files to /system, only replace files with your own. Something like: open is intercepted, but the directory structure is left intact. So, if you add something you have to use the name of something that already existed.
I don't understand you problem after removing the module. Did you reboot afterwards?
You can always reinstall Magisk.
Click to expand...
Click to collapse
You said that we have to put files in /data/adb/modules so that it can reflect in system
So I like to make one app to place in system /app
(eg: Like in older version of android we mangae to do that directly cause their system is rw)
(From this my apps stop working)
So I manually remove the folder from the modules then reboot
But it didn’t fix how it used to be