General [RMX2202] Realme GT 5G (UI2.0 & UI3.0) - ALL ROOT - Realme GT

{
"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

Related

[HOWTO] Make a skin for your tattoo.

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!

[MOD] Enable init.d scripts support on stock kernel

Hello!
This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him ) and his thread in the X10 section.
I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.
So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.
Instructions:
1. Download the zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.
*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.
Let me know if it worked for you!
{
"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"
}
Good, nice to see this posted here too.
Sent from my MT15i using XDA App
great work!
Could this be used in other android devices?
kcthomlau said:
Could this be used in other android devices?
Click to expand...
Click to collapse
Yes, it should be works well on other devices, just try it and let us know.
Sent from my MT15i using XDA App
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
sgj1 said:
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
Click to expand...
Click to collapse
no. I have now locked bootloader and it is working
sgj1 said:
it´s necessary to have unlocked bootloader?
I have followed this tutorial and have not created the file "init.d_log_test.txt"
when i go to /data/local/tmp i only have init.rc file
Click to expand...
Click to collapse
This is working great on mine mate, just try it again maybe you left something, i tested it with init.d scripts from SE Tweaked and it works.
Sent from my MT15i using XDA App
hello guys!
what kind of script is the neo?
Confirmed, working
I tried this mod and it seems to be working. Before its application, Supercharger tells me that he cannot reach init.d or something like that. But with this mod it can use init.d without any problems, no more warning. So it is working. Thank you
iridaki said:
Hello!
This is a small mod, inspired by non other than our great DoomLord (so if it helped you, thank him/donate to him/worship him ) and his thread in the X10 section.
I am trying a lot of things on my phone, so I often switch back and forth from stock kernel to DoomKernel.
However, I use lots of init.d scripts (my favorite one being SuperCharger)
and I just don't want to lose this feature when I'm on stock.
So, without further ado, here are the steps that are needed to make init.d scripts run automatically at boot on stock kernel.
Requirements:
1. Stock Kernel
2. Root
3. Busybox
4. CMW Recovery for Stock Kernel by nAa.
5. Root Explorer or any other similar app.
Instructions:
1. Download the zip and place it in a folder in your SD card.
2. With Root Explorer, go to /system/etc. Press the Mount RW button on top right corner.
a. If the file install-recovery.sh is not there, then press Menu and create a New File.
Name it install-recovery.sh and then long-press on it and select Open in Text Editor.
Paste this text in it:
Code:
#!/system/bin/sh
# init.d support
busybox run-parts /system/etc/init.d/
Save it and delete any .bak file that Root Explorer might have created. Set the permissions as in the attached screenshot.
OR
b. If the file install-recovery.sh is already there, long-press on it and select Open in Text Editor. Paste this text in the end:
Code:
# init.d support
busybox run-parts /system/etc/init.d/
In both scenarios, don't forget to leave one empty line at the end of install-recovery.sh file. ***
3. Reboot into Recovery and flash the init.d-autorunner-stock.zip.
4. Reboot your phone and with Root Explorer go to /data/local/tmp.
There should be a txt file there named "init.d_log_test.txt" and once you open it, you should see the word "done".
5. Now you can use your favorite init.d scripts on stock kernel!
If you want to check if the scripts you want to use actually work, please refer to one of my older threads about how to test them.
*** I am not including an install-recovery.sh because this is the file that Link2SD depends on, so it's better if you modify it yourself, rather than use mine.
Let me know if it worked for you!
Click to expand...
Click to collapse
this is working for neo v?
It should on stock yes
Sent from my MT15i using Tapatalk
onlavu said:
Before its application, Supercharger tells me that he cannot reach init.d or something like that.
Click to expand...
Click to collapse
Have you checked original thread from zeppelinrox: http://forum.xda-developers.com/showthread.php?t=991276
where he shared his way(AutoStart Script) of enabling init.d for stock ROM/kernel: http://forum.xda-developers.com/showthread.php?t=1017291
kormatoes said:
It should on stock yes
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
ok but i have a noob question,
how to change vm heapsize to 48?
Pandemic said:
ok but i have a noob question,
how to change vm heapsize to 48?
Click to expand...
Click to collapse
You need to edit build.prop in system folder.
Taptalked
Tenacius D said:
You need to edit build.prop in system folder.
Taptalked
Click to expand...
Click to collapse
hm ok and how will i do that with rootxplorer, what must i do and tick/untick?
Edit: Anyone know??
With rootxplorer go to system mount read/write (see screenshot)
long press build.prop open in text editor find vm heapsize change it to 48 save the change and reboot. Make buckup of build.prop just in case.
Taptalked
Pandemic said:
hm ok and how will i do that with rootxplorer, what must i do and tick/untick?
Click to expand...
Click to collapse
Have you tried long press on file, and select "Open in Text Editor"?
EDIT: was to slow
Tenacius D said:
With rootxplorer go to system mount read/write (see screenshot)
long press build.prop open in text editor find vm heapsize change it to 48 save the change and reboot. Make buckup of build.prop just in case.
Taptalked
Click to expand...
Click to collapse
i cant edit it when i open as text:S
Pandemic said:
i cant edit it when i open as text:S
Click to expand...
Click to collapse
Not open as text, scroll down and open in text editor.
Taptalked

[WINDOWS]aPkgMan - Easy batch install/uninstall/rename/backup APK packages ^2012/4/16

Just having fun around with Android so I made this little program aPkgMan
Features
Very light-weight (less than 45KB, just extract and run)
Batch install APK packages via ADB (restore data option available)
Batch uninstall APK packages via ADB
Batch backup APK packages via ADB (backup data option available)
Batch renaming APK packages (using file mask)
Check for online version of APK packages
v0.1
http://i.imgur.com/4VEhD.png
v0.2
http://i.imgur.com/vvhk7.png
v0.3
http://i.imgur.com/vkZfM.png
v0.4
{
"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"
}
How to use?
Download, extract and run
Enable USB debugging mode on your device, connect it to computer via USB cable and select it from the Home tab (Hit Refresh to refresh the connected device list)
You are ready to go
Tip : If the program won't start, open Task Manager and kill the "mshta.exe" process and restart the program
Changelog
2012/04/01 - Initial version
2012/04/02 - v0.2, added batch renaming (support file mask) and backup packages
2012/04/05 - v0.3, added restore package data after installing, added backup data for package; plus code cleaning and commenting and other minor improvements
2012/04/16 - v0.4, added new feature checking for online version of APK packages
aPkgMan is absolute free. Any questions, comments or suggestions are welcome. If you find it useful please click Thanks button below
Good Work
wow, this will be very helpful.
just a question, would this backup app+settings?
thanks!
melander said:
wow, this will be very helpful.
just a question, would this backup app+settings?
thanks!
Click to expand...
Click to collapse
I'm about adding backup/restore feature and a simple file manager too
Thanks man
2012/04/02 - v0.2, added batch renaming (support file mask) and backup packages To restore use the batch install feature
The next things to do are supporting ADB over WiFi and a file manager.
I use "pull" command to backup app data but ADB returns "0 files pulled. 0 files skipped". Can anybody tell me why please?
Hm,i'm havin problem with picking apk path
Sent from my SK17i using xda premium
Black_jackss said:
Hm,i'm havin problem with picking apk path
Sent from my SK17i using xda premium
Click to expand...
Click to collapse
Hi, can you tell me where the problem occurred please? And did the program return any error message?
acb123 said:
Hi, can you tell me where the problem occurred please? And did the program return any error message?
Click to expand...
Click to collapse
It's just i didnt understand how to pick the apk i want to install
Sent from my SK17i using xda premium
New v0.4 as of 2012/04/16, added new feature checking for online version of APK packages Some packages will return "Not Found" since they are no longer on Play Store.
acb123 said:
2012/04/02 - v0.2, added batch renaming (support file mask) and backup packages To restore use the batch install feature
The next things to do are supporting ADB over WiFi and a file manager.
I use "pull" command to backup app data but ADB returns "0 files pulled. 0 files skipped". Can anybody tell me why please?
Click to expand...
Click to collapse
I am having the same issue in an app I am building for the Acer a510.
Or should I say, WAS having.
Bad Code
Code:
adb pull /system/app/ /Backups/system/app
Good Code
Code:
adb pull /system/app/ ./Backups/system/app
The difference for me was the " . " for the destination.
It was creating the files on my root C:\ drive instead of the
intended directory. I pulled the entire contents where I want now.
I am not sure if this will help you at all, but I thought I would share.
***EDIT***
It worked until I got to /data/app
There is where I got the same error.
"0 files pulled. 0 files skipped"
After changing permissions on the folder,
everything pulled.
marlopainter said:
I am having the same issue in an app I am building for the Acer a510.
Or should I say, WAS having.
Bad Code
Code:
adb pull /system/app/ /Backups/system/app
Good Code
Code:
adb pull /system/app/ ./Backups/system/app
The difference for me was the " . " for the destination.
It was creating the files on my root C:\ drive instead of the
intended directory. I pulled the entire contents where I want now.
I am not sure if this will help you at all, but I thought I would share.
***EDIT***
It worked until I got to /data/app
There is where I got the same error.
"0 files pulled. 0 files skipped"
After changing permissions on the folder,
everything pulled.
Click to expand...
Click to collapse
Thank you so much for your sharing On my Sk17i I also changed the folder permission too but still didn't work, but upgrading to custom ROMs makes it work. I will note your solution in the next update of the program so it could help other users
acb123 said:
Thank you so much for your sharing On my Sk17i I also changed the folder permission too but still didn't work, but upgrading to custom ROMs makes it work. I will note your solution in the next update of the program so it could help other users
Click to expand...
Click to collapse
The way I changed permissions was in Root Explorer.
I believe the way I changed them made it 777, not sure.
hi man, thanks for sharing your work!!
it's a really useful program, I just used it to delete a theme apk: I applied the theme (CM 7) and when I reboot my phone had a bootloop!
just a question: why is this software not into the general development section? Here is hard to find it!
anyway, a great alternative for people who don't / are not able to use adb..
see you!
brainvision said:
hi man, thanks for sharing your work!!
it's a really useful program, I just used it to delete a theme apk: I applied the theme (CM 7) and when I reboot my phone had a bootloop!
just a question: why is this software not into the general development section? Here is hard to find it!
anyway, a great alternative for people who don't / are not able to use adb..
see you!
Click to expand...
Click to collapse
It's almost a year and suddenly a new post appeared. Thanks for your interest ! I also hope I could find way to update it in the future.
hi acb123, a really nice little tool you developed!
do you think there would be any way that the uninstall menu does not show every single installed "app", but only the ones that the user installed and can be actually removed?
download link???????
i-HaBiB said:
download link???????
Click to expand...
Click to collapse
Check the attachments in first post

[Split Screen] Multi-window on moto G4 plus.

Hello people. After successful root and installing xposed module n-ify you still don't get a multi window feature. Though many of you must be familiar with it but those who ain't. This is just the right place.
Here's something new .... U can do it without root too.
Enable Multiwindow WITHOUT ROOT
Requirements:
1. Working adb and fastboot on PC
2. Notepad++ or anything to edit the build.prop
3. TWRP on your device
4. Cool Attitude
Let's begin.
(Note: The commands in command prompt are to be give without the Quotes)
1. Boot your Android device into TWRP recovery.
2. Select Mount and then select System from the list of partitions to mount the system partition and then go back.
3. Connect your device to the PC.
4. Open minimal adb and fastboot or just open command prompt if u have adb shell installed separately
5. Type command, "adb devices" and if adb is properly installed, your device will be listed.
Then type command,
"adb pull /system/build.prop"
The above command will download the build.prop file to your PC in the same directory where your command prompt is running from. (Tip: Make a copy of your build.prop)
6. Open the build.prop file on your PC using the Notepad++ program.
7. Find the line "ro.build.type=user" and change it to "ro.build.type=userdebug" and save the changes
8. Now again in command prompt, type the command
"adb push build.prop /system/"
9. Now set the correct permissions for the build.prop file with following commands (issue them one-by-one):
"adb shell"
"cd system"
"chmod 644 build.prop"
10. Now reboot your device.
11. Go to Developer options in settings and you'll see a "Multi-window mode" just toggle it on and voila.
Enable Multiwindow on Rooted device...!
Requirements:
1. Root access
2. Any root explorer (es explorer is very good and I'm using it in this tutorial)
Let's begin.
1. After rooting your Moto G4 plus, download and install any root explorer and grant it superuser access. (I'm using es explorer)
2. In the explorer, go to Device\ System\ Build.prop.
3. Copy the build.prop to any other location (incase you wish to revert this, this is kinda backup step)
4. Now again go to original build.prop (Device\ System\ Build.prop)
5. Open it with the es note editor (I'm using es explorer here)
6. Find the line "ro.build.type=user" and click on the 3-dot menu on top right side (es explorer) and click edit.
7. Now edit the line and change "user" to "userdebug" (without quotes)
8. Save it and Reboot your device.
9. Go to Developer options in settings and you'll see a "Multi-window mode" just toggle it on and voila.
You have the Working multi window. Screenshots attached.
[To get other Android Nougat features, just get working xposed on your device and install n-ify module. Activate it and there you are!]
Screenshots here,
https://drive.google.com/folderview?id=0Bya7b1JXXZycS2pHT3d4alhxaWc
A thanks would be really appreciated
Tested and it works
Added screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's an old trick. I know but it's really cool
Would this work on the regular G4? Noob question but I don't wanna mess up my phone.
NexusFan9219 said:
Would this work on the regular G4? Noob question but I don't wanna mess up my phone.
Click to expand...
Click to collapse
Yeah sure it would. Go ahead. Just make a copy of Build.prop. Incase u desire to revert it or Incase u edit something else in build.prop
If u are not rooted and still want to have multiwindow...... Then u can pull the build.prop via adb and edit it and then push it again into the system via adb.......
If u do not get it or want a detailed explanation then comment below..... I'll update the OP
cool_sid said:
If u are not rooted and still want to have multiwindow...... Then u can pull the build.prop via adb and edit it and then push it again into the system via adb.......
If u do not get it or want a detailed explanation then comment below..... I'll update the OP
Click to expand...
Click to collapse
Pl update process for non-root, dont think its a noob question..
sirtbhopal said:
Pl update process for non-root, dont think its a noob question..
Click to expand...
Click to collapse
OP has been updated with the Non Root method.
N buddy..... It's just question...... Never a noob or a silly question.....
U don't know guys..... Some simple questions teach lot to us.....
Just like I learned that I can edit system without root too just by mounting the system in twrp....
So guys now u can do this without even having root access on your device....
Multiwindow on Moto G4 Plus and that too without root.....
Rush it guys....
So I hear you can't do OTA updates with TWRP installed? Is there a way to do the non root method without TWRP? If not, is there a quick way to install TWRP, make the fix and then return to normal recovery? I can't see much in the way of guides?
Thanks
damonsmith666 said:
So I hear you can't do OTA updates with TWRP installed? Is there a way to do the non root method without TWRP? If not, is there a quick way to install TWRP, make the fix and then return to normal recovery? I can't see much in the way of guides?
Thanks
Click to expand...
Click to collapse
Use recovery switcher app from XDA..... It also is great to quickly switch recoveries....... Then u can easily switch between stock recovery n twrp
To apply ota..... Flash fire can also be used.... (Never used it though)
And u can modify system without root or a custom recovery at least...... Hope u can understand that......
Rest I'll see if there is any other possible way
cool_sid said:
Use recovery switcher app from XDA..... It also is great to quickly switch recoveries....... Then u can easily switch between stock recovery n twrp
To apply ota..... Flash fire can also be used.... (Never used it though)
And u can modify system without root or a custom recovery at least...... Hope u can understand that......
Rest I'll see if there is any other possible way
Click to expand...
Click to collapse
What he said, plus you can just boot TWRP instead of flashing it if you want to use features of TWRP without flashing it.
Tel864 said:
What he said, plus you can just boot TWRP instead of flashing it if you want to use features of TWRP without flashing it.
Click to expand...
Click to collapse
Yeah instead of giving command.
fastboot flash recovery twrp.img
U can use
fastboot boot twrp.img
I guess......
On my N5, with TWRP I can flash Google OTA files just fine. Maybe with TWRP for Moto G4 that can be possible...
Recently picked up this phone up, sucks there isn't much for the G4's compared to the Nexus/Pixel devices, even tho they basically run stock AOSP. But I have an Nexus 5 still too
Anyway, I tried out your little tip and it worked like a charm ?
Thanks for this!
My device = Moto G4 XT1625_retail_non-amazon_garbage lol
Thanx

Is it possible to change the default TimePicker dialog in Android?

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

Categories

Resources