Hey guys,So um i am using redmi note 10 miui 12.5.3 global and i pulled the stock miui camera and gallery apk using adb pull commands. I plan to install pixel experience custom rom. How would i install these in that rom?
Would require this custom ROM gets rooted, phone's bootloader gets permanently unlocked, phone's Android's AVB permanently gets disabled, as also phone's Android's SELinux permanently gets disabled.
can i find links for tutorial on how to do this?
and even if I managed to do all these,what do i do after that? would the apk install just like that?
ahmed6392 said:
and even if I managed to do all these,what do i do after that? would the apk install just like that?
Click to expand...
Click to collapse
If the APKs are of type
system-app
then you've to mount device's /system partition
user-app
then you've to mount device's /data partition
as RW before installing the APKs.
i've done the three steps. i didnt understand the last thing.How do i install the apks? do i need a seperate installer or a custom recovery? could you please explain and the apks are of system-app
You simply install them by means of ADB
Code:
adb devices
adb install <LOCATION-OF-APK-FILE-ON-PC-HERE>
Related
Earlier today I successfully rooted my phone and uninstalled a bunch of bloatware. Foolishly, I also uninstalled the Samsung keyboard (figuring I only use the Swype keyboard) which I now suspect it is used to enter my pin when turning the phone on. Now I can't get past the pin entry because the keypad does not show up. Is there anyway to reinstall the app in this situation?
trusko1 said:
Earlier today I successfully rooted my phone and uninstalled a bunch of bloatware. Foolishly, I also uninstalled the Samsung keyboard (figuring I only use the Swype keyboard) which I now suspect it is used to enter my pin when turning the phone on. Now I can't get past the pin entry because the keypad does not show up. Is there anyway to reinstall the app in this situation?
Click to expand...
Click to collapse
You can get a copy of the .apk file and then boot to TWRP, then use adb to sideload the .apk to /system/app or /system/priv-app (wherever it was at before you deleted it).
Or you can reflash your stock firmware or custom ROM if you're using one.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I flash magisk.zip but it is normal app not system app
Magisk is a 3rd-party-app. Take note that a system-app is necessary part of Android OS. And Magisk isn't.
jwoegerbauer said:
Magisk is a 3rd-party-app. Take note that a system-app is necessary part of Android OS. And Magisk isn't.
Click to expand...
Click to collapse
Not quite right, when a 3rd party user app is installed or pushed to system, it then becomes a system app. The term "system app" refers to any app that is in the system partition, it has nothing to do with whether the app is a necessary part of the OS. Stock system apps, or, at least, "some" of them can be considered to be necessary parts of the OS but this isn't completely true because a lot of devices come pre-installed with non essential bloatware apps in the system partition. These non essential bloatware apps can be removed via root or by adb on non rooted devices because they are not necessary parts of the system.
For me a "system app" is - as already mentioned - an app that comes pre-installed in Android ROM's one of the partitions /system/app or /product/app or /product/overlay or /vendor/app, is a "system app" an app that is intended for the functioning of the Android device.
Your admission to this view of mine does not change my opinion.
private app is also a system app but seems to be an add-on. and i flashed the zip but it was not set as a system app, it seems the zip is not related to install like the system in twrp, and twrp mounted the system but couldn't delete any folder in. rooted but so bad!
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
iBreakStuff said:
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
Click to expand...
Click to collapse
It may be having a conflict with cached data from the version that you installed, removing the cached data might allow you to install the version you want.
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Click to expand...
Click to collapse
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
iBreakStuff said:
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
Click to expand...
Click to collapse
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So I tried what you suggested, I got the same result. Maps uninstalls but still lives in the root directory. Not being an ADB expert I went into adb shell super user mode and tried the the rm command to delete the folder, also the remount system command. Neither of those worked. Trying to install the older APK results in "App not installed"
And yes I have Magisk manager. It installed the latest version automatically. I use RootExplorer and it has superuser permissions.
Would something like this work? I'm not completely clear on how this works.
https://www.isrgrajan.com/how-to-copy-and-delete-files-in-android-using-recovery-mode.html
I'm quite new to using a phone without root, so is there a possibilty to add apks to system without rooting?
I tried ADBFastbootTools but it seems like it won't add anything. No apk and also no new folder.
Impact7 said:
I'm quite new to using a phone without root, so is there a possibilty to add apks to system without rooting?
I tried ADBFastbootTools but it seems like it won't add anything. No apk and also no new folder.
Click to expand...
Click to collapse
System partition is write protected. Not only Root is needed, you need a systemlees system like Magisk for example to not break dm-verify. Another option should be a rooted phone with dm-verify disabled.
In both cases, you will need a unlocked bootloader and root
Hello people,
I have unlocked my phone yesterday and installed Magisk and root explorer.
I would like to replace the files in /system/fonts to change the default fonts. I tried to flash a twrp zip with new fonts and also manually tried to replace the fonts. But the system cannot be mounted as r/w in root explorer even after granting root permissions and flashing twrp zip does nothing. Is there any way to overcome this issue to mount system as r/w?
I mean what is the point of rooting if we cannot modify system!
Thanks!
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Many modifications are starting to be systemlessly. Like viper4android and others. The worst is not being able to flash system/vendor images in recovery.
wopr33 said:
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Click to expand...
Click to collapse
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
I don't know how TWRP works for the Poco X3, but for the Redmi Note 4 I copied the file using the built-in explorer, with no errors.
I think you need to activate the system partition in R/W in TWRP.
htcmusic said:
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
Click to expand...
Click to collapse
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Slim K said:
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Click to expand...
Click to collapse
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
htcmusic said:
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
Click to expand...
Click to collapse
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ?
Click to expand...
Click to collapse
You don't need twrp to install a Magisk module. You can do that through the Magisk Manager just as easily.
wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
Click to expand...
Click to collapse
I just installed the magisk module with custom fonts in internal storage as mentioned in the github page. It was magical, I was trying to replace the fonts for the whole day and it didn't work. Somehow this magisk module does the job.
Dear All,
I am using the Pixel 5 with Android 13 Build No: TQ1A.230105.001 and I rooted by flashed the image from Magisk app through ADB.
I checked and the phone said ROOTED and I cant grant access to apps but when I change font by any app, it isn't work and I copy in Root Explorer, I can't change the button "MOUNT R/W".
What can I do now? Should I re-root or flash again???
Thank you and waiting for your help.
Some new versions of android restrict it, and you have to do so through recovery.
Arealhooman said:
Some new versions of android restrict it, and you have to do so through recovery.
Click to expand...
Click to collapse
can I install TWRP on Andoird 13???
dpn025 said:
can I install TWRP on Andoird 13???
Click to expand...
Click to collapse
Yes. You Amy be able to set your system to rw through stock recovery, take a look if you can mount it.
Arealhooman said:
Yes. You Amy be able to set your system to rw through stock recovery, take a look if you can mount it.
Click to expand...
Click to collapse
please help me, I can't understand it.
do you have atock recovery? Or TWRP?
Arealhooman said:
do you have atock recovery? Or TWRP?
Click to expand...
Click to collapse
I'm still stock recovery.
Boot into stock recovery. Take a photo for me. If you can’, just tell me if there’s a option that starts with “mount” and what does it say?
From Android 10 and above, the system has changed to one Super Partition. This means that the system cannot be mounted as R/W as it's Read-only by nature.
There is a tool Universal SystemRW that supposedly converts the Read-only to R/W. I haven't tried it personally but it looks very promising.
swangjang said:
From Android 10 and above, the system has changed to one Super Partition. This means that the system cannot be mounted as R/W as it's Read-only by nature.
There is a tool Universal SystemRW that supposedly converts the Read-only to R/W. I haven't tried it personally but it looks very promising.
Click to expand...
Click to collapse
No, TWRP can mount too. And stock recovery for some devices
Root explorer is screwed up for some pixel ROMs including lineage so I don't know about stock. It will crash when trying to read many files, specifically text files you should normally be able to read or edit. It's working on the latest pixel experience ROM but crashed on two other roms I was trying
dpn025 said:
please help me, I can't understand it.
Click to expand...
Click to collapse
use material file manager. It's the only one that seems to be working right now